Validate descriptors

part of: https://github.com/creek-service/creek-platform/issues/4
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage decreased (-0.5%) to 98.462% when pulling 7d3713f5b735401f2112ae19110dd3f43f331eb5 on validate_components into 17f897b2d721a4aae8452754c56cd54d5bdfa08a on main.


Import of Enum from .d.ts only used as type results in unused import in JS

Bug Report
Have a .d.ts in a package/another file with an enum like:
export enum MyEnum {
    a = 0,
    b,
    c,
    d
}

Have a file which imports that enum and uses it like such:
import { MyEnum as MyEnumFromModule } from "my-package";

enum MyEnum {
    a = MyEnumFromModule.a,
    b,
    c,
    d
}

Once transpiled to JavaScript, there should not be any generated imports/requires like const my-package_1 = require("my-package") in the file.
Recently, I am now seeing such a require be generated, and it is marked unused with a message like: 'my-package_1' is declared but its value is never read.ts(6133)
I have seen the expected behavior in:

4.5.5
4.6.0-beta

I have seen the wrong behavior in:

4.6.1-rc
4.6.2
4.7.0-dev.20220304

🔎 Search Terms
enum unused .d.ts regression
🕗 Version & Regression Information

This is a regression
This changed between versions 4.6.0-beta and 4.6.1-rc
This is the behavior in every version I tried, and I reviewed the FAQ for entries about enums

⏯ Playground Link
I had a hard time creating a playground for this, as my repro requires importing from another file.
💻 Code
See above.
🙁 Actual behavior
See above.
🙂 Expected behavior
See above.

@MRayermannMSFT what are your tsconfig / CLI options?

@andrewbranch
{
    "compilerOptions": {
        "allowJs": false,
        "forceConsistentCasingInFileNames": true,
        "importHelpers": true,
        "module": "commonjs",
        "noFallthroughCasesInSwitch": false,
        "noImplicitAny": false,
        "noImplicitReturns": false,
        "noImplicitThis": false,
        "noUnusedLocals": true,
        "noUnusedParameters": false,
        "outDir": "./out/app",
        "preserveConstEnums": false,
        "resolveJsonModule": true,
        "skipLibCheck": true,
        "strictNullChecks": true,
        "target": "esnext",
    },
    "include": [
        "./app/**/*"
    ]
}

@andrewbranch any update on this? :)

I'm unable to provide a playground link since the repro requires importing another file, but here's the generated JS for the example TS input files which shows the unused import:
exporter.ts
export enum Enum {
  X = 'x',
}

main.ts
import {Enum} from './exporter';

export enum ValuesInInitializer {
  ENUM_MEMBER = Enum.X,
}

Generated js:
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.ValuesInInitializer = void 0;
const exporter_1 = require("./exporter"); // unused import in JS
var ValuesInInitializer;
(function (ValuesInInitializer) {
    ValuesInInitializer["ENUM_MEMBER"] = "x";
})(ValuesInInitializer = exports.ValuesInInitializer || (exports.ValuesInInitializer = {}));

// @module: commonjs

// @filename: enum.ts
export enum MyEnum {
  a = 0,
  b,
  c,
  d
}

// @showEmit
// @filename: index.ts
import { MyEnum as MyEnumFromModule } from "./enum"

enum MyEnum {
  a = MyEnumFromModule.a
}

Workbench Repro

Lol @andrewbranch that's a lot of reactions.

If only I could react with each of those twice over, there would be one for every I spent getting this to work after I thought I’d already be done

@andrewbranch I'll add a round of reactions to give you the twice over. Thanks for taking the time to look at this. :)


Support generating an import depfile (.d) like GCC & Clang -MD option

When using the GN build system, we need to specify all imported emboss files (including recursively imported files) as inputs to the action target that runs embossc. It would be simpler and more maintainable to use a depfile that was generated by emboss. The format of the depfile is a Makefile like the ones generated by GCC and Clang when the -MD option is used.
I haven't tried, but I think this format might work:
a.emb: b.emb c.emb

What I'm not sure of is what gn expects the rule name to be. It might need to be "my_script.py" instead of "a.emb".

It looks like the rule name needs to be the name of the output file (e.g. a.emb.h: b.emb).


quick translation of the read me

Your English is much better than mine... Thanks.

btw you should mirror this PR https://github.com/doctrine/common/pull/71 it will ease the metadata implementaiton.


Anchor links to same page shows as broken

Issue:
Anchor links on internal or same page shows as broken.
My dev setup:
I am able to replicate this issue on basic Silverstripe site
My composer.json
    "require": {
        "php": "^7.1 || ^8",
        "silverstripe/recipe-plugin": "^1.2",
        "silverstripe/recipe-cms": "4.7.3@stable",
        "silverstripe-themes/simple": "~3.2.0",
        "silverstripe/login-forms": "4.3.0@stable",
        "dnadesign/silverstripe-elemental": "^4.5"
    },

To Replicate:

In existing or new content block, create an anchor tag
Click Insert Link -> Anchor on page
Chose above anchor tag
Save/Publish Page
New Tag is generated as
Link to some anchor

Related
https://github.com/silverstripe/silverstripe-elemental/issues/796
ACs

[ ] Broken anchor on existing pages are not reported as broken links

PRs

https://github.com/silverstripe/silverstripe-elemental/pull/911

Note

The current logic for identifying broken anchor is very weak and will report a lot of false positive aside from Elemental blocks. Given that, we think it's better to remove it and only report anchor link broken if the parent page is missing all together

Thanks for reporting Amol.
Could I get you to quickly find the exact versions of cms and elemental that you're running?  You can do that with
composer show | grep '/cms\|/silverstripe-elemental'
Cheers

dnadesign/silverstripe-elemental          4.5.0   Elemental pagetype and collection of Elements
silverstripe/cms                          4.7.1   The SilverStripe Content Management System

Hi
We are having similar issues.  Anchor links on the same page show as broken. Any updates on this?
Just adding my findings below if that helps in debugging the issue further.
Anchors work fine when you select a different page on the "Link to an anchor on a page" popup modal form, but not when you select the same page. (Though doesn't throw any error in the console.)
However, AnchorSelectField::getAnchorsInPage()  method does not seem to get called on the initial form load; I'm guessing that the initial set of information in the AnchorSelectField is just loaded from the current WYSIWYG field only and not the whole page.
Adding below list of element module versions and their dependencies.
dnadesign/silverstripe-elemental                             4.0.5                                  Elemental pagetype and collection of Elements
dnadesign/silverstripe-elemental-list                       1.2.0                                  Adds a new element for nested elements
dnadesign/silverstripe-elemental-userforms            3.0.0                                  Adds a new element for usersforms
silverstripe/cms                                                        4.7.1                                  The SilverStripe Content Management System
symbiote/silverstripe-elemental-dashboard             1.0.x-dev 7e14217             Dashboard module with three column elemental area layout
thewebmen/silverstripe-elemental-grid                    2.x-dev dc60207               Elemental grid module

Cheers
Khushbu

Core issue is that SiteTreeLinkTracking_Parser (which is used by the SiteTreeLinkTracking DataExension, which DOES run on elemental blocks) assumes that page content is $page->content, while elemental content is $page .. ElementalAreas() .. Elements() ... HTMLText fields (which are also used in templates)
} elseif (!empty($matches['anchor'])) {
    // Ensure anchor isn't broken on target page
    $anchor = preg_quote($matches['anchor'], '/');
    $broken = !preg_match("/(name|id)=\"{$anchor}\"/", $page->Content); // <<< here's your issue
}

https://github.com/silverstripe/silverstripe-cms/blob/4/code/Model/SiteTreeLinkTracking_Parser.php#L72
Seems like need to add quite a bit of API to do this properly, something along these lines:
// SiteTree.php
public function getRendereredContent(): string
{
    $renderedContent = [];
    $this->updateRenderedContent($renderedContent);
    $this->extend('augmentRenderedContent');
}

// protected to allow subclasses to override this i.e. NOT include $page->Content on BlockPage
protected function updateRenderedContent(array &$renderedContent)
{
    $renderedContent[] = $this->Content;
}

// BlockPage.php
protected function updateRenderedContent(array &$renderedContent)
{
   // noop
}

// ElementalPageExtension.php
public function augmentRenderedContent(array &$renderedContent)
{
    foreach ([ElementalAreas] as $area) {
        foreach ($area->Elements() as $element) {
           foreach ($element->[HTMLText fields] as $field) {
              // this is assuming that ALL HTMLText fields are rendered in templates, should probably have a private static array to specific what will is rendered
              $renderedContent[] = $element->$field;
           }
        }
    }
}

This would allow use to update SiteTreeLinkTracking_Parser to use $page->getRenderedContent() to look for broken links

It's perhaps also worth noting there's the dream of a single 'content' API: https://github.com/silverstripe/silverstripe-cms/issues/2454

Yup, that single content API is pretty much what's required here

The root problem here is that anchors inside an elemental block are not properly supported. This will be resolved with #186, so I'm closing this issue in favour of that one.


Maps with non-default atmos and/or parallax (nukie planet, ...) broke

Description

Screenshots

nuke op planet is space now
probably related to maploader changes
also affects glacier on nyano

nukieplanet was saved as a grid.

nukieplanet was saved as a grid.

Probably my fault but when I asked how I should save it I was told savegrid, how does it need to be saved, as a map?

nukieplanet was saved as a grid.

Probably my fault but when I asked how I should save it I was told savegrid, how does it need to be saved, as a map?

yeah. When I told you grid I was thinking of infiltrator.
At least this doesn't break master anymore.

@metalgearsloth  This appears to be because SwapRootNode in RobustToolbox's MapLoaderSystem is replacing the saved entity that had the Map component with Parallax and MapAtmosphere, with an entirely new entity lacking all of this.
It's following the code path starting here: https://github.com/space-wizards/RobustToolbox/blob/4e0deb2e423c9d100141dada33c8bf88038802d1/Robust.Server/GameObjects/EntitySystems/MapLoaderSystem.cs#L490

@Vordenburg that's intentional.
Fixed in #12650


How to get the labels of BVCC test wav?

How can I get BVCC test dataset? I only found data and label of train and val in VoiceMOS codalab, but I don't know how to get the labels of test wav. Is it opensource?

Hi @jiusansan222,
We are preparing an all-in-one package containing all the materials of the VoiceMOS Challenge 2022, including the ground truth labels of the test set. We will support instructions on how to access the labels and perform evaluation once it is released.

Has the dataset been released yet? The codalab competition website doesn't seem to work, is there any other method to get the labels? Could you E-mail me a copy? Thanks!

I recommend to use this script to get the data: https://github.com/unilight/sheet/blob/main/egs/bvcc/local/data_download.sh


Possibility to add custom config to node-local-dns

Is your feature request related to a problem? Please describe.
We should expose the node-local-dns configmap to be configurable from apps config, so that one can add custom config to node-local-dns.
Describe the solution you'd like
Expose node-local-dns configmap to apps config.
Definition of done:
An administrator can now add custom config to node-local-dns through the apps config.

