[Avr-GNU] HelloPthreads

[HelloPthreads]
Create a simple reusable example for pthreads.

Since AVR doesn't use threads, it uses interrupt subroutines, i am closing this issue as doesn't exist, this issue content is transferred to #64.


[GHSA-x3p3-929j-pq66] Improper Neutralization of Input During Web Page Generation in Jenkins

Updates

References
Source code location

Comments
Add patch links and source code location related to CVE-2015-7536.
In https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09 shows CVE-2015-7536 is related to SECURITY-95.

Hello, I apologize for the confusion. The two patches are as follows:
https://github.com/jenkinsci/jenkins/commit/d3fb2c09f29007dce84a213ae8323df1105dcc30
https://github.com/jenkinsci/jenkins/commit/27c303417a226bf4c06a588570f28ac2e2507c6c


Decouple layout and content

It's really bizarre to me that content pages like "overview," "components," etc. are nested within views/. These pages often include documentation content, yet cannot use Markdown and exist separately from "docs." It feels strange to me that the only way to create a new, non-Markdown page at the root or an arbitrary location is to create a brand-new "view."
I guess instead of this:
├── docs/
│   └── javascript.md    → /docs/javascript.html
└── views/
    ├── layouts/
    ├── index.html       → /index.html
    └── typography.html  → /typography.html

I'd love for the structure to be more like this (actual directory names aren't as important as the structure more clearly influencing the end result):
├── content/
│   ├── docs/
│   │   └── javascript.md  → /docs/javascript.html
│   ├── index.html         → /index.html
│   └── typography.md      → /typography.html
└── layouts/

All righty, it is now time to answer the question, based on our ideal situation:
What defines what HTML pages get created?
I've heard input that a hard coupling between views and directories full of patterns is not ideal. Now's your time to brainstorm! What do you think is the best logic for determining the structure of the output HTML content?
This includes all of the pieces involved: docs, patterns (and collections of patterns), sandbox and any arbitrary pages you may wish to add to the mix.

Okay, this is truly a brainstorm for me. But I'm going to describe how I might structure this. I am not married to what I describe.
Types of Stuff
Layouts (or "Templates"?)
Layouts are written in Handlebars (or whatever). They do not represent the compiled results. They are simply the containers for optional page content.
As an example, consider a layout file named simple.hbs that looks like this:
<!doctype html>

  <title>{{title}}</title>

  {{{contents}}}

This would not result in a simple.html page being compiled. But any page (more on that later) that specified layout: simple in its Frontmatter would be compiled with the aforementioned layout.
Pages (or "Content"?)
Pages define static content to be compiled. They should have a default layout assigned to them so you don't need to specify, but you can override the layout via Frontmatter.
This would allow you to structure any informational pages, documentation, etc. any way you'd like:
├── docs/
│   └── javascript.md    → /docs/javascript.html
├── index.md             → /index.html
├── pages/
│   ├── home.hbs         → /pages/home.html
│   └── product.hbs      → /pages/product.html
└── sandbox/
    └── my-prototype.hbs → /sandbox/my-prototype.html

If you wanted a page to not have the style guide nav, or to use some completely different layout, you'd set the layout property within its Frontmatter.
Patterns and Collections
The most complicated part of things are the patterns themselves. Which kinda makes sense... that's the whole reason we're making a tool, and not simply re-using a static site generator!
Directories in patterns/ result in compiled pages as long as they have one or more visible pattern files as immediate children:
├── typography/               → /typography.html
│   ├── headings.hbs
│   └── paragraph.hbs
├── components/
│   ├── button/               → /button.html
│   │   ├── 00-base.hbs
│   │   ├── 01-primary.hbs
│   │   ├── 02-secondary.hbs
│   │   └── social.hbs
│   └── icon/                 → (nothing, includes only a hidden pattern)
│       └── _icon.hbs
└── utilities/                → /utilities.html
    ├── space.hbs
    └── text.hbs

Patterns (including hidden) are available to other patterns and pages as partials ({{>collection.pattern}}).
Layouts have access to two objects that result from this structure:

An object representing the hierarchy of all visible patterns. This allows layout templates to construct navigation.
An object representing the current collection (if any). This can be used by the layout that compiles the collection pages.

Individual patterns are never compiled. They must always be part of a collection, or included by a page.
Putting It All Together
I find it helps sometimes to visualize what the start and end results might be. Here's my attempt to visualize an example source and destination directories (for this stuff only, not assets and the like):
Source
├── layouts/
│   ├── partials/
│   │   ├── header.hbs
│   │   ├── footer.hbs
│   │   └── nav.hbs
│   ├── default.hbs
│   ├── page.hbs
│   └── sandbox.hbs
├── pages/
│   ├── docs/
│   │   └── javascript.md
│   ├── index.md
│   ├── pages/
│   │   └── home.hbs
│   └── sandbox/
│       └── my-prototype.hbs
└── patterns/
    ├── typography/
    │   ├── headings.hbs
    │   └── paragraph.hbs
    ├── components/
    │   ├── button/
    │   │   ├── 00-base.hbs
    │   │   ├── 01-primary.hbs
    │   │   ├── 02-secondary.hbs
    │   │   └── social.hbs
    │   └── icon/
    │       └── _icon.hbs
    └── utilities/
        ├── space.hbs
        └── text.hbs

Result
├── button.html
├── docs/
│   └── javascript.html
├── index.html
├── pages/
│   └── home.html
├── sandbox/
│   └── my-prototype.html
├── typography.html
└── utilities.html

Misc. Thoughts

I'd love if files with the extension .md were parsed with Markdown, while files with a Handlebars extension were compiled with handlebars. This would be the most helpful with pages (a documentation page could end in .md for instance), but it might also be useful for typographic patterns?
I don't really care if patterns/components/button/ gets compiled to button.html or components/button.html.
If we do have example pages, it might be confusing for them to be nested in pages/pages in our source directory..?

Riffing on what you wrote:

I think it's nice to have a directory that, as closely as possible, contains things that will result in output HTML. In my case, I'm grouping most of this under a content directory. Any single file under docs, pages, or sandbox will result in an output HTML file. It's not as easy to do a one-to-one representation in source of the patterns, but I think that's OK.
I'm segregating templates outside of content and sticking layouts and partials inside.
One would be able to dictate within frontMatter what layout or whatnot to use against a given resource within content (excepting patterns), with some sane defaults (page.hbs, docs.hbs, e.g.).
I'm still having some semantic difficulty between layouts and, uh, not-layout hbs source.

Source
├── content
│   ├── docs
│   │   ├── 01-howto.md
│   │   └── javascript.md
│   ├── pages
│   │   ├── arbitrary-page.hbs
│   │   └── nested-page
│   │       └── index.hbs
│   ├── patterns
│   │   ├── components
│   │   │   ├── button
│   │   │   │   ├── 00-base.hbs
│   │   │   │   ├── 01-primary.hbs
│   │   │   │   ├── 02-secondary.hbs
│   │   │   │   └── social.hbs
│   │   │   ├── icon
│   │   │   │   └── _icon.hbs
│   │   │   └── link
│   │   │       └── 01-visited.hbs
│   │   ├── typography
│   │   │   ├── headings.hbs
│   │   │   └── paragraph.hbs
│   │   └── utilities
│   │       ├── space.hbs
│   │       └── text.hbs
│   └── sandbox
│       └── my-prototype.hbs
└── templates
    ├── default.hbs
    ├── docs.hbs
    ├── layouts
    ├── page.hbs
    ├── partials
    │   ├── footer.hbs
    │   ├── header.hbs
    │   └── nav.hbs
    └── sandbox.hbs

Resulting in:
Output
├── arbitrary-page.html
├── docs
│   ├── 01-howto.html
│   └── javascript.html
├── nested-page
│   └── index.html
├── patterns
│   ├── components
│   │   ├── button.html
│   │   └── link.html
│   ├── index.html
│   ├── typography.html
│   └── utilities.html
└── sandbox
    └── my-prototype.html

Note:

Nesting of the pattern library under patterns. I suggest this because it's easier to scan, lets us potentially use the output for more than a pattern library, and prevents namespace collisions.
For pattern output, I'm going here with an approach of: any directory under patterns in source that has any pattern files in it will generate an HTML page. That HTML page would be named after the parent directory and would contain the patterns from that directory. I do like nesting the output directories so that they represent source (not flattening to top level). Note that a patterns subdirectory that only contained directories would not result in an HTML file.
Anything under pages in source would get output at the top level.

It's the end of the day so I might be getting a little fuzzy...but this feels like it's overall going the right direction! Keep it coming!

In your example tree, I'm not sure why docs/ are not handled just like pages/? I know in Fabricator's example they are handled as "material," but in our projects we never use them that way. I think they should just be pages, and we should allow pages to be written in Markdown (page-title.md).

Nesting of the pattern library under patterns. I suggest this because it's easier to scan, lets us potentially use the output for more than a pattern library, and prevents namespace collisions.

I am not emphatically opposed to this. On principle, it's really no different than nesting journal/ or posts/ under content/ and treating it special in a static site (a strategy I believe you and I both employ).
That said, I can't help but wonder if separating patterns/ from pages/ might be useful as a cognitive line in the sand, a clear indication that patterns/ are handled differently than pages/. In Fabricator, it's confusing that layouts/ live together with views/... I'm not sure it would be any less confusing to have material/ living in views/ instead.
 But by that logic, our Gulpfile should be buried somewhere bizarre and all our patterns should be in the repo root, so I'm unsure how valid an argument that is! :laughing:

Briefly, I agree with most of your feedback. I think your insight about having patterns elsewhere because they don't have a one-to-one pages-output connection is a good one. Let me think on the docs one—it may be fine; something is bugging me about it but I haven't quite figured out what yet :). More soon.

