Use gulp-babel instead of gulp-es6-transpiler

This P-R contains 2 changes:

Install gulp-babel babel-preset-es2015 and use then in gulpfile.js
Uninstall gulp-es6-transpiler

:+1:

+1 for that too, gulp-es6-transpiler is no longer maintained (and it's deprecated)


Extend Houdini's help: Add AYON examples

Is there an existing issue for this?

[X] I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?
It'd be great to include examples to Houdini examples
It'd be beneficial for USD workflow examples and upcoming low level publish support.

How would you imagine the implementation of the feature?
You can create custom examples: https://www.sidefx.com/docs/houdini/help/createexamples.html
Are there any labels you wish to add?

[X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:
No response
Additional context:
No response

We need to define specific examples, create issues for them and link them here.


Add license, improve README

Eh, would you like me to remove the CMakeLists.txt file?
I forgot to remove it. (CLion has mandatory support currently)

cool, thanks.

no problem :)


How can find distance between pdf and sdf files through picking ?

I want to upload pdb and sdf files respectively and find the distance between them by selecting the atoms of each other.
However, it seems that only the atoms in each file can be selected, and the interatomic distance between different files (sdf, pdb) cannot be measured.
How to solve this problem?
// pdb loadFile
    stageRef.current
      .loadFile(fileData, { name: "receptor.pdb", ext: "pdb" })
      .then(function (o) {
        o.addRepresentation("cartoon");
        o.autoView();
      });

//sdf load FIle
      stageRef.current.loadFile(files[0]).then(function (o) {
        o.addRepresentation("ball+stick");
      });

There's no simple general workaround for this unfortunately. The problem is distance representations only apply to a single structure (file). However, you can concatenate two structures into a new one and display that, the test/concat example should get you started:
https://github.com/nglviewer/ngl/blob/master/examples/scripts/test/concat.js

@fredludlow  Thanks. I tried to use that example in my project and it works.
I wanna show to ball+stick only ligand(sdf file). so I used sele option.
finally, I can measure distance between sdf and pdb files through picking two point.
It is my code.
      (stageRef.current as any).loadFile(files[0]).then(function (o: any) {
        if (NGL)
          var cs = NGL.concatStructures(
            "concat",
            o.structure.getView(new NGL.Selection("")),
            (stageRef.current as any as any).redPandas.structure.getView(
              new NGL.Selection(""),
            ),
          );
        var comp = (stageRef.current as any).addComponentFromObject(cs);
        comp.addRepresentation("ball+stick", { sele: "ligand" });
        comp.addRepresentation("cartoon");
        o.autoView();
      });

@seongsangcho-hits - I received an email notification of your reply but I can't see it on this page (some caching thing at github, or maybe it got deleted?) Anyway, glad it worked!


About the tag autocomplete extension

I modified my code with reference to this problem to make the extension works.
https://github.com/TheLastBen/fast-stable-diffusion/issues/409

It works correctly until today.
The change of the cell cause start up problem while nothing wrong was reported.

After change back the cell, it return to normal.
Seems we have to find a new way to make this extension work.

keep the change and use the gradio server to see if it works

No, it doesn't.
And I just realized that my operation was the opposite of what was in your commit.
I change stable-diffusion to stable-diffusion-webui

Did I misunderstand something？

did you figure out why it suddenly won't work ?

No, I try a lot include the API option and finally find the problem is caused by change stable-diffusion to stable-diffusion-webui

I do a clean run, and it works. Thanks for help!


CommonRegexes.Date: accept incomplete dates

CK3 has multiple instances of incomplete dates in character history. Some log lines from IRToCK3:
2024-05-01 15:03:12 [DEBUG] Ignored history keywords: 640.1.
2024-05-01 15:03:12 [DEBUG] Ignored history keywords: 889
2024-05-01 15:03:12 [DEBUG] Ignored history keywords: 1019.1.
2024-05-01 15:03:12 [DEBUG] Ignored history keywords: 1058.1.
2024-05-01 15:03:12 [DEBUG] Ignored history keywords: 1065.1.
2024-05-01 15:03:13 [DEBUG] Ignored history keywords: 1077.1
2024-05-01 15:03:13 [DEBUG] Ignored history keywords: 1101.1
2024-05-01 15:03:14 [DEBUG] Ignored history keywords: 976.1
2024-05-01 15:03:14 [DEBUG] Ignored history keywords: 880.1.1.
2024-05-01 15:03:14 [DEBUG] Ignored history keywords: 1049
2024-05-01 15:03:15 [DEBUG] Ignored history keywords: 939.1.
2024-05-01 15:03:15 [DEBUG] Ignored history keywords: 841.1.1.
2024-05-01 15:03:15 [DEBUG] Ignored history keywords: 1046
2024-05-01 15:03:15 [DEBUG] Ignored history keywords: 879.1.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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 92.928%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3389

Relevant Lines:
3609

💛  - Coveralls

Reworked the Date constructor to accept incomplete dates. Ready for review again.


proposal: encoding/yaml: Add YAML support in the standard library

TL;DR
Seems like since JSON and XML are supported in the standard library, it's time to move YAML support into the standard library as well.
Why now?
Following a discussion in the #cup-o-go channel in the Gopher slack, we figured that:

YAML has a de-facto standard, so it CAN be added - it's not ambiguous
YAML is massively used specifically in the Go space. The best example is K8s, Helm, etc. that's totally dominated by YAML. From grank.io:

Since JSON, XML, and CSV are in the standard library, YAML can be part of the standard library as well
Seems like it would be useful for other major projects in the Go space, such as Fyne on embedded chipsets

History
Seems like this proposal was suggested 13 years ago. YAML went a long way since then.
What do y'all think? Would any more data or research help?

which version of yaml? there's 1.2, which removes foot guns, but isn't widely implemented
what features should it support? k8s has its own fork for making structured edits, it's that something we will need to support too?

Counterproposal: Block gopkg.in/yaml in the Go module proxy to stop the virus from spreading.
YAML is a terrible format which is never appropriate to use. There is literally always a better choice. Yes, it's popular in the devops and Go world, but that's no reason to encourage it.

Less inflammatory statement: YAML has a large and complex spec. Putting it into the Go standard library means choosing a subset of the spec to implement. If we can’t implement a full YAML parser (and we really cannot), it makes more sense to leave it to third parties to pick and choose which subsets of YAML they want.

Also note https://go.dev/doc/faq#x_in_std.

@carlmjohnson : I am not sure YAML is that complicated in comparison to XML. So the argument of being something is large and complex, we should not do it, is not really strong. And nothing wrong with just implement a subset of the specs first as well. XML is not come all at one, isnt it?
For example :
https://github.com/golang/go/issues/11496 (7 years XML issue)

I've burned myself quite badly using YAML. YAML looks like a really approachable configuration language until you use it long enough to find the rough edges. It seems to me it has really bad design decisions marketed as easy to use, readable, which it is.
What worries me about adding YAML is that then there'll be more justification for using it over other better ML languages like TOML, JSON5 which are not yet in the standard library (heck, maybe I'd even give in to using it). I think if we do add YAML we should also have another ML similar language with better design so YAMLers can use their YAML and those who want a ML language, period-- can evaluate between YAML and a well designed ML language.
relevant: https://noyaml.com/

Massive yes from me. I've wished for it so many times, I even started to write a draft proposal myself but never finished it, 616 words last modified on 6 Feb 2022. With the - some would say unfortunate - prevalence of YAML, support is really needed in the standard lib I feel, so that external imports become unnecessary. External imports can be difficult to justify in heavily regulated industries, and on occasion I've JSON for things instead where perhaps YAML would have better/more consistent with other tooling and tech.

Counterproposal: Block gopkg.in/yaml in the Go module proxy to stop the virus from spreading.
YAML is a terrible format which is never appropriate to use. There is literally always a better choice. Yes, it's popular in the devops and Go world, but that's no reason to encourage it.

Certainly agree YAML is horrible to work with, and I'd personally choose JSON over YAML and put up with the lack of comments. However, I think a dislike of YAML is not a good reason not to support it via the std lib, it's just so unbelievably prevalent these days to ignore.

@sam-orca the fact that XML isn't being looked after the way it should in the standard library is probably an argument against adding more complex packages to the standard library. I suspect that, if it had to be considered for addition today, it wouldn't meet the bar outlined in the FAQ.

To echo what mvdan has said, encoding/xml has already caused security problems because it only implements a subset of XML, which makes it unsuited to use in SAML, for example. YAML would have much larger versions of the same problems. Look at https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell. YAML has directives which make producing a proper parse essentially impossible. We would have to pick a subset, and that subset would end up being observably different from Python, gopkg.in/yaml, etc. There's no alternative where we just implement the full spec. There is no full spec. Just say no to YAML.

Something being not perfect or not liked is not the measure that should be used.
Everytime something "teoritically perfect" is proposed, someone asks: "is there a real use case for this?" "how often does this come up"?
Well here we have the opposite of those proposals. something that is not perfect but it is widely used and nomater how much we may wish for, it's not going away.
XML, CVS, etc have their problems and their implementation can never be complete but I am surely grateful we have a useful standard implementation anyway.
The same goes for YAML. While I avoid it as much as I can (same as xml) the reality is that it's a must have. Better to have a standard way than again maybe 10 different 3rd party implementations all with their pecularities.

Better to have a standard way than again maybe 10 different 3rd party implementations all with their pecularities.

Why? I think it’s better to have several third party libraries carve out the subset of YAML they support and if you need a different subset, you pick a different library. What’s gained by standardizing something that resists standardization?

This discussion has been a bit heated. I just want to encourage everyone to try to take the temperature down a little. In particular, comments like https://github.com/golang/go/issues/61023#issuecomment-1609445302 are not constructive in any way, but that's not the only problematic comment here.
YAML is an important and useful data format. Among the generic data formats, it stands out for being far more human editable than JSON while still being appropriate for encoding data structures (unlike XML and CSV). In an ideal world, which perhaps would contain a somewhat different definition of YAML, having an encoding/yaml package in Go's standard library would make sense.
I have considered the question of a standard encoding/yaml package for well over a decade. On the one hand, it is widely used, including in Go's own infrastructure like x/website and many popular Go projects. It would certainly help the community to standardize on a single, robust package. On the other hand, while basic YAML looks trivial, in detail it is incredibly complex, far more so than JSON (which it embeds) or even XML (which attempts much less). A full YAML parser and printer is a very large amount of subtle code, one that the current Go team practically speaking cannot write or support. On top of that, @niemeyer has done an excellent job writing gopkg.in/yaml.v3, which as the top comment points out is the most widely used YAML package in the Go ecosystem. For that I am incredibly grateful, and I think we should continue to encourage use of that package.
I have occasionally considered defining a strict subset of YAML ("YAML: the good parts" or "YAML: what everyone thinks it means") that removes most of the unexplored dark corners and would be a better base for tooling like x/website and other projects. Almost no one needs the * notation for creating cyclic references, for example, and that causes "interesting" complexity bugs. But that too would be a lot of work, and it's unclear how much real adoption it would get, especially with a very good full YAML implementation available instead. And it wouldn't belong in the standard library, at least not to begin with.
For all these reasons, it seems clear to me that encoding/yaml is not feasible for the forseeable future and probably not even desirable either. Thanks again to @niemeyer for his excellent work on gopkg.in/yaml.v3 (and gopkg.in itself!). I encourage anyone who needs YAML support to use it, as the Go team does.

