circ_RNA to be added to non-coding class to align with INSDC

What is this request referring to?
Addition of circular RNA under both ncRNA and mRNA. This was recently discussed at INSDC and will be added as a valid INSDC value.
What is the name you would like SO to give the term?

For the non-coding RNA please add circular_ncRNA.

For the mRNA please add circular_mRNA

What is the definition that you would like for this term?

A non-coding RNA that is generated by backsplicing of exons or introns, resulting in a covalently closed loop without a 5’ cap or 3’ polyA tail.

An mRNA that is generated by backsplicing of exons or introns, resulting in a covalently closed loop without a 5’ cap or 3’ polyA tail.

Synonyms

INSDC_feature:ncRNA, INSDC_qualifier:circRNA

INSDC_feature:mRNA, INSDC_qualifier:circular_RNA

Parent Term

Please put this under ncRNA-gene (SO:0001263)

Please put this under mRNA (SO:0000234)

Relevant Publications
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5723916/

There is an existing ticket #391.
I think this should be circRNA, without the underscore, if matching the INSDC usage.
For its position in the hierarchy, I think it needs to be a child of both ncRNA and mRNA. Or we'll need two separate terms, for noncoding and coding circular RNAs. If going that route, the terms could be:

circular_ncRNA, with the synonyms INSDC_feature:ncRNA, INSDC_qualifier:circRNA
circular_mRNA, with the synonyms INSDC_feature:mRNA, INSDC_qualifier:circular_RNA

I'm basing those terms on others like "monocistronic_mRNA"
-Terence

Hi guys,
I apologize that I have not yet gotten to issue #391. I am trying to keep up with the current requests but work backwards on the old requests that were submitted before I joined the team.
I think you are right and these should be added to be consistent with other databases.
I like Terence's idea of making two terms. Do you think there should be a third term made that is simply "circRNA" that is a parent to both of the proposed terms? I am thinking this one would go under "transcript" (SO:0000673) and have the definition "Circular RNA in a covalently closed loop without a 5’ cap or 3’ polyA tail."
This would mean that circular_ncRNA is_a circRNA as well as is_a ncRNA-gene (SO:0001263). circular_mRNA would also have two parents, circRNA and mRNA (SO:0000234).
What do you guys think? Do you think it would be better with just the two terms, or is it most correct to add circRNA as well?
Thanks,
Dave

That would certainly be formally correct, although maybe it should go under "mature_transcript" (SO:0000233).
I don't really know what the pros and cons are, for this specifically and the general issue of adding complexity to the hierarchy. What comes to mind are:

If the extra term circular_RNA exists, is it likely to get used in a context where the user really should use the more specific term? If they do, it creates a problem of how to interpret the feature when you need the specificity. With a GenBank submission, circular_mRNA can be readily interpreted into INSDC terms, but circular_RNA can't without checking for presence/absence of a CDS.
Or to put it another way, is there a point to having a node that you really don't want anybody to use?
Does having multiple parents for a node in the hierarchy make it harder to compute on? For example, say I want to extract out all "transcript" types from a file, and furthermore simplify those types to just a subset by moving up the hierarchy. That poses a problem if there are multiple paths. I don't know if anyone does this -- I can think of places where it would be desirable to do so, but trying to come up with a simple rule to collapse say a rich set of 50 types down to a more tractable set of 5 without having to define everything individually isn't obvious.

I'm somewhat biased towards simpler-is-better, so if there isn't an immediate use case for the extra node I'm inclined to omit.

Hi Terrence,
It sounds like it will be both more consistent with INSDC and simpler if only the two terms are added. Below are my suggested changes to SO. Would you mind looking through these and giving and suggested changes before they are added? Especially look at the synonyms and make sure those are correct.
[Term]
id: New
name: circular_ncRNA
def: "A non-coding RNA that is   generated by backsplicing of exons or introns, resulting in a covalently closed loop without a 5’ cap or 3’ polyA tail." [PMID:29230098, PMID:   29626935, PMID: 29576969, PMID: 29086764, PMID: 29182528]
synonym: "circular ncRNA" EXACT   []
synonym: "noncoding circRNA"   EXACT []
synonym: "circRNA" BROAD []
synonym: "INSDC_feature:ncRNA"   EXACT []
synonym:   "INSDC_qualifier:circRNA" EXACT []
is_a: SO:0001263 ! ncRNA_gene

[Term]
id: New
name: circular_mRNA
def: "An mRNA that is generated by   backsplicing of exons or introns, resulting in a covalently closed loop without a 5’ cap or 3’ polyA tail." [PMID:29576969, PMID: 29086764, PMID: 29182528]
synonym: "circular mRNA" EXACT   []
synonym: "coding circRNA" EXACT   []
synonym: "INSDC_feature:mRNA"   EXACT []
synonym:   "INSDC_qualifier:circular_RNA" EXACT []
is_a: SO:0000234 ! mRNA
Thanks,
Dave Sant

Hi Dave,
For circular_ncRNA, it should be:
is_a: SO:0000655 ! ncRNA
Everything else looks good to me. Thanks!

Hi guys,
Thanks for responding and helping me update these. circular_ncRNA has been assigned ID SO:0002291 and circular_mRNA has been assigned ID SO:0002292. As usual, the SO Browser should be updated with these terms within about 24 hours.
Thanks,
Dave


Where to put the database?

I'm a new IOS programmer.
Can you tell me where to put the sqlite db in xcode project?

Right now it's opening (or creating if it doesn't exist) the database in the app sandbox documents directory. It sounds like you want to include a pre-made db in the app bundle then open it. Probably what it should do is check first in the documents directory for the filename given then, if it doesn't exist, check in the bundle and copy the file to documents directory before opening it if it finds it.

Thank you.

I just added code to do that. You should now be able to put the database in your bundle (don't forget to add it to "Copy Bundle Resources" in "Build Phases"). When you try and open the database it will first look in the documents directory, if it isn't in there then it will look in the the bundle directory.
If you've previously run the example it might have already created an empty db in the documents directory, so make sure you delete the app from the simulator before trying again.


Added documentation to transposition.rs

Screwed that up when I moved the test over =P

I keep forgetting to do a cargo fmt =P

I keep forgetting to do a cargo fmt

This should be configurable in your editor of preference, so that you format on save 👀 (some people don't like it, but I strongly recommend it)


docs(limits): add measurable application requirements

Description

This PR will add the following conditions as measurable targets by CARET.

The rclcpp library must be used.
The processes that act as ROS node.

Related links

Notes for reviewers

Pre-review checklist for the PR author

[x] I've confirmed the contribution guidelines.
[x] The PR is ready for review.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR has been reviewed.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

LGTM


Hiera does not merge correctly

I have a hiera file with the following data:
:hierarchy:
    - "%{::environment}"
    - webserver/hosts/foo.local
    - webserver/hosts/bar.local

And 2 yaml files with the following code:
nginx::nginx_vhosts:
  'foo.local:
    ensure: 'present'
    listen_port: '80'
    listen_ip: '*'
    index_files: ['index.php']
    www_root: "/var/www/foo.local"
    server_name: ['foo.local']
    use_default_location: false

and
nginx::nginx_vhosts:
  'bar.local:
    ensure: 'present'
    listen_port: '80'
    listen_ip: '*'
    index_files: ['index.php']
    www_root: "/var/www/bar.local"
    server_name: ['bar.local']
    use_default_location: false

the hiera command " hiera -c hiera.yaml -h nginx::nginx_vhosts"
gives me the correct result... a merge from the two vhosts and files
{"foo.local"=>
  {"ensure"=>"present",
   "listen_port"=>"80",
   "listen_ip"=>"*",
   "index_files"=>["index.php"],
   "www_root"=>"/var/www/foo.local",
   "server_name"=>["foo.local"],
   "use_default_location"=>false},
 "bar.local"=>
  {"ensure"=>"present",
   "listen_port"=>"80",
   "listen_ip"=>"*",
   "index_files"=>["index.php"],
   "www_root"=>"/var/www/bar.local",
   "server_name"=>["bar.local"],
   "use_default_location"=>false}}

But only the first vhost is installed on the system, the second is ignored. I used the multiple files with multiple hashs with other modules and this problem seems to be only with the nginx module.
Greetings Jan

What was the bug (link, etc?)
I am having the same issue and searching got me here.

I did experienced the same issue some time ago, it has became even more confusing when I started to fix "deprecation notice" about direct parameters assignment to class {"nginx":}. So I've done it with a following code in my "nginx_base" profile:
class site::profiles::nginx_base (
$nginx_vhosts    = hiera_hash('nginx::nginx_vhosts', {}),
$nginx_upstreams = hiera_hash('nginx::nginx_upstreams', {}),
$nginx_locations = hiera_hash('nginx::nginx_locations', {}),
$http_cfg_append = hiera_hash('nginx::config::http_cfg_append', {}),
) {
############### Some magic to autoconfigure collect::plugin::nginx ###############
$status_location = "${nginx_locations['stub_status']['location']}"
$status_vhost    = "${nginx_locations['stub_status']['vhost']}"
$status_hostname = "${nginx_vhosts[$status_vhost]['server_name'][0]}"
$status_port     = "${nginx_vhosts[$status_vhost]['listen_port']}"
$status_url      = "http://${status_hostname}:${status_port}${status_location}"
##################################################################################
class {'nginx::config':
http_cfg_append => $http_cfg_append,
# expand by parameters which require hash's deep merge
}
class {'nginx':
nginx_vhosts    => $nginx_vhosts,
nginx_upstreams => $nginx_upstreams,
nginx_locations => $nginx_locations,
# expand by parameters which require hash's deep merge
}
->
class { 'collectd::plugin::nginx':
url => "$status_url"
}
->
Class['site::profiles::nginx_base']
}
You can adjust hiera lookups as needed (for priority lookups). However, I'd like to hear some notes from maintainers whether I did it right or wrong.


⚠ Nebulance has degraded performance

In 596bd79, Nebulance ($NBL) experienced degraded performance:

HTTP code: 200
Response time: 1768 ms

Resolved: Nebulance performance has improved in 371a39b.


Set ec2_prefer_imdsv2: true by default

What does this PR do?
Set ec2_prefer_imdsv2: true by default, which means that Agent use IMDSv2 by default. When Agent fails to get a token by any reasons, Agent try to request to IMDSv1.
Motivation
FRAGENT-1317
Background
Upon AWS' Security Hub recommendations the client enabled IMDsV2 on their EC2 instances, but noticed that they could no longer collect default metadata using the Datadog Agent.
User Story
Have ec2_prefer_imdsv2 enabled by default rather than have the client do so manually.
Related internal FRs

FRAGENT-1029
FRAGENT-1321
FRAGENT-1520

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

1 ) Build the Agent.
vagrant@vagrant:~/go/src/github.com/DataDog/datadog-agent$ sudo bin/agent/agent version
Agent 7.42.0-rc.2 - Meta: git.2.f6066e9 - Commit: f6066e9e75 - Serialization version: v5.0.46 - Go version: go1.19.4

2 ) Prepare datadog.yaml.
3 ) Run commands to check a default value.
vagrant@vagrant:~/go/src/github.com/DataDog/datadog-agent$ echo 'api_key: <DD_API_KEY>' > datadog.yaml
vagrant@vagrant:~/go/src/github.com/DataDog/datadog-agent$ sudo bin/agent/agent run --cfgpath datadog.yaml  > /dev/null 2>&1
[1] 154004
vagrant@vagrant:~/go/src/github.com/DataDog/datadog-agent$ sudo bin/agent/agent config --cfgpath datadog.yaml | grep prefer
ec2_prefer_imdsv2: true

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