try to include this in apps v0.31


Cover JSON data in Data node control

What would that feature address
I have some transactional data as json file representing a list of shops with various characteristics address, size, location, opening time, type, owner, contact, etc... The structure of the document is globally the same all the time, but time to time a new field appears,  disappears or changes. I am using data node to keep track of the changes since it is edited by many people, and because I also have sql data nodes on the side.
I want to show the JSON data node in the data node control.
Description of the ideal solution
The ideal solution would be to have the possibility to collapse and expand recursively the various sections of the document. A syntax coloration or a visual hint could give the type of the field displayed like in the following example

{"web-app": {
  "servlet": [
    {
      "servlet-name": "cofaxCDS",
      "servlet-class": "org.cofax.cds.CDSServlet",
      "init-param": {
        "configGlossary:installationAt": "Philadelphia, PA",
        "configGlossary:adminEmail"<EMAIL_ADDRESS>        "configGlossary:poweredBy": "Cofax",
        "configGlossary:poweredByIcon": "/images/cofax.gif",
        "dataStoreDriver": "com.microsoft.jdbc.sqlserver.SQLServerDriver",
        "dataStoreUrl": "jdbc:microsoft:sqlserver://LOCALHOST:1433;DatabaseName=goon",
        "dataStoreInitConns": 10,
        "dataStoreMaxConns": 100,
        "dataStoreConnUsageLimit": 100,
        "dataStoreLogLevel": "debug",
        "maxUrlLength": 500}},
    {
      "servlet-name": "cofaxEmail",
      "servlet-class": "org.cofax.cds.EmailServlet",
      "init-param": {
      "mailHost": "mail1",
      "mailHostOverride": "mail2"}},
    {
      "servlet-name": "cofaxAdmin",
      "servlet-class": "org.cofax.cds.AdminServlet"},

    {
      "servlet-name": "fileServlet",
      "servlet-class": "org.cofax.cds.FileServlet"},
    {
      "servlet-name": "cofaxTools",
      "servlet-class": "org.cofax.cms.CofaxToolsServlet",
      "init-param": {
        "templatePath": "toolstemplates/",
        "log": 1,
        "logLocation": "/usr/local/tomcat/logs/CofaxTools.log",

        "fileTransferFolder": "/usr/local/tomcat/webapps/content/fileTransferFolder",
        "lookInContext": 1,
        "adminGroupID": 4,
        "betaServer": true}}],
  "servlet-mapping": {
    "cofaxCDS": "/",
    "cofaxEmail": "/cofaxutil/aemail/*",
    "cofaxAdmin": "/admin/*",
    "fileServlet": "/static/*",
    "cofaxTools": "/tools/*"},

  "taglib": {
    "taglib-uri": "cofax.tld",
    "taglib-location": "/WEB-INF/tlds/cofax.tld"}}}

Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] Create related issue in taipy-doc for documentation and Release Notes
[ ] Check if a new demo could be provided based on this, or if legacy demos could be benefit from it
[ ] Ensure any change is well documented

@vhfgosselin @dinhlongviolin1 @toan-quach ?

Thank you for the issue @EYisaac. This feature aligns with what the Data Node viewer aims to do.
You could also use the tree visual element to obtain this effect in the meantime.
@jrobinAV @FabienLelaquais what do you think about it?

I would prefer it to be in a data node control instead of a tree control. Especially for editing the content of the JSON file.
I guess I can use the tree if there is no other way.

I agree! This is just a workaround in the meantime

It is a great idea. @FabienLelaquais Let's discuss this.

Will it be in the next release?

Will it be in the next release?

This won't be in the next release. It is still an open issue.

 Thank you

Hey @FlorianJacta ! Can i work on this issue ? I have completed my previous issue and it has been marked hacktoberfest-apporved.
Also can you tell which file contains the logic for this issue.
Thanks

Here you go @THEBOSS0369, you can work on it! I will not be able to tell you which files are to be changed. Maybe, @jrobinAV or @FredLL-Avaiga will help you on that

@quest-bot embark

Hey Everyone ! I have created a PR for this issue #2164 . Please review it and give the feedback. Thanks!

Are we suppose to support json edition in this issue ? @FlorianJacta @jrobinAV @EYisaac ?

Are we supposed to support json edition in this issue ? @FlorianJacta @jrobinAV @EYisaac ?

Being able to edit the JSON data is part of the issue, yes.
However, if it is too complex at first, we can split it into two issues and start with the reading part only. But we should at least keep in mind that editing the data will, in the end, be part of it.

the chosen frontend package allows for editing.
So we'll be good when we decide to implement that feature.
Would you mind creating another issue for that purpose @jrobinAV ?

@FredLL-Avaiga SOunds fair. Let me create another ticket.
@EYisaac Do not hesitate to get back to us with more details on your edition needs, if ever.


is this a virus?

idk if this is a rat plz show me some proof

I get that you don't want to get a virus, but asking the developer of a minecraft song player mod if its a virus is taking it a step too far when it comes to not getting a virus. That is to the level where you are far too concerned about it.

I get that you don't want to get a virus, but asking the developer of a minecraft song player mod if its a virus is taking it a step too far when it comes to not getting a virus. That is to the level where you are far too concerned about it.


Write a TypeScript program to convert string to consonantcase

Description
Write a TypeScript program to convert string to consonantcase
Consonantcase is a style of writing in which all consonants are converted to uppercase and all vowels are converted to lowercase.
Input  : "hello world"
Output : "HeLLo WoRLD"

How to contribute

Save the solution in ConvertStringToConsonantcase.ts file
Add ConvertStringToConsonantcase.ts file in program/convert-string-to-consonantcase folder

!assign

!assign


SubSquid integration views

What's missing to speed up for us and where we could have advantage using SubSquid?
Potential targets

#1838 collection activity graph
artist profile - various tabs
collections list (new resolver to drop collections with 0 nft)

Would be great we could deliver it to v2.2

collection activity graph - done
artist profile - various tabs - done as separated service
collections list (new resolver to drop collections with 0 nft) - hidden by default on Koda


Adding person to camp is taking invalid age value

Subject of the issue
camp/<int:camp_id>/add_person/ is taking invalid age value.
Your environment

version of your python
which browser and its version
OS Type (iOS/Android/Linux/Windows)

Steps to reproduce
Visit camp/<int:camp_id>/add_person/ for any camp_id and try to add a negative value to the age. It'll successfully validate and respond with a success message.
Expected behaviour
Age should not take negative values.
Actual behaviour
Age is taking negative values.
I'm working to fix this issue

Sorry for being grumpy, but using PositiveIntegerField instead would have saved you from writing  a validator

@angrysumit94 changing the model at this time can be troublesome given the migrations and live database one has to take care. The solution which I've proposed is backward compatible.


[newrelic-infrastructure] cannot set enable process metrics to false

Bug description
The enableProcessMetrics lets you configure whether the infrastructure agent should send or not send process metrics ( https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/configuration/infrastructure-agent-configuration-settings#enable-process-metrics
). Accounts created before July 20, 2020 have this config option enabled by default. Therefore, they need to be able to set the value to false, otherwise the default value changes based on the account creation date. Currently, the chart only allows setting enableProcessMetrics's value to true, assuming that the default value is always false, which is not the case.
Which chart?
helm chart version: newrelic-infrastructure-2.0.2
What happened?
After setting enableProcessMetrics to false, customer was still receiving process data.
What you expected to happen?
Customer shouldn't receive any process data

Hello, it is an issue with the helm template that is not able to recognize the difference between the logical false, 0 and nil.
There are two workaround, the first one is to pass the bool as a string:
enableProcessMetrics: "false"

$ helm template ./charts/newrelic-infrastructure -f ./values.yaml | grep "PROCESS" -C2
            - name: "NRIA_ENABLE_PROCESS_METRICS"
              value: "false"

The second one is to pass the value with the agent config file and is mounted and mapped in the container

A proper fix would be to  include enableProcessMetrics: "false" in the values since we specify in the documentation that it is disabled by default

Great! option one looks good to me, whereas option two seems too hacky and prone to errors.

I'll add in the values, that commented out to keep the current behaviour, but making it easier to configure for the users


bump zerolog version

bump zerolog version to the latest v1.27.0 and update dependencies with:
$ go mod tidy -compat=1.17

this also solves all currently open CVEs, see Snyk Report before:

Does it matter what zerologr depends on? Shouldn't someone who builds and ships a binary bump up the dependencies? They can always pick something more recent than the versions that zerologr depends on.


Benchmarking + some perf. improvements

This PR adds a new app to the monorepo, core-lib-benchmark. It is a simple web app and a script to collect and compare Chrome traces using Puppeteer. The app is just a simple web app with a router, where each route can contain a set of components or layout that should be tested.
Benchmarks can be run like this:
$ nx run core-lib-benchmark:collect-trace decl-layout-1

This will fire up a dev server, and point the headless Chrome instance to the /decl-layout-1 route. The trace will be outputted as JSON to the ./trace-snapshots dir. The trace can be used as comparison in future runs, or opened and inspected in DevTools.
This PR also adds a caching optimization for constructed stylesheets, and replaces the use of the watch decorator with a setter in the @styleExpressionProperty decorator.
Example output, comparing difference between using cached stylesheets, versus no caching:
Scripting: 843.55ms
Rendering: 504.05ms
Painting: 4.93ms
-------------------
Total: 1352.53ms

Compared to snapshot-decl-layout-1-m3pro:

Scripting: 82.70%
Rendering: 577.22%
Painting: 10.27%
-------------------
Overall: 150.19%

Other minor things:
Remove dyanmic line-height from input, since that is a textarea feature
Remove inline-size style from badge, since it overrode width and caused broken layout.

Amazing work like always 👌


Will this get me VAC banned?

My friend told me that modifying the Steam client could result in a vac ban or not being able to play on Secure servers...

This does not modify anything that should trigger VAC.
At least this is true as of right now, I suppose it's always possible that Valve could change what VAC detects and wind up banning for this, it's not a possibility that I'm personally concerned about but of course I can't guarantee that it won't happen.


A move constructor for the session object

Hi -- it would be nice to have a move constructor for the session object.
I'm writing a wrapper around a connection pool for a project I'm working on, and having to return session instances in unique_ptrs.
Which is fine, I guess, but it would be nice to use value semantics.

Oh, just in case that sounded like a whinge -- love SOCI so far! :)

Adding a move ctor to this class shouldn't be a problem, if you can add the few required lines and a test to check that it's working, please feel free to submit a pull request with them. Just please use #ifdef SOCI_HAVE_CXX_C11 around the new code as SOCI still supports compiling in C++98 mode.

I'll have a look in the week -- cheers, @vadz

Good idea, thanks in advance @biot023