IMO, the biggest advantage of having yaml (or any encoding, really) in the standard library is not to build the end-all be-all implementation, but to create the framework for standardization.
I think we can consider encoding/json as an example.  There are many alternative implementations that have their own niches.  But the majority of them still use the standard library's json.Marshaler and json.Unmarshaler interfaces, at least as options. This standardization is valuable, even when using third-party implementations. And most, if not all, use the standard library's json struct tag syntax.  Implementation aside, these standarizations are valuable when interoperating between disparate libraries.
I think an argument could be made on the same grounds for including yaml in the Go standard library. However, it's not a particularly strong argument considering:

as already pointed out, gopkg.in/yaml.v3 is widely adopted, and thus largely, if not completely, serves this purpose already.
not all niche uses conform to the standard interfaces, even for JSON. They're even less likely to for YAML.

This proposal has been declined as infeasible.
— rsc for the proposal review group


next-css: can't load css module

Hi. Trying to load a css module, but getting this error:
 [ error ] ERROR in /test/pages/index.tsx
 1:17 Cannot find module './index.css'.
   > 1 | import css from './index.css';
       |                 ^
     2 |
     3 | function Home() {
     4 |   return
Welcome to Next

The index.css located in the same folder and contains this code:
.main {
  background: red;
}

My configuration.
next.config.js
const withCSS = require('@zeit/next-css');

module.exports = withCSS({
  cssModules: true,
  cssLoaderOptions: {
    importLoaders: 1,
    localIdentName: "[local]___[hash:base64:5]",
  }
});

package.json
{
  "name": "test",
  "version": "0.0.1",
  "description": "test",
  "main": "index.js",
  "dependencies": {
    "@zeit/next-css": "^1.0.1",
    "next": "^9.0.0",
    "react": "^16.8.6",
    "react-dom": "^16.8.6"
  },
  "devDependencies": {
    "@types/node": "^12.6.1",
    "@types/react": "^16.8.23",
    "typescript": "^3.5.3",
    "webpack": "^4.35.3"
  },
  "scripts": {
    "start": "next start",
    "dev": "next",
    "build": "next build"
  },
  "author": "Safort",
  "license": "ISC"
}

P.S.
If I importing css like this
import './index.css';

Next can find and compile it succsesful, but in that case I can't get module class name.

The issue is very bad. Tried all the options around the google. Still get following error:

ValidationError: CSS Loader Invalid Options
options should NOT have additional properties

It's a problem with css module support in typescript. You can by pass it with :
const css = require('./index.css');

Or make a file index.css.d.ts with content:
export const main: string;

@levlexx it's worked, thank you.

Add this to next-env.d.ts
declare module '*.module.css' {
  const classes: { [key: string]: string };
  export default classes;
}
declare module '*.css' {
  const classes: { [key: string]: string };
  export default classes;
}

It would really help if the above comment regarding next-env.d.ts was in the readme.md in https://github.com/zeit/next-plugins/tree/master/packages/next-css.


cant download on my vps ubuntu 20.04

Cloning into 'localtunnel-server'...
fatal: unable to connect to github.com:
github.com[0: <IP_ADDRESS>]: errno=Connection timed out

try this command:
gitt clone https://github.com/localtunnel/server.git localtunnel-server


Upgrade to .NET 8.

Is there a reason to upgrade to .NET 8? Being able to target .NET 7.0 will have more reach I think. We're not using .NET 8 specific features.

.NET 8 is LTS and .NET 7 is not.  Also, I believe .NET 8 is a feature superset of .NET 7?


python3 support and some simple unit tests

Some very simpel unittests to confirm libraries as working etc. Also updated some things that I needed for it to work on python3. It is not backwards compatible as of now (will probably be enough to include a import future print (something like that)).
Let me know what you think,

Hey, thanks for porting this to the future! Could you include whatever little fixes are needed to preserve backwards compatibility with Python 2.7? I'd be happy to merge after that.

I'll fix it and do a new commit :)

Finally updated this for backwards compatibility, changed to setuptools in setup.py and updated some things in the setup py to make sure the module installs correctly. The tests pass, but feel free to try it on python2.7. Let me know if there is anything else you want me to change.

Merging since this looks good to me at a glance, thanks @klintan !


Search Saved Tracks

Is your feature request related to a problem? Please describe.
I try to find a track in my huge saved track list, I would like the Search like you can do on Spotify.
Describe the solution you'd like
Have a way to search or filter the saved Track list or other lists if it makes sense.
Describe alternatives you've considered
Scrolling looking for the track in the list is hard.

Hi, I've just added the find dialog into Saved Tracks in 1627cd4. It's the same code as for playlists, and is quite rudimentary for now. I'll polish it a bit before the beta release.

@jpochyla I downloaded the latest binary build but can't see a search, and when clicking on a Saved Track to play, it crashes.
Not sure if it is connected to this issue.

Never mind, I think it was another bug I found; I went away and came back, and it is working again. If I can reproduce it, I will create an issue for it.

How does this search work? Is it a menu command?

@jacksongoode It is added as a section in the normal search. It has to get better; it would be friendly with just a filter in the liked songs. Search is hard to navigate now.


false positive

Hi.
https://raw.githubusercontent.com/hectorm/hmirror/master/data/digitalside-threat-intel/list.txt
This file is blocking transfer.sh, which is a legitimate command line file-sharing website. Could it be removed please?

I've reported this issue to upstream (davidonzo/Threat-Intel#19) and I've released a new hBlock version removing this list.
I don't have much more to do on my side so I'm going to close this issue.
Thanks for the notice!


数据能提供一下吗

你好，能提供一下咱们训练的数据集吗？谢谢

Hi,
We've recently been finalizing our dataset.
We will release our dataset as soon as possible.
Thank you for waiting.

Hi, we added our dataset link.
Please check the README.md.
Thank you.

您好，请问你这个代码跑通了吗？


Labeling instructions ignore empty lines formatting

Describe the bug
When typing text into "Labeling instructions" field, I use new lines to split the text into logical blocks.
But when it showed, all text is formatted as one big paragraph, without any formatting.
To Reproduce
Steps to reproduce the behavior:

Create new project
Go to Settings -> Intructions -> Labeling Instructions
Type any text with empty lines.
See error when it's displayed.

Expected behavior
Proper handling of empty lines.
Screenshots

Environment (please complete the following information):

OS: Ubuntu 16
Label Studio Version: 1.1

Instructions are in html format, please, use  for new line.


Test pipelines

Current state
The resource requirements defined in test/resources.yaml to run a specific scenario are overly involved for running live integration tests. It should not be the case that:

To run pdf_extraction you must also provide text.json. This could be generated live via Cosmos as a preamble. This also enables the test suite to use the best and latest extractions provided by Cosmos
To run profile_dataset or profile_model you should not need text.json for the same reason as mentioned above
To run link_amr you should not have to provide extractions.json since those could be generated via 1) call Cosmos on the PDF then 2) call SKEMA to generate extractions
If you have code or equations, you should be able to run link_amr without amr.json via invoking code or equation to JSON ahead of time
Running profile_model should not require having amr.json in the same case as above

Desired future state
An ASKEM team member should be able to propose a fairly complete scenario simply by providing code and a paper. This should allow a full pipeline to be tested:

PDF to cosmos
PDF extraction
Code to AMR
Profile model
Link AMR
If data is available that is associated with the paper it should also be able to be profiled.

If ground truth is offered for any of the steps above it should be able to be provided as well and have quality metrics calculated over it. Additionally, if the intermediate artifacts are provided, they should be leveraged. For example, if curated extractions exist they ought to be able to be used so error doesn't propagate. This may be of interest for more complicated scenarios where there is really no hope to run steps 1-6 above without a HITL.

[ ] Decide between the following:

Run these tests pointing at Terarium's staging environment only. To do this we would need to sync the forks of the TA1 repos automatically and have someone keep the TA1 staging K8's containers working when the syncs break something. This would require communication from TA1 to TA4 when they push any breaking changing to their codebases. This option shows the status of the bleeding edge as it is currently functioning in Terarium.
Run two sets of tests, one set pointing at the TA1 hosted services (api.askem.lum.ai) and another set pointed at the Terarium hosted services (skema-unified.staging.terarium.ai). This option shows any changes in the bleeding edge of TA1 services while showing the TA1 Terarium integration status separately.

[ ] Decide between the following:

Run full pipeline test suite from step 1-5 using generated artifacts in downstream tests. If any of the previous steps fail, substitute in hardcoded artifacts and take note that a substitution was made (i.e. a failure occured). This allows the test pipeline to run end to end regardless, but failures along the way are noted on the integration dashboard.
Run steps 1-5 as piecemeal tests like happens currently, and have an additional test that runs the full pipeline. If the pipeline fails, display where it failed on the integration dashboard and all downstream parts of the pipeline do not run.

[ ] Create a testing framework that allows a user to create their own scenarios by providing a paper and some code zip

[ ] Allow for addition and swap of testing source materials via some configuration

[ ] Create the pipeline to manage output artifacts from the following steps:

[ ] PDF to cosmos

[ ] Send provided paper to Cosmos endpoint
[ ] Process returned artifacts and store them for future endpoints to use
[ ] Finish the rest of the PDF to Cosmos test

[ ] PDF extraction (Needed?)
[ ] Code to AMR

[ ] Take provided code zip and run code to AMR process. This creates the AMR model in TDS.

[ ] Profile model

[ ] Profile the AMR that results from the Code to AMR step

[ ] Link AMR

[ ] Using prior paper extractions from pdf steps and the AMR from the code to AMR step, run the link AMR test.

[ ] If data is available that is associated with the paper it should also be able to be profiled.


Implement generating target code for resources.

This PR implements the missing support in generating code for the --target option of cargo component new when the targeted world exports items with owned and borrowed resources.

Expecting CI to fail until the wit-bindgen/wasm-tools deps are sorted out.


Slow to open a Go file with long line

Issue Type: Performance Issue
File https://gist.githubusercontent.com/egonelbre/f93be4d31e7f4dad766a5e8f63374bb3/raw/747cf854bef769e3b8f57edbe207e4e001d98421/example.go is very slow to open. ~20s
This does not happen when file is renamed to example.c.
VS Code version: Code 1.40.2 (f359dd69833dd8800b54d458f6d37ab7c78df520, 2019-11-25T14:52:45.129Z)
OS version: Darwin x64 19.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz (4 x 2700)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
3, 4, 3

