"Card absent or mute" errors when ejecting and reinserting a card

There seems to be some currently not well understood combination of conditions that leads to the CCID driver being unable to power up the card and, consequently, to failures to perform any SCard operations with it.
One scenario that seems to cause this issue relatively often is ejecting a card and reinserting it back within 2-3 seconds; however, the same problem was observed in other scenarios as well.
It's also unclear whether it's related to specific reader(s) or card(s); so far it was reproduced on two different readers ("SCM Microsystems Inc. SCR 3310" and "Gemalto IDBridge CT30") and on one specific card ("Oberthur Cosmo (eID)"). It was reproduced on two different versions of the CCID Free Software driver: 1.4.33 and 1.4.31.
In the logs, the problem manifests itself through the following errors:
CmdPowerOn Card absent or mute
IFDHPowerICC() PowerUp failed

According to detailed CCID logs, in both successful and failing scenario the same command is sent to the reader:
62 00 00 00 00 00 05 00 00 00
(according to specs, 62h corresponds to the "PC_to_RDR_IccPowerOn" message)
However, the response to this command is different. In the success case, we get:
80 16 00 00 00 00 05 00 00 00 <then the ATR code follows>
meanwhile in the failing case we get:
80 00 00 00 00 00 05 41 FE 00
IIUC, 80h corresponds to the "RDR_to_PC_DataBlock" message, 41h corresponds to bmICCStatus=1 ("An ICC is present and inactive (not activated or shut down by hardware error)") and bmCommandStatus=1 ("Failed (error code provided by the error register)"), FEh is "ICC_MUTE" (with the documented possible cause "CCID timed out while talking to the ICC"). Overall, this combination of the error codes is documented for the PowerOn command as "ICC mute (Time out)".

I've tried a couple of workarounds, but so far none of them helps. For posterity:

Tried to repeat the PC_to_RDR_IccPowerOn command in a loop (up to 100 times);
Tried to additionally do the PC_to_RDR_IccPowerOff command before each PC_to_RDR_IccPowerOn retry attempt;
Tried inserting 1-second sleeps between the retry attempts.

Closing this - we haven't seen this recently, and it might've been a hardware issue.


regroup by app instead of by layer type

If using Fields see #9 then regroup layers into "apps" and apps can share data, outputs and formulas. Currently there is only one main model, and it has modules for data, output, formulas, etc. Sometimes each module has only one or two lines.
EG: pvpower.data contains:
from carousel.core.data_sources import DataSource

class PVPowerData(DataSource):
    data_file = 'pvpower.json'
    data_path = 'path/to/pvpower,json'

and the other modules are similar.
The proposal is to combine these layers into a single model or app file with fields.
EG: pvpower.sandia contains:
from carousel.core.models import Model
from carousel.core.fields import DataField, OutputField, FormulaField
from carousel.core import UREG

class SandiaModel(Model):
    air_temp = DataField(units=UREG.degC, dtype=float)
    wind_speed = DataField(units="m/s", dtype=float)
    ...
    ac_power = OutputField(units=UREG.watt, dtype=float, size=8761)
    ...
    f_energy = FormulaField(?)

class DeSotoModel(Model):
    # can still use data from SandiaModel
    series_resistance = DataField(units="ohms", dtype=float)
    ...
    current = OutputField(units="amps")
    ...
    ac_power = OutputField(units=UREG.watt, dtype=float, size=8761)
    ...
    f_energy = FormulaField(?)

I don't really see how this would work because:

there's no logical grouping of data, outputs, formulas, etc.
there's no place to call __prepare_data__() for data sources
models will get too long and difficult to manage
models can't share data sources, formulas, etc.


Remove post install message

Proposal: remove post install message.
When I bundle, my brain lazily watches for something different to mean something changed or is gonna change. When a post-install message comes up, I expect it to be about a deprecation warning or a breaking change. I don't expect it to be a link to documentation.
I'm already on board to use the gem. The name "AvaTax" is already pretty googleable. The name "AvaTax-REST-V2-Ruby-SDK" is even more so. If I need the docs for this gem, googling the name of the gem would get me to this repo where there are the same links to the developer site and blog.
In the spirit of reducing the visual noise in a normal, uneventful bundle install, can y'all remove this post-install message, please?
Thanks

Bump.

Is there anything I can do to move this PR along?


winget upgrade --all - rebooted without confirmation, winget now missing

Brief description of your issue
I ran winget upgrade --all.  I'm assuming one of these caused the reboot. However, after the reboot, I can't run winget any more:

Steps to reproduce
I'm not sure about reliable steps. I have to assume this isn't happening for everyone. All I did was upgrade --all.
Expected behavior
upgrade all the bits and don't remove itself; preferably, don't just reboot - I was in the middle of a meeting, with the upgrade running in the background
Actual behavior
reboot; no winget any more
Environment
Can't run winget any more )': I don't know what other info to furnish here.

ah, never mind - I managed to break the PATH entry for winget. So the report about missing winget is invalid - it's just the reboot without confirmation; I'll open a new issue for that so as to make it clear.


Fix/delete repo #1372

Implemented #1372

Codecov Report

Merging #1410 (20a70f5) into master (68a6461) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1410      +/-   ##
==========================================
+ Coverage   40.49%   40.53%   +0.03%
==========================================
  Files         153      153
  Lines       12020    12020
==========================================
+ Hits         4868     4872       +4
+ Misses       6463     6460       -3
+ Partials      689      688       -1

Impacted Files
Coverage Δ

pyramid/tier_fs.go
58.77% <0.00%> (+1.75%)
:arrow_up:

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 68a6461...20a70f5. Read the comment docs.

Hey @ozkatz, I've made the changes you requested, do review and let me know

I agree @ozkatz , working on the changes

hey! I'm not sure how to redirect to the /repositories page after the repo delete action, I could use some help here please and thank you

hey! I'm not sure how to redirect to the /repositories page after the repo delete action, I could use some help here please and thank you

Sure, it should be similar to create a repository, it moves to the specific repository after the operation completes.
So delete repository will probably look something like this:
    useEffect(()=> {
        if (deleteStatus.done) {
            history.push('/repositories');
        }
        listRepositories();
    }, [listRepositories, deleteStatus.done, history]);

Thanks!

@nopcoder I'm getting this error after I submit delete repository. Looks like it isn't redirecting. Am I missing something? ->

The issue is related a reset of the state we need to perform, which is missing here and in the create repository page.
In actions/repositories.js you will need to add deleteRepositoryDone (or other name) that will reset the REPOSITORY_DELETE.
Import it and call when you push the /repositories into the the history.
Additionaly we need to add a call to createRepositoryDone in components/RepositoryListPage.js when create.done.
The problem was that after the action completed rendering the list repositories kept the previous state and viewed the repository you deleted as if it is just created.
For example if you had full refresh and than go and delete your repository - it would have seen that all is working.
Now when the state changes to done we reset the action so for delete and create repository the state reset after successful operation.


Assisted Keys: Restrictions

Task Description
The following restrictions have been implemented on assisted keys:

Signing Server: requires m:2, n:3
IKS: requires m:3, n:5

Also, IKS can only be added to one vault for this release. To be unlocked by #3802

Verified this issue on keeper app v 1.1.11(293)


Barebones pipelines

This is the structural elements of the CI pipeline. Doesn't do anything yet but I wanted to get this merged in so that when I start doing more PRs I can start getting pass/fail in the PRs.

/check-enforcer evaluate


Reels support for instaloader.

Reels support for instaloader.
this is newly supported featured from Instagram
adding a other parameter -- reels
need a feature to download reels of the profile.

Duplicate of #812.


learning git

I'm learning git branch

Cool! Given that this doesnt really add any test coverage, going to close this PR but good job submitting it / etc!


Additional sensor values

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
/
Describe the solution you'd like
I see that the integration already parses  most of the data that the EVSE provides, but it does not expose all of it to the home assistant as a sensor. Specifically, i am missing total home power and total solar power, to have an easy way to use the measurements for showing whole home consumption data, import and export.
Describe alternatives you've considered
do you plan on adding that, or should i make a fork and add the missing info, and open a pull request?  Also, it might be useful to have some of the entities disabled by default, and then have an option in HA to just enable the ones you want to see.
Additional context
/

Oh hey, an unexpected visitor :D
I mean I can add it, but not sure when i will find the time - if your comfortable enough with the sloppy code I'll gladly accept a PR.

Well, ive already added the two mentioned manually in the custom components on my install. So it is not a big deal to make a pull request to the repo. I'll first go through the other values and add the rest of the missing ones though.

I've added total house and solar power in the latest update. Are you missing some?
There is a lot of values exposed from the EVSE but some of them are not exactly useful.

Hey, first, thank you very much. I see you have also fixed the websocket requirement.
I'll check if any other values seem useful. I just have to fix the wireless coverage outside of home first (or run a cable), that is actually the reason why i havent pushed my local changes before and created a pull request.
Lots of values might not me bush of use to everyone, i agree. I know that there is an option to implement all the sensor values, but just have them disabled by default in HA. Implementing all and just enabling the "important" would imo be the best solution.


Update ember data

Fixes https://github.com/owid/owid-issues/issues/839 (data for several African countries was missing in the original Ember data; but on their latest update they have solved it).
Not all files need to be reviewed (but feel free to check them), since most of them are copies of a previous data step with minor changes, like versions and metadata. The files that need revision are:

dag_files/dag_energy.yml
snapshots/ember/2022-12-13/yearly_electricity.csv.dvc
etl/steps/data/meadow/ember/2022-12-13/yearly_electricity.py
snapshots/ember/2022-12-13/yearly_electricity.py

Thanks @lucasrodes very much for the detailed review! I'll make some small amendments to the graph you created.


Import articles

Fixes #392
These are the articles I imported

https://www.citusdata.com/blog/2017/07/13/citus-addon-for-heroku/

Turned it into a paragraph in our installation section

https://www.citusdata.com/blog/2017/01/17/parallel-indexing-with-citus/

Added it as a Table Management topic

https://www.citusdata.com/blog/2016/04/28/scalable-product-search/

Turned it into the "Real-Time Faceted Search" tutorial

https://www.citusdata.com/blog/2017/03/10/how-to-scale-postgresql-on-aws/

Used it as the new cloud intro, "Why We Built Cloud"

https://www.citusdata.com/blog/2016/11/29/event-aggregation-at-scale-with-postgresql/