I've had a quick look on my lunch hour -- you'll need to bear with me -- the code changes are probably easy enough, but I've got to figure out the test framework and work out how to test my changes! :)


How can i get the coordinates of div while dragging

I need to get the x,y coordinates of dragged item. please help

use the 'onDrag' event (you can send an id of your element to it), for example:
on html:
'onDrag: ctrl.myFunc(my_elem_id)'
inside your code/controller:
myFunc = function(event, ui, id){
console.log(id)
}


Session cookies break requests-oauth

Hi,
requests 0.8 breaks requests-oauth. See the related issue in requests-oauth:
https://github.com/maraujop/requests-oauth/issues/5
After debugging both together, I've found out the culprit is this line:
https://github.com/kennethreitz/requests/blob/develop/requests/sessions.py#L190
Cookies were not updated automatically in sessions before 0.8. If I add self.cookies = {} before sending the request, requests-oauth starts working again.
Not sure if this is a bug or you want me to set cookies to an empty dictionary in my hook.
Cheers,
Miguel

I don't see what the problem is, but the requests behavior is intentional.

How would cookies break your hook?

Me neither, but trust me, if I set them to an empty dict, tests start passing again.
I thought you would have a clue about it. I'm guessing Twitter OAuth API doesn't support cookies?

Poking at this with Charles, so far the only difference I'm seeing is the presence of cookies on the 2nd request.
Gist: https://gist.github.com/1371423
Trying out other libraries to see how they behave.

My understanding was that Twitter supported specs 1.0 and 1.0a. I've tried removing oauth_body_hash and oauth_verifier and it breaks the same way. So it's not because passing those parameters with cookies at the same time.

I'm trying to implement something simple to pass the OAuth bits in headers, and see if they like that more.
-I
On Thursday, November 17, 2011 at 11:53 AM, Miguel Araujo wrote:

My understanding was that Twitter supported specs 1.0 and 1.0a. I've tried removing oauth_body_hash and oauth_verifier and it breaks the same way. So it's not because passing those parameters with cookies at the same time.

Reply to this email directly or view it on GitHub:
https://github.com/kennethreitz/requests/issues/272#issuecomment-2774121

Also as @juanriaza says, this is not an API specific thing, Rdio fails the same way and it was working before.

@idangazit
I've moved OAuth bits to headers, but OAuth isn't working for a simple Twitter status POST example, so I must be doing something wrong, but I cannot catch the error.
Headers: {'Authorization': 'OAuth%20oauth_nonce%3D%2273947544%22%2C%20oauth_timestamp%3D%221321529518%22%2C%20oauth_consumer_key%3D%22CONSUMER_KEY%22%2C%20oauth_signature_method%3D%22HMAC-SHA1%22%2C%20oauth_version%3D%221.0%22%2C%20oauth_token%3D%OAUTH_TOKEN%22%2C%20oauth_signature%3D%225IYmrXKbEMp5npH%2FUrwcH0H%2FZ5s%3D%22', 'Content-Type': 'application/x-www-form-urlencoded', 'Accept-Encoding': 'identity, deflate, compress, gzip', 'Accept': '*/*', 'User-Agent': 'python-requests/0.8.1'}
URL: http://api.twitter.com/1/statuses/update.json
Params: {}
Data: {'status': 'Kind of a random message 0.862699448264', 'wrap_links': True}
2011-11-17T12:31:58.369048   POST   http://api.twitter.com/1/statuses/update.json
{"error":"Could not authenticate with OAuth.","request":"\/1\/statuses\/update.json"}

Can you spot anything wrong here? I've debugged it as much as possible.
Even though I'm not sure this will fix the cookies error, I think it's a good try. If you want to look at the code, I can put it in a branch.
Miguel

At this doesn't look any longer related to requests, but the problem seems to be in how OAuth API providers handle cookies. I've disabled cookies in requests-oauth and I'm closing both issues.
Cheers,
Miguel


Potential security issue

Hello 👋
I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@0xshdax) has found a potential issue, which I would be eager to share with you.
Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.
Looking forward to hearing from you 👍
(cc @huntr-helper)

Thank you for contacting us!
Personally I have no experience with SECURITY.md files yet, perhaps we'll add one later.
In the meantime you could contact the leader of SocketCluster team @jondubois via personal email<EMAIL_ADDRESS>or via direct messages in Gitter https://gitter.im/jondubois

Ok thank you! :))

@psmoros Thank you for your report.
The issue you mentioned only appears to affect docker commands which are intended to be executed in a dev (not production) environment on the user's own machine (which they have full control over). It doesn't appear to allow privilege escalation since the user already has full access to code/containers running on their own host machine and could execute any command they like inside (or outside) containers anyway. It's also important to note that the user in our case is either a developer or sys admin so they are trusted; I cannot see any realistic scenario whereby an unauthorized user would be able to execute the commands you mentioned without already having full access to the host.
That said, if you can give specific examples of how it could be a problem for some users in our particular case (e.g. maybe an unintended use case which we haven't considered), feel free to send me a follow-up email.

Thanks @jondubois! @0xshdax will follow up if they have any disagreements for the moment we'll consider this report invalid... Sorry for wasting your time

Hello @jondubois ,
This issue is like CVE-2021-44684, If the developer does not accept this issue, there is no problem. I am simply informing them of potential security issues.
Thanks.


The host Activity doesn't implement PermissionAwareActivity

Description
When I try to use PermissionsAndroid to require some permissions with my app, I have an error that says:
Tried to use permissions API but the host Activity doesn't implement PermissionAwareActivity.
I've used the example code from the React-Native doc.
Expected Behavior
Android Permissions management
Observed Behavior
I've done some research that tell me to eject my app from Expo and modify manually the main activity, however, I prefer not do to that for now.
Looking for another solution.
Environment
Please run these commands in the project folder and fill in their results:

npm ls react-native-scripts<EMAIL_ADDRESS>npm ls react-native<EMAIL_ADDRESS>npm ls expo<EMAIL_ADDRESS>node -v: v8.11.3
npm -v: 6.4.0
yarn --version:
watchman version:

Also specify:

Operating system: MACOS
Phone/emulator/simulator & version: Galaxy s8 on expo app

+1

+1


Find improvements

close #1168

Fix #1170
Added UpdateSourceTrigger=PropertyChanged in find tool window xaml

Fix #1172


Slashes in path parameters

Currently openapi-core allows anything inside path parameters, as it uses the format parser to create regexes. This way the pattern
/foo/{arg1} will match /foo/bar/baz. This is contrary to the openapi3 spec which disallows matches like this (as discussed e.g. https://github.com/OAI/OpenAPI-Specification/issues/502)
What’s more troublesome, if we have two paths defined:

foo/{arg1}
foo/{arg1}/baz

Then whether the path foo/bar/baz matches the first one or the other depends on the order in which dictionary is iterated.
Is there any good reason we do this like that?

No i see, this is fixed in master, sorry for this.


[GLUTEN-1767][CH]Bug fix posexplode function argument check error

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
(Fixes: #1767)
posexplode in clickhouse backend will make the convert:
posexplode(array_or_map) -> CH: arrayJoin(map), in which map = mapFromArrays(range(length(array_or_map)), array_or_map)
But somethimes in mapFromArrays the second argument type is nullable, which can not pass the arugment check.
And when use the posexplode function to transfrom value from a map, like posexplode(split(map['key'], ',')), in clickhosue backend will  use the arrayElement function to extract the map value, and it would force the convert the key argument to UInt32, and this also will be check as illegal argument .
How was this patch tested?
unit tests
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

LGTM


Fix the issue where namespaceSelector never takes effect when podSelector is nil

What type of PR is this?
/kind bug

What this PR does / why we need it:
Fix the issue where namespaceSelector never takes effect when podSelector is nil
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Did you close this by mistake or did you conclude that it was working as intended?


[kernel] Add RPM spec

This should track the latest stable kernel for now starting with Linux 6.3 which will be released in a couple of weeks.
https://kernel.org/

Building the Linux kernel with GitHub Actions results in No space left on device error.
+ echo BUILDING A KERNEL FOR x86_64...
+ /usr/bin/make -s 'HOSTCFLAGS=-O2  -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64  -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection   ' 'HOSTLDFLAGS=-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' ARCH=x86_64 olddefconfig
USING ARCH=x86_64
BUILDING A KERNEL FOR x86_64...
+ perl -p -i -e 's/^CONFIG_BUILD_SALT.*/CONFIG_BUILD_SALT="6.3.13-200.playtron.fc38.x86_64"/' .config
+ /usr/bin/make -s 'HOSTCFLAGS=-O2  -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64  -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection   ' 'HOSTLDFLAGS=-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' ARCH=x86_64 'KCFLAGS= ' WITH_GCOV=0 -j2 bzImage
vmlinux.o: warning: objtool: hyperv_init+0x42f: unreachable instruction
+ '[' 1 -eq 1 ']'
+ /usr/bin/make -s 'HOSTCFLAGS=-O2  -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64  -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection   ' 'HOSTLDFLAGS=-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' ARCH=x86_64 'KCFLAGS= ' WITH_GCOV=0 -j2 modules
objcopy: drivers/net/ethernet/aquantia/atlantic/stiY4CzQ: No space left on device
btf_encoder__write_elf: failed to add .BTF section to 'drivers/net/ethernet/aquantia/atlantic/atlantic.ko': 2!
Failed to encode BTF
make[1]: *** [scripts/Makefile.modfinal:62: drivers/net/ethernet/aquantia/atlantic/atlantic.ko] Error 1
make[1]: *** Deleting file 'drivers/net/ethernet/aquantia/atlantic/atlantic.ko'
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1954: modules] Error 2
+ exit 1
error: Bad exit status from /var/tmp/rpm-tmp.vuVTUb (%build)
    Bad exit status from /var/tmp/rpm-tmp.vuVTUb (%build)

RPM build errors:
Error: Process completed with exit code 1.

GitHub Actions only provides virtual machines with 14 GB of storage space. For building a Linux kernel, you need a lot more space than that.
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources
We will have to compromise and only test building the source RPM and skip the binary RPM build.


Removed Example Folder

It contained another copy of PINCache and was causing duplicate
definition errors.

Hi @yuzaken you'll have to explain a bit more about the issue. This pull request deletes the example app which shows how to use the library!

Please feel free to send another pull request or open an issue if you feel this was closed in error.


add function get_photo

The get_photo function was not in message.py so we couldn't get the file id

Thanks for contributing.


Blocks: landing page hero

Noting that the right column has a video that launches in a popout div and that the main image is a composite of two images where the text bubble is overlaid onto the background image, but that image is a separate overlay div element positioned absolutely over the landing page hero, so likely shouldn't be included in the section structure and should instead be a separate block

@david-granberg :


[feature request]Does libgdx need a scripting language? Ideas and possible contributors as well as possible problems.

Libgdx has a JSON parser and a XML parser. It is my opinion that it should also feature a wrapper that supports the creation of basic scripts, either using a unique language or a language that already exists. I would be willing to write some of the code for this, but before I commit to thousands of lines of coding I would like to get an idea of how many people would use this.
Many great game engines and frameworks use scripting languages to avoid the need to recompile games when making changes. It is, as a matter of fact, recommended to use a scripting language for large projects. While most libgdx projects are small, some can be pretty big. For example, I was compiling my game to test it and it took fifteen minutes to complete. This is annoying, and I toyed around with the concept of creating my own scripting language, but the idea of debugging 2000+ more lines of code by myself was daunting.  It seems better and more efficient to break the work up between multiple devs than to try and accomplish such a task alone.
I want to keep with the reusable and extendable tradition of libgdx and have drafted the following (rough) graph of how the engine could work;

The Parser would be an interface to handle the syntax of the script while the Interpreter (an abstract class and the real meat) would handle expressions and logic. The java implementation would, of course, be custom implementations of the interfaces which tie together into a controlling class which can be instantiated in your create method and implemented in your render method.
Would this fit well with the main project? Should I add it to the main project?  Any ideas on how to implement it?

Reinventing the wheel yet again? What's wrong with any of: Lua, Scala/Groovy, JavaScript, Python, Ruby, Lisp etc, via either direct Gradle inclusion/preprecession or e.g. javax.script (http://docs.oracle.com/javase/7/docs/technotes/guides/scripting/programmer_guide/) or any other standard-compliant solution?

Pretty much. If you really wanted to create some more LibGDX specific language then go for it, it would stay as a third party extension though.

I've recently used Javascript (Rhino) with libgdx. Worked pretty well also on android, because with the proprietary mozilla API (not javax.script), it's possible to turn off optimizations and set language levels.

What's wrong with java? The entire modding community for minecraft adds to the game with extra classes, why introduce another language?
Is it the steep curve for the people to build a jar? or the fact that you can't distribute the java compiler with the game? I'd love to hear your thoughts.

I think that you should use whatever is available. Implementing (and maintaining!) an own scripting engine is in most use cases unneeded.
That said. A time ago I looked into adding scripting support, because we still have a problem with managing the shaders. Adding a small (graphical/programmable) layer might make it easier to manage and extend uber shaders. Preferable while keeping it possible for users to copy paste glsl code (the language should be similar to glsl). Ofcourse that adds some specific requirements and it doesn't necessarily have to actually compile/execute, just generate the final shader. Fixing this shader problem is still on my todo list, but lack of time...
So, if anyone is going to make a custom scripting engine, then keep this in mind ;)

xoppa, you kicked it up another notch by talking about scripted glsl shaders... XD

@xoppa I am actually currently working on the language. I have basic if/then and (semi-working) functional syntax working with regular expressions. I will keep that in mind when I post the code on GitHub and add it if I can. I will have to read up on glsl shaders, though first. Before that though I will have to fix my functions (weird bugs occur when calling functions from within the script that are not predefined in Java classes), add support for math operations (gonna be difficult I think, especially without causing the script to slow performance down), and touch up on many minor bugs that make it impractical to use. As it is it is not the fastest possible implementation, but I do intend on releasing it as open source after I play around with it in my game.
I don't feel comfortable with releasing my code yet, as I want to fix some things first, though, such as add an "Object" system to my script to make better abilities for it. I am up to my head in things I need to do before I release it as open source (because I just want to get an open source extension started and then open source it for people to do with as they please). It turns out that this is a fun challenge.
@FyiurAmron I looked at your repo and studied the code but (honestly, no offense intended) I had trouble reading your naming scheme. I am dyslexic and the lower cases combined with the "_" were killing my eyes. I do have one question though, why did you use chars? I am using Strings and the standard libgdx file system. Are chars faster? Do they create less clutter? I am using java.utils.regex.* to parse the scripts and they seem (mostly) fine after I debug.
@xGnoSiSx I want to add a scripting language to stop from having to recompile my project every time I fix a few bugs. I could probably figure out how to include a java compiler if I wanted to, but the purpose is not explicitly modding support.

Regular expressions? It sounds pretty weird to parse a scripting language. Unless it has a very basic syntax and you don't mind performance.
Regular expression are good for the lexical part (identifiers, numbers and so on). Usually for the syntax you use grammars.
I'd suggest using Ragel.

@jacksondus the code has a severe C legacy, so it's naming convention is mostly C. String is just an immutable wrapper for char[] - you won't see String used as a base type anywhere in any serious tokenizer/lexer, since the most basic data struct appearing there is a single char. To be able to do any real tokenization/parsing/lexing, you'll need a properly constructed state machine. https://en.wikipedia.org/wiki/Ragel (suggested by @davebaol) is indeed a very stable and quite standard solution, easy to implement and maintain. Alternatively, you can use https://en.wikipedia.org/wiki/JavaCC , http://www.antlr.org/ or any other tool. If you're using regexes, both the extend of your lexical analysis and the performance will suffer.
Creating and maintaining own lexical/syntactical analysis framework is IMO just asking for development hell and Yet Another Abandoned Project, unless you have a couple of good developers willing to works a couple of years for free.

@FyiurAmron I apologize for the closes and reopens. I feel the need to say that tokenizing with regex and then building lexeme's and compiling them into a parse tree (which is what is actually executed as it is traversed and actually what I meant by regex parsing). And referring to your dyslexic joke - following that logic don't you see the possible risk of a dyslexic writing code in general?

You don't need to reopen to comment. Also, it feels like this conversation is no longer relevant for libgdx so should probably be moved elsewhere.


Fix for issue #925

Addresses compatibility issue when running with older SdlRouterService (4.5 or earlier).
Fixes #925
This PR is ready for review.
Risk
This PR makes no API changes.
Testing Plan
n/a
Summary
This change makes SDL Proxy 4.7 to work with older SdlRouterService.
Changelog
Breaking Changes

n/a

Enhancements

n/a

Bug Fixes

This change fixes issue #925.

Tasks Remaining:

n/a

CLA

[x] I have signed the CLA

This PR has extremely wide ranging changes included. For that reason I will be closing the PR. Please resubmit a PR with only the changes you believe address the issue along with no unnecessary code changes.


Available modules differ between management and compute nodes

I am trying to run some MPI jobs on my CitC. However, the available MPI modules are different on the management and compute nodes. I have compiled my code on the shared filesystem logged in on the management node, using the module mpi/openmpi-x86_64. However, when I then tried to load it on the compute nodes (as part of my job script), it told me that it did not exist.
Below are the listed available modules on the management node:

[joealex@mgmt run_test]$ module avail
--------------------------------------------------------- /usr/share/Modules/modulefiles ---------------------------------------------------------
dot         module-git  module-info modules     null        use.own
---------------------------------------------------------------- /etc/modulefiles ----------------------------------------------------------------
mpi/mpich-3.2-x86_64 mpi/openmpi3-x86_64  mpi/openmpi-x86_64
And the compute node:
[opc@vm-standard2-2-ad1-0001 ~]$ module avail
--------------------------------------------------------- /usr/share/Modules/modulefiles ---------------------------------------------------------
dot         module-git  module-info modules     null        use.own
---------------------------------------------------------------- /etc/modulefiles ----------------------------------------------------------------
mpi/mpich-3.0-x86_64 mpi/mpich-x86_64     mpi/openmpi3-x86_64

There is only one that overlaps...

Hi Joe,
Thanks for reporting that. It's an odd one, because we use the OS package manager to install the MPIs and we don't specify a version, just the name (Here's the commit that does that https://github.com/ACRC/slurm-ansible-playbook/commit/340846035060866b87583b82f560ea68ab223326 )
One difference between the management and compute nodes is that the *-devel packages are installed on the management node and only the runtime ones on the compute nodes. That could be where the divergence is coming in.
Since Oracle release regular updates to the OS images, and these are configured in both the terraform (for mgmt) and ansible (for compute) repos, there is a chance they might get out of sync. But that isn't the case here, they're currently both on the Feb 20 release:

Node
Image
Source

mgmt
Oracle-Linux-7.6-2019.02.20-0
https://github.com/ACRC/oci-cluster-terraform/blob/827d73d5f4ef3ae6d7d6e4f071a6d6f20cb1d7d7/variables.tf#L36-L41

compute
Oracle-Linux-7.6-2019.02.20-0
https://github.com/ACRC/slurm-ansible-playbook/blob/71947683f6a1a0da3d299fe65ea3200665589247/roles/slurm/files/citc_oci.py#L141-L146

We're still looking in to this. One option would be install a non OS MPI package with EasyBuild or spack - I'll see if I can come up with a tested workaround.
For "newer" MPIs we need a rebuild of the Slurm packages with PMIx support (https://github.com/ACRC/slurm-ansible-playbook/issues/24). @milliams is working on this (https://github.com/ACRC/slurm-ansible-playbook/pull/27) however he is away this week and I think because of the change we reverted in #17 we can't just point at the slurm18 branch in terrafrom.tfvars


Seventh Korean l10n work for release 1.18

Translate reference/command-line-tools-reference/feature-gates.md int… (#22240)
Fix issue of broken links to translated docs (#22105)
Fix issue of document link in some ko documents (#22379)
Translate tasks/administer-cluster/access-cluster-services.md into Ko… (#21776)
Fix issue with 'Linux' and 'Windows' notation in Korean docs (#22362)
Fix issue of broken links to translated docs #2 (#22270)
Fix issue with k8s.io/ko/docs/concepts/overview/kubernetes-api.md (#22261)
Fix issue with k8s.io/ko/docs/concepts/overview/working-with-objects/ (#22263)
Fix incorrect notation of 'directory' into Korean (#22155)
Fix issue with k8s.io/ko/docs/concepts/overview/components.md (#22232)
Update outdated files in dev-1.18-ko.7 (#22128)
Modify spacing term ReplicaSet in Korean (#22148)

Co-authored-by: Jerry Park<EMAIL_ADDRESS>Co-authored-by: woopyoung<EMAIL_ADDRESS>Co-authored-by: coolguyhong<EMAIL_ADDRESS>Co-authored-by: PyungHo Yoon<EMAIL_ADDRESS>Co-authored-by: Seokho Son<EMAIL_ADDRESS>Co-authored-by: jmyung<EMAIL_ADDRESS>Co-authored-by: Ian Y. Choi<EMAIL_ADDRESS>

/hold

/hold cancel

/lgtm
/approve


Make compatible with io.js

../node_modules/nan/nan.h:409:19: error: no type named 'ExternalAsciiStringResource' in 'v8::String'; did you mean 'ExternalStringResource'?

io.js ships a newer V8 version where String::ExternalAsciiStringResource
has been replaced with String::ExternalOneByteStringResource

via https://github.com/rvagg/nan/pull/223 via https://github.com/iojs/io.js/issues/386

Whoops, I misread the logs. This is actually failing on nan.h. I'll keep this open incase the dependency needs a bump, but the semver here seem loose enough that it shouldn't be an issue.

Okay, so nan v1.5 is out (and v1.4 is going to get a patch for io.js support as well) but them semver on pty.js is locking the project to v1.0.0 <= v0.1.1.
Updating this request to: can we get a semver bump on this dependency please?

https://github.com/iojs/io.js/issues/456

@snostorm would a semver bump be the only thing required to fix this issue?

I think that was all that was needed. I'll need to re-test to be sure. If it was that simple ... not sure why I didn't just PR, sorry.

I think this will depend on https://github.com/rvagg/nan/pull/265 to land -- the latest nan+iojs I have seems to hit the issue, which builds when built against the fix living via https://github.com/touhou-gensokyo/nan.git#master --
But the npm test still doesn't pass after a successful compile still fails

New pty.js released using nan v1.6.2. Hopefully this fixes something.

I'm still getting the error..

@chjj it builds with node-0.12 and iojs but the tests are all failing: timing out.

the example from the readme doesnt work with node-0.12.0

@chjj We'd love to have node-0.12 support. Is there anything we can do to help?

There is also @gottox rewrite of pty.js: https://github.com/Gottox/child_pty
I am no expert here; I only checked out child_pty and ran the tests under node-0.10 iojs and node-0.12.
Maybe @chjj and @gottox could give us a hint as to what direction we should take?

Pro pty.js
pty.js is better tested in production and actually used in more than just demo applications. Also debugging on MacOS is hard for me, as I haven't access to a MacOS System.
pty.js has windows support.
Pro child_pty:
As child_pty does not support windows, it can be much simpler and smaller. It borrows most of it's functionality and API from nodes core module child_process, hence the name. The whole projects is smaller than 150 lines of code, not counting the tests.
Furthermore child_pty does not shim the Stream objects as pty.js does. This implicates some nasty bugs in pty.js that this has unexpected values in some cases.

@Gottox much appreciated! I had not realised child_pty does not support windows. I am on a mac.

@chjj We're willing to help get pty.js compile for 0.12, but wouldn't want to end up having the effort done twice. Could you help coordinate?

Yeah, I first noticed the issue with v0.12 a little while ago. I spent a day trying to figure out what was wrong. It looks like the pty FDs just aren't getting polled or read from properly. I'm not sure there's an easy fix from the node side.
Originally, pty.js used fs.ReadStream and fs.WriteStream to read and write to the tty FDs. That turned out to cause thread pool exhaustion. We switched to using net.Socket. That also broke with a later release of node which disallowed tty FDs being used by net.Socket. We switched to using tty.ReadStream, which seemed appropriate. This also failed.
I can play around with it a bit more to see what I get working.

@javruben, also, it could be that fs.ReadStream and fs.WriteStream still work, but it may cause thread pool exhaustion still. I'll try to whip something up.

Also, a thing to note: if we switch to using a different mechanism, we won't be able to support older versions of node without including a bit of compatibility code. I really wish this didn't change so frequently.

After a minute or two of fumbling around, it looks like fs.ReadStream works for the tty fd, but fs.WriteStream does not. Very confusing. Even so, these may still exhaust the thread pool. We'll have to check.

I actually meant to address to @hmalphettes' concern with all that.
This build issue looks like a problem with nan.h, but I still don't have issues on linux. I'll try to reproduce it on OSX again.

@chjj, that commit builds and test fine on OSX 10.10.2 here. The readme example also works.
Downstream, webBoxio/atom-term2#90 is still giving the same error from the OP, but that may be a caching issue with atom / apm / npm, as that project's package.json points to master. Or maybe it needs a version bmp here? Not really sure. Maybe you or someone else here can shed some light on the issue there, maybe you can't. Either way, thanks for the time you put in.
$ apm install term2

# ...
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the pty.js package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls pty.js
npm ERR! There is likely additional logging output above.

# (full log available on request ;)

IT WORKS! :D Thanks so much @chjj

@chjj polling ReadStream helps to display some output, but unfortunately it introduces new issues:
var term = pty.spawn('bash', [], {
  name: 'xterm-color',
  cols: 80,
  rows: 30,
  cwd: process.env.HOME,
  env: process.env
});

term.on('error', function(err) {
  console.log("[error]", err);
});

displays errors { [Error: EAGAIN, read] errno: -11, code: 'EAGAIN' } every time interval function is called.

piping doesn't work

process.stdin.pipe(term)
term.pipe(process.stdout) // used to work with 0.10

the cpu usage is too high

polling interval is not cleared when terminal is closed

Strangely https://github.com/Gottox/child_pty works without polling so maybe the error is caused by a change in node steams?

@nightwing, odd. EAGAIN should be filtered out. I'll look into piping. The CPU usage was 1-2% higher for me due to the interval. I'll probably just implement the old fs.ReadStream (before it was refactored like crazy). That was a bit easier to work with and should suit our needs better.
child_pty seems to do the exact same thing. pty.js originally used the FS streams in the early days. I don't see why it wouldn't work now. I'll have to investigate. It could be that child_pty does not use non-blocking file descriptors, which means child_pty would severely fail if you get more than a few pty's open (assuming node/libuv handles the FDs the same way).

@nightwing, my suspicions were confirmed. The FS read stream works for child_pty because it doesn't set the tty FDs to nonblocking. That's bad. It should not be using blocking FDs. We can't settle for that. It causes strain on the thread pool (a thread necessary for each tty FD), eventually leading to thread pool exhaustion. I'll be including my own read stream so we don't need the interval.

@nightwing, here's a first pass at using our own ReadStream. Ideally we would implement our own IO watcher like node.js used to have to avoid unnecessary reads, but it's better than before, and definitely better than using blocking FDs.

I'll have to dig into node and libuv to see what became of IO watchers (as they were called in old versions of node.js). That's all I'm familiar with for polling async FDs in node.js. If anyone else has knowledge on the subject that would be good.

@nightshark, try the above commit. This might be a better fix. It simply wraps net.Socket and forces it to handle tty FDs like pipes (which is, in a way what they are). However, this might not work on all OSes. It would be nice to get people to test it.
This saves us a lot of trouble if the problem with using tty fds with net.Socket is negligible. I suppose we could research old node.js commits and find out.

@chjj awesome! This works well on ubuntu.

Good. Works on Arch and OSX too.


gComponent.data error with single data

This code has an error:
<g-composer data="10"></g-composer>
<script>
  console.log(document.querySelector('g-composer').data);
</script>

In console is displayed:
composer.js:1  Uncaught TypeError: Cannot create proxy with a non-object as target or handler

The error is related to trying to create a JavaScript Proxy for something that is not an object. This typically happens when you're trying to use a Proxy on a primitive type, like a number or a string. In this case, the  element might be trying to apply a Proxy to the value stored in the data attribute, which is a number, not an object. This issue is related with https://github.com/graphery/graphane/issues/4.

It is fixed in version 1.0.0-beta.4. Please confirm and close the issue.


initializeDateFormatting and Material delegate conflicting on tests

Hello, we were working on some test cases here and found an interesting conflict between the initializeDateFormatting helper and the MaterialApp delegate util.loadDateIntlDataIfNotLoaded(). If in our tests file we have a unit test case using the initializeDateFormatting and right after this case, we create another widgetTest the test fails due to a conflict.
Example:
Future main() async {
  test("Unit test example", () async {
    initializeDateFormatting('en', null);
    //... code test
  });

  testWidgets("Widget test example", (WidgetTester tester) async {
    // Arrange
    await tester.pumpWidget(const MaterialApp(
      locale: Locale('en'),
      localizationsDelegates: L10n.localizationsDelegates,
      supportedLocales: L10n.supportedLocales,
      home: Text('test'),
    ));
    await tester.pumpAndSettle();
  });
}

This error is being returned
When the exception was thrown, this was the stack:
#0      _UnmodifiableMapMixin.[]= (dart:collection/maps.dart:269:5)
dart-lang/i18n#352      initializeDateFormattingCustom (package:intl/date_symbol_data_custom.dart:35:19)
dart-lang/i18n#353      loadDateIntlDataIfNotLoaded.<anonymous closure> (package:flutter_localizations/src/utils/date_localizations.dart:25:33)
dart-lang/i18n#354      CastMap.forEach.<anonymous closure> (dart:_internal/cast.dart:288:8)
dart-lang/intl#4      _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:539:8)
dart-lang/i18n#355      CastMap.forEach (dart:_internal/cast.dart:287:13)
dart-lang/intl#6      loadDateIntlDataIfNotLoaded (package:flutter_localizations/src/utils/date_localizations.dart:21:8)
dart-lang/i18n#356      _MaterialLocalizationsDelegate.load.<anonymous closure> (package:flutter_localizations/src/material_localizations.dart:728:12)

After digging down on it we found the cause, it seems that inside the initializeDateFormatting it's loading the date patterns with this map dateTimePatternMap() which is a const. And when Material calls the loadDateIntlDataIfNotLoaded it's trying to update the map with a new value, but the map is a constant.
One way to avoid it is splitting the unit and widget tests into 2 diff files, but I believe this shouldn't be necessary since the Flutter tests framework allows us to have mixed tests on the same file. I would like to get your feedback about it and see how we can work from our side to improve it if necessary.

Hi @alanknight-wk, you claim that using a custom initialization should fix it, but I'm getting this error thrown with the custom initialize function as part of the stacktrace #1      initializeDateFormattingCustom (package:intl/date_symbol_data_custom.dart:35:19).  And the map that it's trying to modify in this case is: dynamic dateTimePatterns,  which is not const. I'm confused about how to fix this.


chore(contracts): Revert when no change happens in a state-changing function

What does this PR do?
Updated registries with additional check - if there is no change in the state revert the transaction.
Related ticket
Fixes #804
Type of change

[x] Chore
[ ] Bug fix
[ ] New feature
[ ] Documentation update

Check list

[x] Unit tests for any smart contract change
[ ] Contracts and functions are documented

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

Project coverage is 48.84%. Comparing base (66c8473) to head (6746306).

Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #834   +/-   ##
=======================================
  Coverage   48.84%   48.84%
=======================================
  Files          18       18
  Lines         389      389
  Branches       63       63
=======================================
  Hits          190      190
  Misses        196      196
  Partials        3        3

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


high pitch noise on micro:bit with kittenbot arcade shield

Description
When playing different makecode arcade games on the micro:bit 2.21 and kittenbot arcade shield 1.0, i noticed a high pitch noise coming from the micro:bit buzzer. I checked with the oscilloscope and measured a 16kHz ringing, see the attached screenshot.

When I used the screen using the arcade shield extension for microbit makecode, the noise is neither hearable nor visible. Which makes me believe that this bug is something that might be fixable by firmware.
To Reproduce
Steps to reproduce the behavior:

Generate jumpy plattformer or caterpillar hex files for the N3 hardware in microsoft arcade
Plug micro:bit into kittenbot arcade shield and copy hex file via USB to the micro:bit
Listen to the buzzer on the back of the micro:bit

As far as I understand, the relevant files are in the codal-nrf52833-dk repository since it contains the drivers for the N3 hardware.
My initial idea was to call the function that corresponds to the ubit.audio.set_silence_level(0) function of the microbit-v2 codal, but since the structure is actually quite different, this is trickier.
I found a similar function called: int Mixer2::setSilenceLevel(float level) in github.com/mmoskal/codal-nrf52833-dk/blob/master/source/Mixer2.cpp but im not sure if the problem really lies there.


Force Discharge stops working after one percent

I try using the recent version of the tool with the command:
"battery maintain 60 --force-discharge"
It starts to work but essentially reverts back to charging up after one percent of the battery was dropped.
I use a MacBook Pro M2 Max with a Thunderbolt Dock from Dell and an external monitor, keyboard and mouse. Yet I do not use clamshell mode.

I turned off smart battery charging. Yet, the charging still enabled itself every now and then.
Seems like mostly it enables itself as soon as 1% is dropped.

Same thing happens when trying to charge up. I am trying to go from 60% to 90% for a road trip tomorrow - it starts charging, then basically stops immediately.
No matter if "force-discharge" is set!
This is a blocking bug imho!


Fix order of signatures in PartialSign function

Related issues:
https://github.com/gagliardetto/solana-go/issues/84
https://github.com/gagliardetto/solana-go/issues/224

Thank you!


generalize tacitly fails

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Checked that your issue isn't already filed.

Specifically, check out the wishlist, open RFCs,
or feature requests.

Reduced the issue to a self-contained, reproducible test case.

Description
Invoking the generalize tactic does nothing although a suitable subterm is present.

Actual behavior:
example1a : generalize does nothing (maybe a failed rw as in example2b).
The issue seems to be due to i.val containing a reference to l.
Versions
Lean (version 3.3.1, commit d83b9ef3efbf, Release)
OS: Windows 7, 64bit

This is intended behavior. If we look at the state of the first example before the generalize with set_option pp.implicit true, we see
⊢ @subtype.val ℕ (λ (i : ℕ), i < @list.length ℤ l) i < @list.length ℤ l

and generalize and rw are both trying to replace both occurrences of list.length l with n, and only the second can be done without causing a type error. It is very difficult to determine which subsets occurrences can be replaced without causing a type error, so generalize just tries to replace all instances, and if this fails it just adds the equality to the context and leaves the goal unchanged.
simp works by a completely different method, and the first list.length l is not even accessible here because it is a dependent propositional argument.


Fix addressinput right click paste on init

@polymorpher this fixes the right-click to paste on address input for initial loading of the select box. But due to the nature of the select input box, as soon as a selection is made, the input value will be covered with the label, which makes it unable to right-click to paste again.

great, looks good


No function of formatting code in .jsx file

What should I do?
Hope add this function in code  soon.

duplicate of #140

Thanks,@jrieken.


Handle protobuf response in tracer

The previous code would only handle the thrift-based response format. This change adds handling for the proto response for both timing and errors.

@iredelmeier or @austinlparker  Can you review this? It looks like this affects clock skew correction on the JS tracer.


Move Mini Model

Possibly move Mine Model to other side so can see when when blocks take up the right side of the build.

I made configurable offsets in the next update.

I made configurable offsets in the next update.


Legal Files: change schema:pages to schema:pagination

Change schema:pages to schema:pagination. It's the wrong property.
Right now, this data property has two values attached, for example

schema:pages "S. 1",
"S. https://id.acdh.oeaw.ac.at/legalkraus/D_000001-002-000.xml" ;

The second value has an unsuitable "S. " – but needs to be removed as a whole anyway.

removed second property type entirely; changed first to schema:pagination "S. 2" ;
hope thats right @BOberreither ?!


Docs/tutorials registry

@holyhope
md doc lint failed.
I saw you removed the external DB, Redis, and storage configuration doc links, will you add them in other sections?

It is not yet planed. I saw that:

This documentation was outdated and was here because CRD were not strongly typed.
CRD documentation explains well all storage definitions.
The documentation I removed did not bring anything more than the CRD documentation.

Do not you agree?

It is not yet planed. I saw that:

This documentation was outdated and was here because CRD were not strongly typed.
CRD documentation explains well all storage definitions.
The documentation I removed did not bring anything more than the CRD documentation.

Do not you agree?

@holyhope
Ok, I got your plan. I agree. For better doc navigation experiences, I can create some doc links to point to the right section of the CRD spec doc for guiding users on how to customize the external services.
One more thing, maybe we also need to add comments on the CRD about the secret data of psql secret and redis secret?

It is not yet planed. I saw that:

This documentation was outdated and was here because CRD were not strongly typed.
CRD documentation explains well all storage definitions.
The documentation I removed did not bring anything more than the CRD documentation.

Do not you agree?

@holyhope
Ok, I got your plan. I agree. For better doc navigation experiences, I can create some doc links to point to the right section of the CRD spec doc for guiding users on how to customize the external services.
One more thing, maybe we also need to add comments on the CRD about the secret data of psql secret and redis secret?
@holyhope

I’ll merge this PR and append some info about the data of psql secret and redis secret as well as related links pointing to the right content sections located at CRD spec doc.


qt5, qt6: use versioned QML import paths in wrappers

Description of changes
Qt is smart enough to figure out the target Qt version for native plugins. However, Qt is not smart enough to figure out the target Qt version for QML imports, which causes all kinds of funny breakage when you start running Qt 5 applications from Qt 6 ones and vice versa.
So, do some minimally invasive surgery to make different Qt versions pick up different QML import path variables, so they don't mess with each other.
This is kind of very cursed, but what can you do.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

One concern I have with this is that it's no longer going to work with applications that vendor their own Qt, but I really hope none of those are importing nixpkgs QML, and if they are, there's going to be problems anyway.

Should we also change most other references like in kdeltachat? https://github.com/search?q=repo%3ANixOS%2Fnixpkgs QML2_IMPORT_PATH &type=code

The existing variables still work, these are added on top. We may have to migrate some NixOS things though...

We are already using versioned qtQmlPrefix, can we make use of that, e.g. filtering the paths in QML2_IMPORT_PATH by suffix.

We are already using versioned qtQmlPrefix, can we make use of that, e.g. filtering the paths in QML2_IMPORT_PATH by suffix (or sorting? So the correct ones are always prioritized).

We could in theory do that, but that requires way more invasive changes on the Qt side of things, and there's still the question of how to handle unversioned paths should they exist.

We could in theory do that, but that requires way more invasive changes on the Qt side of things

I would argue some filtering/sorting after all the search paths have been collected is not that invasive.

and there's still the question of how to handle unversioned paths should they exist.

That's why we might just sort the paths, so the unversioned ones are still available for use, albeit with a lower priority.

Qt sorts the paths internally, and in multiple places, so it's ... weird. I'm not really sure if there's a good way to reorder them.

Qt sorts the paths internally, and in multiple places, so it's ... weird. I'm not really sure if there's a good way to reorder them.

So we can also not just symlinkJoin them?

Never could really, because it needs to also pick up ambient stuff.

I'm sending it. Hopefully we have another cycle to fix this after this staging and before Plasma 6.


azcopy10 within cloud environments - errors out as --RESPONSE Status: 403 This request is not authorized to perform this operation.

We are trying to use Azcopy within the cloud i.e. from a VM to loading data into ADLS gen2, we are getting following error
RESPONSE Status: 403 This request is not authorized to perform this operation.
Which version of the AzCopy was used?
10.2.1
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
Azcopy.ps1 -SourceDirFile "F:\Sts*" -Destination_Azure "https://xxxxxxsdddd.dfs.core.windows.net/sdsdsd-dsdss-fsys-edsdsdl"
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered?
RESPONSE Status: 403 This request is not authorized to perform this operation.
Date: [Mon, 09 Sep 2019 21:04:49 GMT]
Server: [Windows-Azure-HDFS/1.0 Microsoft-HTTPAPI/2.0]
X-Ms-Error-Code: [AuthorizationFailure]
X-Ms-Request-Id: [24bcba9d-fsdsdf-0sdd-1ddd52-6xxxxxxxx000]
X-Ms-Version: [2018-11-09]
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?

Hi, @srini99mkl -- I'm not entirely sure what goes on within your AzCopy.ps1 file. Could you provide more detail on that?
As this is an auth related error, I need to understand what kind of auth you're trying to use as well as your actual scenario.

Hello,
Azcopy.ps1 has  just azcopy command
C:\Program Files (x86)\AzCopy" -SourceDirFile "D:\files*" -Destination_Azure "https://dddddssxxxxx.dfs.core.windows.net/sdsdsdv-001"
To get Outh2 autorization I am using
Azcopy azlogin command ….  I was able to login to my azure account from the VM(Azure VM) that calls above azcopy command.
From: adreed-msft<EMAIL_ADDRESS>Sent: Monday, September 09, 2019 5:29 PM
To: Azure/azure-storage-azcopy<EMAIL_ADDRESS>Cc: Arumilli, Srinivas<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-storage-azcopy] azcopy10 within cloud environments - errors out as --RESPONSE Status: 403 This request is not authorized to perform this operation. (#588)
Hi, @srini99mklhttps://github.com/srini99mkl -- I'm not entirely sure what goes on within your AzCopy.ps1 file. Could you provide more detail on that?
As this is an auth related error, I need to understand what kind of auth you're trying to use as well as your actual scenario.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-azcopy/issues/588?email_source=notifications&email_token=AMAWRLUAYEW3A4TZ24FVNN3QI25YXA5CNFSM4IVAHY62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6JDB3I#issuecomment-529674477, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMAWRLXATHZUNBFYMAVXCLTQI25YXANCNFSM4IVAHY6Q.
This message has been scanned for malware by Websense. www.websense.com

@srini99mkl That copy command you showed looks unusual. I don't recognize it as having the format of an AzCopy v10 command, nor does it look like a v8 command.
Also, you mentioned an "azlogin" command. There is no "azlogin" in AzCopy, it's just AzCopy login.
It sounds like you might have some mixed up versions of things.

I propose to close this, on the assumption that it was indeed some mixed up versions of things - e.g. using "azlogin" (from the cloud CLI) instead of AzCopy's own "AzCopy login". Let us know if you need it reopened.


new Function to provide region Value Size.

Changes proposed in this pull request
(Fill in the changes here)
Patch testing
(Fill in the details that how was this patch tested)
Other PRs
(Does this change required changes in other projects- snappyData, spark, spark-jobserver, aqp? Add the links of PR of the other subprojects that are related to this change)
Added new function to provide Region Value size
Registered the function in store.

duplicate  of SNAP-733


Remove roundtrip

Removes the double rountrip to validate decompiled blocks.
Extra: removes the "remove block" button.

https://github.com/Microsoft/pxt/issues/622

👍


You have hit the rate limit. Please-upgrade link doesn't work

Describe the bug
it has a link when you hit the rate limit in the response. you can click "upgrade". It did nothing for me. I am now less likely to upgrade
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-w78vx7
Steps to reproduce
hit the rate limit, try and click the link. doesn't work... It's because it's just an anchor with no href.
Expected behavior
it should be clickable.
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
performance.memory = {
  "totalJSHeapSize": 63736699,
  "usedJSHeapSize": 59994279,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = Seanmclem
Chat ID = 36c776a99be3

Additional context
Error:
You have hit the rate limit. Please Upgrade to keep chatting, or you can continue coding for free in the editor.

Hi @Seanmclem,
Appreciate the feedback! I have relayed this to the team and they are investigating - will follow-up here.

@Seanmclem this has been resolved! Thanks for the report 🙏🏻


docs: update to make styling more consistent

I have updated the Readme part by adding some icons aside two headings i.e. Environment and How to setup.

@naman-tiwari Hi! Please apply my and Missy suggestions, and then we will accept it and merge :)


[Compatibility Request] Deeper and Darker Support, Enderite Support

Make sure you are not opening a duplicate.

[X] I have searched the issue tracker and did not find an issue describing my bug.

Description of your suggestion.
Could it be possible to have working weapons for the Enderite and Warden materials? I'm no code expert, just asking for a modpack

Please provide the textures for this compatibility.

warden textures for medieval weapons.zip
If I provided more textures for the ender dragon mob from Adventure Z, would it be possible to have variant textures for it when spawning? I think that would be nice in multiplayer environments, so that every player has its own dragon.

Added with https://github.com/Globox1997/MedievalWeapons/commit/4fbb8ff61289c3965b9bad5c923f964d7d2f64c3


Feature/loading

Implement reusable component loading based on alceo documentation

[x] Loading Circle

[x] Loading Ellipsis

[x] Functional
https://user-images.githubusercontent.com/98725806/177745542-0801100c-1c08-4d3e-a641-f8cc562eb811.mov

Rada anehnya sebelah mana mas @MarioAtSirka ?

soalnya colornya itu ga ada brand color dari sirkanya gt caa, warnanya netral gt kan

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


delete old task nativeTest

Feature description
We recommend people to use testNative instead. It is confusing to have the other task around which is shown in the IDE.

testNative doesn't exist. The task is nativeTest.

testNativeImage was removed in b97d8fc590c47b2678d5bd0d7e2688d7c0f8c49d


Add ZonedDateTime converter to Long and vice versa

The goal of the PR is to use String instead of Date because the ZonedDateTime create from the database is slightly different than the original one causing some tests to fail when using Jhipster with mongo and elasticsearch. https://github.com/jhipster/generator-jhipster/pull/6595

@ramzimaalej Oh I understand now!! Yes, that makes sense.
What, however, I don't get is the need to have an instance as there's no state at all in the utils class. Can you enlighten me?

Nevermind my comment, I didn't see the whole file was like that...


Fix qemu test runner issues with symbolizer_test

We recently discovered that some tests that were skipped during CI builds because of how certain test labels conflicted with each other. Once the tags used for bazel test filtering were fixed, it was identified that the symbolizer_test.cc is flaky under the qemu test runner and so it was disabled (#1342). This is likely due to timing issues since the test relies on sleeping before certain assertions are made.

I think there might be inconsistencies with our bazelrc file used in development (meaning the fixes applied to #1342 may be relevant elsewhere). When attempting to run the symbolizer_test with qemu locally, bazel believes the test should be filtered. I had to apply the following diff to reproduce the qemu failures (P385). Without those changes, bazel is unable to find a test target as seen below:
$ bazel test -c opt --config=qemu-bpf --test_output=all  --cache_test_results=no --remote_download_outputs=all //src/stirling/source_connectors/perf_profiler/symbolizers:symbolizer_test  --test_output=streamed --//bazel/test_runners/qemu_with_kernel:kernel_version=latest
INFO: Invocation ID: eade06e7-b056-48ec-909d-fb419f20f8b4
INFO: Streaming build results to: https://bb.corp.pixielabs.ai/invocation/eade06e7-b056-48ec-909d-fb419f20f8b4
WARNING: Streamed test output requested. All tests will be run locally, without sharding, one at a time
WARNING: All specified test targets were excluded by filters
INFO: Analyzed target //src/stirling/source_connectors/perf_profiler/symbolizers:symbolizer_test (1 packages loaded, 13 targets configured).
INFO: Found 1 target and 0 test targets...
Target //src/stirling/source_connectors/perf_profiler/symbolizers:symbolizer_test up-to-date:
  bazel-bin/src/stirling/source_connectors/perf_profiler/symbolizers/symbolizer_test
INFO: Elapsed time: 0.550s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
ERROR: No test targets were found, yet testing was requested
INFO: Streaming build results to: https://bb.corp.pixielabs.ai/invocation/eade06e7-b056-48ec-909d-fb419f20f8b4
INFO: Build completed successfully, 1 total action

I am mistaken that there are additional fixes necessary for the bazel config. #1342 will allow bazel to identify that the test target applies for the qemu-bpf config.


Update dependencies

Shows two scoreboards at the moment 🤔

I'll remove the double-load workaround for map dragging for now. There's been many major chromium updates since then so it may not be a problem anymore.


GH-33649: [C++] Fix documentation on Newly Added Methods on ExecPlan

This is a minor fix for CI failure in https://github.com/apache/arrow/pull/33623#issuecomment-1381326714.
TODO

[x] Self review
[x] Check for CI status
[x] Mark PR ready for review

Closes: #33649

Ah, sorry, I did not see this when I logged on this morning and I fixed this on my existing docs PR.
https://github.com/apache/arrow/commit/22136989ab28954bb3ad42514fbd130848b2fc0d
Can you review my wording?  If it's ok we can probably close this.

closing this PR in favor of https://github.com/apache/arrow/commit/22136989ab28954bb3ad42514fbd130848b2fc0d

Ah, sorry, I did not see this when I logged on this morning and I fixed this on my existing docs PR.
2213698
Can you review my wording? If it's ok we can probably close this.

Sorry I wasn't online at that time. And I see the PR is merged, the wording is fine. Since, I am closing this one.


Custom ToastContainer component not functioning as expected

As seems to be the case with a few people, I'm struggling to style the ToastContainer. After reading the docs and this issue I was under the impression that I could provide a custom ToastContainer component which I have done, but the issue I have now is that when triggering a notification the toast container isn't populated. If I don't pass my custom container to the components prop on the ToastProvider then the toast is populated. Is there something I'm not passing down from the ToastProvider to the ToastContainer?
Also worth noting I tried to customise the existing component in the same way the docs do with the Toast component to no avail.
import { DefaultToastContainer } from 'react-toast-notifications';

Any pointers would be much appreciated!
_app.js
import App, { Container } from "next/app";
import React from "react";
import { ToastProvider } from "react-toast-notifications";

import ToastContainer from "../components/notifications/toastContainer";
import Toast from "../components/notifications/toast";

class MyApp extends App {
  render() {
    const { Component, pageProps } = this.props;

    return (
      <Container>
        <ToastProvider components={{ ToastContainer, Toast }}>
          <Component {...pageProps} />
        </ToastProvider>
      </Container>
    );
  }
}

export default MyApp;

ToastContainer.js
import React from "react";
import styled from "styled-components";

const Root = styled.div`
  position: fixed;
  top: 20px;
  left: 50%;
  transform: translateX(-50%);
  z-index: 20;
`;

const ToastContainer = ({ children, ...rest }) => {
  return <Root {...rest}>{children}</Root>;
};

export default ToastContainer;

Have the same issue :/

I would just like to move it from the default position of upper right and I am have zero luck.
If anyone has and example code that would be nice

@MarkLyck
In this lib (see docs), they have given flexibility to override Toast component, not the ToastContainer. Although technically we can override this also, as you are trying to do (not recommended). your code is not working because you are missing few important things in your custom ToastContainer component, here is is modified version of your ToastContainer component which should work.
import React from 'react';
import styled from 'styled-components';
import { TransitionGroup } from 'react-transition-group';

const Root = styled.div`
  position: fixed;
  top: 20px;
  left: 50%;
  height: 100%;
  maxheight: 100%;
  overflowx: hidden;
  overflowy: auto;
  transform: translateX(-50%);
  z-index: 20;
  padding: 10px;
`;

const ToastContainer = ({ children, placement, ...rest }) => {
  return (
    <Root {...rest}>
      <TransitionGroup component={null}>{children}</TransitionGroup>
    </Root>
  );
};

export default ToastContainer;

@nate456789 please the documentation for placement.

@ConnorTCM @MarkLyck after refactoring a bunch of stuff and upgrading to emotion@10, the default toast container now accepts styles however you'd like to provide them:
import { DefaultToastContainer } from "react-toast-notifications";

const ToastContainer = props => (
  <DefaultToastContainer
    className="toast-container"
    css={{ outline: "4px dashed green" }}
    style={{ background: "red" }}
    {...props}
  />
);

Checkout this CodeSandbox: https://codesandbox.io/s/toast-container-styles-duxs5

I'm afraid I can't afford the time right now to implement the solution described in #14, but I think this will be sufficient for most instances.

Thank you for your response @priteshjha4u, that would have worked. Since refactoring, the consumer no-longer needs to understand  or implement "react-transition-group".

People in this thread may find the solution I came up with here useful. It's working for me: https://github.com/jossmac/react-toast-notifications/issues/44


when use DisplacementFilter & ColorMatrixFilter , there is a strange thing.

open http://pixijs.github.io/pixi-filters/examples/
First , enable the DisplacementFilter, it's already enabled by default.
Then enable the ColorMatrixFilter,  you will find the  strange thing.
I don't know how to describe the thing.
Please try it by yourself.

It seems likes it messes with the offset of the displacement texture and everything shifts over. Not sure why that's happening.

Yep, that's a bug.

In last version , this bug has disappeared... Is there anyone fix it ?

When use another filter(some , not all)  with DisplacementFilter , the ratio in DisplacementFilter.applyFilter will changed :
    apply(filterManager, input, output)
    {
        const ratio =  (1 / output.destinationFrame.width) * (output.size.width / input.size.width);

        this.uniforms.filterMatrix = filterManager.calculateSpriteMatrix(this.maskMatrix, this.maskSprite);
        this.uniforms.scale.x = this.scale.x * ratio;
        this.uniforms.scale.y = this.scale.y * ratio;

         // draw the filter...
        filterManager.applyFilter(this, input, output);
    }


add js and css

Please Consider. What you did was bad.

Please Consider. What you did was bad.

If i may, how do you think you are? dude


Rename dockerfile to Dockerfile

Somehow the runner became case sensitive and starting to fail the deployment. This change worked for me.

修改后确实有用，但为什么不合并呢！ @renzhaosy


[release-1.13] add trivy exception

Add exception for CVE-2024-26147.
Kind
/kind cleanup
Release Note
NONE

/test pull-cert-manager-release-1.13-trivy-test-ctl

I should have used the make target.
My point is that:

If the problem is https://testgrid.k8s.io/cert-manager-periodics-release-1.13#ci-cert-manager-release-1.13-trivy-test-ctl
how did you test that this fixes the problem?

When I check out this PR and run the make target, it fails.
$ gh pr checkout 6835 --force
From https://github.com/cert-manager/cert-manager
 * branch                refs/pull/6835/head -> FETCH_HEAD
HEAD is now at f97af3c50 add trivy exception

$ make trivy-scan-ctl
cd _bin/tools/ && ln -f -s<EMAIL_ADDRESS>trivy
/home/richard/projects/cert-manager/cert-manager/_bin/tools/trivy image --input _bin/containers/cert-manager-ctl-linux-amd64.tar --format json --exit-code 1
2024-03-07T16:09:01.307Z        INFO    Vulnerability scanning is enabled
2024-03-07T16:09:01.308Z        INFO    Secret scanning is enabled
2024-03-07T16:09:01.310Z        INFO    If your scanning is slow, please try '--scanners vuln' to disable secret scanning
2024-03-07T16:09:01.310Z        INFO    Please see also https://aquasecurity.github.io/trivy/v0.44/docs/scanner/secret/#recommendation for faster secret detection
2024-03-07T16:09:01.363Z        INFO    Detected OS: debian
2024-03-07T16:09:01.364Z        INFO    Detecting Debian vulnerabilities...
2024-03-07T16:09:01.364Z        INFO    Number of language-specific files: 1
2024-03-07T16:09:01.365Z        INFO    Detecting gobinary vulnerabilities...
{
  "SchemaVersion": 2,
  "ArtifactName": "_bin/containers/cert-manager-ctl-linux-amd64.tar",
  "ArtifactType": "container_image",
  "Metadata": {
    "OS": {
      "Family": "debian",
      "Name": "11.9"
    },
    "ImageID": "sha256:83b701955f654ca04be89ac716ffc90182bbea94ef4afc8ee14e540cf43e44ff",
    "DiffIDs": [
      "sha256:70c35736547b3e931b1a31e6d5e7df15ca445f3923da9c5bf966e67fe7f08564",
      "sha256:6fbdf253bbc2490dcfede5bdb58ca0db63ee8aff565f6ea9f918f3bce9e2d5aa",
      "sha256:1df9699731f7846ad827986563c27981294fd53a7ce7b4665f87936b0d9a7945",
      "sha256:ff5700ec54186528cbae40f54c24b1a34fb7c01527beaa1232868c16e2353f52",
      "sha256:d52f02c6501c9c4410568f0bf6ff30d30d8290f57794c308fe36ea78393afac2",
      "sha256:e624a5370eca2b8266e74d179326e2a8767d361db14d13edd9fb57e408731784",
      "sha256:1a73b54f556b477f0a8b939d13c504a3b4f4db71f7a09c63afbc10acb3de5849",
      "sha256:d2d7ec0f6756eb51cf1602c6f8ac4dd811d3d052661142e0110357bf0b581457",
      "sha256:4cb10dd2545bd173858450b80853b850e49608260f1a0789e0d0b39edf12f500",
      "sha256:b6a7d418a890b8591e951458fe8603e0698606f60c2a80eb544b292ee00ae0a5",
      "sha256:9ef0ae7d0f90dac63e9020d5d9424eda9b2c2e554c86bed22db07da0d6d19719",
      "sha256:4f64750281fd6550e0d6dd3438f637c8228a932c796802ee67c6c60ed9adb07a"
    ],
    "ImageConfig": {
      "architecture": "amd64",
      "created": "2024-03-07T15:47:17.079496895Z",
      "history": [
        {
          "created": "0001-01-01T00:00:00Z"
        },
        {
          "created": "0001-01-01T00:00:00Z"
        },
        {
          "created": "0001-01-01T00:00:00Z"
        },
        {
          "created": "0001-01-01T00:00:00Z"
        },
        {
          "created": "0001-01-01T00:00:00Z"
        },
        {
          "created": "0001-01-01T00:00:00Z"
        },
        {
          "created": "0001-01-01T00:00:00Z"
        },
        {
          "created": "0001-01-01T00:00:00Z"
        },
        {
          "created": "0001-01-01T00:00:00Z"
        },
        {
          "created": "2024-03-07T15:47:16.902211875Z",
          "created_by": "LABEL org.opencontainers.image.source=https://github.com/cert-manager/cert-manager",
          "comment": "buildkit.dockerfile.v0",
          "empty_layer": true
        },
        {
          "created": "2024-03-07T15:47:16.902211875Z",
          "created_by": "USER 1000",
          "comment": "buildkit.dockerfile.v0",
          "empty_layer": true
        },
        {
          "created": "2024-03-07T15:47:16.902211875Z",
          "created_by": "COPY ctl /app/cmd/ctl/ctl # buildkit",
          "comment": "buildkit.dockerfile.v0"
        },
        {
          "created": "2024-03-07T15:47:17.001772411Z",
          "created_by": "COPY cert-manager.license /licenses/LICENSE # buildkit",
          "comment": "buildkit.dockerfile.v0"
        },
        {
          "created": "2024-03-07T15:47:17.079496895Z",
          "created_by": "COPY cert-manager.licenses_notice /licenses/LICENSES # buildkit",
          "comment": "buildkit.dockerfile.v0"
        },
        {
          "created": "2024-03-07T15:47:17.079496895Z",
          "created_by": "ENTRYPOINT [\"/app/cmd/ctl/ctl\"]",
          "comment": "buildkit.dockerfile.v0",
          "empty_layer": true
        }
      ],
      "os": "linux",
      "rootfs": {
        "type": "layers",
        "diff_ids": [
          "sha256:70c35736547b3e931b1a31e6d5e7df15ca445f3923da9c5bf966e67fe7f08564",
          "sha256:6fbdf253bbc2490dcfede5bdb58ca0db63ee8aff565f6ea9f918f3bce9e2d5aa",
          "sha256:1df9699731f7846ad827986563c27981294fd53a7ce7b4665f87936b0d9a7945",
          "sha256:ff5700ec54186528cbae40f54c24b1a34fb7c01527beaa1232868c16e2353f52",
          "sha256:d52f02c6501c9c4410568f0bf6ff30d30d8290f57794c308fe36ea78393afac2",
          "sha256:e624a5370eca2b8266e74d179326e2a8767d361db14d13edd9fb57e408731784",
          "sha256:1a73b54f556b477f0a8b939d13c504a3b4f4db71f7a09c63afbc10acb3de5849",
          "sha256:d2d7ec0f6756eb51cf1602c6f8ac4dd811d3d052661142e0110357bf0b581457",
          "sha256:4cb10dd2545bd173858450b80853b850e49608260f1a0789e0d0b39edf12f500",
          "sha256:b6a7d418a890b8591e951458fe8603e0698606f60c2a80eb544b292ee00ae0a5",
          "sha256:9ef0ae7d0f90dac63e9020d5d9424eda9b2c2e554c86bed22db07da0d6d19719",
          "sha256:4f64750281fd6550e0d6dd3438f637c8228a932c796802ee67c6c60ed9adb07a"
        ]
      },
      "config": {
        "Entrypoint": [
          "/app/cmd/ctl/ctl"
        ],
        "Env": [
          "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
          "SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt"
        ],
        "Labels": {
          "org.opencontainers.image.source": "https://github.com/cert-manager/cert-manager"
        },
        "User": "1000",
        "WorkingDir": "/"
      }
    }
  },
  "Results": [
    {
      "Target": "_bin/containers/cert-manager-ctl-linux-amd64.tar (debian 11.9)",
      "Class": "os-pkgs",
      "Type": "debian"
    },
    {
      "Target": "app/cmd/ctl/ctl",
      "Class": "lang-pkgs",
      "Type": "gobinary",
      "Vulnerabilities": [
        {
          "VulnerabilityID": "CVE-2019-25210",
          "PkgName": "helm.sh/helm/v3",
          "InstalledVersion": "v3.12.3",
          "Status": "affected",
          "Layer": {
            "DiffID": "sha256:b6a7d418a890b8591e951458fe8603e0698606f60c2a80eb544b292ee00ae0a5"
          },
          "SeveritySource": "ghsa",
          "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2019-25210",
          "DataSource": {
            "ID": "ghsa",
            "Name": "GitHub Security Advisory Go",
            "URL": "https://github.com/advisories?query=type%3Areviewed+ecosystem%3Ago"
          },
          "Title": "helm: shows secrets with --dry-run option in clear text",
          "Description": "An issue was discovered in Cloud Native Computing Foundation (CNCF) Helm through 3.13.3. It displays values of secrets when the --dry-run flag is used. This is a security concern in some use cases, such as a --dry-run call by a CI/CD tool. NOTE: the vendor's position is that this behavior was introduced intentionally, and cannot be removed without breaking backwards compatibility (some users may be relying on these values).",
          "Severity": "MEDIUM",
          "CVSS": {
            "redhat": {
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
              "V3Score": 6.5
            }
          },
          "References": [
            "https://access.redhat.com/security/cve/CVE-2019-25210",
            "https://github.com/helm/helm",
            "https://github.com/helm/helm/issues/7275",
            "https://nvd.nist.gov/vuln/detail/CVE-2019-25210",
            "https://www.cncf.io/projects/helm",
            "https://www.cncf.io/projects/helm/",
            "https://www.cve.org/CVERecord?id=CVE-2019-25210"
          ],
          "PublishedDate": "2024-03-03T21:15:49.867Z",
          "LastModifiedDate": "2024-03-04T13:58:23.447Z"
        }
      ]
    }
  ]
}
make: *** [make/scan.mk:42: trivy-scan-ctl] Error 1
richard@LAPTOP-HJEQ9V9G:~/projects/cert-manager/cert-manager$ echo $?
2

Am I doing something wrong? How did you test this before you put it up for review?

@wallrj You can test this by running the make trivy-scan-all command before and after the change.
You will see that the https://github.com/advisories/GHSA-r53h-jv2g-vpx6 disappears.
What you are showing is a different CVE (compare the CVE numbers), that I have not looked at yet.

Here is the prow Job:
https://github.com/cert-manager/testing/blob/365d570125e751a7d9aac4148d8c0ef23e42168c/config/jobs/cert-manager/cert-manager/release-1.13/cert-manager-release-1.13.yaml#L1501-L1539
When I run make trivy-scan-ctl (the command run in that prow job) on my laptop it exits with error code 2,
which I would expect to cause the prow job to fail.
Is there something in the Prow configuration that configures Trivy to show only HIGH and CRITICAL vulnerabilities?
/approve
/lgtm

Cycling home and thinking more about this, I suppose I might have something in my laptop environment that is causing trivy to show MEDIUM errors....I'll check tomorrow.