As more food for thought re: docs...
I've always hated the heading "docs," because the whole deliverable is documentation. It doesn't really say anything to the viewer.
If you look at our most recent shipped pattern library (no link since it's not open source), it seems arbitrary to me that a page like "Icons" is treated differently than a page like "Naming Conventions." They're both pages documenting how to do things with a combination of prose and figures/examples... the only difference is where they're output, and whether or not they're written in Markdown or HTML.
Also using that pattern library as an example, it seems completely silly that a page like "Overview" absolutely cannot be written in Markdown. It's 100% prose! :laughing:

TL;DR: I feel like relegating documentation in Markdown to a specific, special directory inadvertently establishes a "technical documentation ghetto." I'd like it to be a first-class citizen.

I agree with this. It seems like Markdown should be able to exist anywhere, and by default should be rendered to a corresponding HTML page with an assumed layout that can be overridden via front-matter.
patterns
└── components
    └── button
        ├── 00-base.hbs
        ├── 01-primary.hbs
        ├── 02-secondary.hbs
        └── index.md

---
foo: bar
baz: bang
layout: some-other-layout
---

This is the content. Maybe this can take the place of "notes"?

Also worth noting:

We can always still have regular HTML within Markdown.

I would propose this:

Any file under pages that is .md will be parsed as markdown and will generate an output HTML file
Let's not do this inside of the patterns structure—it's a bit too hard to scan what input/output relationships are for files both for humans and for the already-complex globbing and parsing mechanism for patterns

That is, yep, let's support markdown-anywhere inside of the content directories, but let's not do it from inside patterns as it is already complicated enough in there.
Thoughts?

Expanding a little:

Any file...that is .md will be parsed as markdown and will generate an output HTML file

By default, that's how we would treat those files. Let's pretend we call this feature (processing content and generating HTML output) docPages (though we probably won't because that term is lame). Say the default handling is something like (this is pseudo-code):
const defaults = {
// ...
  docPages: {
    glob:  'src/content/pages/**/*.md',
    contentFn: (contents, filePath) => marked(contents),
    defaultLayout: 'src/templates/docs.hbs'
  }
};

The notion of contentFn is something I'm already using in a few places—it provides a sensible default function for running over files' contents when they're parsed (e.g. JSON over JSON data, yaml over YAML data) but can be overridden with options. In this case, we'd have a default content-parsing function of markdown and look for .md files, but there's no reason the glob or the parsing function couldn't be specified to do something differently in a given installation.
The implication here is that defaultLayout (or whatever we ultimately name it) could be overridden in front matter.

Let's not do this inside of the patterns structure—it's a bit too hard to scan what input/output relationships are for files both for humans and for the already-complex globbing and parsing mechanism for patterns

If this is a technical limitation, I'm fine with it. I'm not so sure about it as a design decision. Some patterns, particularly those describing default typography, might be easier to write using Markdown.

If this is a technical limitation, I'm fine with it. I'm not so sure about it as a design decision. Some patterns, particularly those describing default typography, might be easier to write using Markdown.

It's technical if we want .md files inside of patterns to generate a unique output page. It's not a problem as much if we want .md files inside of patterns to get marked-parsed but otherwise be treated as a pattern.

It's not a problem as much if we want .md files inside of patterns to get marked-parsed but otherwise be treated as a pattern.

:point_up: This is what we want for sure!

All right! An attempt to boil down the things I've heard and seen and thought! Let's propose this as a src tree:
├── pages
│   ├── about.hbs
│   ├── about.md
│   ├── arbitrary-page.hbs
│   ├── docs
│   │   ├── 01-howto.md
│   │   └── javascript.md
│   ├── nested-page
│   │   └── index.hbs
│   ├── sandbox
│   │   └── my-prototype.hbs
│   └── somePage.md
├── patterns
│   ├── components
│   │   ├── button
│   │   │   ├── 00-base.hbs
│   │   │   ├── 01-primary.hbs
│   │   │   ├── 02-secondary.hbs
│   │   │   └── social.hbs
│   │   ├── icon
│   │   │   └── _icon.hbs
│   │   └── link
│   │       ├── 01-visited.hbs
│   │       └── notes-about-links.md
│   ├── thing.md
│   ├── typography
│   │   ├── headings.hbs
│   │   └── paragraph.hbs
│   └── utilities
│       ├── space.hbs
│       └── text.hbs
└── templates
    ├── layouts
    │   └── default.hbs
    ├── page.hbs
    ├── partials
    │   ├── footer.hbs
    │   ├── header.hbs
    │   └── nav.hbs
    └── sandbox.hbs

And as output:
├── about-01.html
├── about.html
├── arbitrary-page.html
├── docs
│   ├── 01-howto.html
│   └── javascript.html
├── nested-page
│   └── index.html
├── patterns
│   ├── components
│   │   ├── button.html
│   │   └── link.html
│   ├── patterns.html
│   ├── typography.html
│   └── utilities.html
└── sandbox
    └── my-prototype.html

Now to talk through how we got to this dist:
Pages

There is a one-to-one relationship for all files under pages to a single HTML file.
Per suggestion, we can parse the contents of these files differently depending on extension.
Pages, like other files, have recourse to frontMatter to override defaults and set data.
Note that I've introduced a purposeful namespace collision by creating an about.hbs and an about.md file. Let me know if there's a different way you'd like to handle that than what I've done.
I've left a docs directory there but that name doesn't have any real meaning. Point being: you can nest pages however you like.

Patterns

In this example, I've put patterns inside of a patterns directory in dist. I kind of like that, but am also amenable to making that an option that can be passed to the builder.
The rule for creating an HTML page from anything in patterns: If a directory has any files in it, a page, named after the directory, will be created. Ergo patterns.html but not components.html. (Patterns.html would contain the thing.md output).

I still need to get a sense of how sandbox items differ from other pages. I'll get to that at some point!
/cc @tylersticka @erikjung @mrgerardorodriguez

Note that I've introduced a purposeful namespace collision by creating an about.hbs and an about.md file. Let me know if there's a different way you'd like to handle that than what I've done.

I almost think this should just error out or show a warning and override the file. I would rather the tool tell me "hey, these aren't named uniquely" than to inadvertently start relying on permalinks that were auto-renamed like that. That's just my knee-jerk opinion!

In this example, I've put patterns inside of a patterns directory in dist. I kind of like that, but am also amenable to making that an option that can be passed to the builder.

I'd prefer if they were just output to dist directly. I feel like the "patterns" distinction is only relevant during development, it's not really super relevant to the end-user (someone viewing the library). But I agree this should be an option.

I still need to get a sense of how sandbox items differ from other pages. I'll get to that at some point!

I'm not sure they need to differ? As long as pages can define a new layout (or template) to use (one that's essentially "blank" with none of our style guide UI), that's all we'll need for sandbox.

I'm a call this done.


ICBM and CMG together for the same primary site?

Hello,
Can a single SCCM Site be configured for both - Internet-Based Client Management (IBCM) and also Cloud Management Gateway (CMG)?
Because we already have IBCM configured on our single primary site to manage only all servers in DMZ network.  All these servers do not have Internet connection (for security).  Now, to manage laptops that are on the Internet, we want to use CMG, so can we configure our primary site for CMG implementation?
Is this supported by Microsoft or can this be even implemented?
Your feedback will be valuable.
(admin edit: add metadata to link article)

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

ID: 0ef9884b-385c-a5c1-7449-43d3fff9d84d
Version Independent ID: 6b0135c4-bd5e-fa24-9528-8d24a4604f01
Content: Manage clients on the internet - Configuration Manager
Content Source: sccm/core/clients/manage/manage-clients-internet.md
Product: configuration-manager
Technology: configmgr-client
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @irfan-fakih for the feedback. I need to confirm with the engineering team.

If a device gets policy from the site for both IBCM and CMG, then it randomizes between them for communication.
If your DMZ clients can't access the CMG (no internet access) and the HTTPS MP in the DMZ isn't exposed to the internet (not really IBCM), then internet-based clients should only use the CMG.
I'll keep this issue open to include a note about this topic in this article. But I suggest you may also want to file product feedback as well.

Thank you Aaron Czechowski on following up on this issue.
Here are some observations based on my ConfigMgr CB 1810 version environment with 20,000 Windows workstations & 3000+ Windows Servers & 200+ servers in DMZ.
Your Response:  “If a device gets policy from the site for both IBCM and CMG, then it randomizes between them for communication.”
My feedback:  Correct, Within a single Site, I had seen this behavior on 200+ IBCM configured servers in our DMZ.
Your Response:  “If your DMZ clients can't access the CMG (no internet access) and the HTTPS MP in the DMZ isn't exposed to the internet (not really IBCM), then internet-based clients should only use the CMG.”
My feedback:  Correct, all our 2000+ Internet based laptops (running SCCM Clients) are using only CMG extensively and accordingly, we see all statistics on the CMG report (Good).  But, on the 200 servers in DMZ, we see random site-system names selection (IBCM or CMG, as you said).  So, for those Servers in DMZ (with no Internet connection) where it selects CMG, it is a big problem now because the SCCM Client on those DMZ servers goes dormant after a while (my observation), nothing happens on these servers.  For these specific DMZ servers, I can confirm this by periodically looking from Control Panel -> ConfigMgr applet, -> Network Tab, and I can see the CMG server FQDN name under IBCM MP field staying there forever.  Hence, going forward, any SCCM operations (patching, etc.) do not work on these DMZ servers.
Another thought:
In order to resolve this issue and in consideration of my ConfigMgr environment (which is currently just single primary site), I thought about creating a secondary site in DMZ based on HTTPS.  Then, I can install the SCCM client (as IBCM) on all 200+ DMZ Servers reporting to this newly created secondary site (with new sitecode).  While the primary site is still remains HTTP taking care of 20,000 Windows workstations & 3000+ Windows Servers.  And I will leave the existing CMG on the primary site for the laptops.
Will this work? Is IBCM configuration (not real IBCM) supported on secondary site?  Will this scenario be supported by Microsoft?
Your feedback/advice will be helpful.
Irfan.Fakih<EMAIL_ADDRESS>Mobile#: 1-908-295-8271.
From: Aaron Czechowski<EMAIL_ADDRESS>Sent: Tuesday, May 21, 2019 3:52 PM
To: MicrosoftDocs/SCCMdocs<EMAIL_ADDRESS>Cc: irfan-fakih<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/SCCMdocs] ICBM and CMG together for the same primary site? (#1541)
If a device gets policy from the site for both IBCM and CMG, then it randomizes between them for communication.
If your DMZ clients can't access the CMG (no internet access) and the HTTPS MP in the DMZ isn't exposed to the internet (not really IBCM), then internet-based clients should only use the CMG.
I'll keep this issue open to include a note about this topic in this article. But I suggest you may also want to file product feedbackhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fsccm%2Fcore%2Funderstand%2Ffind-help%23product-feedback&data=02|01||fcfba557862a4a48ee2408d6de25cda8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636940651269510251&sdata=yPUDj5D84%2FD1MsQe201neDAXspzk2pp3KoFPAt83ST0%3D&reserved=0 as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FSCCMdocs%2Fissues%2F1541%3Femail_source%3Dnotifications%26email_token%3DAMCLH3WZTJSPBLBATYOWJNDPWRHGLA5CNFSM4HM5QYH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV47VKI%23issuecomment-494533289&data=02|01||fcfba557862a4a48ee2408d6de25cda8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636940651269510251&sdata=%2BrCziGR%2Biw0Dg%2FN%2BDpIXSgIyMEro7xfPw3wDgjRFG%2Fo%3D&reserved=0, or mute the threadhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMCLH3QIH7HK4SFE474GNQLPWRHGLANCNFSM4HM5QYHQ&data=02|01||fcfba557862a4a48ee2408d6de25cda8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636940651269520260&sdata=MlMA8gBNXiOKEc450BAmLiChhnrY5J6eoocOstVnnmA%3D&reserved=0.

Thanks @irfan-fakih for the followup. Although it's quickly surpassed the scope of what we can provide here. As I previously mentioned, you could try filing product feedback to suggest a better way of handling this scenario built into the product.
As for the alternative process you propose, I suggest one of the following options to provide the best level of support for this:

Post on Configuration Manager forums. These are moderated by our community MVPs who are very experienced, knowledgeable, and helpful.
Use Microsoft Support to search for the issue, or open a case with professional support.
Contact your Microsoft Premier team, such as a Premier Field Engineer or Technical Account Manager.


Copyright violation

Hi @VladThodo
I found this app on the Google Play Store. This guy just took your source code, added some ads in it and put it on the Store, without warning this is free software...
By the way, all his apps are open source software he copied...
As you are the owner of the source code, feel free to open a request to google here to remove the false app from the Store, if it's your wish ;)
Don't forget to tell Google that:

The app is licensed under Apache v2 license and this guy is violating it;
He is falsely claiming he made the app;
Provide some screenshots of your own app.

Thanks for letting me know. I wasn't aware of that, and never had to face such an obvious copyright violation as this. I'm surely going to report him.
Also, thanks for your kind instructions, that's really helpful :-)
I'm glad to know I have people who are interested in my apps and are also ready to help.

No problem, you're welcome :)
Let me know if one day you find another copyright violation like this one, so that I can track the fake developer ;)

