Unable to overwrite zookeeper values.yaml when installing via helm in kubernetes

I'm trying to change some of the default values in zookeeper and they aren't getting applied.
I tried to change multiple stuff only in zookeeper pod and nothing was being applied to I thought I'm doing something very bad and went with this very easy example:
After adding the signoz repository, I use:
helm --namespace platform install my-release signoz/signoz -f over.yaml
Contest of over.yaml:
clickhouse:
  securityContext:
    enabled: true
    runAsNonRoot: false
    runAsUser: 0
    runAsGroup: 0
    fsGroup: 0

zookeeper:
  securityContext:
    enabled: true
    runAsNonRoot: false
    runAsUser: 0
    runAsGroup: 0
    fsGroup: 0`

(yes I know that I should not run the pods as root, but this is an example of something that worked on clickhouse so helm did apply the values from the over.yaml file and didn't on zookeeper).
After everything deploys checking the yamls of every pod, clickhouse pod have the changes in securityContext while zookeeper has the default values it ships from the bitnami charts https://github.com/bitnami/charts/blob/main/bitnami/zookeeper/values.yaml:
securityContext:
        allowPrivilegeEscalation: false
        runAsNonRoot: true
        runAsUser: 1001
securityContext:
    fsGroup: 1001

I tried also, but with no difference:
zookeeper:
  podSecurityContext:
    enabled: true
    fsGroup: 0
  containerSecurityContext:
    enabled: true
    runAsUser: 0
    runAsNonRoot: false

What I'm doing wrong?

@sati-max can you please add indentation of the override YAML? Perhaps use code blocks.

@sati-max can you please add indentation of the override YAML? Perhaps use code blocks.

I've edited the question with code blocks, didn't realize that github cut the "spaces".

Ok, I'm dumb / didn't notice that in https://github.com/SigNoz/charts/blob/main/charts/signoz/values.yaml the zookeeper pod is "inside" the clickhouse pod. Changing the over.yaml to have this dependence fixed this issue and the (again, very bad example) root:root permissions in zookeeper got applied.
The correct over.yaml (if anyone would stumble on similar issue) should be this:
clickhouse:
  securityContext:
    enabled: true
    runAsNonRoot: false
    runAsUser: 0
    runAsGroup: 0
    fsGroup: 0

  zookeeper:
    podSecurityContext:
      enabled: true
      fsGroup: 0
    containerSecurityContext:
      enabled: true
      runAsUser: 0
      runAsNonRoot: false

(notice the indentation at the zookeeper: line compared to the original post).


ConfigurationProperties refresh doesn't remove entries from Maps via Config-Server.

I have a problem with the refreshing of a ConfigurationProperties object. The Properties includes a Map<String, MyObject> object. My problem is that when I remove from the configuration one entry of this map, the map in the Properties object still includes this entry. I guess my issue could be similar like #183.
I prepared a sample project for you. https://github.com/tommyziegler/spring-cloud-prototype.
You can clone the project and follow my sample and see my issue.
Sample
Clone the sample repo
 $ git clone https://github.com/tommyziegler/spring-cloud-prototype.git
 $ cd spring-cloud-prototype

Start the Server with 2 Rel's and see the Rel's in the interface
Following two Rels 'rel1' and 'rel2' are in the config file "config-server/config-server.yml" defined.

config-server/config-server.yml

com:
  tommyziegler:
    server01: http://localhost:8083

    cloud-server:
      links:
        rel1:
          href: ${com.tommyziegler.server01}/rel1
          method: GET
        rel2:
          href: ${com.tommyziegler.server01}/rel2
          method: GET
        # rel3:
        #   href: ${com.tommyziegler.server01}/rel3
        #   method: GET

Start the Server
$ mvn spring-boot:run

Curl the RootRestInterface
$ curl http://localhost:8080/rest
{
  "links" : [ {
    "rel" : "rel1",
    "href" : "http://localhost:8083/rel1",
    "method" : "GET"
  }, {
    "rel" : "rel2",
    "href" : "http://localhost:8083/rel2",
    "method" : "GET"
  } ]
}

Enable the 3rd Rel, refresh the Properties to see the Rel's in the interface
Extend one Rel 'rel3' in the config file "config-server/config-server.yml" defined.

config-server/config-server.yml

com:
  tommyziegler:
    server01: http://localhost:8083

    cloud-server:
      links:
        rel1:
          href: ${com.tommyziegler.server01}/rel1
          method: GET
        rel2:
          href: ${com.tommyziegler.server01}/rel2
          method: GET
        rel3:
          href: ${com.tommyziegler.server01}/rel3
          method: GET

Commit the 3rd Rel into the local Git repo for Spring-Cloud.
$ git commit config-server/config-server.yml -m "Activate 3rd rel"

Refresh the Scope to reload the changed configuration file.
$ curl -X POST http://localhost:8080/actuator-endpoint/refresh

Curl the RootRestInterface
$ curl http://localhost:8080/rest
{
  "links" : [ {
    "rel" : "rel1",
    "href" : "http://localhost:8083/rel1",
    "method" : "GET"
  }, {
    "rel" : "rel2",
    "href" : "http://localhost:8083/rel2",
    "method" : "GET"
  }, {
    "rel" : "rel3",
    "href" : "http://localhost:8083/rel3",
    "method" : "GET"
  } ]
}

Deactivate the 3rd Rel, refresh the Properties to see the Rel's in the interface
Deactivate the 3rd Rel  'rel3' in the config file "config-server/config-server.yml" which we defined in the previous step.

config-server/config-server.yml

com:
  tommyziegler:
    server01: http://localhost:8083

    cloud-server:
      links:
        rel1:
          href: ${com.tommyziegler.server01}/rel1
          method: GET
        rel2:
          href: ${com.tommyziegler.server01}/rel2
          method: GET
        #rel3:
          #href: ${com.tommyziegler.server01}/rel3
          #method: GET

Commit the deactivation of the 3rd Rel into the local Git repo for Spring-Cloud.
$ git commit config-server/config-server.yml -m "Deactivate 3rd rel"

Refresh the Scope to reload the changed configuration file.
$ curl -X POST http://localhost:8080/actuator-endpoint/refresh

Curl the RootRestInterface
$ curl http://localhost:8080/rest
{
  "links" : [ {
    "rel" : "rel1",
    "href" : "http://localhost:8083/rel1",
    "method" : "GET"
  }, {
    "rel" : "rel2",
    "href" : "http://localhost:8083/rel2",
    "method" : "GET"
  }, {
    "rel" : "rel3",
    "href" : "http://localhost:8083/rel3",
    "method" : "GET"
  } ]
}

Doesn't look for me like expected.
Conclusion / Question
After deactivating the 3rd Rel my interface still returns it. Is that like expected!? Do I still need maybe an annotation to build up the whole PropertiesObject? Is that even a Spring-Cloud problem, or more an ConfigurationProperties issue?
I would appreciate if you could give some hint how I could solve this issue, as we would like to take such an service online, where we can specify which Rel's on an RootRest Interface are included via a Git Repository.
Thx a lot
Tommy

Your problem is that your @ConfgurationProperties bean is not in @RefreshScope. You can put it in the right scope by explicitly marking it as a @Component instead of using @EnableConfigurationProperties to define the bean.

I too faced this same issue. Here is the solution that worked for me:

Keep the variable name linksConfig(which is different than the java binding variable i.e. links).
Create just a setter of links(not linksConfig by the above variable name) with body :

public void setLinks(Map<String, HrefAndMethod> links) {     this.linksConfig = links;   }
Let me know if you still face an issue.

I too faced this same issue. Here is the solution that worked for me:
Keep the variable name linksConfig(which is different than the java binding variable i.e. links).
Create just a setter of links(not linksConfig by the above variable name) with body :

public void setLinks(Map<String, HrefAndMethod> links) {      this.linksConfig = links;  }
Let me know if you still face an issue.


Incorrect state notes for the state in data

Describe the bug
Incorrect state notes for the state in data
To Reproduce
Steps to reproduce the behavior:

Go to 'https://api.covid19india.org/data.json'
Click on 'statewise'
Scroll down to 'West Bengal'
The statenotes for West Bengal are shown in Punjab

Expected behavior
The statenotes for West Bengal should be shown in West Bengal
Screenshots

Desktop (please complete the following information):

OS: Mac OS X
Browser Firefox
Version 75

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This is resolved.


libminiupnpc.so.10: cannot open shared object file: No such file or directory

/home/gms1/Desktop/virtauniquecoin-qt'
/home/gms1/Desktop/virtauniquecoin-qt: error while loading shared libraries: libminiupnpc.so.10: cannot open shared object file: No such file or directory
i have confirmed the file is present in my system i am not sure whats going on.
i also tried to compile from source of the qt and it says there is no target to make the qt

apt-cache search libminiupnpc
apt-cache search libssl
:-)

sudo apt-get install libminiupnpc-dev

sudo apt-get install libminiupnpc-dev

That does not work. Still have same error. Using Ubuntu 20.04. Installed using the deb file.
error while loading shared libraries: libminiupnpc.so.10: cannot open shared object file: No such file or directory
Would anyone have any other suggestions? Thanks.

Try to symlink libminiupnpc.so.17 (installedd from Ubuntu 20.04 repos) as libminiupnpc.so.10. In my case it does work.

i guess that wont work as the lib itself is different. you may need to
change some upnp stuff in the core code to reflect changes
On Tue, 27 Apr 2021 at 11:41, xmolin @.***> wrote:

Try to symlink libminiupnpc.so.17 (installedd from Ubuntu 20.04 repos) as
libminiupnpc.so.10. In my case it does work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/virtauniquecoin/virtauniquecoin-master/issues/1#issuecomment-827505240,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2BKF7E2CQVYRH2YA7YAA3TK2IFXANCNFSM4DX47B3A
.

It may work, because new versions of libraries are usually cumulative, i.e. they include functions present in older versions; but it not need to be so. BTW, in my opinion, the best programming practice is not to link the program against a particular version of the library, but to set the requirements about the minimal version number of the library in the dependencies.


Initial revisions of project lifecycle

This is an initial attempt to rework the project lifecycle process.
Note that once this is merged I will work on renaming the repo from TSC to TAC and adjusting all the links.

Looks like the templates are hardcoded into check_projects_syntax.py, Ill have to work on that and file an updated pr.

Yikes, OK the content and therefore process is tightly coupled to the code. This makes updates pretty hard, once I get this merged, perhaps we can chat about decoupling TAC process from the code that generates the website.

I filed https://github.com/chipsalliance/chips-alliance-website/pull/118 to address the path change I submitted in this PR.
I'd like @mgielda to review before I merge these.

@mgielda I know you are super busy, but given the changes in this PR, it would be great to have your eyes on it before we merge.

Hi Ben, as mentioned in the latest TAC meeting, I was travelling to EW and then EOSS / CHIPS open HW event / LatchUp. If you want my review, you may have to ping me using another channel, as I have thousands of emails from GitHub. I was simply not aware of this PR. Overall, I believe the entirety of the TAC should have been made aware that the template is being changed by an email to the mailing list.
The code to build the website was specifically tied to the project templates to avoid discrepancies, so I would definitely oppose decoupling them again.

@mgielda noted, I will send out notifications to the TAC mail list from now on for anything this substantial.
Understood about keeping things coupled.


attempting to extract file (file name) but it did not exist

trying to create a technic modpack, everything is fine and not using solder, but for some reason this error message comes up when i try to use it "Attempting to extract file candycoow-1.0.zip, but it did not exist" and i am modpack author

nvm, someone else helped me out


how can I open navigator when press in notification?

Thank for advance, can I open my navigator when I presed in the notificartion?
Regards

Hi @LuisBonsembiante
You can listen for the click event like this
this._pushNotifications.create(
    'Example One',
    {body: 'Just an example'}
)
    .subscribe(res => {
        if (res.event.type === 'click') {
            // You can do anything else here
        }
    }
)

thanks ready

hey guys,  how is it possible to open the navigator? I see the click handler is there.


Custom components indexing

Initially this was an effort to address some error while trying to use ui-components in Sveltkit, but I think the changes are still an improvement

moved components to either components/mdc or `components/custom' and updated index files
added an index file to components without one for consistency
added components/custom/index.js
refactored index.mjs

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