Memory (System)
8.00GB (0.10GB free)

Process Argv

Screen Reader
no

VM
0%

Workspace Info
|  Window (~/code/adventofcode >)
|    Folder (adventofcode): 63 files
|      File types: go(43) gitignore(1) mod(1) js(1) json(1) md(1)
|      Conf files: settings.json(1);

Extensions (6)

Extension
Author (truncated)
Version

gotemplate
cas
0.3.0

dart-code
Dar
3.7.0

vue
jcb
0.1.5

csharp
ms-
1.21.8

proto
pet
0.0.2

vscode-svg-previewer
vit
0.5.1

Profiling seems to indicate Go syntax highlighting is hitting a bad-case.

https://github.com/microsoft/vscode/issues/82549 could end up fixing this as a side-effect.

Profiling seems to indicate that the parsing time is growing non-linearly, which isn't great.

size
time

~5K
~2.5s

~10K
~9s

~15K
~20s

~19K
~34s

The main culprit seems to be "match": "(?<!var)\\s*(\\w+(?:\\.\\w+)*(?>,\\s*\\w+(?:\\.\\w+)*)*)(?=\\s*=(?!=))", at https://github.com/microsoft/vscode/blob/master/extensions/go/syntaxes/go.tmLanguage.json#L231
Removal improvement: 15.1s -> 3.6s.
The second culprit is "match": "(\\bfunc\\b)|(\\w+)(?=\\()", at https://github.com/microsoft/vscode/blob/master/extensions/go/syntaxes/go.tmLanguage.json#L130
Changing to \\bfunc\\b improved from 3.6s -> 0.006s.
I also tried opening the same file with Atom so it doesn't seem like a problem in https://github.com/atom/language-go.

Atom doesn't use the textmate grammar at https://github.com/atom/language-go anymore, so issues with the textmate grammar that VS Code uses likely won't occur there.
Since atom is no longer making changes to the textmate grammar, #82549 is the best hope for fixing this.


Add eslint-plugin-import

See https://github.com/netlify/build/issues/1955
This adds eslint-plugin-import.

This is very strange, the tests are passing locally but failing in CI.
Also, the linting error is showing a line of code which does not exist... Any ideas @erezrokah?


cmd/cgo: Relocation overflow occurring when calling crosscall2 on aix/ppc64

While trying to compile metricbeat (with go1.15rc1 and 1.14.6), we discovered that a relocation overflow might occur when a CGO generated file tries to call crosscall2.
ld: 0711-780 SEVERE ERROR: Symbol .CallbackSubscr (entry 49130) in object /tmp/golang/000019.o:
       Relocation overflow in reference to: .crosscall2 (entry 6)
       Address: 0x0000004c;    RLD type: R_RBR;   RLD length: 26

I don't really know why ld isn't able to generate a trampoline but we don't want one anyway as it might end up being added inside Golang generated .text section, changing the offset, alignement, etc. The problem already happened with kubernetes where we decided to add __attribute__((longcall)) for a few runtime/cgo functions (cf gcc_aix_ppc64.c).
It's possible to do the same thing in generated CGO code (here), but I don't know if it's possible to add it only for AIX ? Moreover, could it be merged for 1.15 (and maybe backported to 1.14) ? This error is not a new one, thus I don't remember if it's possible to merge it this late in the cycle.
@fearful-symmetry

/cc @ianlancetaylor


Update policy-csp-update.md

In 1903 we deprecated the value of 32 and combined Semi-Annual Channel (Targeted) with the Semi-Annual Channel. We need to communicate this change in the documentation.

@manikadhiman Please review and merge this PR that seems to be from an internal source. Thanks.

@ManikaDhiman Following up for updates.

