add CORS_ORIGIN var in wrangler.toml

In source var CORS_ORIGIN is used, not secret.
Description
ctx.var("CORS_ORIGIN") cannot be found if set as secret.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Manually

Checklist:

[ x] My code follows the style guidelines of this project
[ x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Hi Christian, thanks for adding the pull request.  I will take a detailed look at this.  I just wanted to check you tried running:
wrangler secret put CORS_ORIGIN

to set the value in your Cloudflare worker project from the Terminal, so that it is read as a secret?

Hi Rodney, yes I tried.
Maybe secrets changed in new versions?
See this documentation:
        .get("/secret", |_req, ctx| {
            Response::ok(ctx.secret("CF_API_TOKEN")?.to_string())
        })

https://github.com/cloudflare/workers-rs/blob/c52798df921767ee0c8911814bfcc5e51101ade0/README.md?plain=1#L160

Thanks Christian, hope you had a good weekend. Does it work for you if you use ctx.secret as above?
I just updated the repo to use worker 0.09 and compatibility_date "2022-04-20" but it still works for me defining the secrets the previous way.
Just to make sure it's an issue with the secret, could you add a console_log to the  /verify post route in src/lib.rs so it reads:
        .post_async("/verify", |mut req, ctx| async move {
            console_log!("Origin: {}", ctx.var("CORS_ORIGIN")?.to_string());
            let data: CaptchaRequest = match req.json().await {
                Ok(res) => res,
                Err(_) => return Response::error("Bad request", 400),
            };
...

then send a test request from a browser and check if your origin gets output?

Hi, I'm sorry, it seems I did sth. wrong last time.
I tested now
.get("/", |_req, ctx| {
            console_log!("Secret Origin: {}", ctx.secret("CORS_ORIGIN")?.to_string());
            console_log!("Origin: {}", ctx.var("CORS_ORIGIN")?.to_string());
            Response::ok("Have a great day!")
        })

and getting also output for var.
Secret Origin: https://www.example.com,http://<IP_ADDRESS>:3000
Origin: https://www.example.com,http://<IP_ADDRESS>:3000

I will close this merge request.

No worries, glad you got it working, and I got to find out about ctx.secret!


Property 'isNan' does not exist on type 'NumberConstructor'

TypeScript Version:
3.1.3
Search Terms:
isNan
Code
const foo = 87;
if (Number.isNan(foo))
{
  console.log('NaN');
}

Expected behavior:
The above code compiles and produces JavaScript that uses Number.isNan().
Actual behavior:
Compilation fails with this error:
$ tsc --target ES2017 --strict --noEmit foo.ts
foo.ts:2:12 - error TS2551: Property 'isNan' does not exist on type 'NumberConstructor'. Did you mean 'isNaN'?

2 if (Number.isNan(foo))
             ~~~~~

  build/node_modules/typescript/lib/lib.es2015.core.d.ts:241:5
    241     isNaN(number: number): boolean;
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'isNaN' is declared here.

Related Issues:
I found issue #15149 that claims the issue is fixed, but it doesn't appear to be fixed.

Can you believe that I typed isNan instead of isNaN every single time?  Need more coffee.


feat: check for fixed checkpoints being moved/rotated/scaled

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


[DOC] Adding minimal working examples to docstrings; a checklist

Background
This thread is borne out of the discussion from #968 , in an effort to make documentation more beginner-friendly & more understandable.
One of the subtasks mentioned in that thread was to go through the function docstrings and include a minimal working example to each of the public functions in pyjanitor.
Criteria reiterated here for the benefit of discussion:

It should fit with our existing choice to go with mkdocs, mkdocstrings, and mknotebooks.
The examples should be minimal and executable and complete execution within 5 seconds per function.
The examples should display in rich HTML on our docs page.
We should have an automatic way of identifying whether a function has an example provided or not so that every function has an example.

Sample of what MWE should look like is shown here.

I'm thinking we can create a task list so that 1. we can encourage more users to join in the effort, and 2. make sure we don't do duplicate work. A lot of the groundwork can be covered by selectively copying one or two examples over from the software test suite.
Then we can label this issue as a Help Wanted / Low-Hanging Fruit and get people to mention in this thread if they're intending to work on the files?
Task list

[X] functions/add_columns.py
[x] functions/also.py
[x] functions/bin_numeric.py
[x] functions/case_when.py
[x] functions/change_type.py
[x] functions/clean_names.py
[x] functions/coalesce.py
[x] functions/collapse_levels.py
[x] functions/complete.py
[x] functions/concatenate_columns.py
[x] functions/conditional_join.py
[x] functions/convert_date.py
[x] functions/count_cumulative_unique.py
[x] functions/currency_column_to_numeric.py
[x] functions/deconcatenate_column.py
[x] functions/drop_constant_columns.py
[x] functions/drop_duplicate_columns.py
[x] functions/dropnotnull.py
[x] functions/encode_categorical.py
[x] functions/expand_column.py
[x] functions/expand_grid.py
[x] functions/factorize_columns.py
[x] functions/fill.py
[x] functions/filter.py
[x] functions/find_replace.py
[x] functions/flag_nulls.py
[x] functions/get_dupes.py
[x] functions/groupby_agg.py
[ ] functions/groupby_topk.py
[x] functions/impute.py
[x] functions/jitter.py
[x] functions/join_apply.py
[x] functions/label_encode.py
[x] functions/limit_column_characters.py
[ ] functions/min_max_scale.py
[x] functions/move.py
[x] functions/pivot.py
[x] functions/process_text.py
[x] functions/remove_columns.py
[x] functions/remove_empty.py
[x] functions/rename_columns.py
[x] functions/reorder_columns.py
[x] functions/round_to_fraction.py
[x] functions/row_to_names.py
[x] functions/select_columns.py
[x] functions/shuffle.py
[x] functions/sort_column_value_order.py
[x] functions/sort_naturally.py
[x] functions/take_first.py
[x] functions/then.py
[x] functions/to_datetime.py
[x] functions/toset.py
[ ] functions/transform_columns.py
[x] functions/truncate_datetime.py
[ ] functions/update_where.py
[ ] spark/backend.py
[ ] spark/functions.py
[ ] xarray/functions.py
[ ] biology.py
[x] chemistry.py
[x] engineering.py
[ ] errors.py
[ ] finance.py
[ ] io.py
[ ] math.py
[ ] ml.py
[x] timeseries.py
B

functions/bin_numeric.py is already in PR

I'm currently having a look at

functions/rename_columns.py
functions/reorder_columns.py
functions/to_datetime.py

Will probably look at some more as and when I have time over the next week or so

This is awesome, @thatlittleboy! Thank you for handling this here :smile:. I've invited you to the dev team to help move this along.
Also, please do consider joining the Discord channel that we have! https://discord.gg/VPgHDQx2

One trick I'm finding is that it's pretty easy to create a minimal working example from the test suite :joy_cat:.

Ongoing sprint, dibs on the following:

functions/change_type.py
functions/coalesce.py

Same here, dibs on:

functions/take_first.py
functions/sort_naturally.py

Dibs on:

functions/min_max_scale.py
functions/move.py

Two per PR seems to be the load that I can handle :joy_cat:.

Ongoing sprint:

functions/concatenate_columns.py
functions/deconcatenate_column.py
functions/select_columns.py

Going to work on:

functions/drop_constant_columns.py
functions/drop_duplicate_columns.py

Ongoing sprint:

functions/move.py
functions/remove_columns.py
functions/remove_empty.py
functions/limit_column_characters.py

Ongoing sprint:

functions/round_to_fraction.py
functions/row_to_names.py
functions/shuffle.py

Currently looking at:

functions/impute.py

functions/jitter.py

functions/join_apply.py

functions/encode_categorical.py

functions/label_encode.py

functions/factorize_columns.py

hi - this is amie, i am claiming:
functions/convert_date.py

Hey, I'm Geir Arne @ the PyCon US 2022 sprints.
I'm claiming functions/count_cumulative_unique.py to work on.

It's Catherine Devlin at PyCon 2022!
I'll start on chemistry.py.

Pycon 2022 - working on timeseries.py

I'll also do functions/find_replace.py

I'll do functions/fill.py

Pycon 2022 - working on functions/get_dupes.py

Pycon 2022 - working on functions/groupby_topk.py

I'll do math.py

Dibs on functions/transform_columns.py

For my next trick, I'd like to do biology.py

It looks like transform_columns.py is already done :(
Dibs on update_where.py

Dibs on finance.py

I'll do ml.py next

I'll do xarray/functions.py

In honor of my favorite Jovian moon, I'd like to do io.py next.  (It looks almost done already, but there are still a couple non-doctest)

functions/min_max_scale.py done via #1107 and #1112


Make sharing links, social links extendable including the icons, not always powered by font awesome

http://www.concrete5.org/community/forums/5-7-discussion/extend-social-links-missing-icons-for-bandcamp-email/

This can be closed.


Data Discovery

@AeriShan-ODI will drive discovery around Caltrans data, creating this issue to track that work.

Changed the assignee on this from @AeriShan-ODI to @britt-allen per yesterday's call. Britt will take the lead on data discovery. May bring in Aeri for support when they return from PTO end of December.
Also changed the milestone since we are consolidating the two discovery milestones into one.

This issue should get broken out into smaller, definable issues. We can use the upcoming meeting with Monica to identify the specific follow-on tasks.


Add image scanners

Currently we are just building and pushing the image
This issue
https://github.com/goreleaser/goreleaser/issues/1189#issue-505236381
Mentions a way to scan the images pre pushing it
We should integrate

clair

And other image scanning tools

Found a GHA that is not fully compatible but is a good start
https://github.com/marketplace/actions/docker-build-clair-scan-acr-push


lock users

Hi there,
did you get this snippet to work?
- name: Lock users | Lock password & ssh key authentication
  user:
    name: "{{ item.0.username }}"
    expires: 0 #lock account if not locked
    #  command: change -E 0 {{ item.0.username }} #Alternative lock password & ssh key authentication
    #  register: user_results
    when: item.0.user_state == 'lock' and item.1 in groups
    with_subelements:
      - "{{ users }}"
      - servers
    loop_control:
      label: "username: {{ item.0.username }}, user_state: {{ item.0.user_state }}"

What do you mean? Yes, it works.
See: https://docs.ansible.com/ansible/2.9/modules/user_module.html


The demo at celebdil.benet.ai:8080/ipfs seems to be dead.

http://celebdil.benet.ai:8080/ipfs/Qmezm7g8mBpWyuPk6D84CNcfLKJwU6mpXuEN5GJZNkX3XK/
That link is published at https://github.com/orbitdb/orbit-db/blob/master/README.md#background

The link appears to work for me. Try again?

The link does work, but I am unable to get the page to do anything at all.
My apologies, I was imprecise.
I'm seeing many console errors but, this is most likely the culprit:
WebSocket connection to 'ws://<IP_ADDRESS>:9090/socket.io/?EIO=3&transport=websocket' failed:

Error in connection establishment: net::ERR_CONNECTION_REFUSED WS.doOpen @

Swarm listening on /libp2p-webrtc-star/ip4/<IP_ADDRESS>/tcp/9090/ws/ipfs/QmSUXq2cq4241sGLq7u6XbdyC26XNbeGZMagGTgG2r1GQr

See also : Live demo seems unresponsive from  Mar 11/2018

Live demos are working for me, closing. Re-open if necessary.


Implement offheap server data structure for clustered caches

Implement the map of lists structure that will back the clustered ehcache instances.  As an initial start an implementation of the following interface will be required:
interface HashOperationStore {

  Chain get(int hash);

  Chain getAndAppend(int hash, ByteBuffer value);

  void append(int hash, ByteBuffer value);

  void replaceAtHead(int hash, Chain expected, Iterable<ByteBuffer> replacement);
}

interface Chain extends Iterable<ByteBuffer> {}

The Chain interface is required to allow for the use of sequence numbers in the stored values to accelerate the replaceAtHead operation (sequence number match is a safe substitute for a full binary comparison).  Other than the sequence number detail, the initial implementation of this interface should use a pessimistic locking approach... i.e. a copy under read lock during the get operation, and all mutation performed under write lock.  For now this is allows for a significantly simpler implementation, and we can then move toward something more complex as the need arises (or is proven through performance testing).

My suggestion for implementation here is to create a simple locked implementation using the AbstractOffHeapClockCache and then simply shard that implementation in the normal way.


Support Python 3

The only thing I had to do to make the tests pass is the syntax to catch
exceptions. There might be other things, but it's a start.

Thanks for your contribution.


SSL distribution: document that Erlang ignores dist. port range

We receive several reports of this problem on the mailing-list and IRC.
It seems nobody got back to @videlalvaro on the Erlang mailing-list so far, we should probably send a patch to move this forward.

Closing as there have been no recent reports of this problem and I'm not sure how we can make progress on this issue.


false should be a valid value for opts

If opts is false (for instance, in the case where we want to clear Storage and exit), then it will be set to an empty object and cause a jQuery bug.  Instead, strictly check against undefined

Ah, understood. Thanks for fixing this! Same rules apply to this one as #19. Thanks :-)

Just realized that you changed the dist directory's file which is built. You should have changed the src directory's file. I'll make the updates though. Thanks.


SDK/Namadillo: Sometimes Tx broadcast times out

Sometimes users are encountering a "tx failed" error due to a timeout, even when the transactions are successful.
We need to investigate the exact cause of this, and perhaps figure out a better way to verify that a Tx either succeeded or failed. Currently we are throwing an error when our SDK integration broadcastTx() (which in turn calls process_tx() in Namada SDK) throws an error of any kind, which in turn notifies user that the Tx failed (which is obviously not accurate every time).

The namada sdk can either "send a tx and forget" or "send and wait". The first method, just send a transaction and doesn't check if it was actually included in a block (it just wait until it passes mempool validation). The second instead, waits for the transaction to be included in a block. The timeout you are experiencing is probably due not being able to tell if a tx was included in a block or not during the timeout window


Add container for Vumi aggregation workers.

Ready for review.

Just those 2 questions about the number of things.

Merged in develop and attempted to answer the two questions.

:+1:


Fix dependency conflict for issue

#5

@jonathanferreiras
Could you please help me review this issue?
Thank you very much!
BTW, dependency conflict problems are very common in practice in python ecosystem.
I have encountered the issues several times. What's your oppinion on the challenges of detecting and repairing such issues?
And how to avoid dependency conflict problems among python projects, especially from the ecosystem's perspective?


Rust / Rocket / Diesel / Mysql - Backend Application

https://github.com/navinkumarr/rust-realworld-example-app

Could you clarify how this is different from: https://github.com/gothinkster/rust-realworld-example-app

Here are a few points because of which I started working on this application. Don't see these in the example application you have posted above.

It is built according to the Rocket framework standard (Trying to make a complete application with proper error handling, database connection pooling, support for master/slave architecture for database etc).
I have seen many example applications using Postgres. This one has the implementation for Mysql (Even though using an ORM, a straightforward example still helps).
Clean architecture (Could use this app architecture for writing bigger applications since it is properly layered).

Do let me know what you think @anishkny

I am not an expert on Rust. It might be worth discussing with their contributors if this is different enough? @davidpodhola, @leia,
cc: @Cameron-C-Chapman

I will support the new implementation by @navinkumarr.
Not only it is using a different database, but also using a different framework; Rocket is nice (note: we did not use it because we were told it is old and un-updated).
Also please note our implementation was done when we were very Microsoft oriented (everything in the repo is Windows-oriented); I hope the new one is multiplatform.
I think @navinkumarr you could at least reuse the tests we did, we had a very good code coverage.

@davidpodhola  Thank you for reviewing the project. Your feedback is much appreciated. Will surely take reference from your application wherever possible.

Go for it @navinkumarr best luck! Would be good if you could document differences from the first repo.

@navinkumarr Is this still WIP? I'd love to take this on using the Rocket 5.0 beta

Hello we are currently moving all work in progress to Github Discussions.
I'll close this issue by now, you can find instruction to open a discussion there : https://github.com/gothinkster/realworld/discussions/633
Thanks for your contribution !


(TenantPaging) Add APIs and performance improvements needed for supporting 20k+ tenancies

LGTM, this can be merged in once the UI is ready. Marking as On Hold and assigning to @nicolaasmatthijs

Merged


Made Design_Matrix convolution more general. Fixed missing silhouette plot imports, fixed upsample exports

Coverage decreased (-0.2%) to 52.817% when pulling 476f810654fd5ce6fbf63a1efe22ac150deda0a5 on ejolly:master into fab11719365bf8ccd97c6f693a32299a9b07069f on ljchang:master.


feat: Add labels and annotations to pods.

Currently, there is only one deployment, so avoid premature optimization by making these global (and follow the same pattern for imagePullSecrets)
Requires more aggressive usage of the strip-kustomize-helm.sh script because we have to preserve existing annotations and labels from the config/manager directory.

This PR

adds this new feature

Related Issues

Fixes #1234523
Notes

Follow-up Tasks

How to test

I'll give this and your other PRs a test tomorrow.

Hey @cpitstick-latai this is a great start! I was able to easily get the annotations working locally after running make helm-release and setting some in my values.yaml. I think I see 2 issues:

NOT passing any values seems to break the install. It's not immediately obvious to me why, since your defaults seem correct. In any case, I see:

helm upgrade --install open-feature-operator  /home/todd/git/open-feature-operator/charts/open-feature-operator-v0.6.1.tgz
Release "open-feature-operator" does not exist. Installing it now.
Error: YAML parse error on open-feature-operator/templates/apps_v1_deploymen

This PR doesn't deal with the runtime pods created by the operator. I think the annotations/labels should be added there as well, similar to how we added imagePullSecret there. See https://github.com/open-feature/open-feature-operator/pull/655 and https://github.com/open-feature/open-feature-operator/pull/666

Hey @cpitstick-latai this is a great start! I was able to easily get the annotations/labels working locally after running make helm-release and setting some in my values.yaml. I think I see 2 issues:

NOT passing any values seems to break the install. It's not immediately obvious to me why, since your defaults seem correct. In any case, I see:

helm upgrade --install open-feature-operator  /home/todd/git/open-feature-operator/charts/open-feature-operator-v0.6.1.tgz
Release "open-feature-operator" does not exist. Installing it now.
Error: YAML parse error on open-feature-operator/templates/apps_v1_deployment_open-feature-operator-controller-manager.yaml: error converting YAML to JSON: yaml: line 16: did not find expected key

This PR doesn't deal with the runtime pods created by the operator. I think the annotations/labels should be added there as well, similar to how we added imagePullSecret there. See feat: add image pull secrets #655 and fix: handle multiple imagePullSecrets #666

This sounds that we need to implement a CI action for testing the Helm installation in the e2e tests 🤔

I think I fixed the issue where empty dictionaries {} break.
Thinking about how to implement the runtime pod issue.

@toddbaert I believe I've resolved all the issues you pointed out. I've largely followed your blueprint for adding labels and annotations for image pull secrets, but this also means I may have missed other places they should go. Still, I think this is worth merging to get this formally in as a supported feature.

@toddbaert I believe I've resolved all the issues you pointed out. I've largely followed your blueprint for adding labels and annotations for image pull secrets, but this also means I may have missed other places they should go. Still, I think this is worth merging to get this formally in as a supported feature.

Amazing work. I'm reviewing and testing this now.

Hey @cpitstick-latai ! This all looks good to me, but I tried to install via helm and I get an error (whether or not I pass any values for annotations/labels).
Things I did:

pulled your branch
ran make helm-package
installed with helm upgrade --install open-feature-operator '/home/todd/git/open-feature-operator/charts/open-feature-operator-v0.7.0.tgz'

Then I got:
Error: UPGRADE FAILED: parse error at (open-feature-operator/templates/apps_v1_deployment_open-feature-operator-controller-manager.yaml:42): unexpected <range> in parenthesized pipeline

It seems like something isn't working with the templating

Ok I'll take a look and do some thorough testing on my end!

@toddbaert Alright I've updated it and done much more thorough testing. A couple notes:

Sometimes when a container is injected, the original deployment has to have hostNetwork: true enabled. This doesn't always seem to be true; however, there may be an issue with my cluster.
Looks like labels, annotations, and imagePullSecrets do not matter for injected pods, as they key off the settings of the original Pod the container is being injected into. So it's only with FlagD standalone and FlagD proxy mode that this matters (and I didn't specifically test those, but I did verify that the labels are being parsed correctly in the main.go function)

The ugliest/most awkward parts are this line and its companion for annotations: {{ $labelKeys := keys .Values.labels -}}{{- $labelPairs := list -}}{{- range $key := $labelKeys -}}{{- $labelPairs = append $labelPairs (printf "%s:%s" $key (index $.Values.labels $key)) -}}{{- end -}}{{- join "," $labelPairs }}
I don't know how to write it better, but it does work and build properly.

Maybe that nil check should be moved out so that it's always at least an empty map?

It makes sense. I did merge the if statements a little so that it would make sure the map wasn't nil before the merge check. In this way, it's always an empty map rather than a nil map that's applied to the cluster, and then we don't need nesting!
We have a cyclomatic complexity issue now; however, it seems the additional conditionals tipped this function over the edge.

It makes sense. I did merge the if statements a little so that it would make sure the map wasn't nil before the merge check. In this way, it's always an empty map rather than a nil map that's applied to the cluster, and then we don't need nesting!
We have a cyclomatic complexity issue now; however, it seems the additional conditionals tipped this function over the edge.

It makes sense. I did merge the if statements a little so that it would make sure the map wasn't nil before the merge check. In this way, it's always an empty map rather than a nil map that's applied to the cluster, and then we don't need nesting!
We have a cyclomatic complexity issue now; however, it seems the additional conditionals tipped this function over the edge.

I've simplified my solution: I now simply default the annotations on the template with the empty annotation map you created. That fixes the problem without more complexity.

Looks good to me, feel free to merge this at your convenience and when you get some teammates to review it!


Key Error when running AC-MADS-TEM.jl with target data containing compartments (E.g. VEGC, VEGN)

The following error is occurring when loading target data in AC-MADS-TEM.jl for variables with compartments such as vegetation carbon or nitrogen:
ERROR: LoadError: PyError ($(Expr(:escape, :(ccall(#= /home/develop/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:43 =# @pysym(:PyObject_Call), PyPtr, (PyPtr, PyPtr, PyPtr), o, pyargsptr, kw))))) <class 'KeyError'>
KeyError(0)
  File "/work/scripts/drivers/MadsTEMDriver.py", line 312, in observed_vec
    targets = [self.targets[ct][PFT] for PFT in range(10) if PFT in pftnums]
  File "/work/scripts/drivers/MadsTEMDriver.py", line 312, in <listcomp>
    targets = [self.targets[ct][PFT] for PFT in range(10) if PFT in pftnums]

Stacktrace:
  [1] pyerr_check
    @ ~/.julia/packages/PyCall/1gn3u/src/exception.jl:75 [inlined]
  [2] pyerr_check
    @ ~/.julia/packages/PyCall/1gn3u/src/exception.jl:79 [inlined]
  [3] _handle_error(msg::String)
    @ PyCall ~/.julia/packages/PyCall/1gn3u/src/exception.jl:96
  [4] macro expansion
    @ ~/.julia/packages/PyCall/1gn3u/src/exception.jl:110 [inlined]
  [5] #107
    @ ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:43 [inlined]
  [6] disable_sigint
    @ ./c.jl:458 [inlined]
  [7] __pycall!
    @ ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:42 [inlined]
  [8] _pycall!(ret::PyCall.PyObject, o::PyCall.PyObject, args::Tuple{}, nargs::Int64, kw::Ptr{Nothing})
    @ PyCall ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:29
  [9] _pycall!
    @ ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:11 [inlined]
 [10] #_#114
    @ ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:86 [inlined]
 [11] (::PyCall.PyObject)()
    @ PyCall ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:86
 [12] top-level scope
    @ /work/mads_calibration/AC-MADS-TEM.jl:111
in expression starting at /work/mads_calibration/AC-MADS-TEM.jl:111

@Benjamin-Maglio just noticed that there is a comment about compartments right before line 312 in MadsTEMDriver.py:
Maybe try modifying as suggested in the comment and see what happens? Notice the typo in self in the comment.
Probably will need an else clause too. If the type is a single value, then its a soil variable, if its a list then its a PFT variable, if its a dict, then its a PFT/Compartment variable. Maybe this is not the absolute best solution, but it might work?

@tobeycarman when I tried that I get this similar but different error:
ERROR: LoadError: PyError ($(Expr(:escape, :(ccall(#= /home/develop/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:43 =# @pysym(:PyObject_Call), PyPtr, (PyPtr, PyPtr, PyPtr), o, pyargsptr, kw))))) <class 'TypeError'>
TypeError("'int' object is not subscriptable")
File "/work/scripts/drivers/MadsTEMDriver.py", line 312, in observed_vec
targets = [self.targets[ct][PFT] for PFT in range(10) if PFT in pftnums]
File "/work/scripts/drivers/MadsTEMDriver.py", line 312, in
targets = [self.targets[ct][PFT] for PFT in range(10) if PFT in pftnums]

@valeriabriones @Benjamin-Maglio, wow, on account of your issues, I just found a separate, but kinda related bug!! In MadsTEMDriver.py: there is an indentation error with the return statement in MadsTEMDriver.observed_vec() that was allowing the test to pass despite totally flawed logic!
Notice that the test actually includes a target with compartment values (VegCarbon), but the test was passing. Basically because the return statement is indented one level too far.
Here is one question that comes up: what do you want the returned vector to look like? Still a flat list enumerating the targets by PFT and compartment, i.e. like this:
[vegc_pft0_leaf, vegc_pft0_stem, vegc_pft0_root, vegc_pft1_leaf, vegc_pft1_stem, ...]

or organized some other way?

@tobeycarman I think a flat list still works well for the current workflow we have set up! So the indentation allowed it to pass although it wasn't working properly?

@valeriabriones ok, so that order is good? Or would you rather have it in a similar order to how they are listed in the targets?
Option (1) looks like this:
[
  GppAllignN pft1, pft2, ... pft6
  vegC pft1 leaf, vegc pft1 stem, vegC pft1 root,
  vegC pft2 leaf, vegc pft2 stem, vegC pft2 root,
 ...
  vegC pft6 leaf, vegc pft6 stem, vegC pft6 root,

]

Option (2) looks like this (more like the existing calibration_targets.py data structure):
[
  GppAllignN pft1, pft2, ... pft6
  vegC pft1 leaf, vegc pft2 leaf, vegC pft3 leaf,  ... vegC pft6 leaf,
  vegC pft1 stem, vegc pft2 stem, vegC pft3 stem, ... vegC pft6 stem,
  vegC pft1 root, vegc pft2 root, vegC pft3 root, ... vegC pft6 root,
  ...
]

In either case, it seems like the totally flattened list might be kind of error prone to work with as the number of targets increases??? It would be up to the user of the MadsTEMDriver.observed_vec() to make sure that they are correctly indexing into the flat list...not mixing up the order of PFTs or the compartments...
Maybe it would be better to return nested lists or some other data structure...?
I think that so far this has not been a problem because y'all haven't been using this MadsTEMDriver.observed_vec() function in any post processing and have been reading the target data a different way? I think that the MadsTEMDriver.observed_vec() might have been something I added so that I could do the testing - looks from the comment that is might exist there as a way to print out the target data during setup and before actually running the model.

@tcarman you're right I think we're only referencing this function within the MADS calibration only and not in other calibration functions, so maybe it wouldn't disrupt anything to modify the output format. Maybe Format Option 1 would make sense, but would be good to get your thoughts @Benjamin-Maglio @jsclein-uaf ?

Yeah, maybe a better option is to return a richer data structure, like a pandas DataFrame, something like this:
d = drivers.MadsTEMDriver.MadsTEMDriver(config_dict)

# ... load targets, etc, etc

import pandas as pd
pd.DataFrame( d.observed_vec() ) # <-- maybe would want to rename func since its no longer returning a plain vector
        cmtnum                  ctname  pft  observed cmprt
    0        6  GPPAllIgnoringNitrogen    0    11.833   NaN
    1        6  GPPAllIgnoringNitrogen    1   197.867   NaN
    2        6  GPPAllIgnoringNitrogen    2    42.987   NaN
    3        6  GPPAllIgnoringNitrogen    3    10.667   NaN
    4        6  GPPAllIgnoringNitrogen    4     3.375   NaN
    5        6  GPPAllIgnoringNitrogen    5    16.000   NaN
    6        6  GPPAllIgnoringNitrogen    6     6.000   NaN
    7        6               VegCarbon    0     2.000  Leaf
    8        6               VegCarbon    0     4.000  Stem
    9        6               VegCarbon    0     0.297  Root
    10       6               VegCarbon    1    37.100  Leaf
    11       6               VegCarbon    1     0.000  Stem
    12       6               VegCarbon    1   161.280  Root
    13       6               VegCarbon    2     8.060  Leaf
    14       6               VegCarbon    2     0.000  Stem
    15       6               VegCarbon    2    11.040  Root
    16       6               VegCarbon    3     2.000  Leaf
    17       6               VegCarbon    3     0.000  Stem
    18       6               VegCarbon    3     3.200  Root
    19       6               VegCarbon    4     2.000  Leaf
    20       6               VegCarbon    4     0.000  Stem
    21       6               VegCarbon    4     0.000  Root
    22       6               VegCarbon    5    22.000  Leaf
    23       6               VegCarbon    5     0.000  Stem
    24       6               VegCarbon    5     0.000  Root
    25       6               VegCarbon    6    23.000  Leaf
    26       6               VegCarbon    6     0.000  Stem
    27       6               VegCarbon    6     0.000  Root

@valeriabriones I agree with option 1, I think that also matches sensitivity too?
@tobeycarman, how do you foresee this structure being used? Currently, I'm only really concerned with having MADs run, but is there a benefit to using this for something else?

@Benjamin-Maglio good point - I don't have a direct use, maybe just thinking if I were to consume the data it would be less error prone to have it be labeled. In any case I ended up with both implementations (flat and labeled) as it ended up being easier way to try testing the expected order of the list. I will admit I am not sure I understand the implications of the previous  bug with the return value of the MadsTEMDriver.observed_vec(...) function.

@tobeycarman Yeah I mean the labeled data is much nicer, and I could see there being some application at some point...
So that PR should fix our original bug? Have you tried a mads run with VEGC? Or I could try that?

@Benjamin-Maglio I did not try full MADS run. That doctest script uses the MadsTEMDriver.run() function, but that doesn't really invoke anything with MADS. If you are setup to try it that would be great. I expect that PR to fix the original bug but maybe uncover more :-),

@tcarman @Benjamin-Maglio I implemented the changes and am still getting some syntax errors starting at the line in AC-MADS-TEM.jl targets = dvmdostem.observed_vec(format= 'format')
ERROR: LoadError: syntax: character literal contains multiple characters
Stacktrace:
[1] top-level scope
@ /work/mads_calibration/AC-MADS-TEM.jl:111
in expression starting at /work/mads_calibration/AC-MADS-TEM.jl:111

Oh! My bad - Julia likes double quotes for strings, single quotes for
single chars. So if you change to double quotes, it should help
On Wed, Sep 11, 2024 at 8:44 AM valeriabriones @.***>
wrote:

@tcarman https://github.com/tcarman @Benjamin-Maglio
https://github.com/Benjamin-Maglio I implemented the changes and am
still getting some syntax errors starting at the line in AC-MADS-TEM.jl targets
= dvmdostem.observed_vec(format= 'format')
ERROR: LoadError: syntax: character literal contains multiple characters
Stacktrace:
[1] top-level scope
@ /work/mads_calibration/AC-MADS-TEM.jl:111
in expression starting at /work/mads_calibration/AC-MADS-TEM.jl:111
—
Reply to this email directly, view it on GitHub
https://github.com/uaf-arctic-eco-modeling/dvm-dos-tem/issues/738#issuecomment-2344155603,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGMYT6FI72VUUSHXFEUUZLZWBXOLAVCNFSM6AAAAABNYWW4VGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBUGE2TKNRQGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@valeriabriones hey so were you able to test this by checking out the branch #iss738-mads-targets-compartments or did you kind of manually copy the code into the branch you are working on? In that branch I think I have the return statement set at the correct indentation level because the doctest tests pass - but I obviously didn't check the AC-MADS-TEM.jl script...
Let me know if you want to meet quickly to discuss...

@tobeycarman No I did a hack and manually copied the revised code into my current set up on master

@tobeycarman tried testing the revised MADS on a calibration run with soil and vegetation but ended up getting this new error:

haven't seen this error before. Any help appreciated

OK. Thats good  - it seems to be getting past the "expensive" part (the Mads.calibrate(md, tolOF=0.01, tolOFcount=4), approx line 238, and is failing when trying to build nicely named lists for the plotting that happens later. In both cases, the .iterationresults and .finalresults files should exist, but may not have been copied into their final location yet. In the second screen capture, it looks like the out_labels are not quite right - seems like they should have the pft compartment in there too ?
For the record, we me offline and updated @valeriabriones workstation and containers to v0.8.0 and then pulled #741 into a temporary integration branch for testing.

I am still hitting a similar error to earlier:
ERROR: LoadError: PyError ($(Expr(:escape, :(ccall(#= /home/develop/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:43 =# @pysym(:PyObject_Call), PyPtr, (PyPtr, PyPtr, PyPtr), o, pyargsptr, kw))))) <class 'TypeError'>
TypeError("'float' object is not subscriptable")
  File "/work/scripts/drivers/MadsTEMDriver.py", line 354, in observed_vec
    targets.append(self.targets[ct][PFT])

Stacktrace:
  [1] pyerr_check
    @ ~/.julia/packages/PyCall/1gn3u/src/exception.jl:75 [inlined]
  [2] pyerr_check
    @ ~/.julia/packages/PyCall/1gn3u/src/exception.jl:79 [inlined]
  [3] _handle_error(msg::String)
    @ PyCall ~/.julia/packages/PyCall/1gn3u/src/exception.jl:96
  [4] macro expansion
    @ ~/.julia/packages/PyCall/1gn3u/src/exception.jl:110 [inlined]
  [5] #107
    @ ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:43 [inlined]
  [6] disable_sigint
    @ ./c.jl:458 [inlined]
  [7] __pycall!
    @ ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:42 [inlined]
  [8] _pycall!(ret::PyCall.PyObject, o::PyCall.PyObject, args::Tuple{}, nargs::Int64, kw::PyCall.PyObject)
    @ PyCall ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:29
  [9] _pycall!
    @ ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:11 [inlined]
 [10] (::PyCall.PyObject)(; kwargs::Base.Pairs{Symbol, String, Tuple{Symbol}, NamedTuple{(:format,), Tuple{String}}})
    @ PyCall ~/.julia/packages/PyCall/1gn3u/src/pyfncall.jl:86
 [11] top-level scope
    @ /work/mads_calibration/AC-MADS-TEM.jl:111
in expression starting at /work/mads_calibration/AC-MADS-TEM.jl:111

I'll try and follow the approach above (updated workstation, containers, and create and temporary integration branch)

Ok, so I followed a similar approach above updating containers and creating a temporary integration branch and this error has gone. I am now getting the same error as @valeriabriones.
I'm going to try and fix this issue today by working through the plotting in Python / Julia terminal

@tobeycarman @Benjamin-Maglio Not sure if you have come across any issues since the updates with the AC-MADS-TEM.jl, but after running calibration a few times now it seems there is something going on where post-MADS optimal targets are returning as NaN or zero for some/ all of the targets:

When running with GPPAllIgnoringNitrogen as the target all returned as zeros.
Of course, nothing is failing, just requires a workaround where I run a single run with the opt_params to visualize what the targets are

Weird, I haven't encountered this. So are the values NaNs or zeros in the .finalresults file?

Ok, I can dig a big further. The parameter values write out correctly, but the OF and lamda values in the .finalresults are NaN as well

I'll try and take a look at this today. Is this happening for a specific configuration (e.g. compartment, pft specific variables)? Or particular parameters?

It seems to be with both soil and non-soil targets similarly with parameters Its happened with kdcs and soil as well as cmax and INGPP.

Ok, I will try to replicate this issue!


Improve short input hashing performance on ARMv8

This uses similar style of code as for Intel code path for reading individual bytes at end of input.
For short inputs there are significant gains.
Assembly generated for switch statement: https://godbolt.org/z/DPxU4h
Before:
  Fewest cycles to hash 1b:   136
  Fewest cycles to hash 2b:   140
  Fewest cycles to hash 3b:   146
  Fewest cycles to hash 4b:   151
  Fewest cycles to hash 5b:   155
  Fewest cycles to hash 6b:   161
  Fewest cycles to hash 7b:   166
  Fewest cycles to hash 8b:   170
  Fewest cycles to hash 9b:   176
  Fewest cycles to hash 10b:  181
  Fewest cycles to hash 11b:  186
  Fewest cycles to hash 12b:  190
  Fewest cycles to hash 13b:  195
  Fewest cycles to hash 14b:  200
  Fewest cycles to hash 15b:  206
  Fewest cycles to hash 16b:  128
  Fewest cycles to hash 17b:  143

After:
  Fewest cycles to hash 1b:   129
  Fewest cycles to hash 2b:   130
  Fewest cycles to hash 3b:   130
  Fewest cycles to hash 4b:   130
  Fewest cycles to hash 5b:   131
  Fewest cycles to hash 6b:   131
  Fewest cycles to hash 7b:   134
  Fewest cycles to hash 8b:   130
  Fewest cycles to hash 9b:   131
  Fewest cycles to hash 10b:  131
  Fewest cycles to hash 11b:  134
  Fewest cycles to hash 12b:  131
  Fewest cycles to hash 13b:  134
  Fewest cycles to hash 14b:  134
  Fewest cycles to hash 15b:  135
  Fewest cycles to hash 16b:  126
  Fewest cycles to hash 17b:  138

Awesome!  Thanks Martins!
- Casey


Details on pre-training of torchvision models

I realize there is a closed issue on this topic here: https://github.com/pytorch/vision/issues/666
The issue has been opened in 2018. I have not found any documentation on how the models of torchvision are pre-trained, therefore I am opening another issue. Is the above answer still valid? Are the models still trained according to https://github.com/pytorch/examples/tree/master/imagenet ?
Specifically, I would like to know the details on the image size and data transformation used.
Thanks!

Have a look on the documentation and on the readme. You will find hyper-params and script references along with detailed accuracies etc.
I'll close the issue to keep things neat but if you have more questions feel free to reopen.

Thanks for the rapid response @datumbox
I found the image size to be 224 and that standardization with imagenet statistics was used (according to the doc. The readme you've sent contains ResNext, but unfortunately does not mention ResNet which I'm interested in (forgot to specify, my bad!). Would you happen to know the exact data augmentation pipeline used for the pretrained ResNet models found in torchvision? Or are these the same as in the readme you've sent?

We use the same standardization and size in all models unless explicitly specified otherwise. As far as I recall the only model that deviates is InceptionV3 that uses a different input size (299x299). See:
https://github.com/pytorch/vision/blob/8317295c1d272e0ba7b2ce31e3fd2c048235fc73/references/classification/train.py#L85

Great, that's all the info I need. Thanks again @datumbox !


Add Functionality: Custom ID Filter

This should allow for players to config their own curated list of allowable items in special slots, including items added by mods.
resolves #2

This is great! Thanks for taking the time to contribute. Merged


Updated to use SAS in place of ACS

ACS is no longer supported in Azure Service Bus Queues, so we now need to leverage the SAS policy name and key in place of the UserName and Password values. I've tested this change for a client that was trying to do JMS to ASB over AMQP and it worked. Also, note that this feedback was previously provided in the comments section for this article.

Hi @swgriffith, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@sethmanheim - Could you please review this public repo contribution?

@swgriffith Thank you for the contribution! We'll get this added right away.
@tysonn OK to merge.


Add ProGuard support

Close #172
I made draft for README. Feel free to comment on that!

Cool, let me check tomorrow! Good night!

Have a wonderful night!

Almost LGTM!

@shiraji Thx man!


trivial updates for v3 auth

This PR has two commits that just fix trivial problems in v3 auth.

lgtm


Documentation not enough, not sure how to use and what exactly is its use case.

The Readme.md file contains just the basic details and doesn't contain enough info how can i use PingPong in my project. What does the code given do? What does setup.py do? How can i import it in my project and improve my chatbot? No link to even an external documentation is provided. I recently found out about this repo, but don't know how to use it.

Wait for the next few hours


Non quantified variables

Hi, I'm a bit confused on how you are dealing with non-quantified variables. For example, in the following program, how are you quantifying p and q? Are they quantified in the inner-most quantified block existentially or the outer-most quantifier block existentially or you just ignore both variables and all the rules related to them? Thanks.
_exists(1, x). _forall(2, r). {x;r;p;q}. x :- r. p :- q. q.

Hi, they are quantified in the inner-most quantified block existentially. That program is essentially the same as this one:
 _exists(1, x). _forall(2, r). {x;r;p;q}. x :- r. p :- q. q.
 _exists(3, p). _exists(3, q).

Note that this agrees with the informal definition given on the README, and with the formal definition of the paper that is linked from there.


Typo in page

There is a typo in the word "following" here:

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: cc5b41d6-127a-a1ba-a9ad-fe1d0549b5a4
Version Independent ID: cc5b41d6-127a-a1ba-a9ad-fe1d0549b5a4
Content: Step by step guide on configuring your proxy settings
Content Source: data-integration/gateway/service-gateway-proxy-setup-guide.md
Product: on-premises-data-gateway
GitHub Login: @miquelladeboer
Microsoft Alias: mideboer

Hi @martaequintao
Thanks for the feedback! The typo has bee fixed.


Comparison to similar tools?

Eternal Terminal seems similar to other projects like mosh and autossh. I think it would be helpful to have a review of the differences between these tools in the documentation.

Thanks for the feedback!


super-slicer: init at <IP_ADDRESS>

Motivation for this change
Added SuperSlicer — PrusaSlicer fork with more features and faster development cycle.
Things done

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

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

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

@GrahamcOfBorg build super-slicer

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/290

@Moredread pls :D

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/218


The element in transition can't get ref with style scoped

Version
3.0.0-beta.15
Reproduction link
https://codesandbox.io/s/green-night-y486i?file=/src/App.vue
Steps to reproduce
Describe the bug
The vue3.0.0-beta.15 with style scoped can't get the element's ref in  <transition>.
When I delete scoped, I get both foo and bar.
I tried it in vue 2.6.11, and get both foo and bar too.
Reproduction
<template>

    <transition>

    </transition>

</template>

<template>

    <transition>

    </transition>

</template>

What is expected?
this.$refs include both  foo and bar.
What is actually happening?
only got bar

When I try to use this.$refs.foo.scrollBy(),  I got Uncaught TypeError: Cannot read property 'scrollBy' of undefined, Firstly I thought there's something wrong with my code, but all looks right, Then I create a new project , delete unrelated code to debug...Later, I delete style scoped the console logged foo and bar!

This is fixed by be69beed5ed05067006c297589598b33e7108b1b

Wow, awsome! thank you.


Structured file logger

This provides a much more detailed log file than either Unity's own output log, or UberLoggerFile does. The intention is to include much more information in the logs, thereby making it easier to diagnose errors which occur in deployed builds.
Main features:

UTC timestamps for each log message (useful when correlating logs from multiple machines in the same MP match)
Channel information present in logs
One log message per line, except when callstacks are included
Ability to have full callstacks in logs - either for all messages, or only for warnings/errors

Thanks for this! I'll try and have a proper look at it soon - apologies for the silence up until now. :)

Hmm, perhaps I should spin the StructuredFile logger off into a separate repo instead, like this module. The latter is an UberLogger logger + config of Google's Stackdriver Logging service, which provides centralized logging for game clients.

Closing this, see #31 for just the UberLogger-specific changes


More access when it comes to points

Perhaps the ability to add points to all users at once. The ability to change my peoples points by looking their user up on the website. For example. Going here: https://bot.mystogan.xyz/user/NotOofHayden and while logged in I can click on my point value and edit it.

Please see the linked issues to discuss each of the feature requests individually


Issue with k8s.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/

This is a Bug Report

Problem:
In the "Configure a Pod to Use a PersistentVolume for Storage" example, a storageClass named "manual" is used but there is no comment to warn user that there must be a storageclass in the cluster named "manual". If we follow the steps written in this page we got "storageclass.storage.k8s.io "manual" not found" error.
Proposed Solution:
User should be warned to have a storageclass named "manual". It might be very good to add sample yaml for that storageclass onject:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: manual
provisioner: kubernetes.io/no-provisioner
volumeBindingMode: WaitForFirstConsumer

Page to Update:
https://kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/

When i try this, i notice storageclass is missing but it didn't work after i create sc. I tried to delete pv and recreate it, then it worked.
I tried same scneraio to open a bug to Kubernetes but even i deleted the sc "manual" it worked as it described in page.

/language en

/priority backlog

@yvzsrt
Hey, just got the same confusion here. Very curious about what the "manual" storage class is...

@yvzsrt
Hey, just got the same confusion here. Very curious about what the "manual" storage class is...

Same problem here. Why is this not mentioned in the docs?
Sometimes it works without creating StorageClass manual, sometimes not. Absolutely confusing.

I think someone should make manual here more clearer, as it is indeed very confusing. But to my understanding, this is a way to statically bind a PVC to a PV, by simply specifying a "virtual" StorageClass, PVC can bind to PV.


sap_hana_install: Replace ansible.posix.firewall (#83)

We can replace ansible.posix.firewall by a executing the firewall-cmd command via the ansible.builtin.command module, by constructing an argument list from the same variable which is used by the Linux System Roles firewall role.
By adding a new tag sap_hana_install_configure_firewall, we can let the role only update the firewall settings for SAP HANA.
The associated role variable for configuring the firewall settings remains sap_hana_install_update_firewall with its default no.

Ports
- "30105"
- "30107"
- "30140"
       are included in range

"3{{ sap_hana_install_number }}00-3{{ sap_hana_install_number }}90"

I do not see a reason why we should add them separately.

SMART data integration ports
5050
and SAP HANA Smart Data Streaming ports
- "9090"
- "9091"
- "9092"
- "9093"
Are not required for every HANA installation. Why are we including them by default? But not including ports for HTTP (XSA) 80? And at the same time include HTTPS 43?

Don't you think this should be separate role? So it can be called as day 2 automation role for already installed HANA system?

Are HA ports for CCSPs included?

From your point of view should ssh port be included?

1 - Taking the example of a SAP HANA installation number 77, the port range of 3{{ sap_hana_install_number }}00-3{{ sap_hana_install_number }}90 would be 37700-37790. So we cannot remove the three ports. However, there are some examples in the list which can be converted to a range, e.g. '9090/tcp-9093/tcp',
2 - I cannot answer this question, as I focused on replacing the call to ansible.posix.firewall. The topic of which ports we need to open for SAP HANA should also be discussed, maybe in a separate issue.
3 - Yes, having a separate role is an idea which already came up. For the time being, we could leave the current firewall related code as part of sap_hana_install, taking into account that this code is only used if the default setting for variable sap_hana_install_update_firewall is changed from no to yes. There are more options available:

introduce a user variable, e.g. named sap_hana_install_firewall_ports which can be used to set your own range of ports
(suggested by @rhmk): Use firewalld service configuration files as documented in https://firewalld.org/documentation/man-pages/firewalld.service.html and https://firewalld.org/documentation/howto/add-a-service.html
4 - Probably not.
5 - I cannot answer this question but in my tests, the ssh connection to the managed nodes remained open.

Regarding item 5, the following output probably explains why we don't have to include ssh here:
# firewall-cmd --list-services cockpit dhcpv6-client ssh

Tests completed.


fix(socketio): Fix MaxListenersExceededWarning

Closes: #308

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Comment & Uncomment Selected text from a Query

I would like to comment & un comment selected text from a query instead the full row
Example  :
Select * From Tbl_Temp Where Active  = 1 And Dept = 1024
Comment selected text " And Dept = 1024 "
Select * From Tbl_Temp Where Active  = 1  /And Dept = 1024/

SQL Operations Studio Version: 0.32.2

Steps to Reproduce:

The comment\uncomment behavior is part of the editor platform we inherit from vscode. We prefer to avoid significant changes to the base platform code as it is hard to maintain as we take continual vscode source code updates.  Please log this issue in the vscode repo for their consideration.  Thanks!


Cypress Best Practices

Moved logout command from afterEach to beforeEach. A Cypress test could be interrupted and tests that follow may fail since the afterEach logout would not have run - https://docs.cypress.io/guides/references/best-practices.html#Using-after-or-afterEach-hooks
Removed out of date log messages in beforeEach
Added some TODO notes to the afterEach wait command (related to video)

Thanks @bronson-fpcc


Failures new nnbd VM builders on simarm targets

There are new test failures on [infra] Add additional nnbd VM builders
language/mixin_constructor_forwarding/const_constructor_test/issue38304 (crashes instead of RuntimeError)
language/mixin_constructor_forwarding/mixin_constructor_parameter_forwarding_test (crashes instead of RuntimeError)
standalone/http_launch_test/0
standalone/http_launch_test/1
standalone/http_launch_test/2
standalone/http_launch_test/3

language/mixin_constructor_forwarding/const_constructor_test and language/mixin_constructor_forwarding/mixin_constructor_parameter_forwarding_test are currently passing (https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket.appspot.com/8867760015291470256/+/steps/test_results/0/logs/tests_that_began_passing/0).
The fix for standalone/http_launch_test failures: https://dart-review.googlesource.com/c/sdk/+/165406

We have some tests timing out
co19/LibTest/collection/ListMixin/ListMixin_class_A01_t05
co19/LibTest/collection/ListBase/ListBase_class_A01_t05
co19/LibTest/collection/ListBase/ListBase_class_A01_t06
co19/LibTest/collection/ListMixin/ListMixin_class_A01_t04
co19/LibTest/collection/ListMixin/ListMixin_class_A01_t06

The tests
co19/LibTest/collection/ListBase/ListBase_class_A01_t03 Timeout (expected Pass)
co19/LibTest/collection/ListBase/ListBase_class_A01_t04 Timeout (expected Pass)
co19/LibTest/collection/ListMixin/ListMixin_class_A01_t03 Timeout (expected Pass)
co19/LibTest/core/List/List_all_t03 Timeout (expected Pass)
co19/LibTest/core/List/List_all_t04 Timeout (expected Pass)
co19/LibTest/core/List/List_all_t05 Timeout (expected Pass)
co19/LibTest/core/List/List_all_t06 Timeout (expected Pass)

are failing on configurations
dartkp-strong-linux-debug-x64
dartkp-weak-asserts-linux-debug-x64

The tests in co19/LibTest/collection/ListMixin/, co19/LibTest/collection/ListBase/ and co19/LibTest/core/List/ mentioned above perform sorting of large lists specified by enormous list literals (they include co19/src/LibTest/core/List/sort_A01_t05.test.dart, co19/src/LibTest/core/List/sort_A01_t06.test.dart, co19/src/LibTest/core/List/sort_A01_t07.test.dart or co19/src/LibTest/core/List/sort_A01_t08.test.dart).
I saw 2 kinds of timeouts on those tests:

Timeouts at run time on simulated architectures (-simarm, -simarm64). Simulator is inherently slower than native architectures.
Timeouts in gen_snapshot on AOT/debug configurations (dartkp-*-debug-*). In this case it looks like we have too heavy assertions in debug mode which slow down compilation considerably.

I wasn't able to reproduce some of these timeouts locally (although running those tests takes considerable time).
For timeouts which I could reproduce, corresponding co19_2 legacy test also times out.
These timeouts seems to be unrelated to NNBD. We just don't currently run legacy co19_2 tests on these configurations.
I think we can do one of the following:

Skip those tests on the simulated and aot/debug configurations. This would make bots faster but potentially reduce test coverage.
Mark them as Pass, Slow. This may or may not work depending on the test, and would result in slower bots and higher probability of flaky timeouts on these tests.
Ask co19 folks to cut down those tests.

I'm leaning towards skipping those tests if $arch == simarm || $arch == simarm64 || ($runtime == dart_precompiled && $mode == debug).
@a-siva @mkustermann What do you think?

@alexmarkov As a general rule, we should avoid skipping tests or polluting status files / approval database. So if we can reduce the runtime of those tests by making them do less work without sacrificing what the test is actually testing, I would suggest to file a co19 issue to make them faster.


⚠ Fortnite has degraded performance

In 0819606, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1527 ms

Resolved: Fortnite performance has improved in 1d749d7.


Support for Powermock

I am trying to incorporate Powermock as a dependency for my Android tests using the following build.gradle configuration:
dependencies{
    compile 'com.android.support:appcompat-v7:21.0.+'
    androidTestCompile('org.mockito:mockito-core:1.9.5')
    androidTestCompile('com.google.dexmaker:dexmaker:1.2')
    androidTestCompile('com.google.dexmaker:dexmaker-mockito:1.2')
    androidTestCompile('org.powermock:powermock-module-junit4:1.5.5') {
        exclude module: 'junit'
    }
    androidTestCompile('org.powermock:powermock-api-mockito:1.5.5') {
        exclude module: 'mockito-all'
    }
}

However, the compiler is complaining that
Error:Gradle: Execution failed for task ':app:packageDebugTest'.
> Duplicate files copied in APK mockito-extensions/org.mockito.plugins.MockMaker
  	File 1: ~/.gradle/caches/modules-2/files-2.1/com.google.dexmaker/dexmaker-mockito/1.2/b99884a4c6ef6335ba376f79aa79632b2421c17c/dexmaker-mockito-1.2.jar
  	File 2: ~/.gradle/caches/modules-2/files-2.1/com.google.dexmaker/dexmaker-mockito/1.2/b99884a4c6ef6335ba376f79aa79632b2421c17c/dexmaker-mockito-1.2.jar

Looking into the jar structure, I noticed that both Dexmaker and Powermock declare a MockMaker in mockito-extensions

What is a MockMaker? How do they differ?
And the most important question: Is it possible to get Powermock to work nicely with Dexmaker?
Thanks in advance. Any help would be greatly appreciated.

@littledot Are you running Instrumentation tests that run on a device or pure Java unit tests that run in a standard JVM?
If you are talking the former, then even if dexmaker fixed this issue, you would still have trouble.
This issue explains it nicely

PowerMock won't work on Android if you run it
on a device since PowerMock is using JVM byte code manipulation. It will
work if you run it on a JVM though.

I mention this because your example shows you using androidTestCompile instead of testCompile.

so sad

Thanks for clarifying~


Pax new completion badge

write job status to a json file
run publish badge workflow using that status

I've replaced the badge url for pax. This badge is just tracking if the jobs completed, next steps will be to check the results of passing tests against a loss and iter time baseline.

Thanks for fixing this! Now we'll have a better idea what's failing


pre_train model and dataset link has been invalid!

please refresh the link,Thank you!

have the same issue, please consider renew the links if possibile

Hi the pre_train model is not accessible. The link to the models has been expired. could you please share the pretrained models?

have the same issue,please refresh the link,Thank you!


docs(v2): 2020 recap blog post

Motivation
https://deploy-preview-4020--docusaurus-2.netlify.app/classic/blog/2020/01/12/docusaurus-2020-recap/

I feel we should give MLH special mention as its own category.

Did we remove the MLH call out in the post? I only see one mention of it in a bullet under Media. Or am I missing something?

I feel we should give MLH special mention as its own category.

Did we remove the MLH call out in the post? I only see one mention of it in a bullet under Media. Or am I missing something?

Nevermind my previous comment. I just totally missed it.

Nevermind my previous comment. I just totally missed it.

Hi @JoelMarcey 👋
You are missing out on a great GitHub feature! You can make your improvements easy to implement for the maintainers by using the "suggestions" feature in GitHub.
I suggest you check out the GitHub docs, adding line comments to a pull request
Step number 6 is the good stuff!
By doing it this way, you also get credits as a "co-author" in the Git commit!
I hope you find this useful! 😄 😉
Greetings,
HonkingGoose

Hi @JoelMarcey 👋
You are missing out on a great GitHub feature! You can make your improvements easy to implement for the maintainers by using the "suggestions" feature in GitHub.
I suggest you check out the GitHub docs, adding line comments to a pull request
Step number 6 is the good stuff!
By doing it this way, you also get credits as a "co-author" in the Git commit!
I hope you find this useful! 😄 😉
Greetings,
HonkingGoose

I just thought, if someone has a photo of Docusaurus plushie (I don't have one), it would be nice to use it as the main picture of new blog post.

I just thought, if someone has a photo of Docusaurus plushie (I don't have one), it would be nice to use it as the main picture of new blog post.

I don't think it's easy to get one as people are working remotely.
Apart this one from google that is not very suitable for a banner/social card imho: https://twitter.com/ericnakagawa/status/942819218684182528/photo/1
We are going to publish very very soon so maybe we can find a better one for the next blog post (that is going to be quite soon as i18n is ready :p)

I don't think it's easy to get one as people are working remotely.
Apart this one from google that is not very suitable for a banner/social card imho: https://twitter.com/ericnakagawa/status/942819218684182528/photo/1
We are going to publish very very soon so maybe we can find a better one for the next blog post (that is going to be quite soon as i18n is ready :p)

My twitter profile has a Docusaurus plushie picture, if we want to use that? And I think I have another picture lying around too.

My twitter profile has a Docusaurus plushie picture, if we want to use that? And I think I have another picture lying around too.


Nelson Mandela Bay Metro street addresses

http://www.nelsonmandelabay.gov.za/datarepository/documents/street-address.zip

Connects with https://github.com/openaddresses/openaddresses/pull/2144, which was merged.


The problems of multi host healthcheck and scheduler

Rancher versions:
rancher/server:v1.6.11
rancher/agent:v1.2.7
Infrastructure Stack versions:
healthcheck:v0.3.3
ipsec:v0.13.2
network-services:v0.9.5
scheduler:v0.8.2
kubernetes (if applicable):null
root@ubuntu:/var/lib/rancher# docker info
Containers: 10
Running: 10
Paused: 0
Stopped: 0
Images: 11
Server Version: 17.03.1-ce
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 67
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: active
NodeID: nlix8v2qufh30gg8uulij898x
Is Manager: true
ClusterID: 0yte1awl1bup4pvvcn1ahf331
Managers: 1
Nodes: 2
Orchestration:
Task History Retention Limit: 5
Raft:
Snapshot Interval: 10000
Number of Old Snapshots to Retain: 0
Heartbeat Tick: 1
Election Tick: 3
Dispatcher:
Heartbeat Period: 5 seconds
CA Configuration:
Expiry Duration: 3 months
Node Address: <IP_ADDRESS>
Manager Addresses:
<IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
apparmor
Kernel Version: 4.4.0-31-generic
Operating System: Ubuntu 14.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.937 GiB
Name: ubuntu
ID: QFKM:XNH6:YYJ3:LYOI:SJO6:LQLS:SXBN:2RSE:WYRH:WTJF:WRIZ:RXYA
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: jarno517
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
Hi：
I installed rancher on 1 hosts and added another host (non HA). I observed that my healthcheck and scheduler always showed yellow hints. Is this normal?
And it's not a long time to restart healthcheck?

Scheduler's log is as follows:
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Connecting to cattle event stream."
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Subscribing to metadata changes."
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Listening for health checks on <IP_ADDRESS>:80/healthcheck"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Initializing event router" workerCount=100
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Connection established"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Starting websocket pings"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 10 for host  a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [cpuReservation] with total 1000 and used 0 for host  a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host  a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [storageSize] with total 13614227 and used 0 for host  a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [portReservation], ip set [<IP_ADDRESS>], ports map tcp map[<IP_ADDRESS>:map[2201:d7b48aca-547d-4a4c-9d10-ed131d94b097 8801:d7b48aca-547d-4a4c-9d10-ed131d94b097 8080:88bfc890-c8b4-48fb-9eb3-93a12bd7f176]], ports map udp map[<IP_ADDRESS>:map[500:3942fe9e-71b7-4420-8bc6-3f3a6eb7538b 4500:3942fe9e-71b7-4420-8bc6-3f3a6eb7538b]] for host a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [hostLabels] with label map [map[io.rancher.host.agent_image:rancher/agent:v1.2.7 io.rancher.host.docker_version:17.03 io.rancher.host.linux_kernel_version:4.4]]"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 9 for host  97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [cpuReservation] with total 1000 and used 0 for host  97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host  97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [storageSize] with total 15768231 and used 0 for host  97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [portReservation], ip set [<IP_ADDRESS>], ports map tcp map[<IP_ADDRESS>:map[5000:156818ff-7d03-422d-9be7-6e79cd9ade02]], ports map udp map[<IP_ADDRESS>:map[500:7a622d1b-eaac-4a92-b165-d9bcd56297ea 4500:7a622d1b-eaac-4a92-b165-d9bcd56297ea]] for host 97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/28 下午4:08:50time="2017-11-28T08:08:50Z" level=info msg="Adding resource pool [hostLabels] with label map [map[io.rancher.host.agent_image:rancher/agent:v1.2.7 io.rancher.host.docker_version:17.03 io.rancher.host.linux_kernel_version:4.4]]"

I was facing the same issue, although I deleted the healthcheck stack and re-created using the Catalog. Now helathcheck is green but scheduler is still yellow and no logs at all

@yangjia517 The docker info output shows the node is part of a Swarm cluster, are you deploying as a stack or separate docker run commands? Can you supply the steps you took to get the environment in this state so I can reproduce?
@Edenshaw Same question for you.
Things to check are:

Are all the hosts in Infrastructure -> Hosts view showing the correct IP address (and that they can reach other using UDP/500 and UDP/4500)
Is cross-host networking working properly? (you can run the following command inside a ipsec-router container:

for i in `curl -s <IP_ADDRESS>/latest/self/service/containers/` ; do id=$(echo $i| cut -f1 -d=) ; name=$(echo $i| cut -f2 -d=) ; echo " ---- $name --------" ; ping -c2 `curl -s curl <IP_ADDRESS>/latest/self/service/containers/$id/primary_ip` ; done

If scheduler is stuck in Initializing, you can check the logs by using View Logs in the UI or docker logs on the host where the scheduler container is running.

As you say, I've built swarm before, and now I've run docker swarm leave.
According to your suggestion, check the results:

scheduler View Logs：
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Connecting to cattle event stream."
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Subscribing to metadata changes."
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Listening for health checks on <IP_ADDRESS>:80/healthcheck"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 10 for host  97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [cpuReservation] with total 1000 and used 0 for host  97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host  97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [storageSize] with total 15768231 and used 0 for host  97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [portReservation], ip set [<IP_ADDRESS>], ports map tcp map[<IP_ADDRESS>:map[5000:156818ff-7d03-422d-9be7-6e79cd9ade02]], ports map udp map[<IP_ADDRESS>:map[500:7a622d1b-eaac-4a92-b165-d9bcd56297ea 4500:7a622d1b-eaac-4a92-b165-d9bcd56297ea]] for host 97d800e6-2bbb-42e4-b238-962037e3a516"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [hostLabels] with label map [map[io.rancher.host.agent_image:rancher/agent:v1.2.7 io.rancher.host.docker_version:17.03 io.rancher.host.linux_kernel_version:4.4]]"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 10 for host  a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [cpuReservation] with total 1000 and used 0 for host  a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host  a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [storageSize] with total 13614227 and used 0 for host  a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [portReservation], ip set [<IP_ADDRESS>], ports map tcp map[<IP_ADDRESS>:map[2201:d7b48aca-547d-4a4c-9d10-ed131d94b097 8801:d7b48aca-547d-4a4c-9d10-ed131d94b097 8080:88bfc890-c8b4-48fb-9eb3-93a12bd7f176]], ports map udp map[<IP_ADDRESS>:map[500:3942fe9e-71b7-4420-8bc6-3f3a6eb7538b 4500:3942fe9e-71b7-4420-8bc6-3f3a6eb7538b]] for host a2a6c585-fce9-44c9-a138-270cba0e31ba"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Adding resource pool [hostLabels] with label map [map[io.rancher.host.agent_image:rancher/agent:v1.2.7 io.rancher.host.docker_version:17.03 io.rancher.host.linux_kernel_version:4.4]]"
2017/11/29 上午10:31:49time="2017-11-29T02:31:49Z" level=info msg="Initializing event router" workerCount=100
2017/11/29 上午10:32:16time="2017-11-29T02:32:16Z" level=info msg="Connection established"
2017/11/29 上午10:32:16time="2017-11-29T02:32:16Z" level=info msg="Starting websocket pings"

No, the 172.17 one is the Docker interface.  Each host needs a unique IP that every other host in the environment can reach.  You do not have that.  If that is the host that is running the server container, auto-detection of the right IP cannot be done and you need to provide it with the CATTLE_AGENT_IP environment variable.

@vincent99 Thank you very much for your answer。
How should I increase the variables?

like this?
sudo docker run -e CATTLE_AGENT_IP=<IP_ADDRESS> -d --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent:v0.7.9 http://<IP_ADDRESS>:8080/v1/scripts/DB121CFBA836F9493653:1434085200000:2ZOwUMd6fIzz44efikGhBP1veo

@vincent99 @superseb
The problem has been solved, thank you very much!
Explain：
You need to specify CATTLE_AGENT_IP when you add a host, and now all the hosts' healthcheck and scheduler are normal.


rosetta: fix suggested_fee for first transaction.

In rosetta a suggested fee is computed by taking the median of all the fees in recent blocks. This fails however on a newly created blockchain where this array of blocks is empty (as it can be the case for the rosetta-cli tests).
This PR fixes this by returning the minimum_fee in that case.
Explain how you tested your changes:

run the rosetta-cli construction test locally.

!ci-build-me


Adjusting color range for vvenc

I don't understand how to reconcile my source video which is yuvj420p(pc, bt470bg/bt470bg/smpte170m, progressive) with the color formats that vvenc supports: yuv420, yuv420_10, yuv420_10_packed.
vvdec decodes to yuv420p10le which is what is seemingly necessary as an input. However no matter what I do to the input it results in a different color-range-wise output.
By default I used: ffmpeg -i *mp4 out.y4m.
I've also tried, ffmpeg -i *mp4 -strict -1  -pix_fmt yuv420p10le out.y4m with -color_range 1 and -color_range 2.
I've also tried -vf scale=in_range=limited:out_range=full and -vf scale=in_range=full:out_range=limited - no success either.
There's this post by John Carmack but it's about x265, not vvenc: https://news.ycombinator.com/item?id=20036710
Here's the source:

Here's the encode:

Screenshots are produced by mpv. As you can see the grass on the second shot (encode) is more yellow/red. The plastic glass shield is a lot darker - it almost lost its transparency.

If we are talking about ffmpeg then for 8bit it should be:
ffmpeg.exe -i VID_20190409_090117.mp4 -f rawvideo -vf scale=1920:1080:in_color_matrix=bt470bg:in_range=full:out_color_matrix=bt709:out_range=limited,format=yuv420p input.yuv
Then the codec test.
VVEncoderApp is only for bt709. I have problem with the 60000/1001 framerate
uvg266e.exe -i "input.yuv" -o "output_uvg266.vvc" --no-info --input-bitdepth 8 --threads 4 --input-res 1920x1080 --input-fps 60000/1001 --input-format P420 --gop=16 --ref=4 --bipred --gop lp-g16d4t1 -p 256 --bitrate 6000000 --preset medium --level 6.2 --colormatrix bt709
xeve_app.exe -i "input.yuv" -o "output.evc" --info 0 -v 2 -q 30 -m 4 -d 8 -w 1920 -h 1080 -z 60000/1001 --preset medium --profile main --bitrate 6000000 --level-idc 6.2 --matrix-coefficients 1
VVEncoderApp_avx.exe -v 5 -t 4 -s 1920x1080 --framerate 60000 --framescale 1001 -c yuv420 -q 30 --bitrate 6000000 --passes 1 --preset medium --level 6.2 --tier high -i "input.yuv" -o "output_vvenc.vvc"

-vf scale=1920:1080:in_color_matrix=bt470bg:in_range=full:out_color_matrix=bt709:out_range=limited,format=yuv420p

Will try this, thanks!

-vf scale=in_color_matrix=bt470bg:in_range=full:out_color_matrix=bt709:out_range=limited,format=yuv420p

Will try this, thanks!

This has worked perfectly, thanks a ton!

So, first of all, please don't add resolutions to the issues, that's up to us.
Second, about your actual problem.
yuv420 vs yuv420p10le is about the data layout, both layouts can contain any color space you want. VVenC does not assume either full nor restricted range, and would just try to reproduce the input as good as possible.
Now your problem is the meaning of the values, which is independent of the sample representation within the core codec. The meaning of the samples values would be signaled in some form of high level or supplementary information. Here the question is, does your player understand those and apply them correctly?
For VVenC you could set --TransferCharacteristics=bt470bg --MatrixCoefficients=bt470bg (only directly available in FF-app, for simple app would need to be passed through the additional-parameter). Now your player should be able to understand the values correctly. This is of course assuming you are playing the VVC bitstream in your player directly. If you do conversions to and from YUV its up to you to maintain correct metadata.
To be fair tho, we only really test bt709 and bt2020 color spaces, so there might be more to be done here. Feedback appreciated.

@adamjw24
Here's the issue.
The second screenshot belongs to the y4m stream produced by vvdec, so the player, mpv, is unlikely to add any of its own processing (it absolutely does, it needs to convert yuv420_10 to RGB but it doesn't AFAIK change the palette).

Alright, I see the problem. Could you please list all the steps you do starting from the input file and define at which point do you view the results to see the difference described above?
Best regards,
Adam

ffmpeg -i source.mp4 out.y4m
vvencapp --preset slower -qp 20 -i out.y4m --output=bit.266 # version 1.6.1
vvdecapp --bitstream bit2.266 --output result.y4m # version 1.6.0

Take screenshots of source.mp4 and result.y4m.

View out.y4m and see if the problem is already visible there.

And if thats possible could you post the Y4M header of out.y4m?

View out.y4m and see if the problem is already visible there.

You're right, the resulting y4m file already looks different. Looks like this is an invalid bug report. Sorry.

And if thats possible could you post the Y4M header of out.y4m?

(This is a xz file, not zip).
short.y4m.xz.zip

And if thats possible could you post the Y4M header of out.y4m?

(This is a xz file, not zip).
short.y4m.xz.zip

Yeah, as I was expecting. The y4m does not have any color space related metadata. So thats the step your information gets lost. You would need to tell mpv when displaying the raw data what color space to use.

Let's close as invalid then.

Let's close as invalid then.

Let's close as invalid then.


Feedback for “HuggingFace”

MONGO_URI
Please, i don't know what this means.
It just says * use the string aquired in the previous step.
it's so unclear i'm getting frustred.

Sorry about that, the info was indeed missing. Will fix soon. This is how you get the MONGO_URI : https://librechat.ai/docs/configuration/mongodb/mongodb_atlas


[FLOC-3162] Pass the current process name as SYSLOG_IDENTIFIER to journald API

Temporary fix for: https://clusterhq.atlassian.net/browse/FLOC-3162
Until Eliot 0.9.0 and https://clusterhq.atlassian.net/browse/FLOC-3145 land.

eliot 0.9.0 should be out tomorrow, so might as well wait for them.

Ok, we're almost ready to release Eliot 0.9.0 so this temporary fix isn't necessary.


Add scheduler and de-scheduler configuration

Use the same configurations used in eventing-kafka

Part of #1537

/test pull-knative-sandbox-eventing-kafka-broker-upgrade-tests


[BUG][0.3.1] memsource job create --debug has empty output

Describe the bug
memsource job create --debug has empty output
Affected version
<0.3.1
To Reproduce
$ memsource job create --debug
Result: nothing
Expected behavior
A log should be displayed.
Screenshots or Traceback
n/a
Additional context
n/a

https://github.com/unofficial-memsource/memsource-cli-client/commit/59a9d27a64482ab700519987c159794a8159f115


Default font sizes for "Normal" and "Smaller" swapped

The current (caaf6ef679fab3984e75e0e356a804250d2ff53c) default values for the font sizes are:
		{ label:'Size', type:'size', items: [
			{ label:'Normal',  value:'10px' },
			{ label:'Smaller', value:'13px' },
			{ label:'Larger',  value:'18px' },
			{ label:'Huge',    value:'32px' }
		]}

I suspect "Normal" should be 13px and "Smaller" then 10px.
Ideally the order would still be "Smaller", "Normal", "Larger", "Huge", but it looks like the first element is assumed to be "Normal"? I haven't investigated this, but it'd be nice if above were the default option order and "Normal" were the default selection.

+1

+1

Thanks a lot for noticing that. I've corrected the default items, and sorted out the selection state.


filter false doesn't work

I tried filter false, and also
before_filter :skip_sidebar!, :only => :index
neither works.  filter false displays a blank filter panel and skip_sidebar errors out.

You might want to join in issue #257, disable filters on index page.
I'm not sure what you're trying to do, but you might try the technique described in issue #297.

That works!  however what if I also want to remove the filters conditionally?  ie:
config.clear_sidebar_sections!, :unless => proc{ current_user.admin? }
That doesn't work.

You are in ActiveAdmin filter-land, but that statement is just vanilla Ruby. Try removing some doo-dads.
config.clear_sidebar_sections! unless proc { current_user.admin? }

@holden This seems to be a support request, would you mind re-posting your question on our Google Group (http://groups.google.com/group/activeadmin)? We're trying to limit Github Issues to only feature requests and bug reports.
Thanks!


[📑 Docs]: document payload schema

What Dev Docs changes are you proposing?
As part of Google Season of Docs 2023 at AsyncAPI, we're going to write in-depth explanations of the different sections of an AsyncAPI document to avoid difficulties in implementing EDAs.
This task is part of the Docs EPIC: https://github.com/asyncapi/website/issues/1507.
For this issue, we'll cover:

Payload schema - More complex message example with payload added using JSON and Avro schemas, and explain how to specify them. Explain how to reuse schema from components.

Code of Conduct

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

I suggest we clarify in the description of this issue that this doc should be based on AsyncAPI Spec version 3.

The issue in context is now resolved as PR #2414(merged) adds the document intended to the AsyncAPI website. Hence, closing the issue.


curl convert to json error

Error: found "variable_assignment" AST node, only "command", "pipeline" or "redirected_statement" are supported
curl www.baidu.com/a/b/c?x=1&c=3
^^^

put the url in quotes
curl 'www.baidu.com/a/b/c?x=1&c=3'

it won't work as a command either


build(npm): allow React 17 as peerDependency

React 17 was released recently and can be allowed in the peerDependencies to avoid warnings when requiring react-geolocated in a React 17 project.

Hi @danbtl thank you for the contribution :) have you tested it in some react 17 application?

Also, please change the commit message to start with feat so that it is released as a minor change after this is merged.

@no23reason Yes, I did test it (I should have mentioned). No issues, only the peerDependency version warning. Hence this small PR.

Awesome, thank you very much 🙂  merging


Request to use jackson-databind-2.10.0 or later

Several security vulnerabilities have been identified with jackson-databind-2.9.10 and earlier. This request is to update the dependency to 2.10.0 or later where the vulnerabilities have been resolved.

The 5.2 module was upgraded to use the <IP_ADDRESS> Jackson Databind version. The other modules are meant to be compiled and run with the minimum version of Java required by the associated Hibernate version. Now, since Jackson does not maintain those branches, nothing can be done about it. It's the responsibility of the user to upgrade these dependencies, as they are transient to this project.


python310Packages.cleo: 1.0.0a5 -> 2.0.1

Description of changes
fixes CVE-2022-42966
https://github.com/python-poetry/cleo/blob/2.0.1/CHANGELOG.md

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Yep but it will break a bunch of packages. I do not have the resources to do a full nixpkgs-review run right now but a partial run shows a bunch of issues:
error: builder for '/nix/store/z5rkz9mpc3373mqg2ak2ixncfx91pssp-python3.10-poetry-1.2.2.drv' failed with exit code 1;
       last 10 log lines:
       > Requirement already satisfied: requests-toolbelt<0.10.0,>=0.9.1 in /nix/store/g6klr9lgfrkxf7wkdsf7r9pc39n45hgd-python3.10-requests-toolbelt-0.9.1/lib/python3.10/site-packages (from poetry==1.2.2) (0.9.1)
       > Requirement already satisfied: pexpect<5.0.0,>=4.7.0 in /nix/store/lxinahd9qhdzmqia3493mrgkqh3ingig-python3.10-pexpect-4.8.0/lib/python3.10/site-packages (from poetry==1.2.2) (4.8.0)
       > Requirement already satisfied: poetry-core==1.3.2 in /nix/store/y7m62x2v20cxga1vpqr7kmbgc6nibs5s-python3.10-poetry-core-1.3.2/lib/python3.10/site-packages (from poetry==1.2.2) (1.3.2)
       > Requirement already satisfied: shellingham<2.0,>=1.5 in /nix/store/2qskk48bga2hpwcy2bpp9idcx9bf370q-python3.10-shellingham-1.5.0/lib/python3.10/site-packages (from poetry==1.2.2) (1.5.0)
       > Requirement already satisfied: requests<3.0,>=2.18 in /nix/store/msn1w5hapjnckz4dnkjpmjwp88421a5z-python3.10-requests-2.28.1/lib/python3.10/site-packages (from poetry==1.2.2) (2.28.1)
       > Requirement already satisfied: jsonschema<5.0.0,>=4.10.0 in /nix/store/cxn5s0s9zgh0czm8w85wwi3rjpvnfk2c-python3.10-jsonschema-4.17.0/lib/python3.10/site-packages (from poetry==1.2.2) (4.17.0)
       > Requirement already satisfied: pkginfo<2.0,>=1.5 in /nix/store/qnnhxhsylg7m63blsy13wk86z6xivn17-python3.10-pkginfo-1.8.3/lib/python3.10/site-packages (from poetry==1.2.2) (1.8.3)
       > ERROR: Could not find a version that satisfies the requirement cleo<2.0.0,>=1.0.0a5 (from poetry) (from versions: none)
       > ERROR: No matching distribution found for cleo<2.0.0,>=1.0.0a5
       >
       For full logs, run 'nix log /nix/store/z5rkz9mpc3373mqg2ak2ixncfx91pssp-python3.10-poetry-1.2.2.drv'.
error: 1 dependencies of derivation '/nix/store/44nbpzw1i0h7n23p6nxb412mlcf65pm6-cmake-language-server-0.1.6.drv' failed to build
error: 1 dependencies of derivation '/nix/store/x4kvablv4h9lcm2jrfqpvxzdrww9rjwj-commitizen-2.37.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/hyzpbhllfslagkay8gnps8a74v7wirjr-poetry2conda-0.3.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/hck7hrbv7kpa7fmj7cywlzql9mxdjjyk-python3.10-aioeafm-1.0.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/hw2x4kwa55kx4hqmfal0q9r45snw9849-python3.10-aioeafm-1.0.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/5i657qdzihs5gmvipx4apyigxccxx0fx-python3.10-aria2p-0.9.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/m727mvcmkgfvq2cfj40v0vrbrpnl2ycn-python3.10-expecttest-0.1.3.drv' failed to build
error: 1 dependencies of derivation '/nix/store/a3mx88kfa3ry1jh6fphrh0agcnp34d6a-python3.10-hypothesis-auto-1.1.4.drv' failed to build
error: 1 dependencies of derivation '/nix/store/gr2vjq4cay7jifk516wkqlm8f1v0bjjm-python3.10-jedi-language-server-0.37.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/bgkivwx5jxz94ymdhdkgqwgvkx4wx3ng-python3.10-pipenv-poetry-migrate-0.2.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/b1agvxw454vkh3q69fc6kdkalanc38zz-python3.10-pyairnow-1.1.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/s12v2dbavb70wa1qm40sc3qynhdsdvh2-python3.10-pyairnow-1.1.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/45agyarfc41m9d4wsym7q320ynx1a7cj-python3.10-pytest-golden-0.2.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/v57q4d9ijmg8qx6qfbxnlcsfhxa197kw-python3.10-strawberry-graphql-0.125.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/8lazf3b1311s6xqi612a5ld3pl4fgchf-homeassistant-test-airnow-2022.11.4.drv' failed to build
error: 1 dependencies of derivation '/nix/store/3hamkasyvk015q6bnhacgv92nsgin0dr-homeassistant-test-eafm-2022.11.4.drv' failed to build
error: 1 dependencies of derivation '/nix/store/36bjqd4rrvwchpvi1rz2w0rjff5bqyv2-python3.10-functorch-0.2.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/a7i729ib816n2c1m9p4f8ayrzf9aqf2f-python3.10-ical-4.1.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/p11qvs4agxrl75dqn3fsfi0kfmf17qw7-streamdeck-ui-2.0.6.drv' failed to build
error: 1 dependencies of derivation '/nix/store/2adand7d4i7a4j1y424g69q5bkvswqn8-vscode-extension-ms-python-python-2022.17.13011006.drv' failed to build
error: 1 dependencies of derivation '/nix/store/n184plx7npip0phbdqkk8zyxrxsay10f-ycmd-unstable-2022-08-15.drv' failed to build
error: 1 dependencies of derivation '/nix/store/aiv0y4wgwr9g203mi79mxyq62qsznyyp-python3.10-gcal-sync-4.0.3.drv' failed to build
error: 1 dependencies of derivation '/nix/store/sc1lb9q9649dcb37pzxvsb53kpsih98n-python3.10-gcal-sync-4.0.3.drv' failed to build
error: 1 dependencies of derivation '/nix/store/xj4pz8947k9368kqgirqyxdf4knzsm76-vimplugin-YouCompleteMe-2022-11-19.drv' failed to build
error: 1 dependencies of derivation '/nix/store/sx1kdkfvayp0mmbgbzr83cakxsvvi49s-homeassistant-test-google-2022.11.4.drv' failed to build
error: builder for '/nix/store/5fn5whs8ipfdjn8nf01dgf8zgpg3kvy3-python3.10-pyatv-0.10.3.drv' failed with exit code 1;
       last 10 log lines:
       >   /build/source/tests/protocols/raop/test_raop_functional.py:484: DeprecationWarning: Call to deprecated function volume_down.
       >     await volume_interface.volume_down()
       >
       > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
       > =========================== short test summary info ============================
       > FAILED tests/protocols/mrp/test_mrp_auth.py::MrpAuthFunctionalTest::test_authentication
       > FAILED tests/protocols/mrp/test_mrp_auth.py::MrpAuthFunctionalTest::test_pairing_with_bad_pin
       > FAILED tests/protocols/mrp/test_mrp_auth.py::MrpAuthFunctionalTest::test_pairing_with_device
       > FAILED tests/protocols/mrp/test_mrp_auth.py::MrpAuthFunctionalTest::test_pairing_with_existing_credentials
       > =========== 4 failed, 995 passed, 1 skipped, 288 warnings in 11.97s ============
       For full logs, run 'nix log /nix/store/5fn5whs8ipfdjn8nf01dgf8zgpg3kvy3-python3.10-pyatv-0.10.3.drv'.
error: builder for '/nix/store/ianwyyi9m3shcx3y22127h676qrj1fb2-python3.9-poetry-1.2.2.drv' failed with exit code 1;
       last 10 log lines:
       > Successfully built poetry
       > Finished creating a wheel...
       > Finished executing pipBuildPhase
       > installing
       > Executing pipInstallPhase
       > /build/source/dist /build/source
       > Processing ./poetry-1.2.2-py3-none-any.whl
       > ERROR: Could not find a version that satisfies the requirement cleo<2.0.0,>=1.0.0a5 (from poetry) (from versions: none)
       > ERROR: No matching distribution found for cleo<2.0.0,>=1.0.0a5
       >
       For full logs, run 'nix log /nix/store/ianwyyi9m3shcx3y22127h676qrj1fb2-python3.9-poetry-1.2.2.drv'.

At least for the backports will probably need to apply the patch to limit the potential breakages.

Instead of python310Packages.poetry people should really be using python310Packages.poetry-core so it's fine if that breaks.
@abbradar poetry as packaged by poetry2nix is also affected by this CVE. Please fix.

poetry and poetry2conda are the only packages still failing for me, aarch64-linux.

Instead of python310Packages.poetry people should really be using python310Packages.poetry-core so it's fine if that breaks.

They're not quite the same thing though. One is a CLI interface, the other is a build library.

Instead of python310Packages.poetry people should really be using python310Packages.poetry-core so it's fine if that breaks.

They're not quite the same thing though. One is a CLI interface, the other is a build library.

True, but poetry is also the CLI and isn't broken (yet).

I  did have to patch some packages i just use in a private project to use the core.mansory api, to make them usable with poetry-core.
  postPatch = ''
    substituteInPlace pyproject.toml \
      --replace 'build-backend = "poetry.masonry.api"' 'build-backend = "poetry.core.masonry.api"'
  '';

Just in case someone else comes around here.


Removing points from interval

The following used to work on DomainSets v0.7.0, but throws an error on recent releases (e.g. v0.7.8). Is this a breaking change?
julia> (-1 .. 1) \ 0
(-1 .. 0 (closed-open)) ∪ (0 .. 1 (open-closed))

julia> @which (-1 .. 1) \ 0
\(d1::AnyDomain, d2)
     @ DomainSets ~/.julia/packages/DomainSets/WAqmd/src/generic/setoperations.jl:306

This has broken the tests for ApproxFunOrthogonalPolynomials

Hmm, depending on one's point of view it is either a breaking change or it was a bug to begin with. The issue is that an operator from Base (here setdiff) is used with a domain argument and with an argument of another type. The philosophy of the domain-interface 0.7 series was to have domain-specific functions (in this case setdiffdomain) and domain references when using standard operators or functions defined elsewhere (such as setdiff). The code should do one of:
julia> (-1..1) \ Point(0)
(-1 .. 0 (closed-open)) ∪ (0 .. 1 (open-closed))

julia> (-1..1) \ DomainRef(0)
(-1 .. 0 (closed-open)) ∪ (0 .. 1 (open-closed))

julia> setdiffdomain(-1..1, 0)
(-1 .. 0 (closed-open)) ∪ (0 .. 1 (open-closed))

What's the corresponding solution for
julia> (-1..1) \ [-0.05,0.45]
(-1.0 .. 1.0) \ v

v = 2-element Vector{Float64}:
 -0.05
  0.45

julia> (-1..1) \ [-0.05,0.45] |> typeof
SetdiffDomain{Float64, Tuple{ClosedInterval{Float64}, Vector{Float64}}}

It might be better to deprecate these instead of removing directly so that the transition is smoother.

agree, deprecation was the way to go here