backend/drm: make page-flip error scarier

The logs don't currently display the importance of a line. It's easy to
read "skipping page-flip" as a debug message instead of an error
message.
Change the error message to make it more explicit.
References: https://github.com/swaywm/wlroots/pull/2147

Much better! :)

Note, the Arch build fails because of:
> clang
clang: error while loading shared libraries: libicuuc.so.67: cannot open shared object file: No such file or directory

Has that been reported to Arch upstream?

Thanks!

Still investigating. On my system I have icu 67.1-1, on builds.sr.ht we have 65.1-3. Both are up-to-date, clang works locally. clang depends on icu through libxml2. Both my local machine and builds.sr.ht have libxml2 2.9.10-2.
tl;dr probably an issue due to a partial update on one of Arch package mirrors.

...so, report your findings upstream?

Yeah, definitely. Still collecting more info for now.

Thanks :)


Reporting API

Describe the problem
#5496 added CSP report-only mode. To use the report-to directive, it's necessary to add Report-To and Reporting-Endpoints headers inside handle (the latter is the newer API, but isn't universally supported yet, so both are necessary), which somewhat defeats the object of letting the framework handle CSP. In fact it's worse, since report-to isn't universally supported; you need to use the report-uri directive as well.
The whole thing is a shocking mess.
Describe the proposed solution
Copied from this comment:

Just spitballing:
export default {
  kit: {
    csp: {...},
    reporting: {
      'main-endpoint': {
        uri: '/reporting/main',
        maxage: 86400
      },
      default: {
        uri: '/reporting/default',
        maxage: 86400
      }
    }
  }
};

SvelteKit could then easily create the headers and report-to/report-uri directives and verify that the directives match the headers (i.e. the endpoints have been defined in reporting, and have a POST handler if they're implemented as SvelteKit endpoints).

Alternatives considered
Leave it as an exercise to readers. I think that would be a shame, since it's so finicky to set up, and we already have nice CSP handling.
Importance
nice to have
Additional Information
No response

@Rich-Harris
I'll put together a test implementation this weekend.

Rich, where are you getting this maxage parameter? How does it affect anything? I don't see any option to add a maxage to Reporting-Endpoints (is it a Report-To option I don't know about?).

Scratch that, I just hadn't found the right documentation yet. Found it.

The problem with using handle, is that report-to and report-uri headers won't be applied to pre-rendered routes, at least not in production certainly.
A solution I'd suggest
Make this build-adapter specific and write the CSPs to each platform's headers file, instead of using meta tags.
Examples

For (Cloudflare and Netlify), detect if _headers exists within the build and append the CSP headers to it, or create _headers if the file doesn't exist yet. This file will exist if the dev is using it to specify custom headers, so don't overwrite it!
For Vercel, update vercel.json's headers property to append CSP headers to any existing headers.
And so on.

Then headers will be set in production even if routes prerendered.

To go further, this workflow creates the opportunity for SvelteKit to allow devs to specify headers within svelte.config.js too, using a pattern like:
headers: {
  "/*": {
    "X-Frame-Options": "DENY"
    "X-Content-Type-Options": "nosniff"
  },
  "/foo": {
      "Another-header": "some-value"
   }
 }

(It seems okay to not worry about type safety of property options.)
I use the following when creating my _headers:
type HeadersObj = {
  [key: string]: {
    [innerKey: string]: string;
  };
};

export function toStr(obj: HeadersObj): string {
  let output = '';

  for (const [key, value] of Object.entries(obj)) {
    output += `${key}\n`;

    for (const [innerKey, innerValue] of Object.entries(value)) {
      output += `  ${innerKey}: ${innerValue}\n`;
    }

    output += '\n';
  }

  return output.replace(/\n\n$/, '\n');
}

This also lets me use an object of standard headers for all projects with strict security, that can be customized within each project.


Use Unix TimeStamp instead

Hi repo owner,
Appreciate your hard work.
I am testing this repo and I notice the payload has timestamp in the format like this "Timestamp":"05:07:53.144".
It seems not very standard and would recommend to use Unix Timestamp in the unit of seconds like this "Timestamp":<PHONE_NUMBER> which converts to GMT | Tue Aug 15 2023 09:24:28 GMT+0000 according to https://www.unixtimestamp.com/.
Cheers,
Paul

Yes, I've named it "Timestamp", but really it's just "Time". I could change this to the Unix Timestamp. I'll think about this...

I try to fix this but confused, seems timestamp is a bit off. No idea where is the problem.
This is what I did, I added few lines to debug in registrationTask.c.
        // remove the current local tick time from this
        // to obtain a rough "boot" time value.
        printf("time %" PRId64 "\n", time);
        printf("seconds %d \n", (uPortGetTickTimeMs() / 1000));
        unixNetworkTime = time - (uPortGetTickTimeMs() / 1000);
        printf("unixNetworkTime %" PRIu32 "\n", unixNetworkTime);

Then use TeraTerm to log local timestamp, here it is:
[2023-08-17 16:16:58.870] 20243: Buttons #1 and #2 are now enabled
[2023-08-17 16:17:56.037] 77419: Connected to Cellular Network: Telstra Mobile (50501)
[2023-08-17 16:17:56.119] time<PHONE_NUMBER> // 16:18:43, not close to my wall clock
[2023-08-17 16:17:56.119] seconds 77
[2023-08-17 16:17:56.119] unixNetworkTime<PHONE_NUMBER> //16:17:26, not close to my wall clock

None of time and unixNetworkTime are close to my wall clock.
Cheers,
Paul

I am trying to fix it myself, and I am poking around.
My network does not restrict NTP. So, which parameter you are holding the ntp synced timestamp?
Then it should be an easy fix.

I'm not sure what there is to fix :)
The code request the time from an NTP Server, and then removes the current uPortGetTickTimeMs() so that the logging timestamp is aligned.
What does the NTP Server return in your case, and what is the uPortGetTickTimeMs() report?
The two values should give you a rough "boot" timestamp in the logging.

No, I was just trying to find out the var in your code which holds unix timestamp to replace the original time in mqtt payload.

The entire published message from each "appTask" is created in that appTask. The MQTTTask() which does the sending doesn't do anything with the payload - it just publishes it.

Understood, all I want to have is "Timestamp":<PHONE_NUMBER>.
I was trying to fix it myself and sending you PR.
Obviously, I was reading the wrong part.

Just to note, UTC Time and GPS Time are not the same. GPS is ahead of UTC by 18 seconds. The timestamp from the NTPService will probably show a difference from the GNSS timestamp you get once you have a GNSS lock.


SunGrid Engine support

This is a re-submission of https://github.com/spotify/luigi/pull/1056, with a rebase, better docs, cleaned up for tox/Python 3, and also to reset some confusing conversation around the PR :)
Overview:

Submits luigi tasks to a SunGrid Engine cluster using qsub
Executes "work" function on pickled task class
Monitors task completion using qstat

Adapted from Alex Wiltschko's (@alexbw) implementation of LSF (https://github.com/dattalab/luigi/tree/lsf_submission).

Another comment is to prepend all private_functions with a _, make it _private_functions, otherwise they'll clog the documentation page on readthedocs.

Sorry for the spurious commits, I was using this branch to sync with my SunGrid Engine cluster for further testing. All tests passing on SGE now.

Looks better now, but can you squash the commits? I think it would be appropriate for these 7 commits to be one single commit.

yup, done

Good job!

Nice, thanks! And thanks again @alexbw for the original framework
On Monday, August 17, 2015, Arash Rouhani<EMAIL_ADDRESS>wrote:

Good job!
—
Reply to this email directly or view it on GitHub
https://github.com/spotify/luigi/pull/1124#issuecomment-131863582.

--
Jacob Feala, PhD
Scientific Investigator II, Bioinformatics
H3 Biomedicine
300 Technology Square
Cambridge, MA 02139
(mobile)<PHONE_NUMBER>
<EMAIL_ADDRESS>--
[This e-mail message may contain privileged, confidential and/or
proprietary information of H3 Biomedicine. If you believe that it has been
sent to you in error, please contact the sender immediately and delete the
message including any attachments, without copying, using, or distributing
any of the information contained therein. This e-mail message should not be
interpreted to include a digital or electronic signature that can be used
to authenticate an agreement, contract or other legal document, nor to
reflect an intention to be bound to any legally-binding agreement or
contract.]

Cool!


standalone generated quantities checks on model / fitted_params too brittle

Summary:
currently, CmdStan takes a shortcut in that it assumes that the parameters blocks in the data fitting model and in the add’l quantities-of-interest generating model are the same:
parameter variables declared in the same order
variables have same sizes, i.e. if the size is passed in as a dimension, the size must be the same
it looks like in your initial report, the parameter blocks matched, but the sizes were different. but then you tried models where the parameters blocks weren’t the same.
the fix requires adding more logic to CmdStan so that instead of just slicing out the block of columns from the fitted_params csv file, it picks and chooses which columns to use.
Description:
Given this simplifying assumption, the checks on the input are straightforward:  https://github.com/stan-dev/cmdstan/blob/97d5cbdea5680033b5f010c1cc2c94119869792f/src/cmdstan/command.hpp#L260-L267
and the data matrix passed in to the services method is simple to grab from the csv file: https://github.com/stan-dev/cmdstan/blob/97d5cbdea5680033b5f010c1cc2c94119869792f/src/cmdstan/command.hpp#L271
changing the input checks is easy.  investigate best way to handle the latter; if not feasible, fully document these restrictions.
Reproducible Steps:
discourse thread:  https://discourse.mc-stan.org/t/generated-quantities-returns-error-mismatch-between-model-and-fitted-parameters-csv-file/17869
Current Output:
standalone generate fails if these conditions aren't met.
Expected Output:
ideally, as long as the parameters required in the generated quantities block are present in the fitted_params csv file, standalone generate quantities will do the right thing.
Additional Information:
Provide any additional information here.
Current Version:
v2.24.0

the only robust and efficient way to code this. trying to re-order and/or subset the fited parameters to match the ordering expected by the standalone generated quantities model would be slow and inefficient. every change made to the parameters block is an opportunity for error.
closing this issue - the current implementation is the only sane one - instead filing an issue on CmdStan documentation to better document various use cases.


Relabel Host Name

Patch as a part of https://github.com/ManageIQ/manageiq/issues/2127

@jrafanie please review

Can you include screenshots? I can't tell where exactly this change is presented.

@dclarizio verified, looks good.
@jrafanie attaching some of the screenshots from affected screens:

Same issue here with storage manager as #2228, storage manager wasn't on the #2127 list so we should probably do that after the backend storage manager has been converted to use hostname and not ipaddress.

does it look odd for the text to wrap to two lines?  Maybe something shorter or widen the area the text covers?

@jzigmund let's not do storage manager in this PR (vmdb/app/views/storage_manager/_form.html.haml)
I have to fix the storage manager and subclasses to stop using ipaddress first.  I'm ok with the text, it looks a little odd to be multiple lines but I can't think of a shorter label for this field,  maybe @dclarizio @h-kataria have suggestions.

@jrafanie updated PR without storage manager view

@jzigmund please rebase and force push to your branch, there was a failing test on master that is in your branch.  It's been fixed so pull in master and it should go :green_heart:

@jzigmund Please rebase, this is based on a commit that had a broken test in product features.

@jrafanie @dclarizio rebased

Thanks, the changes look good to me but I'd prefer to have some tests like #2228 unless there's a better way to do it for checking the html.  The screens appear to have conditional logic for ec2/non-ec2 and operating_system knowledge.


Provide proper documentation for using Tooltip with selector

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
There is currently no documentation on how to use Tooltip with 'selector' using plain JS.
Reduced test cases
This unfortunately doesn't work:
document.querySelector('body').tooltip({
  allowList: myAllowList,
  selector: '[data-bs-toggle="tooltip"]'
});

What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Firefox
What version of Bootstrap are you using?
5.3.3

Does the "enable tooltips" example in the docs not meet your needs?
https://getbootstrap.com/docs/5.3/components/tooltips/#enable-tooltips
const tooltipTriggerList = document.querySelectorAll('[data-bs-toggle="tooltip"]')
const tooltipList = [...tooltipTriggerList].map(tooltipTriggerEl => new bootstrap.Tooltip(tooltipTriggerEl))

If not, it'd be helpful to hear more about exactly what you're trying to achieve.

@nwalters512 No, as this doesn't take care of elements added dynamically to the page later on.

Well that doesn't really document the selector setting, which from its description, should alleviate the need to pull in another dependency.

🙈 never mind; today I learned something new about the Bootstrap API! Yes, it'd be great for this to be formally documented.


Removes iGEMM solvers not typically picked

Resolves issue #229
The following solvers have been removed:
fwd, bwd-data

[X] ConvHipImplicitGemmV4R4Xdlops_1x1
[X] ConvHipImplicitGemmV4R4FwdXdlops
[X] ConvHipImplicitGemmV4_1x1
[X] ConvHipImplicitGemmV4Fwd

bwd-wrw solver

[X] ConvHipImplicitGemmV4WrW
[X] ConvHipImplicitGemmV4R4WrWXdlops

I think now we have some dead code in RunAndMeasureSolutionBase and GetSolutionBase. Maybe some invokers, too.

fwd, bwd-data
ConvHipImplicitGemmV4R4Xdlops_1x1
ConvHipImplicitGemmV4R4FwdXdlops
ConvHipImplicitGemmV4_1x1
ConvHipImplicitGemmV4Fwd

bwd-wrw solver
ConvHipImplicitGemmV4WrW
ConvHipImplicitGemmV4R4WrWXdlops

Can be removed.
@zjing14 @TejashShah please confirm

Looks good.

Looks good.

@atamazov @asroy @zjing14 Please review again I have removed all the indicated solvers.

I think now we have some dead code in RunAndMeasureSolutionBase and GetSolutionBase. Maybe some invokers, too.

@atamazov  I believe I have fixed that, please let me know if I still need to remove something.

Unfortunately, there is some dead code in invokers. And some unused wrappers, I guess.

@JehandadKhan @atamazov I can remove these dead code after #243 is merged

@asroy #243 is merged. Are you going to update this branch/PR directly?
@JehandadKhan Could you please resolve merge conflicts, thanks.

@atamazov , @asroy the kernel wrappers and the remaining invoker logic has been removed, please review.

@daniellowell  CI passes

@JehandadKhan Thank you!


improve existing draft up UX

Right now, the draft up UX looks like this:
Building Docker Image: started
Building Docker Image: ongoing
Building Docker Image: ongoing
Building Docker Image: ongoing
Building Docker Image: ongoing
Building Docker Image: ongoing
Building Docker Image: ongoing
Building Docker Image: ongoing
Building Docker Image: ongoing
Building Docker Image: ongoing
Building Docker Image: ongoing
Building Docker Image: success
Pushing Docker Image: started
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: ongoing
Pushing Docker Image: success
Releasing Application: started
Releasing Application: Release "calling-jaguar" does not exist. Installing it now.
Releasing Application: calling-jaguar DEPLOYED
Releasing Application: notes:
  http://calling-jaguar.k8s.local to access your application

Releasing Application: success

To the user, we don't need to see the status logs every second. It would be cool to see the stages shown in the form of a spinning wheel UX. @fibonacci1729 made a really cool demo which I personally think would be an awesome UI design: https://asciinema.org/a/Kd283QyRkXVEQlOyDzJrcUC0I

@bacongobbler is this in now? WANT. :-)


🚀 Major feature request: Onboarding and signup process for care providers.

Use Case
The app is mainly targeted to be used by care providers to manage one or multiple patients and their questionnaires and EEG recordings. Individual care provider might want to create an account in the app to manage their patients.
Problem
Currently, the app (template) is primarily targeted for individual use.
Solution
Create a respective onboarding and signup process that is targeted specifically for care providers such that they can easily manage one or multiple patients and their respective health records.
Alternatives considered
--
Additional context
No response
Code of Conduct

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

We consider the initial milestone completed as of #8. We might want to extend the work with more access restrictions in the future. This is tracked separately.


made checking for allowed_urls from database more generic

Because of inactivity of the project and no answer of the author our team decide to fork it. Please create a pull request if this is always required.

Since the model isn't very popular, and this is nearly 2 years stale, I'm closing it. Please re-open if you think it's still applicable.


Fix #6985

Summary
Fix #6985
Details and comments
We needed to handle the phase, but I forgot to take care of it. To my surprise, the test was missing, so I added.
The bug is introduced in #6826.

@ikkoham Thanks for the quick fix. I tested locally and it solved the issue. There is now a small output difference, e.g. OperatorMeasurement(Z) vs. OperatorMeasurement(1.0 * Z), but that is cosmetic.
Is there any reason the PauliExpectation is not in the added tests?

Thanks. The difference is from PauliOp and PauliSumOp. In my opinion, they should be merged in the future (i.e. I, X, Y, Z should be PauliSumOp. But now it is not addressed.)
Since this is a unit test, it is better to test it on the root. It will help we find problems in the future. Of course, we can test it on PauliExpectation too. There is no so deep reason why I didn't write both tests (I felt it was redundant, but I can add another test).


[Server] Design Import: Use filename as design name

Current Behavior
During design import (of any supported file type), when no name for the design is provided, "Autogenerated" is used as the design name.
Expected Behavior
Using the filename of as the Design name is more descriptive and helpful.

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I'd like to work on this Issue!