Converted to "Real-Time Event Aggregation" tutorial

I omitted the next batch of articles. They turned out to be just too random, or else more about postgres than Citus:

https://www.citusdata.com/blog/2016/10/10/outer-joins-in-citus/
https://www.citusdata.com/blog/2017/06/30/efficient-rollup-with-hyperloglog-on-postgres/
https://www.citusdata.com/blog/2016/08/30/citus-clouds-usage-of-citus-cloud/
https://www.citusdata.com/blog/2016/07/25/sharding-json-in-postgres-and-performance/

This next batch was redundant with the information in docs already. I think redundancy is already kind of a problem in docs, so I didn't want to make it worse.

https://www.citusdata.com/blog/2017/04/04/distributed_count_distinct_with_postgresql/
https://www.citusdata.com/blog/2016/10/03/designing-your-saas-database-for-high-scalability/
https://www.citusdata.com/blog/2016/08/10/sharding-for-a-multi-tenant-app-with-postgres/

Note to self: there are sphinx warnings we'll want to fix, but I'm de-prioritizing this PR while others review which of the blog posts would be better in a separate "articles" section.

Hey @begriffs -- I read over these changes. I think most of these blog posts (and the posts that we didn't yet incorporate) could live better in an Articles section. Here's why I think this way.

https://www.citusdata.com/blog/2016/04/28/scalable-product-search: Turned it into the "Real-Time Faceted Search" tutorial
https://www.citusdata.com/blog/2016/11/29/event-aggregation-at-scale-with-postgresql: Converted to "Real-Time Event Aggregation" tutorial

In our current tutorials, we provide step-by-step instructions. Our first goal is to guide users to download sample data and make them successful at the end of a tutorial. Our secondary goal is to prime them for our target use cases. Neither of these blog posts fit that pattern -- that said, I think they are pretty interesting for more advanced users.
(Side question: Have we thought about updating the Use-case Guide > Real-time Analytics with information in the Real-time Event Aggregation tutorial?)

https://www.citusdata.com/blog/2017/03/10/how-to-scale-postgresql-on-aws: Used it as the new cloud intro, "Why We Built Cloud"

This section talks to Citus Cloud's benefits and our architectural decisions in delivering those benefits. In that sense, a more accurate description could be "Why We Built Citus Cloud In a Particular Way." I don't know where other databases put architectural decisions and their resulting benefits. This feels more product marketing rather than traditional docs material to me. But I could be convinced. I know for example PostgREST does this. :)

https://www.citusdata.com/blog/2017/01/17/parallel-indexing-with-citus: Added it as a Table Management topic

If we had a section on benchmarking, this blog post could go there. That said, I think we'd need to do some rewording to align this post's contents with that new section.

https://www.citusdata.com/blog/2017/07/13/citus-addon-for-heroku: Turned it into a paragraph in our installation section

I'm split on this post. Part of this post talks about Citus Cloud's benefits and we also talked about them in the Citus Cloud launch post.
I don't know if we'd like to mention Heroku as a way to install Citus. I think not -- so that we don't conflate this section further.

@begriffs -- I think the fastest way to move forward on this PR is to open a new Articles section and start adding these blog posts into that section. What do you think?

Sure, no problem. I'll move them all into an articles section.

Articles are in their own section now. Ready for review.

Hey @begriffs - I went over this pull request today. This looks generally good.
I had the following comments.

I wasn't able to see an active deployment / preview. How can we get a preview?
Since the content in the articles section is the same as the one in our blog, do we need to do anything on the SEO side?
We shortened or changed the names for these blog posts. Could we keep the original titles? (Similarly, one the of links was too short -- aggregation.rst. Could we make it a bit more descriptive?)
We skipped over some of the articles we originally picked. For example, we skipped over the sharding for a multi-tenant app and HLL articles. Could we include them?

OK, I took care of your comments and noticed quite a few other things to improve as well.

I wasn't able to see an active deployment / preview. How can we get a preview?

Heroku had taken the preview down due to inactivity. I've recreated it and it's at https://citus-doc-preview-pr-424.herokuapp.com/

Since the content in the articles section is the same as the one in our blog, do we need to do anything on the SEO side?

Yes, after deployment to the docs I'll need to work with Jason or somebody else with CloudFlare access to set some Canonical URI headers for each of these pages to tell search engines that the blog posts are the real source. This will avoid SEO penalties, but it will also mean that google searches for terms in these articles will link to our blog rather than our docs. If we want the reverse behavior for search we will need to add those headers when serving the blog posts instead.

We shortened or changed the names for these blog posts. Could we keep the original titles? (Similarly, one the of links was too short -- aggregation.rst. Could we make it a bit more descriptive?)

I shortened the names so they would fit better on the left hand nav menu. However I restored them all to their original long versions for you, and I guess it doesn't look so bad on the menu. Check out the preview and see what you think. Also a name like aggregations.rst only affects the URL. In the docs a link to this page would show "Real-time Event Aggregation at Scale Using Postgres with Citus," or else a custom title if that was specified in the originating link.

We skipped over some of the articles we originally picked. For example, we skipped over the sharding for a multi-tenant app and HLL articles. Could we include them?

Done.

Hey @begriffs -- I went over the preview and the changes look generally good.
I had the following comments before we could merge this pull request. I'm super excited by this work btw.

