build: ignore crd not found in uninstall/undeploy targets

uninstall and undeploy targets both want to delete the CCRuntimeConfig
CRD. When we call these targets one after another the second one will
always fail. This is because we add 'ignore-not-found=false' when we
call kubectl delete.
It is safe to set ignore-not-found=true in the undelete/undeploy case
because if a resource is not there we don't have to delete it.
Signed-off-by: Jens Freimann<EMAIL_ADDRESS>

@jensfr I'm wondering if we need to change the default from the operator-sdk provided one, since the Makefile targets explicitly mentions about using ignore-not-found=true if required:
https://github.com/confidential-containers/operator/blob/main/Makefile#L137
https://github.com/confidential-containers/operator/blob/main/Makefile#L146
Should this behaviour be instead documented leaving the default as-is?

@jensfr I'm wondering if we need to change the default from the operator-sdk provided one, since the Makefile targets explicitly mentions about using ignore-not-found=true if required: https://github.com/confidential-containers/operator/blob/main/Makefile#L137 https://github.com/confidential-containers/operator/blob/main/Makefile#L146
Should this behaviour be instead documented leaving the default as-is?

You're absolutely correct. @wainersm this PR isn't even needed. Just call it with make ignore-not-found=true uninstall undeploy and the effect should be the same.

@jensfr I'm wondering if we need to change the default from the operator-sdk provided one, since the Makefile targets explicitly mentions about using ignore-not-found=true if required: https://github.com/confidential-containers/operator/blob/main/Makefile#L137 https://github.com/confidential-containers/operator/blob/main/Makefile#L146
Should this behaviour be instead documented leaving the default as-is?

You're absolutely correct. @wainersm this PR isn't even needed. Just call it with make ignore-not-found=true uninstall undeploy and the effect should be the same.

how end user will uninstall the operator? If not using those make targets, it would be better to change on CI.

make help describe the options that are available.
What you can do is run these commands in the CI.
make uninstall ignore-not-found=true
make undeploy ignore-not-found=true

Well, I'd say end users create a subscription via OLM. But that's probably a discussion for https://github.com/confidential-containers/operator/pull/63
The two make targets are the correct ones two get rid of everything

closed because the change is not needed, instead one can set the ignore-not-found variable


UI is broken in @scalar/hono-api-reference on v0.5.147

What happens?
Hi,
This has been reported on other packages as well and it seems it was fixed, but unfortunaly not in hono package I assume.
I tried to revert back to v0.5.146 and v0.5.146 but there were broken as well.
see the sidebar or tri to click test request, you should see a blank screen.
What did you expect to happen?
the test request screen should work
OpenAPI Document
https://public-api.mando.cx/swagger

a quick fix for now is to pin the scalar version to 1.25.11
app.get(
	'/swagger',
	apiReference({
		cdn: 'https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>		spec: {
			url: '/openapi.json',
		},
	}),
)

hey @omarkhatibco @NotReallyPrince wouod you be able to share a link to your docs or your openapi spec? :)
can also dm it to me<EMAIL_ADDRESS>

Hi @marclave,
Just sent you an email with the links, thanks for your help

Hi @marclave,
Just sent you an email with the links, thanks for your help


There is no index.css file when installing

I'm submitting a ...  (check one with "x")
[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior
There is no index.css file when installing in the release folder. So when importing it in my app the build fails.
Expected behavior
It should be this file.

Reproduction of the problem
Install the library and import the CSS files as the documentation says.
Please tell us about your environment:
OS X Sierra 10.12.3.
Table version: 0.8.x
"@swimlane/ngx-datatable": "^10.0.1"
Angular version: 2.0.x
4.0.0

Can you post the error? I don't believe the index.css is needed anymore.

Yeah, is this one:
Module not found: Error: Can't resolve<EMAIL_ADDRESS>in '/Users/aletormat/Dev/smartua/frontend/src/app/components/datatable'

I have the same issue. Can you please update documentation if it is not needed anymore?

index.css should not be needed as the ngx-datatable project compiles the datatable.component.scss file and sets the global CSS support for you. See below or here:
datatable.component.ts
encapsulation: ViewEncapsulation.None,
styleUrls: ['./datatable.component.scss'],

and here where webpack supplies a scss loader:
webpack.common.js
          test: /\.scss$/,
          use: [
            { loader: 'to-string-loader' },
            { loader: 'css-loader' },
            {
              loader:'postcss-loader',
              options: {
                sourceMap: true,
                plugins: [autoprefixer]
              }
            },
            {
              loader: 'sass-loader',
              options: {
                sourceMap: true
              }
            }
          ]

@amcdnl I know it's not directly related but do you know if there is a way to apply user-supplied theming (css, scss, etc) without enabling global css support aka ViewEncapsulation.None? The css applied in the project is global and requires all class names to be super long to avoid collision.

@wizarrc - I've been playing with view encapsulation lately, Angular brought out a new ::deep operator that might enable this to be easier but haven't had a chance to play w/ it much yet.

hmm, interesting. Is that related to ::shadow and /deep/ that have been deprecated in chrome because they break encapsulation? I noticed they recently added ::deep to angular and was quite confused if it's a deprecated feature in browser land.

@wizarrc - see https://twitter.com/stephenfluin/status/892766742241353728

Thanks! Sounds like ::deep is good for the foreseeable future, at least until there is something better.

Can we close this given all the info above?

@amcdnl I think this comment clears up the confusion. In the 10.0.0 release, the index.css file was (inadvertently?) physically removed from the release folder in the repo, but not removed from the docs.
Since it's actually a breaking change that is not mentioned in the changelog.md file. People upgrading versions, where they previously relied on index.css being imported, even though it is redundant and unnecessary, are broken by just doing an npm update.
Options:

Add back index.css to the release folder. (easy)

All mentions of index.css be removed from the docs and update changelog.md to include removal of index.css from the project with instructions that everyone should remove it from their project upon upgrading being that it's unnecessary. (recommended)

A side note: themes.md states:

Out of the box, the data-table is not styled.

That simply is not true anymore, as it has a default style that can be overridden. Looks like the docs in general might need some updating.

I added it back to help prevent breaking changes. Done in 10.0.2


General understanding: What is it in nodejs >=v0.12 that introduced nicely nested ~/.nvm/node/versions/[version] path?

After some experimentation to try to retrace my steps installing a really really old version of node, I narrowed down that nodejs versions < 0.12.0 got installed in a path like ~/.nvm/v0.10.48, for example, but >=0.12.0 introduced nicer installation paths like ~/.nvm/versions/node/v0.12.0 (notice the clean versions/node placement).  I couldn't figure out from nvm codebase where that change was introduced, and am just curious: Just getting to this realization really saved me a lot of grief just now! :D

I introduced that change before 0.12 came out, and i preserved the locations for older installations of node, so as not to break things for people.


Experiment: C level array parititoning vs partition pragma

Experiment
Hypothesis: Manually partitioned arrays at C level perform as well as the partition pragma
Program 1: Two dimensional array with partition pragmas on both dimensions (say with 2 banks). Access each element of the array and increment it by 1 for 1000 iterations.
Program 2: 4 two dimensional arrays representing the partitions for the array in prog 1. A function with manual arbitration logic for selecting the right array based on the input arrays. Only use the function to access and update the elements of the arrays in the same way that prog 1 does.
Rationale
I'm writing the Views section with a "Challenges in implementation" subsection which shows why the primitives exposed by various HLS backends are not the right one.
One challenge in implementing views is we can't take slices of multidimensional arrays in C. We assume that this will be easy to do in a hypothetical RTL backend. Let's try to implement this at the C level and see how well it does and make sure we have an airtight argument backed up by an experiment.
Running this experiment also makes it easier to argue why views should be first class feature supported by the compiler.
@sampsyo can I ping you to do this? I'll write up the C code tonight if someone can try to push it through synthesis / estimation tomorrow.

Good call! I would be interested to see this too. I really have no idea whether the tool’s built-in banking will have “magical” efficiency we can’t attain otherwise. Seems like we could even test this with a single-dimensional array, although a multi-dimensional one is of course where it really matters for our backends.
Happy to run some jobs when I get a moment. But FWIW, here is my favorite way to run jobs from home:
$ ssh -NL8000:gorgonzola:8000 waffle
$ export BUILDBOT=http://localhost:8000

Tracked in https://github.com/cucapra/fuse-benchmarks/pull/93


Fix length of in fixture

Fixes #98
Maybe I misunderstood something?

Fixes #98
Maybe I misunderstood something?

I agree with you from what I understood


Remove PHP short open tags from page_list_form

PS: only this page_list_form.php file contains short tags, no other core files need to be fixed.


Fix exception message

Description
Fix exception message
Type of change

[ ] Refactor
[ ] New feature
[x] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

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

Comparison is base (1f5a60f) 95.93% compared to head (cc52a69) 95.94%.
Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #407   +/-   ##
=======================================
  Coverage   95.93%   95.94%
=======================================
  Files          32       32
  Lines        1033     1035    +2
=======================================
+ Hits          991      993    +2
  Misses         42       42

Files
Coverage Δ

ols/app/endpoints/ols.py
100.00% <100.00%> (ø)

ols/src/cache/cache.py
100.00% <100.00%> (ø)

/approve
/lgtm


support LargeUtf8 in sort kernel

This PR adds LargeUtf8 support for the sort kernels. Closes #25

Codecov Report

Merging #26 (c29f49a) into master (463f88f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #26   +/-   ##
=======================================
  Coverage   82.49%   82.49%
=======================================
  Files         162      162
  Lines       43522    43530    +8
=======================================
+ Hits        35902    35910    +8
  Misses       7620     7620

Impacted Files
Coverage Δ

arrow/src/compute/kernels/sort.rs
94.32% <100.00%> (+0.04%)
: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 463f88f...c29f49a. Read the comment docs.


The process misses to export all firehose tags keys

We are using some metrics customization on the messsages sent to firehose (with tags Keys) . We can see those tags in the firehose (with cf nozzle) , but they are lost on the firehose exporter end point .
Those tags contain ApplicationId and AppInstance ID , so that it's possible to retrieve custom metrics in Prometheus for instance .
Those tags are standard regarding the documentation (https://github.com/cloudfoundry/dropsonde-protocol/blob/master/events/README.md) , so it's important that we can get them .
Thanks

Glad to accept a contribution with those changes :) Bear in mind that labels in prometheus must be consistent on all metrics from a particular family, so this means that all events of the same type should have the same tags, or you will need to implement some logic at the exporter to deal with this.

I think I have identified the place in the code where the tags get lost. I will try to figure out a PR.

@jointcloudfoundry I just tested the patch in the above mentioned pull request and it worked for me. Can you give feedback, if the behavior is now what you expect?

Hello mathias . I've just tested your patch (pushing to cloudfoundry the app from your repo https://github.com/mathias-ewald/firehose_exporter.git , on the right branch)
I confirm that this solve the issue above . We can see all the tags in the output of firehose-exporter .

That's awesome! Now we need to wait for a reviewer to accept the PR, I guess :) @frodenas


fix repo links

What this PR changes
Fixed the repo links in the README to use the organization repo.

Thanks @lgraubner!


Ingress ClassName for helm chart 1.15.28

Describe the bug
While using helm chart 1.15.28 I noticed for me nginx annotation kubernetes.io/ingress.class doesn't work. So I had to use it like this
uiIngress:
    # -- Use Ingress
    enabled: true
    className: gopher-jino
    # -- Additional annotations for the Ingress resource.
    annotations:
      nginx.ingress.kubernetes.io/rewrite-target: /$1
      #kubernetes.io/ingress.class: nginx

I don't see className parameter in helm chart. So may be we need to update it ?
Expected behavior
Attach an nginx ingress Class and create an LB
Version / Cluster

Which testkube version?

 kubectl testkube version                                                                                4m 22s  ⎈ krupesh2/testkube 09:00:10 am

Client Version 1.15.20
Server Version 1.15.20
Commit 0f6ee4996613e46d86a23787811dc755d91377a2
Built by goreleaser
Build date 2023-11-21T07:52:09Z

What Kubernetes cluster? (e.g. GKE, EKS, Openshift etc, local KinD, local Minikube)
EKS
What Kubernetes version?
1.28

thank you @rr-jino-jose pinging @ypoplavs


AllowCloudRecording should be AllowTranscription

Hi,
I see there's is typo in the use case scenario section
333724
In the last scenario you mention

I want transcription to be disabled for the majority of the users but selectively enable specific users who are allowed to transcribe.
Confirm Global CsTeamsMeetingPolicy has AllowCloudRecording = False.

AllowCloudRecording should be AllowTranscription

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

ID: 976b8a9b-5a3e-1f3b-b848-d1dfbfd3389d
Version Independent ID: 2b13a471-3baf-0086-439a-f94abb162fd6
Content: Teams cloud meeting recording - Microsoft Teams
Content Source: Teams/cloud-recording.md
Service: msteams
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Can anyone look a these issues / pull requests

I'm writing here, because in the other repos no one seems to respond!
Can anyone look at:
https://github.com/Polymer/polymer-cli/pull/878
https://github.com/webcomponents/shadydom/pull/187

ths https://github.com/webcomponents/shadydom/pull/187 is closed

The webcomponents issue has been resolved. I have also pinged the tools team regarding the CLI issue. I hope we can get that PR going as well.
Given the above fact, I am closing this issue for now. Feel free to ping the CLI PR in a week or so if there is still not a response from the team.

thx

can you also ping the team about https://github.com/Polymer/polymer/issues/4859

@TimvdLippe maybe you can also trigger the CLI Team to look at these issues:
https://github.com/Polymer/polymer-cli/issues/886
https://github.com/Polymer/polymer-cli/issues/701
https://github.com/Polymer/polymer-cli/issues/633
I think they are all the same, but not yet solved...

These issues will be addressed when we get to them. Right now the modulizer
is on focus in preparation for Polymer 3.
On Thu, 16 Nov 2017, 21:46 Jochen Kühner<EMAIL_ADDRESS>wrote:

@TimvdLippe https://github.com/timvdlippe maybe you can also trigger
the CLI Team to look at these issues:
Polymer/polymer-cli#886
https://github.com/Polymer/polymer-cli/issues/886
Polymer/polymer-cli#701
https://github.com/Polymer/polymer-cli/issues/701
Polymer/polymer-cli#633
https://github.com/Polymer/polymer-cli/issues/633
I think they are all the same, but not yet solved...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/polymer/issues/4931#issuecomment-345056991,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrDb7ytxUqsiAnGMk9NL4BjTbBr9WIMks5s3J8XgaJpZM4Qb-yC
.

maybe it‘s possible to help you? where‘s help needed?

I dont manage that repository. However, for this repository I will do
another cleanup and then mark issues which you can help out with. Stay
tuned!
On Fri, 17 Nov 2017, 19:19 Jochen Kühner<EMAIL_ADDRESS>wrote:

maybe it‘s possible to help you? where‘s help needed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Polymer/polymer/issues/4931#issuecomment-345321889,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrDb-HBGGL_Z7X0amuqmKLjozSw2EHAks5s3c4lgaJpZM4Qb-yC
.

@jogibear9988 I believe that issue is related to how babel-preset-minify handles unicode characters. Not sure but it might be this issue.

I‘ve also added a issue at babel already https://github.com/babel/minify/issues/706 ;-)

I think 2 of the issues are fixed in babel-minify (but not yet in a release) and for the 3rd one I created a fix (https://github.com/babel/minify/pull/733). I look that they'll create a release when the 3rd fix is in, so polymer/cli could be updated!


Set params encoding to Rack

This is necessary for filtering with array parameters

:shipit: released on version 1.2.0


Adding Known Issues section to the web-view doc entry

add Intelij editor internal files to .gitignore
add known issues section
remove ide config files from the repo(please recreate them locally if needed)

 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.


Kenkoooo/list hide experimental

Codecov Report

Merging #326 into master will decrease coverage by 16.68%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #326       +/-   ##
==========================================
- Coverage   19.27%   2.59%   -16.69%
==========================================
  Files          71      52       -19
  Lines        1909    1349      -560
  Branches      272     187       -85
==========================================
- Hits          368      35      -333
+ Misses       1470    1313      -157
+ Partials       71       1       -70

Impacted Files
Coverage Δ

...ms-frontend/src/pages/ListPage/DifficultyTable.tsx
0% <0%> (ø)
:arrow_up:

atcoder-problems-backend/src/sql/streak.rs

atcoder-problems-backend/src/sql/models.rs

...tcoder-problems-backend/src/sql/rated_point_sum.rs

...er-problems-backend/src/lambda/time_submissions.rs

atcoder-problems-backend/src/lambda/io.rs

atcoder-problems-backend/src/crawler.rs

...tcoder-problems-backend/src/sql/contest_problem.rs

atcoder-problems-backend/src/sql.rs

atcoder-problems-backend/src/sql/simple_client.rs

... and 10 more

Continue to review full report at Codecov.

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


chore: merge last changes from dAppBooster(core)

Description:

Merge last changes from dAppBooster(core)
Fix conflicts.
Fix broken demos.

fixed the build (wrong env variable due to the other temp PR, sorry)

@nicosampler I may have broken something, but it took quite a long time (actually, changing the window focus for the transaction request to actually appear in the wallet... well, I think it's my setup and has nothing to do with the implementation, but anyways).

Then, when all finish, I get the button asking for me to Send 10K which I no longer have, and get an error toast (is this last one intentional to display the error?)

@gabitoesmiapodo it's still in draft for some reason?

@fernandomg was this broken for some reason?

@fernandomg

I may have broken something, but it took quite a long time (actually, changing the window focus for the transaction request to actually appear in the wallet... well, I think it's my setup and has nothing to do with the implementation, but anyways).

It's you.
@fernandomg @nicosampler

Then, when all finish, I get the button asking for me to Send 10K which I no longer have, and get an error toast (is this last one intentional to display the error?)

This was an existing error, the demo doesn't detect that the transaction has finished and the UI is not updated to reflect that. You have to reload the page so it changes.
Fix here? Later?

Fix here? Later?

Later

@fernandomg was this broken for some reason?

The last failure was due to the SGs URLs, that I changed its structure 😬


Swag Portal: More flexible authentication options

swagportal currently uses PAM to authenticate, which means all users must have accounts recognized by the OS on the Linux server where the portal is hosted. It would be nice to be able to offer alternatives like social media login, oAuth, etc.
Options for doing this include:

Expanding the existing PHP-based portal to incorporate PHP-based auth libraries. A quick search reviews a few candidates:

PHP Native oauth support
HybridAuth

Switch to a framework with built-in (or easily added) support for multiple authentication options

Some work has been done on a Django-based portal, but it isn't complete
Might be worth considering a lighter-weight framework like Flask

My suggestion: HybridAuth looks promising. It would be great if someone could start by looking into it. Even if we move to something else later, this might be the easiest way to get more flexible auth set up quickly.

Overview of OAuth https://en.wikipedia.org/wiki/OAuth

Ideas around implementing this... The goal for the "authentication" is basically to populate the $_SESSION["username"] variable with something, this is checked in https://github.com/tunapanda/swagportal/blob/master/src/controllers/MainController.php on line 69.
So... One way to do it would be to have a configuration variable in the config.php file that chooses between different configuration options. And there would be 2 options, the current PAM method, and then a new one based on maybe HybridAuth, and the option would select which one should be used...

If we go with HybridAuth, they have an example in their user manual that it looks like we could use to offer both pretty easily. That way, no config tweaking would be needed unless we want to let people explicitly not allow one method or another.

...and actually, looking more closely at that example, I think it's way more that we need. In the example they're actually itegrating social auth into an existing login system. All we really need is to present the social auth buttons next to the un/pw prompt, which should be even easier.

Yep, I think HybridAuth is the way to go...
// Micke
On Wed, Apr 22, 2015 at 8:20 PM, Brad Smith<EMAIL_ADDRESS>wrote:

...and actually, looking more closely at that example, I think it's way
more that we need. In the example they're actually itegrating social auth
into an existing login system. All we really need is to present the social
auth buttons next to the un/pw prompt, which should be even easier.
—
Reply to this email directly or view it on GitHub
https://github.com/tunapanda/swagportal/issues/1#issuecomment-95272408.

HybridAuth is implemented!
I only enabled it for Facebook, should we have more from the start?
Someone who would like to test this and we can close the issue?

When I load the login page I see this:

Should there be a Facebook login icon or something?

Ah! Had to enable it in the config file. Ok, now I'm getting this:

Is this something you need to set up on the FB end?

Hm... if you enable it in the config file you should get the facebook login
button... As you say, similar to this:
https://github.com/tunapanda/swag/blob/master/config.template.ini
What could be wrong? I added a dependency on:
https://github.com/samcollins/css-social-buttons.git
Maybe you need to update the dependencies?
If not, do you get some errors in the javascript console, php log or are
there some network resources it tries to load but can't? (Strange though,
there shouldn't be any "invisible" errors, I have tried to make it fail
"hard" if there are any problems)
// Micke
On 12 May 2015 17:42, "Brad Smith"<EMAIL_ADDRESS>wrote:

Ah! Had to enable it in the config file. Ok, now I'm getting this:
[image: screen shot 2015-05-12 at 11 37 42 am]
https://cloud.githubusercontent.com/assets/188349/7591431/d9fba942-f89b-11e4-9f8d-5320ec237eca.png
Is this something you need to set up on the FB end?
—
Reply to this email directly or view it on GitHub
https://github.com/tunapanda/swag/issues/1#issuecomment-101324894.

This is what you get from responding via email. :P See my follow-up comments.

Ah ok...
I made the app live on FB, try now!

Woo! I am logged in. Great work, Micke! :D
I've now got another error (of course), but afaict it's not related to this issue, so I'll make a new one for it: #8.
We may want to keep this issue open until we either get PAM working or get non-FB logins working some other way, though.


GitHub edit link tag

This PR exposes a github_edit_link tag that generates links to edit the current page on GitHub.
To generate a link

This site is open source. {% github_edit_link "Improve this page" %}

Produces:

This site is open source. Improve this page

To generate a path
If you'd prefer to build your own link, simply don't pass link text

This site is open source. Improve this page

Produces:

This site is open source. Improve this page

In order to add the tag, I made to related changes:

Broke the various spec helpers into spec/spec_helpers/foo_helper.rb to keep spec/spec_helpers.rb more managable

Broke the README into individual documents, and moved to the docs/ folder since adding the edit tag docs made the README a bit unwieldy.

@parkr thanks for the feedback. I believe I've implemented your suggestions and answered your questions to the best of my ability. Mind taking another look? :smile:

@jekyllbot: merge

Is it supposed to work locally?
My default branch is master, my _config.ymlalso has branch:masterand here is the link that gets generated when testing on my machine:
`https://github.com/DirtyF/frank.taillandier.me/edit/gh-pages/_posts/2017-05-21-sept-ans-de-sud-web.md``

@DirtyF I believe the following should work in your config:
github:
  source:
    branch: master

I hoped so but something is wrong:
GitHub API is returning master
$ http --body https://api.github.com/repos/DirtyF/frank.taillandier.me/branches
[
    {
        "commit": {
            "sha": "15a70597f9aee29fcb4c7ae354489b0b560230e8",
            "url": "https://api.github.com/repos/DirtyF/frank.taillandier.me/commits/15a70597f9aee29fcb4c7ae354489b0b560230e8"
        },
        "name": "master"
    }
]

Whether {{ site.github.source.branch }} is returning gh-pages. 😲

The tag uses site.github.source.branch which comes from https://github.com/jekyll/github-metadata/blob/master/lib/jekyll-github-metadata/metadata_drop.rb#L61, which itself is delegated to  https://github.com/jekyll/github-metadata/blob/master/lib/jekyll-github-metadata/repository.rb#L125-L127 which will either be the source as returned from the pages endpoint, or if it can't hit that endpoint, gh-pages for user pages.
If site.github is a hash, we merge the drop (the logic above) with the user-supplied value. It could be that Jekyll's deep_merge_hashes isn't recursive enough, but in theory, if you supply site.github.source.branch it should prefer that over the calculated value.

Thanks for taking the time to explain how this works under the hood. 🔧

in theory, if you supply site.github.source.branch it should prefer that over the calculated value.

Well, as I said, In my case, it keeps the default value 'gh-pages`.
If this only supposed to work with repos that have GitHub Pages activated, I guess it's an edge case and out of scope.

@DirtyF You found a 🐛 🐞! Fix in progress via https://github.com/jekyll/github-metadata/pull/110.


local icon png not showing with new update

Describe the bug
With the new update, all my local icon .png disapear , they are setup like this :  /local/photo/bulb-small.png

here is a screenshot from my ipad :

Hi, I have removed this possibility because you can do that directly in Home Assistant by customizing the entity_picture, here's how:
https://www.home-assistant.io/integrations/homeassistant/#entity_picture

Ok thank you, that’s perfect 😊

You're welcome 🙂


RPP Tensor Audio Support - MelFilterBank

@rrawther @kiritigowda MelfilterBank as a functionality is dependent on spectrogram.
So PR #312 needs to be merged into develop first, followed by a develop/ToT sync to ensure only MelFilterBank files-changed shows for this PR.

This PR adds audio tensor support for MelFilterBank
Adds relevant QA tests and performance tests

@r-abishek Same build issue on this PR as on #312

@rrawther We have explored the second library suggested too. We can go over findings and tradeoff in precision match for trainings to take a call on this.

Checked all audio passing after changes:

@kiritigowda can we merge this too?

Waiting for this to complete - http://math-ci.amd.com/blue/organizations/jenkins/main%2Fprecheckin%2Frpp/detail/PR-332/6/pipeline


request: browser support

it would be sweet to use this client-side, but some things would need to change first:

remove assumption that a filename will be passed in and a folder will be created + extracted to
instead have an abstract interface that requests byte ranges (e.g. what getBuffer is doing) but is decoupled from fs. that way it can be hooked up to FileReader in the browser. require('fs') would have to move to separate node-only file from the extraction logic. the extraction logic would be generic so that it can run in the browser or in node
also abstract the extraction so that instead of passing in a destination folder you can just get a readable stream for each file file extraction

:+1:
Would love this. Any decent alternatives yet?

@timdp https://stuk.github.io/jszip/

Right before I saw your comment, I finished writing some Promise wrappers around zip.js. Thanks though. :smile:


Enhancement: Update Token Values for gpt-4o because it now points to the gpt-4o-2024-08-06

What features would you like to see added?
Update the token calculations for the gpt-4o model to use the gpt-4o-2024-08-06 model's pricing because gpt-4o now points to the gpt-4o-2024-08-06 model.
More details
gpt-4o has been pointed to the  gpt-4o-2024-08-06 since Oct 3rd, 2024. Source: X, API Docs.
The token caculations for gpt-4o should now be based on the gpt-4o-2024-08-06 model, which is $2.50/1m prompt tokens and $10/1m completion tokens. The legacy model gpt-4o-2024-05-13 should be caculated as $5/1m prompt tokens and $15/1m completion tokens.
Which components are impacted by your request?
Endpoints
Pictures
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Closed by https://github.com/danny-avila/LibreChat/pull/4387


in samsung galaxy 10+

hello. in Samsung galaxy 9+ working perfect but in Samsung galaxy 10+ inside parents after login crash, and 3 option not working in all phone .
1 . Notifications received: Whatsapp, Instagram, Messenger.
2. call recoder.
3. after password settings then app not open. app crash.
other all options is working good.
please check this. thankyou.

Subsection 3 corrected.


Concatenate all participants data as "motiondata"

Thank you for sharing this great work!
svm_*.m scripts seem to require motiondata and label variables which contains all participants data.
This patch will fix the errors because of that missing variables.
But still, in my environment (matlab R2019B + libsvm-3.24) the accuracy shown in fig2.png cannot be reproduced. So, something might be wrong with this patch.

What kind of variables are contained in the output of make_data.m (i.e. DSADS_all.mat and DSADS.mat) before this modification?
In our environment used for the experiment, DSADS_all.mat contains the variables you say missing.
I will try in your environment please wait a few days.

Before applying this patch, the following variables are stored respectively.

DSADS.mat contains labels and motiondata1
DSADS_all.mat contains labels,  labels1,  labels2,  labels3,  labels4,  labels5,  labels6,  labels7,  labels8,  motiondata1,  motiondata2,  motiondata3,  motiondata4,  motiondata5,  motiondata6,  motiondata7 and  motiondata8

So, motiondata and label are not defined.
It corresponds with the description in make_data.m perfectly.
Maybe, DSADS_all.mat now you are referring might not have been produced by current make_data.m in the master branch.

I confirmed

The error doesn't happen in matlab R2017b.
The error happen in matlab R2019a.
In addition, I found a mistake which is not related to this modification and modified it.
Please confirm the experiments with the latest file.

Thanks to your correction,  now the accuracy in my environment perfectly corresponds with the result shown in fig2.png!


Send message with emoji

How I can send emojis using the chat.send_message() function?
I am using Python 2.7 and I also included the # -- coding: utf-8 --
After googling it, I tried the following commands without any results:

chat.send_message(u"\xF0\x9F\x98\x81")
chat.send_message(u"\xF0\x9F\x98\x81".encode("utf-8"))
chat.send_message('😀'.decode().encode("utf-8"))
I also tried an emoji library from emoji import emojize

Thanks in advance

I also tried :smile: but it didn't worked

Please use python 3 for better emoji support.
On Sun 4 Mar, 2018, 2:32 AM Nicolas Velasquez<EMAIL_ADDRESS>wrote:

I also tried 😄 but it didn't worked
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mukulhase/WebWhatsAPI/issues/111#issuecomment-370179570,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJPo3entORmKqYlQxjbFXLkoHha6bixPks5tawTZgaJpZM4SSaZL
.

@mukulhase
I am sure that this is a noob mistake but, when I run the echo.py sample I got this response:
$ python3 echo.py
Traceback (most recent call last):
  File "echo.py", line 2, in <module>
    from webwhatsapi import WhatsAPIDriver
  File "/usr/local/lib/python3.5/dist-packages/webwhatsapi/__init__.py", line 116
    print "Exited"
                 ^
SyntaxError: Missing parentheses in call to 'print'

How I can use Python3 to run this script? I installed the package properly?
Thanks for your time

You have to Put brackets around every Print Statement Like print("Python 3
has brackets!")
Am 04.03.2018 1:45 nachm. schrieb "Enric Moreu"<EMAIL_ADDRESS>
@mukulhase https://github.com/mukulhase
I am sure that this is a noob mistake but, when I run the echo.py sample I
got this response:
$ python3 echo.py
Traceback (most recent call last):
File "echo.py", line 2, in
from webwhatsapi import WhatsAPIDriver
File "/usr/local/lib/python3.5/dist-packages/webwhatsapi/init.py", line 116
print "Exited"
^
SyntaxError: Missing parentheses in call to 'print'
How I can use Python3 to run this script? I installed the package properly?
Thanks for your time
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mukulhase/WebWhatsAPI/issues/111#issuecomment-370226485,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGhecX6gSZZKKgzu2EvrgCysrMbymmbuks5ta-HqgaJpZM4SSaZL
.

Thanks for your fast reply @kevinkit
I know that Python3 use brackets in the print statement, however I can't change the __init.py file.
I have to change all the code to use Python3? I am using only the echo.py with the out-of the-box install of the package.

After some investigation, I am able to display utf8 characters via console in Python 2.7:
# -*- coding: utf-8 -*-
message= unicode(u'😂').encode('utf8')
print message

But when I use chat.send_message(message) it still representing this in Whatsapp: ð
Does the send_message function support sending emojis?
Sorry for the inconvenience

Solved using Python3.
I solved the problem installing the package via setup.py instead of pip install

Hello! How did you resolve to send emoji?

Just using Python3

Help me please?
Enviado do meu iPhone
Em 30 de abr de 2019, à(s) 14:19, Enric Moreu<EMAIL_ADDRESS>escreveu:

Just using Python3
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Using Python3 try: self.driver.send_message_to_id(some_id, "🐱")
Please be more specific if you need additional help

No receite emoji
Receive cod
Exemple
Send 😴
Receive ud83d\ude34
Enviado do meu iPhone
Em 30 de abr de 2019, à(s) 14:28, Enric Moreu<EMAIL_ADDRESS>escreveu:

Using Python3 try: self.driver.send_message_to_id(some_id, "🐱")
Please be more specific if you need additional help
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

import emoji
driver.send_message_to_id(id, emoji.emojize(txt))


I will add a Linkedin UI clone created with HTML and CSS

Project title
(Linkedln UI clone)
Project Description
(LinkedIn UI clone created with HTML and CSS it is a clone of LinkedIn homepage it doesn't consist of any  functionality because it was only created using HTML and CSS please assign me this issue to work on.)
Stack:
And in order to tick the check box just put x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS

@khushi-purwar kindly review this issue
@gurjeetsinghvirdee Kindly review this issue

Someone already created LinkedIn PR, so I'm closing thi issue


"Mărgaia" is listed in the drop-down menu

Description:
"Mărgaia" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Mărgaia" in the search bar.

Expected results
The location is listed in the drop-down menu as "Mărgaia, Alba (Lupșa)".


Skinned mesh in incorrect position

Describe the bug
The skinned meshes display in the incorrect positions.
To Reproduce
Steps to reproduce the behavior:

Load into blender
File -> Export ->glTF2.0
Check to skinning
Export

Expected behavior

Screenshots

.blend file/ .gltf
rabbit.blend.zip
Version

OS: macOS
Blender Version 2.8.0

Additional context
The model is imported from .fbx. The position is correct with FBX2glTF (Facebook).
I'm not sure whether it is a bug.

Confirmed.
Seems to be linked to ears object location that are not initial before skinning.
Applying location ( Ctrl+A) on both ears seems to solve the issue

Thanks, but it doesn't work on this
test.blend.zip,
is this another problem?

This will be fix after merge of branch https://github.com/KhronosGroup/glTF-Blender-IO/tree/fix_IBM

Fixed now !


.gitattributes: Syntax highlight bpftrace script

These scripts are obviously not written in the D language, but Linguist doesn't support the bpftrace syntax [1]. The D language is the closest match and what the upstream bpftrace repository uses as well [2].
1 - https://github.com/github-linguist/linguist/blob/main/vendor/README.md
2 - https://github.com/bpftrace/bpftrace/blob/master/.gitattributes

/test


Multiple face detection with high probability when a single face is present

First of all, thank you for this library and your commitment to making such an interesting resource available in such a simple way.
I am using multiple face (set to a maximum of 2) to try to ensure the presence of a single face. But sometimes when only one face is present, the probability of face detection for 1 and 2 appears with very high values (even when adopting a threshold of 0.9).
I noticed this behavior in my application (using version 2.0.5 via npm) and that can also be seen in the multiCubes example.
This behavior usually happens with the face in some positions or after some time moving the head. There is often a large overlap between the detection rectangles, but not always.
Is this behavior expected or is there a method to mitigate the problem? I tried a few different settings, but I was unsuccessful.

Hi,
I have worked to improve multi face detection and fixed a major bug.
Can you retry and tell me if it is better now?
Thanx


Wikibase: proxy manifest requests

This makes the backend proxy requests for Wikibase manifests to allow them to be hosted in MediaWiki itself(removing the CORS requirement).
MediaWiki hosted manifest example(Wikidata): https://www.wikidata.org/wiki/User:Abbe98/openrefine-manifest.json?action=raw
Setting this to draft for now but I would like to hear what others think about this approach before working out the details.

I think it makes sense to fetch the manifest from the backend instead of in the frontend.
The implementation you have looks like an open proxy to let the frontend fetch any JSON through the backend. My intuition would be to try to make this more specific to Wikibase manifests, for instance by validating the JSON structure of the manifest before returning it, and perhaps even registering it in the command in the list of known Wikibases.
GitHub identifies a security issue in the fact that we are fetching a user-supplied URL. I guess it makes sense but I am not clear on what the security implications really are. Perhaps the server could serve a maliciously crafted JSON payload which would exploit a vulnerability of our JSON parser, say (like there were similar attacks with exponential expansion of XML documents). But obviously we already do plenty of backend-side fetching of user-supplied URLs so any security issues with that would also apply there.

I think it makes sense to fetch the manifest from the backend instead of in the frontend.
The implementation you have looks like an open proxy to let the frontend fetch any JSON through the backend. My intuition would be to try to make this more specific to Wikibase manifests, for instance by validating the JSON structure of the manifest before returning it, and perhaps even registering it in the command in the list of known Wikibases.

I think that #3109 is a natural follow up, however, my intent for now is only to enable the manifest hosting use-case.

GitHub identifies a security issue in the fact that we are fetching a user-supplied URL. I guess it makes sense but I am not clear on what the security implications really are. Perhaps the server could serve a maliciously crafted JSON payload which would exploit a vulnerability of our JSON parser, say (like there were similar attacks with exponential expansion of XML documents). But obviously we already do plenty of backend-side fetching of user-supplied URLs so any security issues with that would also apply there.

I share your view, an exploit here would already effect other parts of the codebase. Just proxying it is probably the safest thing we can do?

Maybe a user-agent string?

I agree with @wetneb that some type of restriction/registration of the target domain or payload would be useful. The fact that the current security posture is poor doesn't mean that we shouldn't try to minimize, or at least not increase, the attack surface. Letting the user pick from a set of configured URLs would like resolve the security warning, but if that's not possible, validating the content (a la #3109) would be next best.
What issue # is this associated with? The PR template should have included a placeholder for the issue #.

I agree with @wetneb that some type of restriction/registration of the target domain or payload would be useful. The fact that the current security posture is poor doesn't mean that we shouldn't try to minimize, or at least not increase, the attack surface.

In what way would this increase the attack surface?

I've lost the thread here. I'm happy to let you two agree on the best solution.

@Abbe98 I'm assuming you won't have time to make this progress, so I'd just make a few cleaning tweaks and merge it unless you have concerns?

I am actually tempted to make this more generic, rather than more specific, turning it into a endpoint to fetch JSON from arbitrary third-party sources and return it to the frontend. That would be a way to eliminate all uses of JSONP in the frontend, which would be a clear security win. (I think @Abbe98 has suggested something similar in the past.)
We could still have some safeguards to limit the size of the data downloaded (to make sure we don't choke up the backend) and ensure that the JSON parsing is suitable for adversarial payloads (which should be the default with Jackson, but it's always worth checking).

I patched the potential issue regarding encoding that @wetneb pointed out. While I think there is more potential work in this area, I think a general purpose proxy is out of scope for now(it do indeed sound like something I might get back to!).


endpoint: Don't scrub local ct map on leave

The local ct map will be deleted soon after, so don't bother spending
the CPU cycles to dump and delete entries from the table.

This change is

test-me-please

The local ct map will be deleted soon after

@joestringer 2 questions: 1) where? 2) What about if the user is using a global CT?

@aanm Local maps are deleted here:
https://github.com/cilium/cilium/blob/f730b6b97f677368e7ff68af85a284c90c58c253/daemon/endpoint.go#L499-L501
(Technically this happens before the code that is changed here, but the map won't be properly cleaned up until we remove the BPF program from the device which should happen from the cni/docker plugin when the veth is deleted).
If the user is using global CT, the entries are still cleaned up at this path.


CVE-2019-10172 disappears when using redhot version

When I run mvn org.owasp:dependency-check-maven:6.1.1:check on the following project:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>foo</groupId>
    <artifactId>foo</artifactId>
    <version>1.0-SNAPSHOT</version>

    <repositories>
        <repository>
            <id>redhat-ga</id>
            <url>https://maven.repository.redhat.com/ga/</url>
        </repository>
    </repositories>

    <dependencies>
        <dependency>
            <groupId>org.codehaus.jackson</groupId>
            <artifactId>jackson-mapper-asl</artifactId>
            <version>1.9.13</version>
        </dependency>
    </dependencies>
</project>

CVE-2019-10172 is found as a vulnerability of jackson-mapper-asl. However if I change the version to 1.9.13.redhat-00007 CVE-2019-10172 isn't found any longer.
Shouldn't both cases find CVE-2019-10172?

Shouldn't both cases find CVE-2019-10172?

Why?
1.9.13 < 1.9.13.redhat-00007 and the vuln is for <= 1.9.13,
clearly 1.9.13.redhat-00007 is a higher version than 1.9.13

Ok, understood. Than you!


slack is posting two/three messages with chat_postMessage

Description
Describe your issue here.
I am using slack-bolt python framework for my slack bolt which is going through some logic. I am using chat_postMessage method to send a message from bot. But currently it is sending three messages even though it's having single API call. I read about it and notices that it can be avoided with making X-Slack-Retry-Num =1 in header.(https://api.slack.com/apis/connections/events-api#graceful_retries) But i am wondering how can i change the header of the api call in res_out = app.client.chat_postMessage(channel=message['channel'],thread_ts = original_thread_id,blocks=block_final)
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[x] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:

use res_out = app.client.chat_postMessage(channel=message['channel'],thread_ts = original_thread_id,blocks=block_final) in the bot's code and due to retry mechanism it tries and sends the same message thrice on single call.

Expected result:
Bot should only post single message.
Actual result:
Bot is posting two/three same messages
Attachments:

Transferring this issue to slackapi/bolt-python


add to members

Please, resolve merge conflict

Your commit will be the last one, so you can easily resolve conflict.


Json post with Apache Http Client failed with length required error

ItemScore itemScore = HttpBuilder.configure({ c -> new ApacheHttpBuilder(c); } as java.util.function.Function) {
    request.uri = 'http://httpbin.org'
    request.contentType = JSON[0]
    response.parser(JSON[0]) { config, resp ->
        new ItemScore(NativeHandlers.Parsers.json(config, resp).json)
    }
}.post(ItemScore) {
    request.uri.path = '/post'
    request.body = new ItemScore('ASDFASEACV235', 90786)
}

println "Your score for item (${itemScore.item}) was (${itemScore.score})."

with above code using ApacheHttpBuilder, cause error below:
Caught: groovyx.net.http.HttpException: Length Required
groovyx.net.http.HttpException: Length Required
        at groovyx.net.http.NativeHandlers.failure(NativeHandlers.java:69)
        at groovyx.net.http.HttpBuilder$ResponseHandlerFunction.apply(HttpBuilder.java:2305)

What version of HttpBuilder-NG are you using?

Looks like we must already be providing the Content-Length in the Java core client but not in the other two. I have a fix for this pending.


refactor _expanding.less

Move the following line
https://github.com/sButtons/sbuttons/blob/223b97b1e9952751dbfc57a30b709aa334d6b8bb/src/components/animated/_expanding.less#L28
to outside the hover under line 3

May I do this?

Sure @SamD97


[Admin] (iPad/Mac) Clarify instructions

Related to PR https://github.com/OfficeDev/office-js-docs-pr/pull/2070.

Docs Build status updates of commit 6518826:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/my-add-ins-wikipedia.png
:white_check_mark:Succeeded
View

docs/testing/sideload-an-office-add-in-on-ipad-and-mac.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Thanks @ElizabethSamuel-MSFT! Will this also fix #1716?

@AlexJerabek Not sure yet. I'll go through the entire thread then proceed as applicable.


[BUG] Country dropdown extends beyond browser window in default starter

Describe the bug
We have lots of countries connected to the Hydrogen preview store:

This has a couple of ramifications:

A large chunk of JSON data is being serialized for each and every country in the initial SSR HTML and in the RSC responses
This dropdown extends beyond the height of the average browser screen, and it's not scrollable

We should consider alternatives to this approach to keep the payload of the page down in size. Maybe lazy-load the contents of the dropdown on click?
Additionally, we should make sure the entire list is scrollable.

When I ran the initial project, I got a full, unscrollable list containing "GBP", "EUR", "EUR", "EUR", "EUR", etc. Was a bit strange but when changing away from the default store it was fixed.

When I ran the initial project, I got a full, unscrollable list containing "GBP", "EUR", "EUR", "EUR", "EUR", etc. Was a bit strange but when changing away from the default store it was fixed.

I believe that's been fixed in the 0.11-experimental branch

@jplhomer  Hi! May I take charge of this issue?

A large chunk of JSON data is being serialized for each and every country in the initial SSR HTML and in the RSC responses

Changed to lazy loading using React.lazy. Does this change solve this problem?

I don't think it does. It isn't the component that needs to be lazy loaded, it is the contents or the countries prop. My guess is the right way to lazy load that data would be to setup an API route for pulling it, and when the dialog is displayed, have CountrySelector.client.jsx fetch the countries by that API route endpoint.

Related - #887

@blittle Thanks for the reply!
Okay, now that I understand the direction, I will try to adjust it again.
If I am not sure, please let me consult again.
@elisenyang
OK, I will check this one as well.


Need documentation on AdditionalAttributes property and operation

The AdditionalAttributes property has appeared in several controls along with the AddMultipleAttributes method on RenderTreeBuilder, and is a useful feature for passing attributes to a Component that are not directly handled but are required in the render process. I looked for documentation on this (e.g. how can we write these attributes in our own control using Razor syntax, rather than calling AddMultipleAttributes ?

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

ID: be4c4d0c-149c-bde1-c7fa-f082916390ca
Version Independent ID: 9d945996-ad02-bd4b-58ea-c465cc5cc74c
Content: Create and use ASP.NET Core Razor components
Content Source: aspnetcore/blazor/components.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

This has been covered since the issue was opened ...
https://docs.microsoft.com/en-us/aspnet/core/blazor/components?view=aspnetcore-3.0#attribute-splatting-and-arbitrary-parameters

Hi @guardrex,
The documentation here is sufficient. However, when I searched for AdditionalAttributes I cannot find the documentation.

Searching for "attributes" does find it, about 20 down, but that is a pretty generic term, and I would not expect it to bubble up.
I realize that AdditionalAttributes is an arbitrary variable name, and would not expect it to be searchable in general, but since it is used internally in the source and examples and other documentation, it would be helpful.
So, any chance we could index  AdditionalAttributes (and maybe the singular, AdditionalAttribute, just in case) to point to the above link?
Also, is there a correct way for me to request an index term and link? I didn't see anything searching issues, but I am sure I am just missing the correct term to search for ;-)
Thanks

I believe the filters are title based. We don't have search term indexing as far as I know.
Your best bet for these types of searches isn't to use that search system but to go with a good 'ole Google search. Search for it this way in Google ...
site:docs.microsoft.com/en-us/aspnet/core "AdditionalAttributes"

Also ... btw ... it's best not to comment on closed issues and PRs. Feel free to open a new issue using the This Page feedback button+form at the bottom of a topic.

I will send feedback. Thanks

I mean that just opens the issue for us, so it's the same answer. If you want to open feedback about the search feature itself, open an issue here ...
https://github.com/MicrosoftDocs/feedback/issues


Notify Service Restarts in LWRPs for EL7

Hi there,
I was trying to use the LWRPs on a centos 7 install, but was unable to because the service didn't support a :reload action. This PR parameterizes the restart method as an attribute and then uses that wherever service reloads/restarts are notified.

:+1: Thanks!


take much time on building OpenCL program

Hi Peter,
I found it takes more time when compiling an OpenCL program using clCompileProgram() and clLinkProgram() separately compared to only using clBuildProgram().
Are there some reasons to use the two-step compilation, not the one-step compilation, when building an OpenCL program in SYCL-GTX?
Any response would be appreciated a lot!

Hi,
I believe it was because of implementation simplicity. There could definitely be another path that builds the program directly.


🎉 1.1.1

ℹ About this release

Version: 1.1.1
Type: patch
Last Release: 1.1.0 (3/7/2022, 4:55:08 PM) [?]
Commits to merge: 55 [?]

📦 Dependencies

Update express from ^4.17.3 to ^4.18.1
Update ical-generator from ^3.4.1 to ^3.4.2

📦 Development Dependencies

Update @types/luxon from ^2.3.1 to ^2.3.2
Update @types/mocha from ^9.1.0 to ^9.1.1
Update @types/node from ^17.0.23 to ^17.0.31
Update @typescript-eslint/eslint-plugin from ^5.17.0 to ^5.22.0
Update @typescript-eslint/parser from ^5.17.0 to ^5.22.0
Update dayjs from ^1.11.1 to ^1.11.2
Update mocha from ^9.2.2 to ^10.0.0
Update moment from ^2.29.2 to ^2.29.3
Update typescript from ^4.6.3 to ^4.6.4

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

v1.1.1
GitHub release
Docker container (sebbo2002/fitness-first-ical-proxy:1.1.1)
v1.1.1

Your semantic-release bot :package::rocket:


Enable IPSec encryption of tunnel traffic

Create a separate OVS tunnel port for each remote Node.
Change L3 forwarding flows to support outputting to the IPSec tunnel port.
Add yamls to enable IPSec encryption and add a new container in the Agent DS to run IPSec daemons.

Will add e2e tests in the same PR.

@wenyingd: I changed the L3 and L2 tables as we discussed offline. Please check.

I still plan to add e2e tests before merging the PR, but the current comments are ready for review.

/test-e2e

/test-e2e

/test-e2e

/test-e2e

/test-e2e

/test-conformance

/test-e2e

/test-conformance
/test-networkpolicy

/test-e2e

/test-e2e

/test-e2e

/test-all


/api/auth/github return timeout error in custom dns and 404 not found in local environment

When I set up backstage in local enviroment and try to log in to github when the sign-up button shown
backstage will return 404 /api/auth/github not found
and when I enter /api it will return 404 as well
For my production environment, I am deploying backstage into eks
the sign-in popup will be stuck in about:blank
And the whole app will be stuck in refreshing state till  this error appearGET https://domain:7007/api/auth/github/refresh?optional&env=development net::ERR_CONNECTION_TIMED_OUT
I tried to ping the https://domain:7007/api/auth/github but it will just time out
Expected Behavior

Actual Behavior
In localhost, when enter /api/auth/github it will return:
{"error":{"name":"NotFoundError","message":"No auth provider registered for 'github'"},"request":{"method":"GET","url":"/api/auth/github"},"response":{"statusCode":404}}
Steps to Reproduce
This is my app-config.yaml
app:
  title: my-title
  baseUrl: https://mydomain:3000
backend:
  baseUrl: https://mydomain:7007
  listen:
    port: 7007

  # content security policy
  csp:
    connect-src: ["'self'", 'http:', 'https:']

  database:
    client: pg
    connection:
      host: ${POSTGRES_HOST}
      port: 5432
      user: ${POSTGRES_USER}
      password: ${POSTGRES_SECRET}

integrations:
  github:
    - host: github.com
      token: ${GITHUB_TOKEN}

techdocs:
  builder: 'local' # Alternatives - 'external'
  generator:
    runIn: 'docker' # Alternatives - 'local'
  publisher:
    type: 'local' # Alternatives - 'googleGcs' or 'awsS3'. Read documentation for using alternatives.

auth:
  # authenticate with github
  providers:
    github:
      development:
        clientId: ${AUTH_GITHUB_CLIENT_ID}
        clientSecret: ${AUTH_GITHUB_CLIENT_SECRET}

Context
In the container, the refresh will causing hundreds of lines of
2022-09-16T17:52:44.917Z backstage info ::ffff:<IP_ADDRESS> - - [16/Sep/2022:17:52:44 +0000] "GET / HTTP/1.1" 200 1924 "-" "kube-probe/1.21+" type=incomingRequest
2022-09-16T17:52:44.918Z backstage info ::ffff:<IP_ADDRESS> - - [16/Sep/2022:17:52:44 +0000] "GET / HTTP/1.1" 200 1924 "-" "kube-probe/1.21+" type=incomingRequest

Your Environment

Browser Information: 105.0.5195.125 (Official Build) (arm64)

Output of yarn backstage-cli info:

OS:   Darwin 21.4.0 - darwin/arm64
node: v16.16.0
yarn: 1.22.19
cli:  0.19.0 (installed)
backstage:  1.5.0

Dependencies:
  @backstage/app-defaults                          1.0.6
  @backstage/backend-common                        0.15.1
  @backstage/backend-plugin-api                    0.1.2
  @backstage/backend-tasks                         0.3.5
  @backstage/catalog-client                        1.1.0
  @backstage/catalog-model                         1.1.1
  @backstage/cli-common                            0.1.10
  @backstage/cli                                   0.19.0
  @backstage/config-loader                         1.1.4
  @backstage/config                                1.0.2
  @backstage/core-app-api                          1.1.0
  @backstage/core-components                       0.11.1
  @backstage/core-plugin-api                       1.0.6
  @backstage/errors                                1.1.1
  @backstage/integration-react                     1.1.4
  @backstage/integration                           1.3.1
  @backstage/plugin-api-docs                       0.8.9
  @backstage/plugin-app-backend                    0.3.36
  @backstage/plugin-auth-backend                   0.16.0
  @backstage/plugin-auth-node                      0.2.5
  @backstage/plugin-catalog-backend-module-github  0.1.7
  @backstage/plugin-catalog-backend                1.4.0
  @backstage/plugin-catalog-common                 1.0.6
  @backstage/plugin-catalog-graph                  0.2.21
  @backstage/plugin-catalog-import                 0.8.12
  @backstage/plugin-catalog-node                   1.1.0
  @backstage/plugin-catalog-react                  1.1.4
  @backstage/plugin-catalog                        1.5.1
  @backstage/plugin-github-actions                 0.5.9
  @backstage/plugin-org                            0.5.9
  @backstage/plugin-permission-common              0.6.4
  @backstage/plugin-permission-node                0.6.5
  @backstage/plugin-permission-react               0.4.5
  @backstage/plugin-proxy-backend                  0.2.30
  @backstage/plugin-scaffolder-backend             1.6.0
  @backstage/plugin-scaffolder-common              1.2.0
  @backstage/plugin-scaffolder                     1.6.0
  @backstage/plugin-search-backend-module-pg       0.4.0
  @backstage/plugin-search-backend-node            1.0.2
  @backstage/plugin-search-backend                 1.0.2
  @backstage/plugin-search-common                  1.0.1
  @backstage/plugin-search-react                   1.1.0
  @backstage/plugin-search                         1.0.2
  @backstage/plugin-tech-radar                     0.5.16
  @backstage/plugin-techdocs-backend               1.3.0
  @backstage/plugin-techdocs-module-addons-contrib 1.0.4
  @backstage/plugin-techdocs-node                  1.4.0
  @backstage/plugin-techdocs-react                 1.0.4
  @backstage/plugin-techdocs                       1.3.2
  @backstage/plugin-user-settings                  0.4.8
  @backstage/release-manifests                     0.0.6
  @backstage/test-utils                            1.2.0
  @backstage/theme                                 0.2.16
  @backstage/types                                 1.0.0
  @backstage/version-bridge                        1.0.1

Yeah you have to add the provider in your packages/backend/src/plugins/auth.ts.
https://backstage.io/docs/auth/identity-resolver

Hi @freben there is a default github auth in the code already:
github: providers.github.create({
        signIn: {
          resolver(_, ctx) {
            const userRef = 'user:default/guest'; // Must be a full entity reference
            return ctx.issueToken({
              claims: {
                sub: userRef, // The user's own identity
                ent: [userRef], // A list of identities that the user claims ownership through
              },
            });
          },
          // resolver: providers.github.resolvers.usernameMatchingUserEntityName(),
        },
      }),

I disabled the /api/auth
And when I enter repo url, it will stuck in refresh/pending mode as well. WIth  /api/catalog/entities?filter=kind=template will have net::ERR_CONNECTION_TIMED_OUT as well. Followed  by /api/auth/github/refresh?optional&env=development net::ERR_CONNECTION_TIMED_OUT
So /api/auth is connected with other /api ? I might be mistaken

More log after enter the entity file url and press analyze button
And if you go to the network tab, you will still see /api/auth/github/refresh?optional&env=development in request url
and causing everything in a pending state
So that just appear to me like /api/auth seems to be tied with other /api and somehow is blocking the other /api?
2022-09-23T10:43:56.782Z search info Collating documents for techdocs via DefaultTechDocsCollatorFactory type=plugin
13
2022-09-23T10:43:56.796Z backstage info ::ffff:<IP_ADDRESS> - - [23/Sep/2022:10:43:56 +0000] "GET /api/catalog/entities?filter=metadata.annotations.backstage.io%2Ftechdocs-ref&fields=kind,namespace,metadata.annotations,metadata.name,metadata.title,metadata.namespace,spec.type,spec.lifecycle,relations&offset=0&limit=500 HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
12
2022-09-23T10:43:56.799Z search info Collating documents for techdocs succeeded type=plugin
11
2022-09-23T10:43:56.904Z search info Collating documents for software-catalog via DefaultCatalogCollatorFactory type=plugin
10
2022-09-23T10:43:56.908Z backstage info ::ffff:<IP_ADDRESS> - - [23/Sep/2022:10:43:56 +0000] "GET /api/catalog/entities?offset=0&limit=500 HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
9
2022-09-23T10:43:56.909Z search info Collating documents for software-catalog succeeded type=plugin

Hope this is helpful! ``

How are you deploying this?
I note that you have base URLs in your config with https:// and on two different ports. I wanted to check if you are terminating https in node itself really, or if there's some proxy in front of it all.
What we do, is that we have a single authenticating reverse proxy in front of everything, and from the browser's point of view it's all on the same regular https port. But the proxy splits traffic on the /api prefix to the backend installation, and the rest to the frontend installation - as plain unencrypted http. This has some huge benefits in terms of simplicity and performance, and the client doesn't have to worry about CORS etc since it's all on the same domain + port.

Hi @freben Many thanks! ❤
You are right about the ports, I removed all the port numbers and it is working!
Also I cleaned all the cookies...
So basically if you have a domain you don't need to worry about the ports, ports are for local developments. Because if you have a domain, the proxy will send /api directly to backend?
Would be interesting to see more documentations on how the reverse proxy work (I am very new to everything 😆 )
My deployment is in with kubernetes, it will therefore be good to update the setup documentation in the future! 😸

Alright, sounds like this was resolved so going to close 👍
Please let us know if there's anything else, or you can open new issues for separate topics

Hello @jiawenh1 do not mean to hijack an old thread, but did you remove the ports within the baseURL, or did you also remove the
listen:
port:  7007
Part as well? Working on deployment to cloud (azure) and I am experiencing the same error. Thanks!


Update comment blocks.

Adds matrix comments, and also color comments.
sadly since C-Blocks don't work i could not add them 😭.

@LilyMakesThings this is your extension
do you agree with this?

I don't like this. I'd prefer people to use a coupler for these values.

I don't like this. I'd prefer people to use a coupler for these values.
Adding a comment to a color or matrix value is so niche that, for the one person who is going to do that, they should just use the extra block to do that if it keeps this palette to a minimum.

It's worth noting there's not currently a matrix/color coupler in any extensions (other than LMS utils, which is currently unlisted). If these blocks were in couplers i'd be inclined to agree, but as it stands, they are not.

related: https://github.com/TurboWarp/extensions/pull/757

Similar blocks are in couplers now


what is the current work directory?

hello,
the manual says
by default go2rtc will search go2rtc.yaml in the current work dirrectory
but I cannot find the file,
so my question, what is the current work directory? of do I need to create one manually in /config or something?

You can check config path in the go2rtc WebUI


convert all the socketStatHash definitions into a map on startup instead of doing the same work over and over in resusable plugs

fixed


Replace  all  of the old assets

As this game was made with a tutorial, it's a valuable goal to make it something more than that. A good step is to make it visually distinct. I will replace all old assets.

This issue is actually less an issue than a milestone.


Memory overflow while compiling BLS Signature Verification

Aim
Here is my bls signature verification implementation in Noir: https://github.com/onurinanc/noir-bls-signature. When I tried to run this, the cli crashed somehow. There are 2 more persons that tried to run this but having the same issue happens.
Here is the corresponding issue that I got for the bls signature verification compilation: https://github.com/onurinanc/noir-bls-signature/issues/2
As a summary,
@stefan-nikolov96 says that
"I am unable to run test_verify_bls_signature() with over 256GiB in RAM and just as much in swap memory. I get a memory overflow and then the program recieves a SIGKILL signal from the OS.
I tried running nargo compile in debug and release mode and with 0.9.0 and 0.15.0 compiler versions.
GDB shows that the nargo overflows in the compiler frontend. On a machine with 64GiB RAM, it uses about 50GiB during inlining and the program fails during mem2reg
https://github.com/noir-lang/noir/blob/master/compiler/noirc_evaluator/src/ssa/opt/mem2reg.rs "
Expected Behavior
compiler shouldn't crash
Bug
memory overflow and then the program recieves a SIGKILL signal from the OS.
To Reproduce

run verify_bls_signature function

To have an issue solutions what's happening in the back, you can navigate to test_proving_time branch in the repository.
When you run nargo prove if you comment the line 326 inside pairing.nr, it is working correctly.
When you not comment this line, it is not going to work. (due to memory issues)
You can the issue quickly using this repo: https://github.com/onurinanc/test-bls-proving-time
Installation Method
Binary
Nargo Version
nargo 0.17.0 (git version hash: 86704bad3af19dd03634cbec0d697ff8159ed683, is dirty: false)
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response

If we're running into an issue in the mem2reg pass, is it possible this is due to same issue from trying to loop unroll brillig that affected the RSA library?
@onurinanc if you compile this on the nightly version of nargo do you still get the same issue?

@TomAFrench If it is crashing during mem2reg I doubt they are the same. The brillig issue affecting the RSA library is each ArraySet operation in brillig copying the array. Brillig isn't evaluated until later, and this isn't an issue in SSA, since SSA doesn't copy the whole array for each ArraySet.
From looking at the description real quick, if inlining is taking 50GiB then I'd assume the generated SSA is already quite large. The reality may be that, depending on the source program (which I haven't looked at), it may be necessary. This can be if the source program uses large or nested loops, recursion, etc. which necessitate many SSA instructions once every function is inlined - and later when each loop is unrolled. We can try to reduce memory usage by decreasing the size of each instruction (and freeing no longer used ones more often), but this still may not fix it if the program is too large.

@onurinanc No, I couldn't compile in both 0.9.0 and 0.17.0

@TomAFrench, @TomAFrench nargo failed during mem2reg while running it in GDB in debug mode, my PC ran out of memory at that pass, however if I had more memory it would probably overflow further down the line. The memory used may be exaggerated due to nargo being ran in debug mode, however @onurinanc in his documentation of BLS states that he has previously ran bls_verify on a 16GiB machine, therefore I'm assuming it's due to some breaking change in the noirc frontend

@stefan-nikolov96 No, I could not able to run it with 16 GiB

I've ran into this same issue trying to run the noir-bn254 repo (https://github.com/onurinanc/noir-bn254/issues/3) in any Noir version past 0.9.0. The issue is the memory usage of the mem2reg pass as well. I'll document my investigation and my findings below to try and help shed some light on the issue:
The main issue seems to be that the first mem2reg optimization pass runs out of memory. Adding debug prints around the code, it seems that in the case of the noir-bn254 repo, the problem is that there are too many basic blocks (around 450k basic blocks) during that first optimization pass, and the value for self.blocks gets larger and larger for every iteration with more and more time spent cloning some very large BTreeMaps.
Specifically, every block iterated always gets stored in self.blocks and never removed until the end of the optimization pass. The problem here is that the Blocks themselves have BTreeMaps which grow as the blocks get processed. I don't have the specific numbers on me, but IIRC the number of elements of the aliases inside each stored block grows as more and more basic blocks get processed by mem2reg, which happens as the basic blocks get unified and the alias sets of the blocks gets combined (since the non-empty sets just get union'd together). The problem is that every time a block is unified, the alias set unification creates a full clone of the entire (growing) alias set for every expression, and each block in self.blocks contains a copy of this ever-growing map. Since there is no memory sharing or pruning of any of these BTreeMaps, the memory usage grows until OOM.
I've tried understanding a bit more about mem2reg by taking a look at https://hackmd.io/@JakeF/S1FA9rTnh and I believe that this issue could be partly mitigated by pruning blocks from the self.blocks list once we're sure they're no longer necessary (all of their successors have already been processed, so find_starting_references will never return the block anymore and it can be safely removed), and things could be improved even further by pruning the alias set or sharing memory between copies of Blocks.
I've done some rudimentary experiments, first by essentially disabling the implementation by making find_starting_references always return Block::default() and never inserting into self.blocks. This keeps memory usage very low, but as expected it turns off a very important optimization and the resulting ACIR might have issues or be way too unoptimized. Another thing I've attempted is adding processed blocks to a BTreeSet and then regularly pruning self.blocks by removing all blocks whose successors have already been processed. Here is a patch showing my attempt (with some extra debug prints). Doing this allowed the memory usage to be low enough for it to finish after giving it about 300GB of memory (RAM + swap), but the resulting ACIR from compiling with this patched noir was still very slow to execute despite the compilation actually finishing. Also weirdly, the number of elements in self.blocks never went as low as I expected, it seems that only roughly 1/4th to 1/5th of the blocks added were being removed by my retain call, so I might have misunderstood how the code works.
Another (mostly unrelated) issue I've ran into, because the compiled code has so many basic blocks, is that after getting past mem2reg, the flatten_cfg pass will stack overflow due to the recursive nature of the code (there is another stack overflow when printing the inlined SSA too). Increasing the stack limit with ulimit was enough to work around this.
I've (unsuccessfully) attempted to make a minimal repro test case that triggers the same mem2reg behavior, but I believe the root cause of this problem might be some combination of the following:

The mem2reg pass conservatively clones all the state associated with basic blocks and their references/alias sets for every new block, and this state is never pruned until the optimization pass is over.
The noir-bigint library uses arrays for storing the bigints, which have particular semantics in mem2reg that might be causing it to generate larger-than usual alias sets for the basic blocks. (this might not be an issue and just a misunderstanding on my part)
The bigint library also has a large amount of functions that contain if blocks (in particular, multiplication has an if block that happens inside a doubly-nested for loop), which compile to a very large amount of basic blocks when many multiplications are performed. All of those basic blocks end up with many references to individual array elements too.
The EC functions require a large of amount of multiplications to be performed, for example for exponentiation and pairing operations, which leads to an exponential blow up in the number of basic blocks after inlining and loop unrolling is performed.

The big unknown here is that it's unclear to me whether reducing the memory usage would be enough for the compiled program to be actually efficient when compared to the 0.9.0 codebase. I'm not particularly familiar with how compilation worked in version 0.9.0 with the pre-SSA backend (please enlighten me if you can), but the fact that working around the mem2reg memory issue seemed to still take a very long time to finish evaluation/proving even after the ACIR compilation finished makes me wonder if the resulting program really is just too big for SSA compilation because of too many variables/loops/functions like @jfecher said.

I've taken a look at your library and noticed a couple of places where we can reduce the size of the circuit as well. I don't think this would fix this issue by itself but it will help:
https://github.com/onurinanc/noir-bls-signature/blob/510a24f6caebd033e5eea293b92981fe0a08dc6c/src/bls12_381/g2.nr#L100-L141
In this function you've added special behaviour for if one of the inputs is equal to zero or the inputs are equal to each other. When generating a circuit this should actually increase the cost of the function as we will need to generate  constraints for all potential codepaths.

The noir-bigint library uses arrays for storing the bigints, which have particular semantics in mem2reg that might be causing it to generate larger-than usual alias sets for the basic blocks. (this might not be an issue and just a misunderstanding on my part, though there are mentions of it in the hackmd about mem2reg)

Seems like this could be simplified to
let k_mod = k as u56 % NUM_LIMBS as u56
let (n, c) = utils::mac(hi.limbs[k_mod], self.limbs[i], other.limbs[j], carry);
hi.limbs[k_mod] = n;
carry = c;

This shouldn't affect the final circuit size as both the if-statement and modulo are optimized away during compilation but it could ease the memory consumption.

@shuklaayush implemented the above snippet in the noir-bigint library, so we should also add him to this conversation since I am not sure whether this is correct or not since all the prime field tests work correctly.

I think there may be a misunderstanding. The mistake was made by me, thinking that we could remove the if statement.

@TomAFrench any update on this?

@stefan-nikolov96 Hi, apologies for the lack of updates. I've started working on this issue today (thanks @wwared for the analysis). I've yet to have a fix for it yet but I have some initial observations of running the mem2reg pass on the test-bls-proving-time repository:

On latest master (on my machine with 32GiB ram) we are able to process 20k blocks before getting OOM killed.
Switching to a shared im::HashMap we're able to process 45k blocks, but then still get OOM killed.
Switching to im::OrdMap bumps us up to 70k blocks before again getting killed.

So switching to shared map implementations improves things but does not completely fix the problem. I'm looking into pruning old entries in the blocks list now.

I've also noticed there are a few early returns on some methods (e.g. when). I haven't checked to see if they're just short cuts or a proper special case which can't be handled by the general case logic, but if the former then we should remove these.

In both the mem2reg pass and unrolling pass, roughly 30% of the program's memory is spent here https://github.com/noir-lang/noir/blob/master/compiler/noirc_evaluator/src/ssa/ir/dfg.rs#L329. In the values map but specifically for values that are the result of another instruction. We may be able to save quite a bit of space if we switch to a different representation for ValueId such that we can avoid saving result values in this Vec. E.g. enum ValueID { Normal(OldValueId), Result(InstructionId, /*index:*/u32) }

Same issue here, with https://github.com/dndll/GhostFi/blob/don/prover/circuits/ed25519/src/lib.nr. I wasn't quite able to test this due to Message:  index out of bounds: the len is 4290 but the index is 4290.
Although, last night this was taking over 555s on my machine, since @jfecher's work in https://github.com/noir-lang/noir/pull/3572 has increased the time it takes to OOM from ~555s to ~6.5s.


Namron 4512757 z-wave thermostat requires specific float encoding

Discussed in https://github.com/zwave-js/node-zwave-js/discussions/6791

Originally posted by @tronsdal April 26, 2024
Checklist

[X] I have read and followed the above instructions

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue
What is happening?
When I try to set the temp to whole degrees (e.g 17.0, 18.0 etc.) there is an error, and nothing gets updated. If I set it to 17.1, the thermostat gets updated. The same with 17.01 (the thermostat then shows 17.0 in the physical display). I have tried two different thermostats with and without security, and I have tried both with the original z-wave-js and with z-wave-js-ui.
This is very unfortunate, bacause I have a smart integration with my electricity company Tibber, but they only send whole degrees, thus no smart change of temperatures are working. I also have a Homey Pro 2019, and there everything works.
What did you expect to happen instead?
The temp setpoint set to 17.0
Steps to reproduce the behavior:
Try to set the Namron Thermostat entity to an even number like 17 or 17.0 fails. Half degrees like 17.5 works.
Anything else we should know?
Software versions
Driver (node-zwave-js): 12.5.5
Z-Wave JS UI: 9.11.1
Home Assistant Z-Wave Integration: Not sure (1.35.0-beta.1 ?)
Home Assistant Z-Wave JS Addon: 3.5.0
ioBroker.zwave2 Adapter: Aeotec Z-Stick Gen 5
If you are using something non-standard, tell us here: nope
Device information
Manufacturer: Namron
Model name: 16 A Thermostat - White - 4512757
Node ID: 034 (insecure) and 037 (secure)
Checklist

[X] I made sure to provide a driver log on level debug.

[X] The log includes a re-interview of the problematic device (if applicable).

[X] The log includes the problematic interaction with the device (if applicable).

[X] I provided the node ID of the problematic device (if applicable).

Upload Logfile
zwave-js-ui-store.zip

@zwave-js-bot add compat flag to 0x0438:0x0004:0x0108
		// This device only accepts Thermostat Setpoint Set commands with a specific float encoding
		"overrideFloatEncoding": {
			"precision": 1,
			"size": 2
		},


Biome ID's in the config

Biome ID's should be able to be changed/viewed in the config?
In the wiki biome names and ID's should be added as well so that they can be utilized with modpack tweaking mods.

I found an alternative method to obtain mod ID's

Not sure what you mean. Biome IDs are automatically assigned by Forge and that's not something I can control.

Most of the biome names are just the same as the display names, except for traverse:green_swamp is Lush Swamp and traverse:temperate_rainforest is Coniferous Forest. The rest are just like Autumnal Woods -> traverse:autumnal_woods

You can also see the biome names in the autocomplete for the /findbiome command


Groups infrastructure

Similar to the Stack class, a Group class should provide for selecting and grouping cards together without forcing those underlying Card objects to be pulled into a stack. The objects contained within a Group will remain in their original location on the canvas and instead have a tag attached to them to indicate that they are grouped together.

The Group class is being abandoned since it was too similar to the Stack class, and did not offer a compelling difference in interactions. Instead, a Tag system that allows tags to be added to Card and Stack instances will be introduced in later versions.


cfitsio: 3.430 -> 3.450

Motivation for this change

Update cfitsio version from 3.430 to 3.450. Please also note that this update contains security fixes made in 3.440 (ChangeLog).
Added optional bzip2 support in derivation (disabled by default). This also includes a fixup of the cfitsio.pc file to point to the store path of the bzip2 libraries.

Things done

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

[ ] NixOS
[ ] macOS
[x] other Linux distributions (CentOS 7.4)

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] *Tested compilation of all pkgs that depend on this change manually
[x] Tested compilation with bzip support enabled and manually inspected libraries and pc-file.
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] **Fits CONTRIBUTING.md.
Apart from meta.maintainer

* I had to manually build some packages due to error cloning builder process (I'm running single user on CentOS without sandboxing).
** There's no maintainer, can I add one?
Built ok:

cfitsio
gimpPlugins.ufraw
ufraw
indilib
gildas
gimp-with-plugins
giv

Hello @xbreak and welcome around here :)

** There's no maintainer, can I add one?

Yes, definitely! You can add yourself to the maintainer list if you wish to maintain this package.
This should be done in a separate commit. See PR 61137 for a recent example.

@c0bw3b: Thanks for the review. I've updated the PR with the requested changes. Apart from your comments I also changed the url to use https since HEASARC are phasing out unencrypted FTP access.

Perfect. Thanks for your contribution.

Forgot to mention: wrt security fixes, the grave public vulnerabilities (4 CVE published) were already fixed in v3.43 that we ship in release 19.03
Now 3.44 may have cleaned up some more codebase but it's undocumented what was fixed exactly and there is no CVE. So exploitability is very close to null.
For this reason I think a backport to stable is not warranted here.


Merge/upstream to 1.5.1

Update develop to the latest 1.5.1 release.  This the last version to support rebar2

+1


Workflow to deploy to NPM

This repository contains code imported by other projects and they could benefit from @thesis/solidity-contracts packages published to NPM registry containing *.sol files from this repo.
Tagging @michalinacienciala - not a top priority right now but in case you'll have some spare cycles, worth looking at.

@pdyraga, could you add me to the project? I have the workflow ready to push, but don't have privileges.
ERROR: Permission to thesis/solidity-contracts.git denied to michalinacienciala.
fatal: Could not read from remote repository.

Added you @michalinacienciala,  you can accept the invite at https://github.com/thesis/


Bugfix missing parameters on json2ytmusic prints

Because of missing parameters that we're being printed on "json2ytmusic.py" the code would crash.
In these changes, we now check for the field "author name" on the youtube destination playlist; and also when searching for a matching music on youtube, we check if the field "artists [0] name" exists, before printing.
This fixed the code crash on the cases that those fields weren't present (which were many when I was converting my playlists).

Thanks!


ZstdDecompressCtx: pass nativePtr directly to JNI calls

This avoids having to lookup the field and fixes a bug where the wrong fieldId was passed causing a segfault if
ZstdDecompressCtx#reset() was called before ZstdCompressCtx() was used.

Yes, that makes sense. I don't know why I didn't pass the ptr by value.

Just released 1.5.4-2 with that fix and similar refactor of the ZstdCompressionCtx.


Add all PEGI categories/descriptors to Generic rating body

As requested by IARC:

Generic has no records in Descriptor table, it uses the complete set of PEGI descriptors
Generic has no records in AgeRating table either, it uses the complete set of PEGI age ratings, but for ageRatingID 55 it shows a 12+ icon, i.e. when PEGI shows an exclamation point icon Generic shows “12+”.

I'm r+ing this from looking through it. Also because this has gone on enough. :)


Error resolving a CSS file import with custom Webpack rule

Hi!
I'm (eventually) attempting to build a PostCSS/cssnext setup on top of Next.js, but somehow importing a CSS file cannot be resolved.
My pages/index.js file tries to import the pages/index.css file (that exists):
import './index.css'

With the Webpack config:
next.config.js:
module.exports = {
  webpack(config) {
    config.module.rules.push({
      test: /\.css$/,
      exclude: /node_modules/,
      loader: ['style-loader', 'css-loader']
    });
    return config;
  }
};

results in
output:
yarn run v0.15.1
$ next
> Using "webpack" config function defined in next.config.js.
 DONE  Compiled successfully in 3004ms

> Ready on http://localhost:3000
{ Error: Cannot find module './index.css'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/kpuputti/code/projects/nextlatest/pages/index.js?entry:3:1)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3) code: 'MODULE_NOT_FOUND' }

Package versions in package.json:
  "dependencies": {
    "css-loader": "^0.26.1",
    "next": "2.0.0-beta.12",
    "style-loader": "^0.13.1"
  }

Do I need to do some extra setup to get the resolving work, or how should I approach this? Thanks!

https://github.com/css-modules/css-modules-require-hook
as i heard this works perfectly!

I have a similar issue with raw importing markdown.
next.config.js
module.exports = {
  webpack: (config, { dev }) => {
    config.module.rules.push({ test: /\.md$/, loader: 'raw-loader' });
    return config;
  }
}

code
import React from 'react';

import render from '../md/renderer';
import Wrapper from '../components/Wrapper';

import content from './index.md';

export default () => (
  <Wrapper>
    {render(content)}
  </Wrapper>
)

error
> Ready on http://localhost:3000
{ Error: Cannot find module './index.md'
    at Function.Module._resolveFilename (module.js:472:15)
    at Function.Module._load (module.js:420:25)
    at Module.require (module.js:500:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/joel/sites/joelburget.com/pages/index.js?entry:6:1)
    at Module._compile (module.js:573:32)
    at Object.Module._extensions..js (module.js:582:10)
    at Module.load (module.js:490:32)
    at tryModuleLoad (module.js:449:12)
    at Function.Module._load (module.js:441:3) code: 'MODULE_NOT_FOUND' }

As an additional data point, if I load the page in the browser (showing the error), then edit my source with any change, including adding a blank line, the page live reloads and shows the expected content. But when I reload I get the error page again.

Also, I was running 2.0.0-beta.0 when I first saw this error and have since upgraded to 2.0.0-beta.9 and still see it.

It seems like the problem is an imparity between server and client side rendering. You add a webpack loader for some new file type but it doesn't apply on the first render (because SSR doesn't involve bundling via webpack, right?), so it doesn't work. But if you manage to re-render on the client (either buy following a link or triggering HMR) it works.
If this is correct, the whole extending your webpack config to add additional loaders use case is flawed, because SSR is at the core of Next.js. @rauchg
The alternative is to rely on Babel transforms instead of webpack loaders, because those get applied consistently.

Guys, yes this is a real problem.
The real issue comes when we need to deal with the server side.
Since we don't(and can't) run webpack on the server, if a module introduce a new file extension to require, it'll be kind a hard to do.
Just like @skidding mentioned, babel plugins will be the solution for this. (At least in the short term)

@arunoda No way to get this working on the server? Something like this? https://github.com/halt-hammerzeit/universal-webpack

Thanks  @davidrossjones. I have seen similar projects. But we need find a reliable but performant way to do it. Need to investigate into these tools.

I have the same problems when I import the bootstrap css. Is there any solution?

Has any one tried using https://github.com/istarkov/babel-plugin-webpack-loaders with success?

@noeljackson That should be something interesting. I'd like to play with this.

@arunoda It seems like babel-plugin-webpack-loaders should work, but then  I run into an issue with loading pages and webpack-hot-middleware-client ... I tested this with Rauch's blog example of next.js This is the type of error I get.
Module build failed: TypeError: /Users/noel/n/optimized.technology/pages/2014/7-principles-of-rich-web-applications.js?entry: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.parse (path.js:1494:5)
    at Object.<anonymous> (/Users/noel/n/optimized.technology/webpack.config.js:16:35)
    at Module._compile (module.js:570:32)
    at loader (/Users/noel/n/optimized.technology/node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/noel/n/optimized.technology/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)

 @ multi ./~/next/dist/client/webpack-hot-middleware-client ./pages/2014/7-principles-of-rich-web-applications.js?entry

I think i solved this. Have a look at https://github.com/davibe/next.js-css-global-style-test and #544

@davibe I found that the repo you linked to loaded the css / scss but caused other issues. For example, I wasn't able to deploy successfully. Really wish there was better support for css imports in some way... And I don't get why <style jsx>{interpolatedStyles}</style> doesn't work. We should be able to use css as modules some way...

This is actually a duplicate of #544. Closing this in favor of having the full CSS importing discussion there.