Thank you, @dusdjhyeon 👍


Refactor project to not use C++ coroutines

This is primarily due to a lack of knowledge/experience with C++ coroutinues.
See https://github.com/irods/irods_client_http_api for a reference implementation.
The refactor should look very similar to the HTTP API implementation.

This change has been implemented and merged.  Closing this issue.


No matching JWK when using the Org Authorization Server

This seems like a duplicate of #16, but I'm creating a new issue as I would like to initiate a new discussion.
I'm also using https://support.okta.com/help/s/article/Signature-Validation-Failed-on-Access-Token?language=en_US as a base for my assumptions, as that describes exactly my scenario.

You can confirm that you are using the Org Authorization Server if the issuer of the token (stored in the iss claim) is your Okta domain URL, e.g. https://example.okta.com/

Yes, I can confirm that is what I get as iss value.

Cause
Signature validation fails, because the kid (key identifier) in access token's header does not have a matching kid from the key's endpoint (e.g. https://example.okta.com/oauth2/v1/keys).

That is exactly why I get the No matching JWK error when trying to validate the access token with an AccessTokenVerifier. The verify_access_token method tries to match the kid using the get_jwk method here:
https://github.com/okta/okta-jwt-verifier-python/blob/474fa9d04ea2cea527ccea87a9830080cb868715/okta_jwt_verifier/jwt_verifier.py#L96
and get_jwk fails because no matching key was found:
https://github.com/okta/okta-jwt-verifier-python/blob/474fa9d04ea2cea527ccea87a9830080cb868715/okta_jwt_verifier/jwt_verifier.py#L202-L203
According to the mentioned article above:

This is expected. By design, Okta does not provide keys for access tokens minted by an Okta org.

In #16 you already mentioned you won't support the introspection endpoint as that can be done as a direct http call without extra dependencies. Is the instrospection endpoint the only way to validate tokens from an Okta Org Authorization Server, or can the okta-jwt-verifier Python package somehow be used to validate such tokens too?

Any updates regarding to this issue?

We're also running on the same issue, any news?

Are you intending to issue accessTokens from your org server and not the authorization server?  Need to understand the use case a bit to fully grasp what you're wanting to accomplish but I ran into this same issue and found this post.  In my case, I was sending accessTokens to a lambda authorizer function that was calling back to Okta and experiencing this error.  For me the solution was to simply ensure that my client side access tokens were instead being issued by the okta authorization server instead of the org server and then everything worked out fine

Hi @nsilver7.

Are you intending to issue accessTokens from your org server and not the authorization server?

The tokens are issues by our Okta org authorization server, correct. Using an Okta custom authorization server instead is not an option in our case.


Cache limited by Object weighed

tcache supports limiting the maximum number of entries by element count. That works well if elements are equally big. OTOH it does not work so good if elements have highly differing memory consumption. Examples:

If the value is a List, it depends on the list size
If the value is a complex nested object, the memory consumption is hard to know [1]

it would be good if tcache could support limiting the maximum number of entries by entry weight. That weights can be estimated via Collection.size() or an entry-specific weigher.

[1] The whole object graph needs to be traversed, which may not be possible w/o reflection tricks, it can be big, and the object graph can contain circles. Even worse it contain references to shared objects you are not interested in. Worst case are references to a Thread which is a GC root and thus may reference many objects. So in short: It is not wise to try to traverse the whole object graph.

An experimental implementation can be found in the weigher branch https://github.com/trivago/triava/tree/weigher .

Implementation committed to branch https://github.com/trivago/triava/tree/weigher
Status: All unit tests are working. TCK tests pending.


r5x-Project-Awaken-12.1-DragonRaider188

_ No description provided. _

Sir approve my build when ? 🥲


Fixed #23727 -- Inhibited the post_migrate signals when using serialized...

When using a TransactionTestCase-based class with serialized_rollback set to
True, after creating the database and running its migrations (along with
emitting the post_migration signal), the content of the database is serialized
to _test_serialized_contents.  Without this fix, after the first test case,
_fixture_teardown would flush the tables but then the post_migrate signal would be
emitted and new rows (with new PK's) would be created in the django_content_type
table.  Then, when starting the second or any subsequent test cases in a suite,
_fixture_setup attempts to deserialize the content of _test_serialized_contents,
but these rows are identical to the rows already in the database, except for
their PK's.  This causes an IntegrityError due to a uniqueness constraint in the
django_content_type table.
This change made it so that, in the above scenario, the post_migrate signal is
not emitted after flushing the tables, since it will be repopulated during
_fixture_setup.
The problem is simple to reproduce with the following app test code:
class TestIt(TransactionTestCase):
    serialized_rollback = True

   def test_one(self):
       self.assertTrue(True)

   def test_two(self):
       self.assertTrue(True)

however this proved to be very difficult to write a test case for in the
django unit tests framework because the framework requires that the test case
class's 'available_apps' attribute be non-None, but doing so would cause the
suppression of the post_migrate signal to be emitted anyway.

As far as I understand the code involved in this change, this patch makes sense, though I don't understand your explanation of why it's hard to write a test yet.
Furthermore, I haven't found a place where the _test_serialized_contents is ever being unset. Not sure though if this is required/important.

I think we could we set available_apps = None to suppress the warning from runtests.py saying "Please define available_apps in TransactionTestCase and its subclasses". Then could we do something like connect a post_migrate signal that raises an exception, thereby testing that it isni't called?

Added a test in https://github.com/django/django/pull/5168.


Error when using nvim-orgmode on files without an extension after setting filetype=org

Describe the bug
When using nvim-orgmode, everything works fine with files that have the .org extension. However, if I open a file without an extension (e.g., a cheat sheet file) and manually set the filetype to org using :set filetype=org, the initial folding levels appear correctly, indicating that orgmode recognizes the file.
The problem arises when I try to interact with the org structure, such as attempting to unfold headings. I receive the following error:
Error: Current file is not found or not an org file.

This error points to line 134 in lua/orgmode/files/init.lua, which contains an assert function related to get_current_file().
Steps to reproduce

Open a file without an extension in Neovim (e.g., nvim cheatsheet).
Manually set the filetype to org: :set filetype=org.
Attempt to unfold an org heading or interact with the org structure.

Expected behavior

Orgmode should fully recognize the file as an org file after setting the filetype.
All org functionalities, including folding and unfolding sections, should work without errors.

Emacs functionality
NA
Minimal init.lua

-- Enter your minimal_init.lua here

Screenshots and recordings
No response
OS / Distro
macOS 14.6.1 intel
Neovim version/commit
0.10.0
Additional context
Actual Behavior:

An error is thrown when interacting with the org structure.
The error message states that the current file is not found or not an org file.
Points to line 134 in lua/orgmode/files/init.lua.

Additional Information:

The issue seems to occur because the plugin does not recognize files without an extension as org files, even after setting filetype=org.
Line 134 in init.lua is within the get_current_file() function, which asserts the presence of the current file in the list of org files.

The filename needs to end in .org or .org_archive to be properly loaded as an org file. I'm not sure if I understand your use case here. Why would your cheet sheet not be an org file if you need to treat it as such?

Thanks for the note @kristijanhusak - good question: the scenario is that lots of command line/utilities would use markdown as the default format (such as cheat, obsidian) - which uses the text file in markdown format (though file are not with .md alias);  I am trying to use those utilities with the text file, but I prefer all the great functionalitiies of orgmode, so I would like to load orgmode, even though these text files don't have .org alias
I have tried to find a good markdown plugin for those files, but none is as useful as orgmode ...
Any ideas/suggestions on a solution? Thanks

@ipstone I added a support for this. It should work now.
@chipsenkbeil let me know if this change breaks something in org-roam. Hopefully it shouldn't, but I know you do some stuff for the backlinks buffer.

this is amazing, thanks! @kristijanhusak @a006c93181


🍒 Cherry pick PR #19546 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/19546 to staging 🍒

🚀 Cherry-picked to staging by https://github.com/OSBotify in version: 1.3.17-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/chiragsalian in version: 1.3.17-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 1.3.28-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Fix for ISSUE 98 - add example for usage data

Summary of Changes

added example for usage data

Tests

this is example data, so, no tests, though, I did test this on an ec2 instance and it worked as expected

Documentation

self documenting

LGTM 👍 Great first PR!
@jinhyukchang care to take a look?
Looks like this not only resolves #98, but also #27

@javamonkey79 looks like the CLA check is failing. Have you had the chance to configure your github id/email locally ?

Ah, whoops, I left the author as my work email. I'll fix it.

CLA check fixed

LGTM 👍 Great first PR!
@jinhyukchang care to take a look?
Looks like this not only resolves #98, but also #27

Ah, yes my bad - 98 is a dupe.

@javamonkey79 FYI, there are some flake8 errors for the pr:
flake8 .
./example/models/test_column_usage_model.py:11: [E302] expected 2 blank lines, found 1
./example/models/test_column_usage_model.py:31: [E261] at least two spaces before inline comment
./example/models/test_column_usage_model.py:32: [E261] at least two spaces before inline comment
./example/models/test_column_usage_model.py:32: [E262] inline comment should start with '# '
./example/models/test_column_usage_model.py:96: [W292] no newline at end of file
./example/scripts/sample_data_loader.py:220: [E302] expected 2 blank lines, found 1
./example/scripts/sample_data_loader.py:243: [E502] the backslash is redundant between brackets
./example/scripts/sample_data_loader.py:247: [E501] line too long (125 > 120 characters)
./example/scripts/sample_data_loader.py:250: [E302] expected 2 blank lines, found 1
./example/scripts/sample_data_loader.py:355: [E128] continuation line under-indented for visual indent
make: *** [lint] Error 1

Thanks I'll correct these.

@javamonkey79 it seems there are still 3 more flake8 errors.

I even got the chance to take this for a test drive. The databuilder part certainly works, Frequent users is populated, see proof in the screenshot below. So if the Flake CI error @feng-tao pointed to above is fixed I’d encourage a merge.
But, I think I spotted a problem with Popular tables on the front page. The problem has nothing to do with this PR though. I’m suspecting it’s due to some bug in the metadata service (or possibly the frontend) @jinhyukchang I see you recently did a few changes over there. Can you confirm if Popular tables is working for you or not? (With latest version from yesterday). I can provide specific steps to reproduce over in “metadata” if you want.
One additional thing: I think there’s room for doing some code-refactor to reduce redundancy. (which we can do in a followup PR, lets get this merged!). Basically, my thought is that if the example model class in this PR is put in instead of the existing “proper one” and a new Transformer is introduced to work with the Presto and BigQuery usage Extractors we get better reuse, and clearer code. Or was there a reason for not doing that? Like performance or something?

@jornh , popular table works for us. But the logic on calculating popular table is different between neo4j and atlas proxy. Could you share more on your error for the popular table(or an issue)?

@javamonkey79 @jornh I manually fixed the flake8 error in the pr. If the CI is good, it is good to go. And @jornh , could you file an issue for the code refactor ? I am all for it for removing duplicate code :)

Codecov Report

Merging #100 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #100   +/-   ##
=======================================
  Coverage   82.78%   82.78%
=======================================
  Files          52       52
  Lines        2591     2591
  Branches      271      271
=======================================
  Hits         2145     2145
  Misses        359      359
  Partials       87       87

Continue to review full report at Codecov.

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

Thank you. I'm actually out for vacation the rest of this week, so if you
can hit it fixed and merged that would be great.
Shaun
On Wed, Jul 3, 2019, 9:55 AM Tao Feng<EMAIL_ADDRESS>wrote:

@javamonkey79 https://github.com/javamonkey79 @jornh
https://github.com/jornh I manually fixed the flake8 error in the pr.
If the CI is good, it is good to go. And @jornh https://github.com/jornh
, could you file an issue for the code refactor ? I am all for it for
removing duplicate code :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lyft/amundsendatabuilder/pull/100?email_source=notifications&email_token=AAKWTGIDMHJWN5W2X76PNXLP5TKYZA5CNFSM4H4WYWK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFB4ZA#issuecomment-508173924,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKWTGM46NP34CXXG6LYZWTP5TKYZANCNFSM4H4WYWKQ
.

Also, I think I noticed some duplication in the models as well, as @jornh mentioned. during my first pass, I tried to use existing models but they relied on a column reader object that I was not familiar with. Just FYI.

@javamonkey79 CI is green . Just merge the change. Thanks a lot for the contribution :)

