[🚀esl-share]: consider esl-share-button custom element API rework

As an ESL Share consumer, I want transparent esl-share module sub-APIs.
It is requested to rethink the esl-share-button component API to resolve the following concerns (inconsistencies):
esl-share-button marked as public and mentioned in the doc to be used separately as a low-level API

on practice: the component cannot be used without ESLShareConfig provided, which means that the consumer will face an inconsistency in component role and usage
on practice: the button component does not look to be helpful for the consumer as it is required to declare all attributes manually (independently of ESlShareConfig)

It is proposed to provide the ability to pass just an action name from the ESLShareConfig to make the share button work. It is also proposed to update the availability check to make a decision from the merged version (from config + custom properties on the button itself)

:tada: This issue has been resolved in version 4.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[BUG, Crash] Tab crashed without user interactions (BreakPoint reached in RenderFrameImpl)

Desktop

OS: [happened on WinXP], touches any OS (I think).
https://github.com/win32ss/supermium/releases/tag/v122-hf

Describe the bug
breakpoint in the code, leaved here for development stage, reached. As result, Tab was crashed. (see screenshots)
Additional context
The Google Translate tab was open. I'm worked with it.
Then I switched to work with other programs.
When I returned, I saw that the tab was crashed.
So it was happened without any useractions.
Screenshots
Here screenshots of result tab crash, and info which will help to fix it.

UPD: the same breakpoint on same tab was reached again, after I switched to other programs and returned back. New crashdump occured :)

If it's OK for Android, then it may be OK for Windows as well. I will remove this check.

fixed in today debug ver I think. Not occured yet. Im not seen updated source codes, dev not updated it.


sample RefreshTokenHandler

What is the purpose of the RefreshTokenHandler? Should I expect something like refreshing the access token when it is expired using the refreshtoken?

That's the idea - yes.

But how should I use this function? any sample? i don't see any validation of the expire date time in this handler.

It's a handler for an HttpClient.

No expiration check needed - when a 401 is returned - that means the token is invalid.


Failure to bump complex version tag.

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
Docker
dependabot.yml content
version: 2
updates:
  - package-ecosystem: "docker"
    directory: "/"
    schedule:
      interval: "daily"
    ignore:
      - dependency-name: "*"
        update-types: ["version-update:semver-major"]

What you expected to see, versus what you actually saw
Expected:
Both Ruby and Alpine versions are bumped to the latest, without affecting major release:
from 3.1.1-alpine3.15 to 3.1.3-alpine3.17
Actual Outcome:
Ruby version is bumped, but alpine version remains the same:
from 3.1.1-alpine3.15 to 3.1.3-alpine3.15
Could the Alpine tag be being ignored as it is not in full semver version format?
Smallest manifest that reproduces the issue
FROM ruby:3.1.1-alpine3.15 as base1

I think this is a duplicate of https://github.com/dependabot/dependabot-core/issues/5708, although you are reporting slightly different symptoms 🤔.


please add new tab open

Thanks for your feedback @niksooo7, we have started working on it. Keep an eye on our updates.

Duplicate https://github.com/duckduckgo/Android/issues/157


Tooltip does not close when clicked again

These 2 lines after if(_this.isClick) are commented out. Uncommenting them fixes the issue.
    if (this.options.clickOpen) {
        this.$element.on('mousedown.zf.tooltip', function (e) {
          e.stopImmediatePropagation();
          if (_this.isClick) {
            // _this.hide();
            // _this.isClick = false;
          } else {
            _this.isClick = true;
            if ((_this.options.disableHover || !_this.$element.attr('tabindex')) && !_this.isActive) {
              _this.show();
            }
          }
        });
      } else {
        this.$element.on('mousedown.zf.tooltip', function (e) {
          e.stopImmediatePropagation();
          _this.isClick = true;
        });
      }

How to reproduce this bug:

Step one
Create a tooltip with clickOpen option true
Step two
Click the button to open tooltip
Step three
Click the button again

What should happen:
Tooltip should close
What happened instead:
Tooltip remains open
Foundation Version(s) you are using:
6.4.3

The change was in (https://github.com/zurb/foundation-sites/pull/8730). I disagree with this new behavior, finding it unintuitive, but I see that it was thought out and intentional.


Merlin picks gpu0 even when taken

I recently installed a second GPU in our machine and in .theanorc I have set device=cuda. When I just run python and then import theano it picks whichever gpu is available. However, Merlin seems to only want to take gpu0 and when it is already taken, the process terminates with an error message:
File "/home/esther/merlin/src/run_merlin.py", line 55, in
import theano
File "/usr/local/anaconda/lib/python2.7/site-packages/theano/init.py", line 116, in
theano.sandbox.cuda.tests.test_driver.test_nvidia_driver1()
File "/usr/local/anaconda/lib/python2.7/site-packages/theano/sandbox/cuda/tests/test_driver.py", line 30, in test_nvidia_driver1
A = cuda.shared_constructor(a)
File "/usr/local/anaconda/lib/python2.7/site-packages/theano/sandbox/cuda/var.py", line 166, in float32_shared_constructor
enable_cuda=False)
File "/usr/local/anaconda/lib/python2.7/site-packages/theano/sandbox/cuda/init.py", line 589, in use
gpu_init(use.device_number, config.lib.cnmem)
RuntimeError: ('initCnmem: cnmemInit call failed! Reason=CNMEM_STATUS_OUT_OF_MEMORY. numdev=1\n', 'You asked to force this device and it failed. No fallback to the cpu or other gpu device.')

I don't know the exact reason.. Maybe this part of code always picking the gpu0 https://github.com/CSTR-Edinburgh/merlin/blob/master/egs/slt_arctic/s1/scripts/submit.sh#L12L18

You are right, it was hardcoded in there. I have taken it out for my scripts.


Dockerize

Create a Dockerfile to serve the webfrontend from #2 .

Hi is this available for hacktoberfest could you please assign it to me.

Sure, but atm it is blocked by #2.
Additional info:

I want this to be based on opensuse
I want this to include an arm32v7 build like I am using in my autobuilds: https://github.com/dragonchaser/dockerhub-autobuild/
(if opensuse becomes a blocker at this point debian is also fine)

This is unblocked now. Are you still up for it @Deepeshac2890 ?

Hey,
Sure I would like to learn as I have very less exp. I want to gain exp by
working on this project.
On Thu, 8 Oct, 2020, 4:03 pm Christian Richter<EMAIL_ADDRESS>wrote:

This is unblocked now. Are you still up for it @Deepeshac2890
https://github.com/Deepeshac2890 ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dragonchaser/maptool/issues/3#issuecomment-705482619,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM3KDLR3FAUBJZCVJK5QQ5TSJWIOLANCNFSM4R4FPBFQ
.

Go ahead :) ping me if you need help.

Can you please send me the link of the issue?
On Thu, 8 Oct, 2020, 4:49 pm Christian Richter<EMAIL_ADDRESS>wrote:

Go ahead :) ping me if you need help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dragonchaser/maptool/issues/3#issuecomment-705503411,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM3KDLSYWR7EDHSM7A3IUSDSJWN4DANCNFSM4R4FPBFQ
.

This page?

Actually I am replying from Gmail so I don't have link to the issue's page
😅😅
On Thu, 8 Oct, 2020, 4:52 pm Christian Richter<EMAIL_ADDRESS>wrote:

This page?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dragonchaser/maptool/issues/3#issuecomment-705504535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM3KDLWSFYIVNXGV4GWSDFTSJWOFTANCNFSM4R4FPBFQ
.


Improve fixed-point tangent calculation for division-less operations and accuracy

When calculating the twin_tan(), division is used, specifically $\frac{\sin x}{\cos x}$
// twin_tan()
return ((s << 15) / c) << 1;

To minimize the use of the division operator, you can refer to the division implementation mentioned in https://hackmd.io/@sysprog/linux-intdiv, which describes the implementation in jemalloc to avoid direct use of the division operator.
Currently, testing and experimental data are needed to confirm that using this division method in twin_tan within mado can achieve faster calculation times.
As for the other issue, it's whether twin_tan can be improved further, including enhancements in precision and calculation speed.
Perhaps coordinate rotation digital computer(CORDIC) cloud be a solution.
The note here provide a quick overview of the mathematical principles behind conventional CORDIC and scaling-free CORDIC.
Reference:

https://hackmd.io/@sysprog/linux-intdiv
https://github.com/Max-Gulda/Cordic-Math
https://hackmd.io/@jouae/mado_trig

An array architecture for fast computation of discrete Hartley transform by A. S. Dhar and S. Banerjee, 1991, mentions the use of small-angle approximations for sine and cosine functions to compensate for the need for a scaling factor $K$.
In the method, a magic number $(p−2.852)/3$ is referenced, where this magic number imposes the restriction that the number of bits shifted in the iteration $j$ must be greater than $\left\lceil \frac{p-2.585}{3} \right\rceil$.
This magic number is derived from the error estimation obtained from the remainder terms of the Taylor series approximation for sine and cosine functions. If the initial number of shifted bits $j$ does not exceed this magic number, the result of the approximation will not be accurate.
The detailed derivation process is recorded in the note: Scaling-free method of CORDIC.


fix: wrong postgres env vars for deployment templates

WHAT
Fixes the environment variables in some deployment templates where the wrong postgres creds values were used.
WHY
Helm Charts currently unusable.
FURTHER NOTES
Closes #463

Hi @ayhanmesin-zf
thanks for your contribution please sign the eca

Done


COMPONENTS (request): Editable DataTable

Re DataTable component

The existing DataTable component is fairly comprehensive, yet there is a strong use case for editable tables, a pattern used across many web apps for tabularly managing data, including spreadsheets (e.g. Google Sheets, AirTable), PM software (e.g. Linear, Notion), and more.
Here is an example from TanStack: https://tanstack.com/table/v8/docs/examples/react/editable-data
It doesn't look great, aesthetically, but it works functionally similarly to what I am proposing, where each cell is directly editable. I will be using this pattern on an upcoming project, and syncing changes in the table to my database.

@brandonmcconnell did you end up implementing this for your project?

Yes, but all custom. Would still love to see this implemented into shadcn natively

@mkandan Yes, but all custom. Would still love to see this implemented into shadcn natively

@brandonmcconnell what was your approach / any tips? Would like to do this as well and but wouldn't I love to save time haha 👀

Basically created an input inside every single cell of the DataTable component bound to something in my database. Some were plain inputs, some dropdowns, etc. Hope that helps 🙂

an input inside every single cell of the DataTable component

Just making sure I understand the logic: were you

by default, hiding the input and showing text of the data's value
if user clicks, make the data value editable inside of the now visible input/text area?

or permanently making an input visible and usable inside of each cell?

@mkandan I made it permanently an input and simply made them readonly when needed, bit it could be even nicer to do it the way you're saying, flattening them to plain text when not in use.

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


fix(handler): Don't export makeResponse, getAcceptableMediaType or isResponse