This fake dev is down now. Please let me know if you find any other new copy, so I can continue to track fake developers... Will close this issue for now, do not hesitate to reopen it ;)


foreign_key_violation doesn't catch a missing trip_id

Describe the bug
When testing a feed with GTFS-flex data where there is a missing trip_id in trip.txt(parent file) but being referenced in stop_times.txt, validator doesn't show a foreign_key_violation error.
Here is the report link:
https://gtfs-validator-results.mobilitydata.org/83a0d446-3a65-4258-92c1-22b61c5dd6fe/report.html
Steps/Code to Reproduce

Download the test feed provided below
Upload the feed to Canonical GTFS Schedule Validator

Expected Results
Validator shows a foreign_key_violation error that indicates trip_id=t_5298041_b_77503_tn_0 in stop_times.txt cannot be found in trips.txt.
Actual Results
Validator doesn't show the error
Screenshots
No response
Files used
on-demand_services_between_multiple_zones.zip
Validator version
5.0.1
Operating system
MacOS
Java version
No response
Additional notes
No response

I got too deep into analyzing the issue—it actually stems from a parsing error in the stop_times.txt file. Let's delve into how we can improve the presentation of this error for our end users.

3 of the Flex gtfs data sets got parsing issues listed here https://docs.google.com/document/d/1QABoIeOdR6lAB7A6_X6WIbZwC7EnAIZvm_hRNwNQeoI/edit#heading=h.xt9phhoxqouq
New issue created https://github.com/MobilityData/gtfs-validator/issues/1767

Closing this as the issue is not reproducible. I was able to observe the foreign key error notice for the specified example feed and trip ID.

Wondering if this works now because of other modifications we've made so Flex feeds are parseable. Regardless, glad to see this is corrected.


use filter in any field

Search value in any field of object as a string

seems that this PR is a pretty important "must-have" for this repo to actually be useful for others..

Hey @arturoblack changes looks fine but can't see the updated compiled JS files i.e. dist files . Please add those too.


Update Solaris SPARC compile options.

This solves part of https://github.com/knu/ruby-unf_ext/issues/32 based almost entirely on the solution that @MarkGibbons provided. Since SPARC is technically a 64bit operating system by default, this seems reasonable.
Signed-off-by: Scott Hain<EMAIL_ADDRESS>@markgibbons I am happy to add an Authored by or amend commits for full attribution if you'd prefer!

@scotthain, it's good as is. Thanks

Thanks!


Not dropping cards in battlefield

Hi,
I have setup everything, connection to adb, screenshot is also good, but the botis not taking card, it always says "please choose a card"
How to solve this ?
I also changed bluestacks screen resolution as in the setup tutorial.

Also, i don't have drawings, is it normal or you must activate or call smth ?

You should get screenshots in clashroyalebuildabot/screenshots  if you add the debug=True flag:
bot = CustomBot(card_names, debug=True)

They look like this by default:

What are your screenshots looking like? If it says "please choose a card" it's normally misclicking.
How did you install the library? At the moment the version of the code from pip is not up-to-date, so you might have better luck with git clone.


auth on @searchable

Issue #, if available:
re #1043
Description of changes:
added auth logic for @searchable
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2484 into master will increase coverage by 0.84%.
The diff coverage is 95%.

@@            Coverage Diff             @@
##           master    #2484      +/-   ##
==========================================
+ Coverage   65.27%   66.11%   +0.84%
==========================================
  Files         196      199       +3
  Lines        9655     9567      -88
  Branches     1964     1838     -126
==========================================
+ Hits         6302     6325      +23
+ Misses       3073     2965     -108
+ Partials      280      277       -3

Impacted Files
Coverage Δ

packages/graphql-auth-transformer/src/resources.ts
89.11% <100%> (+1.3%)
:arrow_up:

...aphql-auth-transformer/src/ModelAuthTransformer.ts
91.06% <94.44%> (+0.23%)
:arrow_up:

...y-graphql-types-generator/src/compiler/legacyIR.ts
96.77% <0%> (ø)
:arrow_up:

...ackages/amplify-appsync-simulator/src/utils/log.ts

...amplify-appsync-simulator/src/server/operations.ts

...tor/src/velocity/util/transform/dynamodb-filter.ts

...fy-appsync-simulator/src/data-loader/none/index.ts

...y-appsync-simulator/src/schema/directives/index.ts
0% <0%> (ø)

...y-appsync-simulator/src/velocity/util/map-utils.ts
0% <0%> (ø)

...sync-simulator/src/velocity/util/dynamodb-utils.ts
0% <0%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


Updating all icons to be compliant with FontAwesome 4.3.0

Many of the icons needed updating to be compliant with IPython's implementation of the FontAwesome 4.X.X series. Those that have not been updated simply show up as blank in the Notebook toolbar. I have gone through the code and updated all icons to the FA 4.3.0 series (the most recent), attempting to keep the graphical images as closely as intended by the original authors. This work done in response to Issue #187. I have verified that these icons work on a subset of all changes made.

Thank you, looks good to me.


feat(Data/Quot): add surjective_quotient_mk

add missing surjective_quotient_mk to mirror surjective_quotient_mk', Quotient.surjective_quotient_mk'', and surjective_quot_mk.

bors merge
Thanks!


Fix/200488 notification open

Description of Changes
Currently, whenever a push notification is opened in Android, a new task is created.
Updated the launch intent flags for push notifications.
Breaking Changes

For push opens don't set launch intent flags. Instead rely on the default launch mode

Release Checklist
Bump versions in:

[x] CHANGELOG.md
[x] pubspec.yaml
[x] example/pubspec.yaml
[x] ios/optimove_flutter.podspec
[x] ios/Classes/SwiftOptimoveFlutterPlugin.swift
[x] android/src/main/java/com/optimove/flutter/OptimoveInitProvider.java

Release:

[ ] Squash and merge to main
[ ] Delete branch once merged
[ ] Create tag from main matching chosen version
[ ] Fill out release notes
[ ] Run dart pub publish --dry-run to make sure there are no issues
[ ] Run dart pub publish

I would say its better to have the annotations yes. Added where you suggested


Possibility to pass headers to error responses

Hi,
First of all thanks for this package, it's been very useful so far.
I'm using it with Lumen and I am facing a minor issue at the moment, as it is currently not possible to pass headers to the various shortcut methods for returning errors (errorForbidden, errorNotFound, etc).
In my case, authentification is handled using JWT, and the token is refreshed on every request and the new token is returned along with the response using a middleware.
When raising exceptions tho, the returned responses don't get through the middleware and the Authorization header (the one carrying the token) is not set.
This is where I would need to set it manually but the shortcuts methods won't allow me to do so.
This my own specific use case of course, but I believe some others could exist and I don't see anything wrong in adding an argument to these methods' signatures, as such:
public function errorInternalError($message = 'Internal Error', $headers = [])
public function withError($message, $errorCode, $headers = [])
Especially as withArray already accepts an array of headers as its second argument.
What do you think?
Thanks!

@osteel I'm agree with that, but first i need to figure out if it's possible to make it work.
Related to this issue #17

Resolved in #24


ReDesign a new DB schema for scale

All the points are important for the new schema

[x]  create a Data_Record entire collection.

[x]  its subdocuments by RegID and its fields like vehicleID, vehicleNAME.

[x]  each vehicle has particular its own collection of records of sensor data may be.

[x]  each collection it will look like same as previously I design for collection -> document -> field.

[x]  And create a service module.

