[AIRFLOW-3191] Fix not being able to specify execution_date when creating dagrun

Jira

[X] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-3191
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Creating a dagrun using the flask web UI is not possible because execution_date is hidden. This is because the column type is actually DATETIME where Flask only has a converter for DateTime (it's the same type, it's a casing issue).
Fix is to add a form override: form_overrides = dict(execution_date=DateTimeField)
Description

[X] Here are some details about my PR, including screenshots of any UI changes:

Tests

[X] My PR adds the following unit tests OR does not need testing for this extremely good reason:
UI change, no tests for it. Made sure dagrun field appeared in UI and DAGRun was indeed created by the form.

Commits

[X] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[X] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[X] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #4037 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #4037      +/-   ##
==========================================
+ Coverage   75.77%   75.78%   +0.01%
==========================================
  Files         199      199
  Lines       15946    15947       +1
==========================================
+ Hits        12083    12086       +3
+ Misses       3863     3861       -2

Impacted Files
Coverage Δ

airflow/www/views.py
68.87% <100%> (+0.01%)
:arrow_up:

airflow/models.py
91.67% <0%> (-0.05%)
:arrow_down:

airflow/jobs.py
82.39% <0%> (+0.26%)
:arrow_up:

Continue to review full report at Codecov.

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

@aoen Could you provide before and after UI shots? If this does what I think it will it's useful.

Oh - also: We should make a similar change in www_rbac views please.

Certainly!
Here is the screenshot where you can see the execution_date parameter is now available:

Did you verify Tz information? (Didn’t look at the code)

The dagrun got created with the correct timezone, it follows the same pattern as other date elements in the forms.

@ashb
It's a UI change, to my knowledge I don't think we currently test things like this.

@kaxil This PR affects only old UI.
If this one is a go it needs to be merged for 1.10.2 before the final call :)


Kafkamanager does not come up

Created new firecamp cluster from scratch (used firecamp.template). Tried to start up kafkamanager service:
./firecamp-service-cli -cluster=firecamp-qa -region=us-east-1 -op=create-service -service-type=kafkamanager -service-name=kafkamanager-qa -km-heap-size=512 -km-zk-service=zoo-qa -km-user=user -km-passwd=pass
The Kafka Manager heap size is less than 4096. Please increase it for production system
2018-03-05 15:18:48.889010183 +0000 UTC The kafka manager service is created, wait for all containers running
2018-03-05 15:18:48.929875163 +0000 UTC wait the service containers running, RunningCount 0
...
2018-03-05 15:23:50.807640377 +0000 UTC not all service containers are running after 5m0s

firecamp-managesever log:
I0305 15:18:48.631132 1 route53.go:146] find hosted zone /hostedzone/ZL36HKC3OHITW for domain firecamp-qa-firecamp.com vpc vpc-d44e1eb1 us-east-1 requuid req-649f1bce27b440564fceda5f5d983ae6
I0305 15:18:48.631143 1 route53.go:58] get hostedZoneID /hostedzone/ZL36HKC3OHITW for domain firecamp-qa-firecamp.com vpc vpc-d44e1eb1 us-east-1 requuid req-649f1bce27b440564fceda5f5d983ae6
I0305 15:18:48.631154 1 service.go:135] get hostedZoneID /hostedzone/ZL36HKC3OHITW for domain firecamp-qa-firecamp.com vpc vpc-d44e1eb1 requuid req-649f1bce27b440564fceda5f5d983ae6 &{us-east-1 firecamp-qa kafkamanager-qa stateless}
I0305 15:18:48.638979 1 dynamodb_service.go:44] created service &{firecamp-qa kafkamanager-qa 4615cc0394144d224729850cfe4db686} requuid req-649f1bce27b440564fceda5f5d983ae6
I0305 15:18:48.639002 1 service.go:695] created service &{firecamp-qa kafkamanager-qa 4615cc0394144d224729850cfe4db686} requuid req-649f1bce27b440564fceda5f5d983ae6
I0305 15:18:48.644111 1 dynamodb_serviceattr.go:107] created service attr &{4615cc0394144d224729850cfe4db686 CREATING<PHONE_NUMBER>639010452 1 firecamp-qa kafkamanager-qa { { 0 0 false} { 0 0 false}} true firecamp-qa-firecamp.com /hostedzone/ZL36HKC3OHITW false <nil> {0 256 0 512} stateless} requuid req-649f1bce27b440564fceda5f5d983ae6
I0305 15:18:48.644147 1 service.go:798] created service attr in db &{4615cc0394144d224729850cfe4db686 CREATING<PHONE_NUMBER>639010452 1 firecamp-qa kafkamanager-qa { { 0 0 false} { 0 0 false}} true firecamp-qa-firecamp.com /hostedzone/ZL36HKC3OHITW false <nil> {0 256 0 512} stateless} requuid req-649f1bce27b440564fceda5f5d983ae6
I0305 15:18:48.644197 1 service.go:166] created service attr, requuid req-649f1bce27b440564fceda5f5d983ae6 &{4615cc0394144d224729850cfe4db686 CREATING<PHONE_NUMBER>639010452 1 firecamp-qa kafkamanager-qa { { 0 0 false} { 0 0 false}} true firecamp-qa-firecamp.com /hostedzone/ZL36HKC3OHITW false <nil> {0 256 0 512} stateless}
I0305 15:18:48.644241 1 dynamodb_serviceattr.go:144] update service status from CREATING to INITIALIZING requuid req-649f1bce27b440564fceda5f5d983ae6 &{4615cc0394144d224729850cfe4db686 INITIALIZING<PHONE_NUMBER>644215963 1 firecamp-qa kafkamanager-qa { { 0 0 false} { 0 0 false}} true firecamp-qa-firecamp.com /hostedzone/ZL36HKC3OHITW false <nil> {0 256 0 512} stateless}
I0305 15:18:48.649431 1 dynamodb_serviceattr.go:216] updated service attr &{4615cc0394144d224729850cfe4db686 CREATING<PHONE_NUMBER>639010452 1 firecamp-qa kafkamanager-qa { { 0 0 false} { 0 0 false}} true firecamp-qa-firecamp.com /hostedzone/ZL36HKC3OHITW false <nil> {0 256 0 512} stateless} to &{4615cc0394144d224729850cfe4db686 INITIALIZING<PHONE_NUMBER>644215963 1 firecamp-qa kafkamanager-qa { { 0 0 false} { 0 0 false}} true firecamp-qa-firecamp.com /hostedzone/ZL36HKC3OHITW false <nil> {0 256 0 512} stateless} requuid req-649f1bce27b440564fceda5f5d983ae6
I0305 15:18:48.649471 1 service.go:185] successfully created service, requuid req-649f1bce27b440564fceda5f5d983ae6 &{4615cc0394144d224729850cfe4db686 INITIALIZING<PHONE_NUMBER>644215963 1 firecamp-qa kafkamanager-qa { { 0 0 false} { 0 0 false}} true firecamp-qa-firecamp.com /hostedzone/ZL36HKC3OHITW false <nil> {0 256 0 512} stateless}
I0305 15:18:48.701299 1 cloudwatch.go:152] created log group firecamp-qa-kafkamanager-qa-4615cc0394144d224729850cfe4db686 requuid req-649f1bce27b440564fceda5f5d983ae6
I0305 15:18:48.734275 1 ecs.go:294] service is inactive kafkamanager-qa cluster firecamp-qa
I0305 15:18:48.760506 1 ecs.go:341] ListTaskDefinitionFamilies prefix firecamp-qa-kafkamanager-qa token <nil> resp {
Families: ["firecamp-qa-kafkamanager-qa"]
}

ECS console displays this error:
Status reason | CannotStartContainerError:  API error (500): failed to initialize logging driver:  ResourceNotFoundException: The specified log group does not exist. 	status code: 400, request id: ed451ab0-2088-11e8-a5e4-6f3c66053865

Looks like the service is still trying to create a log group in the outdated format:
 "requestParameters": { "logGroupName": "firecamp-firecamp-qa-kafkamanager-qa-b5291cb97e624299744ef6d9b9ce5ad9", "logStreamName": "kafkamanager-qa/firecamp-qa-kafkamanager-qa-container/544c5f99-e1e9-46b1-b50d-fe05a91aaaf7" },

which version did you install? For the latest release, are you using the https://s3.amazonaws.com/cloudstax/firecamp/releases/latest/templates/firecamp.template? Or your own bucket?

I installed the latest. Used firecamp.template from the project:
$ md5sum firecamp.template
9343fb2df76cfb85ed22ccea681a36fe  firecamp.template

yes, that is the latest template. Are you using your own bucket? If so, did you build the new manage image and upload to your bucket? Or you are simply using cloudstax bucket?

Yes, I put that template in my S3 bucket and specify it in the CloudFormation form.
No, I didn't build any new images. Just git pull'ed from your repo and uploaded to the bucket.

Could you please get the docker image version of the manageserver? find the node the manageserver container is running, and run docker images --digests. also run docker plugin ls. Thanks!

[root@ip-172-22-5-35 ec2-user]# docker images --digests
REPOSITORY                            TAG                 DIGEST                                                                    IMAGE ID            CREATED             SIZE
cloudstax/firecamp-manageserver       latest              sha256:486ae9288c7700d6ba3c6fe2d6f0e517debfb52e4a68a8f8f1c5ec2b83df69c3   3e32a7e9bc6a        16 hours ago        149MB
cloudstax/firecamp-kafka              1.0                 sha256:3e8c9a5c040c3df152bb4c9f36bf4bc45c991a1c0d75844d655b2aa1019a568e   60e845f96a27        2 days ago          132MB
cloudstax/firecamp-kafka-manager      1.3.3               sha256:4729587c2ed46a9a74b229ffaebb59f6066a731021a19fecbfa02d444e3e5f34   f4c015b25c38        6 days ago          382MB
cloudstax/firecamp-cassandra          3.11                sha256:3f17c100e112d7868645be79b0ea5394e4e9d506960f1c8158d1ba6cb25087e5   035d6748a9c9        2 weeks ago         320MB
cloudstax/firecamp-zookeeper          3.4                 sha256:ce8622fe8b8dfa1951f3bde63b637621b7ee5a049ec7715ccc756d95ee090cec   daa228143351        3 weeks ago         145MB
cloudstax/firecamp-amazon-ecs-agent   latest              sha256:f87d4c9f901f241502ddf5ab97da34bb8f7993121b324d8183794ca7c0b31196   c197350df554        5 weeks ago         26.9MB
[root@ip-172-22-5-35 ec2-user]# docker plugin ls
ID                  NAME                               DESCRIPTION                                     ENABLED
dea8905f6c44        cloudstax/firecamp-volume:latest   firecamp volume plugin for docker               true
07ac0c9fca04        cloudstax/firecamp-log:latest      firecamp log plugin for docker: consume lo...   true

Thanks! The env looks good.
The manage server actually created the correct log group.
I0305 15:18:48.701299 1 cloudwatch.go:152] created log group firecamp-qa-kafkamanager-qa-4615cc0394144d224729850cfe4db686 requuid req-649f1bce27b440564fceda5f5d983ae6

Where did you get below log?
"requestParameters": { "logGroupName": "firecamp-firecamp-qa-kafkamanager-qa-b5291cb97e624299744ef6d9b9ce5ad9", "logStreamName": "kafkamanager-qa/firecamp-qa-kafkamanager-qa-container/544c5f99-e1e9-46b1-b50d-fe05a91aaaf7" },

Just deployed a latest cluster and kafkamanager worked well. Beside firecamp.template, did you upload all latest templates such as firecamp-ecs.template? and the init.sh script?

Yes, I put that template in my S3 bucket and specify it in the CloudFormation form.
No, I didn't build any new images. Just git pull'ed from your repo and uploaded to the bucket.
No, I didn't upload any other templates nor init script. Should I? I didn't do that before..

Where did you get below log?

It's from CloudTrails

This is ridiculous. Last night I deleted kafkamanager service and today issued a command to create it again. And it went w/o any issues.. I'm sorry. Next time I will increase a number of attempts before reaching you.

Originally, thought you changed QSS3BucketName and QSS3KeyPrefix to your own bucket. If not, you don't have to upload other templates or init script.
It is weird. Good to know it works now. Please feel free to report it if you hit it again. We would like to further investigate any potential issue. Thanks!

Just figured this out. That cluster was created during that short period when you changed loggroup name from clustername-firecamp... to firecamp-clustername-firecamp...
So, when I attempted to create a service it used the very 1st task definition which contained the latter loggroup name. After I deleted the service along with its task definition, the new service creation went w/o issues.


Destrucutes orb

This fixes #2

Sure, will do :)

Looks great to me 👍  Thank you very much @lex111 and @beatbrot


⚠ Syncthing-KA-TM has degraded performance

In d5c81e1, Syncthing-KA-TM ($URL_SYNCTHING_MERZ_NIMBUS_TM) experienced degraded performance:

HTTP code: 200
Response time: 7445 ms

Resolved: Syncthing-KA-TM performance has improved in 5f8ced3 after 5 minutes.


Update code contributions

updated code contributions as discussed.
@mjt320, can you check whether your contributions have been correctly specified. I used the updated code in the new branch, but I might have overlooked something. I wasn't too sure about specifying the PKP models separately for fitting to enhancement and fitting to concentration. Should this be combined into one row or separate rows?

@petravanhoudt Should the notebooks/code_contributions_record.csv file be deleted? I think it was made as a copy (by me?), but I forget why it was copied. Anyways, if it's not being used it can be removed.
Also, I enabled a preview feature through netlify. Each PR should now show a preview of the website whenever a commit is made. For the current PR, the code contribution page looks good! (better than the old one)

Thanks @notZaki, yes I think the contributions csv in the notebooks should be removed. It is also not used anymore, because in the notebooks we refer to the one in the doc-directory. So it will be save to remove it.
I will check the incorrect dois. Maybe the doi-column is a bit confusing. I added it in case there is a link to the original code contribution (e.g. where the code has been used). The doi in the notes is related to the original published method, which is not necessarily a link to the contributed code. Suggestions how to do this, are welcome :)

Thanks @petravanhoudt
The descriptions look fine.
That reminds me that I need to add a test for linear Patlak fitting...


token-2022: Add CreateNativeMint instruction

The native mint for SPL token was forged by special case.  For token-2022, add an idempotent instruction to create the native mint instead. This means token-2022's WSOL mint doesn't get a vanity address, something we'll all need to find a way to live with.

This means token-2022's WSOL mint doesn't get a vanity address, something we'll all need to find a way to live with.

I hear all the cool kids are grinding seeds for vanity PDAs these days...

Where can I read about the motivation for this one?  Somewhat concerned that its going to be so we can track the supply and the implicit write contention on this account that that will entail

Where can I read about the motivation for this one?

It'd be nice to have a WSOL mint for token-2022 so that program instructions can potentially avoid pulling in two token programs. It also puts us on a path to deprecating token-OG over time. If we end up rolling token-2022 into the same program id, then the commit here gets reverted before that transplant happens

Somewhat concerned that its going to be so we can track the supply and the implicit write contention on this account that that will entail

I think you got smol screened or autocorrected. Come again?

Somewhat concerned that its going to be so we can track the supply and the implicit write contention on this account that that will entail

I think you got smol screened or autocorrected. Come again?

Haha. No that was a full keyboard and all the right words :sweat_smile:
I was getting at that if we're adding a mint with the intention of tracking WSOL supply (a point discussed at some point in the past), we now (effectively) have a couple hundred thousand mint authorities 'cause wrap becomes mintTo and there will likely be write-contention on that mint account

Haha. No that was a full keyboard and all the right words

hehe, problem was elsewhere then perhaps

I was getting at that if we're adding a mint with the intention of tracking WSOL supply (a point discussed at some point in the past), we now (effectively) have a couple hundred thousand mint authorities 'cause wrap becomes mintTo and there will likely be write-contention on that mint account

I don't get it still.  There's already a WSOL mint for token-og at https://explorer.solana.com/address/So11111111111111111111111111111111111111112. There's no additional functionality being added here beyond enabling the same for token-2022, in a way that doesn't require bank hacks

I was getting at that if we're adding a mint with the intention of tracking WSOL supply (a point discussed at some point in the past), we now (effectively) have a couple hundred thousand mint authorities 'cause wrap becomes mintTo and there will likely be write-contention on that mint account

I don't get it still. There's already a WSOL mint for token-og at https://explorer.solana.com/address/So11111111111111111111111111111111111111112. There's no additional functionality being added here beyond enabling the same for token-2022, in a way that doesn't require bank hacks

Got it.  So the motivation is not to track the supply of WSOL supply :heavy_check_mark:

Oh, no. Not even an option unless CloseAccount is reworked to accept a mint, or we require WSOL accounts be emptied before CloseAccount is called. Those are all things I have no interest in re-litigating for the sole benefit of the supply field in the WSOL mints


Analyzer does not handle implicitly hidden exports

The analyzer has the same problem as dart2js in http://dartbug.com/20935

It gives an ambiguous export error which I think is the intended behavior. It can be worked around with a hide on on the export from the dart: library.


registry/handlers/app: log healthcheck error before return

this error doesn't show up anywhere, so when the healthcheck does error the cause is often very mysterious.

Codecov Report
Patch coverage has no change and project coverage change: -0.02 :warning:

Comparison is base (87b2807) 55.90% compared to head (f6e1ab2) 55.88%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3948      +/-   ##
==========================================
- Coverage   55.90%   55.88%   -0.02%
==========================================
  Files         108      108
  Lines       10946    10949       +3
==========================================
  Hits         6119     6119
- Misses       4142     4145       +3
  Partials      685      685

Impacted Files
Coverage Δ

registry/handlers/app.go
47.01% <0.00%> (-0.20%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I've no real problem with this but beware these checks may be frequent to this can generate an influx of error logs - this can become a real issue if you have bugsnag hooks attached to your error logger, etc...

hmm I hadn't thought about it this way. is there something we can do about it? I can't really think of anything [that doesn't add significant work] 🤔

Yeah can't think of anything off the top of my head either 🤔 I'll tag in other maintainers so they can weigh in. I'll approve this as it's a small and handy change but let's see what others say.

these checks may be frequent to this can generate an influx of error logs

If your storage driver can't routinely stat /, that's a significant issue, so it might as well be noisy.


Links retrieved from the attribute article_url returns 404s

Hi!
When retrieving articles from the /articles route in the API the article_url attribut is not correct.
I suppose the last path segment should be omitted. Eg.
http://www.frolundaindians.com/artikel/5tr4aithl-24601/premiarseger should be http://www.frolundaindians.com/artikel/5tr4aithl-24601/
Thanks for a really great API!
/ Niklas

Thanks for your feedback. Unfortunately, that seems to be a data issue on the backend (Not sure if the Frölunda organization or the API is at fault though). This is only an unofficial client, so my ability to correct the issue is very limited. I suggest shooting an email to<EMAIL_ADDRESS>to get the issueto the maintainers of the  actual API, and in the meantime have the consumer of the API transform the incoming data
Thanks
Jakob

Ok, I see. I'll contact<EMAIL_ADDRESS>Thanks
Niklas


Cannot add decks to Craft list

When I add decks to the craft list, it does not appear on the craft list. For obvious reasons, the booster adviser also reports that I need to add decks to the craft list.
Here are the work-arounds/troubleshooting ideas that I have tried already for my account:

Access the deck list through the favorites section of browse decks and click on the anvil icon (on 1, 2, and 3 different decks all in different combinations).
Click on a desired deck and beneath the sideboard, click on "Add to craft list"
Use different browsers. (Started with Firefox, then Chrome, then Edge, which has no extensions).
Try the above methods on an Android phone through the web interface.
Use the above methods (anvil icon or "add to craft list") and waiting for some time before navigating away.

Hi! I have already tested the Craft List. I added deck and then opened Craft List. I saw the deck in it. So everything should work correctly.


Insert column to spreadsheet: the docs have it wrong

I believe the documentation on Google's site gives an incorrect example concerning inserting a column into a Google Spreadsheet. The URL in question is here: https://developers.google.com/sheets/samples/rowcolumn
In the "Insert an empty row or column" section, the example uses inheritBefore when in fact it should be inheritFromBefore. The error message from the server was thankfully verbose enough to point this out.

Thanks for reporting the bug!  Since this isn't an issue specific to this library, I've gone ahead and created an issue over here:
https://issuetracker.google.com/issues/77300253
Feel free to follow!


[ar] Translate index to arabic

This PR adds the minimal translation related to the file _index.md and splitting the old https://github.com/kubernetes/website/pull/44902 to smaller
Part of https://github.com/kubernetes/website/issues/37546 and https://github.com/kubernetes/website/issues/44682

/language ar

LGTM for Arabic

/assign @seokho-son

/lgtm

/lgtm
Thanks @mboukhalfa


feat: add lock parameter

add lock parameter for lmdb
The locking mechanism of lmdb is currently blocking this docarray PR
This pull request will not affect the behaviour of PQLite but instead will allow us to customize the configuration in docarray

LGTM !


JIT compiler error crashes Python for simple function

Dear jax team,
I'm sorry that I can't think of a more specific title. While looking into #5133 I have gotten the same crash from jax_jit.cc from a simple function including a newaxis:
import numpy as np
import jax
import jax.numpy as jnp

@jax.jit
def forward(x, y):
    return x[None] * y

nshots = 1200
dim = (28, 285)

a = np.random.rand(*dim)
b = np.random.rand(nshots, *dim)

fwd = forward(a, b)  # crash

crashes Python with
2020-12-08 16:09:15.463435: F external/org_tensorflow/tensorflow/compiler/xla/python/jax_jit.cc:771] Check failed: executable_handlers_out_tree.size() == 3 (5 vs. 3)
Aborted

I am building jax and jaxlib from source at fa15380d97be56b24008a0135beb37bd841f4dd9

Thanks a lot for reporting, and sorry for the inconvenience. Building from source is definitly legitimate, I had just not considered that case when submitting a CL.
You just need to use a more recent version of TF, the related CL should fix the issue. If not, feel free to say so and we will rollback.

Thank you @jblespiau for the swift response! I will try your PR and report if the bug persists.

Everything works! Thank you :+1:

Interestingly this turned up a hole in the set of the CI builds that we make. We regularly test a jaxlib + jax build with jaxlib from the latest TF head, but we don't actually test jaxlib pinned at the version in the WORKSPACE. This was a rare case where the former worker but the latter failed. Sorry for the breakage!


module initialization error

After adding the plugin i get this error in CloudWatch when calling any Lambda function:
module initialization error: Error
at Error (native)
at Object.fs.lstatSync (fs.js:839:18)
at Object.realpathSync (fs.js:1443:21)
at PATH.js:60409:38
at Array.map (native)
at Object.<anonymous> (PATH.js:60408:3)
at Object.291.fs (PATH.js:60539:4)
at s (PATH.js:1:683)
at PATH.js:1:734
at Object.278.PATH.js:57841:16)

This seems to caused by these lines in Uglify.js:

var FILES = exports.FILES = [
    "../lib/utils.js",
    "../lib/ast.js",
    "../lib/parse.js",
    "../lib/transform.js",
    "../lib/scope.js",
    "../lib/output.js",
    "../lib/compress.js",
    "../lib/sourcemap.js",
    "../lib/mozilla-ast.js"
].map(function(file){
    return path.join(path.dirname(fs.realpathSync(__filename)), file);
});

@amitaymolko Module initialization error happens when the lambda path is not set correctly for the handler. Share one of the failing functions lambda path in serverless.yml and your optimize debug output.
Other than that if Uglify is the root cause, is optimize babelifying the code correctly before uglify? Set minify to false and debug to true and check the optimize bundle in _optimizefolder.

@goncaloneves I found that the cause of the issue was that jade had Uglify as a dependancy and not a devDependancy.
Moving over to pug fixed the issue


2.0 branch doesn't work

It worked fine a few days ago.
It prompts for if_eq and based on the answer it outputs different errors

It looks like updating vue-cli fixed the issue


geomag: init at 0.9.2015

Description of changes
geomag python package

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python311Packages.geomag
python311Packages.geomag.dist
python312Packages.geomag
python312Packages.geomag.dist

@GrahamcOfBorg build python311Packages.geomag python312Packages.geomag

The commit message should also be python3Packages.geomag: init at 0.9.2015 since this goes into the python module packageset

The commit message should also be python3Packages.geomag: init at 0.9.2015 since this goes into the python module packageset

Updated commit message

@GrahamcOfBorg build python311Packages.geomag python312Packages.geomag


Catch KeyPermanentlyInvalidatedException with Asymmetric key

When dealing with AES encryption we would get KeyPermanentlyInvalidatedException if new fingerprint was added.
Is it possible to detect fingerprints enrolments with asymmetric keys (RSA)?
I have tried but no success so far

I am closing this issue/PR, as it has been migrated to the new repo linked above in the comments. Thank you!


Feature: Alias management

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #405 (c8b8115) into index-operation (8c61ffb) will increase coverage by 0.10%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##           index-operation     #405      +/-   ##
===================================================
+ Coverage            57.57%   57.67%   +0.10%
===================================================
  Files                  222      229       +7
  Lines                 7331     7540     +209
  Branches              1188     1223      +35
===================================================
+ Hits                  4221     4349     +128
- Misses                2810     2887      +77
- Partials               300      304       +4

Impacted Files
Coverage Δ

...ement-dashboards-plugin/public/pages/Main/Main.tsx
6.25% <0.00%> (-0.21%)
:arrow_down:

...c/pages/CreateIndex/containers/IndexForm/index.tsx
82.55% <0.00%> (-0.09%)
:arrow_down:

...gement-dashboards-plugin/public/utils/constants.ts
100.00% <0.00%> (ø)

...ic/pages/Aliases/containers/AliasActions/index.tsx
100.00% <0.00%> (ø)

...ds-plugin/public/pages/Aliases/utils/constants.tsx
100.00% <0.00%> (ø)

...Aliases/components/IndexControls/IndexControls.tsx
42.85% <0.00%> (ø)

...s/containers/DeleteAliasModal/DeleteAliasModal.tsx
90.47% <0.00%> (ø)

...lic/pages/Aliases/containers/CreateAlias/index.tsx
40.00% <0.00%> (ø)

...ds-plugin/public/components/RemoteSelect/index.tsx
100.00% <0.00%> (ø)

...ublic/pages/Aliases/containers/Aliases/Aliases.tsx
51.61% <0.00%> (ø)

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Topic enforcement

We would like to be able to enforce the topic in channels, the idea is that:

Foobot will store the topic for each channel
If any admin changes the topic Foobot will allow this and update its store
if any non-admin that changes the topic Foobot will revert to the last admin set topic

Initial POC https://github.com/iosdevelopershq/Camille/tree/topic-monitor


Crash when sidebar config object is not defined

I don't use the sidebar feature, so my config doesn't have the sidebar config object. This results in cokeline crashing whenever I open NvimTree on the left (the right side is unaffected):
E5108: Error executing lua ...l/share/nvim/lazy/nvim-cokeline/lua/cokeline/sidebar.lua:146: attempt to index a nil value
stack traceback:
	...l/share/nvim/lazy/nvim-cokeline/lua/cokeline/sidebar.lua:146: in function 'get_components'
	...share/nvim/lazy/nvim-cokeline/lua/cokeline/rendering.lua:107: in function 'prepare'
	...share/nvim/lazy/nvim-cokeline/lua/cokeline/rendering.lua:220: in function <...share/nvim/lazy/nvim-cokeline/lua/cokeline/rendering.lua:219>

If I add a non-empty sidebar block, for example:
    sidebar = {
        filetype = { 'aerial' },
        components = {
            {
                text = function(buf)
                    return ' ' .. buf.filetype
                end,
                fg = colors.yellow,
                bg = function() return require('cokeline.hlgroups').get_hl_attr('NvimTreeNormal', 'bg') end,
                bold = true,
            },
        },
    },

cokeline operates normally (even though I don't specify NvimTree as a sidebar filetype).

Thanks for reporting, I'll look into this ASAP. Could you provide a minimal init for testing? Thanks!

This should be enough to reproduce I think.
require('cokeline').setup {
  components = { },
}

@willothy I ran into this issue as well (finally updated my plugins). The problem you are running into is in sidebar.lua:115-149
Specifically this little bit of logic here
-- Starting at line 138
  if width > sidebar_width then
    sort(sidebar_components, rendering.by_decreasing_priority)
    components.shorten(sidebar_components, sidebar_width)
    sort(sidebar_components, rendering.by_increasing_index)
  elseif width < sidebar_width then
    local space_left = sidebar_width - width
    local last = #sidebar_components
    sidebar_components[last].text = sidebar_components[last].text
      .. rep(" ", space_left)
    sidebar_components[last].width = sidebar_components[last].width
      + space_left
  end

This logic assumes that something is in your sidebar_components. This assumption is unsafe as the only way anything is in sidebar_components is if states.sidebar has a length of greater than 0. However looking at the default configuration (found in config.lua:190-200) we can see that the only way state.sidebar is populated is if config.sidebar.components is not nil and the default configuration for nvim-cokeline indeed specifies that config.sidebar.components is not nil, rather its an empty table
So in short, the default configuration provided by cokeline sets config.sidebar.components to an empty table, which does not fail a truthy check (here is a repl example showing this)

Because this empty table is truthy, state.sidebar is never populated with something and thus you get a nil index error at sidebar.lua:146 due to attempting to index an empty table and concat a string to a nil attribute sidebar_components[last].text .. rep(" ", space_left)

#177 addresses this issue. Tested with no sidebar (the default configuration provided by cokeline) and with a set of custom sidebar components

Thanks for the PR! Sorry for not getting to this, I've been a bit busy recently.

Fixed in #177

Thanks for the PR! Sorry for not getting to this, I've been a bit busy recently.

You owe us nothing :) thanks for picking up this project, maintaining and improving it! I'm glad I could help

Totally, thank you! I appreciate the contributions :)


Scroll for typeahead

#1168 Fixed scroll for typeahead.

Current coverage is 86.64% (diff: 80.83%)

Merging #1189 into development will increase coverage by 1.02%

@@           development      #1189   diff @@
=============================================
  Files               35         35
  Lines             1280       1348    +68
  Methods            228        239    +11
  Messages             0          0
  Branches           213        229    +16
=============================================
+ Hits              1096       1168    +72
+ Misses             184        180     -4
  Partials             0          0

Powered by Codecov. Last update eaba9ca...8647c81


README file

A professional README file must be created outlining the application and the usage.

The readme file has been completed with description, usage, credits and licensing.


Fixed incorrect guidance regarding general channel

As per mail thread on 3/23 (from Dan Herron)

I'm currently working on this file in another branch.  I've made the change there too since the file has been renamed and may not pick up the change.


commit db during replays when replay optimizations are disabled (1.7 backport)

Change Description
porting fix made to develop for committing database on replay with disable-replay-opts
Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

This is actually not needed as the call to fork_db.add will eventually call the db.commit


Enable luminance range = 0-255, 16-235, 16-255???

Please explain :)

In some video standards, the actual range for luminance is 16–235 instead of 0–255. Some cameras let the users set the range they want.


Portal component's wrapper div cannot be styled

Describe the bug
I'm using the Portal component for a toast element where I noticed that the wrapper div element is messing up the styles of the elements.
I know that this div is required, but is it possible to at least add the ability to add the class attribute for this element for these edge cases?
Your Example Website or App
https://stackblitz.com/edit/solidjs-templates-cshflq?file=src%2FApp.tsx
Steps to Reproduce the Bug or Issue

Go to the StackBlitz demo
Click the button to show the toast
You will see that the styles are messed up
If you inspect the elements and manually remove the wrapping div the layout will be fixed

Expected behavior
I expected to at least be able to add the class attribute to the Portal's wrapper div.
I would also be great if we can pass any attributes down to the div element.
Screenshots or Videos
No response
Platform

OS: Linux
Browser: Chrome
Version: 116

Additional context
Sorry if this issue is too specific, feel free to close it if it's out of scope.

You could set the "ref" attribute on the Portal like so:
<Portal ref={x => x.style.display = "contents"} />

This will make the div behave like it wasn't even there (At least visually)


Cert file permissions change after pod restarts

Do you want to request a feature or report a bug?

Bug

What did you do?

After a traefik pod restart in k8s, the cert file permissions turn to something else then 600 on my /data/letsencrypt.json file. Which makes traefik skip this cert resolver. Traefik logs give me:

The ACME resolver "letsencrypt" is skipped from the resolvers list because: unable to get ACME account: permissions 660 for /data/letsencrypt.json are too open, please use 600

Manually i then changed the permissions to that file.
$ chmod 600 /data/letsencrypt.json
$ ls -la /data/letsencrypt.json
-rw-------    1 65532    65532        70349 Mar 26 18:22 /data/letsencrypt.json

However, the certs still fail to load. When i restart the pod, the permissions change again to:
$ ls -la /data/letsencrypt.json
-rw-rw----    1 65532    65532        70349 Mar 26 18:22 /data/letsencrypt.json

Am i doing something wrong?
What did you expect to see?
The SSL certificates that are stored in /data/letsencrypt.json, and persistent in a PVC, should be reloaded on a pod restart.
What did you see instead?
SSL Error on websites
NET::ERR_CERT_AUTHORITY_INVALID
Subject: TRAEFIK DEFAULT CERT

Issuer: TRAEFIK DEFAULT CERT

Output of traefik version: (What version of Traefik are you using?)

Version:      2.4.8
Codename:     livarot
Go version:   go1.16.2
Built:        2021-03-23T15:48:39Z
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
globalArguments:
  - --api.insecure
  - --accesslog
  - --log.level=INFO
  -<EMAIL_ADDRESS>  - --certificatesresolvers.letsencrypt.acme.storage=/data/letsencrypt.json
  - --certificatesResolvers.letsencrypt.acme.dnschallenge=true
  - --certificatesResolvers.letsencrypt.acme.dnschallenge.provider=cloudflare

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
N/A

found a dupe: https://github.com/traefik/traefik-helm-chart/issues/396


provider hashicorp/aws version issue

Hi Team,
Today I am getting the below error related to the provider version, so please let me know what changes are required
till yesterday it was working fine with same version.
error
│ Could not retrieve the list of available versions for provider hashicorp/aws: no available releases match the given constraints >= 2.42.0, >= 2.54.0, >= 2.70.0, >= 3.7.1, >= 3.72.0, <
│ 4.0.0, >= 4.45.0
module version: latest
EKS : 1.24
terraform "~> 1.0"
hashicorp/aws ">= 3.72"
hashicorp/kubernetes  ">= 2.10"
gavinbunney/kubectl  ">= 1.7.0"
tls   "<4.0.0"

Please provide a reproduction


Nova pkg module is not working as expected

Command: __salt__[‘pkg.version’](“openssh-server”) return None but command rpm -q “openssh-server” returns openssh-server-6.6.1p1-25.61.amzn1.x86_64. Looks like something wrong in salt command ? As per my understanding the first command (the salt one) should return the version details. (Tried using pkg.py file)

What operating system is the host running? Does it show up in yum list installed? I'm pretty sure salt's pkg.version is using yum, not rpm. It's possible their results differ.

I was using Amazon Linux.
yes the above command yum list installed is working.
__salt__['pkg.version']('openssh-server') shows bank but if I use __salt__['pkg.latest_version']('openssh-server'), it shows error as
`[ERROR   ] Command '['yum', '--quiet', 'clean', 'expire-cache']' failed with return code: 1
[ERROR   ] output: There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:
/usr/lib64/python2.7/lib-dynload/_io.so: undefined symbol: _PyErr_ReplaceException
Please install a package which provides this module, or
verify that the module is installed correctly.
It's possible that the above module doesn't match the
current version of Python, which is:
2.7.5 (default, Nov  6 2016, 00:28:07)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]
If you cannot solve this problem yourself, please go to
the yum faq at:
http://yum.baseurl.org/wiki/Faq
[ERROR   ] Problem encountered getting latest version for the following package(s): openssh-server. Stderr follows:
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:
/usr/lib64/python2.7/lib-dynload/_io.so: undefined symbol: _PyErr_ReplaceException
Please install a package which provides this module, or
verify that the module is installed correctly.
It's possible that the above module doesn't match the
current version of Python, which is:
2.7.5 (default, Nov  6 2016, 00:28:07)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]
If you cannot solve this problem yourself, please go to
the yum faq at:
http://yum.baseurl.org/wiki/Faq`

Fascinating. Seems like it might be a salt error, I wonder if upgrading our underlying salt version might resolve this?
Also why is python involved at all if it's just shelling out to yum --quiet clean expire-cache? Very odd. I'll have to see if I can reproduce it.
You also might try installing salt and testing with salt-call just to see if you can reproduce in salt.

I can reproduce this. I'm betting it's something related to our pyinstaller build. I'm wondering if it might be as simple as including yum in our hidden imports list. I'll make a new build when I have time and see if that fixes it.

I've tracked it down to something related to pyinstaller. pkg.version works if you do a python setup.py install for hubble instead.

The wonderful @fossam has helped me track this down to a shared library issue. Basically, when rpm is called under hubble, it uses the rpmlib shared libraries that ship with hubble. This is why it works when you execute the commands outside of hubble, and why it works when you just do a python install.
@anuragpaliwal80 Can you try deleting the shared libraries and see if it fixes things (command below)? If so, I'll figure out a solution in my packaging, either leaving out those shared libraries or building directly on amazon linux.
rm /opt/hubble/hubble-libs/librpm*

Oh yes, it working now. Thanks

Perfect. Leaving this open until I automate the removal of those shared libraries in the package building stages.


0.12.1 - Where is ffmpeg-core.worker.js file

Is your feature request related to a problem? Please describe.

Versions 0.11.x had ffmpeg-core.worker.js published, https://unpkg.com/browse/<EMAIL_ADDRESS>Version 0.12.x has no such thing, https://unpkg.com/browse/<EMAIL_ADDRESS>
Describe the solution you'd like
Guide to obtain this file
Describe alternatives you've considered
Revert to 0.11.x

I used this, notice esm instead of umd
      const baseURL = "https://unpkg.com/<EMAIL_ADDRESS>      await ffmpeg.current.load({
        coreURL: await toBlobURL(
          `${baseURL}/ffmpeg-core.js`,
          "text/javascript"
        ),
        wasmURL: await toBlobURL(
          `${baseURL}/ffmpeg-core.wasm`,
          "application/wasm"
        ),
      });

where toBlobURL is imported from @ffmpeg/util.

ffmpeg-core.worker.js is in another package called @ffmpeg/core-mt.
You can find it here: https://unpkg.com/<EMAIL_ADDRESS>


Implement schema text

Example file: https://github.com/MNoya/DotaCraft/blob/7791535a1977610defffb815aab58617235546da/content/dota_addons/dotacraft/models/elven_farm.vmdl

Appears to be a deprecated format of valves, as it got replaced by KV3 for particles at reborn launch, but a couple of observations:

It starts off with a header near identical to KV3's,
<!-- schema text {7e125a45-3d83-4043-b292-9e24f8ef27b4} generic {198980d8-3a93-4919-b4c6-dd1fb07a3a4b} -->

It has two methods of defining arrays, DataType[] array = [value, value2, value3] and DataType(n) array = (value, value2, value3, valuen). The former is multi line, the later is inline. (potentially object vs primitive)

It has "pointer" support for object arrays, marked by DataType*[], and &ValueVariable.

Defines objects by DataType {} and DataType variable = DataType {} with root objects just being DataType variable {}

Appears to have int, uint, float, string, bool and symbol as primitives.

symbol appears to be able to be natural numbers, and as the STATIC keyword

float appears to be formatted to have 6 decimal places.


Platform altyapı çok kötü

Clear and concise description of the problem
Site arkaplanı derme çatma
Suggested solution

code  arkanplan

Alternative
No response
Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Testnette olduğunu hala  anlayamadınmi


reporting: Netflow validation listen vs. egress

https://github.com/opnsense/core/issues/2197 changed the text to make it clearer, but it's further from the truth now. What we need is a validation between listen and egress so that we can confirm egress is a subset of listening interfaces.

https://github.com/opnsense/core/commit/658e3d00924a857d8db9acda4f90d8d2d97ccb50 adds the validation

❤


Deprecate swap function in ArrayExtensions

Deprecate swap(from:, to:) in ArrayExtensions in favor of Swift's native swapAt method.

I think we should deprecate push and pop functions as well


added arch:ppc64le and permission fix for the same

Hi,
I request you to please review as the builds are passing, please let me know if there is more to be looked into.
Thanks

LGTM
@jwhonce PTAL.  @edsantiago or @cevich if you have a quick second for an eyeball...

@ezeeyahoo out of curiosity, is this really running on ppc64 hardware in travis?  If so, cool!

@ezeeyahoo ping, would love to merge this once comments are addressed.  Thanks!

@jwhonce Done 👍🏼

I am trying without -f, I will remove if it goes fine on Travis

Please let me know if this look messy and you want me to create a new PR, abandoning this one.

Package is deprecated and being archived.


Show all properties in the HTML view

Added the additional fields to the handlebars templates for metadata properties.

Coverage remained the same at 78.695% when pulling 81df2d54e5e36e760378a6d2388b17fb652468a4 on kburger-dtl:feature/all-properties-gui into 22ac32ff53c4fde9ce95f89c12f1d5caec5a7d6d on DTL-FAIRData:develop.


fix broken link in documentation

this is just a quick fix so that cargo doc will pass the linter.

Thanks for catching that one!
The changelog entry should go into the Docs section.


Header UI updates

New header design:

Header should remain fixed to the top of the page.
Functionality is as before, things are just moved around and look different.
For now, logged-in users should just see a hamburger menu instead of the "sign in" button. In the future we'll likely want to move the items in that menu elsewhere in the UI but that can be done as a follow up.

Any white github logo is fine.

Done.


how to train a model

First of all, I think  this is a nice work.So  I want  to know  how  to  train a   model ,what can I do.
Look forward to your reply.

Hi! This repository has demo code. You can check #17 for method details and write training pipeline. Possibly neighbor repository will help.

Hope, it is clear now.


Add AltiVec-optimized adler32 and slide_hash for PowerPC

PowerPC is alive! :O

@timofonic PowerPC never died... Some Linux distributions dropped mainline support for 32-bit PowerPC, but 64-bit support is still in early stage. A lot of modern hardware runs on PowerPC but no-one really advertises it as ARM and Intel want to keep the top 2 spots. AMD processors are actually ARM internally even though they use Intel-compatible instruction set.

@mtl1979 Really? I would love to know more about actual uses of PowerPC. I had a Pegasos II and ran MorphOS on it, but I had a terrible accident that destroyed the machine. Everone thinks PowerPC is dead because it isn't in the desktop world.
AMD processors are ARM internally? I didn't know that! I knew X86 CPUs have a translator circuitry and such by using microcode and it seems ARM to be more hardwired.

@timofonic Some of the game consoles use PowerPC chips. As far as I know some recent AMD chips are based on ARMv8-A (AArch64).

I'd really like to see the unaligned_ok related fixes as a preparatory commit, rather than a fix after the fact. Might even be worth pulling as a separate PR, since it is not only altivec-related.

@Dead2, PowerPC is currently the only architecture that needs the unaligned_ok workaround.

@mtl1979 what PPC machine do you use?

@nmoinvaz The original code was written inside qemu... Only difference to real PPC is that unaligned access doesn't raise CPU exception, it only causes address to be realigned and as such the output is garbage.

Please rebase this, then maybe we can find someone with the hardware to test it.

Rebased and cleaned up.

Do we need to add AltiVec to readme list of features?

@nmoinvaz I added to readme ;)

Sorry for the so many comments. It is look really good.

@nmoinvaz I don't mind cleaning up my own pull requests... It might be middle of the night here but I wasn't sleeping.

@mscastanho @iii-i Do either of you have access to hardware and the time to verify that this AltiVec optimization works and is faster than before the PR?
Any other feedback is of course also appreciated.

@mscastanho @iii-i Do either of you have access to hardware and the time to verify that this AltiVec optimization works and is faster than before the PR?

@Dead2 Sure. I can test it later today

I tried to test the code on the oldest processor I have access to (POWER7). It
has support for VMX but does not benefit from the POWER8 optimizations. I was
not able to run the entire testsuite, because it had a very old CMake. Since it
had a very old glibc as well (2.11) it failed to detect VMX instructions support
(didn't recognize getauxval), but the system's GCC 4.3.4 had support for
intrinsics, which caused build problems:
$ ./configure
[...]
Checking for AltiVec intrinsics ... Yes.
Check whether VMX instructions are available ... No.
Check whether POWER8 instructions are available ... No.
ARCH: powerpc64
Using arch directory: arch/power
Architecture-specific static object files: adler32_vmx.o slide_vmx.o
Architecture-specific shared object files: adler32_vmx.lo slide_vmx.lo

$ make
[...]
gcc -O2  -std=c99 -Wall -D_LARGEFILE64_SOURCE=1 -DWITH_GZFILEOP -DHAVE_VISIBILITY_HIDDEN -DHAVE_VISIBILITY_INTERNAL -DHAVE_BUILTIN_CTZ -DHAVE_BUILTIN_CTZLL -DPPC_VMX -DPPC_VMX_ADLER32 -DPPC_VMX_SLIDEHASH -I/home/mscastanho/zlib-ng -c -o functable.o /home/mscastanho/zlib-ng/functable.c
/home/mscastanho/zlib-ng/functable.c: In function ‘slide_hash_stub’:
/home/mscastanho/zlib-ng/functable.c:214: error: ‘power_cpu_has_vmx’ undeclared (first use in this function)
/home/mscastanho/zlib-ng/functable.c:214: error: (Each undeclared identifier is reported only once
/home/mscastanho/zlib-ng/functable.c:214: error: for each function it appears in.)
/home/mscastanho/zlib-ng/functable.c: In function ‘adler32_stub’:
/home/mscastanho/zlib-ng/functable.c:245: error: ‘power_cpu_has_vmx’ undeclared (first use in this function)

I'm not sure if we want to worry about this combination of things.
Using a slightly newer toolchain (glibc 2.18 and GCC 4.8.5) I was able to
properly compile everything and the very basic tests (make check) passed.
I then ran the benchmark on a POWER8 and compared with and without VMX
optimizations, to try to mimic the scenario of a POWER7 (or older).
Force no optimization:
$ ./configure --without-altivec --without-power8 && make
$ ../deflatebench/deflatebench.py --gen

 Tool: minigzip   Levels: 0-9
 Runs: 15         Trim worst: 5

 Level   Comp   Comptime min/avg/max/stddev  Decomptime min/avg/max/stddev  Compressed size
 0    100.008%      0.660/0.705/0.750/0.025        0.439/0.638/0.677/0.071      536,124,384
 1     54.240%      3.960/3.992/4.020/0.020        1.083/1.116/1.133/0.018      154,205,532
 2     43.987%      3.007/3.031/3.047/0.013        0.532/0.586/0.600/0.020       62,758,792
 3     42.526%      2.764/2.778/2.796/0.011        0.404/0.430/0.453/0.017       47,290,047
 4     41.837%      2.482/2.508/2.523/0.012        0.360/0.370/0.380/0.008       39,939,949
 5     41.384%      2.477/2.491/2.506/0.010        0.356/0.371/0.378/0.008       39,507,653
 6     41.246%      2.273/2.284/2.293/0.006        0.301/0.307/0.312/0.005       32,885,139
 7     41.044%      2.185/2.199/2.206/0.009        0.218/0.241/0.256/0.010       26,265,857
 8     41.053%      1.940/1.965/1.980/0.013        0.181/0.192/0.201/0.006       19,811,261
 9     41.043%      2.101/2.116/2.123/0.007        0.171/0.189/0.201/0.010       19,806,112

 avg1  48.837%                        2.407                          0.444
 avg2  54.263%                        2.674                          0.493
 tot                                240.695                         44.399      978,594,726

Force using only VMX optimizations (this PR):
$ ./configure --without-power8 && make
$ ../deflatebench/deflatebench.py --gen

 Tool: minigzip   Levels: 0-9
 Runs: 15         Trim worst: 5

 Level   Comp   Comptime min/avg/max/stddev  Decomptime min/avg/max/stddev  Compressed size
 0    100.008%      0.662/0.699/0.728/0.024        0.641/0.671/0.701/0.022      536,124,384
 1     54.240%      2.378/2.396/2.419/0.015        1.073/1.109/1.129/0.018      154,205,532
 2     43.987%      2.084/2.112/2.129/0.014        0.544/0.572/0.587/0.014       62,758,792
 3     42.526%      2.060/2.088/2.099/0.012        0.420/0.440/0.449/0.012       47,290,047
 4     41.837%      1.903/1.923/1.935/0.012        0.359/0.373/0.377/0.006       39,939,949
 5     41.384%      1.878/1.894/1.908/0.010        0.365/0.374/0.385/0.005       39,507,653
 6     41.246%      1.763/1.786/1.802/0.013        0.289/0.311/0.319/0.011       32,885,139
 7     41.044%      1.787/1.801/1.808/0.008        0.224/0.242/0.255/0.011       26,265,857
 8     41.053%      1.651/1.670/1.680/0.009        0.170/0.190/0.200/0.011       19,811,261
 9     41.043%      1.811/1.822/1.830/0.008        0.170/0.185/0.199/0.011       19,806,112

 avg1  48.837%                        1.819                          0.447
 avg2  54.263%                        2.021                          0.496
 tot                                181.897                         44.663      978,594,726

So the results look good.
I still haven't taken a deeper look at the code. Will try tomorrow.

Checking for AltiVec intrinsics ... Yes.
Check whether VMX instructions are available ... No.

I changed that both tests must pass. That should disable VMX support if getauxval isn't available.

@mtl1979 Comparing slide_vmx with slide_power8, they look roughly equivalent but I believe this new implementation is slightly better. However, if we keep the -mno-vsx flag we may loose some optimization opportunities from the compiler (e.g. gcc 9 does not use mtvsrd to setup the vector before splatting, instead uses a store+load).
What if we remove slide_power8.c, and compile slide_vmx.c with -mcpu=power8 to generate slide_power8?
Then slide_vmx would be compiled twice, with different flags, to generate 2 versions of the optimization.

@mscastanho I think it's because I combined parts of both to get a version that requires minimal amount of editing of files already in the repository...
A lot of the other files had changed since I wrote the original version, so it had to be rewritten.
My original patch had optimized versions for both VMX and VSX but I separated them as getting them reviewed one by one was going to be easier.

Rebased again to fix merge conflict. Some minor cleanups...


Tilemap(Sprite texture region) lost focus in image imported

Godot 3.0 beta.
When I'm going to create a tilemap I have to add a sprite node with staticbody2d and collisionshape2d.
The texture (imported in sprite) non keep the original design as show in the examples below.
After your suggestion I tried to find Texture filtering without success. I tried in documentation  (godot 2) but I still don;t get where this option can be . can you help me please? Thank you.
Imported:

Original:

Please follow the given issue template when filing issues. You report is lacking crucial information, like the Godot version..
At any rate, disable texture filtering and this will work as expected.

I update my comments in main page.

Click on your TileSet image in the FileSystem dock and then select the Import dock, disable filter there and Re-import.
This github isn't for support though, it's for actual bug tracking, you'd be better off asking for instructions on how to do certain things on the QA board or the IRC/Discord chats.

Thank you for your help. :) I try to do what you suggest.


[S2GRAPH-26] Apply squash optimization on mutateElements and make it default behavior on Storage.

Change Graph.mutateElements to use mutateEdges and mutateVertices to use squash optimization.

+1

This PR is no longer valid due to other changes.
So I think this issue should be closed.


Env Variables in baseUrl of openapi handler are not replaced

Describe the bug
When an env variable placeholder is inside the baseUrl String it will not be replaced by the corresponding value of the environment.
To Reproduce

in .meshrc.yml add a openapi handler and for the value of baseUrl set an env var like this

sources:
  - name: StackExchange
    handler:
      openapi:
        source: https://raw.githubusercontent.com/grokify/api-specs/master/stackexchange/stackexchange-api-v2.2_openapi-v3.0.yaml
        baseUrl: "{env.BASE_URL}"

in your environment set the variable like this BASE_URL=https://api.stackexchange.com/2.2

-> See also this codesandbox
https://codesandbox.io/s/graphql-mesh-openapi-baseurl-xg58p?file=/.meshrc.yml:263-277
Expected behavior
Like described in the documentation the '{env.BASE_URL}' in baseUrl should be replaced by 'https://api.stackexchange.com/2.2'
Environment:

"@graphql-mesh/cli": "^0.33.3"
"@graphql-mesh/openapi": "^0.18.4"
NodeJS:14

Additional context
This lines of code seems to be https://github.com/Urigo/graphql-mesh/blob/7a7bcf0505e46051c6e430e3fda2eade4aacac75/packages/handlers/openapi/src/index.ts#L200-L202 interesting to me... Unfortunately I don't understand the difference of these two values. In my tests they are always the same value...

Work for me with<EMAIL_ADDRESS>

Thanks for the super fast fix! 🚀

@ardatan I had the same problem, thanks for the fix.
But could there also be an issue with accessing the context the same way ?

https://www.graphql-mesh.com/docs/handlers/openapi#advanced-cookies-handling
We can't access the endpoints that need auth because of that. I think this might be the same kind of issue.

@gablabelle I think your issue might be related to #2633
I am accessing context in headers exactly like this "headerValue": "{context.request.header.myValue}" and it works for me.
That makes me think your case is broken due to array-like syntax, as reported in #2633

@gablabelle I think your issue might be related to #2633
I am accessing context in headers exactly like this headerValue: "{context.request.headers.myValue}" and it works for me.
That makes me think your case is broken due to array-like syntax, as reported in #2633

Thanks for the heads up! Subscribing to #2633

Hello, I'm running into an issue where the baseUrl is dynamic and served from an environment variable within a Next.js application. When I run my mesh build command, the environment variables are not picked up from my .env file.
Any thoughts?

It is Next.js should pick it up from .env. In other words, Mesh artifacts are not capable of reading .env file by itself because reading from file system is something your environment responsible of.

I managed to get it working by omitting the env. from the yaml file, contrary to the document I was looking at here:
https://www.the-guild.dev/graphql/mesh/docs/handlers/openapi

${ENV_VAR} puts the variable into the artifacts as a static value while {env.ENV.VAR} makes it dynamic. Notice the missing $ sign in the first one. If you still have a different behavior, please create  a new issue with a minimal reproduction on CodeSandbox or StackBlitz, thanks.


Test fileChecksum from ocean.py.

Fixes #114 .
Changes proposed in this PR:

Also, until we merge the branch in provider, you can set the provider version to ptAlgs in tox (?)


Generate header file (for IDA)

I won't do it. Contributions are welcomed!

PS: I attempted many times to correctly generate valid .h files - but unfortunately I never succeeded in doing so.
I also attempted in generating a JSON file containing the types and methods metadata - so I could use the program (Ghidra in my case) scripting to generate the structures and stuff.

PS: I attempted many times to correctly generate valid .h files - but unfortunately I never succeeded in doing so.
I also attempted in generating a JSON file containing the types and methods metadata - so I could use the program (Ghidra in my case) scripting to generate the structures and stuff.

https://github.com/Perfare/Il2CppDumper
I think we can do the same in runtime.
I'm trying reimplement it from Il2CppDumper

I researched it, the theory is feasible, but the memory needs to be searched, and it may not be able to be searched (if there is special treatment)

Maybe a better way is to use Il2CppDumper with the dumped global-metadata.dat and binary

researched it, the theory is feasible, but the memory needs to be searched, and it may not be able to be searched (if there is special treatment)

I don't understand this - would you tell me why memory needs to ne searched?

researched it, the theory is feasible, but the memory needs to be searched, and it may not be able to be searched (if there is special treatment)

I don't understand this - would you tell me why memory needs to ne searched?

We could not get enough imformation through the exported il2cpp api, such as all the typeinfo. The typeinfo table only exsist in global-metadata and there is no way to access it from any known struct. It has to be searched from memory. To dump with frida, we have to know where the global-metadata, the MetadataRegistration and the CodeRegistration is.

This is the same as what Il2CppDumper does. So just use Il2CppDumper. frida-il2cpp-bridge should work as a hook tool, not a dumper, I think.

We could not get enough imformation through the exported il2cpp api, such as all the typeinfo. The typeinfo table only exsist in global-metadata and there is no way to access it from any known struct. It has to be searched from memory. To dump with frida, we have to know where the global-metadata, the MetadataRegistration and the CodeRegistration is.

This is correct, but there are two things you should know.
First, we could find where the global-metadata is, in fact frida is capable of scanning memory - but the biggest problem here is dealing with customized il2cpp structures. It's so easy to change such structs (i.e. change field orders, adding fake fields and so on) I don't think it's worth it.
It's also true there's no way to access all the typeinfo using the il2cpp exported api: I noticed inflated types (i.e. generics with actual types) are missing. If these are the only types missing, we can "easily" check the existence of these (calling Il2Cpp.Class::inflate against every value type and System.Object - reference types shares the same type info, actually).

This is the same as what Il2CppDumper does. So just use Il2CppDumper. frida-il2cpp-bridge should work as a hook tool, not a dumper, I think.

I don't know how much Il2CppDumper is evolved, but frida-il2cpp-bridge won't have problems with packed/encrypted/missing/customized global-metadata. So I think there are situation where Il2CppDumper can't be used


How to detect DNS change of DB?

In out project we are using AWS RDS with multi AZ. If the master DB goes in backup another DB comes back up (because of multi AZ). This behaviour is more like creating a DB and putting behind CNAME.
However if I restart the application or the max-lifetime expires the connection pool is re-created, but till that time out application gives timeout.
I have asked for help over stack overflow, but didn't have a satisfactory answer https://stackoverflow.com/questions/48421107/hikaricp-doesnt-detect-db-dns-change.
What I have tried implementing:

Create a scheduler that polls every 30 sec to check if the DNS has changed. If so, recreate the new connection pool. -> If the scheduler crashes then then we might not be able to check the DSN change.
Created a Haproxy layer and our application will that will poll the db connection from haproxy (HAProxy supports postgres connection) -> This implementation works but if the Db changes we need to reload HAProxy to get it done (Restarting HAProxy is faster than restarting the application). But there is a manual step involved.

Is there a way where HikariCP understands a change in DNS.

... one of the unsatisfying answers on SO was mine. :smile:
HikariCP is not likely to implement DNS change detection any time soon.
I would suggest something like your scheduler, with the difference of calling softEvictConnections() on the HikariConfigMXbean instead of instantiating a new pool.

@brettwooldridge appologies for not recognizing you in SO.  😔
I have tried implementing what you have suggested and it works well. I'm trying to be cautious to make sure that in case my scheduler crashes i don't have an option to reschedule it.
Thank you for the reply.

Thanks for the solutions to manage the DNS change wrt Hikaripool.
I have some confusion wrt DNS caching mechanism in JVM. Sorry to bring it up in this github issue, I couldn't comment on the SO thread due to not having enough points :pray:
Does setting the networkaddress.cache.ttl (as per ref) itself is sufficient for JVM to re-lookup the DNS, or there will be effects of caching of DNS in the Operating System level too needs to be considered?
I am not sure how exactly the DNS resolution is implemented in the JVM (like whether it directly does a UDP based call to the DNS server itself or not), but this SO answer says like the JVM internally makes a DNS lookup call to the OS. Therefore, depending the DNS cache configuration in host OS. The OS will return correponding address to JVM either from it's cache or fetching from the DNS server (if DNS TTL has expired).
That means the DNS change detection also depends on the DNS entry's TTL value configuration on DNS server side. This DNS TTL needs to be set in AWS DNS service as per the "scheduler's" change detection requirement right? (not sure exactly what is the DNS service in AWS, but in GCP it is possible to set TTL per records.


Image training reentrancy doesn't work

@beccamc @LittleLittle

Could you help to provide the image-classification test matrix to validate this issue?
Which training environment should be selected on Environment page? Azure?

Any Image set should work. Do you have an image folder for other testing? If not I can provide one
It should work for both local and Azure environments.

Let me know if that doesn't help

@beccamc I don't have any image folder for testing, could you help to provide the image test matrixes for both local and Azure Environment?

Met some issues for re-entrancy image classification model builder, could you please take a look?
Main branch: https://privategallery.blob.core.windows.net/gallery/refs/heads/main/atom.xml

Windows 10 Enterprise, Version 20H2
ML.Net Model Builder (Preview): <IP_ADDRESS>2301
Microsoft Visual Studio Enterprise 2019: 16.9.4
.Net: 5.0.202

Azure Steps:
1). Download dataset from: https://testpass.blob.core.windows.net/test-pass-data/weather.zip
2). Create new C# console app with .Net 5.0;
3). Add model builder by right click on the project;
4). Click "Image classification" on Scenario page;
5). Select Azure and set up workspace on Environment page;
6). Click "..." to select a folder on Data page;
7). Click "Start training" on Train page, and wait Training complete;
8). Saved and closed the model builder;
9). Reopen the model builder, see:
a. prompt model builder error;

b. closed the error dialog, navigate to Environment page, see the workspace information lost;

c. Navigate to Consume page, the code snippet lost (dark theme);

Local Steps:
1). Download dataset from: https://testpass.blob.core.windows.net/test-pass-data/weather.zip
2). Create new C# console app with .Net 5.0;
3). Add model builder by right click on the project;
4). Click "Image classification" on Scenario page;
5). Select Local (CPU) on Environment page;
6). Click "..." to select a folder on Data page;
7). Click "Start training" on Train page, and wait Training complete;
8). Saved and closed the model builder;
9). Reopen the model builder, see: the code snippet lost (dark theme) on consume page;

Tracking "Model Builder Error" on: Model Builder error occurs on the process of model builder for Azure. #1406
Tracking "code snippet lost" on: The code snippet on Consume page should not lost after added to solution and re-opened. #1417
No other rentrancy issue on main branch:

Windows 10 Enterprise, Version 20H2
ML.Net Model Builder (Preview): <IP_ADDRESS>5801
Microsoft Visual Studio Enterprise 2019: 16.9.5
.Net: 5.0.202

Local (CPU):

Azure:


[NEMO-429] SWPP TEAM 13 code smell fix

JIRA: NEMO-429: SWPP TEAM 13 code smell fix
Major changes:

Fixed code smells (SWPP Code Smell session)

@jeongyooneo Any plans on this PR?

Won't merge this PR.


modbus_serial: Disable rx interrupt if buffer fills up

On many uarts, the RX interrupt flag is only cleared when reading from the fifo. If no read is performed the interrupt is immediately re-triggered when the ISR exits, causing a busy loop that starves the application.

@jfischer-no What more do you need to review and/or merge this?


Not able to override disk size

I have issues when changing the worker_groups disk_size it  still creating volume with 100g
I'm submitting a
worker_groups = [
    {
      name                          = "worker-group-1"
      instance_type                 = "t2.micro"
      additional_userdata           = "echo foo bar"
      asg_desired_capacity          = 1
      additional_security_group_ids = [aws_security_group.worker_group_mgmt_one.id]
      disk_size = 10
    }
  ]

What is the current behavior?
I expect the volume will be 10g and not the default 100g

Please review the valid map key names in locals.tf. disk_size is not a valid name. I think you're aiming for root_volume_size?
There is no validation of incorrect keys.


Add tests for HelpCommand #327

Part of #327

v1
@Zhiyuan-Amos submitted v1 for review.

[v1 1/1] Add tests for HelpCommand

(:books: Archive)

Checkout this PR version locally
git fetch https://github.com/se-edu/addressbook-level4.git refs/pr/477/1/head:BRANCHNAME

where BRANCHNAME is the name of the local branch you wish to fetch this PR to.

@yamgent to call external reviewers :>


Automatically Update OpenAPI Documentation

Requirements

Filling out the template is required.

All new code requires tests to ensure against regressions.

However, if your PR contains zero code changes, feel free to select the checkmark below to indicate so.

[ ] Have you ran tests against this code?

[X] This PR contains zero code changes.

Description of the Change
This PR finally takes advantage of all the work done when modularizing the endpoints and query parameters.
Now we have a system of code objects that define how the code works, define how the tests work, and define the documentation that's generated in a complex way.
This script uses all information available to generate updates to the OpenAPI yaml document on each commit, so that we can ensure our schema never becomes out of date

Superseedes #22

Super excited to see this

One thing that I noticed on the generated YAML, while not a requirement, is that the endpoints appear to not be alphabetized.
If they were
https://github.com/pulsar-edit/package-backend/blob/231de711db097dddda06d76095ec4976d5072e52/docs/swagger/openapi3_def.yaml#L71
should be where
https://github.com/pulsar-edit/package-backend/blob/231de711db097dddda06d76095ec4976d5072e52/docs/swagger/openapi3_def.yaml#L17
currently is
But also there are quite a few endpoints that appear to not have any "response" information such as GET /api/login, GET /api/oauth, GET /api/pat POST /api/packages, GET /api/packages/{packageName}/versions/{versionName}
The Tarball endpoint response is a little screwy too, though I assume that's an indexing problem: https://github.com/pulsar-edit/package-backend/blob/231de711db097dddda06d76095ec4976d5072e52/docs/swagger/openapi3_def.yaml#L229-L231
similar problem here as well
https://github.com/pulsar-edit/package-backend/blob/231de711db097dddda06d76095ec4976d5072e52/docs/swagger/openapi3_def.yaml#L279-L282

@Spiker985 Thanks a ton for pointing this out!
Not sure what's gone wrong with the tarball endpoint so I'll take a look. But I think the other issues is due to those endpoints not being fully written out, as in the object lacks details of it's response data. So I'll make sure to add that so we can start testing for it as well.
Otherwise you're right that alphabetizing this would be really cool, I almost wonder, I'm pretty sure the yaml.dumb() method supports a custom sort function, maybe adding it there would be enough to do that.
But thanks for reviewing the document, since wanna make sure it's valid and keeps up the standard of what your originally wrote

@Spiker985 Would love to hear any feedback, I think I've addressed everything. From here there's just the case of a few missing responses and parameters

Sorry, should have done it as a single review, thought it was just one or two then I went a bit mad... Some are typos, many are just adding a full stop to the end of the sentence to match the style of the others.

@Daeraxa You're feedback has been addressed, thanks a ton for the review and taking a look at this

@Spiker985 @Daeraxa Alright, from here I've addressed the issues that had still existed (as well as discovering another) and I think we are 100% ready to merge if anyone wants to take a last look.
As for what I've addressed in the last couple PRs:

This PR would clobber entries with the same path, such as GET /api/packages and POST /api/packages so I've resolved that
Got rid of multiSchema idea, and instead have a shared dir for parameters that have the same handling but need unique schemas
And resolved the issues around a module having a different components entry because of a mismatch between the name and module name

Nitpicky, but I've never seen any OpenAPI schemas which list the components first
Does this have any effect on how the swagger page displays them?

Nitpicky, but I've never seen any OpenAPI schemas which list the components first
Does this have any effect on how the swagger page displays them?

Valid question, threw me off at first too.
But doesn't seem to have any negative effect:

But this likely happens because we now sort the results to list the endpoints in a more satisfying way. If we really wanted to I could try my hand at a custom sorter, but as it doesn't seem to affect anything I don't think we have anything to worry about.

I'll likely reread this PR later today just to double check and make sure I haven't missed anything with the other changes
But if it gets a green light before then, feel free to merge
Arguably, the "current" version is no more accurate than anything that would be missed in this PR anyway

Nitpicky, but I've never seen any OpenAPI schemas which list the components first

Do you have an example of what you normally expect? It looks the same as the existing UI from what I can see or am I missing the issue here?

Nitpicky, but I've never seen any OpenAPI schemas which list the components first

@Spiker985 Do you have an example of what you normally expect? It looks the same as the existing UI from what I can see or am I missing the issue here?

Nope, that was exactly what I wanted to be sure of.
I was unsure of how the OpenAPI UI implementation was affected by the schema
From confused's response, it appears that the schema ordering is irrelevant and the UI will always display in a "static" order of API information -> endpoints -> schema
Basically, as long as the data exists in your yaml file, regardless of order, it'll always be implemented the same in the UI
That was all I wanted to validate with that question
(This doesn't count as reading through the updates, because I haven't done that yet)

Alright this PR now has OPTIONS methods added, as well as everything else should be fully fleshed out

Alright, since it's been a week since the last comment here, and this PR touches far too much of the codebase to avoid future conflicts, I'm going to go ahead and merge.
Thanks a ton to those that helped get this one along!


DirectionCalculator sometimes erroneously returns default turn direction of 'Left'

The DirectionCalculator.Calculate method is provided with 3 coordinates, which determine an 'angle', and from which it will determine a relative turning direction (e.g. Right, Left, etc).
I have encountered circumstances in which two of the three points are identical, resulting in an calculated angle of NaN, and ultimately returning the default turning direction of Left.
Perhaps I only know enough to make bad judgments, but working my way backward to method RouteExtension.RelativeDirectionAt, I find the collection of 'shape' coordinates that make up the route.  I don't know where or how these were generated, I can only see how they are used, so I don't really know if the problem is in the 'shape' collection, that it should not contain 2 consecutive identical coordinates, or if the problem is in the interpretation, of using consecutive coordinates to calculate the turning angle.  For now, I have assumed that the problem is in the interpretation, and I have provided a possible solution.
Currently, the RouteExtension.RelativeDirectionAt method contains the following code which, based on the current position 'i', passes in the coordinates immediately before and after.
return DirectionCalculator.Calculate(
    new Coordinate(route.Shape[i - 1].Latitude, route.Shape[i - 1].Longitude),
    new Coordinate(route.Shape[i].Latitude, route.Shape[i].Longitude),
    new Coordinate(route.Shape[i + 1].Latitude, route.Shape[i + 1].Longitude));

I have modified the code to allow for consecutive identical coordinates by doing the following:
int h = i - 1; // work backward from i to make sure we don't use an identical coordinate
int j = i + 1; // work forward from i to make sure we don't use an identical coordinate
while (h >= 0 && route.Shape[h].Latitude == route.Shape[i].Latitude
              && route.Shape[h].Longitude == route.Shape[i].Longitude) h--;
while (j <= route.Shape.Length && route.Shape[j].Latitude == route.Shape[i].Latitude
                               && route.Shape[j].Longitude == route.Shape[i].Longitude) j++;

return DirectionCalculator.Calculate(route, i,
    new Coordinate(route.Shape[h].Latitude, route.Shape[h].Longitude),
    new Coordinate(route.Shape[i].Latitude, route.Shape[i].Longitude),
    new Coordinate(route.Shape[j].Latitude, route.Shape[j].Longitude));

Do you think this is the right approach, or should this case have never occurred in the first place?
Thank you.

I think this is fine, there aren't supposed to be edges of length 0 in the route but this code makes things better and more robust. I'll have a closer look later and include it in the current source if you don't mind signing the contributor agreement, see contributing.md on why:
https://github.com/itinero/routing/blob/develop/CONTRIBUTING.md#how-to-contribute
If you have any idea why this route exists or how to reproduce this let us know here, it possibly points to a bug/issue elsewhere.


Allow non admin users to mark pod as dev and do remote debugging

Pull Request Test Coverage Report for Build 6176

0 of 0   changed or added relevant lines in 0 files are covered.
1815 unchanged lines in 30 files lost coverage.
Overall coverage increased (+0.06%) to 44.823%

Files with Coverage Reduction
New Missed Lines
%

azkaban-spi/src/main/java/azkaban/spi/EventType.java
1
94.12%

azkaban-common/src/main/java/azkaban/executor/container/watch/AzPodStatusDrivingListener.java
2
95.0%

azkaban-common/src/main/java/azkaban/jobExecutor/AbstractProcessJob.java
2
52.58%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowPreparer.java
2
81.48%

azkaban-common/src/main/java/azkaban/executor/ExecutionOptions.java
4
96.95%

azkaban-hadoop-security-plugin/src/main/java/azkaban/security/commons/HadoopSecurityManager.java
4
0%

azkaban-web-server/src/main/java/azkaban/webapp/AzkabanWebServerModule.java
5
95.05%

azkaban-common/src/main/java/azkaban/executor/ExecutorApiGateway.java
6
91.3%

azkaban-common/src/main/java/azkaban/project/DirectoryYamlFlowLoader.java
6
95.59%

azkaban-exec-server/src/main/java/azkaban/container/FlowContainer.java
13
22.42%

Totals

Change from base Build 6173:
0.06%

Covered Lines:
17401

Relevant Lines:
38822

💛  - Coveralls


ci: switch to new codecov uploader

This is blocked on https://github.com/codecov/uploader/pull/147


undefinedConstraint problem

Hey,
i have the following json schema definition.
          schema:
            type: object
            properties:
              id:
                type: integer
              test:
                type: string
                format: uuid

and my json is
{
  "foo": "bar"
}

When i run validation i get no errors?!?! But why... The json is definetly wrong.
I found out that the undefinedConstraint from here https://github.com/justinrainbow/json-schema/blob/3921012b92bdda17ec9b5a9f62cd25b2d0591b70/src/JsonSchema/Constraints/ObjectConstraint.php#L141 is the reason for that behaviour.
When i use null for undefinedConstraint it works perfectly. Why do you do this constraint? Do i miss something...

Ahhh sorry my fault. I forgot the required attribute in the schema definition :(


SearchMergeRequestsByIid

Please, add in class MergeRequests extends AbstractApi
public method like
public function getByIid($project_id, $mr_iid)
{
return $this->get($this->getProjectPath($project_id, 'merge_requests'), array('iid' => $mr_iid));
}

Feel free to add it yourself! Try to add some tests with it too though!

With pleasure! but I denied access to your repository.

You can fork the repo and create a merge request. ;)

I created a merge reguest https://github.com/m4tthumphrey/php-gitlab-api/pull/115, but there is an error when checking unrelated amended https://travis-ci.org/m4tthumphrey/php-gitlab-api/jobs/108891748. Checks on other versions of php successful https://travis-ci.org/m4tthumphrey/php-gitlab-api/builds/108891747. What are the next actions?

I'm not sure why but theres something happening with OpenSSL on the 5.3.3 builds, don't worry about it, I've merged it!


How to train only specific classes

I made my custom dataset as COCO dataset format
I'd like to train only specific classes out of my dataset but don't know how
I've tried like below:

Setting dic value '0' except 118, 122, 124 (118, 122, 124 should be trained)

It came out errors

and I noticed "strides[cur - 1]" So i tried next step

Setting dic value '1' except 118, 122, 124

It works but it's not a solution i want because other classes are also trained

Anyone knows how?

According to your numbering in the label map, it seems like you are assigning multiple classes to a single id number. I'm not sure whether that is feasible.

@kidpaul94
Thank you for advice
I don't know if there is a function that can train specific classes(Maybe I didn't find it....), My solution is to delete the classes from the json file that i don't want to train

Thanks @AlexPanteaGit! Initially, I had to do the same as @wooys1012 which for me the "quickest"/not efficient was to run my script to create the coco annotations again, but removing the categories that i didnt want for training the model. Not sure if this will work if you want to finetune your model on a specific category.


support on-premise outlook deployment

Can this be adapted to support on-premise outlook deployment?

This app is a wrapper to the offical online application. is your on-premise outlook have the online version looks similar to outlook.com or office.com?

yes, it looks very similar.  However,  it will perform an authentication redirect using our own AD/ldap.  I tried with your app,  once the authentication redirect is done, it comes back to microsoft login prompt and becomes a loop.

We are using office.com as our company email, we authenticate with our AD and do a redirect after that. all looks good.
if you could run this app with the dev mode. check if any error in the terminal console or the DevTools console.
You can press F12 to pop up the DevTools once running in dev mode.
Electron is using chromium as the core browser, shouldn't have any different with a real chrome.
Just have a look if any error cause the authentication failed.

are you trying to login your on-premise email account with the login page in the app?
The login in the app is either for outlook.com or office.com, if your email server is private. You can't login with that page, because it's not your on-premise login window :)
Let me know the answer, I have a plan to allow user to customise the home page to what ever meaningful.

yes to on-premise outlook.   Please provide an option so that one can start with on-premise URI .

just wondering what's the url looks like? Also I am worrying about once open the input for the url, this will become a desktop shell for any web app :)

web access is like: example.com/owa

There is a workaround solve this issue.
https://github.com/eNkru/freelook/issues/17#issuecomment-621684063
But I am not going to include this in the release app as it stores the clear text credentials in local computer. Feel free to do this as far as you have your protection for your own computer.


MCS-318 colormap

Added dictionary segment_map to StepMetadata where key is the index into object_list. The rgb dictionary (as value) is the segmentation color for that object.
example segment map:
{0: {'r': 218, 'g': 65, 'b': 21},
1: {'r': 239, 'g': 4, 'b': 237},
2: {'r': 126, 'g': 205, 'b': 46},
3: {'r': 36, 'g': 139, 'b': 166},
4: {'r': 37, 'g': 216, 'b': 187}}

Removed misleading color attribute from ObjectMetadata.
Ran into a few problems implementing this change:

Stringifier failed with integer dictionary keys. Will be making a ticket to address that.
Fixing test.msgpack for class modifications is more cumbersome than one would think.
Had to add strict_map_key=False to unpackb for deserialization as msgpack also does not like integer keys.

Closes #240

A few things...
1.) Are we certain that integer keys is preferable over using the uuid?
2.) Semi related, but should we also leave the "color" as part of the ObjectMetadata in addition to this map? To alleviate confusion, would renaming it "segmentation_color" or something be sufficient?
3.) If we're sticking with integer keys, for the serializer, would just doing str(key) be okay, or do we need something more complex?

A few things... 1.) Are we certain that integer keys is preferable over using the uuid?
I assume so since that was the request. Although the GH issue description stated using uuid, that was an interpretation of the work that needed to be done. I imagine that TA1 will use the segment map keys (integer indices) to associate the segmentation color value with rather than using the uuid to do a more expensive list filter or lookup. That approach makes sense to me.

2.) Semi related, but should we also leave the "color" as part of the ObjectMetadata in addition to this map? To alleviate confusion, would renaming it "segmentation_color" or something be sufficient?
Since TA1 requested this change, I'd rather not duplicate this information for maintainability and metadata filtering reasons.

3.) If we're sticking with integer keys, for the serializer, would just doing str(key) be okay, or do we need something more complex?
Since the serializer reads directly in to and out of python classes, I'd prefer keeping the integers and addressing our internal assumptions of the dictionary key always needing to be a string.

I compared the outputs on dev and this branch, and it looks like we're now missing the structural object segmentation colors with this approach. Perhaps leaving the object metadata the way it was and renaming the "color" field to "segmentation_color/id" for clarity would make the most sense.

I compared the outputs on dev and this branch, and it looks like we're now missing the structural object segmentation colors with this approach. Perhaps leaving the object metadata the way it was and renaming the "color" field to "segment_color/id" for clarity would make the most sense.

That is a good point @rartiss55. This PR may be null and void. As you mentioned, a less confusingly named attribute in ObjectMetadata may be the better approach here.

Hi folks - was pointed here by https://github.com/NextCenturyCorporation/MCS/issues/240#issuecomment-929272818.  Thanks for this work!
My first question is, what do the colors in the color map mean?  I.e., same question as in second paragraph of https://github.com/NextCenturyCorporation/MCS/issues/240#issuecomment-920347128.

@bzinberg Due to the earlier comments about some segmentation color information being missing using this approach, we will likely go with the alternative you mentioned with simply renaming the color field. See PR here: https://github.com/NextCenturyCorporation/MCS/pull/415
I'll go ahead and link the issue as well. Sorry for any confusion!

My first question is, what do the colors in the color map mean?

@bzinberg These are the rgb values we get back from Unity representing instance segmentation regions in the segmentation image.

Closing in favor of #415

Agreed, https://github.com/NextCenturyCorporation/MCS/pull/415 looks like the right fix for our situation.  Here are some more comments in case useful:
From the above I'm gathering that the upstream AI2Thor API for computing segmentation masks requires the user to think about colors (in particular, to compare the pixels of an image to the value of the "segment color").  I think, at least in hindsight, that probably wasn't the best choice: if a segmentation image gets passed around and at any point is converted lossily, e.g. to a GIF, then the pipeline (or the downstream viewer of a dashboard, etc.) breaks.  Just as a point of comparison, PyBullet's segmentation maps are integer arrays, of shape (height_px, width_px) where each entry is PyBullet's integer ID for the object, consistent with other methods for manipulating the object.
AI2Thor does seem to maintain a mapping from "name" (whatever that is) to "color"; though I don't know whether they expose these "names" in the public API.


Add padding to series_position

Would it be possible to add padding to this field? I know it's not very often we have series going over 10, but when it happens (looking at you Wheel of Time) my paths for organizing are a bit off.
Not an issue or anything, just something that could be considered.

I'll take a look at this but as you said, this would be lower in the backlog, as this only affects series that are more than 10 items.
I'm not sure if Beets itself is able to do this padding, you may want to check the Beets options for configuring paths.

Check out the beets inline plugin for more complex examples of path formatting
https://beets.readthedocs.io/en/stable/plugins/inline.html
Specifically the stuff like u'%02i' % (track)


Refactors deterministic cache mechanism and adds test

Work on #117
This doesn't yet include pickling of the cache.
It makes the use of the cache consistent by properly using the same object in all cases and also adds an option to TournamentManager to share the cache between tournaments.

Good to go. I'm done fiddling with it for now.


[receiver] high resource utilization during the time of uploading TSDB blocks

Issue summary
After upgrading the Thanos stack from version 0.26.0 to 0.32.3, I've begun encountering issues such as high memory usage and frequent restarts of the thanos-receive-router (also known as thanos-receive-distributor) pods during TSDB block uploads. Additionally, there have been high latencies for incoming requests and numerous error logs like the following
{"caller":"handler.go:373","component":"receive-handler","err":"context deadline exceeded","level":"error","msg":"internal server error","tenant":"default-tenant","ts":"2024-01-16T20:02:06.323528706Z"}

Actions done

Modifying certain flags to optimize performance proved unhelpful; even upgrading from version 0.32.3 to the latest version 0.33.0 had no effect.
Interestingly, reverting to version 0.26.0 significantly improved the performance of the receive-router component, making it approximately 10 times more efficient compared to version 0.33.0. The noticeable difference in performance is evident in the images below.

Stack details

Environment and deployment model: Kubernetes via Bitnami Helm chart
Kubernetes version: GKE 1.27
Object storage type: GCP-GCS
Receive and Receive Ingester replicas: 10 replicas every
Incoming requests per second: ~800 r/s
Incoming samples per second: ~800k

pprof result
Here is the result of the CPU profiles for both versions

receive-router-heap-0.26.0 vs receive-router-heap-0.33.0
receive-router-profile-0.26.0 vs receive-router-profile-0.33.0

pprof binaries: thanos-receive-router-pprof.zip

Confirming that the use of the --receive.grpc-compression=none field in version 0.33.0 was effective, and now the resource utilization is similar to that in version 0.26.0. Thanks @MichaHoffmann!

BTW should I add that flag in the receive-ingesters as well, does it make sense?

@hayk96 I don't think you need it there. The routers will take care of firing all the requests to achieve replication. The ingesters have nothing more to do than read the incoming non-compressed request and write the data.

Maybe we can add this in the Troubleshooting; Common cases? What do you think?

Maybe we add this in the Troubleshooting; Common cases? What do you think?

I'm indifferent i think; Its a bit of a tradeoff between network bandwidth and CPU; and usually CPU is cheaper so i think defaulting to snappy here is the correct behavior. But then again you faced the regression during update and would have profited from an FAQ article about it. I dont know whats the best course of action tbh!

I have mixed opinions regarding this. CPU is usually cheaper than network bandwidth. Ingest latency is super important too. If to save network bandwidth we need to pay in latency, this is a very sensible decision. Latency with the compression in @hayk96's environment was awful compared to no-compression. And check that memory usage chart...


Document doesn't exist but snapshotChanges returns empty data

Version info

Angular: 7.0.2
Firebase: 5.5.6
AngularFire: 5.1.0
Other (e.g. Ionic/Cordova, Node, browser, operating system): Ubbuntu, Chrome
How to reproduce these conditions
Failing test unit, Plunkr, or JSFiddle demonstrating the problem
  getOne(): Observable<any> {
    return this.angularFirestore
      .doc<any>(this.path)
      .snapshotChanges()
      .pipe(
        map(snap => {
          const data = snap.payload.data() as any;
          return { id: snap.payload.id, ...data };
        })
      );
  }

snapshotChanges() returns value for example return is {id: 'aaa'}
but when you browser in dashboard, this message view 'This document does not exist, it will not appear in queries or snapshots'

you'll want to filter by existence:
getOne(): Observable<any> {
    return this.angularFirestore
      .doc<any>(this.path)
      .snapshotChanges()
      .pipe(
        filter(snap => snap.exists),
        map(snap => {
          const data = snap.payload.data() as any;
          return { id: snap.payload.id, ...data };
        })
      );
  }


Error while setting up IDE

Steps to reproduce
1.Use the docs, link below to install and setup the ide -
https://docs.openmv.io/openmvcam/tutorial/software_setup.html
Expected behaviour
When you run ./openmvide or ./openmvide.sh it should run the application.
Actual behaviour
Comes up with the following error -
./openmvide: error while loading shared libraries: libGLESv2.so: cannot open shared object file: No such file or directory

Describe your setup
IDE version: 2.1.0
Firmware version:
Operating system:Raspbian
For developers
GCC version:Dunno
Build target:Dunno

I'll see what I can do about this... I guess I can install the last RPi build and see if that's the issue. If it's not then it's how your system gets setup.

Hi, OpenMV IDE runs great on a newly installed Pi that's totally clean. That's about the best I can debug this... if it's not running on your Pi it means you installed something else to break the IDE.
Did you run the setup.sh script first?
? https://www.raspberrypi.org/forums/viewtopic.php?t=191857

I'm having the same problem. Could you solve it?