@feng-tao thank you for the quick merge! I’ll have to run a few errands but will try to get back hopefully soonish and re-run with the merged and steps to repro/issue as needed. I’d love to be proven wrong on this 😀 and that it was just something in my environment! @feng-tao could it be that it works with your testing of this with full production amount of data - but something fails with the dummy example data? Did you already try the Quickstart?
If anyone interested has cycles to spare feel free to beat me to it with testing the vanilla QuickStart from scratch to see if it works with Popular tables on the homepage.
I’ll also get back to open the issue on the proposed refactoring.
@javamonkey79 enjoy your time off! Welcome as a fellow committer (like me also in the small - but everything starts from there ;)

Thanks @jornh , we're still evaluating if amundsen will work for us. If it does, there will be more commits from me, and from others at edmunds :)

PR https://github.com/lyft/amundsendatabuilder/pull/103 submitted to fix the Popular Tables issue noted in my previous comment


should panic cannot catch ByteArrays

Which component is your bug related to?
snforge
Foundry Version
0.22
What operating system are you using?
MacOS
What system architecture are you using?
arm
What happened
Failure data:
    Incorrect panic data
    Actual:    [1997209042069643135709344952807065910992472029923670688473712229447419591075, 0,<PHONE_NUMBER>054714428529653950710060964899110390720575627693817702546017, 29] (, , Only the owner can make pizza, )
    Expected:  [2141464762054714428529653950710060964899110390720575627693817702546017] (Only the owner can make pizza)

the should_panic attribute is not able to catch a ByteArray as revert message correctly.
Trace
context:
    #[test]
    #[should_panic(expected: ("Only the owner can change the owner",))]
    fn test_change_owner_should_panic_when_not_owner() {
        let (pizza_factory, pizza_factory_address) = deploy_pizza_factory();
        let not_owner = contract_address_const::<'not_owner'>();
        start_prank(CheatTarget::One(pizza_factory_address), not_owner);
        pizza_factory.change_owner(not_owner);
        stop_prank(CheatTarget::One(pizza_factory_address));
    }

    #[generate_trait]
   pub(crate) impl InternalImpl of InternalTrait {
       fn set_owner(ref self: ContractState, new_owner: ContractAddress) {
           let caller: ContractAddress = get_caller_address();
           assert!(caller == self.get_owner(), "Only owner can change");

           self.owner.write(new_owner);
       }
   }
}

see https://github.com/cairo-book/cairo-book/pull/754 for full context
Is there an existing issue for this?

[ ] I have searched the existing issues and verified no issue exits for this problem.

note to self: don't code late at night. sorry for bothering, there's no issue here


⚠ Processors has degraded performance

In b477319, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 75 ms

Resolved: Processors performance has improved in 003bbe3.


Debian of other ditros icons

Hello, where can i find debian or other icons on the web to put it in the file ?
Does the file accept .img or .ico ?
I've searched in Debian logos but I don't know what to take and put to look like your cute little icon on your preview.
Thanks in advance !

As described, I used an icon font (Font Awesome) and fontello to create my own icon font. You can upload SVG files there. It will generate an icon in a font for you.

Ah yeah didn't read this part, thanks !


[BUG] Master does not compile on Linux

Describe the bug
Cannot build codex from source.
To Reproduce
Steps to reproduce the behavior:

Go to build#linux
Clone repository
Run make udate
Run make
See error: passing argument 1 of ‘br_prng_seeder_system’ from incompatible pointer type [-Wincompatible-pointer-types]

Expected behavior
This section should be removed from the BUG template.
Screenshots
[...]
/home/user/.src/codex-storage/nim-codex/vendor/nim-presto/presto/server.nim(41, 28) Warning: Callback could raise only CancelledError, annotate with {.async: (raises: [CancelledError]).}; new is deprecated [Deprecated]
/home/user/.src/codex-storage/nim-codex/codex.nim(31, 13) Warning: imported and not used: 'sequtils' [UnusedImport]
/home/user/.src/codex-storage/nim-codex/vendor/nim-bearssl/bearssl/rand.nim: In function ‘_ZN4rand3newE8typeDescIN12bearssl_rand15HmacDrbgContextEE’:
/home/user/.src/codex-storage/nim-codex/vendor/nim-bearssl/bearssl/rand.nim:35:34: error: passing argument 1 of ‘br_prng_seeder_system’ from incompatible pointer type [-Wincompatible-pointer-types]
   35 |   let seeder = prngSeederSystem(nil)
      |                                 ~^~~
      |                                  |
      |                                  char **
In file included from /home/user/.src/codex-storage/nim-codex/nimcache/release/codex/@mvendor@snim-bearssl@sbearssl@srand.nim.c:8:
/home/user/.src/codex-storage/nim-codex/vendor/nim-bearssl/bearssl/abi/../csources/inc/bearssl_rand.h:318:51: note: expected ‘const char **’ but argument is of type ‘char **’
  318 | br_prng_seeder br_prng_seeder_system(const char **name);
      |                                      ~~~~~~~~~~~~~^~~~
Error: execution of an external compiler program 'gcc -c  -w -fmax-errors=3 -pthread -I/home/user/.src/codex-storage/nim-codex/vendor/nim-libbacktrace -I/home/user/.src/codex-storage/nim-codex/vendor/nim-libbacktrace/install/usr/include -I/home/user/.src/codex-storage/nim-codex/vendor/nim-bearssl/bearssl/abi/../csources/src/ -I/home/user/.src/codex-storage/nim-codex/vendor/nim-bearssl/bearssl/abi/../csources/inc/ -I/home/user/.src/codex-storage/nim-codex/vendor/nim-bearssl/bearssl/abi/../csources/tools/ -DBR_USE_UNIX_TIME=1 -DBR_USE_URANDOM=1 -DBR_LE_UNALIGNED=1 -DBR_64=1  -DBR_amd64=1 -DBR_INT128=1 -I/home/user/.src/codex-storage/nim-codex/vendor/nim-zlib/zlib/csources -DHAVE_UNISTD_H -DSQLITE_ENABLE_COLUMN_METADATA -DLEVELDB_PLATFORM_POSIX -I/home/user/.src/codex-storage/nim-codex/vendor/nim-leveldbstatic/vendor -I/home/user/.src/codex-storage/nim-codex/vendor/nim-leveldbstatic/vendor/helpers -I/home/user/.src/codex-storage/nim-codex/vendor/nim-leveldbstatic/vendor/helpers/memenv -I/home/user/.src/codex-storage/nim-codex/vendor/nim-leveldbstatic/vendor/port -I/home/user/.src/codex-storage/nim-codex/vendor/nim-leveldbstatic/vendor/include -I/home/user/.src/codex-storage/nim-codex/vendor/nim-leopard/vendor/leopard -fopenmp -march=native -g3 -Og -O3 -fno-strict-aliasing -fno-ident   -I/home/user/.src/codex-storage/nim-codex/vendor/nimbus-build-system/vendor/Nim/lib -I/home/user/.src/codex-storage/nim-codex -o /home/user/.src/codex-storage/nim-codex/nimcache/release/codex/@mvendor@snim-bearssl<EMAIL_ADDRESS>/home/user/.src/codex-storage/nim-codex/nimcache/release/codex/@mvendor@snim-bearssl<EMAIL_ADDRESS>failed with exit code: 1