I will close this PR. This approach doesn't consider these points.

this path of code is critical in agent startup and holds up the initialization.
We use this logic in all agents, not just ones on AWS (since it tells us if the machine is onAWS or not).
On AWS, this path will not immediately return a 404 but will be black-holed and would get stuck
the startup would be delayed for a very large number of agents if imdsv2 is misconfigured or unreachable


Draft proposal on simplifying readmes

Working to standardise on a shorter readme for each client library. This proposal would result in more content being centralised to the Java wiki, or linked out to docs.microsoft.com instead. For reference, this is the original document

Another concern - I'm a bit worried about the readmes being 'incomplete'. We publish them to github.io and would like to publish them to docs.microsoft.com. Ideally they offer a complete, if simplified, story.

There was no additional feedback on this draft PR. I'd really appreciate any thoughts from the people who were previously pinged: @willmtemple @annelo-msft @mayurid @schaabs @kaerm (I've now added you all as reviewers)
I'd really like to roll a simplification out across all Java client libraries, as I think it is a step in the right direction to make our libraries easier to get started with.

@JonathanGiles I generally like the idea of making the READMEs shorter and less to maintain. One thing that I get a little concerned about though, as Maggie alluded to above, is all the places other than GitHub where these README files are rendered. In JS, our README becomes our NPM page, and a lot of JS developers are pretty used to the NPM page being some of the only documentation that exists for a lot of libraries. I think it's very valuable for us to have code snippets there, for example. Like I personally really expect to see examples there.
I do think that it's pretty onerous to maintain so many copies of the same information about logging and AAD and how to create resources in Azure. I'd like to think about how we make these simpler to maintain but while keeping them useful for our customers. Like I imagine someone landing on one of our READMEs anywhere on the web and being just a couple of clicks from trying a sample on a free subscription.


Implement Path and Slot

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:

1.0.0
GitHub release

Your semantic-release bot :package::rocket:


[SPARK-29963][SQL][TESTS] Check formatting timestamps up to microsecond precision by JSON/CSV datasource

What changes were proposed in this pull request?
In the PR, I propose to add tests from the commit https://github.com/apache/spark/commit/47cb1f359af62383e24198dbbaa0b4503348cd04 for Spark 2.4 that check formatting of timestamp strings for various seconds fractions.
Why are the changes needed?
To make sure that current behavior is the same as in Spark 2.4
Does this PR introduce any user-facing change?
No
How was this patch tested?
By running CSVSuite, JsonFunctionsSuite and TimestampFormatterSuite.

Test build #114116 has started for PR 26601 at commit 72495e1.

Merged build finished. Test PASSed.

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

Test build #114116 has finished for PR 26601 at commit 72495e1.

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

Merged build finished. Test PASSed.

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

Merged to master.


License for code

Which license is this code under?  Asking because I may want to try to build something using what you've done here as a base.

I want it to have the most liberal license possible, do you have any suggestions? Otherwise I will most likely fall back to dual-license MIT or Apache, which is usual for Rust projects.

The license is here, thanks!


Added support for passing Range as a parameter to .Exclude.

TL;DR
This PR resolves #10 by adding support for passing Range as a parameter to .Exclude:
var samples = Enumerable.Range(1, 100).Exclude(6..94);
foreach (var sample in samples)
    Console.WriteLine(sample);

The expected output for the above snippet is 1 - 5 followed by 95 - 100 with each value on its own line.
Format Adjustment
The existing ternary expressions for the Count properties did not match what was present in other methods in the file. As the other formats are generally cleaner I updated the Count properties to break nesting out:
var sample = foo.Bar
    ? foo.Bar
    : foo.Bar < 5
        ? foo.Fizz
        : foo.Buzz;

Improved Documentation
Methods with access levels of protected or higher should have some form of documentation, even if their containing models are private, simply for consumer understanding. As such, I added documentation to the Count properties, and specified that documentation should be inherited from IEnumerable<T> where applicable.
##Constructor Visibility
I marked the constructors for the private types as internal since by definition they'll never be consumed outside of the assembly.

One thing I note in all three implementations is that they assume that !range.Start.IsFromStart and !range.End.IsFromStart.

Still looking into this, just haven't had much time this week yet.

I still need to add perf improvements and test coverage.

I will have some time this weekend to work on this assuming I'm not still sick. I appreciate your patience with me and your assistance on it!


java.lang.IllegalArgumentException when POSTing Composition

Hello team,
I am new to EHRbase having only used it this week.
With the help of Sidharth Ramesh's excellent YouTube video I've been exploring how to save a small patient observation for Blood Pressure to EHRbase.
I've created a little template and have been trying to POST the composition.
Steps I have followed:

Successfully created a new Composition Template (petetest.opt) using Archetype Designer with Encounter as the root, and BloodPressure archetype (see image below)

Successfully POSTED petetest.opt to EHRBase
POST http://localhost:8080/ehrbase/rest/openehr/v1/definition/template/adl1.4

Successfully created a new EHR record. I think this is required to obtain the patient UUID (?)
POST http://localhost:8080/ehrbase/rest/openehr/v1/ehr/{% uuid 'v4' %}

Used the Cabolabs toolkit to generate a Document instance from petetest.opt. Document is called petetest_000001_1.xml

Tried to POST petetest_000001_1.xml to EHR Base which generates the following error:
POST http://localhost:8080/ehrbase/rest/openehr/v1/ehr/5a5e2244-d4bb-4a31-a8cc-f8a02e2e45fc/composition. (UUID generated from step 3 above)

{
"error": "java.lang.IllegalArgumentException",
"status": "Bad Request"
}
There is nothing displayed on the EHRBase logs for this error.
I have tried removing some of the Composition entities which results in 'missing mandatory attributes' error, so I think the document is being validated.
EHRBase version : v0.16.5 (using the Docker images)
Any help on resolving this issue would be gratefully received :-)
Thanks so much,
Pete
petetest.opt.txt
petetest_000001_1.xml.txt

Hey @wood-pete. We'll have to ask @ppazos for this since the XML composition is being generated by his code.
I don't use Canonical XML that much and I can't figure out what's wrong there.
I do use the FLAT format a lot, for which I have a working example. I have removed the 24 hr average node since DV_DURATION (which is mandatory) is not yet supported by Medblocks UI:
{
    "petetest/category|code": "433",
    "petetest/category|value": "event",
    "petetest/category|terminology": "openehr",
    "petetest/context/start_time": "2021-09-10T13:30:16.590Z",
    "petetest/context/setting|code": "238",
    "petetest/context/setting|value": "other care",
    "petetest/context/setting|terminology": "openehr",
    "petetest/blood_pressure/any_event:0/systolic|unit": "mm[Hg]",
    "petetest/blood_pressure/any_event:0/systolic|magnitude": 120,
    "petetest/blood_pressure/any_event:0/diastolic|unit": "mm[Hg]",
    "petetest/blood_pressure/any_event:0/diastolic|magnitude": 80,
    "petetest/blood_pressure/any_event:0/time": "2021-09-10T13:30:16.590Z",
    "petetest/blood_pressure/language|code": "en",
    "petetest/blood_pressure/language|terminology": "ISO_639-1",
    "petetest/blood_pressure/encoding|code": "UTF-8",
    "petetest/blood_pressure/encoding|terminology": "IANA_character-sets",
    "petetest/composer|name": "Medblocks UI",
    "petetest/language|code": "en",
    "petetest/language|terminology": "ISO_639-1",
    "petetest/territory|code": "IN",
    "petetest/territory|terminology": "ISO_3166-1"
}

The above was generated from the browser directly using Medblocks UI. You can also find the code for the form here. There is also a live deploy of your form and it logs to the console. I'll release a video about this soon 😉.
Here is another more complete composition that was generated by the example endpoint of Better CDR:
{
  "petetest/_link:0|meaning": "Follow up to",
  "petetest/_link:0|type": "Problem",
  "petetest/_link:0|target": "ehr://4b15d43f-d399-470c-b414-691161589d2a",
  "petetest/_uid": "5cbb2bea-2ef8-439d-a3bf-93cdaca144dc::example::1",
  "petetest/context/start_time": "2021-09-10T11:34:15.523Z",
  "petetest/context/setting|code": "238",
  "petetest/context/setting|value": "other care",
  "petetest/context/setting|terminology": "openehr",
  "petetest/blood_pressure/_uid": "d02fa600-6822-48fe-92b5-6c62d98d555d",
  "petetest/blood_pressure/_other_participation:0|function": "performer",
  "petetest/blood_pressure/_other_participation:0|mode": "not specified",
  "petetest/blood_pressure/_other_participation:0|name": "Nurse Bailey",
  "petetest/blood_pressure/_other_participation:1|function": "requester",
  "petetest/blood_pressure/_other_participation:1|mode": "not specified",
  "petetest/blood_pressure/_other_participation:1|name": "Dr. Stiles",
  "petetest/blood_pressure/any_event:0/systolic|magnitude": 624.0,
  "petetest/blood_pressure/any_event:0/systolic|unit": "mm[Hg]",
  "petetest/blood_pressure/any_event:0/diastolic|magnitude": 781.0,
  "petetest/blood_pressure/any_event:0/diastolic|unit": "mm[Hg]",
  "petetest/blood_pressure/any_event:0/time": "2021-09-10T11:34:15.525Z",
  "petetest/blood_pressure/a24_hour_average/math_function|code": "146",
  "petetest/blood_pressure/a24_hour_average/math_function|value": "mean",
  "petetest/blood_pressure/a24_hour_average/math_function|terminology": "openehr",
  "petetest/blood_pressure/a24_hour_average/width": "P3DT3H51M",
  "petetest/blood_pressure/a24_hour_average/time": "2021-09-10T11:34:15.525Z",
  "petetest/blood_pressure/language|code": "en",
  "petetest/blood_pressure/language|terminology": "ISO_639-1",
  "petetest/blood_pressure/encoding|code": "UTF-8",
  "petetest/blood_pressure/encoding|terminology": "IANA_character-sets",
  "petetest/category|code": "433",
  "petetest/category|value": "event",
  "petetest/category|terminology": "openehr",
  "petetest/language|code": "en",
  "petetest/language|terminology": "ISO_639-1",
  "petetest/territory|code": "US",
  "petetest/territory|terminology": "ISO_3166-1"
}