Could we start concurrent work on the SEO side (or this isn't feasible)? That way, we wouldn't penalize ourselves for too long?
In what order do we present these articles? Maybe we sort them by their order of publication on our blog?
Is there a way to signal to the reader that these Articles were previously published on our blog? Maybe we write a short intro for the Articles section? Or, include an "originally published" sentence at the top? (That way, the reader would know that some of these articles could be dated.)
The images in these articles have descriptions underneath them. Do we need those descriptions?
Could you click on all links before submitting to check that they are still live?
I have a few short comments on specific articles. I'll add them to the PR shortly.

Could we start concurrent work on the SEO side (or this isn't feasible)? That way, we wouldn't penalize ourselves for too long?

Putting the SEO changes into effect won't take very long. The main delay will be getting the time of someone who has CloudFlare access. I can put some time on Jason's calendar for this, and wait to merge this PR until that time. Also we are running low on the number of page rules that CloudFlare has allocated to us. We'll need more to add the headers for each of these articles. I'll ask Jason about his opinion here and we may need to pay more money to get more rules, or else find and replace old rules that aren't useful anymore.

In what order do we present these articles? Maybe we sort them by their order of publication on our blog?

Kind of at random. Some of the articles are grouped by topic like the hyperloglog ones at the end. Not sure that sorting by publication date is all that relevant. In fact sorting in the opposite direction might be better, if anything, since older articles may not reflect the current state of Citus as well. :man_shrugging:

Is there a way to signal to the reader that these Articles were previously published on our blog? Maybe we write a short intro for the Articles section? Or, include an "originally published" sentence at the top? (That way, the reader would know that some of these articles could be dated.)

Sure. Probably an "originally published" link in each is best since people may or may not read an introductory section.

The images in these articles have descriptions underneath them. Do we need those descriptions?

I see what you mean. That came from the program I'm using to translate the Markdown format to ReStructuredText. I'll get rid of the unnecessary captions.

Could you click on all links before submitting to check that they are still live?

Good idea. I ran a web crawler on the articles and found two broken links. One of them is actually the awesome multi-tenant microsoft article from 2006! Microsoft took the article down in July. I located it on the wayback machine and turned it into a PDF and included it in our docs repo.

@ozgune I think all the issues you pointed out are now taken care of, except determining a particular order for the articles in the TOC.

hey @begriffs, this looks good.
I'm adding my final four comments to this pull request.

When I visit the docs homepage, I see Articles as a separate extended section under our eight buttons: https://citus-doc-preview-pr-424.herokuapp.com/

This looks a bit off to me. Could we remove Articles links from the documentation home page? (Maybe, we make Articles one of these buttons in the future?)

"How Distributed Outer Joins on PostgreSQL with Citus Work" Article looks different than the original one in three ways:
(a) Our outer join images are placed left and right in the Article. They appear consistently on the right hand side in the blog post.
(b) The bullet point starting with "Outer joins should be between distributed(sharded) tables only" is cut out. (The original blog post also incorrectly puts these together into a paragraph.)
(c) Minor. The image after "How Citus Processes OUTER JOINs When one-to-one matching between shards exists, then performing an outer join on large tables is equivalent to combining outer join results of corresponding shards." is right aligned in the article.

SEO changes

Putting the SEO changes into effect won't take very long. The main delay will be getting the time of someone who has CloudFlare access. I can put some time on Jason's calendar for this, and wait to merge this PR until that time. Also we are running low on the number of page rules that CloudFlare has allocated to us. We'll need more to add the headers for each of these articles. I'll ask Jason about his opinion here and we may need to pay more money to get more rules, or else find and replace old rules that aren't useful anymore.

Sounds good. Could you put time on Jason's calendar? If we need to pay more to CloudFlare to make this work, that also sounds good.

Article ordering

In what order do we present these articles? Maybe we sort them by their order of publication on our blog?

Kind of at random. Some of the articles are grouped by topic like the hyperloglog ones at the end. Not sure that sorting by publication date is all that relevant. In fact sorting in the opposite direction might be better, if anything, since older articles may not reflect the current state of Citus as well. :man_shrugging:

Yes, I had "sorting in the opposite direction" in mind. That way, we'd get articles that reflect Citus' current state at the top. Could you change the Articles' order accordingly?

OK, the SEO, article ordering, image alignment, and fixed frontpage are all ready now.
Assuming those were the last pieces of feedback, so time to merge.


Add a corpus of fuzzer testcases.

It is better not to use djxl_fuzzer as directory name to avoid possible name conflict.


[6.x] Utilise Orchestra\Testbench\package_path()

coverage: 84.977% (-1.4%) from 86.385%
when pulling 341220b624dbf7969e5a2ee6d406a69e352609d8 on 6/use-package-path
into 8b620a63ca5d48f9efbef5ca430b12f80ad949bb on 6.x.


Removing unsupported characters

Removing unsupported characters on windows

@cs-tushar-kanade  can you please remove .DS_Store Files from commit

Closing to re-raise it again

@cs-tushar-kanade can you please remove .DS_Store Files from commit

Done


ci: ignore generated files when calculating coverage

Signed-off-by: Jason Liu<EMAIL_ADDRESS>Ⅰ. Describe what this PR does

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in make test

/lgtm
/approve


scrollAnimation does not affect scrollToIndex

Description
Setting scrollAnimation to false in a LineChart does not disable the initial animation for scrollToIndex. Reviewing the code, it looks like scrollAnimation is only applied for scrollToEnd but not for scrollToIndex.
https://github.com/Abhinandan-Kushwaha/react-native-gifted-charts/blob/8f7d6065e54653b5f1c671567c97e2748ba7a366/src/Components/BarAndLineChartsWrapper/index.tsx#L192
Steps to reproduce

Set scrollAnimation to false and pass an index to scrollToIndex
Load the chart
Chart navigates to the index with the animation enabled. Expected behavior is the for the chart to be disabled.

Snack or a link to a repository
No response
version of react-native-gifted-charts
1.4.34
React Native version
0.74.3
Platforms
Android, iOS
Workflow
None

Thanks for your PR @dannybit
Your changes are available from versions 1.4.44 onwards.


Create multiple OCCT packages with different number of dependencies (with/without VTK etc.)

Hey,
I was wondering if it could make sense to create multiple OCCT packages with varying number of dependencies? The motivation would be to make it possible to reduce the number of dependencies based on what functionality in OCCT you need?
For example, to start, perhaps compile an additional occt version without VTK (which seem to be adding more dependencies than occt itself)?
If this is something that others might find useful, I can start on making a PR with attempting to add a multi-build setup in the meta.yaml. There we can discuss further, such as potential name-conventions etc...
Any thoughts on this? @looooo @adam-urbanczyk

It would be interesting to know which package uses the vtk stuff of occt. Maybe we can skip the vtk dependency?

FYI:
VTK deps:

 vtk               9.1.0       qt_py39hf2c8a5a_210 conda-forge/win-64
 eigen             3.2.8       0                   conda-forge/win-64
 tbb-devel         2018.0.4    hdc96acc_0          conda-forge/win-64
 loguru            0.3.2       py36_1              conda-forge/win-64
 utfcpp            2.3.5       0                   conda-forge/win-64
 python            3.9.9       hcf16a7b_0_cpython  conda-forge/win-64
 python_abi        3.9         2_cp39              conda-forge/win-64
 vc                14.3        h3d8a991_9          conda-forge/win-64
 vs2015_runtime    14.32.31332 h1d6e394_9          conda-forge/win-64
 libpng            1.6.38      h19919ed_0          conda-forge/win-64
 libzlib           1.2.13      hcfcfb64_4          conda-forge/win-64
 hdf5              1.12.1      nompi_h57737ce_104  conda-forge/win-64
 freetype          2.12.1      h546665d_0          conda-forge/win-64
 lz4-c             1.9.3       h8ffe710_1          conda-forge/win-64
 jpeg              9e          h8ffe710_2          conda-forge/win-64
 glew              2.1.0       he025d50_0          conda-forge/win-64
 libnetcdf         4.8.1       nompi_hf689e7d_100  conda-forge/win-64
 ffmpeg            4.3.1       ha925a31_0          conda-forge/win-64
 libtiff           4.4.0       hc4061b1_0          conda-forge/win-64
 zlib              1.2.13      hcfcfb64_4          conda-forge/win-64
 pugixml           1.11.4      h0e60522_0          conda-forge/win-64
 libxml2           2.9.14      hf5bbc77_4          conda-forge/win-64
 tbb               2021.7.0    h91493d7_0          conda-forge/win-64
 libtheora         1.1.1       h8d14728_1005       conda-forge/win-64
 qt-main           5.15.6      hf0cf448_0          conda-forge/win-64
 gl2ps             1.4.2       h2c487a6_0          conda-forge/win-64
 expat             2.5.0       h1537add_0          conda-forge/win-64
 libogg            1.3.4       h8ffe710_1          conda-forge/win-64
 proj              9.0.1       h1cfcee9_1          conda-forge/win-64
 jsoncpp           1.9.5       h2d74725_1          conda-forge/win-64
 double-conversion 3.2.0       h63175ca_1          conda-forge/win-64
 sqlite            3.40.0      hcfcfb64_0          conda-forge/win-64

and
 OCCT 7.6.2 deps

 occt                  7.6.2       h8294837_0          conda-forge/win-64
 fonts-conda-ecosystem 1           0                   conda-forge/noarch
 rapidjson             1.1.0       0                   conda-forge/win-64
 vc                    14.3        h3d8a991_9          conda-forge/win-64
 vs2015_runtime        14.32.31332 h1d6e394_9          conda-forge/win-64
 freetype              2.12.1      h546665d_0          conda-forge/win-64
 freeimage             3.18.0      hfcb8cd7_7          conda-forge/win-64
 vtk                   9.1.0       qt_py39hf2c8a5a_210 conda-forge/win-64
 fontconfig            2.14.1      hbde0cde_0          conda-forge/win-64

and
OCCT 7.4.0

 occt       7.4.0        h823b557_3 conda-forge/win-64
 vc         14.3         h3d8a991_9 conda-forge/win-64
 freetype   2.9.1        hf819b56_4 conda-forge/win-64
 tbb        4.4_20160526 vc9_1      conda-forge/win-64
 tbb        2021.7.0     h91493d7_0 conda-forge/win-64
 fontconfig 2.14.1       hbde0cde_0 conda-forge/win-64

Please don't skip it - OCP is using this functionality. Conda build seems to support multiple outputs from a single recipe, maybe this is the best way forward. Only  VTK related artifacts link to VTK, so it would be trivial to split.

It would be interesting to know which package uses the vtk stuff of occt. Maybe we can skip the vtk dependency?

@looooo at the very least, this component does https://dev.opencascade.org/doc/overview/html/occt_user_guides__vis.html
As @adam-urbanczyk states, this component is in use by downstream projects, so the option to retain a VTK-enabled version is critical.

From what I can gather, it seems we agree on keeping an occt version with VTK support in addition to a minimum version. That's great! I will try to find some time in the coming days to create a PR for a multi-build meta.yaml. There we can discuss naming conventions for the different variations of occt packages.

Hey @looooo :) Some of the build pipelines belonging to conda-forge has suffered some instabilities lately (and it seems our previous build attempt of occt failed as a result). I was recommended by one of the conda-forge staff link to just make an empty commit to main. If you have time, maybe you can try it out?


Fix tests for net6.0

For some reason the test "Can_rewrite_static_method" seems to fail only when targeting net6.0 or greater.
It seems to be caused by not handling InlineSig opcode.

It seems to be caused by the use of unsafe code.
We only discovered this because between .NET Framework 4.8 and .NET 6, calling DateTime.UtcNow invokes unsafe code.

I got the immediate issue fixed by changing the test to not use DateTime.UtcNow (which calls into unsafe unmanaged code).


Display only open issue from project

Hey there, while playing around with the API  I considered to have only listed open issues on a project. It may be not of interest what has already been done so some kind of filter would be nice to have.
thanks for your work here mate!
Greetings
Carsten

Hi @PadawanDeluxe
Thanks for feedback. I have just updated the repo. So, the plugin shows only opened issues of a given project.


#69 implement contains() for Directory

Implemented the Issue #69. Once as synchronous version, once as asynchronous. The code comments should be clear about usage. Nevertheless, I am available for questions.

@passsy I don't understand why the test fail. I can't reproduce them on my local machine. Seems like the analyzer causes errors:
2020-07-25T09:44:59.5932894Z Failed to precompile test:test:
2020-07-25T09:44:59.5933988Z /github/home/.pub-cache/hosted/pub.dartlang.org/analyzer-0.39.15/lib/src/dart/resolver/extension_member_resolver.dart:355:38: Error: The getter 'extensions' isn't defined for the class 'Scope'.
2020-07-25T09:44:59.5934476Z  - 'Scope' is from 'package:analyzer/dart/element/scope.dart' ('/github/home/.pub-cache/hosted/pub.dartlang.org/analyzer-0.39.15/lib/dart/element/scope.dart').
2020-07-25T09:44:59.5935491Z Try correcting the name to the name of an existing getter, or defining a getter or field named 'extensions'.
2020-07-25T09:44:59.5936059Z     for (var extension in _nameScope.extensions) {
2020-07-25T09:44:59.5936181Z                                      ^^^^^^^^^^

Do you know this error?

@passsy can you rerun the tests? I can't do it. Only locally but there all tests pass:
user@device:~/code/dart/dartx$ dart test
Precompiling executable... (12.5s)
Precompiled test:test.
00:15 +310: All tests passed!

#115 solved the issue


Add googlebot and bingbot to list of crawler user agents

Prerender.io docs recommend to upgrade these:
https://prerender.io/documentation/google-support

Make sure to update your Prerender.io middleware or manually add googlebot and bingbot to the list of user agents being checked by your Prerender.io middleware. See the bottom of this page for examples on adding googlebot to your middleware.

There have been some reported issues with Googlebot rendering JavaScript on the first request to a URL that still uses the ?escaped_fragment= protocol, so upgrading will prevent any issues by serving a prerendered page directly to Googlebot on the first request.

Thanks.


Brewed GCC compilation failures after clean linuxbrew installation

Please always follow these steps:

[x] Confirmed this is a problem with running a brew command and not brew installing or the post-install behaviour of one or more formulae? If it's a formulae-specific problem please file this issue at https://github.com/Linuxbrew/homebrew-core/issues/new
[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed all issues and retried your prior step?
[x] Ran brew config and brew doctor and included their output with your issue?

brew config
brew doctor
Beginning with a clean installation in /home/linuxbrew/.linuxbrew (after running the uninstall script, rm -r /home/linuxbrew/.linuxbrew and finally ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Linuxbrew/install/master/install)"). After a brew install gcc, I can brew install bottles, but can't install any packages from source with bottled gcc 5.3.
$ brew install -s hello
gist-log
$ brew install -s stress
gist-log

lib/dirname-lgpl.c:86:1: internal compiler error: Illegal instruction
 }
 ^
0x2ad2f27da30f ???
	/tmp/glibc-20170824-4056-jtmpe6/glibc-2.23/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x2ad2f27c76ff __libc_start_main
	../csu/libc-start.c:289

or
stress.c:765:1: internal compiler error: Illegal instruction
 }
 ^
0x2b147f15530f ???
	/tmp/glibc-20170824-4056-jtmpe6/glibc-2.23/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x2b147f1426ff __libc_start_main
	../csu/libc-start.c:289
Please submit a full bug report,
with preprocessed source if appropriate.

Host glibc: 2.17
/usr/bin/gcc: 4.8.5
glibc: 2.23

@sjackman some glibc mismatch here?

https://gist.github.com/eernst/6638e2cec88eff349376e31c330023a1#file-gistfile1-txt-L13

CPU: 64-core 64-bit westmere

My first guess is that your CPU is too old to run some bottle, possibly glibc. We've encountered this problem with gmp before. I haven't yet seen this problem with glibc 2.19, but perhaps it's a problem for glibc 2.23.
If you're comfortable debugging at the command line, you can try something like…
ulimit -c unlimited
gcc-5 hello.c
gdb core*
x/i $pc

Otherwise try reinstalling the compiler toolchain from source rather than using bottles. Remove all installed packages with brew remove $(brew list), and then run…
HOMEBREW_BUILD_FROM_SOURCE =1 brew install gcc

It looks like gmp could be the culprit. I tried the brew remove and source build as you suggested, and ./configure fails for HOMEBREW_BUILD_FROM_SOURCE=1 brew install gmp (gist-log).
However, ./configure --enable-cxx successfully completes if I download the tarball and run manually (configure stdout)
For some reason, the compiler test bombs out in the linuxbrew build context:
Last 15 lines from /home/eernst/.cache/Homebrew/Logs/gmp/01.configure:
checking for gcc-4.8 option to accept ISO C89... none needed
checking whether gcc-4.8 understands -c and -o together... yes
checking for gcc-4.8 option to accept ISO C99... -std=gnu99
checking for gcc-4.8 -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking how to run the C preprocessor... gcc-4.8 -std=gnu99 -E
checking build system compiler gcc-4.8 -std=gnu99... yes
checking for build system preprocessor... gcc-4.8 -std=gnu99 -E
checking for build system executable suffix...
checking whether build system compiler is ANSI... yes
checking for build system compiler math library... -lm
checking whether we are using the GNU C++ compiler... yes
checking whether g++-4.8 accepts -g... yes
checking C++ compiler g++-4.8  -O2 -pedantic -fomit-frame-pointer -m64 -mtune=corei7 -march=corei7... no, program does not run
checking C++ compiler g++-4.8  -g -O2... no, program does not run
configure: error: C++ compiler not available, see config.log for details

... but is fine with the manual build...
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking build system compiler gcc -std=gnu99... yes
checking for build system preprocessor... gcc -std=gnu99 -E
checking for build system executable suffix...
checking whether build system compiler is ANSI... yes
checking for build system compiler math library... -lm
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking C++ compiler g++  -O2 -pedantic -fomit-frame-pointer -m64 -mtune=corei7 -march=corei7... yes

$ diff /usr/bin/g++ /home/linuxbrew/.linuxbrew/bin/g++-4.8
(no output)

After discovering this, I ran a brew remove $(brew list) again and a HOMEBREW_BUILD_FROM_SOURCE=1 brew install gmp to attempt to build gmp before some of the other dependencies of gcc. It turns out this succeeds:  gist-logs after installing m4 and xz as dependencies.
Now, with
$ brew list
gmp  m4  xz
running HOMEBREW_BUILD_FROM_SOURCE=1 brew install gcc subsequently fails with the following at the make bootstrap stage:
In file included from /home/linuxbrew/.linuxbrew/include/features.h:392:0,
                 from /home/linuxbrew/.linuxbrew/include/stdio.h:27,
                 from ../../../../libgcc/../gcc/tsystem.h:87,
                 from ../../../../libgcc/libgcov.h:41,
                 from ../../../../libgcc/libgcov-merge.c:26:
/home/linuxbrew/.linuxbrew/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
compilation terminated.

gist-logs

Try…
export HOMEBREW_BUILD_FROM_SOURCE=1
brew install glibc
brew install gcc

Tried after a brew remove $(brew list). glibc installs successfully, gcc target fails at gmp with the same configure error as above.

That looks like a bug. I've opened PR https://github.com/Linuxbrew/homebrew-core/pull/4246 to hopefully fix it. In the mean time, try…
HOMEBREW_BUILD_FROM_SOURCE=1  brew install https://raw.githubusercontent.com/sjackman/homebrew-core/gcc-disable-multilib/Formula/gcc.rb

I've been having troubles compiling things using brewed gcc or compiling a new gcc too. I noticed several things that might be helpful.

It seems that the new version of binutils was compiled with a glibc 2.25 (see the comments of binutils.rb)
I tried different systems with glibc 2.17 locally, and gcc 4.4 or gcc 4.8. Somehow I think the glibc and binutils don't match and I can't make them match, even if I tried to compile a new one. So I can't compile a new gcc (many versions) successfully. If I used the brewed gcc, everything will be broken.
I'm trying to build a gcc 7.2 on my Ubuntu 17.04  that has glibc 2.24 and gcc 6.3.0. Since this system has higher version of glibc, brew didn't install another glibc for me. And now the compiling of my gcc 7.2 seems to be perfectly. I haven't encountered the problem I encountered at other machines yet.

Just finished compiling the gcc 7.2. It works perfect.

But still. I'm curious about how to fix the issues on my other machines. I don't have permission to upgrade those systems.

@sjackman With multilib disabled via the formula you provided, I'm now getting an error in make bootstrap while building gcc (for libgomp):
configure: updating cache ./config.cache
configure: error: unsupported system, cannot find sizeof (omp_lock_t)
make[2]: *** [configure-stage1-target-libgomp] Error 1
make[2]: Leaving directory `/tmp/gcc-20170913-27737-4mt8pv/gcc-5.3.0/build'
make[1]: *** [stage1-bubble] Error 2

gist-logs
The issue remains that HOMEBREW_BUILD_FROM_SOURCE=1 brew install gcc fails at on a clean linuxbrew install at gmp on this machine - it appears that gmp needs to be built before glibc in order to make it all the way through the gcc dependencies and begin to compile gcc.
I suspect all of this is resulting from a recent update to something in the gcc toolchain other than gcc, as I had a working gcc 5.3.0 last week, I believe, if not earlier this week. Unfortunately, I did a brew update without noting which basic libraries were updated.

@eernst Did you tried to use gmp-6.1.1? Everything just crashed after I upgrade gmp-6.1.2 on an old machine. But it seems to work after I change back to gmp-6.1.1.
I used the following steps to use gmp-6.1.1.

brew edit gmp
change the everything that is 6.1.1 to 6.1.2, and save it
brew install gmp or brew reinstall gmp if you've already installed it
when you see an error like sha256 is not correct, press ctrl-C to stop it from compiling from source
copy the actual sha256 value
brew edit gmp
in bottle do, change the sha256 value for the :x86_64_linux one, and save it
brew install gmp or brew reinstall gmp if you've already installed it

Then you can simply install gcc by brew install gcc and you don't have to compile it.
You can also try brew install pkg-config to see if gcc can compile it. If so, then it's probably the problem of the new gmp version.
Since I also compiled other things with the system compiler, it's possible that there might be another reason. But this one is the closest reason I found. Hope this helps.

It seems that the new version of binutils was compiled with a glibc 2.25 (see the comments of binutils.rb)

binutils is compiled with glibc 2.5 (not 2.25) so that it can run on older systems with older versions of glibc.

Reverting to the gmp 6.1.1 bottle and using bottles for the rest of the gcc 5.3 toolchain works. I can successfully compile other packages from source afterward (hello, etc.).
Perhaps this is a gmp-specific bug.

Some other ideas. From the gmp website (just in case, I do not believe this is a really the problem here).
Ryzen CPU caution: The AMD Ryzen CPUs sold in spring and early summer 2017 have serious bugs which make any software run very unreliably. One experiences spurious segfaults and system hangs from building as well as running GMP. As of 2017-08-11 AMD has not disclosed the full ramifications of these bugs, and they refuse to recall faulty CPUs. Instead, they replace CPUs on a case-by-case basis after asking each customer to run in exhausting circles for a few weeks. They have invented a newspeak term for these bugs, Performance Marginality Problem.

There is also this old issue which looks similar: https://github.com/Homebrew/homebrew-versions/issues/1038

The gmp formula has a problem wherein the bottle is compiled for the instruction set of the machine that it's being built on rather than the core2 architecture that is usually the target instruction set of bottles. The host architecture may have changed when we update from CircleCI 1.0 to 2.0.

Just to confirm, I have the same issue as eernst, on a computer with the 'Intel Xeon E3-12xx v2 (Ivy Bridge)' processor. Reverting to the 6.1.1 bottle works for me as well.

@davidryderuk Can you please report the output of brew config?

I've uploaded the output for brew config here.

CPU: octa-core 64-bit ivybridge

https://gist.github.com/davidryderuk/9f72b90bfc6cfbd130a21d08a133ec13#file-gistfile1-txt-L12
Ivy Bridge is the sandybridge microarchitecture, which was released on 2011-01-09.
https://en.wikipedia.org/wiki/List_of_Intel_CPU_microarchitectures#Roadmap
It includes a lot of CPU instruction extensions:
x86-64, Intel 64
SSE, SSE2, SSE3, SSSE3, SSE4, SSE4.1, SSE4.2
AVX, TXT, VT-x, VT-d

https://en.wikipedia.org/wiki/Sandy_Bridge
If you're interested in helping troubleshoot this further and are comfortable using gdb to debug a core dump, you can follow these instructions above: https://github.com/Linuxbrew/brew/issues/488#issuecomment-328998824
to help determine which CPU instruction is causing the Illegal instruction error.

Sorry, I'm struggling to get  the core dump. I can confirm a second, newer, but less capable computer is working correctly, without showing the same error. See here.

CPU: quad-core 64-bit broadwell

https://gist.github.com/davidryderuk/902761e55e1692eda6f41d18f6024d61#file-brew-config-output-broadwell-L12
Broadwell is the Haswell microarchitecture, the next one after Sandy Bridge.
https://en.wikipedia.org/wiki/Haswell_(microarchitecture)
Extensions
x86-64, Intel 64
SSE, SSE2, SSE3, SSSE3, SSE4, SSE4.1, SSE4.2
AVX, AVX2, TXT, and TSX (disabled via microcode, except for Haswell-EX)
VT-x, VT-d

Since Sandy Bridge, it gained AVX2. It's possible that the gmp 6.1.2 bottle is unintentionally using an AVX2 instruction. This is a bug. I don't yet know how to fix it.

If anyone has the time and interest to look into the gmp issue, I'd appreciate a PR to fix the issue very much. I believe that the precompiled binary bottle may be using AVX2 instructions. It should not.

The proper fix is to modify the formula to prevent it from using advanced instructions. That's going to require some work. In the mean time, I think we should either revert gmp to 6.1.1 and use the old bottle. Or, as a stop gap solution, build a bottle for gmp 6.1.2 on the oldest 64-bit Intel machine that we can get our hands on, or in a virtual machine emulating an old machine.

I've hopefully resolved the issue with the gmp bottle with PR https://github.com/Linuxbrew/homebrew-core/pull/4399
Try brew update && brew reinstall gmp
If you get a SHA-256 error, delete the old cached bottle and try again.

Thanks. That works for me with the ivy bridge computer.

Appears to be working fine on Westmere and Sandybridge. Thanks!

Works on AMD Opteron(tm) Processor 6378

Glad to hear it!


Fixed opengl Surface with disabling refresh of shader wrapper id in c…

closes #3088

Just waiting for the ci to pass and then we could merge it because it doesn't really change anything anymore (fingers crossed at least i hope 😨 )


Create TataElxsi.html

sample test job do not merge

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

Can one of the admins verify this patch?


Todo items so Gittyup can be moved from the AUR to official Arch Linux repos

I've been hacking away on the AUR build for a few days now and I think this project has moved a lot closer to a respectable build process than it used to be. In the GitAhead days and early Gittyup days there was may too much forced vendoring and other hacks to even consider making an official Arch Linux build out of, but I think we're close now.
Here are some things I'd like to see before making the package official:

[ ] Building on current gcc was fixed in #759, but no release has been made that includes this. I'm cherry picking the patch to make the AUR build work, but that's not a great practice and it would be nice to have a cleaner build for official packaging.

[ ] The libgit2 update in #153 needs to get finished. Currently the build is still using a fork of an old libgit2 build. To make it official I would like to see the build working with -D USE_SYSTEM_LIBGIT2=ON against the latest official libgit2 release. This is also mentioned in #581.

[ ] If (and I haven't researched whether this is the case or not, so if) scintillua can be split out such that it can be built as a separate shared library (or perhaps used via a LuaRocks installed module?) then that should be done. This may not be the way that library is even setup, so if not lets check this off. If it can be done I'll setup the extra library or lua package so satisfy this dependency and make that official too.

[ ] Same for Lexilla, only this looks like a lot more obviously possible to me. It should be pretty easy to make a system package that provides liblexilla.so, we just need a -D USE_SYSTEM_LEXILLA argument and search routines to support it. This is also part of #581.

[ ] Optionally and somewhat tentatively, the whole kuba--/zip thing could use replacement. It looks like it can't even be built as a shared library, so vendoring it might be the only way. As such I won't make this a blocker for moving it to official repos, but linking one of the much more generic archive handling libraries that are in standard use everywhere would be appreciated.

[ ] For bonus points to make other distros more likely to pick this up, change the CMake config to default to using system dependencies, and only set them the other way around for builds where it makes sense to vendor everything (such as Flatpack). If all the dependencies are expected from the system and the sources worked without any submodule initialization/fetches that would make it a lot easier to onboard other distros. Again I can make the current devendoring tricks happen for Arch Linux, but it would sure be preferred the other way around.

The current AUR package already has enough interest and I can take care of the rest of the details. As soon as a release is cut that checks off at least the first two items here and as many of the others as actually makes sense then I'll spin up an official build. Hopefully this issue is encouragement that things are close and perhaps inspires some outside contributors to jump on these points.

@OdinVex There has never been a need to comment out the check function or add cmake options, you can always just build with --nocheck. In any case that is a moot point at the moment because the checks pass properly when built in a chroot. Passing checks finally is actually what prompted me to create this issue since so many other things have gotten worked out and I wasn't sure what was left before I can move ahead with official packaging.

but it does support running sed on content

I'd bet dollars to donuts you can get makepkg args through somehow; every build system I've seen has some way to handle arguments and if you built your own you should be able to add this trivially. But even if not if you can run sed then just add BUILDENV+=(!check) to the top of the PKGBUILD. And again as I said tests do pass now so you shouldn't need to do anything.


react-semantic ui site is not reachable

I was referring react semantic ui control to develop my app in react js later have been facing issue accessing react semantic ui site

I'm wondering how can a popular website like this be down for so many days? Strange!

It seems that it's caused by Cloudflare issues in India:
https://community.cloudflare.com/t/website-blocked-for-some-users-in-india/300620
Unfortunately, I don't know how it could be fixed 😐

@layershifter Would this help - https://community.cloudflare.com/t/website-blocked-for-some-users-in-india/300620/5

I'm working on this with Jack, I don't have CloudFlare rights unfortunately.

Fantastic! Thanks all for the report and investigation.


review patterns in spreadsheet

Nico is putting together spreadsheets with MP terms that fit existing Upheno patterns. We need to review these to make sure everything looks correct.

atrophy spreadsheet https://docs.google.com/spreadsheets/d/1RMVorUO092l4CNnieazkgVT4U14u5ptlAQqQ2DLHbIU/edit?usp=sharing


export TypingsInstaller from tsserverlibrary

Fixes #53414
This exports interfaces necessary for external implementers of ITypingsInstaller and extenders of TypingsInstaller.

@sheetalkamat @DanielRosenwasser Are you alright with this PR as-is, given the above?


Workerpool issue caused by LIFX component

Not sure who else is using the newly merged LIFX component from #930. I'm having some workerpool issues with it though. I've been able to replicate the issue - removing the LIFX component  (no workerpool issues) and then adding it back (causing a ton of queued tasks over the day). I've also noticed that bulbs aren't discovered by HA until the bulbs are manually updated via the LIFX app/IFTTT. That might just be a quirk of the LIFX bulbs themselves though.
Is anybody else having similar issues? Not sure if it's my local build, but wanted to point it out as 0.12 is on the horizon.
16-01-26 17:51:15 homeassistant.core: WorkerPool:All 25 threads are busy and 9601 jobs pending

@TangoAlpha do you know what's up?

I'm not having any issues.

Interesting. I'll play around more. Can't quite figure out what's going on. It'll be working correctly for ~5 hours or so and then something hangs and the tasks start pooling up. Is there a good way to get at workerpool issues at all? Like printing which task is pending in the log or something?

Just wanted to add, so far I haven't been able to re-replicate my previously described issue after letting things run over night.
I'm wondering if this might be related to a separate issue I've been having with one of my LIFX bulbs. In a nutshell, the bulb becomes unresponsive randomly, but the LIFX app still seems to be communicating with it. LIFX customer support offered to replace my bulb, but promised an upcoming firmware update should fix things. Anyway, I think we're squared away here. I'll keep an eye on things.  Cheers.

I am not having issues either. It does take a while for it to locate and register the bulbs. I think this can be worked out so on start up it automatically finds them.

@Xorso, yeah. I've definitely noticed that. If I adjust the bulbs via the LIFX app, it makes them show up instantly in HA. I'm not sure if there is a way to initially ping the bulbs or if they just have to report to the network on some timed interval.

There was another pull request for the LIFX bulbs that could discover them on startup. I think if we look at the library we can work something out.

@Xorso That would be mine; the discovery was great and all, but everything else was terrible. Again, I'm not great with my Python, nor do I have time to commit to HA at the moment.

Hopefully he workerpool thing was transient, not seen anything like that myself.
To discover bulbs, a get_state message is sent as a broadcast. All bulbs should then respond and details are passed back to HA. This is done at start up and also every 10 seconds via poll functionality.
The broadcast address can be set in the configuration. If not, the library tries to work out an appropriate address. If your server has an address of <IP_ADDRESS> (i.e. local LAN of 192.168.1.x) then the broadcast address should be <IP_ADDRESS>. If the server has more than one IP address, I'm not sure the library can figure it out correctly so a broadcast address should be set in the configuration (a quick guide would be to pick the correct network and replace the last octet with 255)
light:
  # platform name
  platform: lifx
  # optional server address
  # only needed if using more than one network interface
  # (omit if you are unsure)
  server: <IP_ADDRESS>
  # optional broadcast address, set to reach all LIFX bulbs
  # (omit if you are unsure)
  broadcast: <IP_ADDRESS>

Ah, I see. So by server address, you mean the address for the device running Home Assistant? The broadcast address would then be that same IP with 255 in the last octet? I'll give that a shot and see if it changes the behavior at all. Thanks for the clarification!

The server address is used so that the LIFX module can ignore the broadcast messages (no point answering itself :-). When not specified, the server address is retrieved using the gethostbyname function.
When not specified, the broadcast address is calculated from the server address using the ipaddress module.

Gotcha. Adding the server/broadcast IPs to my configuration makes the bulbs show up right on startup. Awesome! Thanks for your help on this. I'm working with LIFX to replace one of my bulbs that I think might be defective. Hopefully, that will resolve any outstanding issues. Thanks for the help! Cheers.


refactor: remove unneeded deleted_at in $allowedFields

Description

deleted_at is not needed for soft deletes.

Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[] User guide updated
[x] Conforms to style guide

@paulbalandan Do you know where does array{username: string, status: string, status_message: string, active:            bool, last_active: string} come from?
See https://github.com/codeigniter4/shield/pull/963/files#diff-459f49e48ae4f20464cf08fd3256652536435610f4f7db89305fe7269e539ac9
 ------ ----------------------------------------------------------------------------------------------------------
  Line   src/Models/UserModel.php
 ------ ----------------------------------------------------------------------------------------------------------
  223    Offset 'email' does not exist on array{username: string, status: string, status_message: string, active:
         bool, last_active: string}.
  224    Cannot unset offset 'email' on array{username: string, status: string, status_message: string, active:
         bool, last_active: string}.
  225    Offset 'password_hash' does not exist on array{username: string, status: string, status_message: string,
         active: bool, last_active: string}.
  226    Cannot unset offset 'password_hash' on array{username: string, status: string, status_message: string,
         active: bool, last_active: string}.
 ------ ----------------------------------------------------------------------------------------------------------

I created an issue: https://github.com/CodeIgniter/phpstan-codeigniter/issues/19


Feature Request: quantize_weights does a signed_quantization [-127,+127] as well

**OS Platform and Distribution: Linux Ubuntu 14.04/16.04
TensorFlow installed from (source or binary): Source v1.3
Bazel version (if compiling from source): bazel release 0.5.4
CUDA/cuDNN version:  v8
GPU model and memory: NVIDIA gtx1060
Have I written custom code: No
Exact command to reproduce:

tensorflow/tools/graph_transforms:transform_graph

Only does an unsigned quantization of the weights. I think it is useful for many that we have a signed quantization so that a normal distribution having a median of zero (0.0f) converts to a TF-8 0. This is useful in general. Thanks.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
TensorFlow version

Thanks for your suggestion.  I need to understand it better before I can refer it to the correct person.  transform_graph is a tool that can do many things.  Which quantization operation is not satisfactory,  and exactly how would you like it changed?  Is it possible that you could get what you want by applying some kind of absolute value or normalization operation prior to the quantization?

@poxvoculi, Specifically, I was referring to quantize_weight.cc and quantize_node.cc. The way I understood by looking at the code is that it only considers the min and the max and maps the remaining weights inside the span. However, it would be useful to consider 0.0f as well and map them to 128 tf8 so that the value zero remains unique in the quantized model.
Yes. There are a number of other methods available to do that, e.g., assigning max=-min, etc., but each has some pros and cons. The best practice, in my reckoning, here is to produce a signed 8-bits representing the value 0f to 0 tf8.  Thanks

@petewarden is this contributions welcome?

Nagging Assignees @petewarden, @poxvoculi: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @petewarden, @poxvoculi: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @petewarden, @poxvoculi: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @petewarden, @poxvoculi: It has been 60 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @petewarden, @poxvoculi: It has been 75 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @petewarden, @poxvoculi: It has been 90 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @petewarden, @poxvoculi: It has been 105 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @aselle: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @suharshs: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Really sorry about the delay here!
We have focused quantization efforts to TensorFlow Lite. So we will likely not update the graph transform tool's quantization code.
Your observation is absolutely correct, and we go to measures to make sure that floating point 0.0 maps exactly to a quantized uint8 value. Closing since we have addressed this in TensorFlow Lite. Thanks @amirjamez !


[QUESTION] Swagger Response With RaiseException

First check

[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.

Description
In the auto-generated Swagger UI, is there any way to include the RaiseException responses?
Additional context
For example, if I follow the guide here, to raise a HTTPException 404 error when the record is not found in the database, I want it to appear in the Swagger UI.

https://fastapi.tiangolo.com/advanced/additional-responses/#additional-response-with-model

https://fastapi.tiangolo.com/advanced/additional-responses/#additional-response-with-model

Thanks for the link.

Thanks for the help here @phy25 ! :bowing_man: :cake:
And thanks @TiewKH for reporting back and closing the issue. :+1:


NTLMGrantClientWithHandshake directory is not available

Description:
<APIM_HOME>/samples/NTLMGrantClientWithHandshake is not available in the APIM pack (RC1).
Content Positioning in Documentation:
Step 2 on this documentation: https://apim.docs.wso2.com/en/next/learn/api-security/oauth2/grant-types/ntlm-grant/#invoking-the-token-api-to-generate-tokens

Its now there in the doc: https://apim.docs.wso2.com/en/latest/design/api-security/oauth2/grant-types/ntlm-grant/


sub-element with dashes is not found

The following sub element can not be found:
env:
  sub-elem: value

To quickly test it:
echo -e "env:\n  sub-elem: value" | niet 'env.sub-elem'

Hello,
First thanks for reporting this bug!
Indeed I can easily reproduce the issue, thanks for the given details.
I'll investigate more deeply to try to fix it.
If you already have some clues don't hesitate to propose a patch by submitting a pull request. We will be happy to review your changes.
Thanks

After further investigation I found that you can fix your issue by using the following syntaxe:
# test.yaml
env:
    elem-sub: value

$ niet env.'"elem-sub"' test.yaml

However I wonder if you can pass YAML format by using echo as you proposed in your previous example.
Locally the YAML parser doesn't recognize it as a valid YAML input.
Please take a look to the examples provided in our README.md.
I hope these info will help you, please confirm that it fix your issue and then feel free to close this bug if it's ok for you.
Thanks,

@rez- any update?

Thanks, you are right, i did not know the syntax!


Locally Loading PDF into Digital Paper PDF Reader

Hi,
First things first, excellent work!
Has anyone figured out how to load a pdf into the digital paper pdf reader locally?  For instance, if I download a pdf on the DPT RP1 itself in Fennic Firefox or in a Mail App on the DPT RP1, how can I "share" it over to the PDF reader on the DPT RP1?  I did some digging and the file structure is pretty opaque.  (One option I thought of was installing dpt-rpt-py on the DPT RPT itself, but I thought I'd ask if anyone has implemented something first.)
Thanks for any tips

One way is you write an Android app/plugin on some PDF app for DPT that supports to download/upload files based on DPT app's API.. it's the most intuitive workaround I can think of

Maybe the official android app will work?

The official android app does not work because it requires Android version >6 and the DPT has only 5.
Also it doesn't seem possible to use qpython because the crypto packages do not install on the DPT.
So that means that there is only one solution: rewriting dpt-rp1-py in javascript and using it from the browser (or package it into an apk with WebView). I am currently working on this port. So far I am able to authenticate and list documents from my computer. Next step is uploading pdfs and somehow hosting the page on the DPT so I can access the page from the browser there.

Update: I succeeded in uploading and downloading pdfs from my chrome browser!
Only thing that is left for now is to try hosting the site on the DPT. Because so far I accessed the page from the DPT but I hosted it on my computer.
But I guess that's not gonna be the biggest problem and soon we will be able to locally load pdfs to the device! :D

Pretty coooool
On Wed, May 20, 2020, 3:43 PM Sir Pilcrow<EMAIL_ADDRESS>wrote:

Update: I succeeded in uploading and downloading pdfs from my chrome
browser!
Only thing that is left for now is to try hosting the site on the DPT.
Because so far I accessed the page from the DPT but I hosted it on my
computer.
But I guess that's not gonna be the biggest problem and soon we will be
able to locally load pdfs to the device! :D
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/HappyZ/dpt-tools/issues/135#issuecomment-631767587,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDVEKRQ5EQLDVMFRNRWKS3RSRMJVANCNFSM4IVS55ZQ
.

Update: check out the initial release on https://github.com/JoeKays/dpts
Hope it works :)

Update: There is an update available, check it out! :D
This update removes most of the limitations and makes the tool quite usable I would say.
You can upload and download documents, create folders and delete them. All from the DPT and also from your computer if you like. You only need a browser and some patience for the setup.
Only real problem is that USB only works on Linux. You have to use WiFi on Windows and Mac. I would love it if someone could help me with making it work on these platforms. I don't have any such device available at the moment...


Add Trajectory mode to the visualiser

Added the Trajectory mode from https://github.com/JamieMair/MuJoCo.jl/issues/41 to the visualiser, including:

Methods to set and get the physics state of a MuJoCo model, where the physics state is defined in the MuJoCo docs
Added docs to demonstrate the trajectory mode
Updated docstring for visualise!

All new functionality has been tested and is working.

Codecov Report

Merging #74 (861a4ee) into main (e1b6922) will decrease coverage by 0.73%.
The diff coverage is 0.67%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main      #74      +/-   ##
==========================================
- Coverage   26.32%   25.60%   -0.73%
==========================================
  Files          22       21       -1
  Lines        5021     5053      +32
==========================================
- Hits         1322     1294      -28
- Misses       3699     3759      +60

Files
Coverage Δ

ext/VisualiserExt/VisualiserExt.jl
0.00% <ø> (ø)

ext/VisualiserExt/util.jl
0.00% <ø> (ø)

src/visualiser.jl
0.00% <ø> (ø)

ext/VisualiserExt/defaulthandlers.jl
0.00% <0.00%> (ø)

ext/VisualiserExt/visualiser.jl
0.00% <0.00%> (ø)

src/MuJoCo.jl
23.33% <11.11%> (-4.80%)
:arrow_down:

ext/VisualiserExt/modes.jl
0.00% <0.00%> (ø)

... and 8 files with indirect coverage changes


java.lang.NullPointerException instead of scala.UnitializedFieldE…

Type of change: bug report

Impact: no functional change

Development Phase: implementation
Thanks @seldridge
class Foo { val x: Int = 1 }
class Bar { println(child.x); val child = new Foo }
new Bar

Run in a repl without and with the -Xcheckinit option on, it'll either be a java.lang.NullPointerException or a scala.UnitializedFieldError.
If using scala.UnitializedFieldError ,  Run mill chisel3.test will report error as below in ModuleSpec
- A desiredName parameterized by a submodule should work
[info] [0.000] Elaborating design...
- A name generating a null pointer exception should provide a good error message *** FAILED ***
  "Uninitialized field:  chisel3/src/test/scala/chiselTests/Module.scala: 75" did not include substring "desiredName of chiselTests.NullModuleWrapper is null" (Module.scala:159)

Can one of the admins verify this patch?

ok to test

ok to test


Airflow log link

Note: Airflow is currently only accessible to maintainers & those given
access. If you would like access to Airflow, please reach out to a member of
@WordPress/openverse-maintainers.

Description

Reproduction

DAG status

https://getimg.ai/ref/Qh6OWmszI ``


Decouple deletion of alerts from deletion of expired audit and histor…

…y records, add method to cleanup deleted alerts with a max limit.

Current coverage is 36.42% (diff: 14.28%)

Merging #235 into develop will decrease coverage by 0.06%

@@            develop       #235   diff @@
==========================================
  Files           260        260
  Lines         14186      14202    +16
  Methods           0          0
  Messages          0          0
  Branches       2381       2385     +4
==========================================
- Hits           5177       5173     -4
- Misses         8293       8310    +17
- Partials        716        719     +3

Powered by Codecov. Last update acffcff...7cfc6e6


Chombo reader does not produce correct ghost type with concave problems.

I've written two good emails describing this problem, so I'll attach that here: My response to the user:Hi Alex, I believe your data is correct and VisIt is handling it wrong. VisIt differentiates between different types of ghost data. One type is "ghost cell exterior to the problem". Another type is "duplicated cell" where the duplicated cell is ghost here, but real somewhere else. For the former ghost type, faces between the real cell and the ghost cell should be rendered ... it's the exterior of the problem. For the latter ghost type, faces between the real cell and the ghost cell should not be rendered ... it's a computational boundary, but doesn't represent anything real from the user's perspective. The problem in this case is that VisIt's CHOMBO reader has too simplistic a test for marking ghost cells as "exterior to the problem". That should be the designation for the cells along the missing octant (the concave portion of the boundary), but they are instead incorrectly getting the "duplicated cell" ghost designation. The simplistic test only checks to see if a cell is outside the logical extents of the problem. That works fine for non-concave boundaries, but, as you have seen, breaks for concave boundaries. So: as you suspected, the issue is CHOMBO VisIt concave boundaries. I filed a bug ticket and hope this gets addressed ASAP. In the interim, I believe it may be worth experimenting with turning off ghost data at the exterior of the problem. I think that may put the VisIt CHOMBO reader in a different processing mode. Finally: I think part of what you want to know is whether you are generating a valid file and getting the simulation you want. FWIW, I spent quite a while looking at the individual patches and I believe you are. My description to Gunther:Each patch is a single cell and has 26 surrounding cells. Some of these cells should be contributing a face to the exterior, but aren't. My first suspicion was that we had a problem with our ghost nodes hack, but that doesn't appear to be the case. Alex has ghost data on the exterior of the problem. And we seem to be, for the most part, handling that gracefully. The volume is a cube with an octant carved out. Consider a cell that abuts that octant. It has a neighbor cell that is in this missing octant. That cell should have the designation "ZONE_EXTERIOR_TO_PROBLEM", but actually has the designation "DUPLICATION_ZONE_INTERNAL_TO_PROBLEM". Looking at the logic in the CHOMBO reader, it has too simplistic of a test: if (i>=lowProbI[level] && i<=hiProbI[level] && j>=lowProbJ[level] && j<=hiProbJ[level] && k>=lowProbK[level] && k<=hiProbK[level]) { ghostCells->InsertNextValue(ghostInternal); } else { ghostCells->InsertNextValue(ghostExternal); } which does not account for concave domains.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 704
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: Chombo reader does not produce correct ghost type with concave problems.
Assigned to: -
Category: -
Target version: -
Author: Hank Childs
Start: 05/11/2011
Due date:
% Done: 0%
Estimated time:
Created: 05/11/2011 02:43 pm
Updated: 05/17/2011 07:35 pm
Likelihood: 2 - Rare
Severity: 4 - Crash / Wrong Results
Found in version: 2.2.2
Impact:
Expected Use:
OS: All
Support Group: DOE/SciDAC
Description:
I've written two good emails describing this problem, so I'll attach that here: My response to the user:Hi Alex, I believe your data is correct and VisIt is handling it wrong. VisIt differentiates between different types of ghost data. One type is "ghost cell exterior to the problem". Another type is "duplicated cell" where the duplicated cell is ghost here, but real somewhere else. For the former ghost type, faces between the real cell and the ghost cell should be rendered ... it's the exterior of the problem. For the latter ghost type, faces between the real cell and the ghost cell should not be rendered ... it's a computational boundary, but doesn't represent anything real from the user's perspective. The problem in this case is that VisIt's CHOMBO reader has too simplistic a test for marking ghost cells as "exterior to the problem". That should be the designation for the cells along the missing octant (the concave portion of the boundary), but they are instead incorrectly getting the "duplicated cell" ghost designation. The simplistic test only checks to see if a cell is outside the logical extents of the problem. That works fine for non-concave boundaries, but, as you have seen, breaks for concave boundaries. So: as you suspected, the issue is CHOMBO VisIt concave boundaries. I filed a bug ticket and hope this gets addressed ASAP. In the interim, I believe it may be worth experimenting with turning off ghost data at the exterior of the problem. I think that may put the VisIt CHOMBO reader in a different processing mode. Finally: I think part of what you want to know is whether you are generating a valid file and getting the simulation you want. FWIW, I spent quite a while looking at the individual patches and I believe you are. My description to Gunther:Each patch is a single cell and has 26 surrounding cells. Some of these cells should be contributing a face to the exterior, but aren't. My first suspicion was that we had a problem with our ghost nodes hack, but that doesn't appear to be the case. Alex has ghost data on the exterior of the problem. And we seem to be, for the most part, handling that gracefully. The volume is a cube with an octant carved out. Consider a cell that abuts that octant. It has a neighbor cell that is in this missing octant. That cell should have the designation "ZONE_EXTERIOR_TO_PROBLEM", but actually has the designation "DUPLICATION_ZONE_INTERNAL_TO_PROBLEM". Looking at the logic in the CHOMBO reader, it has too simplistic of a test: if (i>=lowProbI[level] && i<=hiProbI[level] && j>=lowProbJ[level] && j<=hiProbJ[level] && k>=lowProbK[level] && k<=hiProbK[level]) { ghostCells->InsertNextValue(ghostInternal); } else { ghostCells->InsertNextValue(ghostExternal); } which does not account for concave domains.
Comments:
Alex sent a simpler data file.

0715_tst_elShaped_phi__1_.h5.zip
0715_tst_elShaped_phi.h5.zip


After loading a session, adding plots does not work

Steps to reproduce:

Open a session (eg http://spot.phenomldata.org/#session=https://s3-eu-west-1.amazonaws.com/www.phenomldata.org/session_susyai.json)
Add a plot (eg bar plot of some variable)
Note it doesn't work
Refresh the page
Manually select dataset
Add the same plot of step 2
Note it works

Video:
https://www.youtube.com/watch?v=vIbbGNEIZfk
I can reproduce this issue with any dataset and any plot variable

Thank you for reporting. I could recreate the issue.

fixed in https://github.com/NLeSC/spot master branch


server with password

Is there any method for server which can be connected by host with password?

Pomerium

is able to use like this   auth=HTTPBasicAuth(username, password) to  set it's will be work


Bigger font?

Any way to increase the font size? Kind of small on my 3440x1440 display.

Hi,
Sure it should be possible! As you may not know, ValheimTooler is in maintenance mode meaning I won't implement it myself but if anyone is willing to do it, open contribution are appreciated!
Kind regards,
Astropilot


Improve support for triggered cameras

Currently  a CameraSensor can be configured to be a triggered camera by setting the SDF  element to true. A triggered camera does not publish images unless a message is received on the trigger topic.
Here are some proposals for improving support for triggered cameras:

Allow instant on-demand camera image rendering:

The camera sensor currently still respects it's update_rate, meaning the camera does not update immediately when the trigger msg is received, instead it still waits for its time to update. For simulation running at low RTF, the wait time can be long.

Extend support for <triggered> SDF param to other camera sensors

currently only supported by CameraSensor. Consider making it generic and extending to other types of camera sensors, e.g. depth, rgbd, etc

Nice to haves:

Provide an API to toggle the triggered property of the Camera sensor

Alternatives considered
As opposed to changing the timing on how triggered cameras work, we can could add a new SDF parameter for instant on-demand camera image generation. This preserves existing behavior of triggered cameras. However, I'm now sure if there is a common use case for cameras to respect their update rates when they are triggered.
Implementation suggestion

Refactor CameraSensor's logic for loading and handling the  SDF param, make it generic so that it can be used by other camera sensor types.
In Sensor::Update function, there is a check to see if it's time for a sensor to update. Some options to make a sensor update immediate:

set the update_rate to 0
set nextUpdateTime to 0
add a new bool flag to indicate the sensor has been triggered

<triggered> support for depth cameras would be great, especially for applications where a very high density pointcloud is needed. Currently, that leads to poor RTF and UX on those simulations, since moving around in Gazebo can become very laggy.


Add new benchmarks and benchmarker functionality (try 2)

Fixes since the last PR

Use ISO8601FormatStyle to fix the linux build failure
Remove diff filtering for comparison results (just make sure it's more than a picosecond to remove any diffs from floating point rounding)
Add a createBenchmark.py util script to create benchmarks + register them. After looking around at swift-collection-benchmark and the main swift repo's benchmarks, this seems to be the best way of doing things

@swift-ci test

@swift-ci test

@swift-ci test


It triggers MessageLog event 3 times

Expected behavior
I want to see just one message in browser:
Event caught: Route / opened

Observed behavior
I see three messages in browser:
Event caught: Route / opened
Event caught: Route / opened
Event caught: Route / opened

Steps to reproduce

install laravel 5.5
install bugsnag-laravel (latest version)
follow installation instructions
As it says: If you’d like to keep logging to your original logger as well as Bugsnag, you can bind 'bugsnag.multi' rather than 'bugsnag.logger'. I want to be able to log my messages to text log as well as to bugsnag.
in app/Providers/AppServiceProvider.php:

<?php

namespace App\Providers;

use Illuminate\Log\Events\MessageLogged;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    public function boot()
    {
        $this->app->alias('bugsnag.multi', \Illuminate\Contracts\Logging\Log::class);
        $this->app->alias('bugsnag.multi', \Psr\Log\LoggerInterface::class);
    }

    public function register()
    {
        // I need to listen to this event
        \Event::listen(MessageLogged::class, function (MessageLogged $event) {
            echo "Event caught: $event->message \n";
        });
    }
}

I added a web route like this in routes/web.php:

Route::get('/', function () {
    \Log::info("Route / opened");
});

run local server from the root folder of the project (php 7.2):
php -S <IP_ADDRESS>:8821 -t public
open home page in browser: http://<IP_ADDRESS>:8821

Version
2.14.1 (latest at the moment)
php 7.2
laravel 5.5
Comments
File src/EventTrait.php has the logic responsible for that. As I understand, when the BugsnagLogger is combined with the built-in Laravel logger both fire this event. Thus one cannot reliably listen to the event since it can be fired multiple time for the same message.

Hi Hi @lezhnev74, this seems to be an issue with our latest implementation.  The default MultiLogger contains 3 sub-loggers: the apps log, the base bugsnag.logger, and the apps events logger.  The bugsnag.logger contains a further two targets - the bugsnag instance, and the apps events logger again.
It seems we're logging a message to the apps log, and dispatching two messages through the apps events logger, creating three MessageLogged events total.  I need to verify this and discuss a course of action with colleagues for now, but thanks for bringing this up.  I'll update you when a solution or action is determined.

Hi @Cawllec have you made any progress on this bug?
We are also seeing this on the \Log::listen(...) function as well which most likely uses the same event hooks.

I must say that my project apideveloper.io is highly affected by this issue (this service logs all messages to the external storage and I observe multiple entries as a result). If you can increase the priority of this subject that would be most appreciated!

Happy new year! 🌴 Can you refresh the state of this issue?


operator-sdk generate fails to work to work with modules

Bug Report

What did you do?
$ operator-sdk generate k8s --verbose
DEBU[0000] Debug logging is set
FATA[0000] Project not in $GOPATH

go.mod and go.sum are present. The project is valid and it can be built manually.
What did you expect to see?
Successfully generating k8s zz_*.generated.go files.
What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).
Environment

operator-sdk version:
operator-sdk version: v0.8.1, commit: 33b3bfe10176f8647f5354516fff29dea42b6342

go version:
go version go1.12.6 darwin/amd64

Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-20T04:49:16Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:32:14Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
minikube

Are you writing your operator in ansible, helm, or go?
go

Possible Solution

Additional context
Add any other context about the problem here.

there is no such issue on the master branch. Will stick to it for a while...

@nrvnrvn so you are saying this was fixed in master branch but does not work in 0.8.1 release?
We should maybe cherry-pick the fix to the 0.8.2 release? cc @hasbro17 @estroz

Yes I'll release v0.8.2 today or tomorrow.

@nrvnrvn are you running operator-sdk generate openapi in $GOPATH/src?

Right, I’d switched to go modules and that’s where all the fun began )))

Looks like this issue is solved?

solved with the release of v0.9.0


Local test

Thank you for contributing to the Cohere Toolkit!

[ ] PR title: "area: description"

Where "area" is whichever of interface, frontend, model, tools, backend, etc. is being modified. Use "docs: ..."  for CI changes.
Example: "deployment: add Azure model option"

[ ] PR message: Delete this entire checklist and replace with

Description: a description of the change
Issue: the issue # it fixes, if applicable
Dependencies: any dependencies required for this change

[ ] Add tests and docs: Please include testing and documentation for your changes

[ ] Lint and test: Run make lint and make run-tests

AI Description

This PR introduces backend unit tests and makes changes to the Makefile and other configuration files.
Changes:

Added a new workflow file, backend_unit_tests.yml, for running backend unit tests.
Modified backend_tests.yml to ignore src/interfaces/** path.
Updated the Makefile with new targets for running unit tests, integration tests, and other development tasks.
Created a new Alembic configuration file, alembic-test.ini, for database migrations.
Removed the overwrite of the sqlachemy.url value in src/backend/alembic/env.py.
Updated the default user ID and name values in src/backend/alembic/versions/ed17f144f4bf_.py.
Modified the PYTEST_CONFIG_PATH in src/backend/config/settings.py to point to the unit tests folder.
Updated the DATABASE_URL in src/backend/pytest.ini to match the new Alembic configuration.
Added error handling for the case where authorization is not split correctly in src/backend/services/auth/request_validators.py.
Refactored the import statements in multiple test files to use the unit tests modules instead of the old integration tests modules.
Removed the src/backend/tests/model_deployments/mock_deployments folder and updated the corresponding import statements.

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

Project coverage is 76.90%. Comparing base (b05ce43) to head (d707ec9).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #648      +/-   ##
==========================================
- Coverage   77.10%   76.90%   -0.20%
==========================================
  Files         238      233       -5
  Lines       10455    10332     -123
==========================================
- Hits         8061     7946     -115
+ Misses       2394     2386       -8

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


Roll Flutter Engine from 6a54862353b4 to 221b04909117 (3 revisions)

https://github.com/flutter/engine/compare/6a54862353b4...221b04909117
2022-07-01<EMAIL_ADDRESS>Paint tab characters as a single space (flutter/engine#34389)
2022-07-01<EMAIL_ADDRESS>Disables flaky test FlutterMenuPluginTest.TestSetMenu (flutter/engine#34429)
2022-07-01<EMAIL_ADDRESS>Add gen_snapshot for windows. (flutter/engine#34304)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Add packages: network-simple, pipes-aeson, pipes-attoparsec, pipes-binary, pipes-network

There's one dependency problem, identified by Travis:
lens-family-core-1.2.0 depended on by:

pipes-binary-<IP_ADDRESS> (==1.0.*). Renzo Carbonara<EMAIL_ADDRESS>@k0001. @k0001

Note that lens-family-core is a test suite dependency.

@k0001 Are you interested in following up on this?

Yes Michael, definitely, I just haven't setup Stackage locally yet so that
I can test this myself there. I'll try to do it during the day. Thank you.
Le 22 janv. 2015 10:17, "Michael Snoyman"<EMAIL_ADDRESS>a
écrit :

@k0001 https://github.com/k0001 Are you interested in following up on
this?
—
Reply to this email directly or view it on GitHub
https://github.com/fpco/stackage/pull/405#issuecomment-71018497.

Michael, what is the correct thing to do here? lens-family-core idd s not my package, so I can't just add it to the YAML file with me as a maintainer. Should I add pipes-binary to skipped-tests?

@k0001 preferably you'd update the pipes-binary test suite to be compatible with the latest lens-family-core.

OK, I uploaded a new version of pipes-binary and now stackage nightly isn't complaining any more. I think now I get the idea of how Stackage is supposed to be used.

Looks good now!


Light mode 🔆

I have this in a branch (6594633bf679429da32242c5c4b8fc1c47237805) but I'm just not happy with the contrast between the important info (red/yellow) and white. So, I'm not going to implement this.

(For reference:)


Deprecate Libp2p Transport

We have already deprecated the libp2p flags. The next step here is to remove libp2p deps from the codebase, and as an option for users to provide when running a node.

What state is this in? Should we add a issue regarding the removal of libp2p from the codebase? @wdbaruni @frrist


Is there an example file to run tesseract console by c# from win10

I want to use tesseract 4.1.0 windows 10 binary version in c# forms application.
Can I get the ocr result directly by string variable?(not the text file)
Is there an example for it?
or maybe is there a better way to use it for ocr in c#?
Is there a method to import tesseract 4.1.0 to c#?

Please use the user forum for questions.


Add token to pre-commit autoupdate workflow

Committed via https://github.com/asottile/all-repos

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
257

Relevant Lines:
309

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
257

Relevant Lines:
309

💛  - Coveralls


make hook scripts stdout/stderr outputs something else than green/red

Colors in stderr/stdout are usually pretty misleading and we should use colors more sparingly. I think gray color would be better for hook command outputs.

FgHiBlack for both stderr & stdout?

btw, psql is on the Cloud Shell image, which I'm sure you guessed.

gray seems better in my shell


Update and Verify Go version >= 1.15.5

Make sure Go version is >= 1.15.5
Covers at least CVE-2020-28362

 Update and Verify Go version >= 1.15.5

Engineering:

We reference the Go docker images by the 1.15 tag rather than a 1.15.x tag, so we automatically upgrade to the newest patch release when we have a new build.


Image Sensor Not Rendering

From: @EdvardGrodem in issue #3
images from cameras do not encode correctly and appears blue in Rviz. Does anyone know how to fix this?

I suspect that this is an issue with the underlying Unity rendering driver.  The image/camera renders require Vulkan drivers (OpenGL will likely not work).  Can you verify that the Vulkan driver is setup properly as outlined in: https://github.com/fsstudio-team/ZeroSimROSUnity#setting-up-a-new-unity-project

I just tested OpenGL on my system.  It does render and I can visualize in RViz but the colors are incorrect.  Are you sure the camera is attached to something in the scene and not falling through the floor or pointed in a unexpected direction?  Can you try to set the debug parameter in the ZORGBCamera compontent, see image below.  The camera sensor image should be rendered when Unity is running (it will be upside down, that is okay).

Yes, enabling Vulken fixed the issue! I had some stability problems and forgot that I turned it off to test if that improved stability. Thanks a lot!


minor bugfix: don't overwrite duplicate column name

line 247 incorrectly overwrites self.lcsc with a new column named 'Type', erasing it. line 240 is in the right here
to fix, we just store this in a different variable
this wasn't affecting anything because it wasn't used by anything but, was confusing and maybe someday could cause some future developer some heartache

hm.... sorry it appears I have some kind of line ending issue. this is a 1-line code fix, but it's flagged the entire file as changed. woops. will resubmit.

I will re-create this


Feature/#19731: Implementar APM no serviço do Agent

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Various Firebase types does not conform to NSSecureCoding

[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your environment

Xcode version: 10.3
Firebase SDK version: 5.16
Firebase Component: Core, Messaging
Component version: 5.16

[REQUIRED] Step 3: Describe the problem
Our security team scanned our code and dependencies for vulnerabilities and found that the following classes did not conform to NSSecureCoding making them vulnerable to object substitution attacks:
FIRMessagingTopicBatch, FIRInstanceIDAPNSInfo, FIRInstanceIDTokenInfo and FIRMessagingPendingTopicsList
Steps to reproduce:
Open up the header files, note that they conform to NSCoding, and not NSSecureCoding.
Relevant Code:

https://github.com/firebase/firebase-ios-sdk/blob/master/Firebase/Messaging/FIRMessagingPendingTopicsList.h
https://github.com/firebase/firebase-ios-sdk/blob/master/Firebase/InstanceID/FIRInstanceIDAPNSInfo.h
https://github.com/firebase/firebase-ios-sdk/blob/master/Firebase/InstanceID/FIRInstanceIDTokenInfo.h

We removed NSCoding from Messaging but not InstanceID yet. InstanceID is deprecated and will be removed from Messaging soon. We will keep this open for now.

This was addressed for Messaging as noted above. InstanceID is no longer used by Firebase.


Cargo Upgrade

Ran cargo upgrade (after almost 2 years) and start fixing the issues.

@vkgnosis  - fixed, note that I wasn't sure about url and rouille
which went like this
rouille 3 -> 3.3.1
url 2 -> 2.2.2

So I stuck with v3 and v2  respectively


[ADD ME TO THE ORGANIZATION]

Name: Vijay CN
Location: Online
Interest: Web Dev | Python Developer | Linux | Networking
Discord username(optional):-
Why do you want to join?

I want to join because learn and supply the material that i have learned so far and yet to learn stuff. (also to meet some cool people😜)

You can also join our Discord community here
Feel free to check out other cool repositories of the DevsInTech Community here.

@vijay2249 Thanks for your interest. Invitations have been sent to you. Kindly accept it and make your membership public.