Hello All,
I do not see the changes yet in the Docs page. Can you please confirm that the changes were encorperated?
Best,
Aria
From: Manika Dhiman<EMAIL_ADDRESS>Sent: Tuesday, July 23, 2019 3:12 PM
To: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>Cc: Aria Carley<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-itpro-docs] Update policy-csp-update.md (#4505)
Merged #4505https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fpull%2F4505&data=02|01|arianna.carley%40microsoft.com|2be5b8dc147541f30d7308d70fbac764|72f988bf86f141af91ab2d7cd011db47|1|0|636995167197326606&sdata=g%2FonwCv%2F4ol4%2B86CjQvI5wfJJEUj0X9pB5VKVvQ%2BPRE%3D&reserved=0 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fpull%2F4505%3Femail_source%3Dnotifications%26email_token%3DAMNY66NOIMJ554HGATW7YPTQA5623A5CNFSM4IFLIGUKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSVEKIBQ%23event-2504565766&data=02|01|arianna.carley%40microsoft.com|2be5b8dc147541f30d7308d70fbac764|72f988bf86f141af91ab2d7cd011db47|1|0|636995167197336597&sdata=%2FkpIoGe07mVmv0kuxZ0ZFMlcB1zb8UR5hjgsdwMAbfI%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMNY66PT5A7OQ5WV6YAIKPLQA5623ANCNFSM4IFLIGUA&data=02|01|arianna.carley%40microsoft.com|2be5b8dc147541f30d7308d70fbac764|72f988bf86f141af91ab2d7cd011db47|1|0|636995167197336597&sdata=0qntJNwjMfarfvLSXYznqRS02LCgEzZE2UJ91ZGFGMM%3D&reserved=0.

@arcarley : I presume your question is about the doc page https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update and its Github source https://github.com/MicrosoftDocs/windows-itpro-docs/blob/master/windows/client-management/mdm/policy-csp-update.md

Your PR got merged into the Github source 7 days ago in commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/075a38373c7b133b3eb97e75b504ff85041689e0 (file link https://github.com/MicrosoftDocs/windows-itpro-docs/commit/075a38373c7b133b3eb97e75b504ff85041689e0#diff-325a2815ead8b1adb632466282c8e341) - July 23 2019, 23:13 GMT.
The docs.microsoft.com target page has not yet been updated since 05/21/2019, but I presume this is because the migration process can sometimes (at least these days) take a week or more. These days, knowing that it is summer holiday/vacation season, it might take even longer. Not to worry, it will be published, although a little slower than we expected.

Perfect, thank you! :)

From: Trond B. Krokli<EMAIL_ADDRESS>Sent: Tuesday, July 30, 2019 5:30:08 PM
To: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>Cc: Aria Carley<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-itpro-docs] Update policy-csp-update.md (#4505)
@arcarleyhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farcarley&data=02|01|arianna.carley%40microsoft.com|30d2b54543d543e5a13b08d7154e3e21|72f988bf86f141af91ab2d7cd011db47|1|0|637001298096562518&sdata=%2FvR7A1xEcwpvWGgGuVlmqh9RIJYe28uORXwXeMMTVhs%3D&reserved=0 : I presume your question is about the doc page https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-updatehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fpolicy-csp-update&data=02|01|arianna.carley%40microsoft.com|30d2b54543d543e5a13b08d7154e3e21|72f988bf86f141af91ab2d7cd011db47|1|0|637001298096562518&sdata=d%2FSXoXqAQ5K8zpAPZavgh9X5jvgdBiX7RBgY8lRTMQ8%3D&reserved=0 and its Github source https://github.com/MicrosoftDocs/windows-itpro-docs/blob/master/windows/client-management/mdm/policy-csp-update.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fblob%2Fmaster%2Fwindows%2Fclient-management%2Fmdm%2Fpolicy-csp-update.md&data=02|01|arianna.carley%40microsoft.com|30d2b54543d543e5a13b08d7154e3e21|72f988bf86f141af91ab2d7cd011db47|1|0|637001298096572511&sdata=K6s2PbSg5XlAk18Fr6Woj5FU0v4nq3vkDWcExkcNZBo%3D&reserved=0

Your PR got merged into the Github source 7 days ago in commit 075a383https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fcommit%2F075a38373c7b133b3eb97e75b504ff85041689e0&data=02|01|arianna.carley%40microsoft.com|30d2b54543d543e5a13b08d7154e3e21|72f988bf86f141af91ab2d7cd011db47|1|0|637001298096572511&sdata=pAAACNI%2FcvHYMkKxuikX9j7xl9MxXkcA0XJrZLoggNU%3D&reserved=0 (file link 075a383#diff-325a2815ead8b1adb632466282c8e341https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fcommit%2F075a38373c7b133b3eb97e75b504ff85041689e0%23diff-325a2815ead8b1adb632466282c8e341&data=02|01|arianna.carley%40microsoft.com|30d2b54543d543e5a13b08d7154e3e21|72f988bf86f141af91ab2d7cd011db47|1|0|637001298096582504&sdata=0WEZvARY27nVTs69DF8Qs7eFwePRXvKHmliUR7NvLO4%3D&reserved=0) - July 23 2019, 23:13 GMT.
The docs.microsoft.com target page has not yet been updated since 05/21/2019, but I presume this is because the migration process can sometimes (at least these days) take a week or more. These days, knowing that it is summer holiday/vacation season, it might take even longer. Not to worry, it will be published, although a little slower than we expected.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fpull%2F4505%3Femail_source%3Dnotifications%26email_token%3DAMNY66LXPLJWQS2DLZFCU7LQCDMJBA5CNFSM4IFLIGUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3FWJII%23issuecomment-516646049&data=02|01|arianna.carley%40microsoft.com|30d2b54543d543e5a13b08d7154e3e21|72f988bf86f141af91ab2d7cd011db47|1|0|637001298096582504&sdata=O95L0YOndUluoYYxt49wTgP6cOQk118feSeksYyZWUk%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMNY66NA5KUDKJJL3K3LFCLQCDMJBANCNFSM4IFLIGUA&data=02|01|arianna.carley%40microsoft.com|30d2b54543d543e5a13b08d7154e3e21|72f988bf86f141af91ab2d7cd011db47|1|0|637001298096592498&sdata=NRrDEla6pVp7pYBVTNzkV3cjYMpfL4Vk9vqhWsaEr0k%3D&reserved=0.


run a script on every xiwi window open?

I have to run the command setxkbmap -model chromebook every time a xiwi window opens to fix the keyboard (#1558).  Is there any way xiwi could run a script of mine on every window open?  It needs to run in the new process but it doesn't have to run before the app that xiwi is opening.
This might have other use cases also.

Yep, just add your commands to ~/.xiwirc in your chroot.


Settings Editor is not launching in PGO tests

The nightly canary build failed to PGO TerminalSettingsEditor due to no counts, which suggests that it didn't get exercised in last night's PGO run. That further hints that it may not have opened.
The PGO agents run Windows 10, I think? And they launch in unpackaged mode. May be a good place to start the investigation!

Unpackaged build fresh off of #16954 (the first PR I clicked on with a finished CI run), on a win10 vm.
So, it's not that.

notes
##[warning]PGOMGR(0,0): Warning PG0188: No .PGC files matching 'C:\__w\1\s\build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor!*.pgc' were found.
    34>PGOMGR : warning PG0188: No .PGC files matching 'C:\__w\1\s\build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor!*.pgc' were found. [C:\__w\1\s\src\cascadia\TerminalSettingsEditor\Microsoft.Terminal.Settings.Editor.vcxproj]
           Reading PGD file 1: C:\__w\1\s\build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor.pgd
##[error]build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor.pgd(0,0): Error C2220: the following warning is treated as an error
    34>C:\__w\1\s\build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor.pgd : error C2220: the following warning is treated as an error [C:\__w\1\s\src\cascadia\TerminalSettingsEditor\Microsoft.Terminal.Settings.Editor.vcxproj]
##[warning]build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor.pgd(0,0): Warning C4961: No profile data was merged into 'C:\__w\1\s\build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor.pgd', profile-guided optimizations disabled
    34>C:\__w\1\s\build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor.pgd : warning C4961: No profile data was merged into 'C:\__w\1\s\build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor.pgd', profile-guided optimizations disabled [C:\__w\1\s\src\cascadia\TerminalSettingsEditor\Microsoft.Terminal.Settings.Editor.vcxproj]
            Creating library C:\__w\1\s\bin\x64\Release\Microsoft.Terminal.Settings.Editor\Microsoft.Terminal.Settings.Editor.lib and object C:\__w\1\s\bin\x64\Release\Microsoft.Terminal.Settings.Editor\Microsoft.Terminal.Settings.Editor.exp
         Generating code
##[error]LINK(0,0): Error LNK1257: code generation failed
    34>LINK : fatal error LNK1257: code generation failed [C:\__w\1\s\src\cascadia\TerminalSettingsEditor\Microsoft.Terminal.Settings.Editor.vcxproj]

abridged:

PGOMGR : warning PG0188: No .PGC files matching 'C:\__w\1\s\build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor!*.pgc'
warning C4961: No profile data was merged into 'C:\__w\1\s\build\PGO\..\..\packages\Microsoft.Internal.Windows.Terminal.PGODatabase.1.21.0-2403272312-main\tools\x64\Microsoft.Terminal.Settings.Editor.pgd', profile-guided optimizations disabled

etc

LKG: Windows Terminal OneBranch Signed Nightly_2403.26001

dc64efca5e866f386d875eefbdd00ce8b9ae67bb

#16821
#16944

First bad: #Windows Terminal OneBranch Signed Nightly_2403.27001

but that was dusting messing with the build

First NIGHTLY bad: Windows Terminal OneBranch Signed Nightly_2403.27010

862ff39cbadac53aa9d5c4eb3e1dd3c89ea2f8eb

Just the copy task 6 revert?

The PGO builds trail the nightlies by one night - so the bad data would have been produced one or more nights previously in instrument pipelines

The last PGO build that successfully instrumented TSE was 0.0.2403.2501.
The first one that failed was 0.0.2403.2601; evidenced by this message:
Running pgosweep on 'Microsoft.Terminal.Settings.Editor.dll' for test: WindowsTerminal.UIA.Tests.SmokeTests.RunOpenSettingsUI
Microsoft (R) Profile Guided Optimization Sweeping Utility 14.38.33130.0
Copyright (C) Microsoft Corporation. All rights reserved.

PGOSWEEP : fatal error PG1032: Can find no running instrumented instance of image 'Microsoft.Terminal.Settings.Editor.dll'.

All new in -26.
* de7f93122 Add support for customizing font fallback (#16821)
* a67a13288 AtlasEngine: Make Direct2D/3D and Present1 configurable (#16939)
* 501522d69 Add an experimental "scratchpad pane", for testing (#16171)
* e8f18ea92 ci: trigger builds for gh-readonly-queue/* merge queue branches (#16941)
* 08dc34612 Refactor Pane to be able to host non-terminal content (#16170)

Test instrumentation builds:

de7f93122: https://microsoft.visualstudio.com/Dart/_build/results?buildId=94842448&view=results
08dc34612: https://microsoft.visualstudio.com/Dart/_build/results?buildId=94842479&view=results
main, but then just send escape at the start: https://microsoft.visualstudio.com/Dart/_build/results?buildId=94842645&view=results

Win10 VM, without any other terminals installed (so no cascadia code/mono anywhere)

We suspect we broke nearby font loading, but only on windows 10.

This was fixed by #16993


Lambda.Function doesn't seem to be shipping the code

although this is being triggered by the wrapper in https://github.com/punchcard/punchcard/blob/d0b6fe43d5e9ef5994c96929b28405bf7ca6cc45/packages/punchcard/lib/core/code.ts#L90-L111
error returned by AWS::CloudFront::Distribution step:
The function cannot have environment variables. Function: arn:aws:lambda:us-east-1:xxxx:function:xxxx:1 (Service: AmazonCloudFront; Status Code:
400; Error Code: InvalidLambdaFunctionAssociation; Request ID: xxxx)

some kind of heuristic analysis on AWS side I guess. the code below is enough to trigger this when adding to a CloudFrontWebDistribution
import {
  CloudFrontResponseEvent,
  CloudFrontResponseResult,
} from 'aws-lambda'

// hide frontend from search engines / bots
const noIndex = new Lambda.Function(stack, 'app-noindex-lambda', {
  handle: async (event: CloudFrontResponseEvent): Promise<CloudFrontResponseResult> => {
    const response = event.Records[0].cf.response
    const headers = response.headers

    headers['x-robots-tag'] = [{
      key: 'X-Robots-Tag',
      value: 'noindex,nocache,nofollow'
    }]

    return response
  }
})

stack.map((s) => {
  /* ... */
  const noIndexVersion = new Version(s, 'no-index-version', {
    lambda: Build.resolve(noIndex.resource)
  })

  new CloudFrontWebDistribution(s, 'frontend', {
    /* ... */
    originConfigs: [
      {
        behaviors: [{
          /* ... */
          lambdaFunctionAssociations: [
            {
              eventType: LambdaEdgeEventType.VIEWER_RESPONSE,
              lambdaFunction: noIndexVersion
            }
          ]
        }],
      },
    ]
  });
  /* ... */
})

EDIT: just noticed that the build step isn't happening for the "handler" property and the code isn't being packaged. the .punchcard has the unbuilt (aka, just the wrapper) app.js file and the app.js doesn't exist, or I'm doing something wrong

Oh no, sorry about the bugs!
Looks like that CloudFront problem is caused by a restriction for Lambda@Edge functions - that is a case I was not anticipating. PC currently relies on environment variables for bootstrapping lambda functions with things like ARNs. For this case, we'll need to come up with another solution, I'll need to look into that more.
RE: the code packaging issue, I'll need to dig deeper in. Can you provide a working code snippet I can debug for you?

This seems relevant: https://aws.amazon.com/blogs/networking-and-content-delivery/leveraging-external-data-in-lambdaedge/

Lambda@Edge functions will have to fetch their configuration data from a remote source. Perhaps we need to write a Custom Resource to collect things like Table ARN at deploy time and store them in a S3 object for the edge function to grab at container boot time.
This could also be a part of a larger solution to passing arbitrarily large data to a function as configuration, where the data doesn't fit in an environment variable.

yeah, about Lamda@Edge, if you need to do something more advanced than just setting / retrieving values, it might get nasty without an opinionated way to do this. fetching config using json files should be a good bet like the article proposes! fetch, parse then map the resources (although we are doing AWS job here haha)
About the "not packaging", I'll try to do a minimum repro. I was about to debug punchcard with my current CDK stack, but the cloudfront was failing (not an issue with punchcard), and I was wasting ~45 minutes per try because of a bug (aws/aws-cdk#5269).

@sam-goodwin found the issue, it's trying to compile the TS file without the typescript plugin (I'm using ts-node in cdk.json). in core/app.ts there's a call to core/code.ts, and it's failing inside "compile.run". the funny thing is that the "err" variable is null, which makes it even more confusing. second variable, that is currently omitted is the "Stats" class, and the "compilation.errors" member isn't empty:
[
  ModuleParseError: Module parse failed: Unexpected token (77:23)
  You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
  | const certificateArn = 'arn:aws:acm:us-east-1:xxxx:certificate/xxxx'
  |
  > const viewerCertificate: ViewerCertificate = {
  |   aliases: ['xxxx'],
  |   props: {
      at handleParseError (G:\www\reader\deploy\node_modules\webpack\lib\NormalModule.js:469:19)
      at G:\www\reader\deploy\node_modules\webpack\lib\NormalModule.js:503:5
      at G:\www\reader\deploy\node_modules\webpack\lib\NormalModule.js:358:12
      at G:\www\reader\deploy\node_modules\loader-runner\lib\LoaderRunner.js:373:3
      at iterateNormalLoaders (G:\www\reader\deploy\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
      at Array.<anonymous> (G:\www\reader\deploy\node_modules\loader-runner\lib\LoaderRunner.js:205:4)
      at Storage.finished (G:\www\reader\deploy\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16)
      at G:\www\reader\deploy\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9
      at G:\www\sale-reader\deploy\node_modules\graceful-fs\graceful-fs.js:115:16
      at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
]

so basically, besides checking for "err" there
https://github.com/punchcard/punchcard/blob/3dc3e5ad19bc3734998c6caf330e156d9cd252d7/packages/punchcard/lib/core/code.ts#L113-L120
you'd need to check for the length of the "compilation.errors" array.
so, in the end, I need to compile my app.ts to .js before trying to do a cdk synth

@sam-goodwin found the issue, it's trying to compile the TS file without the typescript plugin (I'm using ts-node in cdk.json). in core/app.ts there's a call to core/code.ts, and it's failing inside "compile.run". the funny thing is that the "err" variable is null, which makes it even more confusing. second variable, that is currently omitted is the "Stats" class, and the "compilation.errors" member isn't empty:
[
  ModuleParseError: Module parse failed: Unexpected token (77:23)
  You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
  | const certificateArn = 'arn:aws:acm:us-east-1:xxxx:certificate/xxxx'
  |
  > const viewerCertificate: ViewerCertificate = {
  |   aliases: ['xxxx'],
  |   props: {
      at handleParseError (G:\www\reader\deploy\node_modules\webpack\lib\NormalModule.js:469:19)
      at G:\www\reader\deploy\node_modules\webpack\lib\NormalModule.js:503:5
      at G:\www\reader\deploy\node_modules\webpack\lib\NormalModule.js:358:12
      at G:\www\reader\deploy\node_modules\loader-runner\lib\LoaderRunner.js:373:3
      at iterateNormalLoaders (G:\www\reader\deploy\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
      at Array.<anonymous> (G:\www\reader\deploy\node_modules\loader-runner\lib\LoaderRunner.js:205:4)
      at Storage.finished (G:\www\reader\deploy\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16)
      at G:\www\reader\deploy\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9
      at G:\www\reader\deploy\node_modules\graceful-fs\graceful-fs.js:115:16
      at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
]

so basically, besides checking for "err" there
https://github.com/punchcard/punchcard/blob/3dc3e5ad19bc3734998c6caf330e156d9cd252d7/packages/punchcard/lib/core/code.ts#L113-L120
you'd need to check for the length of the "compilation.errors" array.
so, in the end, I need to compile my app.ts to .js before trying to do a cdk synth

This change also helped this problem: https://github.com/punchcard/punchcard/pull/84
Before: if the webpack compilation failed, then the error was swallowed silently, so synth would succeed but there'd be no code (app.js).

the initial issue is gone along with #84, so I guess this could be closed 👍
for the lambda@edge issue, I'll open a new one, since I mixed a lot of stuff in here haha


Add tests for Data Science Projects page

Initial testing for the upcoming feature. Tests will be developed incrementally based on feature development.

Jenkins Job: SUCCESS - approx 17 minutes of run

@bdattoma I see a few failures in the dryrun, could you take a look?
==============================================================================
[ ERROR ] Error in file '/home/runner/work/ods-ci/ods-ci/tests/Tests/400__ods_dashboard/415__ods_dashboard_projects/415__ods_dashboard_projects_templates.robot' on line 5: Resource file '../../../Resources/Page/ODH/ODHDashboard/ODHDataScienceProject/Workspaces.resource' does not exist.
Tests.Ods Dashboard.Ods Dashboard Projects.Ods Dashboard Projects Templates
==============================================================================
Verify User Can Create A Data Science Project                         | FAIL |
Setup failed:
Keyword 'ODHDashboard.Launch Dashboard' expected 6 arguments, got 3.
------------------------------------------------------------------------------
Verify User Can Create A Workspace With Ephimeral Storage             | FAIL |
Setup failed:
Keyword 'ODHDashboard.Launch Dashboard' expected 6 arguments, got 3.
------------------------------------------------------------------------------
Verify User Can Create A Workspace With Persistent Storage            | FAIL |
Setup failed:
Keyword 'ODHDashboard.Launch Dashboard' expected 6 arguments, got 3.
------------------------------------------------------------------------------
Tests.Ods Dashboard.Ods Dashboard Projects.Ods Dashboard Projects ... | FAIL |
3 tests, 0 passed, 3 failed
==============================================================================
Tests.Ods Dashboard.Ods Dashboard Projects                            | FAIL |
23 tests, 20 passed, 3 failed
==============================================================================

@bdattoma I see a few failures in the dryrun, could you take a look?
==============================================================================
[ ERROR ] Error in file '/home/runner/work/ods-ci/ods-ci/tests/Tests/400__ods_dashboard/415__ods_dashboard_projects/415__ods_dashboard_projects_templates.robot' on line 5: Resource file '../../../Resources/Page/ODH/ODHDashboard/ODHDataScienceProject/Workspaces.resource' does not exist.
Tests.Ods Dashboard.Ods Dashboard Projects.Ods Dashboard Projects Templates
==============================================================================
Verify User Can Create A Data Science Project                         | FAIL |
Setup failed:
Keyword 'ODHDashboard.Launch Dashboard' expected 6 arguments, got 3.
------------------------------------------------------------------------------
Verify User Can Create A Workspace With Ephimeral Storage             | FAIL |
Setup failed:
Keyword 'ODHDashboard.Launch Dashboard' expected 6 arguments, got 3.
------------------------------------------------------------------------------
Verify User Can Create A Workspace With Persistent Storage            | FAIL |
Setup failed:
Keyword 'ODHDashboard.Launch Dashboard' expected 6 arguments, got 3.
------------------------------------------------------------------------------
Tests.Ods Dashboard.Ods Dashboard Projects.Ods Dashboard Projects ... | FAIL |
3 tests, 0 passed, 3 failed
==============================================================================
Tests.Ods Dashboard.Ods Dashboard Projects                            | FAIL |
23 tests, 20 passed, 3 failed
==============================================================================

yeah but these are old

Jenkins Job RUNNING


Optimize the style of the head of the index page.

Optimize the style of the head of the index page.when the page moves to the area with white background, the background color of the head turns to black.


Speedup

Addresses Issues #25 and #35 to speedup plotting by appending new simulation results written by simulation thread to MainWindow private (plotted) data. This is faster than the old way which copied and replotted all results each plot refresh period.

Tested and looks good to me

Tested and looks good to me

Rick messed up merges so these modifications/features have been moved to branch speedup2

Rick messed up merges so these modifications/features have been moved to branch speedup2


[Harvesting] Provide Cluster API for CoreCoord

Provide Cluster (read/write) API for all types of coordinates (logical, physical, virtual)

Closed by #401


hw-probe: init at 1.6.4

Description of changes
This adds hw-probe to nixpkgs.  First time creating a package on nix, LMK if there's any gotchas to check out :).
Note:  there are a slew of optional dependencies.  I am thinking this could be added in a follow-up contribution, creating hw-probe.full as an alternative package.  See the hw-probe.pl file in the source distribution for a list of optional dependencies.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I did
docker run -ti --rm -v $PWD:/nixpkgs nixos/nix sh -c 'cd /nixpkgs; nix-build -A hw-probe; /nix/store/*/bin/hw-probe -probe'

to verify it works and is not pulling in runtime dependencies from my systemPackages.

Very pleasant to see people working on this package, thanks for your effort!
I just noted that there is another person working on the same package: https://github.com/NixOS/nixpkgs/pull/168787
Maybe you want to team up with each other.

Thanks for pointing that out!  Unsure how I missed the existing work!  The earlier PR looks far more mature.  I'll test and leave comments in the other PR.


Error with _ufunc_config.config

When dispatching using CuPy from Dask (multithreaded python) there is a failure due to _ufunc_config.config

Conditions (you can just paste the output of python -c 'import cupy; cupy.show_config()')

CuPy Version          : 7.0.0
CUDA Root             : /usr/local/cuda-10.1/
CUDA Build Version    : 10010
CUDA Driver Version   : 10010
CUDA Runtime Version  : 10010
cuBLAS Version        : 10201
cuFFT Version         : 10101
cuRAND Version        : 10101
cuSOLVER Version      : (10, 2, 0)
cuSPARSE Version      : 10300
NVRTC Version         : (10, 1)
cuDNN Build Version   : None
cuDNN Version         : None
NCCL Build Version    : None
NCCL Runtime Version  : None

Code to reproduce

import dask, cupy
import dask.array as da

rs = dask.array.random.RandomState(RandomState=cupy.random.RandomState)
x = rs.random((100, 100))
x = x.persist()
u, s, v = da.linalg.svd(x)
u.compute()

Error messages, stack traces, or logs

Traceback
Traceback (most recent call last):
  File "cpu-svd.py", line 10, in <module>
    u.compute()
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/base.py", line 165, in compute
    (result,) = compute(self, traverse=False, **kwargs)
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/base.py", line 436, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/threaded.py", line 81, in get
    **kwargs
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/local.py", line 486, in get_async
    raise_exception(exc, tb)
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/local.py", line 316, in reraise
    raise exc
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/local.py", line 222, in execute_task
    result = _execute_task(task, data)
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/core.py", line 119, in _execute_task
    return func(*args2)
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/optimization.py", line 982, in __call__
    return core.get(self.dsk, self.outkey, dict(zip(self.inkeys, args)))
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/core.py", line 149, in get
    result = _execute_task(task, cache)
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/core.py", line 119, in _execute_task
    return func(*args2)
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/dask/array/linalg.py", line 48, in _wrapped_qr
    return np.linalg.qr(a)
  File "<__array_function__ internals>", line 6, in qr
  File "cupy/core/core.pyx", line 1344, in cupy.core.core.ndarray.__array_function__
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/cupy/linalg/decomposition.py", line 248, in qr
    geqrf, dev_info)
  File "/datasets/bzaitlen/miniconda3/envs/rapids-12/lib/python3.7/site-packages/cupy/linalg/util.py", line 42, in _check_cusolver_dev_info_if_synchronization_allowed
    print(cupyx._ufunc_config.config.linalg)
AttributeError: '_thread._local' object has no attribute 'linalg'

Rather than using threading.local() here
https://github.com/cupy/cupy/blob/f06f509167957240d17924965238cb0901b700ab/cupyx/_ufunc_config.py#L4-L13
We could use types for a two line code change:
import types

config = types.SimpleNamespace()

But I may be missing this reason as for using threads here

@quasiben
Thank you for reporting!

FYI backport PR to v7 is here: #2937


Hande our social accounts

[x] register meaningful twitter name https://twitter.com/rcn_io
[ ] create Facebook page
[ ] decide on how to maintain and what to post there
[ ] should we periodically post stuff and updates? e.g. releases?
[ ] should we post anything else, things about racing/cycling in general?

We can use this to manage postings https://buffer.com @Me4ta


Add native to the docs

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
First off, I love the new structure!
Here are my biggest questions with regards to getting native in the site:

Queries aren't the same between native and dom. Should we make those more of a generic priority list and explain the reasoning? Maybe something like "Things a user can see", "Things that denote hierarchy", "Things hidden from users"
Native doesn't have a DOM to observe, so on native all of the wait utils are the same. In fact, they don't even all exist. I only ported wait and waitForElement (for convenience). How should we handle that guide?
The examples are roughly equivalent with the exception of routing and transition group. Should example titles be more generic? "Firing Events", "Updating Props", "Navigating" "Managing State" so that we can use code tabs to split native and dom?
From the guiding principles: "If it relates to rendering components, it deals with DOM nodes" but native doesn't have DOM nodes. The big overarching question here is, would basically all pages need to be revised to take into account that testing-library is no longer about "DOM" or "documents" but about user experiences? Who should be the one to do those edits if yes?
Once I got all of native's sections ported over (think basically every section under DOM Testing Library right now) the sidebar would actually be pretty long. It was nice to have everything easily accessible at first, but this may get really long. Do you think that would be overbearing?
The ecosystems are platform specific, right? I don't want to mislead people into thinking user-event would work with native and cause lots of issues and requests for the maintainers of ecosystem components.

Overall though, huge update with lots of good work!
Describe alternatives you've considered
N/A
Additional context
Would the navbar title need to change to "Testing Library" from "DOM Testing Library"?

I'm kinda feeling like merging the two would cause undue confusion on everyone involved (maintainers included). 🤔

I can definitely see that. The thing I keep going back to, I would love a testing-library site dedicated solely to principles and guides. That site could also serve as an entry point to family packages and wrappers.
I may be thinking too big here but I see testing-library as more of a philosophy than a library. Implementations of that philosophy right now are DOM and Native. Wrappers of those implementations are angular, react, Vue, etc.
I’ll admit this doesn’t work super great because “native” is actually react native (naming conflict) and there’s no underlying platform that another library could wrap and take advantage of. But it seems close. Does that seem wrong to you guys?

Honestly, I'm not sure how I feel about it. I know that I want to make things simple for people, but I don't know how much more time I can dedicate to improving documentation currently :-/ (@alexkrolick has actually been doing most of that work for the last few months ❤)

If we could slightly condense the Native docs I think they would fit in OK

https://testing-library.com/docs/intro is pretty generic now, and calls out some of the more divergent libraries - Reason and Native
the API docs are now scoped to the DTL heading, and wrappers for web frameworks reference that directly
the examples right now are pretty heavily focused on React - it would be good to add support for Vue and other libraries anyways, so Native examples could probably fit in to that

I've been thinking about this, and as a part of the process I've switched native's docs to match the new format.
I think this will help see how things could merge. That said, to your point Kent, it may just not make things simpler. My goal is to think on it for a few days to see how we all feel about it.

I think I'm going to go ahead and close this for now because I haven't been able to think about it much more.
If this is something you're still interested in @alexkrolick and @kentcdodds we can keep working on it. If it's something you'd rather not do, I'm fine with that approach as well. Just let me know 👍


Merge two binary Max heaps

Given two binary max heaps as arrays, merge the given heaps to form a new max heap.

Example-
Input  :
n = 4 m = 3
a[] = {10, 5, 6, 2},
b[] = {12, 7, 9}
Output :
{12, 10, 9, 2, 5, 7, 6}

/assign


[Candidate 1v1 Oil Rampage V3] Title text is inconsistent to other ranked maps

Issue Description
Title says "Oil Rampage \n Made by: TKLyo"
Expected behavior
Title says "Oil Rampage, by TKLyo"
Screenshots

Fixed with https://github.com/xezon/GeneralsRankedMaps/commit/bdf1faea39459ae850e8e89e263550d7cf3436f1


fatal crash of tool

I will install tools on Linux Mint 18.1 Serena without error:
$ sudo npm install -g geobuf

All convert tool crash, i.e. json2geobuf. Any idea?
$ json2geobuf

fs.js:540
binding.open(pathModule._makeLong(path),
^
TypeError: path must be a string
at TypeError (native)
at Object.fs.open (fs.js:540:11)
at ReadStream.open (fs.js:1677:6)
at new ReadStream (fs.js:1664:10)
at Object.fs.createReadStream (fs.js:1612:10)
at Object. (/usr/local/lib/node_modules/geobuf/bin/json2geobuf:8:38)
at Module._compile (module.js:410:26)
at Object.Module._extensions..js (module.js:417:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
$ json2geobuf issue62.json > issue62.pbf
/usr/local/lib/node_modules/geobuf/bin/json2geobuf:20
var buffer = Buffer.from(encode(geojson, new Pbf()));
^
TypeError: this is not a typed array.
at Function.from (native)
at /usr/local/lib/node_modules/geobuf/bin/json2geobuf:20:25
at ConcatStream. (/usr/local/lib/node_modules/geobuf/node_modules/concat-stream/index.js:36:43)
at emitNone (events.js:72:20)
at ConcatStream.emit (events.js:166:7)
at finishMaybe (/usr/local/lib/node_modules/geobuf/node_modules/readable-stream/lib/_stream_writable.js:607:14)
at endWritable (/usr/local/lib/node_modules/geobuf/node_modules/readable-stream/lib/_stream_writable.js:615:3)
at ConcatStream.Writable.end (/usr/local/lib/node_modules/geobuf/node_modules/readable-stream/lib/_stream_writable.js:571:41)
at ReadStream.onend (_stream_readable.js:490:10)
at ReadStream.g (events.js:260:16)

Looks like this was caused by using an older Node version which didn't provide support for Buffer.from(typedArray). Should work properly for Node v4.5.0+.


⚠ ClamAV has degraded performance

In 0752e8b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 251 ms

Resolved: ClamAV performance has improved in 403086d after 5 minutes.


Login using Google credentials

As a registered user, I can login to ZVGQ using my Google credentials, so that I don't have to remember another username or password.

Commited 587b3e91fb14260e9bc99164f4a2261844e93a73.


[Feature Request]:  Developing each page for the requested tab in the bar

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

On clicking all these tabs the Home page is directed. I want to add the feature of Contact, About and the others as well thus making these tabs function properly and also enhancing the features of the website.
Please assign me this issue
I am a GSSoC'24 Contributor, proficient in HTML, CSS, JavaScript and having good knowledge of React.js and Web Design as well.
Use Case
On adding the pages for Contact and About, the reach of this website can be increased through social media. Also we could credit the Team behind building and developing this website; also News section can hold some art based facts or news depending on the necessity of it.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor
[X] I want to work on this issue

@K-Svayam05 Already being fixed in #234 & #226

@K-Svayam05 Already being fixed in #234 & #226

Okay Sir. Do consider Me for any future issues! Would love to work on this project :)

@K-Svayam05 The app still needs too much improvement so you can find bugs that you can fix or enhancements that you can make & create issues for the same after checking whether there is already any issue regarding that or not.


[QUESTION/HELP] DNS-Resolution inside Pods is not working (related to CoreDNS File-Plugin?)

DNS-Resolution of external domains not working inside pods
Since today (2024-07-08) I've a problem with DNS-Resolution inside pods running in a k3d-cluster.
But as soon as I comment-out the file-plugin inside the coredns-custom ConfigMap the problem goes away.
But without the file-plugin the dns-resolution of host.k3d.internal cannot work.
K3D Version:
❯ k3d version
k3d version v5.7.0
k3s version v1.29.6-k3s1 (default)

The Problem:
I can't resolve any external domain, here is an example with google.com
❯ kubectl exec -i -t dnsutils -- nslookup google.com
Server:	<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

** server can't find google.com: NXDOMAIN

But host.k3d.internal is working just fine (which means coredns is doing it's thing):
❯ kubectl exec -i -t dnsutils -- nslookup host.k3d.internal
Server:	<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Name:	host.k3d.internal
Address: <IP_ADDRESS>

How to "fix" the Problem:
After a bunch of try and error (because i really don't know coredns that well). It turned out that the problem seams to be rooted inside the coredns configuration. When I remove the file-plugin inside the coredns-custom-ConfigMap it is working again:

Proof it does not work

❯ kubectl exec -i -t dnsutils -- nslookup google.com
Server:	<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

** server can't find google.com: NXDOMAIN

command terminated with exit code 1

Check coredns-custom ConfigMap with file-plugin

❯ kubectl -n kube-system describe cm coredns-custom
Name:         coredns-custom
Namespace:    kube-system
Labels:       objectset.rio.cattle.io/hash=a3e4960ef9f39950a366d81f48be07a01f218c1e
Annotations:  objectset.rio.cattle.io/applied:
                H4sIAAAAAAAA/4yPQevTQBBHv8oy52SzaWpsAoJ/PImoB8GTl8nuJF2TzJSdbURKv7sERQSp/o/D8Hu8dwO8xM+UNApDD1sNBQTMCP0NMISYozAuZWC1YYAeXpumdc68/WA+fXwyaJ...
              objectset.rio.cattle.io/id:
              objectset.rio.cattle.io/owner-gvk: k3s.cattle.io/v1, Kind=Addon
              objectset.rio.cattle.io/owner-name: coredns-custom
              objectset.rio.cattle.io/owner-namespace: kube-system

Data
====
additional-dns.db:
----
@ 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com.<PHONE_NUMBER> 1800 900<PHONE_NUMBER>0
host.k3d.internal IN A <IP_ADDRESS>
k3d-test-server-0 IN A <IP_ADDRESS>
k3d-test-serverlb IN A <IP_ADDRESS>

hosts.override:
----
file /etc/coredns/custom/additional-dns.db

BinaryData
====

Events:  <none>

Edit coredns-custom ConfigMap and comment-out the file-plugin

❯ kubectl -n kube-system edit cm coredns-custom
configmap/coredns-custom edited

Proof file-plugin is commented-out in coredns-custom configmap

❯ kubectl -n kube-system describe cm coredns-custom
Name:         coredns-custom
Namespace:    kube-system
Labels:       objectset.rio.cattle.io/hash=a3e4960ef9f39950a366d81f48be07a01f218c1e
Annotations:  objectset.rio.cattle.io/applied:
                H4sIAAAAAAAA/4yPQevTQBBHv8oy52SzaWpsAoJ/PImoB8GTl8nuJF2TzJSdbURKv7sERQSp/o/D8Hu8dwO8xM+UNApDD1sNBQTMCP0NMISYozAuZWC1YYAeXpumdc68/WA+fXwyaJ...
              objectset.rio.cattle.io/id:
              objectset.rio.cattle.io/owner-gvk: k3s.cattle.io/v1, Kind=Addon
              objectset.rio.cattle.io/owner-name: coredns-custom
              objectset.rio.cattle.io/owner-namespace: kube-system

Data
====
additional-dns.db:
----
@ 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com.<PHONE_NUMBER> 1800 900<PHONE_NUMBER>0
host.k3d.internal IN A <IP_ADDRESS>
k3d-test-server-0 IN A <IP_ADDRESS>
k3d-test-serverlb IN A <IP_ADDRESS>

hosts.override:
----
#file /etc/coredns/custom/additional-dns.db

BinaryData
====

Events:  <none>

Restart CoreDNS

❯ kubectl -n kube-system rollout restart deployment coredns
deployment.apps/coredns restarted

Test Again (working)

❯ kubectl exec -i -t dnsutils -- nslookup google.com
Server:	<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Non-authoritative answer:
Name:	google.com
Address: <IP_ADDRESS>

How to Reproduce:

Create new Cluster

❯ k3d cluster create test
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-test'
INFO[0000] Created image volume k3d-test-images
INFO[0000] Starting new tools node...
INFO[0000] Starting node 'k3d-test-tools'
INFO[0001] Creating node 'k3d-test-server-0'
INFO[0001] Creating LoadBalancer 'k3d-test-serverlb'
INFO[0001] Using the k3d-tools node to gather environment information
INFO[0001] HostIP: using network gateway <IP_ADDRESS> address
INFO[0001] Starting cluster 'test'
INFO[0001] Starting servers...
INFO[0001] Starting node 'k3d-test-server-0'
INFO[0005] All agents already running.
INFO[0005] Starting helpers...
INFO[0005] Starting node 'k3d-test-serverlb'
INFO[0011] Injecting records for hostAliases (incl. host.k3d.internal) and for 2 network members into CoreDNS configmap...
INFO[0013] Cluster 'test' created successfully!
INFO[0013] You can now use it like this:
kubectl cluster-info

2.Create POD with DNS-Utils (for Testing)
❯ kubectl apply -f https://k8s.io/examples/admin/dns/dnsutils.yaml
pod/dnsutils created

3.1. Lookup google.com using nslookup inside dnsutils-pod:
❯ kubectl exec -i -t dnsutils -- nslookup google.com
Server:	<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

** server can't find google.com: NXDOMAIN

3.2. Lookup host.k3d.internal using nslookup inside dnsutils-pod:
❯ kubectl exec -i -t dnsutils -- nslookup host.k3d.internal
Server:	<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Name:	host.k3d.internal
Address: <IP_ADDRESS>

Workaround:
As a workaround i've added the hosts from the zone-file inside coredns-custom configmap to the host-plugin inside coredns configmap:
❯ kubectl -n kube-system edit cm coredns
configmap/coredns edited

❯ kubectl -n kube-system describe cm coredns
Name:         coredns
Namespace:    kube-system
Labels:       objectset.rio.cattle.io/hash=bce283298811743a0386ab510f2f67ef74240c57
Annotations:  objectset.rio.cattle.io/applied:
                H4sIAAAAAAAA/4yQwWrzMBCEX0Xs2fEf20nsX9BDybH02lMva2kdq1Z2g6SkBJN3L8IUCiVtbyNGOzvfzoAn90IhOmHQcKmgAIsJQc+wl0CD8wQaSr1t1PzKSilFIUiIix4JfRoXHQ...
              objectset.rio.cattle.io/id:
              objectset.rio.cattle.io/owner-gvk: k3s.cattle.io/v1, Kind=Addon
              objectset.rio.cattle.io/owner-name: coredns
              objectset.rio.cattle.io/owner-namespace: kube-system

Data
====
Corefile:
----
.:53 {
    errors
    health
    ready
    kubernetes cluster.local in-addr.arpa ip6.arpa {
      pods insecure
      fallthrough in-addr.arpa ip6.arpa
    }
    hosts /etc/coredns/NodeHosts {
      ttl 60
      reload 15s
      fallthrough
    }
    prometheus :9153
    forward . /etc/resolv.conf
    cache 30
    loop
    reload
    loadbalance
    import /etc/coredns/custom/*.override
}
import /etc/coredns/custom/*.server

NodeHosts:
----
<IP_ADDRESS> k3d-test-server-0
<IP_ADDRESS> host.k3d.internal
<IP_ADDRESS> k3d-test-server-0
<IP_ADDRESS> k3d-test-serverlb

BinaryData
====

Events:  <none>

❯ kubectl -n kube-system rollout restart deployment coredns
deployment.apps/coredns restarted

❯ kubectl exec -i -t dnsutils -- nslookup google.com
Server:	<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Non-authoritative answer:
Name:	google.com
Address: <IP_ADDRESS>

❯ kubectl exec -i -t dnsutils -- nslookup host.k3d.internal
Server:	<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Name:	host.k3d.internal
Address: <IP_ADDRESS>

Hey :wave:
This was fixed (feature reverted) in v5.7.1 (see #1462)
If you think this is a different issue or you're still facing this with v5.7.1, feel free to reopen :+1:

Hey 👋 This was fixed (feature reverted) in v5.7.1 (see #1462)
If you think this is a different issue or you're still facing this with v5.7.1, feel free to reopen 👍

Thank you very much! I'll try again with the newer Version !
Sorry for the inconvenience!


Add resource IDs to ECS Cluster and Service models

This enhances metadata retrieval and it's more complete. We should do physical resource IDs for anything that supports CloudFormation at some point.
I found that Cluster uses name and Service uses ARNs looking at existing CFN stacks with those resources.

Coverage decreased (-0.08%) to 93.335% when pulling ddcfd445ee9740dfd7e15f3796f5015a9c3a3b75 on feature/ecs-cluster-and-service-physical-resource-ids into 51129f6ef3f25c9f53fafdbf86fd2f586c5f13e0 on master.

Thanks!


hard coded paths to data files

prevents user from calling main script from outside project directory
art@Wernstrom git % python3 sc2rf/sc2rf.py
Traceback (most recent call last):
  File "/Users/art/git/sc2rf/sc2rf.py", line 987, in <module>
    main()
  File "/Users/art/git/sc2rf/sc2rf.py", line 73, in main
    mappings = read_mappings('mapping.csv')
  File "/Users/art/git/sc2rf/sc2rf.py", line 875, in read_mappings
    with open(path, newline='') as csvfile:
FileNotFoundError: [Errno 2] No such file or directory: 'mapping.csv'

I'm currently working on this as part of lenaschimmel#3 in the resources branch.
It's mostly working, but since virus_properties.json is both a resource that's bundled with the program, and something the program can update itself, I still need to put it into a writable location. As soon as I fix this, I will merge that branch.


colors part 4

Should we merge this PR? What is the status of secondary color?

we need to merge this or a similar PR to be able to release since the colors are unfinished in the current version


Why are you so diao?

Why are you so diao? Why are you so diao? Why are you so diao? Why are you so diao? Why are you so diao?

Because I learned from you

Is tHiS RaTEd?

Is tHiS RaTEd?

Unfortunately..........................


Cannot apply global Settings.

I have a problem with confirming the global settings. I wanted to add a proxy (global). So I added the specific settings and pressed save. But all my collections did not use this proxy and ignored it. But when I use the settings for a single collection, it works. But there is no field for SSL/ TLS certification validation there. So my problem is that the global settings are not applied. Has anyone had the same problem? Is this a bug? I am using the Windows version and have tested version 1.1.0.

For me it is working. I tried out different combinations between global and collection level proxy. All settings are applied and used as configured.  In Release 1.1.1 nothing at this part was changed. But you could try to update to this version.

I think your are right. When 'global' is not set on collection level, as default nothing is set on collection level, then the global proxy is not taken. We have to change the order. First take the global config and then check if anything is set on collection level.
FYI: @helloanoop

@mirkogolze @helloanoop
I think this issue was fixed by PR #951 and should be closed


Ability to resize images

Hello I'm new using this app and I can't find a way to increase an image size on the template configuration, since it isn't really an "img" element on HTML, it's just an internal reference to an uploaded image...
I've even uploaded images with windows background size(!) and they show up very small...
Here's an example (Preview):

And a on a printed label.

Yes, the image has move a little to the right :) But we can see that the image is very, very small
I would like the image to almost fill all the cell.
How can that be achieved?

Hi @andrepetinga. Looks like this is an enhancement request. The image size on a label is set to have a maximum height of 25% of the label height.

Hi @andrepetinga. Looks like this is an enhancement request. The image size on a label is set to have a maximum height of 25% of the label height.

Hello @mgobat. Yes, it's a possible enhancement for the app :)
For now I managed a workaround. What I did was to place an image on our company website, on a public URL, and on the HTML what I did was a simple "img" tag using the "width" and "height" properties, so that I can set the size I want.

@andrepetinga, smart workaround!


unofficial-superset-snowflake

Adding a new repo for a Helm chart, for superset connected to Snowflake.

Hello, can you please approve this request ?

The Artifact Hub is another place you can list your repos. To do that, you login (or create an account), create an organization, and list your repository. You can link it to a user or organization.

The Helm Hub has been superseded by the Artifact Hub. Chart repositories should now be listed there. Closing this PR.


Implement metric charts as modules

Overview
Removed redundant R code.
Cleaned up shared JavaScript.
Implemented Widget_BarChart() & mod_BarChart_*().
Test Notes/Sample Code
In theory it should look almost identical to how it was (except now I'm showing thresholds where appropriate). You can deselect on Bar Chart and Time Series tabs on Metric Details (and those deselects are reflected everywhere else); before this fix deselecting didn't work.
Connected Issues

Closes #309.
Closes #310.

Working well on the bar chart, but the deselect on the time series chart isn't working for me.

It never has (see for example https://openrbqm.shinyapps.io/gsm-app/). As far as I can tell, the widget doesn't support... well darn, I think I can make it work, now that I think about it 🙃
Fixing!

@lauramaxwell Darnit, I can't get it to register a click event for deselect. It isn't that my click callback isn't updating things properly; I can't get it to call the clickCallback in that situation.
@samussiah I can't figure out what would cause this to not work. It feels like it's in the vicinity of rmb-viz/src/util/onClick.js line 7+; the selected point doesn't give an interaction icon on hover, so it doesn't think it's clickable at that time. It isn't a HUGE issue, but... should I file an issue over in rbm-viz? And can you help me figure out where to tell it that it's clickable?

@lauramaxwell Darnit, I can't get it to register a click event for deselect. It isn't that my click callback isn't updating things properly; I can't get it to call the clickCallback in that situation.
@samussiah I can't figure out what would cause this to not work. It feels like it's in the vicinity of rmb-viz/src/util/onClick.js line 7+; the selected point doesn't give an interaction icon on hover, so it doesn't think it's clickable at that time. It isn't a HUGE issue, but... should I file an issue over in rbm-viz? And can you help me figure out where to tell it that it's clickable?

I'm seeing the same thing - the highlighted point isn't responding to click events (issue 1).  The other nice-to-have is a aligning the time series update methods with the bar chart and scatter plot update methods: updateSelectedGroupIDs vs updateConfig (issue 2).

I'm seeing the same thing - the highlighted point isn't responding to click events (issue 1). The other nice-to-have is a aligning the time series update methods with the bar chart and scatter plot update methods: updateSelectedGroupIDs vs updateConfig (issue 2).

Excellent, yes! I have a special "If this method exists, use it, if this other method exists, use that" in the code I'm experimenting with.


Build out stub/example DOI minting service

We cannot guarantee which DOI minting authority an installation of DMPRoadmap would like to use so we will need to provide an example that developers can use to plug in their own service. These services can then be built as gems in a separate repo here for the DMPRoadmap organization.
A global config setting should be added to allow for this functionality to be enabled. It should be disabled by default.
Build an initializer that will configure these gems

see parent issue #2351

decided not to go the gem route so did not do a stub.


Website is down

The documentation website has been down for a little over a day

Back up now! Great project by the way, I have really enjoyed playing around with it.


Clarify the environments being installed to.

Adding cla: yes label, as the PR author is a googler at the time of this PR was created.


BOINC can't attach to account manager

Greetings! It's the third day of me trying to set up this repo to work in my K8S environment.
I've tried this repo along with some others and also made my own containers and deployments and nothing seems to work, so I resorted to asking here - hope this is OK.
I'm trying to connect to GRCPOOL.com account manager. Whenever I launch the deployment, I'm getting pretty standard error "boinc
15-Aug-2022 13:54:19 [---] This computer is not attached to any projects", even though I specified everything in the ENV:
        env:
        - name: BOINC_CMD_LINE_OPTIONS
          #value: "--acct_mgr attach https://www.grcpool.com $SECRET_USERNAME $SECRET_PASSWORD"
          value: "--join_acct_mgr https://www.grcpool.com $SECRET_USERNAME $SECRET_PASSWORD"

And set-up the secrets (BTW, your secret template says that there should be user's email, while it should be user login at least for GRCPOOL - don't know if this is a typo or if different pools work differently).
I've also tried different other containers and nothing really helped. If I manually try to attach the node after it started, I'm getting this:
root@boinc-deployment-68499f4b96-5bf5b:/# boinccmd --acct_mgr attach https://www.grcpool.com LOGIN PASSWORD
root@boinc-deployment-68499f4b96-5bf5b:/# boinccmd --acct_mgr sync
root@boinc-deployment-68499f4b96-5bf5b:/# boinccmd --acct_mgr info
Operation failed: unexpected XML tag or syntax

I've tried also adding port forwarding rules, load balancers and pretty everything I could think of. Could you help here a bit maybe @Pelirrojo ? Thanks!

Hello!
First of all, sorry for the delay in replying.
I'm afraid that with the versions that appear in the repository I didn't manage to link by the command to a project manager like https://www.grcpool.com or https://scienceunited.org/ in fact I actively participate in Science United and this was my interest.
That part was done manually through the GUI via web access with Guacamole.
If you finally manage to do it, I would also be interested.
I think it was related to the versions I was using, although the docker repository I use has been extensively updated and may already support that command.
Anyway, from the log you dump I think it's related to the local configuration files that Boinc generates, apparently they are not being formed correctly. This may be due to the fact that it does not manage the secrets properly. In my tests without kubernetes (with docker or docker-compose) I mounted this directory in the docker host to reuse it in successive executions. That also allowed me to debug/investigate bugs.
Best of luck and thanks!


Could not open apk file

My code:
const apkPath = './src/app.apk';
      await FileViewer.open(apkPath, {
        showOpenWithDialog: true,
        showAppsSuggestions: true,
      });

result:
[Error: Failed to find configured root that contains /src/app.apk]

Only absolute paths are accepted. You've given a relative path. And apk support is imperfect. It won't do anything when opening apk. But if there are multiple package installers in your device, it'll ask to choose one, and then you can install the apk.


Handle redirection and gateway certificates

Currently freerdp is not able to properly handle certificates if the connection requires more than one to succeed.
This can occur under the following circumstances:

Gateway is required
The session is redirected

TODOS:

Extend all APIs handling certificates to allow type of certificate to be set

#4754 fixes the issue for external certificate management.


Missing go run or go build example of generated code

https://github.com/google/wire/blob/79660af94317b9c466adc39f27f469f1079c779b/_tutorial/README.md?plain=1#L115
I think this step is a missing example of how to run or build the generated code. Also, it's not obvious that we need also to include the generated files when executing either go run or go build like go build main.go wire_gen.go.
I think adding an extra paragraph explaining how to run or build would be very useful & prevent frustration, especially for people new to go.
When following the steps, I think most people will set seeing the word Hi there! on the console to be the goal to verify that we get the same outcome as in the non-wire code.

Yeah, I think there is something missing in the instructions as well.  If I do go run main.go, I get...
# command-line-arguments
./main.go:77:12: undefined: InitializeEvent

doing go build first then it runs fine when using the built executable.

@troyatomic  you need to execute the wire command to generate the bindings.
https://github.com/google/wire/blob/main/_tutorial/README.md#using-wire-to-generate-code

I agree it would be good to add some documentation about this. I'm fairly new to Go, and this was not intuitive to me. Up till now, I've been running my project with go run cmd/myproject/myproject.go. However, after integrating with Wire and generating wire_gen.go, I get something like this when I run that command:
# command-line-arguments
cmd\myproject\myproject.go:16:21: undefined: InitializeMyType

The same thing happens with go build cmd/myproject/myproject.go. Being fairly new to Go, I didn't realize I could (or needed to) pass in multiple go files to go run or go build. I eventually figured out I could run it by switching to my project's cmd/myproject directory and then using go run ..
After that, I tried to run it from my project root directory using go run cmd/myproject/, but I was confused when I got the following error:
package cmd/myproject is not in GOROOT

Finally, I figured out I need to put ./ in front of the project directory to tell Go I'm trying to run that instead of an installed package: go run ./cmd/myproject/.
Anyway, all this is to say the documentation @cglotr is suggesting would have saved me some time and frustration.

Whoops, didn't notice till just now that @cglotr has a pull request out for this. 😅 Thanks, @cglotr!


SP-2082 - Track minor Go version on Docker Build #patch

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

Project coverage is 54.59%. Comparing base (a71207f) to head (e8f9827).
Report is 10 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #390   +/-   ##
=======================================
  Coverage   54.59%   54.59%
=======================================
  Files           4        4
  Lines         185      185
=======================================
  Hits          101      101
  Misses         72       72
  Partials       12       12

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


Failed to get an associated pull request

Hello, I've been using ci-info through tfaction. Since upgrading to ci-info v2.2.0, commenting on merged PRs has stopped working properly. I'm encountering the following error:

It might be noise, but I'll post the full actions log.
I've replaced the GitHub owner with OWNER and the repo with REPO, but they are filled with the actual values used.
It appears to be failing to retrieve a pull request like pulls/0.
We do not use a merge queue in this environment.

time="2024-07-14T04:38:43Z" level=info msg="download and unarchive the package" aqua_version=2.29.0 env=linux/amd64 exe_name=ci-info package_name=suzuki-shunsuke/ci-info package_version=v2.2.0 program=aqua registry=standard
time="2024-07-14T04:38:43Z" level=info msg="verify a package with slsa-verifier" aqua_version=2.29.0 env=linux/amd64 exe_name=ci-info package_name=suzuki-shunsuke/ci-info package_version=v2.2.0 program=aqua registry=standard
Verified signature against tlog entry index 111615261 at URL: https://rekor.sigstore.dev/api/v1/log/entries/24296fb24b8ad77a0751df7a540f50d9a599d57ee059426e5bbedc09e8116fdd4ab116ff05442c8d
Verified build using builder<EMAIL_ADDRESS>at commit 458eeb5db3c1eed805f98a6917da7e8c66f512a7
Verifying artifact /tmp/047521249: PASSED

PASSED: Verified SLSA provenance
time="2024-07-14T04:38:44Z" level=fatal msg="get an associated pull request: get a pull request: GET https://api.github.com/repos/OWNER/REPO/pulls/0: 404 Not Found []"

I will also look into the source code to investigate the cause, but I wanted to file this issue promptly.
Please feel free to mention if any additional information is needed or if it would be better to file this issue under the tfaction repository instead.

Thank you for your report!
I'll take a look.

https://github.com/suzuki-shunsuke/ci-info/pull/735

v2.2.1 is out 🎉
https://github.com/suzuki-shunsuke/ci-info/releases/tag/v2.2.1

Thank you! That was incredibly fast. I've confirmed that it works correctly with v2.2.1.


test(transormers): added initial transformer spec

Sorry for the very long absence and the tiny pull request.

No need to apologize! This is a huge help.


Custom metadata for attributes

Sean McGivern [5:08 PM]

I'd like to add a custom option to attributes of any type (in this case, it's whether the attribute is loggable)
it doesn't look like attributor supports any kind of custom metadata like this; is it something we'd like to add?

Josep Blanquer [6:01 PM]

ya, it doesn't have it right now, and yes, it is something we'd like to add
it'd be a well known option...something like... :metadata ... or :custom_data ...
which is a hash...it wouldn't be validated or understood....
but will allow you to add things in it
and at runtime would be retrievable through options[:custom_data] ...
and will also exist in the generated JSON docs
so anybody that knows how to interpret that would be able to

closed by #114


Publish on Accrescent store

Would you please consider publishing it on Accrescent; an alternative android app store?
See their guide: https://accrescent.app/docs/guide/getting-started/

I am currently working on publishing it to F-Droid. No plan to publish on other platform so far. Thank you for your suggestion and I may take it into consideration if I see the needs in future.


docs(whitepaper): update the section of Ledger Plugin (fixed)

This pull-request has already been approved as same as PR #322 .
After the approval, this file was returned to the previous version by another pull-request #298 by mistake, so I requested a correction.
Signed-off-by: Takuma TAKEUCHI<EMAIL_ADDRESS>

I'm sorry that I built my fork repository again due to some technical issue on GitHub and I cannot merge this pull-request.
Then, I made the same pull-request again (#326 ) . Would you mind if you approve PR #326 again?


Kickoff Meetings/Follow Up

Kickoff scheduled for 8/3/21.

8/3/21- Kickoff call completed. Notes here: https://drive.google.com/drive/folders/1BSenecfg4EviKKC3acvK-f-iq7hhWzQt
Follow up call scheduled for 8/4/21 with athenahealth contact to discuss next steps.

8/4/21 - athenahealth was not able to join the call.

8/12/21 - First attempt to set up follow up call with contact.
8/16/21 - Second attempt to set up follow up call.

8/18/21 - Met with contact to review report and current fields. She will send template to us.
8/23/21 - Met with contact to review outstanding reporting questions. She will send sample report today.

8/26/21 - Received signed TOS.


tjson: Port and sync unit testing approach from fjson to tjson

This task is a part of #683 epic.
🎯 The goal of the task is to port and sync  unit tests and testing approaches from fjson package to tjson package.
❗We don't add new data types in this ticket, we only port tests for the types presented and fully implemented in tjson:

[ ] double
[ ] string
[ ] bool
[ ] int32
[ ] int64

The two other implemented types - binary and object_id need special attention and will be covered in a separate task #900.
To Do:

[ ] Create the smallest possible PR containing all the necessary things for one data type first. Then add support for the rest of the types in further PRs.
[ ] Reuse fjson's testing approach - test, fuzz, benchmark in tjson. Adopt the idea by copying some implementation to tjson. The details will vary as tjson needs a schema that describes data types.
[ ] Copy fjson data types' test cases, so they can be used by tjson. Serialization results and some tjson specifics might be different.
[ ] The scope of this task is timeboxed and limited by the simplest cases. It's enough to provide an example of the future approach and describe what needs to be done later in separate issues.
[ ] It might make sense to have a look at the bson package too (in case there are some useful tests there).

@AlekSi please check the description. The task is ready for refinement/planning.


nodemon issue ? continually restarting?

seems to not play well with nodemon
when the app is started it keeps continually restarting /  regenerating the db
i've tried both
var db = new Datastore({   filename: 'database.json',   autoload: true });
and
db.loadDatabase();
to load the db, same for both.

It's going to do that... Your database file is changing whenever you use
it...
On Apr 18, 2016 17:56, "Andy"<EMAIL_ADDRESS>wrote:

seems to not play well with nodemon
when the app is started it keeps continually restarting / regenerating the
db
i've tried both
var db = new Datastore({
filename: 'database.json',
autoload: true
});
and
db.loadDatabase();
to load the db, same for both.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/louischatriot/nedb/issues/409

As well as its creating a backup of the filestore (same filename as your
filestore with a ~ at the end).
On Apr 21, 2016 09:35, "Brian Foster"<EMAIL_ADDRESS>wrote:

It's going to do that... Your database file is changing whenever you use
it...
On Apr 18, 2016 17:56, "Andy"<EMAIL_ADDRESS>wrote:

seems to not play well with nodemon
when the app is started it keeps continually restarting / regenerating
the db
i've tried both
var db = new Datastore({
filename: 'database.json',
autoload: true
});
and
db.loadDatabase();
to load the db, same for both.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/louischatriot/nedb/issues/409

Yes you need to have nodemon ignore the datafile or the data directory.

ok, thanks