when the new vehicle adds through the dashboard the code will run like these.
1.  vehicle added into the DB as a document with their respective fields.
2.  if the vehicle added & then the dummy collection will be created through the script for no reason just the avoid complexity and inconsistency.

84f18ef4ec7580417aa3f9e9b8802e52e3d9d667 issue solved*


Spline interpolation + number/hue/alpha interpolation

For linear interpolation:

Bring back short vs. long hue interpolation
Check hue normalization throughout the hue() method

For spline interpolation:

Add closed version
How to spline-interpolate alpha?
How to spline-interpolate short vs long hue?

need to check that performance was not degraded with current developments...

Logged as known issues in the code.


Bidirectional RNNs

This is an implementation of bidirectional RNNs using the go_backwards suggestion from https://github.com/fchollet/keras/issues/418.

Added a go_backwards parameter to every RNN class, which is then passed to theano.scan

Added a layer called recurrent.Bidirectional, which is parameterized by an RNN class as well arguments to pass to that RNN class when creating forward and backward instances of it. One choice I'm not sure was the best: the output_dim of a Bidirectional layer is the sum of the output dims of the forward and backward models (and thus each model gets a hidden state of size output_dim // 2).

Added a unit test which trains a bidrectional LSTM on a trivial task (detecting whether a character is present or absent in a small set of sequences).

Changed the IMDB LSTM example to use a bidirectional LSTM

This is my first attempt at a contribution to Keras and I'm not sure if I implemented enough (or too many) of the methods needed to make a fully functioning Layer, any and all tips & feedback very welcome.

It works when the bidirectional layer is not the first layer, but breaks if it is.
It prompts "theano.compile.function_module.UnusedInputError: theano.function was asked to create a function computing outputs given certain inputs, but the provided input variable at index 0 is not part of the computational graph needed to compute the outputs: <TensorType(float64, 3D)>.
"
No clue where it went wrong for now.

I copied this bit blindly without really understanding how the first layer in the network plugs into the Theano compute graph:
       # create input tensor in case this is the first layer in a network
        self.input = T.tensor3()

I'm not sure what I should be doing here instead, any ideas @jedi00 or @fchollet?

@iskandr : There's no problem with this line. Keras will use the first layer's .input atrribute to figure out the input shape of the whole model.
BTW, did you try my example class inheritance code #418 ? It seems the same problem. I've checked the computation graph of each para of the model, they're all the same with the ones when LSTM is used instead. This is really gnawing.

Finally I captured the bug! The problem lies in the data input path of the the computational graph. When the bidirectional layer is the first layer of the whole model, the input of the underlying forward rnn & backward rnn are not connected properly.
I've submitted a new pull request #465 , resolved this problem.

Any idea how this behaves with masking? I don't fully understand the "go_backwards" flag of Theano, but its relationship with the mask seems dangerous.
My concern is, in every recurrent layer we generate a mask with this function: padded_mask = self.get_padded_shuffled_mask(train, X, pad=1). This prepends a pad to the beginning of the mask so that at each timestep of scan you can view the mask of the previous timestep.
It seems like with go_backwards=True you would want to instead append the pad (i.e. to the end of the array).

@wxs: According to theano documentation, when go_backwards = True, scan() will iterate with all input sequences in backwards direction. After discussing the padding mechansim with you, I just made modification to make the padding comply with the 'go_backwards' parameter @ #465 .
Sadly I still can't make the Bidirectional class work with other RNN class.  I built a model like:
model = Sequential()
model.add(Bidirectional(JZS1, 28, 28))
model.add(Dropout(0.1))
model.add(Dense(28, nb_classes, activation='softmax'))

however, error raised as
Traceback (most recent call last):
  File "C:\Python34\lib\site-packages\theano-0.7.0-py3.4.egg\theano\compile\function_module.py", line 594, in __call__
    outputs = self.fn()
ValueError: Input dimension mis-match. (input[0].shape[1] = 28, input[1].shape[1] = 14)

Any suggestion?

@jedi00 don't you need a TimeDistributedDense there?