stack trace: (most recent call last)
nimscript.nim(429, 18)
build.nims(30, 15)       codexTask
build.nims(23, 7)        buildBinary
nimscript.nim(273, 7)    exec
/home/user/.src/codex-storage/nim-codex/vendor/nimbus-build-system/vendor/Nim/lib/system/nimscript.nim(273, 7) Error: unhandled exception: FAILED: nim c --out:build/codex -d:chronicles_runtime_filtering -d:chronicles_log_level=TRACE --verbosity:0 --hints:off -d:release ./codex.nim [OSError]
make: *** [Makefile:74: all] Error 1

/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim: In function ‘_ZN18addcarry_subborrow4subBE3varI2CtI5uInt8EE3varI2CtI6uInt64EE2CtI6uInt64E2CtI6uInt64E2CtI5uInt8E’:
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim:153:38: error: passing argument 4 of ‘_subborrow_u64’ from incompatible pointer type [-Wincompatible-pointer-types]
  153 |     bOut = subborrow_u64(bIn, a, b, diff)
      |                                      ^~~~
      |                                      |
      |                                      NU64 * {aka long unsigned int *}
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/x86gprintrin.h:39,
                 from /usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/x86intrin.h:27,
                 from /home/user/.src/codex-storage/nim-codex/nimcache/release/codex/@mvendor@sconstantine@sconstantine@smath@sarithmetic@slimbs_montgomery.nim.c:9:
/usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/adxintrin.h:59:61: note: expected ‘long long unsigned int *’ but argument is of type ‘NU64 *’ {aka ‘long unsigned int *’}
   59 |                 unsigned long long __Y, unsigned long long *__P)
      |                                         ~~~~~~~~~~~~~~~~~~~~^~~
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim: In function ‘_ZN18addcarry_subborrow4addCE3varI2CtI5uInt8EE3varI2CtI6uInt64EE2CtI6uInt64E2CtI6uInt64E2CtI5uInt8E’:
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim:131:37: error: passing argument 4 of ‘_addcarry_u64’ from incompatible pointer type [-Wincompatible-pointer-types]
  131 |     cOut = addcarry_u64(cIn, a, b, sum)
      |                                     ^~~
      |                                     |
      |                                     NU64 * {aka long unsigned int *}
/usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/adxintrin.h:67:60: note: expected ‘long long unsigned int *’ but argument is of type ‘NU64 *’ {aka ‘long unsigned int *’}
   67 |                unsigned long long __Y, unsigned long long *__P)
      |                                        ~~~~~~~~~~~~~~~~~~~~^~~
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim: In function ‘_ZN18addcarry_subborrow4subBE3varI2CtI5uInt8EE3varI2CtI6uInt64EE2CtI6uInt64E2CtI6uInt64E2CtI5uInt8E’:
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim:153:38: error: passing argument 4 of ‘_subborrow_u64’ from incompatible pointer type [-Wincompatible-pointer-types]
  153 |     bOut = subborrow_u64(bIn, a, b, diff)
      |                                      ^~~~
      |                                      |
      |                                      NU64 * {aka long unsigned int *}
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/x86gprintrin.h:39,
                 from /usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/x86intrin.h:27,
                 from /home/user/.src/codex-storage/nim-codex/nimcache/release/codex/@mvendor@snim-poseidon2@sposeidon2@sio.nim.c:9:
/usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/adxintrin.h:59:61: note: expected ‘long long unsigned int *’ but argument is of type ‘NU64 *’ {aka ‘long unsigned int *’}
   59 |                 unsigned long long __Y, unsigned long long *__P)
      |                                         ~~~~~~~~~~~~~~~~~~~~^~~
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim: In function ‘_ZN18addcarry_subborrow4addCE3varI2CtI5uInt8EE3varI2CtI6uInt64EE2CtI6uInt64E2CtI6uInt64E2CtI5uInt8E’:
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim:131:37: error: passing argument 4 of ‘_addcarry_u64’ from incompatible pointer type [-Wincompatible-pointer-types]
  131 |     cOut = addcarry_u64(cIn, a, b, sum)
      |                                     ^~~
      |                                     |
      |                                     NU64 * {aka long unsigned int *}
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/x86gprintrin.h:39,
                 from /usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/x86intrin.h:27,
                 from /home/user/.src/codex-storage/nim-codex/nimcache/release/codex/@mvendor@snim-poseidon2@sposeidon2@ssponge.nim.c:9:
/usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/adxintrin.h:67:60: note: expected ‘long long unsigned int *’ but argument is of type ‘NU64 *’ {aka ‘long unsigned int *’}
   67 |                unsigned long long __Y, unsigned long long *__P)
      |                                        ~~~~~~~~~~~~~~~~~~~~^~~
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim: In function ‘_ZN18addcarry_subborrow4subBE3varI2CtI5uInt8EE3varI2CtI6uInt64EE2CtI6uInt64E2CtI6uInt64E2CtI5uInt8E’:
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim:153:38: error: passing argument 4 of ‘_subborrow_u64’ from incompatible pointer type [-Wincompatible-pointer-types]
  153 |     bOut = subborrow_u64(bIn, a, b, diff)
      |                                      ^~~~
      |                                      |
      |                                      NU64 * {aka long unsigned int *}
/usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/adxintrin.h:59:61: note: expected ‘long long unsigned int *’ but argument is of type ‘NU64 *’ {aka ‘long unsigned int *’}
   59 |                 unsigned long long __Y, unsigned long long *__P)
      |                                         ~~~~~~~~~~~~~~~~~~~~^~~
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim: In function ‘_ZN18addcarry_subborrow4addCE3varI2CtI5uInt8EE3varI2CtI6uInt64EE2CtI6uInt64E2CtI6uInt64E2CtI5uInt8E’:
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim:131:37: error: passing argument 4 of ‘_addcarry_u64’ from incompatible pointer type [-Wincompatible-pointer-types]
  131 |     cOut = addcarry_u64(cIn, a, b, sum)
      |                                     ^~~
      |                                     |
      |                                     NU64 * {aka long unsigned int *}
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/x86gprintrin.h:39,
                 from /usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/x86intrin.h:27,
                 from /home/user/.src/codex-storage/nim-codex/nimcache/release/codex/@mvendor@snim-poseidon2@sposeidon2@sroundfun.nim.c:9:
/usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/adxintrin.h:67:60: note: expected ‘long long unsigned int *’ but argument is of type ‘NU64 *’ {aka ‘long unsigned int *’}
   67 |                unsigned long long __Y, unsigned long long *__P)
      |                                        ~~~~~~~~~~~~~~~~~~~~^~~
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim: In function ‘_ZN18addcarry_subborrow4subBE3varI2CtI5uInt8EE3varI2CtI6uInt64EE2CtI6uInt64E2CtI6uInt64E2CtI5uInt8E’:
/home/user/.src/codex-storage/nim-codex/vendor/constantine/constantine/platforms/intrinsics/addcarry_subborrow.nim:153:38: error: passing argument 4 of ‘_subborrow_u64’ from incompatible pointer type [-Wincompatible-pointer-types]
  153 |     bOut = subborrow_u64(bIn, a, b, diff)
      |                                      ^~~~
      |                                      |
      |                                      NU64 * {aka long unsigned int *}
/usr/lib/gcc/x86_64-pc-linux-gnu/14.2.1/include/adxintrin.h:59:61: note: expected ‘long long unsigned int *’ but argument is of type ‘NU64 *’ {aka ‘long unsigned int *’}
   59 |                 unsigned long long __Y, unsigned long long *__P)
      |                                         ~~~~~~~~~~~~~~~~~~~~^~~

Environment:

OS: ArchLinux
Version: Linux intan 6.11.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 10 Oct 2024 20:11:06 +0000 x86_64 GNU/Linux
Tag/Commit: 436baef20afdbba51adc083e324b9cead0c493f1
Arch: x86_64

Additional context
Add any other context about the problem here.

Can you please check your gcc version
gcc --version

It is a known issue and we have a note about it in the docs as well - Known issues.
So, work is still in progress.

Got it. Duplicate of #875


Add (unsafe) ways to temporarily mutate Shared variant collections without unique references

Turns out that sometimes people do want to modify Shared variant collections. @halzy has encountered problems trying to mutate one on stream, and tried to resolve it using assume_unique in an unintended way. As such, it might be better to just add unsafe versions of insert, erase, and other similar methods to Shared collections.
It should be called out in the documentation that safe versions exist for Unique collections, and that modifying a Shared collection is not recommended.

I'm not certain my case is the best driver here. ;-) I'd say my attempt to mutate Shared was due to a lack of understanding the new patterns. I'd expect that the better documentation (book) would have kept me on the good path.