I don't expect this to be a breaking change because its very undocumented, not known and therefore (I think) unused.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Detect circular dependency and panic

Which one do you prefer to be implenmented first: runtime check or static check?
If later, I think we may need a extra tool because there is less support for compiling code in Golang.

I would prioritize a runtime check, since the services can be invoked/replaced in a dynamic way.
And as you said, we won't need an extra tool.
This dependency graph should come with debug functions, in order to understand how the application is booted !

LGTM, I will do a detector in runtime.

Will be added into v2 -> #45


fix: logout confirmation messages

What does this PR do?
fix logout confirmation messages
What issues does this PR fix or reference?
https://github.com/forcedotcom/cli/issues/2671
@W-14903300@

QA notes:
✅  single user:
before:
sf org logout --target-org <user>
? Are you sure you want to log out of all your orgs? no
No orgs selected for logout.

after:
sf org logout --target-org <user>
? Are you sure you want to log out of <user>? (y/N)
No orgs selected for logout.

same when running sf org logout and selecting a username from the prompt.


fixfix minio default region and throw minio error msg, support s3 bucket root path

Proposed changes

check minio region, set default region if user region is not provided, and throw minio error msg
support read root path s3://bucket1
fix max compute public access

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.5 seconds
stream load tsv:          505 seconds loaded<PHONE_NUMBER>9 Bytes, about 141 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          29.8 seconds inserted 10000000 Rows, about 335K ops/s
storage size:<PHONE_NUMBER>7 Bytes

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 44.65 seconds
stream load tsv:          501 seconds loaded<PHONE_NUMBER>9 Bytes, about 142 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          28.7 seconds inserted 10000000 Rows, about 348K ops/s
storage size:<PHONE_NUMBER>5 Bytes

run buildall


Linker fail on linux

During the final link step, the following error occurs:
  = note: /usr/bin/ld: cannot find -lxcb-shape
          /usr/bin/ld: cannot find -lxcb-xfixes
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

On Debian/Ubuntu, this is fixed installing the packages libxcb-xfixes0-dev and libxcb-shape0-dev. Coming from C++ this is strange to me (you'd imagine you need the headers to compile, not to link). Anyway, the error message is unclear.

Coming from C++ this is strange to me (you'd imagine you need the headers to compile, not to link).

The -dev packages include not just headers but also the symlinks necessary for the linker to find libraries.

Anyway, the error message is unclear.

Maybe rustc could try to give a somewhat better error message when it finds this kind of linker error, but it would be impossible to always correctly guess the right package name for a library especially across different distros.

I am on Ubuntu 20.04 and needed to install the following packages libxcb-shape0-dev libxcb-xfixes0-dev libxcb-render0-dev libxkbcommon-dev. Perhaps, it is worth adding to the README.

Hi and thanks for reporting this issue! I'm going to close this as a duplicate of #3 for now, as I think this is more related to unclear build instructions than any other technical problem. Other than that, general linker errors, and the clarity of compiler/linker error messages are I think out of scope for this project.
If you have a definite set of packages that you need to install on your OS, feel free to open a PR that adds it to the readme, and reference #3 in that PR. Thank you!


Feature: functionality to enable filtering of repositories according to programming languages they comprise of

Type of feature
🍕 Feature
Current behavior
When the page loads you see repositories and a filter field for filtering according to repositories titles.  The information displayed regarding the repositories don't show the programming language used in them, neither is there a way of filtering them according to one or more programming languages.
Suggested solution
In addition to the "filter according to title "  field, there should be a series of checkboxes labeled according to the programming languages used in the repositories being loaded. When none of them are checked, all the repositories will be as is. As a language is checked, the repository listing is filtered according to checked programming languages.
Additional context
No response
Code of Conduct

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

Contributing Docs

[X] I agree to follow this project's Contribution Docs

Would you assign me to this issue? I want to work on this feature.

Hey, I wanted to to work on this issue could some please assign?

.take


[TFLite][Frontend] Support quantized less

Support LESS quantization operation as part of #15148

I wonder why my new commits will be added to original successful PR. That means I have to create new PR after it is merged?

Maybe I made a mistake. But I hope the successful version can be merged. @lhutton1 @leandron

Hope you can merge my right approved version and ignore all my new version. @lhutton1  @leandron


[Dialog]: mobile browser scroll unlock

Describe the bug
Mobile browser scroll unlock
To Reproduce
Steps to reproduce the behavior:

Use mobile browser to https://www.radix-vue.com/components/dialog.html
Open dialog. Scroll unlocked

Expected behavior
Scroll will be locked
Screenshots
https://github.com/radix-vue/radix-vue/assets/40693636/4df83801-c0e4-42bd-bd8a-2cf3f34881b3
Smartphone (please complete the following information):

Device: iPhone
Browser Chrome

Desktop (please complete the following information)

OS: MacOS 13.4.1
Browser: safari
Version 16.5.2 (186<IP_ADDRESS>.10)

Also have the same problem, not sure if it's a safari problem.

thanks! we'll look into it!

closed with #265


Bad handshake, unexpected EOF

Can't create new certs and the verbose mode and DEBUG didn't help.
Is there anyone encountering this?

https://answers.atlassian.com/questions/32508806/sslerror-bad-handshake-syscallerror-1-unexpected-eof-when-creating-jira-object-on-python
https://community.letsencrypt.org/t/certbot-sslerror/28687

I was maybe getting a similar error:
2017-03-09 04:38:21,763:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/simp_le.py", line 1401, in main
    return main_with_exceptions(cli_args)
  File "build/bdist.linux-x86_64/egg/simp_le.py", line 1386, in main_with_exceptions
    persist_new_data(args, existing_data)
  File "build/bdist.linux-x86_64/egg/simp_le.py", line 1282, in persist_new_data
    client = registered_client(args, existing_data.account_key)
  File "build/bdist.linux-x86_64/egg/simp_le.py", line 1224, in registered_client
    client = acme_client.Client(directory=args.server, key=key, net=net)
  File "build/bdist.linux-x86_64/egg/acme/client.py", line 63, in __init__
    self.net.get(directory).json())
  File "build/bdist.linux-x86_64/egg/acme/messages.py", line 169, in from_json
    raise jose.DeserializationError(str(error))
DeserializationError: Deserialization error: Wrong directory fields

I had been running a slightly out-of-date version, though, so I updated my containers to the newest stable versions (v1.4 of this companion, alongside docker-gen 0.7.3 and nginx 1:11).  After updating my containers to newer versions, I'm getting this error:
Creating/renewal mydomain.example certificates... (mydomain.example)
2017-03-09 04:49:58,832:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
2017-03-09 04:49:59,509:INFO:requests.packages.urllib3.connectionpool:242: Resetting dropped connection: acme-v01.api.letsencrypt.org
2017-03-09 04:49:59,879:INFO:requests.packages.urllib3.connectionpool:207: Starting new HTTP connection (1): mydomain.example
2017-03-09 04:49:59,940:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): mydomain.example
2017-03-09 04:50:00,119:ERROR:acme.challenges:256: Unable to reach http://mydomain.example/.well-known/acme-challenge/BIGLONGCHALLENGESTRING: ("bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')],)",)
2017-03-09 04:50:00,120:WARNING:simp_le:1303: mydomain.example was not successfully self-verified. CA is likely to fail as well!
2017-03-09 04:50:00,312:INFO:simp_le:1313: Generating new certificate private key
2017-03-09 04:50:03,618:ERROR:simp_le:1271: CA marked some of the authorizations as invalid, which likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in -d example.com:path or --default_root? Is there a warning log entry about unsuccessful self-verification? Are all your domains accessible from the internet? Failing authorizations: https://acme-v01.api.letsencrypt.org/acme/authz/BIGLONGAUTHSTRING


Incorporate drywall in existing node SPA