I think you'll need to add the composer for it to work with EHRbase:
"petetest/composer" : "Your name"

The openEHR-OPT library has been updated with fixes to the generators (CLI). The toolkit will be updated soon.


Change logic for detecting page/post file type

I was playing with a generator
and found that page['name'] is handled a bit differently when they're called. In the
example (and others I've seen) @name is set to the output file name. Usually index.html.
However, the input file is not a .html file. I noticed that page['ext'] still shows the correct
file type for the input even with @name being explicitly set.
The current logic of checking page['name'] then falling back to page['ext']
is causing j-p-t to mis-detect markdown files when going through a generator.
I changed this to try page['ext'] first and then fallback to page['name'].
What I've found is:

A page has page['name'] and no page['ext']
A post has page['ext'] and no page['name']
A post going through a generator has page['ext'] and page['name']
but page['name'] is the generator's output file name not the input file.

Here's the test case I worked up. I think it has full coverage of different ways
content could be fed to j-p-t and similar plugins.
jekyll new myblog4
cd myblog4
mkdir images
mkdir _data
mkdir _layouts
mkdir _plugins
cp ~/s.png images/

Gemfile
source "https://rubygems.org"
gem "jekyll", "~> 3.8.5"
gem "minima", "~> 2.0"
group :jekyll_plugins do
  # My local checkout.
  gem 'jekyll-picture-tag', :path => './vendor/jekyll-picture-tag'
end
gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw, :jruby]
gem "wdm", "~> 0.1.0" if Gem.win_platform?

_config.yml
title: Your awesome title
email<EMAIL_ADDRESS>description: >- # this means to ignore newlines until "baseurl:"
  Write an awesome description for your new site here. You can edit this
  line in _config.yml. It will appear in your document head meta (for
  Google search results) and in your feed.xml site description.
baseurl: "" # the subpath of your site, e.g. /blog
url: "" # the base hostname & protocol for your site, e.g. http://example.com
twitter_username: jekyllrb
github_username:  jekyll
markdown: kramdown
theme: minima
plugins:
  - jekyll-picture-tag
picture:
  source: "images"
  output: "images/generated"

_data/picture.yml
markup_presets:
  default:
    markup: data_picture
    formats: [webp, original]
    noscript: true

_layouts/gens.html
---
layout: gens
---
<!doctype html>
<html>
    <body>
        <div>
            {{ content | markdownify }}
        </div>
    </body>
</html>

_plugins/gens.rb
  class GensPage < Page
    def initialize(site, base, dir, post)
      @site = site
      @base = base
      @dir = dir
      @name = 'index.html'

      self.process(@name)
      self.read_yaml(File.join(base, '_layouts'), 'gens.html')

      self.content = post.content
      self.data['body'] = (Liquid::Template.parse post.content).render site.site_payload

      self.data = post.data.merge(self.data)
    end
  end

  class GensPageGenerator < Generator
    priority :low
    safe true

    def generate(site)
        dir = 'gens'
        site.posts.docs.each do |post|
          site.pages << GensPage.new(site, site.source, File.join(dir, post.id), post)
        end
    end
  end
end

_posts/2019-02-09-html-post.html
{% picture s.png %}

_posts/2019-02-09-welcome-to-jekyll.markdown
---
layout: post
title:  "Welcome to Jekyll!"
date:   2019-02-09 12:01:30 -0500
categories: jekyll update
---

[{% picture s.png %}](/images/s.png)

about.md
---
layout: page
title: About
permalink: /about/
---
[{% picture s.png %}](/images/s.png)

I put these lines in the markdown_page? function in "lib/jekyll-picture-tag/utils.rb"
to output what I described above with page['name'] and page['ext']
puts "p_url:  #{PictureTag.page['url']}"
puts "p_name: #{PictureTag.page['name']}"
puts "p_ext:  #{PictureTag.page['ext']}"

When I build I get this output:
$ jekyll serve
Configuration file: /Users/john/Tmp/myblog4/_config.yml
            Source: /Users/john/Tmp/myblog4
       Destination: /Users/john/Tmp/myblog4/_site
 Incremental build: disabled. Enable with --incremental
      Generating...

 Auto-regeneration: enabled for '/Users/john/Tmp/myblog4'
    Server address: http://<IP_ADDRESS>:4000/
  Server running... press ctrl-c to stop.

Outstanding work! Thank you. It makes much more sense-- if Jekyll gives us a file extension we should use it before we go looking for it on our own.


Update update-api-object-kubectl-patch.md

in here should use --type=strategic, or remove it. otherwise, it will raise an error message
➜ k patch deploy retainkeys-demo --patch-file=./patch2.yaml --type=merge
The Deployment "retainkeys-demo" is invalid: spec.strategy.rollingUpdate: Forbidden: may not be specified when strategy `type` is 'Recreate'

the below information is the test environment
➜ k version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.5", GitCommit:"c285e781331a3785a7f436042c65c5641ce8a9e9", GitTreeState:"clean", BuildDate:"2022-03-16T15:51:05Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.10", GitCommit:"a7a32748b5c60445c4c7ee904caf01b91f2dbb71", GitTreeState:"clean", BuildDate:"2022-02-16T11:18:16Z", GoVersion:"go1.16.14", Compiler:"gc", Platform:"linux/amd64"}

I think PR #35230 do the fix here, please take a look.

#35230

yes, these two PRs all tried to fix the same issue. however, the default behaviour is strategic. so I hope it can be removed but not add --type=strategic.


Benchmarking

Separation of Build & Execution in Compiled Languages
Benchmarking
I'm not sure if it would be trivial or not to consider adding an API flag to separate out the build and execution steps for compiled languages (let's take Go).
As part of the code playground I'm building with Piston at the back, I would like to support running benchmarking methods in multiple languages. So for this, you would want to compile the Go code once, and then run it many times.
I think the biggest issue to this would be avoidance of server side state, you wouldn't want to turn this into two requests (and require the server to remember the compile code, a no-go), and you definitely don't want to send the compiled program back to the client.
I'm just winging it as I type this. Possibly the only way to do this well without introducing state is to create a benchmark API, which can be supported on a per-language basis by adding to the language defs (maybe this isn't even necessary), and then common params like max runtime, samples, etc.
If you guys @realtux, @HexF are up to it, I wouldn't mind diving in and doing the work on this. I recently did a number to benchmark JS in a browser service worker, so I've done a lot of research on good practices for benchmarking. It would be a standalone feature, basically a third API call to add to the existing two.
What do you think?

my first thought would be that this is outside of the scope of what piston is trying to accomplish. another challenge here is that piston has necessary overhead which is the trade for execution safety. using piston to benchmark wouldn't be a very accurate measurement of anything. i'm willing to hear more but i'm not sold on this at first glance.

Understood, but let me play with it a bit and maybe I can make a small, elegant solution. There's ways to mitigate the overhead (like process creation), such as running benchmarks on an empty process and subtracting the overhead. You're right, maybe it won't tell us anything, but it would be nice if it also offered benchmarking with no additional work for all languages!

Parking this for now, may have found another solution earlier on the pipeline than Piston. 👍🏻


Eloquent mixin

Option to add @mixin \Eloquent to model doc block if the model extends from Illuminate\Database\Eloquent\Model.

@barryvdh Any thoughts on this one?
Cheers.

Hmm, I'm not 100% sure about this. It will probably solve a few cases, but not all, right? Why not just extend the facade instead?

Mostly on the grounds that the current documentation always extends the Model (http://laravel.com/docs/5.0/eloquent) which leads me to believe that most people will extend the base class rather than the facade.
Additionally, if you're extending a third party class that extends Model rather than the facade you don't have much choice.
I've been using the mixin for a while with a fair amount of success - my only complaint is that the type hinting on some of the builder methods is a bit annoying as it never type hints static return types for methods like Eloquent::findOrFail() and firstOrFail(). That being said, at least they hint now..
Without putting in special exceptions this is maybe the best we can do.
Anyway, curious to hear your thoughts on potential issues - you've been doing this laravel thing for a while longer than me :)

It should extend both the Eloquent Builder and the Query Builder, right?
The problem I had with it, was that it flagged some errors/warning, because it was behaving as if it was extending the class. Can't exactly remember what.
But if it is an option I guess it wouldn't hurt.

Not sure on extending the QueryBuilder - the methods in there start to get pretty low level - happy to take your thoughts on this.
On a slightly unrelated note and out of curiosity - do you have any idea why some of the query builder methods in Laravel hint Collection|static[] or Model|static and others omit static.
e.g. findOrFail
@return \Illuminate\Database\Eloquent\Model|\Illuminate\Database\Eloquent\Collection
Surely this should be:
@return \Illuminate\Database\Eloquent\Model|\Illuminate\Database\Eloquent\Collection|static|static[]
If not I might go through at some point and submit a pull request.

Hi. What about findOrFail
Autocomplete does not work for findOrFail (laravel 5)

What's the status on this? It'd be helpful for me because I have a preference for staying with the default and just extending Model instead of eloquent.
I would however suggest that the config option is disabled by default, so it won't affect anyone that this won't be useful for.

+1 for this.

+1 is there a update for this one? :)