[#29772][prism] Handle EventTime Timers.

Updates Prism to support EventTime Timers.
Fixes a bug in Go SDK timer handling unset watermark holds would have the wrong default hold. They should default to the firing time.
Timer implementation tracked in #29772.
Largely handles event time timers by treating them as data elements in the processing, with the goal of minimizing unique handling of timers vs data.
Timers with the same event time must always sort after data elements with the same event time, so they can be reasonably be consolidated when firing.
Since only a single timer can be set for a [window, user key, timerfamily, tag] tuple we track the last set EventTime + Hold. This avoids scanning the element queue for a key every time a timer is written at the expense that more timers are retained in memory (a "spend RAM to save CPU" trade off). This requires managing the remaining "pending elements" properly as well, as a timer may be written, but it may not affect size of the pending queue.
WatermarkHolds are tracked on a per Hold basis. Each stage maintains a heap of their holds, and a map of how many timers are using that hold. When the count goes to 0, we remove the hold from the map, and the heap. This approach avoids tracking holds on a per timer basis, which would mean a much larger hold heap.
Aside: A general improvement that could be made to the Element Manager would be to "intern" the user key bytes, tags, and various other strings when persisting the data. This would avoid retaining several copies of each set of bytes in memory between stages (this is a "spend CPU to save RAM" trade off). There's also likely opportunity to clean up "leaked" tails of large byte buffers when a key prefix is being held (a similar CPU for RAM tradeoff).

Deferred to a later PR, related to EventTime timers:

Handling Cleared timers correctly.

Fired timers are cleared, but a user clearing a timer (eg. because a batch is determined complete, so a GC timer isn't needed) isn't tested yet. It's expected that such a timer will simply fire.

Handling OnWindowExpiration, because it's not implemented in the Go SDK yet, so it's hard to test.

Both are likely to be handled in the process of cleaning up prism for the Java and Python Validates Runner tests.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @damondouglas
And in the meantime, I'll validate the RC.

Did you mean to assign this to me?

@christ Sorry about that. Something went haywire with keyboard shortcuts while I was replying to a comment. It must have done the assignement then.  TIL there are GH keyboard shortcuts for assignee-asigning....

No worries, just didn't want it lost in the ether.

Thanks for the review!


Quarantined mails due to Spam cannot be retrieved via Office 365 Management API

Hi,
We have followed https://docs.microsoft.com/en-us/office/office-365-management-api/office-365-management-activity-api-reference to retrieve content from Office 365 Management API and we are able to retrieve information from all mails quarantined due to Malware or Phishing, but those due to Spam (Policy Type - Hosted content filter policy) is not possible to retrieve them.
Is there any other ContentType that should be used or some configuration that is required to be able to retrieve them?
Thanks!

@markjjo for visibility

@marcsantamaria-aiq Please contact/open a ticket with Microsoft Support about this issue/question.


Synthesis failed for nodejs-projectify

Hello! Autosynth couldn't regenerate nodejs-projectify. :broken_heart:
Here's the output from running synth.py:
ool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-01-07 00:47:35,279 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/nodejs-projectify/synth.py.
On branch autosynth-9
nothing to commit, working tree clean
2021-01-07 00:47:35,414 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
.eslintignore
.eslintrc.json
.gitattributes
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/release-please.yml
.github/workflows/ci.yaml
.kokoro/.gitattributes
.kokoro/common.cfg
.kokoro/continuous/node10/common.cfg
.kokoro/continuous/node10/docs.cfg
.kokoro/continuous/node10/test.cfg
.kokoro/continuous/node12/common.cfg
.kokoro/continuous/node12/lint.cfg
.kokoro/continuous/node12/samples-test.cfg
.kokoro/continuous/node12/system-test.cfg
.kokoro/continuous/node12/test.cfg
.kokoro/docs.sh
.kokoro/lint.sh
.kokoro/populate-secrets.sh
.kokoro/presubmit/node10/common.cfg
.kokoro/presubmit/node12/common.cfg
.kokoro/presubmit/node12/samples-test.cfg
.kokoro/presubmit/node12/system-test.cfg
.kokoro/presubmit/node12/test.cfg
.kokoro/publish.sh
.kokoro/release/docs-devsite.cfg
.kokoro/release/docs-devsite.sh
.kokoro/release/docs.cfg
.kokoro/release/docs.sh
.kokoro/release/publish.cfg
.kokoro/samples-test.sh
.kokoro/system-test.sh
.kokoro/test.bat
.kokoro/test.sh
.kokoro/trampoline.sh
.kokoro/trampoline_v2.sh
.mocharc.js
.nycrc
.prettierignore
.prettierrc.js
.trampolinerc
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
README.md
api-extractor.json
renovate.json
samples/README.md
2021-01-07 00:47:35,546 synthtool [DEBUG] > Installing dependencies...
DEBUG:synthtool:Installing dependencies...
npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated<EMAIL_ADDRESS>NOTICE: ts-simple-ast has been renamed to ts-morph and version reset to 1.0.0. Switch at your leisure...
npm WARN deprecated<EMAIL_ADDRESS>"Please update to latest v2.3 or v2.2"
npm WARN deprecated<EMAIL_ADDRESS>Use cheerio-select instead
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>The package has been renamed to `open`
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated

><EMAIL_ADDRESS>postinstall /home/kbuilder/.cache/synthtool/nodejs-projectify/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /home/kbuilder/.cache/synthtool/nodejs-projectify/node_modules/@compodoc/compodoc
> opencollective-postinstall || exit 0

Thank you for using @compodoc/compodoc!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/compodoc/donate

><EMAIL_ADDRESS>prepare /home/kbuilder/.cache/synthtool/nodejs-projectify
> npm run compile

><EMAIL_ADDRESS>precompile /home/kbuilder/.cache/synthtool/nodejs-projectify
> gts clean

/home/kbuilder/.cache/synthtool/nodejs-projectify/node_modules/meow/index.js:61
		throw new Error(`Flag keys may not contain '-': ${invalidFlags.join(', ')}`);
		^

Error: Flag keys may not contain '-': dry-run
    at validateOptions (/home/kbuilder/.cache/synthtool/nodejs-projectify/node_modules/meow/index.js:61:9)
    at meow (/home/kbuilder/.cache/synthtool/nodejs-projectify/node_modules/meow/index.js:136:2)
    at Object.<anonymous> (/home/kbuilder/.cache/synthtool/nodejs-projectify/node_modules/gts/build/src/cli.js:30:13)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>precompile: `gts clean`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>precompile script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/kbuilder/.npm/_logs/2021-01-07T08_47_59_190Z-debug.log
2021-01-07 00:47:59,225 synthtool [ERROR] > Failed executing npm install:

None
ERROR:synthtool:Failed executing npm install:

None
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/nodejs-projectify/synth.py", line 12, in <module>
    node.install()
  File "/tmpfs/src/github/synthtool/synthtool/languages/node.py", line 167, in install
    shell.run(["npm", "install"], hide_output=hide_output)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['npm', 'install']' returned non-zero exit status 1.
2021-01-07 00:47:59,273 autosynth [ERROR] > Synthesis failed
2021-01-07 00:47:59,273 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 81d8032 docs: add instructions for authenticating for system tests (#234)
2021-01-07 00:47:59,281 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2021-01-07 00:47:59,286 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Removing node_modules/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 65, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:

Autosynth passed, closing! :green_heart:


feat: ceph chart improvements to target real disks

Kubernetes Version (output of kubectl version): N/A
Helm Client and Tiller Versions (output of helm version): N/A
Development or Deployment Environment?: N/A
Release Tag or Master: N/A
Expected Behavior: N/A
What Actually Happened: N/A
How to Reproduce the Issue (as minimally as possible): N/A
Any Additional Comments:
Unfortunately some work was dropped for ceph. I think input provided in the previous issue is relatively clear, but this work needs to be put into practice in our charts.

I could take a look at this one.  After working with Cinder a bit, I think it'd be helpful for me to look into some of the Ceph bits.  What are your thoughts, @v1k0d3n?

unless you don't have anything else to do @wilkers-steve, I'm trying to leave some starter items for community members to get their feet wet.

Works for me.  The LVM work we discussed yesterday has kept me busy

@larryrensing i'm assuming you're taking this?

I was going to look at this too as a 'cut your teeth' item - but happy to take something else too.


[Python][Client]  Unify the graph level load_from and save to API

This is a prototype implementation of the design of load_from and write_to Python API
related issue: #2836
Use examples:
import graphscope.Graph as Graph
# load from graphar file
g = Graph.load_from("graphar+file:///tmp/ldbc/ldbc_sample.graph.yml")
# load from oss file storage
g = Graph.load_from("graphar+oss://bucket/ldbc/ldbc_sample.graph.yml")

import graphscope
g = graphscope.load_ldbc()

# write to graphar format
g.save_to("/tmp/ldbc/", format="graphar")
# write to oss output
g.save_to("oss://bucket/ldbc", format="graphar")
# write to graphar format with configuration
g.save_to("/tmp/ldbc/", format="graphar", graphar_graph_name="ldbc",
      graphar_vertex_block_size=1024, graphar_edge_block_size=2048,
      graphar_file_format="orc")

Codecov Report

Merging #2919 (07a3f51) into main (34b3650) will decrease coverage by 8.19%.
The diff coverage is 37.50%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2919      +/-   ##
==========================================
- Coverage   73.96%   65.78%   -8.19%
==========================================
  Files          99       99
  Lines       10672    10719      +47
==========================================
- Hits         7894     7051     -843
- Misses       2778     3668     +890

Impacted Files
Coverage Δ

python/graphscope/__init__.py
82.35% <ø> (-0.51%)
:arrow_down:

python/graphscope/client/session.py
66.77% <ø> (-10.70%)
:arrow_down:

python/graphscope/framework/graph_builder.py
88.88% <ø> (+1.38%)
:arrow_up:

python/graphscope/framework/utils.py
59.57% <5.00%> (-7.99%)
:arrow_down:

python/graphscope/framework/graph.py
83.36% <75.75%> (-0.94%)
:arrow_down:

python/graphscope/framework/dag_utils.py
64.26% <100.00%> (-3.45%)
:arrow_down:

python/graphscope/tests/unittest/test_gar.py
100.00% <100.00%> (ø)

... and 16 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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

this PR is outdated, create a new pull request #3610


Vue website grid component JSFiddle embedding broken

The grid component example on the Vue website, which is embedded via JSFiddle, doesn't work anymore (404):
https://vuejs.org/v2/examples/grid-component.html
GitHub link to this site
However, the "real" JSFiddle link still works:  https://jsfiddle.net/yyx990803/xkkbfL3L   which is without "/embedded/result,html,js,css".

Actually, the example still exists and live, what's your browser?


Calculate Account Details in the Token

Calculate the following information (with getter functions):

Total Tax Paid
Total COMRADE sent
Account Max Balance

Won't be implementing total balances for v.1


error: ‘AA_DontCheckOpenGLContextThreadAffinity’ is not a member of ‘Qt’

hello @puzzlepaint
Thanks for sharing the code. I met the following error when I tried to compile your code:
surfelmeshing/libvis/src/libvis/opengl_context_qt.cc: In member function ‘virtual void vis::OpenGLContextQt::MakeCurrent()’:
/home/fb/SLAM/surfelmeshing/libvis/src/libvis/opengl_context_qt.cc:126:46: error: ‘AA_DontCheckOpenGLContextThreadAffinity’ is not a member of ‘Qt’
   QCoreApplication::instance()->setAttribute(Qt::AA_DontCheckOpenGLContextThreadAffinity);
                                              ^
CMakeFiles/libvis.dir/build.make:270: recipe for target 'CMakeFiles/libvis.dir/libvis/src/libvis/opengl_context_qt.cc.o' failed
make[3]: *** [CMakeFiles/libvis.dir/libvis/src/libvis/opengl_context_qt.cc.o] Error 1

I have tried with QT5.5.1and Qt5.9.1 and have the above errors.Maybe I have installed the QT with errors？
Any idea of why there's such a problem? Thanks in advance!

According to the Qt documentation, Qt::AA_DontCheckOpenGLContextThreadAffinity was added in Qt 5.8. Thus, it seems like the attempt to use Qt 5.9.1 probably didn't work correctly. Probably it still used the Qt 5.5.1 headers for some reason. Correctly using Qt 5.9.1 should solve the issue.

I change to Qt5.10.1, and solved the error

modify the opengl_context_qt.cc file
change the code
QCoreApplication::instance()->setAttribute(Qt::AA_DontCheckOpenGLContextThreadAffinity);
to
#if QT_VERSION < QT_VERSION_CHECK(5, 7, 0)
// todo
#else
QCoreApplication::instance()->setAttribute(Qt::AA_DontCheckOpenGLContextThreadAffinity);
#endif


import runtime from 'serviceworker-webpack-plugin/lib/runtime'; always throws error

import runtime from 'serviceworker-webpack-plugin/lib/runtime'; always throws below error
Error: serviceworker-webpack-plugin: It seems that your are importing
"serviceworker-webpack-plugin/lib/runtime" without using the plugin.
I installed 'serviceworker-webpack-plugin' by
npm install serviceworker-webpack-plugin@0 for 'webpack 1'
Versions.
browser: chrome
browser version: Version 67.0.3396.99
operating system: IOS
webpack version: 1.14.0

Repro steps.
1). var ServiceWorkerWebpackPlugin = require('serviceworker-webpack-plugin'); // require plugin into the webpack config file
2). added following to webpack plugins
 new ServiceWorkerWebpackPlugin({
        entry: path.join(__dirname, '../src/ServiceWorker/service-worker.js'),
        fileName: 'service-worker.js',
        excludes: ['**/.*', '**/*.map', '*.html']
      })

3). import runtime from 'serviceworker-webpack-plugin/lib/runtime'; in the main.js file always throws error.
runtime.js file always throws error as we can see into the source code.
when I change
import runtime from 'serviceworker-webpack-plugin/lib/runtime';
to
import runtime from 'serviceworker-webpack-plugin/lib/runtimeTemplate';
it builds, but then I'm getting another error on the browser.
_client.js?cf27:63 ReferenceError: serviceWorkerOption is not defined
    at Object.register (eval at <anonymous> (main.js?48625b094889c52616ad:3544), <anonymous>:13:30)_