Objective:
I want to integrate my website dashboard with drywall.
Scenario:
Our dashboard SPA is built on node + express + angular + embeddedjs + mongoDB.
We use the command `grunt live' to run the  dashboard SPA.
Our code:
https://github.com/webFaclon/faclon_website
Problems:
1:
How to integrate drywall in our dashboard SPA and run both on one server alongside MongoDB.
2:
The dashboard SPA uses embeddedJS as the view model whereas, drywall uses Jade (pug), will there be any conflicts? or this would work > Stackoverflow: Using multiple view engines

+1 I'm wondering if you could suggest what components can be wrapped in angular directives (if att all). thanks!

Thanks for opening an issue. Here are a couple relevant issues:

Drywall was built as a boilerplate/starter. You start with Drywall and build up on it. So I'm not sure if you're use case aligns with the intended use. I may be misinterpreting what you're going after so feel free to clarify your goals.

Via: https://github.com/jedireza/drywall/issues/305

I haven't used Angular myself. Frame is the core Drywall API using Hapi instead of Express. I know that @Silom was working on creating an Angular front-end to it. https://github.com/Silom/ngFrame

Via: https://github.com/jedireza/drywall/issues/290

1: How to integrate drywall in our dashboard SPA and run both on one server alongside MongoDB.

This isn't impossible, you do have to do the work merging the two projects together though. There isn't a general-solution/best-practice here.

2: The dashboard SPA uses embeddedJS as the view model whereas, drywall uses Jade (pug), will there be any conflicts? or this would work > Stackoverflow: Using multiple view engines

Although I don't typically have two template engines in a project, I'm sure there are ways to accomplish this. Again, comes down to finding a solution you feel good maintaining.

+1 I'm wondering if you could suggest what components can be wrapped in angular directives (if att all). thanks!

I don't use Angular myself. It may be worth checking out https://github.com/Silom/ngFrame

Check this project: https://github.com/arthurkao/angular-drywall
This is fork of Drywall


Radiogroup answer not selected when there is a second radiogroup with two visible-if's

Are you requesting a feature, reporting a bug or asking a question?
bug
What is the current behavior?
With the code below, the visible answer is not selected.
What is the expected behavior?
I expect the answer to be selected.
How would you reproduce the current behavior (if this is a bug)?
I made a plunker that reproduces this behavior
Provide the test code and the tested page URL (if applicable)
Tested page URL:
https://plnkr.co/edit/qoKCmUBes5nprkvTD3Oy?p=preview
Test code
Survey
    .StylesManager
    .applyTheme("default");

var json = {
    "questions": [
        {
            "type": "radiogroup",
            "name": "group1",
            "valueName": "question1",
            "choices": [
                {
                    "value": "answer_possibility_1",
                    "visibleIf": "{other_question} = \"1\"" // If this line is removed value is selected
                },
                {
                    "value": "answer_possibility_2",
                    "visibleIf": "{other_question} = \"2\"" // If this line is removed value is selected
                }
            ],
            "visibleIf": "{another_question} = \"whatever\""
        },
        {
            "type": "radiogroup",
            "name": "group2",
            "valueName": "question1",
            "choices": [
                {
                    "value": "value_should_be_selected" // (but it is not)
                }
            ]
        }
    ]
};

window.survey = new Survey.Model(json);
window.survey.data = {
    "other_question": "2",
    "another_question": "blah",
    "question1": "value_should_be_selected"
};

survey
    .onComplete
    .add(function (result) {
        document
            .querySelector('#surveyResult')
            .innerHTML = "result: " + JSON.stringify(result.data);
    });

$("#surveyElement").Survey({model: survey});

Specify your

browser: chrome (latest)
browser version:
surveyjs platform (angular or react or jquery or knockout or vue): jquery
surveyjs version: 1.50

See https://surveyjs.answerdesk.io/ticket/details/T1239

The bug has been fixed with this commit: https://github.com/surveyjs/surveyjs/commit/36aae56d98449c90de7fbaf570b8a5dcaf2b700d
Released in the v1.0.52


Inject CSP headers into proxied UIs

As discussed on Skype: it seems like at some point (maybe when we weeded out http-proxy-middleware) CSP headers were no longer being injected into proxied UIs. It could also be that I took them out for debug and never put them back in (if it was in the LiveScript days, then the comments wouldn't have been compiled to JS).
So we'll need that again to guarantee that dashboard UIs don't request external resources client-side. IIRC, it should be enough to just set the default-src directive to 'self' for now, and then later on we can do fancier things like have the browser report attempted breaches back to the platform through the report-uri directive. That's kind of cool for papers too, since we would be using something that was designed for detecting bugs to instead enforce accountability.

I will do some investigation but I think with CSP we have to trust the browser, and I'm not sure I do ;-)


Create B1 TASK

NODE ID : a18481342f9cfe73

rejected:B1
It looks like you are trying to submit B1, however it seems like the following submission criteria are problematic:

Logs are missing
We’ve thus marked B1 as rejected, however if this is a mistake, please upload the log summary and we can re-review.

confirmed:B4
address:4t3HeXcJuG4YuZK7WbPLZbvsm6QgB1u2Rmvs6u9ESsHeiEAcWf
baker:547

confirmed:B4
address:4t3HeXcJuG4YuZK7WbPLZbvsm6QgB1u2Rmvs6u9ESsHeiEAcWf
baker:547


ERROR: Memory: bad allocation size -18783732 bytes

So, uh, just downloaded the tool, ran it from the directory the upk file is in, selected the file, clicked export, and then this happened. What am I doing wrong/how could I fix it so I can extract the upk? Is it because the game isn't supported? If so, I should find out the version of UDK it uses and then try again?

Memory: bad allocation size -18783732 bytes
appMalloc:size=-18783732 (total=6 Mbytes) <- FArray::Empty:1072176513 x 12 <- SerializePackageFileSummary3 <- FPackageFileSummary<<:Ver=687/115 <- UnPackage::UnPackage:DD2_SpookyForest02.upk, ver=687/115, game=8000 <- UnPackage::LoadPackage:DD2_SpookyForest02.upk <- CUmodelApp::ShowPackageUI <- Main:umodel_version=553

(If this isn't a real issue, my bad, and please point me in the right direction to a place where I can get my question answered)

What's the game?

I think this is Dungeon Defenders 2, isn't it?
http://www.gildor.org/smf/index.php/topic,2648.0.html
The recent version of this game is not supported.

Yup, that is the game. Because it isn't supported, does that mean there is no way to unpack those files?

UModel worked with older version of this game. New version is not supported, so you can't use UModel to extract or view content.
Just for your information: version could be found in log, in your first message it is "ver=687/115".

Oh well. In any case, thanks for your help!


node.js grpc doesn't handle oneof field properly

I am having several issues with message types containing oneof fields. I have attached an example that is derived from the greeter example code. I have added a oneof field to the request that contains an A and a B message within the oneof. When I create the A message only(without enclosing it in a oneof of the HelloRequest) and send it, it works. However, I then send a B message in the same manner and it encounters an exception during serialization. The interesting thing to point out is that if I change the order of the elements of the oneof in the proto file to B and then A, the B request will be successful.
greeter_client.js.txt
greeter_server.js.txt
helloworld.proto.txt
If I change the example such that I use the HelloRequest, I get another exception indicating the alt field is undefined. I am using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>on ubuntu 14.04.

It seems like the problem here is with protobuf serialization. I would suggest posting an issue at https://github.com/google/protobuf

Thanks - I will do that. The reason I posted here first is that encoding the messages via .encode() seems to work fine so perhaps its related to grpc method of using protobufjs.
\

Here is the example showing that protobuf seems to handle oneof properly.
greeter_client.js.txt
I think this is a valid grpc problem.

It's interesting that the message's .encode() method works. What happens if you call the .serializeBinary() method? That's the one that gRPC uses in the serializer.

@angrbrd Are you sure that the msg object you have is a protobuf message object of the type that the google-protobuf library exposes?

The crash I am seeing is in MessagePrototype.set. Here's the snippet causing it:
var field = T._fieldsByName[keyOrObj];
if (!noAssert) {
if (!field)
throw Error(this+"#"+keyOrObj+" is not a field: undefined");
The problem is either the oneof field should be mapped in the T._fieldsByName or there should be appropriate logic to avoid and skip the checks inside the !noAssert conditional. I hacked a version to avoid the checks and it works. Unfortunately, I can't seem to find a decent way to check that the field is a oneof.

Are you seeing that crash when you call the message's .serializeBinary() method? If so, you should bring this issue to the google/protobuf repo.

I'm having the same issues trying that as angrbrd, generally unfamiliar with using the serializeBinary and haven't been able to find a simple example of using it. Does it require me to statically generate the grpc code?

I just realized that I missed something when I originally read your example code. You are using grpc.load, which means that you are using the built-in Protobuf.js code generation. But that also means that you don't need to (and shouldn't) explicitly construct message objects. You should just create regular objects with the right structure. For example, you can do
var h = {a: {foo: user}};
var bh = {b: {bar: user}};

I have tried that as well and it still crashes - will post that crash next.

Hi @murgatroid99
Thanks for your response. I am using the .serializeBinary() method on a protobuf message object. And when I do so, this is the crash that I observe. I am attaching both server and client code here as well as the .proto file.
helloworld2.proto.txt
greeter_client_v2.js.txt
greeter_server_v2.js.txt
Initializing gRPC client...
empty request A = {"alt":null,"a":null,"b":null}
msgA = {"foo":"ANGRBRD"}
filled request A = {"alt":"a","a":{"foo":"ANGRBRD"},"b":null}
requestADecoded = {"alt":"a","a":{"foo":"ANGRBRD"},"b":null}
/Users/anya/dev/node/grpc/examples/node/dynamic_codegen/greeter_client_v2.js:69
  var requestASerialized = requestA.serializeBinary();
                                    ^

TypeError: requestA.serializeBinary is not a function
    at main (/Users/anya/dev/node/grpc/examples/node/dynamic_codegen/greeter_client_v2.js:69:37)
    at Object.<anonymous> (/Users/anya/dev/node/grpc/examples/node/dynamic_codegen/greeter_client_v2.js:113:1)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:139:18)
    at node.js:968:3

If I comment out lines 69 and 70 of my greeter_client_v2.js file (attached above), which removes the usage of .serializeBinary() on the protobuf message, I do receive the same crash as @pmullaney.
Initializing gRPC client...
empty request A = {"alt":null,"a":null,"b":null}
msgA = {"foo":"ANGRBRD"}
filled request A = {"alt":"a","a":{"foo":"ANGRBRD"},"b":null}
requestADecoded = {"alt":"a","a":{"foo":"ANGRBRD"},"b":null}
/Users/anya/dev/node/grpc/examples/node/node_modules/grpc/node_modules/protobufjs/dist/ProtoBuf.js:2440
                            throw Error(this+"#"+keyOrObj+" is not a field: undefined");
                            ^

Error: .helloworld2.HelloRequest#alt is not a field: undefined
    at Error (native)
    at MessagePrototype.set (/Users/anya/dev/node/grpc/examples/node/node_modules/grpc/node_modules/protobufjs/dist/ProtoBuf.js:2440:35)
    at MessagePrototype.set (/Users/anya/dev/node/grpc/examples/node/node_modules/grpc/node_modules/protobufjs/dist/ProtoBuf.js:2434:38)
    at Message (/Users/anya/dev/node/grpc/examples/node/node_modules/grpc/node_modules/protobufjs/dist/ProtoBuf.js:2363:34)
    at serialize (/Users/anya/dev/node/grpc/examples/node/node_modules/grpc/src/node/src/common.js:87:23)
    at Client.makeUnaryRequest [as sayHello] (/Users/anya/dev/node/grpc/examples/node/node_modules/grpc/src/node/src/client.js:381:19)
    at main (/Users/anya/dev/node/grpc/examples/node/dynamic_codegen/greeter_client_v2.js:77:10)
    at Object.<anonymous> (/Users/anya/dev/node/grpc/examples/node/dynamic_codegen/greeter_client_v2.js:113:1)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)

If I instead follow the approach that you described here by constructing regular objects:
var h = {a: {foo: user}};
var bh = {b: {bar: user}};

You may find that code in my greeter_client_v2.js file (attached above). You can comment out for request A lines 55-70 and 77. And uncomment liens 73-74 and 78. Similarly, you can comment/uncomment the appropriate lines for request be lower in the file. You will observe that request A succeeds on request/response, but request B causes the following problem on the server side. It receives request type B, but is trying to parse for foo, which appears in request type A.
request={"alt":"b","a":null,"b":{"bar":"SUNSHINE"}}
/Users/anya/dev/node/grpc/examples/node/dynamic_codegen/greeter_server_v2.js:57
  callback(null, {message: 'Hello ' + call.request.a.foo});
                                                    ^

TypeError: Cannot read property 'foo' of null
    at Object.sayHello (/Users/anya/dev/node/grpc/examples/node/dynamic_codegen/greeter_server_v2.js:57:53)
    at Object.wrapper [as func] (/Users/anya/dev/node/grpc/examples/node/node_modules/grpc/node_modules/lodash/index.js:3095:19)
    at /Users/anya/dev/node/grpc/examples/node/node_modules/grpc/src/node/src/server.js:485:13

Hold on... nevermind the very last comment.

@murgatroid99 The usage you described below does work for me. My code is below. Could you please clarify why this is the proper usage, as opposed to creating a protobuf message first and filling in the fields? I do not understand the difference.
var h = {a: {foo: user}};
var bh = {b: {bar: user}};

  //
  // Construct a request
  //

  // Sample requests below
  var requestATEST = {a: {foo: "ANGRBRD"}};
  console.log("requestATEST = " + JSON.stringify(requestATEST));

  client.sayHello(requestATEST, function(err, response) {
     console.log("Response received!");
     console.log('Greeting: %j', response);
     console.log("\n\n\n");

     //
     // Construct another request
     //

     var requestBTEST = {b: {bar: "SUNSHINE"}};
     console.log("requestBTEST = " + JSON.stringify(requestBTEST));

     client.sayHello(requestBTEST, function(err, response) {
        console.log('Greeting:', response.message);
     });
  });

@angrbrd The "dynamic codegen" usage pattern, using grpc.load and Protobuf.js, was intended to be easy to use and familiar, so it uses regular JavaScript objects. That's just how the API is designed.

Here is the example showing that protobuf seems to handle oneof properly.
greeter_client.js.txt
I think this is a valid grpc problem.

@murgatroid99: Thanks for pointing out that using javascripts objects in the form above works. It seems more than odd though with the examples using actual messages that the form I originally used doesn't work. I suspect others will run into this.
There is also another problem worth mentioning and it is the reason I used the method of constructing the entire message(setting the oneof field). Consider the example proto in the attached file:
helloworld2.proto.txt
Wouldn't "var requestATEST = {a: {foo: "ANGRBRD"}};" be ambiguous as to the message to create?

I'm not sure what examples you're referring to. The dynamic codegen examples don't use message objects, and the static codegen examples don't use grpc.load.
And you are correct that that line of code alone isn't completely specified. But if you're passing that object to sayHello, then we know what message to create based on the signature of that method.

@murgatroid99: Sorry you're right, the examples in the dynamic codegen don't use message objects. And thanks for the clarification on the how the ambiguity is resolved via the method signature. We may post some examples here run into the same confusion.

Hi @murgatroid99 Thanks a lot for your help with these explanations, that makes much more sense now. Specifically, the point on the "dynamic codegen" pattern which uses grpc.load and regular JavaScript objects. As opposed to the "static codegen" pattern which does not use grpc.load and instead uses protobuf message objects.
I have modifying my files to have a usage example of each of the scenarios below. I am attaching here. Or if you think there's a better way to share these examples that might help others with the same issue? I could push them as .proto and .js to my own repo if that would help others. Just let me know.
helloworld2.proto.txt
greeter_client_v3.js.txt
greeter_server_v3.js.txt
message HelloRequest {
    oneof alt {
        A a = 1;
        B b = 2;
    }
}
message HelloRequest2 {
    oneof alt {
        A a = 1;
        C c = 2;
    }
}
message HelloRequest3 {
   C c = 1;
   oneof alt {
       A a = 2;
       B b = 3;
   }
}

@murgatroid99 : thanks for the help. I have add another case for streaming messages containing oneof to the example above that I will include here for completeness and close the issue.
greeter_client_v3.js.txt
greeter_server_v3.js.txt
helloworld2.proto.txt


[1.12.1] java.lang.NoSuchMethodError

Whenever I start a server using EnderZoo it crashes with the following error:
Note this line: net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from Ender Zoo (enderzoo)
https://pastebin.com/r7yMArFP
Minecraft Version: 1.12.1
Forge <IP_ADDRESS>5
EnderZoo-1.12.1-<IP_ADDRESS>.jar

is it only for servers? Or is it also for client as well? Because I have been getting a player ticking event with this mod and a lot of similar mods in your custom pack, here is my crashlog: https://pastebin.com/JJP7rKhr
I know this might not be relevant, but if ender zoo crashes on servers, then there might be a chance that it could also be the cause of the player ticking event on client-side servers

I am also seeing this crash. It's only when running a server. Client only works fine. Same versions as MinecraftPlaye.

#186

is it only for servers? Or is it also for client as well? Because I have been getting a player ticking event with this mod and a lot of similar mods in your custom pack, here is my crashlog: https://pastebin.com/JJP7rKhr

@MasterBuilder747  java.lang.NullPointerException: Ticking player     at lhykos.oreshrubs.common.entity.villager.trade.RandomLootBagTrade.func_190888_a(RandomLootBagTrade.java:40)  Looks like your problem is caused by Ore Shrubs and not Ender Zoo.

#186

Oh, missed that one. Guess I have to wait then for the next update. ;)

@MinecraftPlaye Oh! Thank you so much! I'll report this to them! I was really trying to figure out what was causing this in my pack!  :D


Steering Issues

          i fixed the positions and used the pre tried config options but now im haveing an issue were the robot will not turn correcctly as both sticks seem to drive until both are operated at the same time were they then seem to steer

Originally posted by @aidenm05 in https://github.com/BroncBotz3481/YAGSL-Example/issues/37#issuecomment-1454222325

I believe there may be an issue with the encoder pulse per rotation in my field relative equipment, which I intended to pursue legal action regarding. Currently, I do not have possession of the robot. The specified value was 2048, but I suspect that it should have been set to a value of one.

Can you post a video?

yes i can tuesday or wednesday

I understand that I need to retest today as ive evaluated my code have hard
set it to field orientation.
On Tue, Mar 7, 2023 at 12:13 AM T Grinch @.***> wrote:

Just to confirm, you are aware that the default control scheme is meant to
test the Swerve Drive by having the left joystick control translation (x
and y) and the right joystick control orientation (robot angle using gyro).
The reason for this is because if this works Autonomous will work.
—
Reply to this email directly, view it on GitHub
https://github.com/BroncBotz3481/YAGSL-Example/issues/45#issuecomment-1457548693,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVILYRQCSRYQMPKSNXDK7N3W227XJANCNFSM6AAAAAAVPWH76U
.
You are receiving this because you authored the thread.Message ID:
@.***>

After reviewing my code with the robot yesterday, I discovered that the magnets on our cancoders were not locked in place. I applied locktight and obtained new offsets. Despite these fixes, the angle motors are not working properly. When attempting to turn or move to the right, the angles fail to move. The only way to get them to move is by manually pushing the joysticks at once. I have tried using multiple different controllers, and I have double-checked the CAN IDs, but the problem remains unresolved.
Please let me know if you need any further information or if you have any suggestions for resolving this issue. Thank you.

my repo is https://github.com/aidenm05/YAGSL-march

I will try un inverting all motors today to see if that helps anything , additionally of note Autonmas works perfectly and all mortors stay together

previously, I added very little code. However, the error was repeated with
fresh YHGSL example code the one thing that I added was the Jason
configurations
On Wed, Mar 8, 2023 at 12:22 PM T Grinch @.***> wrote:

If autonomous works perfectly I am inclined to believe it is your code.
—
Reply to this email directly, view it on GitHub
https://github.com/BroncBotz3481/YAGSL-Example/issues/45#issuecomment-1460534265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVILYRTZO524EF5KQI5NHB3W3C563ANCNFSM6AAAAAAVPWH76U
.
You are receiving this because you authored the thread.Message ID:
@.***>

I. Understand the other template that I tried was bass falcon swerve I’m
going to be testing YAGsl later today while working with another team who
also used yagsl however, they used it with neos I’ll send a video of the
behavior later today.
On Wed, Mar 8, 2023 at 3:24 PM T Grinch @.***> wrote:

I really need a video to understand your issue unfortunately. What
templates did you try? (Also if they work feel free to use them, YAGSL is
still in beta because we havent worked out all of the bugs yet!)
—
Reply to this email directly, view it on GitHub
https://github.com/BroncBotz3481/YAGSL-Example/issues/45#issuecomment-1460824208,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVILYRUUE65KKVRH34QDI6TW3DTJNANCNFSM6AAAAAAVPWH76U
.
You are receiving this because you authored the thread.Message ID:
@.***>

ok will look at this
On Thu, Mar 9, 2023 at 9:34 AM T Grinch @.***> wrote:

Oh if youre using falcons, try this PR. We havent merged it yet because it
isnt tested on Neo's and we hope to soon.
#49 https://github.com/BroncBotz3481/YAGSL-Example/pull/49
—
Reply to this email directly, view it on GitHub
https://github.com/BroncBotz3481/YAGSL-Example/issues/45#issuecomment-1462167397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVILYRQX2ZYLAKSA3VOTNWTW3HTA3ANCNFSM6AAAAAAVPWH76U
.
You are receiving this because you authored the thread.Message ID:
@.***>

Update it was a issue with pid my p was too low will post my configs for
orthers buts working alright now sorry for the confusion
On Thu, Mar 9, 2023 at 11:05 AM Aiden McManus @.***>
wrote:

ok will look at this
On Thu, Mar 9, 2023 at 9:34 AM T Grinch @.***> wrote:

Oh if youre using falcons, try this PR. We havent merged it yet because
it isnt tested on Neo's and we hope to soon.
#49 https://github.com/BroncBotz3481/YAGSL-Example/pull/49
—
Reply to this email directly, view it on GitHub
https://github.com/BroncBotz3481/YAGSL-Example/issues/45#issuecomment-1462167397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVILYRQX2ZYLAKSA3VOTNWTW3HTA3ANCNFSM6AAAAAAVPWH76U
.
You are receiving this because you authored the thread.Message ID:
@.***>


Write tests

Write tests for the package, covering the following datasets:
Sports:

[x] Horses
[x] Greyhounds
[x] Football

Markets types:

[x] EACH_WAY
[x] Any other market type

Betting types:

[x] ODDS
[x] LINE
[x] ASIAN_HANDICAP_DOUBLE_LINE
[x] ASIAN_HANDICAP_SINGLE_LINE

Implemented in the commit above. Just the integration test is sufficient for now because the package is so small.


#656 rake task for mongo

mongo does not support find_each, replaced it with each

This looks fine for Mongo but I think we still need to use find_each for ActiveRecord. take will only load the first batch records.


chore(merge-back): 1.135.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: fd59655ef3f2b5dd912d42d6f7b9f41db3b5e62b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: fd59655ef3f2b5dd912d42d6f7b9f41db3b5e62b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


'pericarp color' should not be a subclass of 'fruit quality trait'

As pericarps are part of fruit
See also #292
Example of downstream problem:

This is fixed, closing.


proj: 9.1.0 -> 9.1.1

Description of changes
https://github.com/OSGeo/PROJ/releases/tag/9.1.1

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)
[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Package tested by running nix-build -A proj.tests and also by running following commands from ./result dir:
./result/bin/projinfo
Rel. 9.1.1, December 1st, 2022

./result/bin/projinfo EPSG:4326
PROJ.4 string:
+proj=longlat +datum=WGS84 +no_defs +type=crs

WKT2:2019 string:
GEOGCRS["WGS 84",
    ENSEMBLE["World Geodetic System 1984 ensemble",
        MEMBER["World Geodetic System 1984 (Transit)"],
        MEMBER["World Geodetic System 1984 (G730)"],
        MEMBER["World Geodetic System 1984 (G873)"],
        MEMBER["World Geodetic System 1984 (G1150)"],
        MEMBER["World Geodetic System 1984 (G1674)"],
        MEMBER["World Geodetic System 1984 (G1762)"],
        MEMBER["World Geodetic System 1984 (G2139)"],
        ELLIPSOID["WGS 84",6378137,298.257223563,
            LENGTHUNIT["metre",1]],
        ENSEMBLEACCURACY[2.0]],
    PRIMEM["Greenwich",0,
        ANGLEUNIT["degree",0.0174532925199433]],
    CS[ellipsoidal,2],
        AXIS["geodetic latitude (Lat)",north,
            ORDER[1],
            ANGLEUNIT["degree",0.0174532925199433]],
        AXIS["geodetic longitude (Lon)",east,
            ORDER[2],
            ANGLEUNIT["degree",0.0174532925199433]],
    USAGE[
        SCOPE["Horizontal component of 3D system."],
        AREA["World."],
        BBOX[-90,-180,90,180]],
    ID["EPSG",4326]]

I also wrote simple package test
diff --git a/pkgs/development/libraries/proj/default.nix b/pkgs/development/libraries/proj/default.nix
index 87736e1e..96479d88 100644
--- a/pkgs/development/libraries/proj/default.nix
+++ b/pkgs/development/libraries/proj/default.nix
@@ -5,6 +5,7 @@
 , cmake
 , pkg-config
 , buildPackages
+, callPackage
 , sqlite
 , libtiff
 , curl
@@ -62,6 +63,7 @@ stdenv.mkDerivation rec {

   passthru.tests = {
     python = python3.pkgs.pyproj;
+    proj = callPackage ./tests.nix { };
   };

   meta = with lib; {
diff --git a/pkgs/development/libraries/proj/tests.nix b/pkgs/development/libraries/proj/tests.nix
new file mode 100644
index 00000000..38126f06
--- /dev/null
+++ b/pkgs/development/libraries/proj/tests.nix
@@ -0,0 +1,11 @@
+{ runCommand, proj }:
+
+let
+  inherit (proj) pname;
+in
+runCommand "${pname}-tests" { meta.timeout = 60; }
+  ''
+    ${proj}/bin/projinfo EPSG:4326 \
+      | grep '+proj=longlat +datum=WGS84 +no_defs +type=crs'
+    touch $out
+  ''

Does it make a sense to add it ?

Result of nixpkgs-review pr 204148 run on x86_64-linux 1

1 package built:

pdal

Result of nixpkgs-review pr 204148 run on x86_64-linux 1

6 packages marked as broken and skipped:

octavePackages.octproj
python310Packages.worldengine
python39Packages.worldengine
qgis
qgis-ltr
worldengine-cli

15 packages failed to build:

apacheHttpdPackages.mod_tile (apacheHttpdPackages_2_4.mod_tile)
cloudcompare
gplates
mysql-workbench
perl534Packages.Tirex
perl536Packages.Tirex
python310Packages.cartopy
python310Packages.opensfm
python310Packages.python-mapnik
python310Packages.rlax
python39Packages.bsuite
python39Packages.cartopy
python39Packages.opensfm
python39Packages.rlax
t-rex

62 packages built:

entwine
gdal (python310Packages.gdal)
gmt
gnudatalanguage
grass
libLAS
libgeotiff
librasterlite2
libspatialite
mapcache
mapnik
mapproxy
mapserver
merkaartor
openorienteering-mapper
osm2pgsql
osmscout-server
paraview
pdal
postgresql11Packages.postgis
postgresql12Packages.postgis
postgresql13Packages.postgis
postgresqlPackages.postgis (postgresql14Packages.postgis)
postgresql15Packages.postgis
proj
python310Packages.asf-search
python310Packages.basemap
python310Packages.bsuite
python310Packages.fiona
python310Packages.geopandas
python310Packages.osmnx
python310Packages.owslib
python310Packages.plotnine
python310Packages.pygmt
python310Packages.pyproj
python310Packages.rasterio
python310Packages.wktutils
python310Packages.wrf-python
python39Packages.asf-search
python39Packages.basemap
python39Packages.fiona
python39Packages.gdal
python39Packages.geopandas
python39Packages.osmnx
python39Packages.owslib
python39Packages.plotnine
python39Packages.pygmt
python39Packages.pyproj
python39Packages.python-mapnik
python39Packages.rasterio
python39Packages.wktutils
python39Packages.wrf-python
pytrainer
qmapshack
saga
spatialite_gui
spatialite_tools
sumo
survex
udig
valhalla
xastir

@tomberek , why is qgis and qgis-ltr marked as broken ?

@tomberek , why is qgis and qgis-ltr marked as broken ?

Because qtwebkit is marked insecure.

Thanks @dotlambda

@imincik I doubt there would be any harm in adding the package test in another PR. It should be possible to use the finalPackage mechanism (https://nixos.org/manual/nixpkgs/unstable/#mkderivation-recursive-attributes) to refer to the actual package in question though as opposed to the callPackage trick, leaving no need for a separate file.

It's ok as a separate file if you like. The issue with using callPackage is overridden derivatives of the main proj package will still be using the main proj package in their my_overridden_proj.tests which could be misleading.
The manual looks like it hasn't been updated following the addition of finalPackage.

Thank you very much for explanation @risicle .
Do you mean doing something like this ?
diff --git a/pkgs/proj/default.nix b/pkgs/proj/default.nix
index 96479d8..41cb732 100644
--- a/pkgs/proj/default.nix
+++ b/pkgs/proj/default.nix
@@ -14,14 +14,14 @@
 , python3
 }:

-stdenv.mkDerivation rec {
+stdenv.mkDerivation (finalAttrs: {
   pname = "proj";
   version = "9.1.1";

   src = fetchFromGitHub {
     owner = "OSGeo";
     repo = "PROJ";
-    rev = version;
+    rev = finalAttrs.version;
     hash = "sha256-yw7eSm64qFFt9egJWKVyVo0e7xQRSmfUY7pk6Cwvwdk=";
   };

@@ -63,7 +63,7 @@ stdenv.mkDerivation rec {

   passthru.tests = {
     python = python3.pkgs.pyproj;
-    proj = callPackage ./tests.nix { };
+    proj = callPackage ./tests.nix { proj = finalAttrs.finalPackage; };
   };

   meta = with lib; {
@@ -73,4 +73,4 @@ stdenv.mkDerivation rec {
     platforms = platforms.unix;
     maintainers = with maintainers; [ dotlambda ];
   };
-}
+})

Yes, except
-    rev = version;
+    rev = finalAttrs.version;

this is unnecessary.

Thank you very much @risicle

Yes, except
-    rev = version;
+    rev = finalAttrs.version;

this is unnecessary.

Without rev = finalAttrs.version; build fails on
error: undefined variable 'version'

           23|     repo = "PROJ";
           24|     rev = version;
             |           ^
           25|     hash = "sha256-yw7eSm64qFFt9egJWKVyVo0e7xQRSmfUY7pk6Cwvwdk=";

so it looks like it must be there.

PR created in https://github.com/NixOS/nixpkgs/pull/205770

Ohh that's just because you removed the rec { from the opening brace of the attrset


Latest-docs build on github pages is broken

According to README, should be at https://scitools-docs.github.io/iris/master/index.html
Currently it's not there

Example build that removes all build files:
https://travis-ci.org/SciTools/iris/jobs/341513348
Pertinent stderrors:
 from /home/travis/build/SciTools/iris/docs/iris/src/examples/General/polar_stereo.py:
Traceback (most recent call last):
  File "/home/travis/miniconda/envs/test-environment/lib/python3.6/site-packages/scitools_iris-2.0.0rc2.dev0-py3.6.egg/iris/fileformats/__init__.py", line 70, in _load_grib
    from iris_grib import load_cubes
ModuleNotFoundError: No module named 'iris_grib'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/home/travis/miniconda/envs/test-environment/lib/python3.6/site-packages/matplotlib/sphinxext/plot_directive.py", line 517, in run_code
    six.exec_(code, ns)
  File "<string>", line 28, in <module>
  File "<string>", line 19, in main
  File "/home/travis/miniconda/envs/test-environment/lib/python3.6/site-packages/scitools_iris-2.0.0rc2.dev0-py3.6.egg/iris/__init__.py", line 373, in load_cube
    cubes = _load_collection(uris, constraints, callback)
  File "/home/travis/miniconda/envs/test-environment/lib/python3.6/site-packages/scitools_iris-2.0.0rc2.dev0-py3.6.egg/iris/__init__.py", line 313, in _load_collection
    result = iris.cube._CubeFilterCollection.from_cubes(cubes, constraints)
  File "/home/travis/miniconda/envs/test-environment/lib/python3.6/site-packages/scitools_iris-2.0.0rc2.dev0-py3.6.egg/iris/cube.py", line 143, in from_cubes
    for cube in cubes:
  File "/home/travis/miniconda/envs/test-environment/lib/python3.6/site-packages/scitools_iris-2.0.0rc2.dev0-py3.6.egg/iris/__init__.py", line 300, in _generate_cubes
    for cube in iris.io.load_files(part_names, callback, constraints):
  File "/home/travis/miniconda/envs/test-environment/lib/python3.6/site-packages/scitools_iris-2.0.0rc2.dev0-py3.6.egg/iris/io/__init__.py", line 210, in load_files
    for cube in handling_format_spec.handler(fnames, callback):
  File "/home/travis/miniconda/envs/test-environment/lib/python3.6/site-packages/scitools_iris-2.0.0rc2.dev0-py3.6.egg/iris/fileformats/__init__.py", line 72, in _load_grib
    raise RuntimeError('Unable to load GRIB file - '
RuntimeError: Unable to load GRIB file - "iris_grib" package is not installed.

Exception occurred:
  File "/home/travis/build/SciTools/iris/docs/iris/src/sphinxext/gen_gallery.py", line 196, in gen_gallery
    for key in app.builder.status_iterator(thumbnails,
AttributeError: 'StandaloneHTMLBuilder' object has no attribute 'status_iterator'
The full traceback has been saved in /tmp/sphinx-err-tkii_wjx.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
make[1]: *** [html] Error 2
make: *** [html] Error 2

WARNING: autodoc: failed to import module 'iris.experimental.raster'; the following exception was raised:
No module named 'osgeo'

I wonder if just before https://travis-ci.org/SciTools/iris/jobs/341513348#L1119 we are getting an exit code and simply ignoring it?

I think we are paying the price for https://github.com/SciTools/iris/blob/master/.travis.yml#L130-L133:
  # "make html" produces an error when run on Travis that does not
  # affect any downstream functionality but causes the build to fail
  # spuriously. The echo-backtick workaround gets around this error,
  # which should be investigated further in the future.

Which was added as a comment >3 years ago.

I've just pushed a branch to upstream to see how it does with a potential fix. Branch is https://github.com/SciTools/iris/tree/travis_docs_build.  The build itself is at https://travis-ci.org/SciTools/iris/builds/341764492.

Fixed in #2958.


TestParser_ParseExpr fails on Go tip

go test -run TestParser_ParseExpr
--- FAIL: TestParser_ParseExpr (0.00s)
	parser_test.go:1858: 7. "'2000-01-32 00:00:00'": error mismatch:
		  exp=unable to parse datetime at line 1, char 1
		  got=%!s(<nil>)

	parser_test.go:1858: 9. "'2000-01-99'": error mismatch:
		  exp=unable to parse date at line 1, char 1
		  got=%!s(<nil>)

FAIL
exit status 1
FAIL	github.com/influxdb/influxdb/influxql	0.006s
This is due to https://github.com/golang/go/commit/8b96be15f6632b33c7341840002bc5b0744b2977

This is marked as "difficult" since it involves building the latest Go tool chain.
We need to help determining if this test case is no longer valid, or if there is a different string we can use within this test case.

This file in question is influxql/parser_test.go.

Starting from Go 1.6 time.Parse will not return an error when parsing a date where date component is greater than 31. (e.g. 36 Jan 2015).
The test checks that influxdb doesn't accept invalid dates. Due to the choice of date strings it passes with Go 1.5. However the validation is still not correctly implemented for dates like 30 Feb, 29 of Feb on non-leap year, 31 Nov, etc.
Depending on the desired influxdb behaviour there are two different ways to fix this issue.
If you decide to reject invalid dates then the parser should validate number of days depending on date's month and year. Relying on time.Parse error checking is not enough.
If you decide to ignore invalid dates then the test should be removed.

@otoolep I started taking a look at this, but the solution depends on the expected behaviour when parsing date(times).
Given the input 2000-01-32 Go 1.6 will parse that as a time.Time equivalent to 2000-02-01. There will be no error returned (hence the failing test case).
So should influx allow this to happen or is it important that the input is a valid date prior to it being parsed (and therefore 2000-01-32 should be a parse error.
Given an answer to this question I could put a fix in for this.

It seems to me the test is just about checking that the system catches parse errors when they happen. If this string is no longer a parse error, then perhaps the test is no longer valid and should just be removed? (When we move to Go 1.6).
Any comment @dgnorton ?

This is no longer an issue. See https://github.com/golang/go/commit/5ef899111e581b1e57aa1546caa204d48bdf5503 for more details.

Thanks very much for the update, @kostya-sh
On Thursday, December 10, 2015, kostya-sh<EMAIL_ADDRESS>wrote:

Closed #4341 https://github.com/influxdb/influxdb/issues/4341.
—
Reply to this email directly or view it on GitHub
https://github.com/influxdb/influxdb/issues/4341#event-488911531.


Compat support for PHPUnit 10

Now that PHPUnit 10 has been released, a few things that changed must be addressed before even considering updating to it. The biggest change that affects us is that the data providers are now expected to be static functions. While updating things here and there, I also found some little typos or mistakes in the code that I fixed in separate commits.

BTW static is not a requirement for PHPUnit 10, just a deprecation... but it's nice to be already on top of it!

Right, non-static providers will be unsupported in PHPUnit 11


Make CoAP block size configurable at build- and run-time

This patch makes the block size used in CoAP block transfers configurable in two ways.

Build-time configurable default value via a cmake variable.
Run-time configurable via new -s command line argument for all examples. This will simplify (automated) testing with different block sizes.

:warning: The new default value for the block size will now be 1024 bytes with no further configuration. The idea is to avoid block transfers in common use-cases.  Any objections?

1024 bytes for the block size agrees with RFC7252 section 4.6

@mlasch Please rebase on the current master :smile_cat:

Pushed again, let clang-format do the formatting.


development site: "CSRF Failed: CSRF token missing or incorrect" when posting with domain ohshown.site

Describe the bug
When creating ohshown event with the domain ohshown.site, the posting will fail and get "CSRF Failed: CSRF token missing or incorrect".
To Reproduce
Steps to reproduce the behavior:

Go to the development site
Create an ohshown event as usual

Expected behavior
Created ohshown event.
Additional context

If we use the url with IP, it will be successful
Get the message  "CSRF Failed: CSRF token missing or incorrect" with your browser in development mode. Take chrome as example, press F12, then go to Network, and then check preview or Response.

fwiw, I thought it was ALLOWED_HOSTS issue.

hypothesis: this seems to be raised by the approach of docker container deployment. That said, POST to ohshown.site may change domain from ohshown.site to localhost when creating ohshown events.
Next step:

check if vue.config.js makes sense (frontend)
check if CSRF manipulation makes sense in django (backend)

fwiw:
Both settings below could reproduce the issue:
diff --git a/vue.config.js b/vue.config.js
index 0c5fdb6..0ebc773 100644
--- a/vue.config.js
+++ b/vue.config.js
@@ -4,7 +4,7 @@ module.exports = {
     disableHostCheck: true,
     proxy: {
       '/server': {
-        target: 'http://localhost:8888',
+        target: 'http://ohshown.site:8888',
         changeOrigin: true,
         pathRewrite: {
           '^/server': ''

I am still figuring out what's going on. Currently I use postman to help me debug. Let me brief the approach here for anyone who may be interested in:

get the payload from your browser (see below for chrome as example)
post the payload in the raw-JSON of postman

Direct post via postman and port 8888 works properly. That said, CSRF is not warned by django.
My possible next step: focus on how vue deals with the proxy with the corresponding .env.

I am still figuring out what's going on. Currently I use postman to help me debug. Let me brief the approach here for anyone who may be interested in:

get the payload from your browser (see below for chrome as example)
post the payload in the raw-JSON of postman

@Neilxx @yanghaochang104  I am a bit blocked and confused by this. If you are familiar with the settings of vue.config.js. Do you have any idea about this issue?

Direct post via postman and port 8888 works properly. That said, CSRF is not warned by django.
My possible next step: focus on how vue deals with the proxy with the corresponding .env.

I am still figuring out what's going on. Currently I use postman to help me debug. Let me brief the approach here for anyone who may be interested in:

get the payload from your browser (see below for chrome as example)
post the payload in the raw-JSON of postman

@tai271828  I'm a little bit confused.
I just post successfully on development site.

Am I reproduce the issue correctly?

@Neilxx thanks for retesting. You really save my day lollllllllllllllllll

Just for the record: the issue happened to me again today, but switching to the other profile of my chrome still works. Hooray!


Infected server

Hello,
I really need help!
My server on digital ocean has infected, I see a lot of connections, but i don't know which are infected.
here is a part of the connections:
http://tinypic.com/r/2djtr29/8
Can someone help me find a solution?
Thanks.

Looks like a socket leak rather then infection....

@willmkt
Please use community forum for discussion.


Fsharp vsix

This isn't intended to be merged. as it's still a WIP.  I've been caught up in another project, so I wanted to open this up so we could discuss the process of moving more of the codebase to F#, streamlining the rest and paying off some technical debt.
The main tasks remaining that I'd like to accomplish are -

Making FsXaml GUIs for all the dialog pages
Switch to using the settings store for persistent configuration settings
Stop using services to provide options settings
Upgrade to using newer services over DTE calls
Switch to VS services over redundant VFPT implementations

Thanks for the great work. We may not be able to accept everything. But there are a few good enhancements I would like to pull in through separate PRs:

Put all files of Logic projects into their own folders.
Use importing constructors in Logic.VS2013 and Logic.VS2015 projects.
Add convenient extension methods for ServiceProvider.

In many of these cases we can move away from using the service provider by using an importing constructor instead.

@cloudRoutine Would you mind to submit the above bullet points as separate PRs? There may be more things we can pull, but it's much easier to do piece by piece. Thanks.

no problem, I'll try to get to it later today or tomorrow.

The file reorganization has been a total disaster, somehow I introduced a bunch of bugs I can't track down. I'll start over from scratch later today

@cloudRoutine How is it going? I think the main idea is to copy relevant changes from this PR and apply to current master :-).


Link Issues

 1. [L1227]  https://samwoolf.net/wp-content/uploads/2017/03/crimemapper1a-1.jpg Failed to open TCP connection to samwoolf.net:443 (Connection timed out - connect(2) for "samwoolf.net" port 443)
6167
  2. [L1228]  https://samwoolf.net/wp-content/uploads/2017/03/crimemapper2a.jpg Failed to open TCP connection to samwoolf.net:443 (Connection timed out - connect(2) for "samwoolf.net" port 443)
6168
  3. [L1229]  https://samwoolf.net/wp-content/uploads/2017/03/crimemapper3a.jpg Failed to open TCP connection to samwoolf.net:443 (Connection timed out - connect(2) for "samwoolf.net" port 443)
6169
  4. [L1230]  https://samwoolf.net/wp-content/uploads/2017/03/crimemapper4a.jpg Failed to open TCP connection to samwoolf.net:443 (Connection timed out - connect(2) for "samwoolf.net" port 443)
6170
  5. [L1231]  https://samwoolf.net/wp-content/uploads/2017/03/crimemapper5a.jpg Failed to open TCP connection to samwoolf.net:443 (Connection timed out - connect(2) for "samwoolf.net" port 443)
6171
  6. [L2352] 301 https://github.com/ivirtex/network-arch  → https://github.com/ivirtex/networkarch-old
6172
  7. [L2405] 404 https://github.com/honjow/FEhViewer/blob/nullsafety/screenshot/2021-06-21%2019.15.21.jpg?raw=true
6173
  8. [L2406] 404 https://github.com/honjow/FEhViewer/blob/nullsafety/screenshot/2021-06-21%2019.15.27.jpg?raw=true
6174
  9. [L2407] 404 https://github.com/honjow/FEhViewer/blob/nullsafety/screenshot/2021-06-21%2019.15.58.jpg?raw=true
6175

https://github.com/dkhamsing/open-source-ios-apps/commit/2a4ca71fc1fba25bd6dc546661a4e0b2521708d3


Hot Reloading running coroutine can sometimes cause issues

this is what happens to me. First time I deleted for loop it works, because FSR reloaded scripts when coroutine entered the first loop. Second time I delete the same for loop, FSR reloads scripts while coroutine is inside the deleted loop and it freezes
https://user-images.githubusercontent.com/6343986/231097378-5286c659-63c0-4863-adc9-d81d4b440e31.mp4

I've got a suspicion as to why this may happen, yield instructions are extracted into auto-generated enumerator class. And MoveNext() and GetCurrent are used to get value in calling code.
The naming is automatic. I think detour may pick up wrong instance from time to time and that's why sometimes you see results and other times you do not.
Move investigation needed


Can't publish stubs; doesn't change behavior

I got to this stage:
php artisan vendor:publish --provider=ATehnix\LaravelStubs\Providers\ConsoleSupportServiceProvider
and the response was
Nothing to publish for tag []
At
php artisan stubs:publish
the response was
[Symfony\Component\Console\Exception\CommandNotFoundException]     There are no commands defined in the "stubs" namespace.
I figured out the intent of both those commands, and manually copied your config file into the /config directory, and manually copied .stubs files into resources/stubs.
No dice, though.
php artisan make:model TestModel
still returns a file based on the original .stub, not my lightly edited one from resources/stubs.
I quit and restarted terminal. Dumped the composer auto-load files. I don't know what else to do.

I suspect that you have cached configuration. Try the command php artisan config: clear.

Let me know if the problem still exists after cleaning the cache.
Then I will know that the problem requires solving.

Sorry. Still doesn't work. Let me know how I can help you track down the bug.
I'm including a screenshot, so you can verify that I've installed and configured this correctly.

Which version laravel you used?
I just checked the installation package on a fresh laravel project and could not replicate your problem. (I used Laravel 5.3.23)
Unfortunately, I have no idea what could be the reason and how can I reproduce your problem.

Huh. I'm on 5.3.23 as well. I'll have a play with a clean project
tomorrow and see if I can track down what's causing the problem.
On 11/15/16 10:25 PM, Андрей Соснов wrote:

Which version laravel you used?
I just checked the installation package on a fresh laravel project and
could not replicate your problem. (I used Laravel 5.3.23)
Unfortunately, I have no idea what could be the reason and how can I
reproduce your problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/atehnix/laravel-stubs/issues/1#issuecomment-260864749,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWJKi5wOeb9tOrmF57dSGgCj5yzdlH9mks5q-qHvgaJpZM4KyJva.


Don't show external icon for links to assets

Trello card
Trello-2643
Context
As our assets are now hosted on a different domain (in test/prod) they are being picked up as external links and an icon is being added incorrectly.
Update LinkController so it knows about the asset URL and treats it as internal.
Changes proposed in this pull request

Don't show external icon for links to assets

Guidance to review

Before
After

We could probably DRY up the body tag but I will wait until the new GTM container PRs have been deployed as they simplify the existing body tag a lot and it will be easier to do then.

Looks good to me!


DBZ-6567 SMT for handling timezone based fields

https://issues.redhat.com/browse/DBZ-6567
To Do

[x] Docs - https://github.com/debezium/debezium/pull/4819
[x] KC timestamp field
[x] Test cases

@ani-sha We are almost there! Please make sure there is no data loss for sub-milliseconds transformations. Add support for seconds in the offset and double check the DST test case. When address this is good to go. This SMT is really going to be useful.


Fix nomenclature for path parameters in routes.go for runner

The problem faced currently?
How can we solve it?

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important to you.
👍

Fixed in v0.17.0


Develop MAC powerpoint add-in/macro

This seems to be quite tricky, since the dev tools for office on mac are not as fully featured. any one have any ideas?

Did I do something?
I applied for a job several times and never hear anything back and I've literally been running your bark software since you released it, I've made over 10000 songs with Suno and was using it since you launched on Discord.
I'm very educated in this area and I'm very creative if not a little questionable I suppose in regards to my thought processes I will admit. Is that what is scaring you guys off. I like to tell stories man, that's it.
But I reported the credits bug to you guys several times and it persisted for months, it wasn't until I DM'd your co founder, and it was fixed days later lol :) but he still never responded to me but that was a clear acknowledgment he saw my DM's and acted on them and chose to ignore me.
I'm not trying to cause a fuss but honestly, what can I do to make you guys believe in me?
I really want to work for you and I will admit I have autism, I tend to turn against people that ignore me like this.
They even blacklisted my profile on Suno so when you goto my profile it just says user profile not found but people still like my music cause it gets shared to the new section and my followers. So it's really got me a bit messed up sanity wise, I won't lie.
It literally feels like I'm on a list and everyone at Suno has been told to not interact with me
I even noticed a bunch of Suno employees running bot accts or fake artists accts on x that have no followers and yet their music on Suno has millions of plays which kind of gives that one away.
But there I go again making up conspiracies which is probably why I am on this do not talk to list eh?
But really, I want to work for you, I don't understand what I have done...? or not done...
You saw my embedded X player I built right? that plays music straight off your CDN. nothing impressive on the ai side, but still.
I haven't seen anyone else build an embedded x player.
But I know a lot about AI and I'm stuck, I can't go forward any further without working for you or udio or someone.
noone posts the source code anymore and I've gotten behind. I was right in there with bark... I know my way around that thing like a champ. I still use it to do all my eve audio and deep fakes and voice cloning. took a while to figure out fyi as far as getting it to not screw up all the dang time... I know you got smarter guys over there, clearly, but I would learn fast and I guarantee I would end up contributing something worth while. its just who I am literally. I like to fix things, debug things, tinker with stuff. I always find clever solutions or new uses, or alternative things people overlook.


Hyperqueue or not hyperqueue?

Comment by @dianaiusan :
We should comment when to use hq and when not. I typically say when you have many short jobs, but I am no expert. Maybe also when to run in a Slurm job, or when to use the slurm or cluster-generic executor. Many times several ways are applicable, but if someone has some good recommendations, that'd be great.

Also, my colleague thinks it would be nice with more exercises, which would turn it into a workshop rather than hackathon, but I think it would be nice.

Some kind of decision tree could be nice to try to come up with?
Including: interactive, one batch job, using SLURM integration with one batch job, using SLURM integration with multiple jobs, using Hyperqueue
Anything more?


How to find which image is used as test set while training nerfacto?

After training nerfacto, we can get test result with ns-eval, but I cannot find which images are used for evaluation.
Is there any way to check which images are used for ns-eval, and check how do they get rendered?

@mylee95 One idea is to run ns-eval with argument --render-output-path then it will save the rendered images at given path and hence you will be able to check the name of the images used for evaluation.

@mylee95 One idea is to run ns-eval with argument --render-output-path then it will save the rendered images at given path and hence you will be able to check the name of the images used for evaluation.

Thank you for suggestion! However, it seems like ns-eval with argument --render-output-path saves rendered images with datamanager's index number as name, not using image's original name.
I just modified the "get_average_eval_image_metrics" function in nerfstudio/nerfstudio/pipelines/base_pipeline.py to save each image's evaluation results with its name together.


Event logs for maintenance and hibernation operations

How to categorize this issue?
/area operations
/area usability
/kind enhancement
/priority normal
What would you like to be added:
Add an "event-log" of performed maintenance operations as well as hibernation / wake-up operations.
Below I listed three options that I could think of how to realize this.
Option (1)
Add an events (or otherwise named field) into the Shoot.Status containing arbitrary Shoot events identified by the type field.
status:
  conditions: <>
  hibernated: true
  events:
    - type: MachineImageVersionMaintenance
      timestamp: "2020-05-25T14:47:54Z"
      status: "Successful"
      message: "Updated image of worker-pool 'coreos-1' from 'coreos' version 'xy' to version 'abc'."
      reason: "AutoUpdate of MachineImage configured"
    - type: MachineImageVersionMaintenance
      timestamp: "2020-05-25T14:47:53Z"
      status: "Successful"
      message: "Updated image of worker-pool 'coreos-2' from 'coreos' version 'xy' to version 'abc'."
      reason: "Machine image version is expired"
    - type: KubernetesVersionMaintenance
      timestamp: "2020-05-25T14:47:52Z"
      status: "Successful"
      message: "Updated Kubernetes version '0.0.1' to version '0.0.5'. This is an increase in the patch level."
      reason: "AutoUpdate of Kubernetes version configured"
    - type: KubernetesVersionMaintenance
      timestamp: "2020-05-25T14:47:53Z"
      status: "Successful"
    - type: KubernetesVersionMaintenance
      timestamp: "2020-05-24T14:47:53Z"
      status: "Successful"
    - type: Hibernation
      timestamp: "2020-05-24T14:47:53Z"
    - type: WakeUp
      timestamp: "2020-05-26T14:47:53Z"

Option (2)
To have a separation between Maintenance and Hibernation, this would be another option.
This would also group events that happened during the same maintenace time window.
status:
  conditions: <>
  hibernated: true
  maintenance:
    - lastSuccessfulMaintenance: "2020-05-25T14:47:53Z"
      events:
      - timestamp: "2020-05-25T14:47:53Z"
        status: "Successful"
        messages:
          - message: Updated image of worker-pool 'coreos-1' from 'coreos' version 'xy' to version 'abc'.
            reason: AutoUpdate of MachineImage configured
            type: MachineImageVersion
          - message: Updated Kubernetes version '0.0.1' to version '0.0.5'. This is an increase in the patch level.
            reason: AutoUpdate of Kubernetes version configured.
            type: KubernetesVersion
  hibernation:
    - timestamp: "2020-05-25T14:47:53Z"
      type: "Hibernation"
    - timestamp: "2020-05-26T14:47:53Z"
      type: "WakeUp"

Another option (3) would be to have a dedicated resource in the core.gardener-cloud API group
apiVersion: core.gardener.cloud/v1beta1
kind: ShootOperation
metadata:
  name: <shoot-name>
  namespace: shoot--dev--<>
  ownerReferences:
    - kind: Shoot
      name: <shoot-name>
spec:
  type: Maintenance / Hibernation
status:
  lastOperation: "2020-05-21T00:00:12Z"
  events: # only contain actual changes
    - type: MachineImageVersionMaintenance
      timestamp: "2020-05-25T14:47:54Z"
      status: "Successful"
      message: "Updated image of worker-pool 'coreos-1' from 'coreos' version 'xy' to version 'abc'."
      reason: "AutoUpdate of MachineImage configured"
    - type: MachineImageVersionMaintenance
      timestamp: "2020-05-25T14:47:53Z"
      status: "Successful"
      message: "Updated image of worker-pool 'coreos-2' from 'coreos' version 'xy' to version 'abc'."
      reason: "Machine image version is expired"
    - type: KubernetesVersionMaintenance
      timestamp: "2020-05-25T14:47:52Z"
      status: "Successful"
      message: "Updated Kubernetes version '0.0.1' to version '0.0.5'. This is an increase in the patch level."
      reason: "AutoUpdate of Kubernetes version configured"

I tend to favour option (3) to not pollute the already quite large Shoot resource with Hibernation and Maintenance event logs. @vpnachev also suggested to restrict the TTL of an event to 14 days.
The same TTL could also be done if we store the event log in the external resource.
Another issue that I see is how to deal with failed Shoot operations e.g a Shoot using an expired Kubernetes version cannot be updated because of a CloudProfile misconfiguration.
It would be handy if the controller could persist this information without writing a new event for each re-tried operation. There are several ways to achieve this.
Why is this needed:
There is no place to properly store a log of automatically performed maintenance operations.
For instance for Maintenance, the Gardener Controller manager just writes events on the Shoot resource stating the reason for a performed update operation.
The problem is that Kubernetes events are Garbage collected after a certain amout of time (configurable in the Kube-Apiserver.
Usually this is somewhere between 1 - 24 hours.
This is problematic because

Users want to be able to see which maintenance operation Gardener automatically performed, when, why and if it was successful.
In case of unwanted update behaviour / problems, operators cannot easily determine what was the reason for the update operation.

In addition Gardener does currently only persist the current and desired state of the Hibernation.
Shoot owners might also want to see a log of the manually & automatically triggered Hibernations.
Integrators like the gardener Dashboard could read this information and display an operations log for both the Hibernation and the Maintenance operations.

cc @gardener/dashboard-maintainers

/assign @BeckerMax

Hey, I am new to K8s and Gardener so I very much welcome corrections/feedback to my suggestion below:
I think it would be cleaner to not introduce any new custom resource for retaining events. Instead, the already created events would best be recorded in some way and then saved in a storage form made for logs. In our case that would mean that something in the Seed Cluster reads these events and writes them to Elasticsearch(/Loki). Which is then accessed by the user via  Kibana(/Grafana). There are multiple solutions like kubernetes-event-exporter but I am worried they could not work in our setup: The controller manager does not know about all the existing elasticsearch instances, right? What do you think? Do you have other ideas?
Advantages of this approach:

K8s docu itself recommends it here: To provide longer history and aggregation capabilities, a third party solution should be installed to capture events..
etcd is a key-value store not made for storing logs. There were problems in the past with high load on etcd due to events here and here. This might not be very critical as we use a second etcd for events.
This might be a minor but by retaining events of customers in our etcd we are paying for storage which the customer should pay. If tens of thousands of clusters get createad/hibernated in two weeks this could add up.
We do not introduce new code (hopefully).

As an alternative we could implement a new resource as originally suggested. After discussion with @tim-ebert  we went away from using a resource which appends new events (as discussed originally above). Instead we want to create something similiar to the current kubernetes events but with a longer ttl (time-to-live in etcd). We thought that would be closer to the original kubernetes implementation and therefore help understanding. Steps involved for the implementation:

Create a new resource in our custom api-server. It should be similiar to the k8s event object. When registering the RESTStorageProvider set a 14 day ttl similiar to here. Probably we can reuse the storageProvider code ?
Create a new eventRecorder. Currently, events are written via client-go eventRecorder  . It would be convenient to have a similar mechanism implementing the same interface which then writes the events in the form of the new resource.
Adapt the machine controller to use the new eventRecorder in addition for certain events.

WDYT?

Thanks @BeckerMax for thinking it through so thoroughly.
I think the approach of leveraging the existing corev1.Event resource and exporting it to a place where the data can be stored for a longer time makes sense in general.
However, I think this is something that needs to taken care of during the deployment of Gardener. The contract from Gardener's point of view could simply be to generate these events. If somebody wants to store them for a longer time then it's his responsibility to deploy additional tools into the garden cluster (e.g., the event-exporter + elasticsearch) and configure them properly to pull the events out of etcd. Consequently, if we would follow this approach, we wouldn't do anything about it here in the gardener/gardener repository other than generating these corev1.Event resources (and maybe providing a document explaining these 'best practices').
The disadvantage, however, would be that our ops tools (e.g., gardenctl or the dashboard) cannot "easily" display these events because they are no longer Kubernetes resources. They would be stored in third-party tools for which "special"/dedicated code needs to be developed. Similarly, end-users that work with the Gardener API programmatically would need to do the same. OTOH, they are already required to do it for accessing their controlplanes' monitoring or logging data.
Considering that in large landscapes most shoots won't have a hibernation schedule and won't get too often Kubernetes/machine image version updates I'd assume that we wouldn't have "too many" of such ShootEvent resources. Though, it can theoretically happen (based on the configuration of Gardener and the shoots, basically), and then we might most likely face bottlenecks and other issues as etcd is not made for storing such information.
Probably it would make sense to have a short discussion with @gardener/gardener-maintainers @gardener/dashboard-maintainers @vlvasilev @dguendisch @vlerenc about the subject matter, and then decide jointly about the desired way to proceed.

I think both arguments are valid: @BeckerMax with not misusing etcd for kind-of log storage but instead re-using our logging solution (by using one of the many events-to-logs solutions) and @rfranzke with a) events are low-volume as maintenance operations are pretty heavy-weight, so customers cannot induce a large amount of them and b) Dashboard or other ops tools would need to code against the logging stack instead of k8s to retrieve those logs.
So it probably boils down to the question where a Gardener operator or consumer wants to read those maintenance events and if this feature is important enough to justify new UIs and extensions in e.g. gardenctl.
Sure, a dedicated Dashboard UI would be great but so do many other features that "would be great" :)
For me personally, it would totally suffice to know that we direct events into our logging stack and e.g. provide a grafana (loki) dashboard, i.e. "Shoot maintenance history" that would directly filter up those events. That grafana dashboard could be part of the users grafana so that consumers can view this too.
This would avoid additional dashboard/gardenctl development and could have the additional benefit of having events (not only for shoot maintenance but generally) available in our logging solution.

I agree with @dguendisch that both options make total sense.
However, I'm not sure, how such a logging implementation would look like for the first step, as we don't have any logging stack visible to the enduser in the garden cluster as of now. We only have a logging stack with the Shoot Control Plane in the Seed clusters (which is also brought down during hibernation). So I guess, we would need a new instance of kibana/grafana (at first just) for displaying these Shoot operation events.
I also started thinking about, how a possible Dashboard integration of such events would then look like (if we would want to do it). So probably we would start with a simple section on the shoot details page displaying the latest events in chronological order. But at the next step, the Shoot owners might ask for an aggregated view of all operations on shoots in their project(s) and then the Gardener operator might want to have an aggregated view of all operation of a whole gardener system. Then we would want to filter, and so on and so on.... So to make this feature more and more useful, we will basically implement a lot of stuff, we could probably get out-of-the-box with already existing logging solutions in combination with an event-to-logs solution.
Long story short: im kind of split on the options and would indeed enjoy a discussion on the matter as @rfranzke proposed.

FYI/from former times: #236

Outcome of the joined discussion:
As an immediate solution we want to extend the life-span of certain shoot related events in etcd. We start with events recording  'K8s version updates', 'imageversion updates' and hibernation. This is implemented with an event controller in PR https://github.com/gardener/gardener/pull/2649 .
To improve observability we need to further discuss :
-> Which relevant information for the users/operators are we currently missing?
-> Is the missing information best provided in logs or events?
-> How do we want to persist events? (Probably we want to export events to some persistent storage other than etcd).
-> Through which interfaces do we want to make the events accessible to the user?
-> Is it helpful for the user to have an operations-id to match events with logs?
Please feel free to add information to the above.

-> Which relevant information for the users/operators are we currently missing?
-> Is the missing information best provided in logs or events?

Do we already have events for reconciliation/deletion operations?

-> How do we want to persist events? (Probably we want to export events to some persistent storage other than etcd).
-> Through which interfaces do we want to make the events accessible to the user?

Hm, didn't we decide on the event controller approach for now with a separate etcd for the events (which is a best practice anyways) and a "short/normal" TTL for the non-shoot events? Everything else is much more work and we don't have a clear plan now, so I'd suggest to postpone this discussion until we have gained some experience with the event controller approach.

-> Is it helpful for the user to have an operations-id to match events with logs?

Probably yes - we had it earlier (2 years ago), but then kicked it out again because we had no solution to store the events for shoots for longer time. Now, with the event controller, we can introduce the operations ID again to allow to find/correlate logs easier.


Just enough TeX

tectonic
MikTex: https://miktex.org/kb/just-enough-tex

Closed by https://github.com/sosiristseng/sosiristseng.github.io/commit/67f7aac97155e9ebde75bc84eb5a140bcf989f9e


#1175 - Dtos in RestController defined in interface are not configure…

…d for reflective access

Merged via f0287dc5d4897e7ee9692f9424d0b78f065d80ec, thanks!


baseline after combining grads in TFR

we should find a elegant way to baseline after combining grads in TFR.
Otherwise the ERD appears positive on grads...

@agramfort Do you have a plot of sorts for this?

what do you mean?
see message on mailing list?


feat: support specialized generic types

Fix #1195

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release adds support for specialized generic types.
Before, the following code would give an error, saying that _T was not
provided to the generic type:
@strawberry.type
class Foo(Generic[T]):
    some_var: T

@strawberry.type
class IntFoo(Foo[int]):
    ....

@strawberry.type
class Query:
    int_foo: IntFoo

Also, because the type is already specialized, Int won't get inserted to its name,
meaning it will be exported to the schema with a type name of IntFoo and not
IntIntFoo.
For example, this query:
@strawberry.type
class Query:
    int_foo: IntFoo
    str_foo: Foo[str]

Will generate a schema like this:
type IntFoo {
  someVar: Int!
}

type StrFoo {
  someVar: String!
}

type Query {
  intFoo: IntFoo!
  strfoo: StrFoo!
}

Here's the tweet text:
🆕 Release (next) is out! Thanks to Thiago Bellini Ribeiro for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)


[Bug]: Link to drive attribute description document, link jumps to 2.4.4, not 2.4.5

ODC version
odc422
OB version
ob410
What happened?
Click on the driver within the link to jump to 2.4.4

What did you expect to happen?
Jump to drive 2.4.5

How can we reproduce it (as minimally and precisely as possible)?
Click on the description document in the link driven attribute
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 13a9f62bab1725d883bff7ff081f90c877d254be
------
晓康
Thu Oct 26 15:05:16 2023 +0800

pass


Branch on carthage_cache exist

It would be really awesome to be able to branch on carthage_cache exist, much like how you can do
carthage_cache install || fallback

Since I'm going to be running this on CI, I don't want to have to re-install if my Carthage directory is cached

If I understand correctly you want to avoid downloading the archive for every build if there a local cache already, am I correct? If that is the case, in the latest release we added support for local cache. Meaning the that carthage_cache won't download an archive if a local copy exists.
Will that work for you?

oh wow, yeah. That would
So if I understand correctly, if I run carthage_cache install and I already have everything correctly installed in Carthage/Build, it won't re-download the archive?

Yeah that is correct you can check that here
I understand that this would work for you so I am closing this issue. Feel free to open a new one if you found a problem or have another question.


podman-remote create|run

add the ability to create and run containers via the podman-remote
client.
we now create an intermediate layer from the the create/run cli flags.
the intermediate layer can be converted into a createconfig or into a
varlink struct.  Once transported, the varlink struct can be converted
back to an intermediate layer and then to a createconfig.
remote terminals are not supported yet.
Signed-off-by: baude<EMAIL_ADDRESS>

I will enable tests on the next PR

the test failures look legit ... ill dig into them today.

@baude Needs a rebase.

@larskarlitski

Varlink API looks strange

Varlink API looks strange

@haraldh can you elaborate?

Code LGTM... Let's get some more reviews on this
@rhatdan @TomSweeneyRedHat @vrothberg @giuseppe

LGTM, assuming happy tests, which aren't at the moment.

I don't understand the changes to the varlink API. What's the purpose of CreateResult and why do I need to pass something called Result into a Create API in the first place? It also seems very clunky to use.

I would encourage you to be patient.  I'm reworking some stuff based on input from harald.  And don't get hung up on wording.

OK, this is now reworked to address some of the concerns about the endpoint that were brought up.  The endpoint is now simpler and includes mostly nullable options.  To deal with this, major rework was done on the remote-client side to deal with lack of context now being sent.

LGTM
@rhatdan PTAL

@TomSweeneyRedHat @giuseppe @vrothberg also

LGTM.
A few nits that will hopefully be fixed up later.

/lgtm