@barryvdh - any chance this will be merged in at some point?

+1

+1 — this is a good thing.

:+1: please :)

If we're going to use mixin, why not use the actual classes, instead of the facade?

Not sure to get what you said. Can you explain it to me plz ?

Yeah fair enough - I'll sort out next week
On Sun, 27 Dec 2015 at 3:11 AM, Barry vd. Heuvel<EMAIL_ADDRESS>wrote:

If we're going to use mixin, why not use the actual classes, instead of
the facade?
—
Reply to this email directly or view it on GitHub
https://github.com/barryvdh/laravel-ide-helper/pull/192#issuecomment-167346774
.

Fixed with https://github.com/barryvdh/laravel-ide-helper/commit/c213be3d3ca95a788aa4f1d9ddf72d4f31700594


AzureBlob::Client raises error about missing secret_key/principal_id on application load

AzureBlob::Client checks that at least one of secret_key and principal_id are present upon instantiation. While this is a useful check, it also means that every environment that loads the app must set such values, even if Azure Storage is not created. For example, build tasks (e.g. precompiling assets) or rake tasks need to set a (possibly fake) value of secret_key or principal_id in order to avoid the error, even though they do not need to make calls to Azure Storage. This is especially a problem for applications that inject such credentials as environment variables, because currently one needs to set such variables even when not strictly needed.
One way to fix this would be to delay the check for secret_key and principal_id to the first actual API call. This is the approach followed in https://github.com/testdouble/azure-blob/pull/7
P.S.: thanks for this library, it's great to see a high quality open-souce effort to replace the deprecated Azure library, and that the implementation is trying to avoid pitfalls of the previous solution (e.g. dependencies on HTTP libraries)

Fixed by #7


Added tests to verify DRILL-4474

Hi Rahul,
I have added tests to verify DRILL-4474, please verify. These are aggregate count queries with use of distinct within count aggregate function. I have a clean pre-commit test run will share details in email.
Thanks,
Khurram

Khurram,
The tests look good. You can go ahead and merge them. Since this is a very bad bug, a few more scenarios might be worth testing

Test this functionality on top of a view (created using '*' and another view created using explicit columns). You can play with a few combinations here.
Also do you think that we should add atleast one sanity test with hive, hbase, & csv formats
A test case where we use a similar count(..) function in a filter condition.

Thoughts?

Thanks Rahul for your review and comments.
I will add tests for (1.) and (2.) in my next commit, and also include CSV and JSON data in my tests.


New AI PracticeTool

The Tool has some bugs with the new AI.
Can u fix this ? The Tool has to choose the right positions for the bots i think..
If i change anything on the positions or i change the bots.. the ui is completly broken and i have to restart the process.
Many thanks for ur time and work :)

Seconding what 4c7578 said. The tool "works", but positions, champions, and bot type cannot be changed without screwing up the UI (most often just kicks you out of the lineup and freezes the UI up when you try to join back).
An update would be great, thanks for your time!

At the current state, I don't think there's much to what I can do since Riot seems to implement a verification of some sort and it triggers if you interact with the UI.
I'll see if I have time to come up with a UI so you can select your preferred bots before it creates the game so you will have the right bots to get started.

This problem kind of resolved itself. When you start a game now, its just empty and there hasn't been a new release of this tool... so I guess this issue can be marked as solved.


Fix #63, support data attributes.

@jdegoes @cryogenian @garyb Could you please review?
Details here:
https://github.com/Matt-Esch/virtual-dom/blob/7cd99a160f8d7c9953e71e0b26a740dae40e55fc/docs/vnode.md#custom-attributes-data-

Is it possible for attributes to be set in props? If so, that may overwrite data- properties set this way - we'd need need to merge a props.attributes and props1.attributes instead.

The only way that's possible right now is if the user creates a custom attribute, of type { attributes: _ }, which I consider to be a misuse anyway.
I actually tried a different approach in which the props constructor branched depending on the key, but then the combineProps function got a bit confusing.
I guess it depends what we want the Props type to represent. If it's just a map for internal use, I think it's probably fine, as long as people stick to the API. If we want it to represent valid virtual-dom property objects, ready to be passed to vnode, then this obviously won't work.

Sorry, didn't have a chance to review this (was scheduled for Monday), get sorted out all right???

Yep, @garyb and I went over it on IRC. I think this is probably the best approach for now, but we can revisit it if necessary.


Refactor to do a real login for OAuth

Fixes https://github.com/jhipster/generator-jhipster-ionic/issues/656.

Unfortunately, this won't work with Keycloak at a domain different then localhost.
This cypress bug, got me to implement the login using api.
The oauth2 would be ready a couple of days ago =).

You're right. If I try to do this:
export SPRING_SECURITY_OAUTH2_CLIENT_PROVIDER_OIDC_ISSUER_URI=http://keycloak:9080/auth/realms/jhipster

I get the following error when running Cypress tests.

This kinda stinks because it means you can't run Cypress tests when running the backend via Docker Compose. That's the only downside I see. You shouldn't be using Keycloak in production anyway. ;)

What do you think about using the API method for Keycloak and using origin for Auth0 and Okta?

Sure, we can move keycloak ui once cypress fixes it.

OK, this PR now uses the API for Keycloak. I tested it on Keycloak with the default settings, as well as:
export SPRING_SECURITY_OAUTH2_CLIENT_PROVIDER_OIDC_ISSUER_URI=http://keycloak:9080/auth/realms/jhipster

I tested it on Okta and Auth0 too. There is a test in login.e2e-spec.ts that fails unless you change your user to have the first name of "Admin".
  // Incompatible with oauth login by api
  it('should login successfully with admin account', () => {
    cy.login(ADMIN_USERNAME, ADMIN_PASSWORD);
    cy.visit('/');

    const welcome = /Welcome, Admin/;
    cy.get('app-home ion-title').invoke('text').should('match', welcome);
  });


Some files not in the zip

Hi,
Thanks for php-ml!
I'm not on my dev machine and would like to have the whole src of your project.
Clicking on "download as a zip file" I get an archive without the docs or tests.
Is it normal?
Thanks.

It's completely normal. The reason for this is .gitattributes. This allows you to reduce the package size that is installed in the target application. If you need all the files, the git clone option remains

Thank you for your explanation. I couldn't find this in the Github docs because it was in the Git docs.


Why set barRect.size.height = bottom - top to be negative?

@danielgindi I was looking into some details about bar chart view today, and I found that the barRect height is negative after calculation, this surprised me a little. Could you explain some details here? Also, where you made the trick to handle the negative height? I don't see you manipulate the matrix.
var top = isInverted ? (y <= 0.0 ? CGFloat(y) : 0) : (y >= 0.0 ? CGFloat(y) : 0)
var bottom = isInverted ? (y >= 0.0 ? CGFloat(y) : 0) : (y <= 0.0 ? CGFloat(y) : 0)
...
barRect.origin.x = left
barRect.size.width = right - left
barRect.origin.y = top
barRect.size.height = bottom - top // supposed to be negative

It could be negative or positive, depending on the specific bar - but you don't have to do any "trick", as all rendering platforms (that I know of, including iOS and Android) take care of negative heights automatically.
It's simple for them because they do not consider width and height, but x1 = left, x2 = left + width, y1 = top, y2 = top + height

@danielgindi but if I try to use barRect.size.height = abs(bottom - top), it actually broke the rendering.

Of course it did, you have change its direction. y2 = (10 + (-50)) = -40 vs y2 = (10 + abs(-50)) = 60

Ah I see. Thanks for the lesson!

:-)


Kudos!

Thanks so much for this guide! I was pulling my hair out after most of the applications I wanted to use refused to install on a case-sensitive file system. This would have been super arduous without your help.

Oh, sweet! That's exactly why I wrote it all down and I am really glad it is still helpful. What version of Mac OS X did you work with, @kylehovey?

High Sierra, most recent version / patch. Luckily I only had around 10 naming conflicts, 9 of which were in /System. I just deleted the first result for each of the /System entries and your technique worked without hassle.

Thanks so much for your feedback! I updated the how-to according. Good to know that the technique still works on recent Macs.


Inline tx adapters

This PR "inlines" the transaction adapters to and from Cosmos SDK and Ethereum types. Previously, they were being passed around as callbacks (we had needed this abstraction to avoid a dependency cycle, but that's no longer a concern).
Essentially, we are removing the callbacks and instead calling the adapter implementations directly, for example, AdaptCosmosTxsToEthTxs.
Remaining Work
There are some other pain-points around the mixing of formats that can be simplified here as well.

Right now we mix our handling of Ethereum and Cosmos formatted data way too much (left over from older days of the codebase).

I plan on doing a scan through the codebase to locate these points where we are unnecessarily mixing transaction formats. We want to only use Ethereum formatted Txs at API boundaries, and use Cosmos SDK format internally.
For reference, we need to convert (or adapt) in a few cases:

Eth --> Cosmos: Only for a few transactions that are sent by the OP node (see the OP Stack Spec).
Cosmos --> Eth: For the few transactions originally sent by the OP node, when the OP node requests the execution payload, and for all transactions in the block when we are returning blocks from the eth_getBlockByNumber and eth_getBlockByHash APIs.

Can we remove the adapter types in the top-level monomer package?

Can we remove the adapter types in the top-level monomer package?

Yes, I don't believe they are used anywhere. I'll do that now.


PUPIL-586 feat(pupil header): create pupil journey header and story

How to review this PR
Leave this text block for the reviewer

Check component hierarchy is followed correctly
Check the design Heuristics have been followed
Check naming conventions have been applied
Check for these gotchyas:

Missing exports for Oak components
Accidental export of Internal components
Snapshots of unexpected components have been modified
Circular dependencies
Code duplication (via not using base components)
Non-functional storybook for this or related components
Sensitve files changed eg. atoms, or style tokens
Relative imports
Default exports

Add your PR description below
Ia the header component for the pupil journey; which contains the icon, title and breadcrumb
it can be used for unit, tier and lesson listing for both primary and secondary
Link to the design doc
https://www.figma.com/file/zqpeecgzMGKRli2gUdJOLp/Pupil-Browse?type=design&node-id=3993%3A50489&mode=dev
A link to the component in the deployment preview
https://deploy-preview-143--lively-meringue-8ebd43.netlify.app/?path=/docs/components-organisms-pupil-oakpupiljourneyheader--docs
Testing instructions
Go to deployment review and check that the component has the correct styles and can meet the needs for all its use cases
ACs

@benprotheroe I think this is looking good. I've mapped this out across the different breakpoints and also added an optional title that would appear for units with options:

Hey @benprotheroe give me a nudge when you want a design review for this component.

Thanks @benprotheroe, feedback below:

It looks like there may be a missing breakpoint for mobile (the OakSubjectIcon changes size for mobile from the tablet breakpoint).
Only other thing was the option to have a unit title as a boolean that can be turned on to appear above the lesson or unit title for when there is an optional unit (or is that part of another ticket?)


Service: Flowise

Changes

Added new service: Flowise

Issues
N/A

@andrasbacsai

Thank you for the PR 💜. I will test it and fix it if necessary.

Hi! I don't see Flowise as an available service after upgrading the coolify version. Does anyone see it?

It will be available soon via this PR https://github.com/coollabsio/coolify/pull/3838


Add error classes for symbol delisting errors, closes #270

You will need to bump version to 0.3.0 as this might be a breaking change for some people who string comparing the previous error message.

Going to reopen a clean PR


Add support for ticks.source: 'data' to category scale

Expected Behavior

I expect that using the new 2.7 feature of defining a bar chart using arrays of objects with x/y values e.g. [{x: ..., y: ...}, ...] to generate the x labels and y values on a barchart as per the docs here: http://www.chartjs.org/docs/latest/charts/bar.html

You can also specify the dataset as x/y coordinates.
data: [{x:'2016-12-25', y:20}, {x:'2016-12-26', y:10}]

Current Behavior

See interactive pen here: https://codepen.io/ortonomy/pen/NaxVeZ
Providing a data.dataset with an array of x/y objects (e.g. data: [{x: ..., y: ...}, ...]) does not render all data points. It only renders a single bar, using the first value of the data set.
The only way that I can get it to display multiple values, is by providing the labels: [...] property to the data object. And even then, the number of bars displayed is only equal to the length of labels: [...].
I may be wrong here, but from what I can tell, the reason for providing the array of x/y objects is so the data itself provides the x label.

Steps to Reproduce (for bugs)

code
data: {
        // labels: ['x','x'],
        datasets: [{
            label: '# of Votes',
            data: [{x: 'label', y: 12}, {x: 'label', y: 19}, {x: 'label', y: 3}, {x: 'label', y: 5}, {x: 'label', y: 2}, {x: 'label', y: 3}]
        }]
    },

link
https://codepen.io/ortonomy/pen/NaxVeZ
Context

The data coming back from my API is already in an object: {x: ..., y: ...} format so you can imagine my joy at seeing this being provided as an option. Now I have to split the data to use x: ... for labels: [...], and then y: ... for data: [...].
Environment

Chart.js version:
2.7.0
Browser name and version:
Chrome 61 Mac OS X
Link to your project:
Can't link -- is private.

This feature is reference here: https://github.com/chartjs/Chart.js/releases/tag/v2.7.0

#4456 Allow specifying bar chart via {x, y} data points. Thanks @benmccann

+1 Aloso found this bug today

Hmmm. There were some more change in https://github.com/chartjs/Chart.js/pull/4673 after my PR was merged. I wonder if that change didn't have its intended effect or if there's something else going on. Any ideas @nagix ?

Yes, you still need to specify the labels. It's at least a bit easier for you because you now only need to create the labels instead of creating the labels and transforming the data from your format to array format.
One solution to this would be to add a ticks.source: 'data' just like @simonbrunel added in the time scale in https://github.com/chartjs/Chart.js/pull/4507. And it should default to this if the user doesn't specify any labels.

Hmmm,
@benmccann -- but why then specify [{x:...,y:...},...] objects if the x:... part is never used. You're right it saves a little bit of time, but I still have to extract the x part into an array of labels.
To actually make use of this feature, the label resolution should be
for type bar chart

if data: { datasets[{data: [{x:...,...},...],...],...},...} else
if data: { labels: ['label',...],... } else
error

I might be missing something of course.

Yes, I agree with you. It depends on the type of scale that you use. It works the way you'd expect with the time scale. It doesn't work well with the category scale, which is the default scale used by the bar chart.

@ortonomy Your codepen link does not work for me, it just opens up an new untitled pen on my account over at codepen.

@tchan -- thanks for pointing that out. I've updated the link

Renders all points in v3.0.0-beta.12 https://codepen.io/etimberg/pen/zYoJPxE


Mini Project Review Ticket

Score
Runtime Link
Plan
Github
Analytics

Frontend
plan

Individuals

Name
Team+Individual+Teacher
Runtime
Issues
Key Commits
Analytics

Haoxuan

sort addingadding sorting progress

Aaron

Quinn

Individual Review Luna Iwazaki grading Quinn B

[ ]  Individual should show that they were key contributor and example to team. This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.

Individuals Video, Issue(s), Commits(s)

[ ] Video, includes Web demo of key contribution to project, 1 minute

[ ]  Issue(s) that show plans/progress to team objectives

[ ]  Highlights of key commit(s) in Issues, summarizes code contributions

[ ] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks

Per check.
0.55 not attempted/no check
0.7 attempted, incoomplete, but some runtime
0.8 mastery and runtime
0.9 above and beyond.
Freeform comment.
Provide positivies and growth summary.
Justify or comment on final score.
Be sure to provide extra details on anything below 0.7 average or above 0.8.
GRADE: XXX
comment

Individual Review "Mati" grading "Haoxuan"

[ ] Individual should show that they were key contributor and example to team.  This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.

Individuals Video, Issue(s), Commits(s)

[ ] Video, includes Web demo of key contribution to project, 1 minute
[ ] Issue(s) that show plans/progress to team objectives
[ ] Highlights of key commit(s) in Issues, summarizes code contributions
[ ] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks

Per check.
0.55 not attempted/no check
0.7 attempted, incoomplete, but some runtime
0.8 mastery and runtime
0.9 above and beyond.
Freeform comment.
Provide positivies and growth summary.
Justify or comment on final score.
Be sure to provide extra details on anything below 0.7 average or above 0.8.


Input keeps state when input manually

For some reasons, when input manually, the value in the input is not reset when the state is.

How are you resetting the state?

resetting the state works when date has been chosen with datepicker but not
manually input. The input itself is uncontrolled
2017-09-21 15:44 GMT+02:00 Ivan Jager<EMAIL_ADDRESS>
How are you resetting the state?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Hacker0x01/react-datepicker/issues/1025#issuecomment-331160649,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACNKqrOTAowQaYUTYUt_ThVCf84TzWkoks5skmhIgaJpZM4Pagli
.

--
 __________________________
!\_________________________/!\
!!                         !! \
!! fsociety: ALX-DEV~$     !!  \
!! Alexandre Teilhet~$     !!  !
!!  How are you resetting it?

we are using the seleted property linked to a state variable.

Ok, I'm going to assume this is a duplicate of #888 unless you care to explain how this issue is different.


Operator multus

Description
Allow decoupling external connectivity using multus.
Attractor CRD supports multus based configuration via new Interface Type network-attachment, where
name and k8s namespace of a network-attachment-definition must be provided as part of NetworkAttachmentSpec (if namespace is ignored, it defaults to k8s ns default).
Additionally, Name of the Interface provided in the InterfaceSpec will by default be used as the POD interface name for both nsm-vlan and network-attachment based interface attachment mechanisms. (For the latter, it can be overridden in NetworkAttachmentSpec by setting InterfaceRequest.)
The demo: (described in multus-kind-ovs.md) Example to run Meridio via Operator using Multus/OVS-CNI on NSM with forwarder-ovs.
Issue link
https://github.com/Nordix/Meridio/issues/326
Checklist

Purpose

[ ] Bug fix
[x] New functionality
[ ] Documentation
[ ] Refactoring
[ ] CI

Test

[x] Unit test
[ ] E2E Test
[x] Tested manually

Introduce a breaking change

[ ] Yes (description required)
[x] No

Introduce changes in the Operator

[x] Yes (description required)
Attractor CRD extended.
[ ] No

The CI doesn't support it this generator yet so it didn't complain, can you do make generate-controller
I tried the demo instructions, everything works as expected.

Thanks, I was using the old make command generate :)


Socket is not writable

Happened on commit  b2f9f19d99c
throw new Error('Socket is not writable');
          ^
Error: Socket is not writable
    at Socket._writeOut (net.js:391:11)
    at Socket.write (net.js:377:17)
    at WebSocket.write (/home/realtime/node_modules/socket.io/lib/transports/websocket/hybi-07-12.js:130:17)
    at WebSocket.onDispatch (/home/realtime/node_modules/socket.io/lib/transport.js:222:10)
    at Manager.onDispatch (/home/realtime/node_modules/socket.io/lib/manager.js:356:31)
    at SocketNamespace.packet (/home/realtime/node_modules/socket.io/lib/namespace.js:156:16)
    at SocketNamespace.emit (/home/realtime/node_modules/socket.io/lib/namespace.js:188:15)
    at /home/realtime/server.js:38:24
    at [object Object].<anonymous> (fs.js:107:5)
    at [object Object].emit (events.js:61:17)

This can be closed. Fixed along with  #555 in bee1efb11c5f52159d88502a925fa6d2c58cd680


fix(search): restore mobile search view

This PR restores the mobile search view to mobile layout and the desktop search view to tablet layout, instead of using the wrong layout for both.
After
Mobile

Tablet

Before
Mobile

Tablet

i believe the old mobile view also used to have a small portion of preview text too, lemme pull it up

https://github.com/jackyzha0/quartz/pull/722#issuecomment-1918689492

#722 (comment)

Alright, one sec.

#722 (comment)


feat(frontend): Introduce OisySymbol prop for appearence interface

Motivation
For grouping tokens, we are going to re-use the TokenCard component that takes a few props of a given token, for example name and symbol. However, for the group, we will provide some different data to be shown, just for appearance sake.
For prop name, we already have oisyName substitute to show something different in place. But, for symbol, there is nothing.
So, similar to oisyName, we create an optional prop oisySymbol to be provided if we want to show some substitute to the usual token.symbol, just for different appearance.
UNRELATED: Since we are here, we will set oisyName.prefix as optional prop, since it makes sense

[OISY-69]


[Improvement]: removeAll() function in lang.array and lang.map panics with inconsistent errors

Description
public function main() {
    int[] arr = [1, 2];
    int[] r = arr.cloneReadOnly();
    r.removeAll();
}

This panics with error: {ballerina/lang.array}InvalidUpdate {"message":"modification not allowed on readonly value"}.
public function main() {
    map<string> m1 = {a: "A"};
    map<string> m2 = m1.cloneReadOnly();
    m2.removeAll();
}

This panics with error: {ballerina/lang.map}InvalidUpdate {"message":"Failed to clear map: modification not allowed on readonly value"}, which is a map-specific error.
This behaviour is inconsistent. What should be the expected error?
Describe your problem(s)
No response
Describe your solution(s)
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

@sameerajayasoma @hasithaa @warunalakshitha @gimantha
Thoughts, please? We should decide on a consistent behaviour to be adhered to in lang.array, lang.map and lang.table


Possibility for a more broken-out build driven by external configuration?

The current build configuration is excellent for producing a very high-performance app with minimal load-time dependencies, but it would be quite helpful for our integration purposes building scrollytelling apps such as https://imerss.github.io/howe-sound-mapping/R-Markdown-AHSBR_Map_1-Reknitted.html# if @imerss/inat-components included in its npm dist a partially built distribution that accepted an external configuration file such as the one at https://github.com/IMERSS/inat-components/blob/main/apps/standalone/src/inat.config.json rather than this being baked into the bundle.
In the end we are aiming for an authoring pipeline that can be driven directly by editing R markdown files and scripts like the ones at https://github.com/IMERSS/howe-sound-mapping/blob/main/scripts/Vascular_plant_map_script.R and whilst we could build the react-scripts process into this pipeline it would be helpful and more performant if we could pull in a "ready to go" configuration-driven distribution of the components - ideally this would also expose configuration of some of the strings seen in the root component definition at https://github.com/IMERSS/inat-components/blob/main/apps/standalone/src/index.tsx#L27
Cheers for any suggestions on the best route for this!

Hey @amb26, great idea. The first version of this app was very much to satisfy my own requirements for BC Leps, but separating the config from the build files and generally make it easier to consume without having to do any local builds would be great.
Lots to think about here... but how about something like this.

In the @imerss/inat-components package, I could include a new standalone.min.js file. That would NOT be referenced in the main/module property of the package's package.json file, it would simply be an extra file that's included in the bundle for anyone that wanted to use it.

As a consumer, you could then do this.

<script src="./standalone.min.js" />
<script>
var myData = {
   // data structure TBH, but this would include everything - settings, classes, strings, etc.
   // just not the actual data for the app - that would still be external.
};
<script>
</script>
<div class="inat-components" data-source="myData" />

Details:

First you'd include the new standalone.min.js file
You'd define all your settings in your own variable somewhere, calling it whatever you wanted
You provide a custom div somewhere with the class name inat-components (or something a little more scoped... but perhaps this is ok). Then to link the two: the DOM node of where it'll be rendered and the data used as the data source,
if you provided class names for the elements, you would need to define your own CSS somewhere in the page.

Feels a bit klutzy feeding in the data this way, but alternatives like passing in the data as a serialized HTML property in a data-role strikes me as a pain for the consumer.
Any better ideas? And do you think this would solve your use-case?

Yeah, better! If it has to be a globally defined, I prefer that to what I suggested before. So how about this:
<script src="./standalone.min.js" />
<script>
inatComponents.init({ ... });
</script>

I'll expose a global window.inatComponents object which contains an init function. At this point, all we need is that one function but I figure I'll make it an object just in case down the road we may want to expose an .update() or whatever & not break the interface.
I'm game if you are. :)

I'm game if you are. :)

Yup that sounds fantastic!
As we might indeed want more/more varied functions perhaps you could save the top-level object as a kind of namespace and so name the constructor after the profile, e.g. iNatComponents.makeStandalone or iNatComponents.initStandalone or so.

Agreed, iNatComponents.initStandalone is probably clear. Will do!


errNotInTransaction is not a public error

Hello -
I'm curious why errNotInTransaction is not a public error. It is returned to the calling client in cases when a transaction has not been opened, and it would be nice to be able to check explicitly for this error type.

The original version of franz-go had way too many errors public, most of which were internalized before stabilizing on 1.0. What's the need to check against errNotInTransaction? I'd expect that error to mean an application bug, in that you may encounter it when developing but you'd never encounter it in production?

The need is largely convenience, I'm calling EndTransaction with kgo.TryAbort when my application receives an exit signal, so it will throw this error if it didn't happen to be in the middle of doing something. I can obviously work around this by keeping track of whether a transaction is in-flight or not, I just think it is an unpleasant API to return un-exported types.

What do you think about calling kgo.AbortBufferedRecords before that? It takes a context, but it really shouldn't block. The intent is that no record should be buffered when entering EndTransaction.

Hm, yeah, it looks like I'm not calling kgo.AbortBufferedRecords at all right now (even in cases where it looks like I should be). I'm not following how this relates to the first question about calling EndTransaction when not in a transaction though? Is that because I would expect a different error from kgo.AbortBufferedRecords if it's called outside of a transaction?

If records are aborted, the client calls promises with the exported ErrAborted (this is the case whether in a transaction or not). The API of EndTransaction is such that it expects no records are buffered when entering, and nothing will be produced while EndTransaction executes (as well as BeginTransaction). In short, the errNotInTransaction error should never be encountered.
Are you concurrently calling EndTransaction while producing? I worry that if you're encountering the error at all, you may be concurrently producing.

No, in the regular case my application finishes processing data and calling Produce, then calls Flush and then EndTransaction with TryCommit. In the case where I'm hitting this error my application is idling when it gets a cancellation signal, and then I'm calling EndTransaction with TryAbort.

Are you seeing this as a return from EndTransaction? I thought you were seeing this in a record promise.

I am seeing this on the return from EndTransaction, the error message is cannot produce record transactionally if not in a transaction though, so it's a bit confusing. I believe I'm hitting this line
	if !cl.producer.inTxn {
		return errNotInTransaction
	}

I can probably relax this error in EndTransaction to return nil if not currently in a transaction. To confirm, when you call EndTransaction on client close, do you kill and wait for the other goroutine that is beginning / producing / ending?

That seems reasonable to me.
Yes I do, it's part of the same routine.

This has been released in v1.3.5 (v1.4 will be a much larger release, soon)

This has been released in v1.3.5 (v1.4 will be a much larger release, soon)

Thank you!


vendor: update Masterminds/semver

Towards https://github.com/giantswarm/giantswarm/issues/6844
I got this while updating opsctl:
Solving failure: No versions of github.com/Masterminds/semver met constraints:
        v3.0.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v3.0.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.5.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.4.2: Could not introduce<EMAIL_ADDRESS>as its subpackage github.com/Masterminds/semver/v3 is missing. (Package is required by<EMAIL_ADDRESS>        v1.4.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.4.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.3.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.3.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.2.3: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.2.2: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.2.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.2.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        v1.1.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        1.1.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        1.0.1: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        1.0.0: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        master: Could not introduce github.com/Masterminds/semver@master, as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        2.x: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        release-1: Could not introduce github.com/Masterminds/semver@release-1, as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.
        release-1.2.3-prep: Could not introduce<EMAIL_ADDRESS>as it is not allowed by constraint 1.4.2 from project github.com/giantswarm/helmclient.

$ dep version
dep:
 version     : v0.5.4
 build date  : 2019-06-14
 git hash    : 1f7c19e
 go version  : go1.12.6
 go compiler : gc
 platform    : darwin/amd64
 features    : ImportDuringSolve=false


Avoid uninitialized variable (fixes #1203)

Only use last_scraped when it has certainly been initialized before.

Thanks! I released 4.8rc3 with this fix included.


Add vim swap files to gitignore

What it says on the tin.
Was working on reviewing #311 and the qa tools complained, loudly, about my swap files :joy:

well, looks like that wouldn't actually help, doh! - though I'm wondering if I can ignore them in the sdist:

lists of files in version control and sdist do not match!

Looks like there's a bit more - I need to add the ignores to MANIFEST.in as well. I was also still seeing the QA fail - was failing on the news/version last check. I'll need to poke at that a bit more, too :thinking:

Okay, this works now.

Okay, assuming all the tests pass, this should be good to merge whenever. Will probably merge tomorrow afternoon if there are no objections.

No objections, so merging


A patch for url-encode.xsl potential to stackoverflow

GitHub issue resolved: #3676
Briefly describe the changes proposed in this PR:
Use a divide and conquer approach to iterate through the xslt string in order to prevent a stackoverflow for large strings.  see: https://stackoverflow.com/a/9081077/5237756

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[ ] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[x] I've squashed my commits where necessary
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

Thanks for submitting this patch @nguyenm100 ! I'll need to find some time to build the workbench and run a test with this - can't think of an easier way to test this unfortunately.


US 0.5 Figma User Story Prototype

started the design project: https://www.figma.com/file/PiCaW09Eg5poVr7aXVYCid/Peer2Pressure?node-id=0%3A1&t=gF9dL2dPpjdlwjOf-1

created the styletile
created the moodboard from one source (https://www.behance.net/gallery/43661487/What-if-Linkedin-was-beautiful-Redesign-concept?tracking_source=search|minimal)

finished two mockups (login and sign up view)
started mock up for post feed view (still ongoing) -- have to study now>.<

added more elements onto the post feed view, currently stuck with post whether we should go for a card view (have to check react how this is implemented) and put all editing elements in it than in the feed itself.
still have to check what a commonmark is <-- what is this? haha.
tried to implement ways to distinguish a public/private post (added green elements to indicate friend posts (like IG); blue for public like globe <- globe is kinda blue? lol)
will do more work tomorrow

worked on creating a public post mockup
started upload a photo mockup <- still have to show a file browser pop up after clicking add photo
added blue indicator to indicate self posts (idk how to implement this on react yet but we can also think of other ways to show this type of indication that's easier to implement in react if possible --less work for us haha)
added a meatball menu because a post can be deleted and edited
added mockups for edit and delete as well


AccessDeniedException: An error occurred (AccessDeniedException) when calling the CreateTokenWithIAM operation:

We are getting this error for some users. But other user can login without issues.
File "/opt/custom-web-experience-with-amazon-q-business/venv/lib/python3.11/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 600, in _run_script
    exec(code, module.dict)File "/opt/custom-web-experience-with-amazon-q-business/src/app.py", line 37, in
    st.session_state["idc_jwt_token"] = utils.get_iam_oidc_token(st.session_state.token["id_token"])
                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^File "/opt/custom-web-experience-with-amazon-q-business/src/utils.py", line 72, in get_iam_oidc_token
    response = client.create_token_with_iam(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^File "/opt/custom-web-experience-with-amazon-q-business/venv/lib/python3.11/site-packages/botocore/client.py", line 565, in _api_call
    return self._make_api_call(operation_name, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^File "/opt/custom-web-experience-with-amazon-q-business/venv/lib/python3.11/site-packages/botocore/client.py", line 1021, in _make_api_call
    raise error_class(parsed_response, operation_name)

@justmekaren are there differences in terms of IAM groups, roles and permissions among the different users?

I dont think there is a difference, we used the IAM IDC is the org level and controlled the access in cognito in the account level. As far as I understand it would always assume the IAM role assigned to the application.

I am wondering if you have any defined Service control policies at the AWS Organizations level that explicitly denies the sso-oauth:CreateTokenWithIAM action for one or more specific IAM Identity Center groups.

Hello @justmekaren, this error can happen if the user trying to connect is not assigned to the customer managed application that you created in IAM Identity Center.
The options to solve this are either to switch the customer managed application that you created to not require assignments and allowing every authenticated user to exchange token or you should assign users to the customer managed application.

Let me know if this solves the issue.

Thank you this resolves the issue now.

I realized another issue came up.
AccessDeniedException: An error occurred (AccessDeniedException) when calling the ChatSync operation: User is not authorized for this service call.
Traceback:
File "/opt/custom-web-experience-with-amazon-q-business/venv/lib/python3.11/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 600, in _run_script
exec(code, module.dict)
File "/opt/custom-web-experience-with-amazon-q-business/src/app.py", line 118, in
response = utils.get_queue_chain(prompt,st.session_state["conversationId"],
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/custom-web-experience-with-amazon-q-business/src/utils.py", line 135, in get_queue_chain
answer = amazon_q.chat_sync(
^^^^^^^^^^^^^^^^^^^
File "/opt/custom-web-experience-with-amazon-q-business/venv/lib/python3.11/site-packages/botocore/client.py", line 565, in _api_call
return self._make_api_call(operation_name, kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/custom-web-experience-with-amazon-q-business/venv/lib/python3.11/site-packages/botocore/client.py", line 1021, in _make_api_call
raise error_class(parsed_response, operation_name)

@justmekaren This usually means that the user trying to access Q is not subscribed in the Q business app.
However we've also just fixed an issue where credentials would outlast the current app session which could lead to this error if you tried once to use Q and then subscribed. Could you try to redeploy the EC2 instance (just terminate it and the autoscaling group will create a new) and confirm if you have still the error ?

But the user who was getting the error was already subscribed. Does that mean that all user must subscribe to Q app before they can fully use it?

Hi
Did you try to redeploy the EC2 instance as I suggested ?
If you still encounter the issue, can you try to use the native UI of Q
(through IAM Identity Center) to confirm that Q is working correctly ?
Regards,
Joseph
Le lun. 24 juin 2024 à 14:48, justmekaren @.***> a
écrit :

But the user who was getting the error was already subscribed. Does that
mean that all user must subscribe to Q app before they can fully use it?
—
Reply to this email directly, view it on GitHub
https://github.com/aws-samples/custom-web-experience-with-amazon-q-business/issues/16#issuecomment-2187194492,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7H63A736AUKQENYHONVP3ZJBSZDAVCNFSM6AAAAABJXUSBO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBXGE4TINBZGI
.
You are receiving this because you commented.Message ID:
<aws-samples/custom-web-experience-with-amazon-q-business/issues/16/2187194492
@github.com>

Yes, I did redeploy it and working as expected at the moment.


PHP Warning:  exif_imagetype(): stream does not support seeking in

what wrong with is?  Is some extension problem?
➜  image-ocr php study.php
PHP Warning:  exif_imagetype(): stream does not support seeking in /Users/dynamo/PhpstormProjects/hack/vendor/mohuishou/image-ocr/Image.php on line 40
Warning: exif_imagetype(): stream does not support seeking in /Users/dynamo/PhpstormProjects/hack/vendor/mohuishou/image-ocr/Image.php on line 40

Perhaps the image link is wrong.
Replace the image link, the program can be successfully run

https://github.com/mohuishou/ImageOCR/commit/b451f452459c8c55e6431adefcabfb25edda12cb


Change omega to lambda in likelihood equation?

The User Manual equation showing the total likelihood uses the symbol omega as the weighting factor for each objective function component. However, throughout the text we refer to these weights as "lambdas". This led to confusion for one user who wrote to ask for clarification by email.
Would it be OK to change the equation from

to the following:

?
The drawback of this change is that the equation no longer matches the syntax in the Methot and Wetzel 2013 supplementary materials, but I think the translation is clear enough that it wouldn't be a problem.
Those changes were made in commit 7b57f60 but can be easily reverted or further refined. Note the last sentence of the description also needed to change an omega to a theta (I accidentally used capital Theta).

@iantaylor-NOAA , I think that is a great idea, especially since someone asked you a question about it.

I concur with this good clarification.

Thanks for the quick responses. I change to lower-case theta in a subsequent commit and confirmed that the equation still looks right, so now closing.


annonymus access to e.g. host/ckeditor/pictures or any other ckeditor asset model

I don't know if it is a bug, but there is an easy anonymous access to any asset folder within ckeditor models.
Is there any way to restrict access to ckeditor models? f.e. - in combination with any authentication gem(devise or else)?

for Devise solved with:
config.authorize_with do
  redirect_to SOME_URL unless signed_in?
end


Multiple Graph Session objects

Describe the bug
Graph Sessions objects do not seems to be independant.
To Reproduce
Steps to reproduce the behavior:
Get users tenant A
client_secret_credentials = ClientSecretCredential(tenant_id='tenant_a',
client_id='xxxx-xxxx-xxxx',
client_secret=client_secret)
graph_session = GraphSession(client_secret_credentials, scopes)
result_a = graph_session.get('/users')
client_secret_credentials = ClientSecretCredential(tenant_id='tenant_b',
client_id='xxxx-xxxx-xxxx',
client_secret=client_secret)
Get users tenant B
graph_session = GraphSession(client_secret_credentials, scopes)
result_b = graph_session.get('/users')
print(result_a.content) # users tenant A
print(result_b.content) # users tenant A!
Expected behavior
print(result_b.content) # users tenant B
AB#9198

Thanks for reporting the issue @poiuytrez. We have managed to replicate the bug and identified the source. However we have since moved away from using GraphSession objects. This will no longer be an issue once we have updated to the new GraphClient.

@poiuytrez you can track the progress of the move to GraphClient #82


[identity] Sign in failing with no error messages

I can no longer sign in. When I chose to sign in, it goes through the whole auth flow and appears successful however the UX doesn't update and I don't appear signed in.

I don't have a repro, but this did happen after I deleted my account and then repro'ed: https://github.com/microsoft/pxt-arcade/issues/3194

Staging or prod?

localhost so staging


Improve factor configuration

Add bindings to fuel-help-mode
Add more bindings to factor mode
Add more bindings to fuel-listener mode

Thanks!


HTTP to docker.sock gives invalid label

http http+unix://%2Fvar%2Frun%2Fdocker.sock/info
returns:
"http: error: InvalidURL: URL has an invalid label."
Any ideas on what I'm doing wrong?

That error is coming from the requests library. See https://github.com/kennethreitz/requests/issues/3683 which talks about that error but for a different issue (hostnames with underscores). I would suggest that you try upgrading or downgrading requests.
I just fired up an Ubuntu 16.04 VM and it worked well for me without any issues.
msabramo@ubuntu:/tmp$ virtualenv venv
Running virtualenv with interpreter /usr/bin/python2
New python executable in /tmp/venv/bin/python2
Also creating executable in /tmp/venv/bin/python
Installing setuptools, pkg_resources, pip, wheel...done.
msabramo@ubuntu:/tmp$ source venv/bin/activate
(venv) msabramo@ubuntu:/tmp$ pip install httpie-unixsocket
Collecting httpie-unixsocket
Collecting requests-unixsocket (from httpie-unixsocket)
Collecting httpie>=0.7.0 (from httpie-unixsocket)
  Using cached httpie-0.9.9-py2.py3-none-any.whl
Collecting urllib3>=1.8 (from requests-unixsocket->httpie-unixsocket)
  Using cached urllib3-1.20-py2.py3-none-any.whl
Collecting requests>=1.1 (from requests-unixsocket->httpie-unixsocket)
  Using cached requests-2.13.0-py2.py3-none-any.whl
Collecting Pygments>=2.1.3 (from httpie>=0.7.0->httpie-unixsocket)
  Using cached Pygments-2.2.0-py2.py3-none-any.whl
Installing collected packages: urllib3, requests, requests-unixsocket, Pygments, httpie, httpie-unixsocket
Successfully installed Pygments-2.2.0 httpie-0.9.9 httpie-unixsocket-0.0.0 requests-2.13.0 requests-unixsocket-0.1.5 urllib3-1.20
(venv) msabramo@ubuntu:/tmp$ http http+unix://%2Fvar%2Frun%2Fdocker.sock/info
HTTP/1.1 200 OK
Content-Length: 1853
Content-Type: application/json
Date: Sun, 19 Feb 2017 03:07:07 GMT
Server: Docker/1.12.3 (linux)

{
    "Architecture": "x86_64",
    "BridgeNfIp6tables": true,
    "BridgeNfIptables": true,
    "CPUSet": true,
    "CPUShares": true,
    "CgroupDriver": "cgroupfs",
...
    "SystemStatus": null,
    "SystemTime": "2017-02-18T19:07:07.438157892-08:00"
}

Note that I have requests 2.13.0:
(venv) msabramo@ubuntu:/tmp$ pip freeze | grep requests
requests==2.13.0
requests-unixsocket==0.1.5

Give that a shot. I'll close the issue, but you can reopen if you're still having problems.


Support localized web UI

Allow to translate the web UI. I added some docs, take a look at them for the instructions.
Only issue is date/time formatting: this is not easy and our formatters must import every language that's added. There's an formatter in vue-i18n, the used i18n lib (https://vue-i18n.intlify.dev/guide/essentials/datetime.html). I will try to migrate it to this.
Closes #258

@qwerty287 please resolve :)

I cant find a menue to select languages, are you able to add it wothin this pull?

I cant find a menue to select languages, are you able to add it wothin this pull?

It uses your browser locale.

Oh, as default this is good, i still think you should be able to change it


Fix LakeFS startup with Azure storage type

LakeFS is not able to start after a restart if using Azure Blob storage as it returns https as storage class and lakeFS uses azure as storage class. This is fixed by an extended check for exactly this case by this PR.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @evelkey,
Thanks for the PR! I've gone ahead and assigned either of the people who know most about Azure urls to review. Please bear in mind that it's already weekend here so we may manage to review it only on Sunday.
In the meantime I've kicked off our ci process on this PR.

You can pass the flag -m that will skip this check at startup, until this issue will be resolved.

Thank you @guy-har, we tested it in our AKS deployment with Azure blob as the backend storage (needed to migrate from version 30 to 31) and all used features are now functional again.


Add PR ontology to KG

This is over 1 GB file and initially failed OWLNETS when downloading and running on the fly

The Data Distillery team agreed that PR had lower quality assertions than other ontologies that we are already ingesting. That plus the 9+ hour OWL-OWLNETS conversion time made ingesting PR not worth the candle. Closing for now.


Ensuring that at least one of a set of fields are set

It would be great if I could say something along the lines of:
#[derive(TypedBuilder)]
struct Foo {
    #[group(a)]
    #[default]
    bar: Option<String>,
    #[group(a)]
    #[default]
    baz: Option<String>,
    #[default]
    bat: Option<String>,
}

Made up the syntax, but basically some way to signal "one or both of bar/baz must be provided".

I don't think the Rust type system is flexible enough to allow this...

Actually... I was thinking about using marker traits, which are not stable yet, but instead I can use empty fields. Just set a field for each group and override its type when any member of the group is assigned.

I recommend stealing from #[cfg], for both optimal flexibility and familiarity.
Something like this, on the struct (not on the field any more):
#[builder(group = "a", required, any("bar", all("baz", not("quux"))))]

This would define a named group “a” (the name is for documentation, and may also be used in other places that accept a field or group, such as field dependencies which I’m about to create an issue about). In this case the group is also then declared to be required before build() can be called.

Recently started using this crate and quickly ran into a scenario that required something like this.
Is anyone working on this? If not, is anyone able and willing to provide guidance on getting this implemented?

See https://github.com/idanarye/rust-typed-builder/issues/14 and my algorithm https://codeberg.org/mo8it/sus-impls
The macro has to use the algorithm to generate implementations


Support multibyte strings and atoms

pyswip/core.py: Add functions required to work with UTF-8 encoded symbols.
pyswip/easy.py (Atom.__init__): Use PL_atom_wchars to get string representation of the atom. Unfortunately PL_atom_wchars can fail on some strings. e.g. second definition of father predicate from https://github.com/Hefaist/test_pyswip/blob/master/utf_facts.pl leads to "ValueError: character U+ffffffe1 is not in range [U+0000; U+10ffff]" error. Allow to pass correct string instead as a workaround.
(Atom.fromTerm): Pass atom string representation extracted from term_t to Atom constructor.
(Variable.__init__): Ask for a UTF-8 string.
(getAtomChars): Ask for a UTF-8 string. Remove "deprecated" comment still this function required for Atom.fromTerm function.
(getString): Ask for a UTF-8 string.
pyswip/prolog.py (Prolog._QueryWrapper.__call__): Specify that we'll send UTF-8 string to prolog.

Suggested change should fix #62 and https://groups.google.com/forum/#!topic/pyswip/82WEx6UX98w

@mnd Thanks for the fix. Could you add a test case?

@yuce I added tests examples from referenced places and from my own experiments.


Added a card of Tourist Landing page

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes:  #(issue no.)

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK
Project Link

Also, make it responsive for all screen sizes.

https://deploy-preview-508--cool-front-end-templates.netlify.app/tourist landing page/


Implement Camera

Follower camera
Camera is parent of the player spaceship nodes.
Gamearea change when players move farther until the maximum distance.
https://www.youtube.com/watch?v=nnyZflag60Q

Done


Display @deprecated doc when available

We need to display documentation associated with the @deprecated tag when available.
Currently we are only displaying the tag on a page, and the documentation is being "scrubbed".  For example: https://deno.land/api@v1.25.4?s=Deno.iterSync which looks like this in JSDoc:
declare namespace Deno {
/**
   * Turns a ReaderSync, `r`, into an iterator.
   *
   * ```ts
   * let f = Deno.openSync("/etc/passwd");
   * for (const chunk of Deno.iterSync(f)) {
   *   console.log(chunk);
   * }
   * f.close();
   * ```
   *
   * Second argument can be used to tune size of a buffer.
   * Default size of the buffer is 32kB.
   *
   * ```ts
   * let f = await Deno.open("/etc/passwd");
   * const iter = Deno.iterSync(f, {
   *   bufSize: 1024 * 1024
   * });
   * for (const chunk of iter) {
   *   console.log(chunk);
   * }
   * f.close();
   * ```
   *
   * Iterator uses an internal buffer of fixed size for efficiency; it returns
   * a view on that buffer on each iteration. It is therefore caller's
   * responsibility to copy contents of the buffer if needed; otherwise the
   * next iteration will overwrite contents of previously returned chunk.
   *
   * @deprecated Use `iterateReaderSync` from
   * https://deno.land/std/streams/conversion.ts instead. `Deno.iterSync` will
   * be removed in Deno 2.0.
   *
   * @category I/O
   */
  export function iterSync(
    r: ReaderSync,
    options?: {
      bufSize?: number;
    },
  ): IterableIterator<Uint8Array>;
}

Done in https://github.com/denoland/doc_components/commit/0b6e1004f2cb3147a65015424cc732839111e828


Write a R program to convert string to reversecase

Description
Write a R program to convert string to reversecase
Reversecase is a style of writing in which all lowercase letters are converted to uppercase and all uppercase letters are converted to lowercase.
Input  : "hello world"
Output : "HELLO WORLD"

How to contribute

Save the solution in convert_string_to_reversecase.r file
Add convert_string_to_reversecase.r file in program/convert-string-to-reversecase folder

!assign


Make Modals Adapt to Screen Size

Description
Filters modal is fixed height and too big for small screens.
Expected Behavior
Current Behavior
Screenshots

Steps to Reproduce
Tasks

Completed


docs: Migrate LCEL documentation to Docusaurus with Diátaxis framework structure (#468)

As per #468 , I've moved the LCEL docs to Docusaurus.
Sorry I had confusion since we initially decided to take inspiration from the python docs using diataxis.
However, there are some differences in moving the docs as they are since this may cause quite some duplication. If I move the docs as they are, the sections under modules may bring duplication in how to organise the documentation.
As we decided to use diataxis.fr, I've created placeholders and empty markdown files for each of the how_to guide and tutorials section. These markdown files have also been added to the sidebar for quick navigation and testing, so anyone can easily contribute to a specific file and just deploy the changes.
I think with this, we can progressively move towards parity with python/js langchain ecosystem.
I also think that the sections under modules can easily fit into the how_to or tutorials sections.
Let me know what you think.

Hey @bettdouglas,
Thanks for the PR!
Sorry, I merge the PR by mistake while I was trying to push some commits to your branch. I've reverted the changes. Could you create a new PR? 🙏

No problem @davidmigloz, I've recreated the PR in #630


Help!!!! not getting refresh-openid-connect-well-known

Hi ,
Thanks for such lib. I am trying to use this lib for my current project but not getting 'refresh-openid-connect-well-known' action under admin panel bz of that getting below error "Invalid URL 'auth/realms/Master/.well-known/openid-configuration': No schema supplied. Perhaps you meant http://auth/realms/Master/.well-known/openid-configuration?" can you guide me where it is wrong.

Please start the url with https://

https:// did't work..
this is my repo. i copied keycloak folder bz there was some issue with python version. superuser:pwd/admin:admin. can you please advice where it is wrong.
https://github.com/garimagupta715/django_keycloak_lib

do you have any error log?

delete th "auth" in Url.
localhost:8080 is enough.

this is not bad

I am facing the same issue, did anybody solve it?


register template kvm context ui fix

Description
On the 'Register Template From URL' screen, when a user selects the KVM option from the Hypervisor dropdown:

It incorrectly displays the 'Original XS Version is 6.1' checkbox. This checkbox should be hidden in the KVM context.
The 'Root Disk Controller' dropdown should display the default option of 'osdefault' instead of a blank default option.

Go to the 'Register Template From URL' screen by clicking the 'Templates' tab on the lefthand side.
On the 'Templates' screen click the 'Add' button to display the  the 'Register Template From URL' screen.
On the 'Register Template From URL' screen, select the KVM option from the Hypervisor dropdown:

It incorrectly displays the 'Original XS Version is 6.1' checkbox. This checkbox should be hidden in the KVM context.
The 'Root Disk Controller' dropdown should display the default option of 'osdefault' instead of a blank default option.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

GitHub Issue/PRs

Screenshots (if appropriate):

How Has This Been Tested?
Manually. See the screenshot above.

Go to the 'Register Template From URL' screen by clicking the 'Templates' tab on the lefthand side.
On the 'Templates' screen click the 'Add' button to display the 'Register Template From URL' screen.
On the 'Register Template From URL' screen, select the KVM option from the Hypervisor dropdown:

It now correctly hides the 'Original XS Version is 6.1' checkbox. This checkbox is hidden in the KVM context.
The 'Root Disk Controller' dropdown now displays the default option of 'osdefault' instead of a blank default option.
CloudStack version 4.11, KVM hypervisor.

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
Testing
[ ] I have added tests to cover my changes.
[ ] All relevant new and existing integration tests have passed.
[ ] A full integration testsuite with all test that can run on my environment has passed.

@rhtyd @nvazquez @priyankparihar @borisstoyanov Please review