we are not getting serviceWorkerOption into global. I'm not sure how serviceWorkerOption is being injected into the global.

This was the server-side rendering issue.  import runtime from 'serviceworker-webpack-plugin/lib/runtime'; was calling on the server side.


feat(entities-shared): consumers are not showing up in consumer group [KHCP-10622]

Summary

Fix - Adding support for useFetcher when a response from BE arrives of the type:

data: {
    data: [
        {
            id: '1',
            ...
        }
    ]
}

Resources

Creating a package docs

To address this issue, please modify the <ConsumerList> instance in the host app by setting paginatedEndpoint to true.


Convert pages to Jekyll layouts

Not urgent, but will help with the content maintenance later on.

Done


v0.13.0

Codecov Report

Merging #58 into master will decrease coverage by 0.55%.
The diff coverage is 96.66%.

@@            Coverage Diff             @@
##           master      #58      +/-   ##
==========================================
- Coverage     100%   99.44%   -0.56%
==========================================
  Files           7       11       +4
  Lines         363      359       -4
  Branches      112      113       +1
==========================================
- Hits          363      357       -6
- Partials        0        2       +2

Impacted Files
Coverage Δ

packages/molecule-lit/src/molecule-lit.ts
100% <ø> (ø)
:arrow_up:

...cule-functional-lit/src/molecule-functional-lit.ts
100% <ø> (ø)
:arrow_up:

...ges/molecule-functional/src/molecule-functional.ts
100% <ø> (ø)
:arrow_up:

packages/molecule-jsx/src/molecule-jsx.ts
100% <ø> (ø)
:arrow_up:

packages/molecule/src/lib/camel-to-kebab-case.ts
100% <ø> (ø)

packages/molecule/src/lib/constants.ts
100% <100%> (ø)

packages/molecule/src/lib/get-attr-for-prop.ts
100% <100%> (ø)

packages/molecule-jsx/src/lib/dom/index.ts
100% <100%> (ø)
:arrow_up:

packages/molecule/src/molecule.ts
99.1% <100%> (-0.9%)
:arrow_down:

packages/molecule/src/lib/observe-property.ts
94.73% <94.73%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


segger-jlink: init at 7.20

Motivation for this change
The SEGGER JLink Software package was missing from nixpkgs.
I was able to test the 64- and 32-bit version on my local machine. I tried to test both ARM version with binfmt, with mixed results. I was able to build the aarch64 version, but it seems autoPatchelf does not detect any of the dynamic libraries (even though just running patchelf --print-needed <bin> displays them correctly. The armv7lrequires to build 400+ dependencies not in the binary cache, which is slow under binfmt, so I did not have a chance to check that yet.
Things done

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

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

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

#80990 suggests this could be made available for x86 and ARM, 32 and 64 bit

#80990 suggests this could be made available for x86 and ARM, 32 and 64 bit

Indeed, and the way it makes udev available is much nicer as well. I will see how we can combine our approaches.

@reardencode Thank you for your work in #80990, I took over a lot of your changes into my derivation and cited you as co-author. Would love to hear what you think about this.
@prusnak @liff @mtetreault I saw you looked in this in #80990, any feedback and testing would be greatly appreciated.

Hi, I was writing a flake for this at some point, with an intent to later submit it to nixpkgs. I pushed what I have to a repo.
You could consider adding the desktop items, which I “stole” from the Windows/macOS packages. Unfortunately the Linux packages do not come with icon(s) for the items. There’s one in Windows and macOS package but it’s generic and low resolution.
Another issue is that you may want to prefer the bundled Qt4 libraries to the ones from nixpkgs. IIRC the UI looks a bit crappier, especially on HiDPI, when using qt4 from nixpkgs. Maybe Segger has modified their Qt or something 🤷🏻. At least check out if it makes any difference on your system, and on 7.20.

This code works for me and with the above mentioned minor patch I am able to use it with nrfjprog (see https://github.com/maxhbr/myconfig/blob/f5910d557a22073b59897733e140d76b1a63ee66/flakes/zephyrproject/nRF-Command-Line-Tools/default.nix)  to flash the nrf5340-dk with Zephyr.

Added commands to symlink libraries as well as updated version and hashes to latest release.

I’m getting a syntax error when building:
error: syntax error, unexpected ASSERT

       at /tmp/nixpkgs/pkgs/development/tools/misc/segger-jlink/default.nix:39:3:

           38|
           39|   assert !acceptLicense -> throw ''
             |   ^
           40|     Use of the "SEGGER JLink Software and Documentation pack" requires the

Anyway, isn’t requireFile the usual way to handle this sort of license thing?

Superseded by and incorporated into by #178603 .


People Page components Review

These should replace the previous, People Page and PeoplePage2

Improved components for issues 1332 and 1333


Dependency Management

Lingua-Franca Dependencies
graph TD;
    S1[[Lockfile Exists?]];
    S2[[Read Lockfile]];

    S3[[Iteratively Pull Dependencies]];
    S4[[Read Version Requirements]];
    S5[[Read Package Version]];
    S6[[Read Package Dependencies]];
    S7[[Select Packages based on Version Requirements]];
    S8[[Create Lockfile]];
    S9[[create lfc_include directory from Lockfile]];
    S10[[Call Backend -Start LFC]];
    S11[[Inherit and merge Target Properties]]

    S1-->S2;
    S1-->S3;
    S3-->S4;
    S4-->S5;
    S5-->S6;
    S6-->S3;
    S3-->S7;
    S7-->S8;
    S8-->S9;
    S2-->S9;
    S9-->S10;
    S10-->S11;

Explanation
File structure
./Lingo.toml
./src
./target
    ./libraries
        ./0ba957161fb429f610a42e881678a5bef797b138 (hash calculated from package sources)
            ./Lingo.toml
            ./src
        ./1618817019dab848783e80a2779eee1a4f57516
            ./Lingo.toml
            ./src
    ./lfc_include (we tell lfc to include files from this directory)
        ./lf-websockets
            ./Lingo.toml
            ./src
        ./requests
            ./Lingo.toml
            ./src

The version resolvement process
Requirements: [">=1.2", "<=1.5", "<=2.0", ">=1.3.2"]
Sources: [("1.1.0", "github..."), ("1.6.90", "tarball...."),("1.4.6", "path...."), ("1.4.9", "github...")]

select a "good" package that fullfills all the requirements.
this selection is documented in the Lingo.lock

Open Discussion Topics

[ ] Systemwide packages? under e.g. ~/.local/lingo/packages ?

potential nasty problems
how to tell that a package should be installed system wide?

Unsolved Problems and Future Work

[ ] Getting manifest files without needing to pull the whole source.

@oowekyala would you mind having a look at this PR? - Thank You


Enable safeptr in AD run

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3183

Relevant Lines:
3542

💛  - Coveralls