@wxs: Bidirectional returns non-sequence, so a Dense layer is used. If there is no 'Dropout' layer, the model works fine; the error is raised only when another RNN layer is appended after `Bidirectional' layer.

@jedi00 @wxs @fchollet I haven't followed the past month of activity closely, do any of the recent PRs contain examples of layers which take other layers as arguments? I'm not sure what goes wrong with dropout following a Bidirectional but it might help to see an example of something that actually works.


Remove selected item and see the placeholder

How can I remove the selected item to see the placeholder?   Initially, I can see the placeholder, but after selecting an item there is no way to remove it. I can set the state to undefined but that does not affect the dropdown showing the selected item.

         import { SelectList } from 'react-native-dropdown-select-list';

         const [selectedItem,setSelectedItem]=useState<string|undefined>(undefined);

          <SelectList
            setSelected={(key: string) => setSelectedItem(key)}
            data={items.map((i) => ({ key: I,id, value: i.name }))}
            save='key'
            searchPlaceholder='Search items...'
            placeholder='Select an item'
            searchicon={<Icon name='magnify' size={25} />}
          />
         <Icon name='delete' size={25}  onPress={()=>setSelectedItem(undefined)}/>

I am using  "react-native-dropdown-select-list": "^2.0.5"
It is not a fully controlled component. So what would be the mechanism for removing the selected item?

   const [resetKey, setResetKey] = useState(0);
  const clearSelection = () => {
        setSelectedItem([]);
        setResetKey(resetKey + 1); // Change the reset key to force re-render
      };

     <MultipleSelectList
                   key={resetKey} //add this
                   defaultOption={{key: '', value: ''}} //add this

and for your button     =>  onPress={clearSelection}


Generating definition class which name is 'Option'

I have swagger docs which has some conflicting part:
"option": {
          "description": "Some options blabla",
          "type": "object",
          "properties": {
            "inventorySource": {bla bla}
           }
}

So by default generated case class for this object looks like this:
case class Option(...)
which obviously conflicts with scala Option which results for example with this error:
.myPackage.definitions.myRequest.Option does not take type parameters

Is it a way to generate definiton class with some prefix to avoid collision like this ?

hi @BBartosz, in my humble opinion, code-gen should be ignostice for any class defined inside user domain/package, just like compiler allowing user to define my.package.my.module.Option. In terms of naming-conflictions, may I suggest to either giving a more descriptive class name, or rename it as part of import, i.e. import myPackage.definitions.myRequest.{Option => GeneratedOption}
May I have your opinions on this?

Maybe I didnt specify the problem enough. So its not me who specify name of class thats the problem. Guardrail generates it based on name of field, so if the field is called unfortunately for me like scala reserved keywords we will have problems like this everytime. so given swagger documentation:
"option": {
          "description": "Some options blabla",
          "type": "object",
          "properties": {
            "inventorySource": {bla bla}
           }
}

generated class will look like:
case class Option(someField, someField)

Which results in conflict. And I cant change whole api contract of some api just because in some language there is naming conflict, it doesnt sound right, do you agree? So I dont understand a bit your solution with changing imports. Yeah I could even rename case class Option to be case class _Option but then should i rename it every time i recompile the project? Or I am missing something? I think generating tool should give me some flexibility how i want generated code to look like.

@BBartosz This may actually already be solved by #434! If you wouldn't mind running your spec via the CLI in that branch, I'd appreciate it. My goal is to review and merge that sometime this weekend.

im not sure those changes are gonna help, i think there are still some cases where FQNs are not used - but i def agree that it would be a good idea to do so and changes in #434 have most likely provided the tools to fix it in other places aswell

@tomasherman  @blast-hardcheese If those changes from #434 add package to class name that would solve my issue. How to publish guardrail locally so i can run it against my spec? I guess through sh cli.sh?

can you pls create a minimized offending swagger definition? that would make it easier for us to fix this ...

@tomasherman
{
  "swagger": "2.0",
  "info": {
    "title": "My API",
    "description": "my test api",
    "version": "v1"
  },
  "x-basePath": "{environment}:8080/test-api/{version}",
  "schemes": [
    "https"
  ],
  "consumes": [
    "application/json"
  ],
  "produces": [
    "application/json"
  ],
  "definitions": {
    "option": {
      "description": "some description",
      "properties": {
        "number": {
          "default": 1,
          "minimum": 1,
          "maximum": 8,
          "description": "Some Number",
          "example": 1,
          "type": "integer"
        }
      }
    },
    "response": {
      "description": "some description",
      "properties": {
        "number": {
          "default": 1,
          "minimum": 1,
          "maximum": 8,
          "description": "Some Number ",
          "example": 1,
          "type": "integer"
        }
      }
    }
  },
  "/search": {
    "post": {
      "operationId": "post_search",
      "responses": {
        "200": {
          "description": "some search response",
          "examples": {},
          "schema": {
            "$ref": "#/definitions/response"
          }
        }
      },
      "parameters": [
        {
          "schema": {
            "$ref": "#/definitions/option"
          },
          "in": "body",
          "name": "body",
          "description": "search request",
          "required": true
        }
      ]
    }
  }
}

Im surprised noboby encouner this problem before which makes me hope there is some obvious misusage of guardrail by me. So generated case class will be case class Option(something) so anywhere guardrail will generate code which returns or take as parameter SCALA Option[+A] from package scala we will have exception that option doesnt take parameters because in scope of generated code compiler will take first our generated case class with name Option instead scala.Option[+A]. Same will happen if you will name definition with any other keyword like list, exception, or literally any keyword from scala standard library. Example:
"definitions": {
    "list": {
      "description": "some description",
      "properties": {
        "number": {
          "default": 1,
          "minimum": 1,
          "maximum": 8,
          "description": "Some Number",
          "example": 1,
          "type": "integer"
        }
      }
    },

Simplest solution which will work for my case i see now is anywhere guardrail is generating scala Option as return type or input parameter, we need to add prefix with scala package before.
Example:
  object DoubleNumber     { def unapply(value: String): scala.Option[Double]     = Try(value.toDouble).toOption    }

Instead right now guardrail generates:
  object DoubleNumber     { def unapply(value: String): Option[Double]     = Try(value.toDouble).toOption    }

But adding scala. prefix to scala Option solves problem for my particular case, not for general case where you can define definition with some other reserved name in language(i.e. list). So general solution will be add possibility for user to define prefix to all names generated by guardrail. So I want to specify: add _ before any class you generate from my swagger docs. I cant check how to do it exactly now, I will be able to check that tomorrow.  But I have other question, @tomasherman do you understand the issue now and if your PR is solving that or your PR is not related? Im talking about #434

so i just tried it and it does NOT compile there is still a lot of work to be done if we want to support this -
i used following swagger:
swagger: '2.0'
info:
  title: Polymorphism nested example
  version: 1.0.0
produces:
  - application/json
paths:
  /foo:
    get:
      operationId: getPet
      responses:
        200:
          description: Return the details about the pet
          schema:
            $ref: '#/definitions/Option'
definitions:
  Option:
    properties:
      value:
        type: number

so basically to fix this we would need to prefix all Option and List etc with scala. ... do we want to go that way before i sink a lot of effort into that branch @blast-hardcheese to me it does make sense

(i only intend to implement this for circe as i do not care all that much for other platforms)

i tried to fix this but didn't make it - maybe i will get back to it but if someone else wants to continue, def go fo it

@tomasherman I'd need to check the OAI specification, but I wonder if something similar to mapping exists, otherwise x-jvm-class-name may be the cleanest option with the least changes required.
One annoying thing would be $refs, as currently we just assume the last chunk of the pointer is the class name.
This would be additionally beneficial, on the other hand, by enabling exhaustivity testing for unused models.
@BBartosz Would this workaround work for you?

(I'll also clarify, the reason I think vendor extensions are acceptable here is because guardrail is already in charge of extracting class names from specification files using some heuristics, so this would just influence the final outcome.
One additional point is that in untyped languages, there's no direct need to name these structures at all, beyond enforcing validation rules. I think that gives us many liberties to offer the best experience to the user, without complex language specific rewriting rules.)

isn't the solution much simpler than adding extensions? We simply need to qualify all names in the generated code (when generating DTOs)

anyway i would be really sad if this issue blocked #434 - just saying ;)

@tomasherman I'm looking for an escape hatch to handle all the cases that we haven't seen yet 😉
I've encountered specifications where operationId: test and the response entity is already called TestResponse, so when the code gets generated we end up with:
object TestResponse {
  case class OK(
    value: TestResponse
  ) extends TestResponse
}

#434 definitely resolves this, by turning it into
object TestResponse {
  case class OK(
    value: _root_.polymorphismNested.client.akkaHttp.definitions.TestResponse
  ) extends TestResponse
}

but I'm optimizing for the situation where if we find other situations similar to the Option case, a user could find the bug, open an issue, then use x-jvm-class-name: _Option to work around it immediately and keep rolling instead of being blocked.
That being said, x-jvm-class-name is equivalent to just renaming the definition in the specification, so they could just do that.
That being said, continually changing the names from one to the next would increase the search space for collisions for other languages that may be added in the future (for instance, "Gah, Option conflicts with Scala. renames to Optional Gah, that conflicts with Java. renames to Maybe Gah, that conflicts with Haskell)
All that being said, prefixing stdlib terms with their fully-qualified paths is probably a good idea. It just assumes that Library authors won't arbitrarily change the FQN for classes, like cats.FunctionK -> cats.arrow.FunctionK

Pardon the long response, but hopefully this clarifies my position around escape hatches and trying to keep folk moving forward instead of getting blocked until a bugfix can get released.

I def. appreciate long responses ;)
I actually thought about it a little bit harder and i think better approach is to avoid wild card imports of DTOs (or actually any imports of DTOs) and instead using fully qualified types where needed - but that's more work because i don't think guardrail is ready for that yet - i wasn't able to find an easy way to add information into appropriate classes

So, circling back to see whether this can be included with 0.54.3, https://github.com/twilio/guardrail/issues/438#issuecomment-551791591's

I think generating tool should give me some flexibility how i want generated code to look like.

is leaning me heavily towards x-${lang}-class-name.
Revisiting the specification posted earlier in this thread, the fact that the definition is named option doesn't in fact generate a conflict, see:
case class option(number: Option[BigInt] = None)

That being said, capitalizing that definition, it does in fact generate an unfortunate issue:
case class Option(number: Option[BigInt] = None)

I'm thinking that x-${lang}-class-name makes the most sense because:

It's very easy to do, and will root out the last few places where we just guess what the class name should be instead of having a direct path to the authoritative class name.
It mirrors x-${lang}-type in the sense that it permits overriding types to define additional language semantics (String @@ NonEmpty, or domain-specific classes that serialize to primitive types that match the wire protocol)
Carefully constraining the definition types as we've done recently goes a long way to reducing ambiguity, but we can see here that it still doesn't help in this case ("Option": { ... }) without threading through Predef, which then locks us in to particular versions of Scala, which I've tried very hard to prevent.
Permitting control of the generated class name instead of trying to do some heuristic matching and automatic adjusting puts control of name conflicts in the hands of the user, which matches the intent of other escape hatches (x-server-raw-response, x-${lang}-type, etc).
Alternate constructions of completely isolating all possible type conflicts, like a type function that takes all primitive types as arguments so we have complete control of catching all name conflicts would be extraordinarily cumbersome to use. There may be some useful research that can be done here more broadly, but for the time being I don't see the benefit of delaying until something may be found to solve this problem elegantly.

To summarize, I think we can't resolve this with package constraints alone, but that's OK. Does anyone want to take a shot at implementing x-${lang}-name?


Update windows.md file

I want to add some more shortcuts in this file.
I want to change the appearance of keyboard shortcuts(second image) as seen in first image

Thanks for your interest in our project. But we can't take this contribution acceptable for the hacktoberfest tag

@aryankashyap7, no i don't want to contribute under hacktoberfest tag. I just want to contribute in general.

Then I'm glad to assign you this task :)


Register 0.1.2

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/83529
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" e56eb4f9d3cbd14ce4ce55d91350c3e26bb6a652
git push origin v0.1.2


versions mismatch

Hi,
running the 4.7.1 from a tarball reports to be 4.4 because of https://github.com/keshavbhatt/whatsie/blob/e0d15c2ee0589f49cfef293606d69872d16b60f0/src/WhatsApp.pro#L51 and also version.txt reports to be 4.7.0:
https://github.com/keshavbhatt/whatsie/blob/9f566869d49578b12e445f8c275e7f8067daf5be/VERSION.txt
I gues that version(s) should be changed before the tag happens.

They will be aligned from now on. I have created a Release dry run action which will let me know the upcoming version based on semantic versioning convention. I have to run it to know the upcoming version and make update to project file to have the new version updated brefore drafting a new release.


Setting "python.analysis.nodeExecutable" requires a manual confirmation?

Is there any way to change this behavior?

With python.analysis.nodeExecutable overridden, our devs often get this prompt. It doesn't always appear, but it also doesn't only appear once. I've had to confirm multiple times. Is there any way to get this to auto-accept? If we're specifying the python.analysis.nodeExecutable value ourselves, I don't understand why users have to additionally manually confirm this with a click. I think this is a bad experience, since in our workspace, there are a bunch of other notifications that appear and this one can be easy to miss.

It should be a bug that you have to answer multiple times. The answer to this question is stored in a global memento on the user's machine (using this VS code API: https://code.visualstudio.com/api/references/vscode-api#Memento).
We ask though to ensure that you aren't running an executable that isn't protected.
Are you changing the path? The answer to the question is keyed off of the path. If there's no key, it would ask again.

I see. I found some other threads about the thinking behind the confirmation. I dislike that behavior, but it doesn't sound like there's any plan to change that. Although, I still think there should at least be a config to let us disable that explicitly.
I don't know what could be changing our path. Is that memento stored somewhere in .vscode-server? There's definitely a bug here, but it doesn't occur every time. Happens both on our remote machines and locally. I'll try to assess what might be triggering this to pop up again since I don't have a solid repro now.

It should pop up on every new machine (or remote machine). So if it popped up for you locally and then you connect to a remote, it would pop up again. The memento is stored on the machine AFAIK.
We were told to ask by the security team at Microsoft. It's a potential attack vector if you set this node executable to a path that's writable by multiple users. You might not be using the node you thought you were. It does seem like overkill to me too though. You explicitly typed it in as it can't be set in a workspace settings.json.

Big agree. Just to confirm, it does happen to me on the same machine, i.e. it happens to me locally multiple times without me consciously changing my path, and it happens on my remote machine multiple times. I believe there's a good chance that it's due to something I'm doing on my end unconsciously, like having to re-install the extension after removing the .vscode-server directory or something similar. Feel free to close this out, thank you for your insight!


Worked on some minor fix

Fixed SQL generation script running directory on Readme.md
SQL generation script will produces aliases for all variable.
Fixed the SQL model saving path from the generation script.

Mind pulling from the main and re-running the SQL generation please?
(Made the paths relative in https://github.com/onefact/synthetic-healthcare-data/commit/5868f8bc45a0a1dd048d7a0d495378154eef59db)
Otherwise LGTM! 🙌


feat(serde): add serde integration

This pull request is a prerequisite for the external crate containing ATC Router's WASM binding

Adding lib to crate-type to allow this crate to be used by other crates
Adding a serde feature to apply serde macros selectively
Adding a no-ffi feature to exclude ffi from mods to avoid symbol conflicts while being used as a dependency

KAG-2426

@dndx I have updated the branch with the suggestion. Thanks for pointing it out - I was not aware of the default features before.

@sumimakito Could you rebase this?


Porting codegen to use syntex_syntax (ie rustc's libsyntax)

I've been looking around for someting rusty and capnp-y to do to get to know both better. I saw that capnpc-rust is producing output by interpolating and concatenating strings. I also saw that syntex_syntax makes rustc's libsyntax available through cargo.
Any interest in this port?

Hi Kamal!
I suppose some benefits that libsyntax might provide are:

The ability to avoid an extra code generation step (I think this is what @cmr was hinting at in https://github.com/dwrensha/capnproto-rust/issues/11).
Extra static error checking.
Nice pretty printing.

Am I missing anything?
Cargo's support for code generation in build scripts lessens the weight of (1). The other benefits would be nice to have, but it seems like using libsyntax to achieve them would bring a significant cost in terms of verbosity.
It also appears that syntex has not been maintained for the past two months, so you'd first need to bring it up to date.
Perhaps I could interest you in taking on some other project relating to capnproto-rust? :)
Two things that would be really cool to support are generics and a dynamic API. I think that the key to implementing both of these features will be to port the schema and schema-loader implementations from capnproto-c++.
Another goal of mine is to eliminate our uses of unsafe in the capnp runtime library. Last I counted, there were something like 160 such uses. We should be able to get that down to zero without paying too much performance penalty.
Also, now that libgreen is dead, we need to figure out a better concurrency story for capnp-rpc-rust, possibly using mio.
Or, lest these biggish projects scare you away, you could get your feet wet by fixing a smallish bug such as https://github.com/dwrensha/capnproto-rust/issues/31. And that reminds that yet another fun project might be to try fuzz testing capnproto-rust with American Fuzzy Lop.

++features, ++security are definitely fine with me. I hadn't looked too much into the AST-generation code to decide if it had value; I just don't like mashing strings together. I'll take a look around!

Closing this since it sounds like you don't consider it terribly desirable. I 'd also prefer not to have to take on maintainership of another project to get this done.


⚠ Thumbnails API Endpoint has degraded performance

In 9761727, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 5662 ms

Resolved: Thumbnails API Endpoint performance has improved in 060aece after 35 minutes.


The examples folder is out of date

https://github.com/textileio/js-threads/tree/master/examples/chat
probably should be updated, moved + updated, or removed

Yes, I'd like to move it out of here, see https://github.com/textileio/js-examples/issues/7 over in js-examples.

Fixed with #159


feat(admin-ui): add invoice list page

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 40.59%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5987

Relevant Lines:
14750

💛  - Coveralls


UTP not affect by dhaste

core/dragonform.py : 121
    def charge_gauge(self, value, utp=False, dhaste=None):
        if dhaste is None:
            dhaste = not utp    # utp affected by dhaste too
        dh = self.adv.mod('dh') if dhaste else 1
        value = self.adv.sp_convert(dh, value)

need to mention that utp works as a float number in the game, so it's convinient for us to direct dh * value.

0905ea6cceba89cd4a1783589e592966093e56c7


Document fine grained access token permissions

Hi and thanks for this useful action. I just got it working and it does exactly what I wanted.
I did have a slight stumbling block though which is that I initially tried to use GitHub's new "fine grained" access token feature which allows limiting the access of the secret to a single repo:
https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/
With the fine grained token it seems that "workflow" scope is not enough and the workflow failed to push to a branch in the repo:
Create New Branch (refs/heads/main -> gh-actions-update-1677328662)
Commit Changes

  [gh-actions-update-167732[86](https://github.com/oscarbenjamin/protosym/actions/runs/4270016606/jobs/7433570757#step:4:95)62 ff18142] Update GitHub Action Versions
   4 files changed, 11 insertions(+), 11 deletions(-)

  Error: remote: Permission to oscarbenjamin/protosym.git denied to oscarbenjamin.
  fatal: unable to access 'https://github.com/oscarbenjamin/protosym/': The requested URL returned error: 403

https://github.com/oscarbenjamin/protosym/actions/runs/4270016606/jobs/7433570757
I was able to fix this by using a "classic" token with workflow scope. I would prefer to use a fine grained token but it is not clear what permissions I would need to give to that token when looking through the list of options.
There does not seem to be any mention of this in the README so I was wondering if you know what the scope for a fine grained token should be.

I would like to update the documentation with the new fine grained token's when I get some time. PR's are welcome. :)

Thanks for the update. I would have sent a PR if I had managed to figure out what permissions are needed!


[BUGFIX] scrolling to the selected item in bottom of the long-size list on first open

This pull request includes a

[x] Bug fix
[ ] New feature
[ ] Translation

The following changes were made

scrolling to the selected item in bottom of the long-size list on first open

If this is related to an existing ticket, include a link to it as well.
#4254 #4204 #3956
i can't scroll to the item in bottom of the list in 4.0.3
i fixed this bug related in #3956 (@zellerda comments)
i think it is correct. please comments. thank you

This was fixed in https://github.com/select2/select2/pull/4238.


Update Android F-Droid version to v1.12.0

F-Droid version is still on v1.11.1 but Google Play version is already up-to-date.

Please use the search next time. Duplicate of #838


Command '['postfix', 'start']' returned non-zero exit status 1

I've successfully used the mdomke/concourse-email-resource docker image in the past, but since yesterday when I set up a new concourse server, concourse is reporting a fatal error from the resource:
Using dir /tmp/build/put
Logging payload to /tmp/tmpxxlhbrfy
Command '['postfix', 'start']' returned non-zero exit status 1.

Here is my test pipeline:
$ cat email_test.yml
---
resource_types:
  # See https://github.com/mdomke/concourse-email-resource
  - name: email
    type: docker-image
    source:
      repository: mdomke/concourse-email-resource
resources:
  - name: send-email
    type: email
    source:
      from<EMAIL_ADDRESS>jobs:
- name: email-job
  plan:
  - put: send-email
    params:
      to:
        -<EMAIL_ADDRESS>      subject_text: Email from concourse
      body_text: Email body

Here's what I get when I run postfix start manually within the container:
fly -t test intercept sh -j email_test/email-job -b18
/tmp/build/put # cat /etc/issue
Welcome to Alpine Linux 3.4
Kernel \r on an \m (\l)

/tmp/build/put # postfix start
postfix: warning: smtputf8_enable is true, but EAI support is not compiled in
postsuper: warning: smtputf8_enable is true, but EAI support is not compiled in
postsuper: fatal: scan_dir_push: open directory defer: Permission denied
postfix/postlog: warning: smtputf8_enable is true, but EAI support is not compiled in
postfix/postfix-script: fatal: Postfix integrity check failed!

Any ideas about what might be going on here?

I was able to get things working by downgrading concourse to version 3.0.1, but I'm not sure what the root cause is. Based on the release notes for version 3.1.0, I thought maybe it had something to do with the privileged user changes in that release: https://concourse.ci/downloads.html#v3.1.0
However, adding privileged: true to my resource_type configuration didn't fix things for me when running 3.1.x

Hmm… We are running on concourse 3.3.2. I'm actually not seeing any error message on our site when sending e-mails but we also didn't receive mails for failing builds. I'll try to look into this…

Thanks for your response. I should add that concourse 3.3.2 also gives me this error.


Share dataset

Would you be so kind to share the downloaded datasets? S3  would be ideal, alternatively torrent?

I'd love to but I only downloaded the 15k Validation set fully, for the 3 million training set i only ran HEAD requests to check the links. If you find or have a share of the actual downloaded data somewhere i'll put a link up!

I crawled many of them, but it downloaded only 1% of the total, which seems a bit fishy to me, are all these links already offline? It's very sad that this dataset is not properly available, as the images obviously vanish over time.

That's very strange! Downloading only 1% is a bit too much decay - what did the final report look like in terms of errors and results? you can use https://github.com/igorbrigadir/DownloadConceptualCaptions/blob/master/downloaded_report.ipynb the same notebook to check

I managed to download more afterall, regarding sharing the dataset: I guess the problem is that it's too big. Someone would need to host it, which they can't do because of copy right. Do you have any idea for that?

My immediate idea would be to host a torrent for the data?
Either way - if you have time, i'd love to get a copy of the downloaded_report.ipynb notebook when it's run on the full dataset - to get the stats of deleted / existing files, sizes etc.


how to get auth token to test my custom apis(POSTMAN/ThunderClient/..) which i added for my new schemas ,

          ![Screenshot from 2024-12-08 11-14-07](https://github.com/user-attachments/assets/589339f2-29df-4dbf-82bd-53c0f9a4efd0)

Originally posted by @zlr-mounikagavara in https://github.com/boxyhq/saas-starter-kit/issues/1893#issuecomment-2525430223

You can create an API key once you log in, there is no auth token as such. But you are always free to extend the functionality to your liking.


Regarding Egc Dataset

Hi there!
The Egc dataset that you have provided seems to be different from other related datasets(For e.g. Egb,Ei,Xc etc.). The smiles in Egc dataset have these '[]'(square brackets) around * symbol but in other datasets the * symbol is not followed or preceded by these brackets. And one more thing the result you reported in the paper for Egc, is that using this same Egc dataset or one without square bracket around it? And if this is the case I was wondering why you guys have used square brackets particularly only for Egc datasets since the RoBERTa model is trained on PI1M dataset which does not contain square brackets around * symbol in smiles.

Hi, thanks for raising the issue. I checked the data file Egc.csv and there are no '[]' around '*'. If you mean the tokenization results, which is similar to your previous issue, I printed out the tokens and I do not see '[]' in the tokens either. Let me know if you still have any questions.

Okk, But earlier when I saw, am pretty sure that the square brackets were there.
I might have made mistake in seeing the data!!
Thanks


Update README.md

To use the latest commit SHA

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (eb238b5) 60.29% compared to head (c7b5834) 60.29%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #360   +/-   ##
=======================================
  Coverage   60.29%   60.29%
=======================================
  Files           3        3
  Lines         136      136
  Branches       32       32
=======================================
  Hits           82       82
  Misses         49       49
  Partials        5        5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add preference to hide card dialog when hovering cards in Deck Manager

This is an annoyance while building decks for those who don't need the card info. Please and thank you. :)

This is no more the case, I can close this one


feat(all): #1096 ssr

Changes
js-example-app SSR
To demonstrate lit's server side rendering capabilities the js-example-app package was converted to a NodeJs Koa application. This includes client side hydration. The ability to perform a static build has been removed. As such the render.com deployment configuration needs to be updated.
Transition to ESM
Library packages such as @boiler/ui-library and @boiler/icons have been transitioned to "ESM only" to reduce complexity and enable a unified development approach on client and server.
To be ESM compliant all import specifiers have to be explicit. As a result all implicit imports have been adapted.
For now all bundle steps have been removed. Bundlers can be re-introduced should the need for minified production bundles arise. We now rely on tsc only. This yields accurate type definitions, source maps and makes debugging much easier since we don't ship garbled js to our consuming packages.
lit upgrade to 3.x
The @lit-labs/ssr package requires version of<EMAIL_ADDRESS>So all our lit dependencies had to be upgraded.
Furthermore<EMAIL_ADDRESS>dropped support for legacy decorators. This necessitates the switch to the new accessor syntax for decorated class fields. (lit docs)

https://lit.dev/docs/components/decorators/#decorators-babel
Note: Lit decorators only work with "version": "2023-05". Other versions, including the formerly supported "2018-09", are not supported.

The above is relevant for Storybook, which uses babel internally to transpile TS source files.
@boiler/icons
The icon generation step for the @boiler/icons package has been changed to inline all SVG icons as strings into one JavaScript icon module instead of relying on webpack's raw-loader syntax. This enables the use of icons from vanilla ES modules without the need for a bundler on consumer side.
Optimized icons have been removed from source control and are now being generated during the compile step.

Closes #1096

Overall looks good. Just curious regarding the step that needs to be taken to resolve the current slow loading issue. Just a hint: The lit-labs/ssr states that "@lit-labs/ssr is pre-release software, not quite ready for public consumption", there might be potential breaking changes required later on if it released the stable version.

From my perspective it's still worth adopting the @lit-labs/ssr package now as it is the only way we can actually verify ssr capabilities with lit. SSR is still a common requirement for many projects. @thrbnhrtmnn, @ChristianHoffmannS2 and me had this discussion while you were on ADAC and we agreed to provide a test bed for further research and development. Imho not investigating ssr and later finding out aren't ssr compatible at all would be far worse than adapting to breaking changes.
Regarding the slow speed: Let's tackle this in a follow up issue. This PR is mainly aimed at providing a development foundation.

@angsherpa456

Overall looks good. Just curious regarding the step that needs to be taken to resolve the current slow loading issue. Just a hint: The lit-labs/ssr states that "@lit-labs/ssr is pre-release software, not quite ready for public consumption", there might be potential breaking changes required later on if it released the stable version.

From my perspective it's still worth adopting the @lit-labs/ssr package now as it is the only way we can actually verify ssr capabilities with lit. SSR is still a common requirement for many projects. @thrbnhrtmnn, @ChristianHoffmannS2 and me had this discussion while you were on ADAC and we agreed to provide a test bed for further research and development. Imho not investigating ssr and later finding out that our components aren't ssr compatible at all would be far worse than adapting to breaking changes.
Regarding the slow speed: Let's tackle this in a follow up issue. This PR is mainly aimed at providing a development foundation.

Thanks @faselbaum for the follow up task, I agree with everything you wrote. We should adopt the ssr package now and potentially adopt to breaking changes in the future rather than not verifying the ssr capabilities at all.


Support for libsodium >= 1.0.17 in Apache Tuweni

Tuweni (1.2.0) has support up to Libsodium 1.0.16. Libsodium has newer versions available - 1.0.17 and higher.
https://github.com/jedisct1/libsodium/blob/master/ChangeLog
It would be nice to have support for newer versions of Libsodium also.
Related discussion thread is here:
<EMAIL_ADDRESS>

We generate the sodium sources by applying this python script to the sodium header file:
https://gist.github.com/atoulme/d37e62545c68dcddd389f284f779311e

@r-peter do you want to take a look at the PR?

Thank you so much @atoulme for incorporating the changes very quickly. The changes look good to me. I am building my solution using the SNAPSHOT I have created from your feature branch.
I observed failure of 2 test cases on my Windows machine. I can open another issue to report it to the team as it is not related to the changes made in this branch.

Please do open another issue. I don’t have a Windows dev box but we can start testing with GitHub actions if that helps.

On Nov 12, 2020, at 17:01, r-peter<EMAIL_ADDRESS>wrote:

Thank you so much @atoulme for incorporating the changes very quickly. The changes look good to me. I am building my solution using the SNAPSHOT I have created from your feature branch.
I observed failure of 2 test cases on my Windows machine. I can open another issue to report it to the team as it is not related to the changes made in this branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

#167 fixes the Windows issue. Closing.


boto3 python version?

Hi
Any chances that there will be a boto3 python version?

I don't know of anything currently in the works, but there are a couple of Python transaction libraries out there. I haven't used either to know what they're like, but I found a couple here: http://dynamodb-mapper.readthedocs.io/en/latest/ and here: https://github.com/drblez/dynamodb-transaction-manager


deprecated timber/loader/paths in favor of timber/locations

fixes : https://github.com/timber/timber/issues/1837

Feedback welcome!

Will have more time this weekend to finish this up.

@jarednova figured out @expectedDeprecated
This PR should be ok now.

We’re waiting for @jarednova’s final approval for the changes he requested.


on-closed not fired when client closes connection

My context is that I'm trying to implement GraphQL subscriptions for Lacinia with aleph (with WS and SSE, but that's not relevant). A GraphQL subscription event might be for, say, my age changing. That happens once a year, so is rare. Ideally, if the client gets bored of waiting for that event they should be able to close the connection which should trigger the unsubscription of the event source.
Let's consider the following request handler:
(defn handler [req]
  (let [s (ms/stream)]

    (ms/on-closed s (fn [] (println "Stream closed, so I can unsubscribe!")))

    {:status 200
     :headers {"content-type" "text/event-stream"}
     :body s}))

When I connect using curl, I see an empty event-stream, the connection remains alive (as it should) but when a Ctrl-c I don't get the expected "Stream closed, so I can unsubscribe!" message.
Let's amend the handler by adding some events:
(defn handler [req]
  (let [s (ms/stream)]

    (ms/on-closed s (fn [] (println "Stream closed!")))

    (future
      (loop [n 1]
        (when (and (< n 100)
                   @(ms/put! s (str "data: " n "\r\n\r\n")))
          (Thread/sleep 100)
          (recur (inc n)))))

    {:status 200
     :headers {"content-type" "text/event-stream"}
     :body s}))

Now, if I connect with curl, I do see the println message. To understand why, look at aleph.http.server/ring-handler.
     :channel-inactive
      ([_ ctx]
        (when-let [s @stream]
          (s/close! s))
        (doseq [b @buffer]
          (netty/release b)))

When the client closes the channel we do indeed get the :channel-inactive event. However, the implementation then derefs the stream, which blocks until the next event (which in my contrived example might be a year away!). In the case I've got bored and closed the connection myself, the deref returns nil and so the (s/close! s) body isn't executed.
So I don't get any notification to unsubscribe my subscriber. Of course, I can wait (maybe a year) until the next event is generated and try to put! on the closed channel, and unsubscribing upon it returning false. I can also live with the assumption that GraphQL events will be produced fairly frequently, but it doesn't feel at all efficient/optimal.
Is there a better way of signalling the closing client connection rather than attempting to put! on the stream? It seems that given the fact that :channel-inactive is called by Netty to aleph, there should be a way of signalling 'user-space' code.

@ztellman I think it's safe now to close this issue 🤔


molsketch: 0.8.0 -> 0.8.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/molsketch/versions.
meta.description for molsketch is: 2D molecule editor
meta.homepage for molsketch is: https://sourceforge.net/projects/molsketch/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.1 with grep in /nix/store/35cbk1ksmmyricsx6vf0y8sgh378j6c0-molsketch-0.8.1
found 0.8.1 in filename of file in /nix/store/35cbk1ksmmyricsx6vf0y8sgh378j6c0-molsketch-0.8.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
molsketch

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/35cbk1ksmmyricsx6vf0y8sgh378j6c0-molsketch-0.8.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/02a5c5cd8fe02470048259411b5a4fb43c15b236#molsketch

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

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

1 package built:

molsketch

Maintainer pings
cc @moni-dz for testing.

@ofborg eval


numba Generator.uniform() doesn't work with array-like inputs

The docs for numpy.random.Generator().integers() reports

"(Both low and high are required arguments. Array values for low and high are currently not supported.)"

which leads me to believe that in general, array values for inputs in Generator methods are accepted. However, the following test fails to compile:
import numba as nb
import numpy as np
from numpy.random import default_rng

@nb.njit
def test(rng, low, high):
    return rng.uniform(low, high)

test(default_rng(0), np.array([0., 0., 10.]), np.array([1., 1., 11.]))

TypingError: Failed in nopython mode pipeline (step: nopython frontend)
- Resolution failure for literal arguments:
No implementation of function Function(<function NumPyRandomGeneratorType_uniform at 0x7f5d3642b740>) found for signature:

 >>> NumPyRandomGeneratorType_uniform(NumPyRandomGeneratorType, array(float64, 1d, C), array(float64, 1d, C))

There are 2 candidate implementations:
  - Of which 2 did not match due to:
  Overload in function 'NumPyRandomGeneratorType_uniform': File: numba/np/random/generator_methods.py: Line 371.
    With argument(s): '(NumPyRandomGeneratorType, array(float64, 1d, C), array(float64, 1d, C))':
   Rejected as the implementation raised a specific error:
     TypingError: Argument low is not one of the expected type(s): [<class 'numba.core.types.scalars.Float'>, <class 'numba.core.types.scalars.Integer'>, <class 'int'>, <class 'float'>]
  raised from [/home/ami/venvs/jax/lib/python3.11/site-packages/numba/np/random/generator_methods.py:81](https://file+.vscode-resource.vscode-cdn.net/home/ami/venvs/jax/lib/python3.11/site-packages/numba/np/random/generator_methods.py:81)

- Resolution failure for non-literal arguments:
None

During: resolving callee type: BoundFunction((<class 'numba.core.types.npytypes.NumPyRandomGeneratorType'>, 'uniform') for NumPyRandomGeneratorType)
During: typing of call at <ipython-input-29-cbf84c3815cc> (10)

File "<ipython-input-29-cbf84c3815cc>", line 10:
def test(rng, low, high):
    return rng.uniform(low, high)

Is this is a bug, or do the docs need to be updated? Are there any plans to support this functionality?

@amifalk thank you for asking about that. I had a look and the current Numba implementation and found the type checks here:
https://github.com/numba/numba/blob/main/numba/np/random/generator_methods.py#L374-L375
So, currently Arrays are not supported for low and high values.
Also, this issue looks related: https://github.com/numba/numba/issues/8770


test: add an option to run Testcafe test with chromium

Requirement: https://dev.azure.com/City-of-Helsinki/kultus/_git/kultus-pipelines/pullrequest/9959.
Add an option to run Testcafe browser tests with Chromium instead of Chrome. There have been some issues with the Chrome that prevents using it in CI environment:

https://github.com/DevExpress/testcafe/issues/8286
https://github.com/DevExpress/testcafe/issues/8300
https://github.com/DevExpress/testcafe/issues/8304
https://github.com/DevExpress/testcafe/issues/8307

kultus-ui branch is deployed to platta: https://kultus-ui-pr344.dev.hel.ninja :rocket::rocket::rocket:


Revert "Fix #778, add cfe assert and example lib"

Reverts nasa/cFE#779
Testing a revert to see if it will update the status on the original PR.

I'm curious if using the revert via the github GUI will update the status of the old PR from "merged".  Maybe try this out to reduce confusion?

Trying it out...


Feature/frontend

+include config.js to reduce hardcoding url in components
+react-native-dotenv to hide sensitive link

+README.MD instruction for frontend development + fix


add 1_simple test back

add what was missed in PR #1920

@cos please review. simple-untyped hasn't been tested yet. please merge asap.


Problem to work with arctech_switch_old

I have a problem to get code from rf remote. I got code when pressing button:
pulses: 50 possible protocol: arctech_switch_old
pulses: 50 possible protocol: arctech_switch_old
pulses: 50 possible protocol: arctech_switch_old
pulses: 50 possible protocol: arctech_switch_old

I tried to get code from another rf remote. These what I got:
pulses: 50 possible protocol: rev3_switch
RF signal arrived [rev3_switch]/[33] (0) {"id":33,"unit":13,"state":"on"} (1)
pulses: 50 possible protocol: ev1527
RF signal arrived [ev1527]/[] (0) {"unitcode":1031337,"state":"opened"} (1)
pulses: 50 possible protocol: rev3_switch
RF signal arrived [rev3_switch]/[33] (2) {"id":33,"unit":13,"state":"on"} (102)
pulses: 50 possible protocol: ev1527
RF signal arrived [ev1527]/[] (2) {"unitcode":1031337,"state":"opened"} (102)

And I got code from 433Mhz door sensor as these:
pulses: 50 possible protocol: rsl366
pulses: 50 possible protocol: arctech_switch_old
pulses: 50 possible protocol: rsl366
pulses: 50 possible protocol: arctech_switch_old

What should I do to get them work?
Thanks.

@ratawit sorry for the late reply, I totally missed this issue.
Are you sure that this is a arctech_switch_old remote?
The output only indicates the pulse behaviour is similar, but the missing RF signal arrived shows that it could not be encoded by this protocol module. The same is for your door sensor.
Probably, the protocols are not yet supported by pilight. Please have a look here, how to report new protocols.


Avatars not displaying on homepage

This is a new issue since the react update. Makes the homepage look rubbish.

cc/ @JedWatson @vitalbone @LennyBoyatzis

This has been semi-fixed. There are still attendees with missing avatars, however the proportion of avatars showing now is well in the majority. Will continue to explore until all avatars (or default image) are displaying.

On further inspection this looks like it has something to do with the social logins, facebook and twitter in particular. Keystone may not be recognising the image URLs for these users.


AsyncFunctionalComponent

What problem does this feature solve?
FunctionalComponent are useful for simple routes that simply do an operation e.g. load pinia  with random data then route.  However, it does not appear to work correctly when the functional component is async.

What does the proposed API look like?
export declare interface AsyncFunctionalComponent<P = {}, E extends EmitsOptions = {}> extends ComponentInternalOptions {
    (props: P, ctx: Omit<SetupContext<E>, 'expose'>): Promise<any>;
    props?: ComponentPropsOptions<P>;
    emits?: E | (keyof E)[];
    inheritAttrs?: boolean;
    displayName?: string;
    compatConfig?: CompatConfig;
}

Yes, functional components are pure, synchronous functions where props go in, and vnodes come out.
For what "simple operation" do you want to use a async functional component,? You haven't provided a use case for your feature request

My use case is to submit a form to the backend as part of vue router that would route to another page.  So I used ChatGPT to convert a template-less component
export default defineComponent({
  setup() {
    const router = useRouter();

    const {
      executeRecaptcha,
      recaptchaLoaded,
      instance: recaptchaInstance,
    } = useReCaptcha();

    const waitForRecaptcha = () => {
      return new Promise<void>(async (resolve, reject) => {
        const timeoutId = setTimeout(() => {
          reject(new Error("recaptchaLoaded() took longer than 5 seconds"));
        }, 5000);

        while (true) {
          const loaded = await recaptchaLoaded();
          if (loaded) {
            clearTimeout(timeoutId);
            resolve();
            break;
          }
          await new Promise((resolve) => setTimeout(resolve, 100));
        }
      });
    };

    onMounted(async () => {
      let recaptchaToken: string | null = null;
      try {
        if (recaptchaInstance) {
          await waitForRecaptcha();
          recaptchaToken = await executeRecaptcha("submitAssessment");
        }

        const userProfileStore = useUserProfileStore();
        if (recaptchaToken) {
          const assessmentPayload: AssessmentPayload = {
            assessment: userProfileStore.assessmentToSendToBackend,
            recaptchaToken,
          };
          if (userProfileStore.isRandomized) {
            console.info(
              "Assessment payload was not sent as it is randomized",
              assessmentPayload
            );
          } else {
            await submitAssessment(assessmentPayload);
          }
        }
      } catch (err: unknown) {
        console.error(err);
      }
      router.replace("/report");
    });

    return {};
  },
  render: () => null,
});

what I would rather have had was something like this (where I take out some of the boiler plate parts like onMounted, defineComponent etc.
const Submit = async ()=> {
    const router = useRouter();

    const {
      executeRecaptcha,
      recaptchaLoaded,
      instance: recaptchaInstance,
    } = useReCaptcha();

    const waitForRecaptcha = () => {
      return new Promise<void>(async (resolve, reject) => {
        const timeoutId = setTimeout(() => {
          reject(new Error("recaptchaLoaded() took longer than 5 seconds"));
        }, 5000);

        while (true) {
          const loaded = await recaptchaLoaded();
          if (loaded) {
            clearTimeout(timeoutId);
            resolve();
            break;
          }
          await new Promise((resolve) => setTimeout(resolve, 100));
        }
      });
    };

      let recaptchaToken: string | null = null;
      try {
        if (recaptchaInstance) {
          await waitForRecaptcha();
          recaptchaToken = await executeRecaptcha("submitAssessment");
        }

        const userProfileStore = useUserProfileStore();
        if (recaptchaToken) {
          const assessmentPayload: AssessmentPayload = {
            assessment: userProfileStore.assessmentToSendToBackend,
            recaptchaToken,
          };
          if (userProfileStore.isRandomized) {
            console.info(
              "Assessment payload was not sent as it is randomized",
              assessmentPayload
            );
          } else {
            await submitAssessment(assessmentPayload);
          }
        }
      } catch (err: unknown) {
        console.error(err);
      }
      router.replace("/report");
   };
Setup.props = []
Setup.emits = []
export default Setup;

That doesn't look like a component, it looks like a VueRouter Navigation Guard?

If it was a navigation guard then it will be triggered per entry of the /report which I want to avoid
I could make it a
{
  path: '/submit'
  beforeEnter: (...)
}

But that means my route configuration would be larger I'd rather simply put components to keep it consistent with the rest of the routes.
{
  path: '/submit'
  component: Submit
}


chore(deps): upgrade rollup and plugins

Related Ticket(s)
retrying this PR: #8707
Description
{{Add a human-readable description / detail summary of what the PR is changing and any details around how and why}}
{{If applicable, include a screenshot indicating an example or examples of what the PR is changing in the application}}
Changelog
New

{{new thing}}

Changed

{{changed thing}}

Removed

{{removed thing}}

closing for now


Broke RDS into multiple sections for each database

Broke RDS into multiple sections for each database and added
RDS-specific content for MySQL, Aurora, MariaDB, and SQL Server

LGTM! Great job, @danhermann!

Thanks for the feedback. I'll work on incorporating your suggestions and update the PR.

@danhermann  - if you resolve the merge conflicts, I think we're ready for a merge.

I think I may have messed up the resolution of the merge conflict on this PR. @jlevy or @ThanosBaskous, can you confirm? If so, I'll close this PR and open another one with the same content as this one.

I think you're right, @danhermann. Creating a new one should be fine.
Thanks for working through this!

Superseded by PR #251.


[BEAM-5367] Removed beam/website check from the Beam build dependency.

beam/website is currently broken and not actively maintained. However, it's test is included in Beam build and breaking nightly build. Removing it from Beam build until it is fixed.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---
---

Failure JIRA: https://issues.apache.org/jira/browse/BEAM-5367
Added a JIRA to enable it once stable: https://issues.apache.org/jira/browse/BEAM-5368

r: @Ardagan
cc: @lukecwik @swegner

r: @pabloem

Okay, this LGTM.


Add providers section in documentation and put current docs under it

Short description of the problem this fixes or functionality that this introduces. This may be used for the CHANGELOG
Add providers section in documentation and put current docs under it

Give a summary of what the PR does, explaining any non-trivial design decisions
This adds a Providers section under the LLMs which is more accurate

Link of any specific issues this addresses

This got stuck at build and publish app image for over 3 hours. Apparently it was waiting for https://playwright.azureedge.net/builds/chromium/1084/chromium-linux-arm64.zip
I restarted the job with debug enabled.

This got stuck at build and publish app image for over 3 hours. Apparently it was waiting for https://playwright.azureedge.net/builds/chromium/1084/chromium-linux-arm64.zip I restarted the job with debug enabled.

Thank you. Yes some jobs just get stuck sometimes. Haven't had time to investigate.


Merge master branch to prTesting1_202009271925 branch

Docs Build status updates of commit b5a4581:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit b5a4581:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestCon1.md
:warning:Warning

Details

split/updateTestCon1.md

Line 0: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 1: [Suggestion-h1-missing] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning around July 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel