Materialize Select Dropdown Not Working

Just the regular single select dropdown is not working for me. I don't need a dynamic one, just the static one for now.

    <select>
      <option value="" disabled selected>Choose your option</option>
      <option value="1">Option 1</option>
      <option value="2">Option 2</option>
      <option value="3">Option 3</option>
    </select>
    Materialize Select

Other form elements like Text fields, including all input fields, Icon Prefixes, Textarea, they all work, but the single select dropdown is not working for me.
Any idea what I could be doing wrong or what's missing or what's causing this?
Thank you for your reply.
Kimberly

@kikithedeveloper see here the documentation on dropdown: http://materializecss.com/dropdown.html
You should be using a different element and styling for dropdowns. Here's sample code: https://github.com/InfomediaLtd/angular2-materialize/blob/master/sample/src/app/components/dropdown.ts

Drop Me!

one

two

three

<select>
  <option value="" disabled selected>Choose your option</option>
  <option value="1">Option 1</option>
  <option value="2">Option 2</option>
  <option value="3">Option 3</option>
</select>
Materialize Select

Hi @rubyboy Thanks for the sample code reference because it gave me more to try out. And I apologize that I wasn't clear.
What I am trying to accomplish is this Form's input single select dropdown.
Reference: https://github.com/InfomediaLtd/angular2-materialize/blob/master/sample/src/app/components/forms.ts
Sample code that I want to accomplish (single-select and multi-select):

              <select name="singleSelect" [(ngModel)]="selectedOption" name="selectedOption" materialize="material_select" [materializeSelectOptions]="selectOptions" [disabled]="isDisabled?true:null">
                <option value="" disabled selected>Choose your option</option>
                <option *ngFor="let option of selectOptions" [value]="option.value">{{option.name}}</option>
              </select>
              Materialize Select

              <select name="multiSelect" [(ngModel)]="selectedOptions" multiple materialize="material_select" [materializeSelectOptions]="selectOptions" [disabled]="isDisabled?true:null">
                <option value="" disabled selected>Choose your option</option>
                <option *ngFor="let option of selectOptions" [value]="option.value">{{option.name}}</option>
              </select>
              Materialize Multi Select

I had everything set up following the entire sample code file, including html, ts. I made sure to import MaterialDirective and be sure to include the attribute materialize in these elements.
Everything in the form work, except these two input select dropdown, single-select and multi-select. I noticed the code below.
    window.setTimeout(()=>{
      this.selectOptions = [
        {value:1,name:"Option 1"},
        {value:2,name:"Option 2"},
        {value:3,name:"Option 3"}
      ]
    },100);

I am not entirely sure if this is a bug or if something is missing.

@rubyboy I came across this issue and you noticed that there's no initial model selection. That's actually the problem for me. Everything works, except these two form input selection.
https://github.com/InfomediaLtd/angular2-materialize/issues/21#issuecomment-215095835

Ok........ So.......... This is kind of a bit of a mind scratcher........ I decided to play with the time and just increased it to 10000 ms. And it works...
    window.setTimeout(()=>{
      console.log("setTimeOut is completed.");
      this.selectOptions = [
        {value:1,name:"Option 1"},
        {value:2,name:"Option 2"},
        {value:3,name:"Option 3"}
      ]
    },10000);

So, I had three regular tabs. In first tab, the input select dropdown works. In the 2nd tab, the input select dropdown did not work. After I turned the tabs into tab-like nav with links to three children routes, all the dropdowns across different tabs work. I think it's because the ngOnInit only works for the components currently rendered and not for the hidden elements / components.

@kikithedeveloper is this issue still relevant? If it is, are you able to create a reproducible bug code? (repo or sample code of a component that reproduces the issue). Thanks.

Its working for me but its temporary hack
*.component.html

      <select formControlName="status" [(ngModel)]="selectedStatus" data-model="selectedStatus" class="select">
          <option [ngValue]="" disabled>Select</option>
          <option [ngValue]="1">Enable</option>
         <option [ngValue]="0">Disable</option>
     </select>
 Status

*.component.ts
ngAfterViewInit() {
        const self = this;
        jQuery(document).on('change', 'select', function(){
            var v = $(this).val().split(': '), model = $(this).attr('data-model');
            if(typeof v[1] != 'undefined') {
                self[model] = v[1];
            }
        });
 }

Hello!
I am having a similar problem with the option/select element.
My  elements are loaded in from an API, and there is therefore a short timelag before the *ngFor is populated.
The  however gets initialised before that, and the new elements are not loaded into it.
When I "hard code" the *ngFor array, everything works perfectly fine.
Is there a possibility to manually initialise the component, or any other workaround.
I would be incredibly greatful for any type of help.
All the Best! :)

@timeo-schmidt  We have solved problems like that with the  materializeSelectOptions directive
From the readme:

For dynamic select elements apply the materializeSelectOptions directive to trigger element updates when the options list changes

This below solved it form me
$(document).ready(function(){
$('select').not('.disabled').formSelect();
});

This below solved it form me
$(document).ready(function(){
$('select').not('.disabled').formSelect();
});

THANK YOU!

This below solved it form me
$(document).ready(function(){
$('select').not('.disabled').formSelect();
});

thank you

This below solved it form me
$(document).ready(function(){
$('select').not('.disabled').formSelect();
});

LOVE U <3

For anyone using Vue, here's a hack that worked for me. This is awfully painful especially with http requests. But the setTimeout() seems to work...

            <select id="country" v-model="country" @change="getCountries">
                  <option v-for="item in countries">{{ item }}</option>
            </select>
            Choose your country

async getCountries () {
     try {
          const res = await this.$http.get('/countries') as AxiosResponse;
          this.countries = res.data.response;
          setTimeout(() => {
                 (window as any).M.FormSelect.init(document.querySelectorAll("select"));
           }, 1000)
      } catch (e) {
           console.error(e);
    }
}

It seems as though, once FormSelect.init() is called, any changes made to model (select options) are ignored. So init needs to be called after all options are there.

Below codes solved my issues.
Index.html
under the script, please add the below codes.

Thanks..


WCAG 1.4.3: (EditingExaminerDemo/edit box text '' No exception edit box)[High Contrast 2] Contrast ratio failure for regular text

The following accessibility issue needs investigation.
App: EditingExaminerDemo
Element path: edit box text '' "No exception" edit box red text
Issue Details: Contrast ratio failure for regular text in High Contrast 2.
How To Fix: https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html
This accessibility issue was found using Accessibility Insights for Windows, a tool that helps debug and find accessibility issues earlier. Get more information and download this tool at https://aka.ms/AccessibilityInsights


Live transcription functionality

Added live transcription functionality and tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-communication-call-automation


Bump Testcontainers

investigating 403 on remote pull

com.github.dockerjava.api.exception.DockerClientException: Could not pull image: error parsing HTTP 403 response body: invalid character '<' looking for beginning of value

Hmpf https://status.quay.io/incidents/z7sbjqmb34p1

:+1:


Recommendation to align project type and data fields in ‘Exits’ endpoint with HUD Data Dictionary

Exits: Like the Enrollments endpoints, these Exits endpoints contain fields that represent a mix of federal funder required information, across HUD/CoC/ESG, VA/VASH/SSVF, SAMHSA/PATH and HHS/RHY. Since each project type requires different data to be collected at each data collection stage, we recommend a structure that ties the data required for each project type/data collection stage in a manner consistent with the Data Dictionary. We would like to further discuss possible solutions with the group.

Thanks @DavidTweedieWellSky. This is a part of a larger conversation that we're anticipating facilitating regarding data validation. If there are any outstanding concerns after that conversation, please feel free to flag here.


Tooltip widget

Now that we can use Overlays, how would one add a "tooltip widget"? As far as I understand to display an Overlay a widget needs to implement the overlay() function, but that means if I want to display a tooltip when I hover, say, a radio button I wouldn't be able to use iced's implementation, because I would need to implement the function myself (which I can't, since the trait is already implemented).
So I guess a way would be to wrap the iced radio button in a custom widget and implement the overlay() function so that it displays a tooltip when the radio button is hovered? Could also be made generic by making a Tooltip widget that takes any widget as content, and shows a tooltip over that content widget when it's being hovered? Would love to see something like this in.

Fixed by #465.


UI: hiding the project used for performing query jobs

This is a bit of a niche feature request, and I have implemented in #227 (but perhaps not optimally), wonder if others have a similar use case.
We have the following scenario:

Data to be queried is in project Y

The query jobs should be made in project Z

Grafana is running on a service account assigned to project X (or it is a user account, regardless, it is not related to Y/Z)

Grafana's SA has roles/bigquery.dataViewer  on certain datasets/tables within project Y and also resourcemanager.projects.get,  resourcemanager.projects.list on project Y

Grafana's SA has roles/bigquery.jobUser role on project Z

We would like the ability to hide project Z from the project-picker in the query builder UI, because it is an "internal" project that is only meant for billing & auditing purposes, it does not have any datasets that Grafana is permitted to query.
Other than the hiding, this all works currently by configuring project Z as the defaultProject in the jsonData. I would also argue from a documentation purpose, it is not entirely obvious that this project is used for creating the query jobs, even when the user selects another project via the query builder (though it is desirable in this particular use-case)

This is completed in https://github.com/grafana/google-bigquery-datasource/pull/239


CI: .github/workflows/ci-sage.yml: Update after move of Sage dev to GitHub

Summary of changes

Closes
Pull Request Checklist

[ ] Changes have tests
[ ] News fragment added in newsfragments/.
(See documentation for details)

dup of #4160


Rotation sensor bugfix

Fixes #17
TODO

[ ] Logic to detect every full rotation
[ ] Testing

ok turns out this is very simple. PROS has similar functionality already through the Rotation::get_position() function.


Add New IDP Property for Native Federation

Is your feature request related to a problem? Please describe.

In native federation, there is a need to track whether the given IDP should support native federation.

Describe the solution you would prefer

This is can be specified as an IDP property where the admin user can enable/ disable the native federation support for an IDP through the console.
This option can be added to the Advanced section of the IDP configuration page as follows (just like it is done for JIT  provisioning).

Additional context

Proposed name for the property: Supported for Native Federation

The proposed solution got changed as follows.

Instead of introducing a new IDP property, it was decided to merge Token Issuer Capability with IDPs.

Therefore, the new solution implementation will be tracked by a new issue.


Feat: [1148] - enrichment extension

Related Issue:
https://github.com/ocsf/ocsf-schema/issues/1148
Description of changes:
extending - enrichment by:
time, recommended - The timestamp when the enrichment data was generated.
desc optional - A long description of the enrichment data.
reputation optional - The reputation of the enrichment data
short_desc, recommended - A short description of the enrichment data.
url_string, recommended - The URL of the source of the enrichment data
Delete once you have confirmed the following:

Did you add a single line summary of changes to Unreleased section in the CHANGELOG.md file?
Have you followed the contribution guidelines?
Did you run a local instance of the ocsf-server and ensure it ran without any errors/warnings?
Is your PR title in sync with the description?

Note - ticket added to incident finding change log record pushed back.


Same here. Wish Stellar would allow to block fraudulent accounts and freeze the assets.

Hey,
Sorry for the long response. We are overwhelmed with similar support requests.
Several days in a row we've been working heads down to prevent further attack spread.
Here is a short post about what we are doing right now to prevent such attacks and help people recover their funds:
https://www.reddit.com/r/Stellar/comments/kij4hb/proactive_blocking_of_phishing_websites_with/
Please provide transaction details. I'll to review your transactions history and mark all attackers' accounts as #malicious. You'll need to contact your local law enforcement agency to fill up an official claim. I'll help you to track transactions all the way up to exchanges when scammers try to cash out funds. Without an official request from police exchanges won't share any details and won't block the accounts. This way, you have a decent chance to get your money back.
I'm afraid, this is all I can do for you at the moment.

I emailed you directly with all the details several days ago, 12-17-20, including transaction number and report I filed with ic3.
Sent from my iPhone

On Dec 22, 2020, at 10:16 PM, orbitlens<EMAIL_ADDRESS>wrote:

Closed #267.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

i got a response from you but i had already sent the info
phil absurd<EMAIL_ADDRESS>[image: Attachments]Thu, Dec 17, 2:46 PM (7 days ago)
to orbit.lens


Inspiration: Verifying CAS algorithms modulo lower levels

References:

What should Sage look like in Lean?
Verifying CAS algorithms modulo lower levels
Sage Demo

Combining this with the ideas in SampCert, cedar-spec, and SSA, we should be able to do 4 things for low level functionalities in one go:

call CAS for the results
have a theorem/axiom for expected property, via opaque/implemented_by maybe fit into a type class
generated the corresponding tests testing the property, with a test subject sampler
use verified codegen or MLIR techniques to generate production code for target language, which could be relying on CAS results.

P.S. An alternative to GiNaC for this idea is gTybalt which is also based on GiNaC (noticed because of AN EXAMPLE OF CLIFFORD ALGEBRAS CALCULATIONS WITH GiNaC).

A smaller scale of experiment is to rewrite kingdon's symbolic capabilities in GiNaC, to check if it could be a drop-in replacement.


pypy3 compatibility

There was an issue in from_ascii which when trying to decode base64 on unicode data caused:
Traceback (most recent call last):
  File "test.py", line 1, in <module>
    import ed25519
  File "/Users/miki725/.virtualenvs/pypy3ed25519/site-packages/ed25519/__init__.py", line 1, in <module>
    from .keys import (BadSignatureError, BadPrefixError,
  File "/Users/miki725/.virtualenvs/pypy3ed25519/site-packages/ed25519/keys.py", line 191, in <module>
    selftest()
  File "/Users/miki725/.virtualenvs/pypy3ed25519/site-packages/ed25519/keys.py", line 183, in selftest
    prefix="priv0-", encoding="base64")
  File "/Users/miki725/.virtualenvs/pypy3ed25519/site-packages/ed25519/keys.py", line 82, in __init__
    sk_s = from_ascii(sk_s, encoding=encoding)
  File "/Users/miki725/.virtualenvs/pypy3ed25519/site-packages/ed25519/keys.py", line 64, in from_ascii
    s_bytes = base64.b64decode(s_ascii)
  File "/usr/local/Cellar/pypy3/2.4.0/libexec/lib-python/3/base64.py", line 83, in b64decode
    raise TypeError("expected bytes, not %s" % s.__class__.__name__)
TypeError: expected bytes, not str

https://github.com/warner/python-ed25519/commit/b7f418d6d5346cf9e87e3f9182e4b53252b834a3 addresses that.
also this PR includes flake8 fixes in https://github.com/warner/python-ed25519/commit/3c6d4f8656263c226e2058a6d58c6ad491d4f963 (using auto-formatter). If you prefer to merge without flake8, let me know and can submit separate PR fixing flake8.

Oh, good catch!
Yeah, could you file a separate PR for the flake8 changes? Also, versioneer.py is copied from upstream (https://github.com/warner/python-versioneer), so the new PR should probably omit changes to that file, and we should add a Versioneer issue to get it fully flake8-clean (I thought it was already, but maybe I'm testing with an old version of flake8).
thanks!

ok. removed flake8 commit. Ill submit another PR with those changes and will omit them from versioneer.py. thanks

Sorry that took me a while to land: I just now noticed that this PR only had the pypy3 changes and not the versioneer.py ones too. I updated the tests to be pypy3-compatible too. Thanks!

@warner no problem. thanks for merging!


DCVC models are not available now.

The Onedrive link seems to break down now.

I can access the link via the VPN. But you can download it from the backup link: https://pan.baidu.com/s/1_hMdtdMVWbIeyQnWFzYEcQ 提取码: g6hw

Thank you!


Introduces NativeEngineKNNQuery which executes ANN on rewrite

Description
All integration tests are passing. Cannot support radial currently since k is not significant, there are ways to do it but since its not planned for 2.17 this should work
Related Issues
Resolves #1845

Check List

[x] New functionality includes testing.
[x] New functionality has been documented.
[ ] API changes companion pull request created.
[x] Commits are signed per the DCO using --signoff.
[ ] Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@shatejas do you think it doesnt need changelog?

@shatejas do you think it doesnt need changelog?

Wasn't planning on adding it. Doesn't seem to be significant enough for users to make it to change log

Please make the change in changelog.md file

Please make the change in changelog.md file

https://github.com/opensearch-project/k-NN/pull/1877#issuecomment-2264201750

@shatejas do you think it doesnt need changelog?

Wasn't planning on adding it. Doesn't seem to be significant enough for users to make it to change log

I think we should put a change log.

@shatejas please resolve conflicts.


Initial metric exporter implementation

Why
Export metrics.
What
Simple implementation of metrics exporter:

No buffering/batching before sending
Sync send
SignalFxReporter and its dependencies e.g WebRequestor, WebRequestorFactory migrated from dotnet lambda wrapper repository (I plan to simplify that part of the code)
Gauge being the only metric type exported for now

Tests
Automated test for SignalFxMetricSender.
Smoke tests with backend.

Do you see any reasonable way to avoid manual code modification under Vendored folder?
It will be overwritten if you execute nuke UpdateVendoredCode task.

Smoke tests with backend.

I would love to have a hyperlink and info what was tested - even for sake of knowledge-sharing 😉

Do you see any reasonable way to avoid manual code modification under Vendored folder? It will be overwritten if you execute nuke UpdateVendoredCode task.

I looked into it, I think it might be reduced (sometimes at the cost of readability imo) but not sure if avoided.

Smoke tests with backend.

I would love to have a hyperlink and info what/how it was tested - even for sake of knowledge-sharing 😉

Added

Do you see any reasonable way to avoid manual code modification under Vendored folder? It will be overwritten if you execute nuke UpdateVendoredCode task.

I looked at it and I do not see any easy way without introducing a lot of complexity. I suggest waiting to see if it would be an issue. Then we may tackle it with more insight what are the potential conflicts and other problems.

Updated not to modify vendored code


merge package from arlac77/npm-package-template-esm-only

.travis.yml

chore(travis): remove node versions 12.3.0
chore(travis): add node versions -10,-11,-12,12.3.1

Coverage remained the same at 70.486% when pulling 7e772b99f4b8f79640b1cdb090d25161b4824045 on npm-template-sync-1 into 71eb3daa10abf005937e10f7d22f499bad9a0c37 on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Simplify unscheduling

Hi there,
I'd like to open a PR for this, but I wanted to double check with you first if you think it makes sense.
We use zrangebyscore to look for the job in the schedule sorted set. That operation has a complexity of:

O(log(N)+M) with N being the number of elements in the sorted set and M the number of elements being returned. If M is constant (e.g. always asking for the first 10 elements with LIMIT), you can consider it O(log(N)).

After that weuse zrem with a complexity of:

O(M*log(N)) with N being the number of elements in the sorted set and M the number of elements to be removed.

Since we're removing 1 element, it becomes O(log(N)).
We look for the job in the schedule set to know if we can remove it, but zrem returns the number of removed elements, so we could use that to decide if the element was there and just delete it. Is that right?
I have a use case where we have quite a few scheduled jobs that I need to unschedule sometimes, and if I didn't need to keep track of the timestamp it would simplify things a bit.

I started to implement this and quickly realized that the schedule set has serialized jobs, so the theory is impossible. Sorry for the trouble!

Thanks for your concern :)


freebsd kinfo_kstat/sigtramp additions

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 6fe55348a1b166bce8a62c67309379b2f75e686e has been approved by Amanieu

:hourglass: Testing commit 6fe55348a1b166bce8a62c67309379b2f75e686e with merge f0b6039ef8d9def9dde671a71c44c40eee5cfb36...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit e29e6427fc60d19633bccd3a2c58bdaa33351162 has been approved by Amanieu

Wait, this isn't the right cfg. It seems that we don't have one for this specific feature. Basically in 1.47 most traits were updated to be implemented for arrays of any length. Add a new cfg in build.rs for this.

@bors r+

:pushpin: Commit 4b61ce8ea955a5786cddbd4155f898008b874795 has been approved by Amanieu

:hourglass: Testing commit 4b61ce8ea955a5786cddbd4155f898008b874795 with merge 67f4cde3ed121dd75509a2aee3a401da16ca969d...

:broken_heart: Test failed - checks-cirrus-freebsd-11

not sure FreeBSD 11 still exist https://pkg.freebsd.org/

Yes, see #2779.

@bors retry

:hourglass: Testing commit 4b61ce8ea955a5786cddbd4155f898008b874795 with merge 5758b11431c2f420d5cec1971e5f5d6f2fce2b72...

:broken_heart: Test failed - checks-actions

To revive the logs, @bors try

:hourglass: Trying commit 4b61ce8ea955a5786cddbd4155f898008b874795 with merge 0297a340a0602503726c30cd1b12a91885678b61...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit 1d20fd1cc7c5c4b2bd9e2ca5c7de1eb906e3feba has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 1d20fd1cc7c5c4b2bd9e2ca5c7de1eb906e3feba with merge b11d46709346ce706c0c2170bbaded7c104416d5...

:broken_heart: Test failed - checks-actions

:umbrella: The latest upstream changes (presumably #3101) made this pull request unmergeable. Please resolve the merge conflicts.

@devnexen Are you still working on this?

@devnexen Are you still working on this?

No I do not think so.


Linkedin stopped working with Gif Delayer installed

The new Linkedin design stopped working with Gif Delayer installed. The only thing I see is a splash screen with endless loading indicator. There are no error messages in the console.
Gif Delayer is the only extension that impacts Linkedin. Once it's turned off, Linkedin loads fine.

I've also noticed this issue and similar issues that break entire sites caused by Gif Delayer. While it may be too much to ask to have him keep up with every single case of a .gif being used, I've submitted a pull request that adds a whitelist, allowing us to simply disable the plugin on non-functioning sites!


ARROW-6485: [Format][C++] Support the format of a COO sparse tensor that manages its indices in separated vectors

I'd like to add matrix-specialized COO sparse tensor format with split indices.
It improves the interoperability among scipy because of reducing the copies of index arrays.

Hey @mrkn - sorry I didn't have capacity to reply for a while.
If I remember correctly only SciPy has this architecture of COO index having two vectors instead of one 2D matrix.
Question: could we handle this as a special case of COO tensor rather than a new type? Could we serialize (row, col) data as a single row major tensor of COO type and only deserialize it into the SciPy layout if desired? (I'm asking because I'm not sure if such approach is feasible)
If we go for a new type - could I propose a name SparseCOOMatrix (as opposed to n-dimensional SparseCOOTensor). It could perhaps be shortened to COOM?

Hey @mrkn - sorry I didn't have capacity to reply for a while.

No problem. Thank you for your cooperation!

If I remember correctly only SciPy has this architecture of COO index having two vectors instead of one 2D matrix.

Not only scipy, but also SuiteSparse employs the split format.

Question: could we handle this as a special case of COO tensor rather than a new type? Could we serialize (row, col) data as a single row major tensor of COO type and only deserialize it into the SciPy layout if desired? (I'm asking because I'm not sure if such approach is feasible)

Although we can handle the split-format as an internal variation of SparseCOOIndex, we still need to introduce the new flatbuffer type.

If we go for a new type - could I propose a name SparseCOOMatrix (as opposed to n-dimensional SparseCOOTensor). It could perhaps be shortened to COOM?

The implementation in this pull-request can handle more than 2-dimension.

If we go for a new type - could I propose a name SparseCOOMatrix (as opposed to n-dimensional SparseCOOTensor). It could perhaps be shortened to COOM?

The implementation in this pull-request can handle more than 2-dimension.

Oh, I forgot to change the title of this pull-request. Sorry.

Not only scipy, but also SuiteSparse employs the split format.

I didn't realize, Then we should indeed have proper support for this option.

Question: could we handle this as a special case of COO tensor rather than a new type? Could we serialize (row, col) data as a single row major tensor of COO type and only deserialize it into the SciPy layout if desired? (I'm asking because I'm not sure if such approach is feasible)

Although we can handle the split-format as an internal variation of SparseCOOIndex, we still need to introduce the new flatbuffer type.

Could we use the original COO flatbuffer type by 'concatenating' vectors when serializing? Concatenated vectors would effectively be like a row-major 2D tensor when serialized. Again - I'm not sure this is feasible with flatbuffers or desirable that's why I ask. The reason I'm interested is that we could avoid introducing another format.

If we go for a new type - could I propose a name SparseCOOMatrix (as opposed to n-dimensional SparseCOOTensor). It could perhaps be shortened to COOM?

The implementation in this pull-request can handle more than 2-dimension.

Oh I see. In case we introduce a new format - your proposal was SplitCOO - could we shorten it to SCO to keep naming style?
Just thinking out loud: we could also call this format coordinate list - COL (wikipedia)?
Or keep COO for vector-style and call tensor style COT (coordinate tensor).

@mrkn @rok what is the status of this PR?

@emkornfield Presumably this need to fix for the canonical flag added in #7477.  I can do this next week.

I couldn't begin to work this pull-request last week. But I've started to do it today. I guess I can finish this by this weekend.

@mrkn @rok This PR hasn't had any activity for a long time, and there are conflicts. Should it just be closed?

@mrkn I can try to complete this sometime next week. Can you authorise me on this branch?

@rok What can I do to authorize you on this branch?

@rok What can I do to authorize you on this branch?

Sorry I mean if you could add me as a collaborator on your fork so I can push changes to this branch.


Add job to load the current yaml configuration into a config map.

Details
This closes #172. Instead of a script that the user must run manually and the other manual steps to run, this PR makes the process automatically.
It does 3 changes:

Adds jq and curl to the current Docker image.
Adds the script update-config-map.sh, this is the script that does all the job.
Adds a job that runs once the previous script. Using jq and curl gets the current configMap, injects into it the current yaml app_config.yaml file, and puts its back into the cluster.

This job could be re-runed manually to get again the default configuration.
Closing issues
Closes #172

Somehow the CI pipeline is not built when trying to merge forks. I will merge this now, hoping for the best :-)


Question: dev-container image with the latest current commits

I just wanted to ask, if there were any plans to release nightly builds of the Deconz image?
So that all peoples could use it before the release if they want some a new features. Since, for example, the situation with Opple Aqara switches is very sad right now, I just get it two switches, but cannot be used until the next official release of the container. I really want to.  :)
Maybe you can build some nightly pre-release container?
It's just question guys, just interesting about this dirrection. Thanks anyway!

This is probably the wrong address to ask this.
If you take a look at the Dockerfile it has to use the build submitted by dresden elektronik. So you should ask them if they would submit a nightly build that could be then used by this docker image.


Fix comparisons with NAN

Attempt to fix #302
What a wonderful bug we found.
I'll start from afar and  take the function Assert::greaterThan($value, $limit) as an example.
The asserted condition is literally described in PHP as follows:
 $value > $limit

And when we need to describe opposite condition in which our assertion must throw an exception there are at least two ways:

!($value > $limit) (literal)
$value <= $limit (simple)

In the first case, the condition is described literally as the logical negation of the assertion.
In the second case, the same conditions is described, but in a more readable form using only one operand.
Its a common practice to avoid negative conditions for better readability.
So it is not surprising that many methods in this library use the second one.
Unfortunately this doesn't work with NAN.
In normal cases both form give the same result:
!($value > $limit) === $value <= $limit # true

But it doesn't work that way for NAN.
Any comparison with NAN will return false (except != and !==).
And our forms of negative condition now return different result:
!(false) === false # false

In addition to functions mentioned in issue I found 9 more assertions that lead to unexpected results when passing NAN.
I added additional test cases for those method in this PR.
Solutions
Straightforward one.
Just change the form of the negative condition from literal to simple.
This is the solution I described in this PR.
Another solution is to left simple condition but add additional checks for NAN for each of arguments.
Method to check for NAN:
protected static function isNaN($value): bool
{
    return is_float($value) && is_nan($value);
}

And the condition for Assert::greaterThan function will be:
if ($value <= $limit || self::isNaN($value) || self::isNaN($limit)) {
    static::reportInvalidArgument(\sprintf(
        $message ?: 'Expected a value greater than %2$s. Got: %s',
        static::valueToString($value),
        static::valueToString($limit)
    ));
}

This is a more readable but verbose method.
I like the second solution more. To reduce verbosity we can change check-method signature to isNaN(...$values)  or atLeastOneIsNaN(...$values)

@gordinskiy thank you for the additional explanation, it is very helpful to understand the context and other approaches. I do not want to introduce an isNaN function, but would rather see it be an assertion by itself. This would be more consistent with other assertion methods:
self::assertNumeric($value);
self::assertNumeric($limit);

if ($value <= $limit) {
    static::reportInvalidArgument(\sprintf(
        $message ?: 'Expected a value greater than %2$s. Got: %s',
        static::valueToString($value),
        static::valueToString($limit)
    ));
}

@shadowhand My first solution was similar but I abandoned it due to the difficulties with customizing messages from nested assert (maybe it's just not necessary).
The problem with assert::Numeric is that NAN is a float and it will pass this assertion.
We can add one more assertion for these cases - assert::notNaN
I had thoughts about adding an assertion assert::number.
But there is one more magic float constant - INF, its not a number, but can be used in comparisons and already work as expected.

@gordinskiy I think numeric assertion needs to be fixed, too:
is_numeric($value) && ! is_nan($value)

@shadowhand

updated ::numeric assertion and tests for it
returned 'simple' condition negation and add numeric assertion for methods that was updated in this PR
some of those methods besides numeric values could compare dates - added test cases with dates for these methods and type checks before calling numeric assertion.


Refactor code ahead of ICRA demo

This PR does a number of housekeeping tasks for this project:

rewrites the obstacles in a json file that can be used by all clients as a single point of truth for the environment
introduces a go mod and updates the visualization code
refactors the code revolving around buttons and movement for maintainability

Just tested on the physical claw, everything is working as intended.

[q] @mcvella will the demo ever use the main-simple.ts file?


Add idiot

Really wanted to add a CWed subject to test out the feature in production, I think this one is mild enough, hope you agree :3

updated with a different word that may be more fitting

omfg I borked this pull request, sorry ahhaha I'm going to create a new one xd


Publish nuget package

Hi,
I'm very interested to begin to use it with asp.net 5 beta5.
Pls, can you publish as nuget package i.e. https://www.nuget.org/packages/Swashbuckle/6.0.0-beta2
Thanks!

It's top of my priority list! I just need to carve out hours to do it - hopefully this weekend

Beta2 released!

:fireworks:


Add recursive idb support

This PR adds support for a new syntax: a do-until-convergence loop containing a list of special MyriaL statements. The loop terminates when there will be no update to any relation. Examples are those newly added optimizer tests.

I expect myself adding some more checks to limit what can be put inside of the do-until-convergence loop, but would like to get the main changes being reviewed first.
For 059673c, I'm not sure if it's the best design. I would like to add a MIN aggregate that takes a list of column indices to compare two tuples in that order, however the current MIN is a binary expression. I added a new aggregate called MULTIMIN instead with less support (e.g. fakedb) than MIN, but maybe extending MIN to an nary expression is another option? Would like to hear your thought.

Coverage decreased (-0.2%) to 91.822% when pulling 22f8ec9bec9b4b0f4c8d9d15588eb14a97d7626b on add_recursive_idb_support into<PHONE_NUMBER>5ebeeed48c975f6a2c341a97b8f116 on master.

Coverage decreased (-0.06%) to 91.898% when pulling d86a4b0482a8e505ea5764e21e73b70abd9f966e on add_recursive_idb_support into 6d75be5d6b3d5bc0a490428bb2938c67039b7330 on master.

I've addressed most comments except for a few pending discussions:

The Zeroary MyriaConsumer for breaking infinite optimization
MIN vs. MULTIMIN and should they use named attribute (and what if we don't know the name)
Join pull order: global or within do-until-convergence only, where to specify

We can discuss them in person if necessary.

Coverage decreased (-0.06%) to 91.898% when pulling da94a7f717c219aa087ba47d96fe4bd8061f299c on add_recursive_idb_support into 6d75be5d6b3d5bc0a490428bb2938c67039b7330 on master.

Coverage decreased (-0.1%) to 91.839% when pulling 81e9e1ed13a47f4218c4bb8008acc9e697d9902d on add_recursive_idb_support into 6d75be5d6b3d5bc0a490428bb2938c67039b7330 on master.

Coverage decreased (-0.05%) to 91.912% when pulling 718157d9cc4d256d3145d33298ea0d324d28e0dc on add_recursive_idb_support into 6d75be5d6b3d5bc0a490428bb2938c67039b7330 on master.

Coverage decreased (-0.05%) to 91.917% when pulling cca8d107132f4df189a3ac5f9c28c0a0367a4d74 on add_recursive_idb_support into 6d75be5d6b3d5bc0a490428bb2938c67039b7330 on master.

Coverage decreased (-0.05%) to 91.917% when pulling 7f0716211eb421c2c2772d88258b40bf9cab35ab on add_recursive_idb_support into 6d75be5d6b3d5bc0a490428bb2938c67039b7330 on master.

Goes with https://github.com/uwescience/myria/pull/877.


Add Chinese (Simplified) Translate by MerakW

This translation is translated by myself, if you have any questions, comments are welcomed.

个人拙见，既然是我们自己看的，可以翻译的简单一些，比如'您已成功准备'，‘您已"取消"准备’，'比赛恢复'，'取消暂停'之类的。
另外，你的文件名是错误的。可以直接改成zh.json

其实也可以自己增加颜色来更醒目，例如
您已{green}准备{default}！
您已{red}取消准备{default}！
我不知道前面颜色是否可以自行更改，毕竟我也不会这语言。
To Author or maintainer:
Is it possible to change the colour code to a specific colour at will?  Support for Hex?

个人拙见，既然是我们自己看的，可以翻译的简单一些，比如'您已成功准备'，‘您已"取消"准备’，'比赛恢复'，'取消暂停'之类的。 另外，你的文件名是错误的。可以直接改成zh.json

翻译确实言之有理，但是我个人翻译的时候还是觉得需要保持原意是最合理的，不去打破原本的内容
至于文件名，zh-cn（中国大陆中文）确实有误，现在应该用zh-hans，代表中文简体中文。

文件名依旧不对。它是RFC 4646格式，所以后一个单词要大写，比如zh-Hans

Hey, thanks for the PR!
As @JammyLin, should the file name be zh-Hans.json?

I'm really sorry that I didn't submit my changes until today, I was so busy a while ago that I didn't pay attention to the Github content. @shobhit-pathak

To be honest, I don't really understand whether it needs to be reviewed by others or by the maintainer, at least I think the translation is pretty good.
Then I checked the code, is it possible to internationalise all strings later? It looks like it's possible.

@JammyLin I agree with your opinion about other strings, there is still a lot strings didn't translated.

Hey!
Yes there's still a lot of strings present for which translation is needed. The idea was to set-up the base of translation with some strings. I'll soon release an update in which I'll try to cover the remaining strings so that we have complete translation available.
Thanks!

It means my pr will be merged after full translate right? @shobhit-pathak

Merged it, thanks for the translations! :D

I'm happy to contribute to such a great open source project!

Merged it, thanks for the translations! :D


Support for cloud mode in Google Analytics 4

Description of the change
Updated doc to accommodate cloud mode details
Type of change

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

Related issues

Fix #1

Checklists
Development

[ ] Lint rules pass locally
[ ] The code changed/added as part of this pull request has been covered with tests
[ ] All tests related to the changed code pass in development

Code review

[ ]  This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
[ ] "Ready for review" label attached to the PR and reviewers mentioned in a comment
[ ] Changes have been reviewed by at least one other engineer
[ ] Issue from task tracker has a link to this pull request

Can we create a complete mapping table for all the properties so that user don't have to visit ga4 api docs
@akashrpo


[reddit] Basic bypass for TLS fingerprinting

Reddit seems to be now employing TLS fingerprinting to block requests #1014. This patch fixes it. However, I am not sure what impact this will have on other websites. Input from someone more well-versed in this matter will be appreciated

It might break some legacy websites that use weaker ciphers.


Image path is error after run build and version is 3.0.0-rc.10

What problem does this feature solve?
Image path error after packaging. What do I need to do that modify path in the config?

What does the proposed API look like?
The background path is right after run build

Use the proper bug report format please.


Dataset hosting

Can you please host the data set on something other then baidu,  I cant get it to download the site is so slow

You can use the download script "download_ffhq_uv.py". It downloads the datasets from AWS CouldFront.
Refer to README for the commands.


Add files via upload

First draft

We don't have the PR template setup in this repository yet but can you provide more details in the PR description and title

I'm still not sure what this pull request is for. The specification is in there along with an example implementation and project setup. Am I reviewing everything? It seems like there are still commits happening.


Fix missing interpolation context for array-based tweens

This PR changes

Nothing, it's a bug fix

Calling generateData() would fail with an error.

Thank you for your PR! Today I released Phaser CE (Community Edition). This is my way of opening up Phaser 2 to the community, allowing you to control features and updates directly. Please see the README in the v2-community folder of the repo for more details about this change.
If you could please re-submit your PR against the new Phaser CE version then I will merge it immediately :) Note that PRs now go against the master branch, and don't forget to add your change to the README too!


Allow multiple brands and add Unbranded utility

fixes #87
I found UnionToIntersection type in keyof.ts and decided to just copy it in brand.ts. Should it imports type for code deduplication?

I will review the PR next week.

I have now checked your code. We can extend the Brand type so that brand can be applied multiple times. However, currently I would not add Brands and Unbranded as it complicates Valibot's source code and testing and I don't quite understand the benefit yet. I have not found any issue or PR at Zod in this regard. So I assume that this feature is rarely needed. If you disagree here, please let me know.


Label repeat

Refer to https://github.com/tangrams/tangram/pull/222

reviewing!

Can we close this in favor of #465?

Closing in favor or rebased version.


docs: Add tmux_3_4 feature to README

I noticed that tmux 3.4 support was added in version 0.3.2, this updates the README to list it (along with all of the other features / version combos).

Of course, thank you!


Add Nepali Locale Support to CircuitVerse

This pull request introduces support for the Nepali language on the CircuitVerse platform. By adding Nepali translations, we aim to improve the user experience for our Nepali-speaking users and promote diversity within our community.
Changes:
Added Nepali locale files (np.yml) for interface translations.
Updated I18n_support files to include Nepali as an option.
Benefits:
Enhances accessibility for computer and electronics engineers in Nepal.
Supports CircuitVerse's commitment to diversity and inclusivity.
Notes:
Translations are accurate, as I am a native speaker with a strong command of the Nepali language.
Feedback and suggestions for improvement are welcome.
Screenshots:

Summary by CodeRabbit

New Features

Added support for the Nepali language across various application components, enhancing accessibility for Nepali-speaking users.
Introduced localization strings for user interfaces, forms, and notifications in Nepali.

Improvements

Expanded internationalization capabilities by including Nepali as an available locale.
Enhanced user experience with localized content for assignments, announcements, projects, groups, and more.

These updates aim to provide a more inclusive experience for users who prefer interacting with the application in their native language.

Looks good !
@Darshan808 great job.
btw CI has some issue, after fixing that I will merge it.

Nepali language code is ne, not np, right ? np is the country code, right ?

Coderabbitai identified some typos, which have been corrected in my latest commit.

@tachyons @tanmoysrt
Whenever you have the time, could you kindly review this PR? I would really appreciate your feedback, as I’ve put a lot of effort into it and am excited to see our Language being integrated into CircuitVerse through my contribution.


Fix wrong name in subrepl issue

Template quotes need a name defined in the reader to work. The LisspREPL always assumed 'main', but could have been embedded in some other module, so this assumption was wrong. Now assumes 'name' (all modules have this, or they're broken), and falls back to 'main' in case it was started with an empty namespace.

Looked through the flake8 output this time. Some of the flake8 warnings are just conflicts with black. It's also not respecting the fmt comments. It's also complaining about some import statements that are not at the top, but those need to be where they are. I've apparently been ignoring these for a while because what's left is useless, but that did allow one real issue to sneak through, which I just fixed. I should look into configuring this better.


chore(package<EMAIL_ADDRESS><EMAIL_ADDRESS>devDependencies

Summary of Changes

Updates Angular2 to v2.0.0 and AngularFire2 to v2.0.0-beta.5
Adds @types/request devDependency required for<EMAIL_ADDRESS>Fixes auth.service.spec to use TestBed.configureTestingModule instead of addProviders (deprecated)
Updates various devDependencies

Notes

<EMAIL_ADDRESS>upgrade causes non-breaking build  #warning. see issue #96
firebase can be updated to 3.4.0
istanbul-instrumenter-loader can be updated to 1.0.0 but has breaking changes I haven't yet figured out

Basic Checks

[x] Tests pass locally
[x] Prod build succeeds
[x] Prod build verified in browser

There we go! Build passing. :) Let me know what you think of these changes.

Requested changes pushed 😄

Awesome! Thanks very much 🌟 💎 ✨ @sbolel 🌟 💎 ✨

You're the real hero @r-park I'm glad I can help!


Roll engine<PHONE_NUMBER>6c..87edd94e9cc7 (4 commits)

https://github.com/flutter/engine/compare/60314077846c...87edd94e9cc7
git log<PHONE_NUMBER>6c123f45c5aaef911c5ea48343d569..87edd94e9cc751a0de72c0828d41793b9f740062 --no-merges --oneline
87edd94e9 Add read-only persistent cache (flutter/engine#8049)
4c9404950 Move android_sdk_downloader so I can more easily deprecate it (flutter/engine#8084)
7cbd9d8b4 Roll src/third_party/skia 3d1b941f3a7d..bea1f94f341e (7 commits) (flutter/engine#8083)
260669c65 Fix deleting text when the last character is some special characters on IOS (flutter/engine#7982)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (mklim@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


nit: Add ListResourceTemplates to ClientRequest / ServerResult in schema.ts

Based on my understanding of the specs, it seems that those values were forgotten in the ClientRequest  / ServerResult type.
Motivation and Context
This change aligns schema.ts with the description of the specs found in https://spec.modelcontextprotocol.io/specification/server/resources/
How Has This Been Tested?
NA
Breaking Changes
Possibly breaking Typescript compilation for developers referencing ClientRequest  / ServerResult. Still mostly a bug fix.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation update

Checklist

[x] I have read the MCP Documentation
[x] My code follows the repository's style guidelines
[x] New and existing tests pass locally
[ ] I have added appropriate error handling
[x] I have added or updated documentation as needed

Ah yes I'll do

Side question: do you think there's a need to clarify the results for SubscribeRequest and UnsubscribeRequest ? Maybe just as a comment that they map to EmptyResult (my understanding) ?
There is no SubscribeResult / UnsubscribeResult and I didn't the the response described in https://spec.modelcontextprotocol.io/specification/server/resources/#subscriptions either

Side question: do you think there's a need to clarify the results for SubscribeRequest and UnsubscribeRequest ? Maybe just as a comment that they map to EmptyResult (my understanding) ?
There is no SubscribeResult / UnsubscribeResult and I didn't the the response described in https://spec.modelcontextprotocol.io/specification/server/resources/#subscriptions either

This might also be an oversight on our end.


Missing documentation?

Hello,
your Project seems intressting to me but i dont know how to use it?
Can you please create a documentation where we have some examples in place. I currently dont understand how to create Wallets for my users or how to get things setup Witz the current doc.
Thanks

Hi
Sure it would be nice to have docs, but I don't have time to work on them.
To attach Wallet to User model you need some proxy like
from django.contrib.auth.models import User
from cc.models import Wallet

class Proxy(models.Model):
    user = models.OneToOneField(User, on_delete=models.CASCADE)
    wallet = models.OneToOneField(Wallet, on_delete=models.CASCADE)

Or substituting a custom User model
You can find more examples in Django docs https://docs.djangoproject.com/en/2.2/topics/auth/customizing/#extending-the-existing-user-model
Also I have an old project https://github.com/limpbrains/django-cc-wallet
It is an attempt to create UI for django-cc
You can take a look at it.
It is outdated and I'm not maintaining it! But you can look at the source code, probably it will help.
Cheers


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.96

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.96


Window functions on distribution col now supported

Update https://docs.citusdata.com/en/v7.0/reference/sql_workarounds.html#data-warehousing-queries and anywhere else they are mentioned

Actually I'm moving this back to the "Next Up" column after looking into it. I'd like to actually see this feature working so I can definitively update the section with "this works, but this doesn't." Ultimately it's an a section trying to show how to use a temp table to work around lack of sql support. So I'll still want an example of the window function failing, but failing on a non-distribution column.

I tried this feature again from Citus built off master (at 9a04b789). Verified that the extension reports itself as 7.1-3 in my local db. Using the schema and data from the RT analytics tutorial I tried a window function.
SELECT
    repo_id,
    count(*) OVER (PARTITION BY user_id)
FROM
    github_events;

I thought it would work according to https://github.com/citusdata/citus/pull/1668 because user_id is the distribution column of github_events. Instead it says:
ERROR:  0A000: could not run distributed query with window functions
HINT:  Consider using an equality filter on the distributed table's partition column.
LOCATION:  ErrorIfQueryNotSupported, multi_logical_planner.c:1856

@furkansahin did I make a mistake in my query or misunderstand the feature in your pull request?

The PR I opened implements the window function support for only SUBQUERY PUSHDOWN and INSERT INTO SELECT. Thus, your query should be
SELECT
    *
FROM
    (SELECT
         repo_id,
         count(*) OVER (PARTITION BY user_id)
     FROM
         github_events
    ) foo;

When I try this query in Citus master branch, it gives me the results.


Article contribution 17/01

@sjoelund Please review and merge such that I can continue w/o conflicts tomorrow. Thanks.

Looked fine. I just pushed one commit on top of it because I spotted some awkward language (not edited by you, but in a line edited by you).

@tbeu I just had a quick look through the changes using my phone at Mumbai airport. Please add your text before Thursday 4pm, I want to do a final editing before the deadline and I also might not agree with all your suggestions and would like the possibility to check them properly.


Robots

@kfranqueiro can you make sure this has some sort of robots that means it isn't crawled by search engines?

Because we're hosting this from w3c.github.io/wai-conformance-model-test/, this would need to be added to the w3c.github.io repository because robots.txt needs to be top-level. It looks like we don't have any in that repo; would we want to block AI bots across w3c.github.io/* sites or only this one?
The alternative is having this set up on its own domain, but I don't know how much effort that would be to set up.


HOCS-2457 add Spring config to allow Swagger service on casework

This ticket adds a Swagger service to casework giving us access to all the exposed api endpoints published by the casework service.
The Swagger page is available at http://localhost:8082/swagger-ui.html

Spring profile switching is now added. The profile is 'swagger' and can be added as an env variable or as a -D JVM command line option. So without the 'swagger' profile there will be no swagger endpoints available.


Automated Tests for the Project

Automated Tests for the Project have been completed.

Automated Tests for the Project have been completed.


prepare_transaction needs the key object

Hi. as I read in bitsv documentation I need to call the prepare transaction when I'm online to prepare a transaction and then I can sign this transaction offline. logically the prepare_tranaction function shouldn't need the key object to work. but when I run the tx_data = PrivateKey.prepare_transaction(address=sender.address, outputs=[(receiver.address, amountToSpend , 'bsv')]) I get this error :
TypeError: prepare_transaction() missing 1 required positional argument: 'self'
I checked the wallet.py file of bitsv and recognized that prepare_transaction isn't a @classmethod while it should be!

Ah yes. Sounds about right. Thanks for the concise report.
Will patch this when I get a moment. 😉

Will this do okay? I had to change the function signature to to add the 'network' positional arg... so this will technically be a breaking change but I'm not aware of too many people using this functionality...

Cut new release now. Will close this issue. LMK though of any issues and can reopen as needed.


Url macro

URL interpolater that fails compilation when provided string is not a valid URL.

Codecov Report

Merging #951 (74a06c2) into main (21cdee6) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #951      +/-   ##
==========================================
- Coverage   53.93%   53.91%   -0.03%
==========================================
  Files          73       74       +1
  Lines        2171     2172       +1
  Branches       59       66       +7
==========================================
  Hits         1171     1171
- Misses       1000     1001       +1

Impacted Files
Coverage Δ

...o-http/src/main/scala/zhttp/http/url/package.scala
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

based on today agreement, the PR is closed.


Cesium not installing on the TI-84 Plus CE Python Edition

**Firmware version: ** <IP_ADDRESS>
I decided to install a few games on my new TI-84 Plus CE (Python) calculator today and install Cesium, as it said to do because TI disabled Asm apps and people said Cesium was working- only for I to find out that Cesium doesn't show up in the apps list.
I restarted my calculator, unplugged it, etc. Transferred it from TI Connect CE.
Am I doing something wrong or is my brain just too flat?

Closed, forgot to isntall artiface. Woops!


Refactor functions into an autoload file

Startup times before:
[...]
243.202  032.647  032.647: sourcing /home/clausseno/.vim/bundle/browserlink.vim/plugin/browserlink.vim
[...]
405.791  000.009: --- VIM STARTED ---

After:
[...]
189.846  012.244  012.244: sourcing /home/clausseno/.vim/bundle/browserlink.vim/autoload/browserlink.vim
189.958  012.560  000.316: sourcing /home/clausseno/.vim/bundle/browserlink.vim/plugin/browserlink.vim
[...]
346.354  000.005: --- VIM STARTED ---

(both times editing a new .html file)

It shouldn't. But you're right, my startup file says it does, although the times are already faster. That's because I overlooked setupHandlers(), which is always called from the plugin. Moving that back into the plugin, I get
193.512  000.200  000.200: sourcing /home/clausseno/.vim/bundle/browserlink.vim/plugin/browserlink.vim

Amendmend follows.


[Candidate 3v3 Glacier 6 ZH v1] Dust particles emit from center Oil Derrick

Observed behavior
Dust particles emit from center Oil Derrick. It looks strange.
Expected behavior
No particles emit from center Oil Derrick.
Screenshots

take as designed

As designed


Re-add parallel calculation of statistics

Mea culpa on this one. I remember removing that and thinking "I'll add
this back in once the tests are green", but then I never did! I wonder,
how might we add a test to ensure that we're always calculating these
in parallel? We can't rely on the same trick we did to ensure that
scenarios are run in parallel, but I'm sure we could come up with
something.
I also noticed now that the old MapValues module is no longer used,
so I've removed that in this commit.
Resolves #99

Yeah, I thought about testing the parallel execution and couldn't come up with anything myself.
The only thing I could think of is benchmarking the statistics generation of quite some scenarios with lots of values to calculate from. Otherwise, I don't know how to :(

I thought of having a rough benchmark for calculating the stats for a bunch of scenarios, but that seemed like it was very likely to be a flakey test since it would be subject to available CPU power on Travis. On busy boxes it would probably fail kind of often 😢


Move istio gateway's override setting into spec.ingress.istio

This patch moves istio gateway's override setting into
spec.ingress.istio.
spec.knative-ingress-gateway and spec.cluster-local-gateway are
still valid but obsolete.
e.g. confgiure gateway override
cat <<-EOF | kubectl apply -f -
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
  name: ks
  namespace: knative-serving
spec:
  ingress:
    istio:
      enabled: true
      knative-local-gateway:
        selector:
          foo: bar
EOF

Release Note
spec.knative-ingress-gateway and spec.cluster-local-gateway are deprecated.
Use `spec.ingres.istio.knative-ingress-gateway` and `spec.ingres.istio.knative-local-gateway` instead.

/cc @houshengbo  @maximilien @ZhiminXiang

How long is the deprecation for?

The deprecation period should be same with Kubernetes's https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecating-parts-of-the-api.

GA: 12 months or 3 releases (whichever is longer)
Beta: 9 months or 3 releases (whichever is longer)
Alpha: 0 releases

serving's field, for example imageDigest, follow the same rule as:

TODO(savitaashture) Remove deprecatedImageDigest. ref https://kubernetes.io/docs/reference/using-api/deprecation-policy for deprecation.

/lgtm
/approve


hdl-dump: init at unstable-2020-02-05

Motivation for this change
I'd like to use the hdl_dump command to manage my PS2 game backup library from my NixOS box.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Replaced by #101243


Exception when used with factor-bundle with somewhat specific source files layout

After building my project with require-globify and factor-bundle I get the following exception in the browser:
a.js:6 Uncaught TypeError: Cannot read property '0' of undefined
    at Object.require.4.dup (file:///home/futpib/tmp/require-globify-factor-bundle-issue-demo/dist/a.js:6:16)
    at s (file:///home/futpib/tmp/require-globify-factor-bundle-issue-demo/dist/a.js:1:262)
    at file:///home/futpib/tmp/require-globify-factor-bundle-issue-demo/dist/a.js:1:313
    at Object.require.3../lib/util.js (file:///home/futpib/tmp/require-globify-factor-bundle-issue-demo/dist/a.js:2:27)
    at s (file:///home/futpib/tmp/require-globify-factor-bundle-issue-demo/dist/a.js:1:262)
    at e (file:///home/futpib/tmp/require-globify-factor-bundle-issue-demo/dist/a.js:1:433)
    at file:///home/futpib/tmp/require-globify-factor-bundle-issue-demo/dist/a.js:1:451

Steps to reproduce:

clone https://github.com/futpib/require-globify-factor-bundle-issue-demo.git
npm install
node index.js
xdg-open index.html or open index.html in your browser
uncaught exception in the browser console

I tried to come up with a shorter executable example, but this is the simplest I could get.
Here is the compiled code that leads to exception (prettified by chrome's debugger):
<!-- index.html -->
<script src="./dist/common.js"></script>
<script src="./dist/a.js"></script>

// common.js
require = (/* omitting boilerplate browser-pack/prelude.js */)({
    2: [function(require, module, exports) {}
    , {}]
}, {}, [])

// a.js
require = (/* omitting boilerplate browser-pack/prelude.js */)({
    3: [function(require, module, exports) {
        module.exports = {
            'util': require('./lib/util.js')
        };
    }
    , {
        "./lib/util.js": 4
    }],
    4: [function(require, module, exports) {
        arguments[4][2][0].apply(exports, arguments) // Uncaught TypeError: Cannot read property '0' of undefined
    }
    , {
        "dup": 2
    }]
}, {}, [3])

Note that naming of the src/* subdirectories is somehow significant (a and a-b). If I rename a-b to b or ab I am no longer able to reproduce this. (no idea)
Also, identical contents of src/a/lib/util.js and src/a-b/lib/util.js seems to be significant (they don't have to be empty, but they have to be identical, for this issue to reproduce). This makes me thing this may be related to dedupe part of browserify pipeline, but I'm not yet that deep into the whole build process to figure this one out for sure.
Workaround: don't glob-require identical files within directories that are prefixes of one another :).
I know this is a very specific edge case that no one probably cares about, I hope to at least get some pointers to what this could be related to.

This turned out to be unrelated to require-globify. Sorry for that.

This is a duplicate of substack/factor-bundle#51


Main Screen taking too long to load

After moving from rest to GRPC the main screen sometimes takes a very long time to load. It is very inconsistent.
It might even be that the initial push message from the server doesn't trigger a screen render.
Here is how it looks like on the front server:

https://github.com/mbrn/material-table/issues/2643
https://github.com/mbrn/material-table/issues/2650
https://github.com/mbrn/material-table/issues/2727
Possible Solutions:
Downgrade as mentioned in posts above
Move to community-supported version:
https://github.com/mbrn/material-table/issues/2727#issuecomment-759196495

Reason: NGINX as grpc-web is a bad proxy. Replacing edge proxy with Envoy should do the trick


Scriptaculous Effect.Highlight no longer works with Prototype 1.7.1

previous lighthouse ticket #1379
by Fjan

I just noticed that upgrading Prototype from 1.7.0 to 1.7.1 breaks the often used Scriptaculous Highlight effect on all browsers I've tried. All other Scriptaculous Effects still work fine. No errors appear.
(I'm not sure if this should be reported here or on Scriptaculous, I'll report it there too, but the Prototype version number suggests it should be backwards compatible)

This got fixed in #59.

(In other words, it works with 1.7.2.)


Story 91 finetuning of scrutinizer build step

Done.

A new inspection was created.

The inspection completed: 3105 new issues, 2 updated code elements


Events fail after Queue::fake()

Laravel Version: 5.3.30
PHP Version: 7.0.9
Database Driver & Version: MariaDB-10.1.16

Description:
I'm testing, if jobs are queued using the fake queue. After I implemented throwing an event in one of my models the QueueFake fails to push.
Tests\Core\SomeTest::testQueueFake
ErrorException: get_class() expects parameter 1 to be object, string given

/home/ape/Symvaro/wasser_web/vendor/laravel/framework/src/Illuminate/Support/Testing/Fakes/QueueFake.php:135
/home/ape/Symvaro/wasser_web/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:423
/home/ape/Symvaro/wasser_web/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:354
/home/ape/Symvaro/wasser_web/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:221
/home/ape/Symvaro/wasser_web/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php:480
...

Steps To Reproduce:
class CustomerChangeEvent
{
    use SerializesModels;

    public $someModel;

    ...
}

public function testQueueFake() {
    Queue::fake();

    event(CustomerChangeEvent::class);
}

@apreiml not sure if this would help or not, but can you try with adding Event::fake() as well?  Not sure if they both need to be done to play nicely together.

Actually, what's most likely happening is you're passing just the class name into event()
Try doing:  event(new CustomChangeEvent()); since it's expecting an object on the first param, whereas ::class only returns the actual class name as a string, ie. 'CustomerChangeEvent'

@astierler Hi, thanks for the input. The class name should also be supported, according to the source comments. Also I don't want the Events to be faked, because it like to see if the event properly adds a job to the queue.
I checked this again and it seems to fixed with the current version of Laravel 5.4.*


FastCell in production environment

Hello.
I am really interested in FastCell control, because I want to improve the performance in my app ListViews (too slow in Android).
But I have to say that this is for a customer project, and this code will be in production very soon.
Do you reccommend me to use it? In readme file you don't recommend to use this library for production...
Thanks!! :-)

you know what, you can give it a go.. I need to update the readme. Since I wrote that I’ve solved a couple of issues I had.

On 18 Jul 2015, at 10:35, fcogutierrez<EMAIL_ADDRESS>wrote:
Hello.
I am really interested in FastCell control, because I want to improve the performance in my app ListViews (too slow in Android).
But I have to say that this is for a customer project, and this code will be in production very soon.
Do you reccommend me to use it? In readme file you don't recommend to use this library for production...
Thanks!! :-)
—
Reply to this email directly or view it on GitHub https://github.com/twintechs/TwinTechsFormsLib/issues/11.

Ok, will do :)


No worldtype for 1.20x exists, please explain how users are supposed to use Modern Beta's worldgen.

If a datapack is supposed to be used, please link to one that works, the one I tried crashes if loaded at all.

Confirmed on 1.21.1.


Request for PyCrypto

From @GoogleCodeExporter on May 31, 2015 11:27
Please consider packaging PyCrypto: http://pycrypto.org/

In particular, I need "from Crypto.Cipher import Blowfish" to work but the
entire library would be very helpful.

Thanks.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 8 Sep 2010 at 2:34
Copied from original issue: damonkohler/android-scripting#422

From @GoogleCodeExporter on May 31, 2015 11:27
Please! Please, port this to SL4A.
Thank you.

Original comment by<EMAIL_ADDRESS>on 18 Sep 2012 at 5:49

From @GoogleCodeExporter on May 31, 2015 11:27
Added PyCrypto to Python build of: https://code.google.com/p/android-python27/

Original comment by<EMAIL_ADDRESS>on 4 Oct 2012 at 12:26


Client/server architecture?

One of the main reasons I struggle to use up is the fact that the complete application .zip must be uploaded on each deploy. If this .zip weighs >30MB and my connection is flakey that day, my deploy often times out. And in Australia where most people have a 1-2 Mbps uplink, this is quite often. This might also be an issue on mobile.
To resolve this, up could be architected like docker, where the client is a cli application which speaks an http server and by default, the client and server reside on the same machine. In the case of up, the "server" could optionally be a lambda function, which uses S3 for project file caching and the client is a thin cli wrapper around the server API.
On deploy, the client could ask the server what it currently has cached in S3, compute the diff, and just send what's missing. And then up works as normal except it's run from a lambda function. In addition to much smaller uploads, this has the added benefit of reduced RTTs to all AWS endpoints.
The current mode would be supported by the running the up server on localhost/localsock, with it as the default server. Of course, S3 caching and file diffs would be skipped.
This would need to be opt-in as it'd be deploying an unknown function, though up is already managing functions, API gateway, etc so I don't think it's much of a stretch.
I was thinking of doing this myself though I thought I'd throw out the idea here first.

Canada is pretty bad too (maybe 3-5mbps), but my ~30mb zips are still a second or two.  Honestly though this would be an issue with any deployment system aside from CI or EC2 with better networks. Even pushing Docker layers is going to be very slow if you have to rebuild the layer with your app constantly.
It could be interesting to explore a diff-based approach, but Up will be able to support Docker platforms too, so I'm not sure I'd want to overkill Lambda specifically. For example Up could still push to ECS, Azure's ACI etc.
Deploying from a local machine is a bit gimmicky, it's great for getting started or small teams, but I think a CI or GIT-hook based system is necessary for teams to utilize better networks, and enforce tests etc of course.

Hey @tj sorry completely forgot about this one. Yeah I agree Docker pushes are quite slow. I think the client/server architecture would be a good fit for up, whereas the diff against image layers would not - since a single layer is hashed and then re-uploaded on any change. A diff with up could be against each individual file, and you could take this a step further with a binary diff against large files (e.g. rdiff) though this only makes sense with a server at the other end doing the packaging.
RE: support Docker platforms directly: Like having an up-server image? which runs a different version of up? or do you mean make it more like a CI server, which pulls up projects and then runs up deploy?
Which brings me to my semi-solution to this, at the moment, I'm using circleci. I add some AWS env vars and:
version: 2
jobs:
  build:
    docker:
      - image: circleci/node:8
    steps:
      - checkout
      - run:
          name: Install npm
          command: 'npm install'
      - run:
          name: Download up
          command: 'curl https://i.jpillora.com/apex/up | bash'
      - run:
          name: Deploy
          command: './up deploy production'

For real apps, you'd want to have a CI/CD workflow, with tests, where up could slot in easily at the end. My use case is personal apps which I just want to deploy as fast as possible. Understandably, this isn't a priority, so all good. Just food for thought 👍


Remove a race condition from TestRetentionCutoff

@fabxc That fixes the minor race conditions (only in test) mentioned before.

:+1:


Launch file for combined gzserver + bridge

🎉 New feature
Summary

This patch lets you combine the functionality from #530 and #532 into a single launch file.
How to test it?
Use the provided ros_gz_sim.launch.py (modify config_file accordingly) to run the bridge as an executable
ros2 launch ros_gz_sim ros_gz_sim.launch.py world_sdf_file:=empty.sdf config_file:=/home/caguero/ros_gz_ws/src/ros_gz/ros_gz_bridge/test/config/full.yaml

You should see messages of gzserver loading. Additionally, verify that you see the /ros_chatter topic:
caguero@cold:~/ros_gz_ws$ ros2 topic list
/parameter_events
/ros_chatter
/rosout

Confirm that no container has been created:
caguero@cold:~/ros_gz_ws$ ros2 component list

Now CTRL-C to stop all nodes and try the composable version:
ros2 launch ros_gz_sim ros_gz_sim.launch.py world_sdf_file:=empty.sdf use_composition:=True config_file:=/home/caguero/ros_gz_ws/src/ros_gz/ros_gz_bridge/test/config/full.yaml

gzserver should be running. Verify that you also see the /ros_chatter topic:
caguero@cold:~/ros_gz_ws$ ros2 topic list
/parameter_events
/ros_chatter
/rosout

And confirm that a container has been created with both nodes:
caguero@cold:~/ros_gz_ws$ ros2 component list
/ros_gz_container
  1  /ros_gz_bridge
  2  /gzserver

Test it

Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@ahcorde, is CI supposed to pass right now with 24.04?

@caguero  yes, I think it should pass


ci: add helm.docs target to helm generate

Helm readme is auto-generated based on template and values.yaml file. This adds the helm.docs target to helm.generate which is the target various CI workflows are targeting.

/approve

/merge


Not able to connect to any other machine through jdbc-json driver

I tried an example with beer-sample and travel-sample on localhost and it worked fine.
But when I tried same with a different hostname:
static String ConnectionURL = "jdbc:couchbase://<IP_ADDRESS>:8093";
I get this error:
9:51:35.463 [main] ERROR com.couchbase.CBConnection - Error opening connection for jdbc:couchbase://<IP_ADDRESS>:8091 exception Error getting cluster response
Exception in thread "main" java.sql.SQLException: Error opening connection
at com.couchbase.CBConnection.(CBConnection.java:79)
at com.couchbase.CBDriver.connect(CBDriver.java:95)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:270)
at com.test.jdbc2.test.App.main(App.java:17)
Caused by: org.apache.http.client.ClientProtocolException: Not found: Check the URL: 404
at com.couchbase.jdbc.core.ProtocolImpl.handleClusterResponse(ProtocolImpl.java:286)
at com.couchbase.jdbc.core.ProtocolImpl.pollCluster(ProtocolImpl.java:944)
at com.couchbase.jdbc.core.ProtocolImpl.connect(ProtocolImpl.java:235)
at com.couchbase.CBConnection.(CBConnection.java:73)
... 4 more

This sounds a lot like issue #33, which is fixed, but the fix has not yet been uploaded. Did you try with the locally-built version?
From: pm48 <notifications<EMAIL_ADDRESS>Reply-To: jdbc-json/jdbc-cb <reply<EMAIL_ADDRESS>Date: Tuesday, April 5, 2016 at 8:08 PM
To: jdbc-json/jdbc-cb <jdbc-cb<EMAIL_ADDRESS>Subject: [jdbc-json/jdbc-cb] Not able to connect to any other machine through jdbc-json driver (#42)
I tried an example with beer-sample and travel-sample on localhost and it worked fine.
But when I tried same with a different hostname:
static String ConnectionURL = "jdbc:couchbase://<IP_ADDRESS>:8093";
I get this error:
9:51:35.463 [main] ERROR com.couchbase.CBConnection - Error opening connection for jdbc:couchbase://<IP_ADDRESS>:8091 exception Error getting cluster response
Exception in thread "main" java.sql.SQLException: Error opening connection
at com.couchbase.CBConnection.(CBConnection.java:79)
at com.couchbase.CBDriver.connect(CBDriver.java:95)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:270)
at com.test.jdbc2.test.App.main(App.java:17)
Caused by: org.apache.http.client.ClientProtocolException: Not found: Check the URL: 404
at com.couchbase.jdbc.core.ProtocolImpl.handleClusterResponse(ProtocolImpl.java:286)
at com.couchbase.jdbc.core.ProtocolImpl.pollCluster(ProtocolImpl.java:944)
at com.couchbase.jdbc.core.ProtocolImpl.connect(ProtocolImpl.java:235)
at com.couchbase.CBConnection.(CBConnection.java:73)
... 4 more
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com/jdbc-json/jdbc-cb/issues/42


Get Restaurants from Area

Currently, JugheadBot fetches best restaurants for only Cities. Ideally, it should be able to fetch from areas like "Kothrud, Pune" or "Mahim, Mumbai"

Fixed this issue with commit ID : 164a686c3a8dbac03732df83980ce014ecbf6b3e


Windows Defender detects the build output as Trojan:Win32/Fuery.C!cl

Hi,
I am building the FIDO bridge using Ubuntu 20.04 under WSL. During the make -j $(nproc) stage Windows Defender quarantines one of the files and alerts me it has found a threat.

I don't have any good suggestions on how to deal with this sadly.

Interesting. Unfortunately, I also don't have any good suggestions other than excluding the build directory from Windows Defender or using the apt repository I maintain at apt.mgbowen.dev (though I totally understand if you want to only compile from source for security or other reasons).

I looked around a bit and it seems quite common when using CMake - apparently the fact that the binary created is a.exe is part of the signal (!!). Anyway, the build worked anyway as it seems to have been only some build test binary and didn't actually have to run.

Glad to hear you were able to get it working! I'm going to go ahead and close this for now; feel free to reopen it or file another issue if you run into any other problems.


Fix programmatically changing index

This PR fixes an issue with changing NavbarNotifier.index. The current code base doesn't start animation to change a visible route, it happens only when user taps on a tab. These changes run "changing tab" animation with corresponding onChanged listener for all cases (independently, if it was called programmatically or not).
https://github.com/maheshj01/navbar_router/issues/57
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing using flutter test

If you need help, consider pinging the maintainer @maheshmnj

Nevermind, I opened another PR @AlexIzh which will fix this issue. https://github.com/maheshj01/navbar_router/pull/59
I really appreciate your effort to contribute, But I really needed to get this out and published asap. I am going to close this PR.
Thank you for your contribution


References to User FAQ on github wiki for kubernetes/kubernetes needs to be removed

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
This started out as a bug report (https://github.com/kubernetes/kubernetes/issues/52430) against the wiki pages at kubernetes/kubernetes on github because of a broken link there. That issue was resolved, and @bgrant0607 indicated that the FAQ page is obsolete and is due to be decommissioned once relevant information is shifted to documentation and referenced the community work at kubernetes/community#116.
There are 4 links in our current documentation that actively reference this FAQ page that probably need excision and the relevant text updated:

_data/tasks.yml:    path: https://github.com/kubernetes/kubernetes/wiki/User-FAQ#how-do-i-change-the-size-of-my-cluster/
docs/home/index.md:* [User FAQ](https://github.com/kubernetes/kubernetes/wiki/User-FAQ)
docs/tasks/debug-application-cluster/debug-application.md:Users are highly encouraged to check out our [FAQ](https://github.com/kubernetes/kubernetes/wiki/User-FAQ).
docs/tasks/debug-application-cluster/troubleshooting.md:   * [User FAQ](https://github.com/kubernetes/kubernetes/wiki/User-FAQ)

Proposed Solution:
Remove the existing links from current pages prior to the wiki page being removed.
Page to Update:

https://kubernetes.io/tasks/debug-application-cluster/troubleshooting.md
https://kuberentes.io/tasks/debug-application-cluster/debug-application.md
https://kuberentes.io/home/
_data/tasks.yml

Hi @heckj, I fixed this issue, could you help me to review?

Absolutely!


Debugger feature request - Minor - Delete breakpoints from debugger panel

With a button for Delete All

easy to add the one-by-one delete (except I had to add the signal which was missing).
also not hard to add delete all but does require more overhead -- will do later.

not sure we need delete all -- more clutter and a separate toolbar just for that -- calling this good enough & simpler..


Only update the branch for push and api requests

https://github.com/travis-ci/travis-core/commit/672f4e595d59d8de9fcb746d8dfd4cfd7749c99a introduced a bug that now sets the current build to the branch's last_build_id even if it's a pull request build.
This change fixes that.

Sven says: maybe we should then also check the api payload, since Eric (customer) was talking about the last_build_id on the “default branch” and stuff. i’m not sure how that all maps to the UI, so maybe it’s easier to check things on the API once this is deployed to production


Moves all Log.h inclusion to Base.h

Describe the issue (if no issue has been made)
The issue have been made: #326.
PR impact (Make sure to add closing keywords)
List of related issues/PRs this will solve:

Impact
Issue/PR

Issues this solves
solves #326

Proposed fix (Make sure you've read on how to contribute to Hazel)
The fix consists of two step:

Adds #define LOG_H in Log.h to act as header guard.
Includes Log.h in Base.h after the definition of Hazel::Ref.

Additional context
As @LovelySanta said, Log.h should be included in Base.h. However Log.h also includes Base.h, resulted in a circular inclusion. Since Log.h only needs the custom reference system Hazel::Ref defined in Base.h, I moved the inclusion of Log.h to after that definition so by the time Log.h is included, Hazel::Ref is already defined and ready to be used.

There is no need for that guard, ´#pragma once´ should take care of that.

There is no need for that guard, #pragma once should take care of that inside Log.h.

The reason I put header guard in is for some reason the compilation failed all the time with some "symbol undefined" error. I thought that was because of the circular inclusion (most of the time circular inclusion is the cause of "symbol undefined"). Note that at that time, both #include "Log.h" and #include "Base.h" is placed at the beginning of the other file. It seems that the problem back then is because of where #include "Log.h" is placed.


Aliasing artefacts when rendering images in Jupyter

I see block-like aliasing artefacts when rendering the sine wave from the Holoviews showcase.

I know that the circular sine wave with varying frequency is very sensitive in this regard, if the images get rescales/resampled  with inappropriate smoothing filters at any point in the rendering pipeline you will obtain visible artefacts.
I also see the artefacts in the images on the documentation
http://holoviews.org/Tutorials/Showcase.html

Thanks for filing the issue!
We've noticed these artefacts for a while now but have no idea what causes them. As far as I know this is just how matplotlib renders this type of data as opposed to anything to do with HoloViews itself. Do you agree @philippjfr ?

I've always thought that those artifacts were the result of rendering at one resolution but then displaying at a slightly different resolution.  But I just checked by right clicking on the image from the tutorial and viewing it in a different tab where I could zoom in, and the artifacts remained, suggesting that they were present when first rendered.  So yes, I would assume they come directly from matplotlib, though it would be nice to replicate the issue outside of HoloViews to be sure.

I don't know enough about matplotlib, but as I understand matplotlib can use various backends.
I'm wondering whether it depends on the particular backend or is present in another.
Implicit scaling appears to be happening with almost every image in matplotlib as a n by m array will usually not be displayed using m by n actual screen pixels. If this rescaling isn't done properly I am not surprised that there are some aliasing artefacts.

Good point; the mismatch between the array in which the function has been evaluated and the resolution at which mpl is rendering it would be sufficient to explain this.  If so, I don't see anything that could be done, as we'd have to figure out what the eventual size in pixels will be on screen and then evaluate the original function with that specific pixel size.
Maybe just use SVG output?

I just spent the better part of an hour to try and reproduce these artefacts wit plain Matplotlib in a jupyter notebook and experiment with different interpolation settings. Preliminary summary: I also get aliasing but it looks different. I don't see the same cube-shape structure in the test images. I will try to place a sample jupyter notebook somewhere, hopefully today.

Uploaded a notebook here:
https://github.com/VolkerH/interpolation_and_aliasing_matplotlib/blob/master/Interpolation%2Band%2BAliasing.ipynb
To me, the kind of artefacts I get with plain matplotlib look different. In particular, I can't reproduce this effect in matplotlib which I observe with holoviews:

Can I easily change the inerpolation mode in holoviews ?

Here's your gist adapted to holoviews:
import numpy as np
import holoviews as hv
hv.notebook_extension('matplotlib')

# play around with the following two parameters
numpoints = 128
freq = 100

def sine(x, phase=0, freq=100):
    return np.sin((freq * x + phase))

dist = np.linspace(-0.5,0.5,128)   # Linear spatial sampling
x,y = np.meshgrid(dist, dist)
grid = (x**2+y**2)                 # 2D spatial sampling

testpattern = sine(grid, freq=freq)

methods = ['none', 'nearest', 'bilinear', 'bicubic', 'spline16',
           'spline36', 'hanning', 'hamming', 'hermite', 'kaiser', 'quadric',
           'catrom', 'gaussian', 'bessel', 'mitchell', 'sinc', 'lanczos']

hv.Layout([hv.Image(testpattern, label=interp)(style=dict(interpolation=interp))
           for interp in methods])

@philippjfr Could you include a screenshot? I am curious as to what that layout looks like.
Thanks!

Updated my post above.

The differences are pretty subtle! None and 'nearest' are the same, I see  a difference with 'hanning' and all the rest look pretty much the same to me.
I can't see the aliasing issue anymore, maybe because it is harder to see with the hot colormap?

Also can't spot the artifacts in that plot and it looks the same with Greys to me.

By accident I just found out that the artefacts go away when you increase the size of the plot.

@philippjfr Does that mean there is a suitable fix?
Can this issue either spawn a new issue/PR or otherwise be closed?

Well, I suspect that the issue is created whenever the image is downsampled for output (if the plotsize is so small that it is required). Without looking into the source codeI suspect the downsampling is not done in a proper way (e.g. not adequate smoothing before downsampling or an error when calculating the indexes with which the image is evaluated).
Therefore I am not surprised that the error goes away once the plot size is large enough for the image to be no longer downsampled.

In the end this is not a HoloViews issue but rather an issue with matplotlib under certain conditions. I'll close but please reopen if there are any suggestions on improving this in HoloViews itself.


TypeError: Cannot read property 'notifications' of undefined

Raspberry 3
nodejs 6
Master branch downloaded an hour ago.
I'm getting this error:
/home/pi/.config/signalk-server-node/node_modules/signalk-schema/src/fullsignalk.js:175
if (!previous[pathPart]) {
^
TypeError: Cannot read property 'notifications' of undefined
at /home/pi/.config/signalk-server-node/node_modules/signalk-schema/src/fullsignalk.js:175:20
at Array.reduce (native)
at addValue (/home/pi/.config/signalk-server-node/node_modules/signalk-schema/src/fullsignalk.js:174:43)
at addValues (/home/pi/.config/signalk-server-node/node_modules/signalk-schema/src/fullsignalk.js:161:5)
at FullSignalK.addUpdate (/home/pi/.config/signalk-server-node/node_modules/signalk-schema/src/fullsignalk.js:105:3)
at FullSignalK.addUpdates (/home/pi/.config/signalk-server-node/node_modules/signalk-schema/src/fullsignalk.js:95:10)
at FullSignalK.addDelta (/home/pi/.config/signalk-server-node/node_modules/signalk-schema/src/fullsignalk.js:52:8)
at FromJson. (/home/pi/.config/signalk-server-node/lib/pipedproviders.js:47:21)
at emitOne (events.js:96:13)
at FromJson.emit (events.js:188:7)
Connection is already closed.
I have some null values in custom notifications keys, is this the problem?

Or have you implemented the alarm system and now notifications paths must point to existing keys?

Can you provide the input delta that causes this?
I am in the middle of implementing alarms, but nothing in master yet.

Not at work now, I think could be caused by another issue with uuid. I will try to report on monday. Thanks.

Fixed.  Wrong uuid/mmsi use in settings file. thanks.


Whether the global data is affected by the sampling rate？

Please answer these questions before submitting your issue.

Why do you submit this issue?
[x] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

Whether the global data is affected by the sampling rate？
For example, the sample rate configuration is 30，Is the global statistics 100？ or 30？

If you are asking about backend sampling, no, it isn't. The metrics are accurate even in sampling mode

If you are asking about backend sampling, no, it isn't. The metrics are accurate even in sampling mode

666


Exception is not porpagated for nonretryable exception when retry policy is used.

Hello there!
I use the retry policy and custom error handling for specific status codes. I expect that exception, which is thrown in ErrorDecoder, should be propagated to the top level, but OutOfRetriesException wrapped the original exception instead. The exception in ErrorDecoder is non-retryable.
We are using feign version 3.2.4
Our config looks like this:
@Bean
fun reactiveRetryPolicy(): ReactiveRetryPolicy {
    return BasicReactiveRetryPolicy.retry(retries)
}

@Bean
fun customErrorDecoder() = ErrorDecoder { methodKey, response ->
    if (HttpStatus.NOT_FOUND.value() == response?.status()) {
        return@ErrorDecoder BusinessException()
    }
    return@ErrorDecoder ErrorDecoder.Default().decode(methodKey, response)
}

Also, I tried to use ReactiveErrorMapper. Without success. Config is here:
@Bean
fun buildNotFoundErrorMapper() = ReactiveErrorMapper { _, u ->
    if (u is FeignException.NotFound) {
        return@ReactiveErrorMapper AppNotInstalledException()
    }
    return@ReactiveErrorMapper u
}

In non reactive feign there is posibility to use exceptionPropagationPolicy()
Could it be added to reactive feign as well?

It's not clear for me what exactly fix do you want:

do not retry on nonretryable exception?
unwrap  OutOfRetriesException  in case of exceptionPropagationPolicy.UNWRAP  ?

Hi @kptfh !
I would expect to unwrap OutOfRetriesException in case of exceptionPropagationPolicy.UNWRAP.
Regarding point 1, if I remember it correctly, if the exception is nonretryable, the lib already makes only one attempt and throws an exception.

Please check this pr https://github.com/PlaytikaOSS/feign-reactive/pull/571
and especially  this test
BTW: Reactive feign uses 'RetryableException' only to detect correct retry delay in 'BasicReactiveRetryPolicy'
https://github.com/PlaytikaOSS/feign-reactive/blob/develop/feign-reactor-core/src/main/java/reactivefeign/retry/BasicReactiveRetryPolicy.java#L58
If retry policy was set it will retry on all errors
If you want to skip retries for specific error then you need to use 'FilteredReactiveRetryPolicy'

Amazing! Looks like it :) Thanks.
Thanks for explaining