Local Port seems to have changed

1. Problem Description
To connect to Pieces OS, we have the following code in Embeetle IDE:
if on_windows:
    PIECES_BASE_URL = 'http://localhost:1000'
else:
    PIECES_BASE_URL = 'http://localhost:5323'

So far, this has always worked. But it now fails on my Ubuntu VM. After listing all the local ports in use, I had a stroke of luck by changing PIECES_BASE_URL to 'http://localhost:39300'.
Please give us a suggestion on how we should determine the PIECES_BASE_URL programmatically (with Python, assume no sudo rights).

2. Context
Not sure if this is relevant, but here is our code snippet for checking if the server is listening:
def is_server_listening(url: str, timeout: int = 1) -> bool:
    parsed_url = urllib.parse.urlparse(url)
    host = parsed_url.hostname
    port = parsed_url.port
    path = parsed_url.path or "/"
    if parsed_url.scheme != "http":
        return False
    conn = http.client.HTTPConnection(host, port, timeout=timeout)
    try:
        conn.request("GET", path)
        response = conn.getresponse()
        if response.status == 200:
            return True
        else:
            return True
    except (http.client.HTTPException, socket.timeout, socket.error) as e:
        print(e)
        return False
    finally:
        conn.close()
    return False

The url parameter passed to that function is the PIECES_BASE_URL variable mentioned earlier.
Then, if that function returns True, we pass the PIECES_BASE_URL to our PiecesBridge()-instance:
class PiecesBridge:
    def __init__(self,
                 config: dict[str, str],
                 tracked_application: Optional[pieces_os_client.models.application.Application] = None,
                 proj_rootpath: Optional[str] = None,
                 ):
        """
        The `PiecesBridge()`-instance does all interactions with Pieces OS. This is the single point
        of communication between Embeetle IDE and Pieces OS.
        """
        self.config = pieces_os_client.configuration.Configuration(
            host=config['baseUrl']
        )
        self.__pieces_client = pieces_os_client.wrapper.PiecesClient()
        self.__api_client = self.__pieces_client.api_client
        self.__conversation_message_api = self.__pieces_client.conversation_message_api
        self.__conversation_messages_api = self.__pieces_client.conversation_messages_api
        self.__conversations_api = self.__pieces_client.conversations_api
        self.__conversation_api = self.__pieces_client.conversation_api
        self.__qgpt_api = self.__pieces_client.qgpt_api
        self.__user_api = self.__pieces_client.user_api

        [...]

Where the parameter config is given like this:
pieces_bridge = PiecesBridge(
    config              = { "baseUrl": PiecesCommunicator.PIECES_BASE_URL, },
    tracked_application = None,
    proj_rootpath       = proj_rootpath,
)

Yeah I ran into the same issue this past weekend. For what it's worth, I was running the OS server on a Mac, so it is possible that it isn't OS-specific and it may have just permanently switched to binding to port 39300 instead of port 1000 previously.
If so then you could change the hardcoded value of the base url and see if you run into any problems.
But it would be ideal to have a way to dynamically get the port info from something like the WellKnown API.

Correct @seantiz
The port is now changed
You should be using the PiecesClient().host instead
The port 39300 is not granted to be the correct one

The port should be stored in the com.pieces.os/Config/.config.txt

Correct @seantiz
The port is now changed You should be using the PiecesClient().host instead The port 39300 is not granted to be the correct one
Also make sure to use the PiecesClient().is_pos_running() To make sure it will work if there is further changes in the apis

I mention this here but it is probably a separate issue from the Python SDK: The Typescript SDK has the basepath value hardcoded as port 1000 in the Configuration class. It is possibly to overwrite it but I cannot see any method to retrieve is dynamically from the server at the moment.

Yupp the Typescript sdks doesn't have a wrapper so we won't be able to overwrite any of the auto generated stuff
But you can get the port it should behave in the config file

Thank you @bishoy-at-pieces for the clarifications.
Based on your suggestion to get the URL from the PiecesClient().host, we now have this python function to test if the PiecesOS server is up-and-running:
import urllib.parse
import http.client
import socket

def is_server_listening(pieces_client: pieces_os_client.wrapper.PiecesClient) -> bool:
    '''
    Check if the PiecesOS server is up-and-running and listening to incoming connections.
    '''
    url = pieces_client.host
    print(f"PiecesClient().host = '{url}'")
    try:
        parsed_url = urllib.parse.urlparse(url)
        host = parsed_url.hostname
        port = parsed_url.port
        path = parsed_url.path or "/"
        if parsed_url.scheme != "http":
            return False
        conn = http.client.HTTPConnection(host, port, timeout=1)
        try:
            conn.request("GET", path)
            response = conn.getresponse()
            if response.status == 200:
                return True
            else:
                return True
        except (http.client.HTTPException, socket.timeout, socket.error) as e:
            print(e)
            return False
        finally:
            conn.close()
        return False
    except:
        traceback.print_exc()
    return False

Then, if this function returns False, the PiecesClient()-instance is closed:
pieces_client.close()

And an error message is shown to the user.
Now, I can imagine that you have a better (more stable, performant) is_server_listening() function in mind to check if the PiecesOS server is doing okay. Could you suggest improvements to our is_server_listening() function?

You can do that
is_running = pieces_client.is_pos_running() # this sends a request to the wellknown health

Hi @bishoy-at-pieces ,
Thanks for the suggestions.
Unfortunately, I have another blocking problem now. Before I get to run that is_server_listening(pieces_client) function, I of course first need to have instantiated the PiecesClient()-object:
pieces_client = pieces_os_client.wrapper.PiecesClient()

On Linux, this instantiating of the PiecesClient()-object always works. On Windows, it only works if the PiecesOS server is running. If the PiecesOS server doesn't run, then this line of code blocks.
Basically, there are three things that can happen when running the PiecesClient() constructor, while the PiecesOS server is not running:

Blocking. This is the behavior on Windows, and it is really bad because I don't get the chance to communicate anything to the user. Everything freezes.

Just continue the instantiation (the PiecesClient() object is made). That's the behavior on Linux. This is okay, because then I can give the object to the is_server_listening(pieces_client) function and check if the PiecesOS server is running. If not, I communicate to the user that he/she must start the PiecesOS server and try again.

Throw an exception. This would also be fine for me. Then I can catch the exception and communicate to the user that he/she must start the PiecesOS server.

Thank you @bishoy-at-pieces for the fixes!
I hereby confirm that pieces_os_client==4.1.1 works great on both Windows and Linux. The two codelines I mentioned earlier that were taking up a lot of time on Windows, are now blazing fast!
Thanks for your quick help!

Welcome let me know if you have any other issue!


fix(cli): remove hostname validation when using --host on wandb login

Description

Fixes #6886

What does the PR do?
Some users are working with internal deployments of wandb and using internal DNS hostnames with services such as Tailscale. Right now, if you use an internal hostname (let's say myhost) under which you can access wandbm while the GUI will work at http://myhost:1234, you'll get an error when trying to log in to the instance:
$ wandb login --relogin --host=http://myhost:1234
wandb: You can find your API key in your browser here: http://myhost:1234/authorize
wandb: Paste an API key from your profile and hit enter, or press ctrl+c to quit:
wandb: ERROR Host must be a url in the form https://some.address.com, received http://myhost:1234

This PR removes the check for normalized_host in sdk/lib/apikey.py, everything works as expected without any further changes. The check previously simply makes sure that either a . or localhost is in the hostname before allowing login, which is an excessively restrictive check.
I considered replacing the check with something to verify a valid hostname, but hostnames can be quite varied and shouldn't be a priori checked based on arbitrary checks (e.g. whether they contain a . or localhost).
Basic validation (e.g., whether the URL contains http:// is unaffected).
Testing
How was this PR tested?

Tested trying to log in with invalid wandb --hosts (e.g., --host api.wandb.ai, --host https://wandb.ai), get correct errors: Error: https://wandb.ai is not a valid server address, did you mean https://api.wandb.ai
Tested without --host, and with --host given a valid server address, with internal DNS and without

Could you remove the corresponding unit test as well? https://github.com/wandb/wandb/blob/11a472c9e8cae03f310b5f79137a909ceaadbf18/tests/pytest_tests/unit_tests/test_lib/test_apikey.py#L14-L17

@timoffex thanks, just removed


Issue 13116 - Should not be able to return ref to 'this'

The deprecation is introduced in 2.068.0 (Aug 09, 2015 - changelog). It's time to make the old behavior an error.
Related PRs: #3761, #4463, #4497

Fewer lines of code, I love it.

Auto-merge toggled on


MultiSelect does not select the first option

When selecting the first option and clicking on it, the selection disappears without adding it to the multiselect. It works perfect for the others option (see video):
https://goo.gl/photos/rdqxoBG4Txc1RGUX8
Here a fiddle:
https://jsbin.com/nuhosetuco/edit?html,js,console,output
unfortunately, it relies on a external source so the results cant be displayed but the code is there
Any idea what the problem could be?
Thank you!

Also I would like to say that I have 4 multiselect in the page and the first one works perfectly, but the others have this problem...

Still having this issue? Check for any errors in the console. If they are none, then could be a typo, as it was for me a while back.

Your API: http://pybel.scai.fraunhofer.de/api/suggestion/pubmed returns a 404 error for me.  If you are still experiencing this problem, please consider asking on Stack Overflow - the issue tracker is not the correct place for general support.


axios is not sending auth information

I've been trying to send a GET call to the stormpath API which requires some authorization to access the tenant data. When using Postman to test it worked just fine. Same result with curl. But when I tried using axios in my react app I get a 401 error.
XMLHttpRequest cannot load https://api.stormpath.com/v1/tenants/current. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. The response had HTTP status code 401.
this is what I used
 axios({
  method: 'get',
  url: "https://api.stormpath.com/v1/tenants/current",
  auth:
        {
          username: 'api ID',
          password: 'api Secret'
        }
}).then(function(response){console.log(response)})

I don't know why but it's not delivering the username and password according to the response I got.
code:401
developerMessage:"Authentication with a valid API Key is required."
message:"Authentication required."
moreInfo:"http://www.stormpath.com/docs/quickstart/connect"
requestId:"3686f590-d69e-11e6-9b8a-22000a8ce5d1"
status:401

But since the keys I used worked for the above previous cases the keys cannot be the problem. It most likely has to do with my configuration right?

I recently had a similar issue and it turned out that the browser's OPTIONS request, which is made in advance of a GET or POST, didn't include the auth info and so the actual GET or POST was never made due to the OPTIONS request error. However, the first error you show is a CORS error. Hmm....

I have a similar issue, when using the method helpers (axios.get, axios.post etc...) the auth is not getting included. But when constructing the request myself using just axios, it works as expected.
Working, headers get set:
axios({
  // ...
  auth: {
    user: 'user',
    password: 'password',
  },
});

Not working, headers don't get set:
axios.get(url, {
  // ...
  auth: {
    user: 'user',
    password: 'password',
  },
});

Perhaps this is expected behaviour? But it is kind of odd you can't use the helper methods and pass through some authentication.

Ah, I think I saw something about OPTIONS. That was what threw the 401 error I think. So then how do you make the OPTIONS request take the key and secret? I tried setting them as a header but it still wouldn't take it.

I have same issue.

My issue was about OPTIONS request. Now I don't have any workaround to send auth info with OPTIONS request. But I solved the problem by modifying the server (nginx) configuration to disable basic auth only when clients send OPTIONS requests.
My configuration like the following:
location / {
    if ($request_method = OPTIONS ) {
        add_header Access-Control-Allow-Origin *;
        add_header Access-Control-Allow-Methods "POST, GET, OPTIONS";
        add_header Access-Control-Allow-Headers "Origin, Authorization, Accept, Content-Type";
        add_header Access-Control-Allow-Credentials true;
        add_header Content-Length 0;
        add_header Content-Type text/plain;
        return 200;
    }
    auth_basic "Restricted";
    auth_basic_user_file /path/to/passwordfile;
}

Same issue here. OPTIONS gets made a preflight request and the server (which I have no control over) requires auth information and I get a 401. Anyway to make OPTIONS send auth details?

I'm closing as it seems an issue on how the browser handles preflight requests and authorization, not an axios issue.

The W3 specification says that preflight requests should never include credentials.

I just solved this as well by not using axios.post(), instead using axios(). In my case the OPTIONS request was accepted by the server, but the following POST didn't have any headers in it.

Experiencing the above issue with the latest axios version - using the shorthand methods to specific request types results in ignoring the auth parameters and ends with a failed Basic Auth strategy.
I'm using Express + Passport on the server side and Axios within the client.

I get the same issue but has nothing to do with Auth and I get a 403. However if I send the same GET HTTP request just through the chrome browser, it works fine.
Using these headers:
axios({
        method: 'get',
        url: url,
        headers: {
            'Access-Control-Allow-Origin': '*',
            'Access-Control-Allow-Methods': 'GET, POST, PUT, DELETE',
            'Access-Control-Allow-Headers': 'Origin, Content-Type, X-Auth-Token',
            'Content-Type': 'application/json',
            Pragma: 'no-cache',
            'Access-Control-Expose-Headers': 'Access-Token, Uid'
        }
    })

Had same issue - was just fine everywhere but in IE.
Switching to fetch did not help.
Switching to axios() did not help.
Adding site to site lists of 'Local intranet', 'Trusted sites' did not help.
Removing Kerberos/negotiate did not help. ( https://stackoverflow.com/questions/16222946/remove-negotiate-from-windowsauthentication-in-iis )
Issue was, site was not in Intranet zone.
Temorary switching from
'Automatic logon only in Intranet zone'
to
'Automatic logon with current user name and password'
in
'Internet options'-'Security'-'Internet' zone-'Custom level'-'User Authentication'-'Logon'
solved it for me.
Sooo... it was my bad :man_facepalming:

+1

same method, post worked,and get didn't

It has nothing to do with the http client, no matter Axios or others. Server should be configured in a way that it allows non-authenticated OPTIONS requests. Read more.

@sepehr I agree but Axios still provide the withCredentials option.
Some API is not perfect but we still have to deal with, unfortunately.

Sure, we can made a credentialed request to a protected endpoint. However, the thing is that we can’t control browser’s preflight request with Axios or any other http client. @GabrielDelepine

@sepehr preflight request is made by the browser, I understand this point.
But on the current documentation of axios, the option withCredentials pretends to be able to control the behaviour of preflight request.

Currently, on Chrome 70, this withCredentials does not work for me.
At this point, I don't know if it's an Axios issue or a new policy from the newest version of Chrome and Firefox.

In server side try to add this block with your response head
res.header('Access-Control-Allow-Origin', 'http://' + url.parse(req.headers.referer).host)
res.header('Access-Control-Allow-Credentials', true)
res.header('Access-Control-Allow-Methods', 'GET, POST')
res.header('Access-Control-Allow-Headers', 'X-Requested-With,content-type,authorization')

https://github.com/rubennorte -- I think you closed this too quickly.  Postman and jQuery can both send requests that provide the authentication headers, but it seems axios can't manage to do that!
This code (in a Vue.js Vuex store action) fails with a 401 (Unauthorized):
async fetch_stats(context) {             var headers = {'headers': {                 'Content-Type': 'application/json',                  'Authorization': 'Token '+context.getters.token}             };             console.log(headers);             var res = await axios.get(                 "http://localhost:8000/api/fetch-stats/",                 {}, headers             ).then(res => ( console.log(res) )             ).catch(error => console.log(error));             return res;         },
The console.log(headers) produces the following output in the dev console on the browser:
Content-Type:application/json
Authorization:Token d89afca11b46da8747dd0acabc3d1542a63b26e1
meanwhile this Postman request succeeds:
http://localhost:8000/api/fetch-stats/
with Headers(2) (as shown in BulkEdit mode):
Content-Type:application/json
Authorization:Token d89afca11b46da8747dd0acabc3d1542a63b26e1
I have also found that the jQuery ajax call can be made to pass the headers properly, so I would assert that this is a problem with axios...


Implement exonum-java configuration using exonum-cli crate [ECR-3458]

Overview

ListProofIndex integration tests disabled, native module disabled
Used JavaRuntimeProxy stab implementation
getActualConfiguration native part removed, tests disabled
Native integration tests are not working
Anchoring & time services are disabled

See: https://jira.bf.local/browse/ECR-3458
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage decreased (-0.9%) to 84.606% when pulling acc9f27d9e7d6c86b8f30aa4062c29b44980d79f on vitvakatu:parameters into 89768b2eae7b849ceacceb3be2e20dfd62dc2e0e on exonum:dynamic-services.

One of them was missed by me, the other one was just pointing the wrong issue.


Check underscores in Bar plots code

There was a bug when removing underscores for lables, all names where changed in the data and affected other tools like the heatmap.
Now it is fixed


Onboarding QA

[x] can't access results for artists/categories after typing and using (x) or done. We should reload the top lists for artists/categories in this case. https://cl.ly/43150t3w1F1Q https://cl.ly/0C3O301q2V3E

[x] change ipad helper text, input text and additional below field text all to 26px

[ ] use separate 1px link line vs default underline text for links

[x] change all helper text, input text and additional below field text all to 20px

[ ] there's a sizable delay between submitting my name and moving forward to personalization

[x] replace purple spinner with white one https://cl.ly/1s1E3O3J0Q2w

So I've ticked all the ones I could do - two remain:
The underline spacing on the buttons:
I can't control that line, and it's quite difficult to draw a line separately with a pixel distance mid-sentence, if you're not using an underline style. Sorry :(.
The delay between account creation and personalisation:
That is probably because we are indeed creating an account, and hence there's a bit of network activity. I think it's best to keep that work in that specific step, because if any errors surface as a result, we need to display them to the user there and then. Whatcha think?
If you'd like me to make any further changes, please re-open!

@mennenia underline note is helpful thanks. I actually got some feedback that we should try to make the facebook callout stronger than a text link (still needs to be less than the full button we had during testing) I figure something like this might work but getting it done for Thursday may be difficult https://cl.ly/100S3g41071E
On the account creation.

Both should be possible - let me do the analytics and tests first, and then I think I can sort this tonight.

Closed by #2161


Database info files are not distinguished between Smallvars and SVs

Describe the bug
DB info files during the import do not distinguish between smallvars and SVs import. This causes problems downstream in VarFish as it maintains the info for both.
To Reproduce
See ticket in VarFish Server repos (link below).
Expected behavior
Distinguish between smallvars and SVs database info during file guessing, or at least before triggering the import in VarFish Server.
Additional context
Related issue in VarFish Server repository: bihealth/varfish-server#497

RCA
There are some code fragments (out-commented) to distinguish between the two, but it has never been finalized.

Resolution Proposal
Introduce an additional file guesser DB_INFOS_SV. However, it can't be guessed by file content (because it is potentially the same to the non-SV file). This means it needs to be distinguished afterwards by filename. There is a code fragment using Levenshtein distance to do so. This can possibly re-used.
Affected Components
VarFish CLI
Affected Modules/Files

create_case_import.py

Required Architectural Changes
None
Resolution Sketch
As described in Resolution Proposal.


Type definitions and tests for pascal-case

https://github.com/blakeembrey/pascal-case
https://www.npmjs.com/package/pascal-case

@stpettersens Thanks mate!


Readiness probe failed: calico/node is not ready: BIRD is not ready: BGP not established with xx.xx.xx.xx

Issue Summary
Calico Version - node:v3.3.2, K8s Version 1.17
Calico Daemsets pods are not running and gives the below error Readiness probe failed: calico/node is not ready: BIRD is not ready: BGP not established with xx.xx.xx.xx
calico-node-xjk                            1/2     Running   0
calico-node-xnx                            1/2     Running   0
calico-node-xq9                           1/2     Running   0
calico-node-xrp                            1/2     Running
calicoctl node status
Calico process is running.
IPv4 BGP status
+---------------+-------------------+-------+------------+--------------------------------+
| PEER ADDRESS  |     PEER TYPE     | STATE |   SINCE    |              INFO              |
+---------------+-------------------+-------+------------+--------------------------------+
| 10.xx.xx.xx | node-to-node mesh | start | 16:43:32   | Active Socket: Host is         |
|               |                   |       |            | unreachable                    |
| | 10.xx.xx.xx  | node-to-node mesh | start | 2022-07-14 | Active Socket: Host is         |
|               |                   |       |            | unreachable
Steps to Reproduce (for bugs)

All the calico pods are throwing the error and not able to run and kube-controller pod shows the below error

2022-07-26 04:14:19.096 [ERROR][1] node_controller.go 174: Error deleting Calico node: node-01%!(EXTRA *errors.errorString=The requested CIDR (10.xx.xx.xx/26) is not within any configured pools.) error=The requested CIDR (10.xx.xx.xx/26) is not within any configured pools.
2022-07-26 04:30:59.540 [ERROR][1] ipam.go 930: Failed to release IPAM affinities for host error=The requested CIDR (10.xx.xx.xx/26) is not within any configured pools. host="node-01"
Your Environment

Calico version -- quay.io/calico/node:v3.3.2
Orchestrator version (e.g. kubernetes, mesos, rkt):
Operating System and version:
Link to your project (optional):

Calico version -- quay.io/calico/node:v3.3.2

Please try again using a modern Calico and Kubernetes version. v3.3.2 is long since out of support. The latest is v3.23, which requires Kubernetes v1.21+


OSSL_PARAM_BLD and BIGNUM; ensure at least one byte is allocated

A zero BIGNUM contains zero bytes, while OSSL_PARAMs with an INTEGER (or
UNSIGNED INTEGER) data type are expected to have at least one data byte
allocated, containing a zero.  This wasn't handled correctly.
Fixes #20011

@levitte is your understanding here that the BN_new() case is also broken.. i.e. it points to a block for this case, but the next parameter would then reuse this location? The BN_secure case just shows an additional problem of using NULL

Would other functions that potentially pass an alloc of zero to param_push() also be a problem
(such as OSSL_PARAM_BLD_push_octet_string() ?)

@levitte is your understanding here that the BN_new() case is also broken.. i.e. it points to a block for this case, but the next parameter would then reuse this location? The BN_secure case just shows an additional problem of using NULL (if there is one param)..

The problem seems to be most visible with BN_secure, but that shouldn't matter...  a zero shouldn't become 0 bytes of OSSL_PARAM data, for any C number type

I can confirm that the fix in https://github.com/openssl/openssl/pull/20013/commits/716cb7931bf6ab3f9f984a9187dd7fe74bf9d4ff does fix the problem.
I wonder if the OSSL_PARAM_get_XXX functions should also be made save about invalid OSSL_PARAMs being passed to it. A bogus application could pass invalid OSSL_PARAMs to providers (e.g. via EVP_PKEY_fromdata() ). I guess the OSSL_PARAM_get_XXX functions should not cause any troubles (like address sanitizer findings) if an invalid param is passed to it. I guess passing a OSSL_PARAM to a getter function with data = NULL and/or data_size = 0 does not make any sense no matter what, and should lead to an error return and add an error to the error stack.

I guess passing a OSSL_PARAM to a getter function with data = NULL and/or data_size = 0 does not make any sense no matter what, and should lead to an error return and add an error to the error stack.

Not quite right.  You can do that to query what the minimum data_size should be for a particular OSSL_PARAM key.  This is documented:
https://github.com/openssl/openssl/blob/4b65d79d7132d6e46bfb385a76082f6502ef617b/doc/man3/OSSL_PARAM.pod?plain=1#L113-L116

Not quite right. You can do that to query what the minimum data_size should be for a particular OSSL_PARAM key. This is documented:

I know that. I did not say that an OSSL_PARAM can never have data = NULL. What I am saying is that when using with the OSSL_PARAM_get_XXX() functions it can not have data = NULL or data_size = 0. So the OSSL_PARAM_get_XXX() functions should check for that and produce an error return if so.

Gah!  For once, I mixed up get and set.  Right you are...

I added a couple of more commits that have the numeric OSSL_PARAM_get_XXX() check that the data field is non-NULL and that the data_size field is non-zero, and also to have OSSL_PARAM_set_BN() ensure that there will be at least one byte of data.

I added a couple of more commits that have the numeric OSSL_PARAM_get_XXX() check that the data field is non-NULL and that the data_size field is non-zero.

Don't you also need to add the check to general_get_int() and general_get_uint()? They are called by the OSSL_PARAM_get_XXX() functions if the size is not as expected.
Within general_get_[u]int() functions [un]signed_from_[un]signed() are called and there the is_negative() function is called on the src which is p->data and p->data_size which can be NULL. This would produce a segfault as far as I can tell.

I added a couple of more commits that have the numeric OSSL_PARAM_get_XXX() check that the data field is non-NULL and that the data_size field is non-zero.

Don't you also need to add the check to general_get_int() and general_get_uint()? They are called by the OSSL_PARAM_get_XXX() functions if the size is not as expected.

I don't understand...  if we have the checks early in OSSL_PARAM_get_XXX(), why would I have to reproduce the same checks in general_get_int() and general_get_uint()?

I added a couple of more commits that have the numeric OSSL_PARAM_get_XXX() check that the data field is non-NULL and that the data_size field is non-zero.

Don't you also need to add the check to general_get_int() and general_get_uint()? They are called by the OSSL_PARAM_get_XXX() functions if the size is not as expected.

I don't understand... if we have the checks early in OSSL_PARAM_get_XXX(), why would I have to reproduce the same checks in general_get_int() and general_get_uint()?

You added the check to OSSL_PARAM_get_int32() etc, but not to OSSL_PARAM_get_int() etc. Within OSSL_PARAM_get_int() it calls general_get_int(). So no check before it reaches general_get_int().
This applies to OSSL_PARAM_get_int(), OSSL_PARAM_get_long(), OSSL_PARAM_get_time_t(), OSSL_PARAM_get_uint(), OSSL_PARAM_get_size_t(), OSSL_PARAM_get_ulong().

The "Provider old versions compat / fips-provider-validation" CI fails...  it appears that the added checks in OSSL_PARAM_get_XXX() may break any provider that happens to set data = NULL and data_size = 0 for a zero BN.
That's not promising.  We may have to forego that part of this PR, sadly enough.

This pull request is ready to merge

Merged
master:
b49cf273883c8d3f47542941fe5cc6cb51aec9c9 test/param_build_test.c: test zero BIGNUM
c2ae89148343750e420b72ef1b709ebbc16e47b8 In OSSL_PARAM_set_BN(), make sure that the data_size field is at least 1
c455f87aebf245814ba58d6a398b45ca4e80d1d7 OSSL_PARAM_BLD and BIGNUM; ensure at least one byte is allocated
3.1:
2b7b7eebf9b7d01f8abab88b9ae0685f33c74b54 test/param_build_test.c: test zero BIGNUM
fcc224a3c5c868ee4c0f5ab71d2f47e7f620bc98 In OSSL_PARAM_set_BN(), make sure that the data_size field is at least 1
e33c37aead7e7dd5647d949db7be875c8fa8c137 OSSL_PARAM_BLD and BIGNUM; ensure at least one byte is allocated
3.0:
5601648e91d99696bc7ae37e8972c5b4b15cf832 test/param_build_test.c: test zero BIGNUM
f51b4ebb07948d942cd6536fe48e325655349d97 In OSSL_PARAM_set_BN(), make sure that the data_size field is at least 1
1932e595c8061bcb8d2718eaf5fdb6038bdec631 OSSL_PARAM_BLD and BIGNUM; ensure at least one byte is allocated


link to example not working

The link to the example flow is not working.

Thank you very much for the report and PR.


Setup Travis CI for this repo

Everything in this repo must be tested, Travis CI should be running rspec on all PRs.
If possible, it would be cool if Travis could build and release a new gem version when PRs are merged into master.
@meatherly interested?

Done, the release branch is automatically deployed to Rubygems


Update google-cloud-storage to 2.36.0

About this PR
📦 Updates com.google.cloud:google-cloud-storage from 2.32.1 to 2.36.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-storage" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-storage" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #1062.


mui imports don't work in /lib - esm compatability?

https://stackoverflow.com/questions/74552589/esm-default-named-import-in-mui-without-having-to-manually-write-default


[Question] How to access the user id

Hello,
the user_id is not set when i refresh the website because store is not ready yet.
Any idea how to fetch the user_id once store is filled?
I searched in the docs but couldn't find anything that can help me with this problem.
        async created() {

            await this.$store.dispatch('')

            const {Todo, User} = this.$FeathersVuex.api
            const user_id = this.$store.state.auth.user.id

            const {data} = await Todo.find({
                query: {
                    user_id,
                    $limit: 40
                }
            })
        }

Thanks in advance!

You must call the authenticate action before your app startup in order to authenticate with the JWT stored in localstorage.
Then the user will be available.


What ProjectType is used for an ItemTemplate you want at the solution level?

Visual Studio 2017
I created an Item Template for Visual Studio. You can get the code at GitHub.
When installing the template or running the solution locally, the template only shows up in the Add New Item dialog for a C# project.
I want it to be in the Add New Item dialog for the solution.
It seems to me the problem is having the ProjectType set to CSharp in the .vstemplate file, but I don't know what to set it to. According to the docs the options are only CSharp, VisualBasic, and Web.

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

ID: cca18c9f-45b4-0a7b-6ce8-d6c88d507dc4
Version Independent ID: 8030dd04-f507-46bc-2e85-c03568984312
Content: ProjectType Element (Visual Studio Templates) - Visual Studio
Content Source: docs/extensibility/projecttype-element-visual-studio-templates.md
Product: visual-studio-dev15
GitHub Login: @gregvanl
Microsoft Alias: gregvanl

After talking to Mads Kristensen, Visual Studio, and Stack Overflow, this is not possible using an Item Template project.
If you want to see your custom item when adding a new item to a solution using Visual Studio, you must add your custom file to C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\NewFileItems


Tab completion behavior for click.File and click.Path types

Lets say this is related to #241 ...
Recently support was added to have argument autocompletion, custom completion functions/lists and a special case for click.Choice options too.
This is great ! I would like to see better support for filenames and directories, have been looking at the code and wanted to share my thoughts here... as far as I can see the problems with filename/directory are multiple but hopefully addressed with a couple of simple patches.
Undesirable Autocompletion of paths
In the case that the user is completing an option which takes one or more arguments, and those arguments cannot be completed (i.e. they are just a string or integer type), then the builtin completion mechanism correctly reports no results, however the bash completion glue (here) specifies "-o default"
This parameter to the bash complete function tells bash to default to completing paths when the resulting COMPREPLY array is empty, and the side effect is undesirable filenames being completed.
Filenames reported for directory arguments
Because click does not do anything for filenames or directories itself, it instead falls back on the undesirable complete -o default behavior mentioned above for filenames and all arguments which did not supply any custom autocompletion list or function.
This means that filenames are suggested when the argument is in fact a directory, and also directory names are suggested for filenames.
Filename and directory completion has different behavior
The default shell behavior is to take the reported list in COMPREPLY, and if there is only one element, it will append a space and the next TAB is ready to complete the next token, but this is not the desired behavior when completing paths, where you want to complete only one directory at a time.
This can be addressed however by using the "complete -o nospace ..." option, which will just cause the shell to not append any space for a single available completion, allowing the program to continue completing the last completion on the next iteration.
In this case, click can:

Append a space to the reported completion in the case that only one completion was available
Append a slash (if none is already there), in the case that the completion is a directory name

Proposed Approach
Instead of handling click.Choice explicitly in _bashcompletion.py, we should instead have the base ParamType cooperate in the process of completion, so that paths and filenames can have an opportunity to decide if the parameter is entirely complete or could be completed further (i.e. whether a space should be appended to the reported completion, or whether it should remain, as in the case for a filename which is a directory that could be completed further).
click.Choice would implement completions by overriding an abstract method of click.ParamType, click.BOOL could also implement this, because why not.
The new autocompletion attribute would be checked before ever consulting the click.ParamType abstract method, so the user can always override the default completions for any parameter.
Also, we should change the completion script to not use "-o default" and use "-o nospace" instead, ensuring that filenames dont show up by default.
Finally, the click.Path and click.File need to do the work we were previously offloading to the shell, this is the most tricky (or "meaty") part of the patch I guess, hopefully a python implementation using os.listdir() and file concatenation would not slow down the completion process too much.

So I'm personally quite satisfied with #782 as a solution for this, sorry at first I missed the test cases and came back to adjust the existing ones and add some additional test cases for Path types.
One thing I'm not sure of is if I'm entirely satisfied with the API surface, although it does work.
In order to deal with completion of tree like data, we have two types of completion result; those with trailing spaces and those without. For the bash facing results in COMPREPLY, this must remain the case for reasons explained in the report above. However for the developer facing APIs of ParamType implementations and the autocompletion attribute now available in the decorators, this might not be the most comfortable.
The options I could see for this are:

Let the implementors append a space for completely completed suggestions, and returning strings that lack a trailing space is an indicator that this completion could be completed further (that is the current approach)
Have the completion functions (ParamType->completions() and autocompletion callbacks) return a tuple of two lists instead of one

With the second approach, we would append spaces to completely completed suggestions automatically inside _bashcompletion.py and have the implementors report results without the appended spaces, which may be a more comfortable API.
Also, I agree with comments in #428 that autocompletion could be named better, either suggests or completions would be nicer words for this, but that is a separate issue.
Would love to hear feedback from the click maintainership on this patch series :)

Adding @untitaker on cc...

I'm rather against removing -o default. It appears to be convention to allow filenames when the custom completion doesn't work, at least with git it does.

This can be addressed however by using the "complete -o nospace ..." option, which will just cause the shell to not append any space for a single available completion, allowing the program to continue completing the last completion on the next iteration.

This appears to be inacceptable to me, since it affects completion of e.g. subcommands as well. I'd rather accept that files and directories are mixed up in the completion.
If one were to implement custom completion for directories, that would mean one would have to recursively traverse and output all directories to avoid appending the space in the case of only one top-level directory name matching. That is slow.

I'm rather against removing -o default. It appears to be convention to allow
filenames when the custom completion doesn't work, at least with git it does.

For what it's worth, git is not a great example. However the effort various applications have made vary quite widely, a lot of coreutils and standard gnu tools never complete option names for instance. Here are some comparisons:
# -f is a file argument, completes directories and filenames
$ make -f <TAB>
dira/ dirb/ file1 file2

# -C/--directory is directory option, completes only directories
$ make -C <TAB>
dira/ dirb/

# tar's -C option is not as smart
$ tar -C <TAB>
dira/ dirb/ file1 file2

# tar's --file option is however smart, it will only complete filenames
# of the expected filename extensions, it will even take the expected
# compression algorithm into account if it was specified
$ tar -f <TAB>
tarball.tar tarball.tgz tarball.tar.bz2

$ tar -zxf <TAB>
tarball.tgz

# tar at least does not complete filenames when a string is expected
$ tar --quote-chars <TAB>
(no completeions here)

# git's -C is like make's directory, but it fails to complete a directory
# and goes on to complete subcommands
git -C <TAB>

This appears to be inacceptable to me, since it affects completion of e.g. subcommands
as well. I'd rather accept that files and directories are mixed up in the completion.

Behavior of subcommand and option name completion still works exactly as expected, in fact the user experience for this is unchanged. Note the test case is changed to expect the trailing spaces which are needed to report to the shell, but that is just the internal get_choices() api.

If one were to implement custom completion for directories, that would mean one would have to
recursively traverse and output all directories to avoid appending the space in the case of only one
top-level directory name matching. That is slow.

In fact, without -o nospace your statement is true; with the current API it is impossible to efficiently implement custom completion of any large tree/path like data sets.
Note that this is implemented in #782, what you do is not append a space to complete one directory at a time, in the next iteration the incomplete text contains to so far completed text.
Currently, if you want to do completions in iteration on any tree/path like dataset, either:

You list one component, and bash appends a space, so all bets are off for the next iteration, you are already completing the next argument
You list every branch/leaf node recursively, which will
Be slow, as you mentioned
Have an unfriendly experience, bash will ask you if you really want to display all 11894 possibilities in the shell, for example

+1 for having a way to customize argument expansion in particular. In the popular git multi command example, completing e.g. branches to checkout is very helpful, but you wouldn't want to add pseudo-subcommands for each and every one of them. Just having API to extend completion would be great!

I also experienced the same issue. main() is never called, so the context is not properly populated, and you can't reuse the shared state for the autocomplete.
In my case, main() has db connection settings. Defines a DB object in the context, and commands can use the db directly. But the autocomplete now doesn't have access to the DB without the proper context.

What is status of this, is open for 2 years, anything blocking this from being merged? (#782)

No news about this issue?

This is not exactly solving this issue, but can take you a long way and hasn't been mentioned on this thread: check out https://github.com/click-contrib/click-completion

Could I confirm that file completions aren't expected to work at all on master?
I'm not able to get any file or directory completions working. When I monkey patch something like #1403, it does work.

@max-sixty Work is being done on https://github.com/pallets/click/pull/1622 that should change that soon. The docs talk a bit more about completion support https://click.palletsprojects.com/en/7.x/bashcomplete/#what-it-completes

Thanks @kx-chen ! That looks very encouraging!

Will this merge https://github.com/click-contrib/click-completion then?

The new design is discussed in #1484. click-completion will not be merged, and may not be compatible with the new system at first. The new system will be much more extensible though, so click-completion or other extensions can add to it more easily.

Hi, I was looking into a related potential issue, that seems related to this one, so I thought I'd ask about it here vs create a new issue (tho lmk if I should create a separate one).
I am using zsh on mac:
fpath=($HOME/.zsh/completion $HOME/.zsh/zsh-completions $fpath)
autoload -Uz compinit
compinit -i
export PATH="$PATH:$HOME/src/sq"
eval "$(_SQ_COMPLETE=source_zsh sq)"

I have a click python file, sq and am trying to get autocompletion working for filepaths:
@dev.command(help="Touch file")
@click.argument("input_filename", type=click.Path(exists=True))
def touch(input_filename):
    _run_command(f"touch {input_filename}")

sq d[tab] → sq dev
sq dev t[tab] → sq dev touch
sq dev touch t[tab] → NOTHING (even if test.txt exists on filesystem)

I would expect this last case to complete to test.txt, especially since i used click.Path for the argument type, esp given this comment in the thread above:

In the case that the user is completing an option which takes one or more arguments, and those arguments cannot be completed (i.e. they are just a string or integer type), then the builtin completion mechanism correctly reports no results, however the bash completion glue (here) specifies "-o default"

Is the behavior I am seeing expected, or do I need to do something special to get file path completions? Is this related to #1622 or user error on my part w the current version of click?

@kortina file/path completion currently does not work, but #1622 addresses it

@davidism are you planning to release a new Click version that includes this feature?

I have looked through the changes in #1622 and think this is a huge improvement!
Something which I am a bit unclear about -- not sure if this is the right place to ask: The OP discussed not only issues with completing files / directories from the local file system but also completing custom tree-like data.
As far as I can see, this is still difficult with the new shell completion system. Directory or file completion can be requested by setting the CompletionItem type to "dir" or "file" but this seems to result in completion being entirely handled by shell based on the current file system. Alternatively, if completion is handled manually, the issue with a trailing space appended to the competed string still exists.
Is it possible to implement ParamType.shell_complete in a way which allows completion of custom tree? In my use case, I would like to implement completion for paths from a virtual or remote file system.

The problem you describe is not generally solvable (at least in a way that seems at all maintainable). If you need to customize at that level and the existing facilities don't provide that for you, you'll need to register a new shell completion script that does what you want for your case.

Ok, that's what I was afraid of :/ At least with the rewrite it is a lot easier to extend the existing completion system.


rawtherapee-git: outdated, can it be removed?

Issue description
rawtherapee-git hasn't received an update in well above a year since it has been introduced. The stable version rawtherapee has received multiple updates in the same timeframe - and ships are more recent version.
Additionally the current -git version which is marked as dev is breaking on newer gcc versions. (see #31747)
So I am asking the maintainers (@viric @jcumming @2chilled @the-kenny) (or anyone else with "authority"):

Can the -git version can be removed?
Or: Will it receive updates?

👍 for removing it.


Add sidebar module

@LITUATUI FYI, now the optional sidebar modules were implemented. You can the preview it and find the source code on HB starter theme.


Won't compile intel icpc

The only issue now seems to be in the 3D fit, where it is very unhappy with the eigen tensors.


⚠ Bofrost.at has degraded performance

In 52f28f1, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 824 ms

Resolved: Bofrost.at performance has improved in bbef1fa after 6 minutes.


Add libsass support

There are a few minor things that prevent me from building the framework right now. I've made some changes in my libsass-compatibility branch that permit me to build the framework, but they haven't been tested really extensively and I'm new to material-ui so I'm probably not the person to do that.
As you can see from the diff, libsass appears to choke on the ripple transition effects. So I've split them up, one for the keyframes and one for the animation value.
I've not made a pull request yet because I'd like to get some feedback on my changes first, since I'm not 100% sure about then.
I've been able to build this using node-sass 1.2.3 which uses libsass 3.1.0.

Thanks @msikma for pointing out this.
I'm also not happy with ruby-sass, yet it was the choice of the original project so I kept it. I'd love to skip the gulp tasks and just use webpack (which is a good reason for me to switch to node-sass).
If I read the diff well, the problem is nesting transitions mixins into selectors. Your change should be compatible with ruby-sass as well (i believe it's just a matter of code readability), but I'd like to give a try first. Did you try to see if it works with the docs project and gulp?

If I read the diff well, the problem is nesting transitions mixins into selectors.

Yeah, I did some tests in Sassmeister. If you put this SCSS in Sassmeister and switch between different engines, you can see that the output changes. Ruby Sass has different output than Libsass, it actually automatically takes the @keyframes declaration out of the a selector.
I fixed this not because Libsass complained about not being able to compile it, but because the compiled CSS wasn't being accepted as valid by Webpack's CSS loader :)

Did you try to see if it works with the docs project and gulp?

Haven't done it just yet because I did this real quickly as I was going out, but I'll see if I can do it tomorrow or possibly tonight.

Well AFAIK keyframes shouldn't stay inside selectors, so here ruby-sass is too permissive... now I understand better, thanks!! I'm sure the change wouldn't affect people using ruby-sass. You don't need to check that for me, just send the PR ;-)
I hope we will get rid of those preprocessors soon...!

I've made the PR :)

The v0.7.1 now uses lib-sass. thanks @msikma !


How can i remove all entered text using coding?

If you are using UIKit version, just call the clearOTP() method.
otpTextField.clearOTP()

And if you are using the SwiftUI version, you have to set the enableClearOTP property to True, and just set the OTP text to be empty.
AEOTPView(text: $otp, enableClearOTP: true)

Button(action: {
                otp = ""
            }, label: {
                Text("Clear OTP")
            })


Cannot verify Polygon Amoy contract

Issue:
When I try to verify Polygon Amoy contract (NFT Drop) via the dashboard I get "Internal Server Error".
Response:
{"error":"Verification failed: internal error"}
Steps to recreate:

Create NFT Drop contract on Polygon Amoy testnet
Go to Contract > Sources
Initiate verification by pressing the "Verify contract" button

please reach out via https://support.thirdweb.com


List snapshots using snapshotter option incorrect usage

Description
I want to list all snapshots in the current address using the --snapshotter option.
Steps to reproduce the issue:
sudo ctr --address /run/firecracker-containerd/containerd.sock snapshots list --snapshotter=firecracker-naive
Describe the results you received:
Incorrect Usage: flag provided but not defined: -snapshotter

NAME:
   ctr snapshots list - list snapshots

USAGE:
   ctr snapshots list [arguments...]
ctr: flag provided but not defined: -snapshotter

Describe the results you expected:
List of snapshots, including info KEY PARENT KIND
Output of containerd --version:
containerd github.com/containerd/containerd 1.2.0+unknown

Any other relevant information:
Using firecracker-containerd

I think --snapshotter flag should be between snapshots and list
Like this:
sudo ctr --address /run/firecracker-containerd/containerd.sock snapshots --snapshotter=firecracker-naive list

thanks, working 👍


Need scripts to download all blobs for fissile?

Hello,
There no src for most of the packages dependency for jobs, does it mean I need to create a separate scripts to download all blobs for the packages when I want to use fissile to renter the release to docker images?
Thanks and Regards.
HAO

@haohaoyingxin For fissile you can use "export FISSILE_RELEASE=xxx" to specify the release path.

@qibobo Thanks for prompt reply qibobo. Probably I did't explain me clearly, the questions is:
I found a scripts to check and download dependency blobs in the old open-Autoscaler repository, but no such scripts in this one. In this new repo, the spec of each packages is just files location, but no link. Should I create a similar scripts to check and downloads those blobs from Internet?

@haohaoyingxin You needn't. In the root of app-autoscaler-release, "bosh create-release" will automatically download all the blobs and dependencies. Then you can add app-autoscaler-release to fissile by "export FISSILE_RELEASE", then all should work. By the way, app-autoscaler-release has been added to scf https://github.com/SUSE/scf.

@qibobo Thanks a lot! One more question,  I saw one postgres-release submodule added in scf, how do you make autoscaler integrate with it?

@haohaoyingxin  we consume its postgres release: https://github.com/SUSE/scf/blob/9d8ce928851b92c22c43961ac66a225cc0a19c46/container-host-files/etc/scf/config/role-manifest.yml#L1354

@qibobo hi, I saw one job named  pruner included in instance-group: autoscaler-actors in the role-manifest.yml of suse/scf repo. But there is no such job in app-autoscaler, does it refer to job operator?

@haohaoyingxin The pruner has been renamed to operator in the latest version of app-autoscaler.

@qibobo Thanks! Ticket can be closed.


Support for Maps

Can support be added for ES2015 Map data structures? Converting it to and from json does not correctly convert Maps.

Hi @Tjorriemorrie
Map support is not planned. When you JSON.stringify a map object you get a simple object, and something similar happens when you add it to a freezer store, all the functions get stripped off.

I thought as much. What about passing a possible second argument when the freezer is created from an json object? And that argument is the schema of field types to parse it to?

Trying to parse class instances inside freezer would have a really big downside: those object could be mutated without triggering events.
For example, the Map class has all the getter and setter methods that modify its internal state. Even when you freeze it you are able to use that methods to update it:
var m = new Map(); // Map {}
Object.freeze( m ); // The map should be freezer
m.set('a', 1);
console.log( m ) // Map {"a" => 1} we have just updated the frozen map :(

This way, the use of freezer lose the point.

Thank you for the detailed explanation.


[CT-3459] [Feature] Add cleanup methods to various base tests in core that are known to create leftover schemas from ci/cd in adapters

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Going to clear out our test account used for dbt-redshift see that several tests defined in dbt-core are leaving hanging artifacts at a rate suggesting their not properly being dropped see: https://github.com/dbt-labs/dbt-redshift/issues/675
Describe alternatives you've considered
We can go look at the tests and evaluate what part of the default schema Is being changed and create cleanup methods to drop that changed schema. then install the connecting pr branch to this issue into local adapter runs and run tests locally to make sure the caught tests are not leaving any more schemas and try to catch follow-up ones that may not be nuisance artifacts
Who will this benefit?
our testing alerts can hopefully start to be more clean and pointing to real failures and stem flow of slowly filling up our ci/cd databases till no tests are allowed to pass
Are you interested in contributing this feature?
yes
Anything else?
No response

@McKnight-42 Should we verify this is working somehow (hence re-open until verified)? Or are you comfortable with this as-is given that it only impacts tests (hence move to Done status)?


[instancer] STAT: ElidedFallbackNameID is removed from 'name' table

When creating a static instance from a VF that has an ElidedFallbackNameID in the STAT table, the name record referred to by ElidedFallbackNameID is deleted, but the field is not cleared.
I'm not sure what the fix should be:

don't delete the name table entry
clear the ElidedFallbackNameID field

who deletes that name table entry? I can't find the code that's responsible for that

Good question, I'll try to find out.

I'm not entirely sure what the fix should be either. What are the implications of 1) or 2)

Hm, I don't think that's the culprit.
I'm investigating further, there's something odd going on in our VF, where nameID 2 == "Regular", yet "ElidedFallbackNameID" is 382, and nameID 382 is also "Regular". But nameID 2 only exists as (3, 1), and 382 was added as (1, 0) and (3, 1). It's 382 that gets zapped somehow.

Oh! I think it's the pruningUnusedNames context manager defined in instancer.names module, which wraps calls to instantiateSTAT. The method calls getVariationNameIDs (also defined in instancer.names module) but for STAT table it does not also considers that ElidedFallbackNameID can "use" a name ID. So it assumes it's unused and later it will be dropped on exit.

assuming we want to retain that ElidedFallbackNameID, then you should add it to the set of used nameIDs as returned from getVariationNameIDs.
Do we want to retain that? When does it make sense to drop it?

in any case, the pruningUnunsedNames logic should be amended to take into account that the ElidedFallbackNameID may in fact be still used and not drop it accordingly. The instantiateSTAT method can decide when is appropriate to unset that ElidedFallbackNameID

I'm working on a fix in getVariationNameIDs, I just need to check whether stat.ElidedFallbackNameID is None or missing in version 1.0 STAT tables.

probably just missing


update pulumi branding on github app docs page

File: themes/default/content/docs/guides/continuous-delivery/github-app.md
a few of the screenshots need updating with the new logo, we should also remove the see below link.
also, check with @gthuang if this is the correct marketing content..

🤔 i do not remember writing this, but there was another issue that fixed this recently as part of the deploy launch, so closing.

oh lol this is in hugo


Acquire domain knowledge from meta-papers on preprints

[x] bioRxiv: the preprint server for biology
[x] Preprinting the COVID-19 pandemic
[x] On the origin of nonequivalent states: How we can talk about preprints
[ ] A multi-disciplinary perspective on emergent and future innovations in peer review
[x] Credibility of preprints: an interdisciplinary survey of researchers

Collected in https://docs.google.com/presentation/d/1Zu-yjfoTg1brTXtfM-V6V-aTx0hdrwQatrRp-I33p0A/edit?usp=sharing

Collected in https://docs.google.com/presentation/d/1Zu-yjfoTg1brTXtfM-V6V-aTx0hdrwQatrRp-I33p0A/edit?usp=sharing


Bug fix filled by error

Description
in order to make it so the requests says who it is filled by I had to update the tables filled_by variable as we could never get the user which is how it was set up initially. Now the full name field from the html is set to the filled by and that name is shown on the request

This is related or unrelated?


Clarification on KV usage

Heya, i'm getting the following error when trying to use KV in Cloudflare workers. I took a look at the example blog project which uses them. Seems like the below should be working?
export const auth = new Hono()
auth.get('/login', async(c) => {
    await c.env.OAUTH_STATES.put(state, code_verifier, {expirationTtl: 600})
}

However, i get the following error:
TypeError: Cannot read properties of undefined (reading 'OAUTH_STATES')

My wrangler.toml:
name = "api-dev"
main = "src/index.ts"
compatibility_date = "2022-06-25"
workers_dev = true
node_compat = true
kv_namespaces = [
    { binding = "OAUTH_STATES", preview_id = "<ID>", id = "<ID>" }
]

vars = { ENVIRONMENT = "dev" }

[env.production]
name = "api"
vars = { ENVIRONMENT = "production" }

[env.staging]
name = "api-staging"
vars = { ENVIRONMENT = "staging" }

Cheers!

Hi @byt3bl33d3r !
Are you using app.fire() at the last line?
const app = new Hono()
//...
app.fire() // <---

app.fire() is for Service Workers mode. On the other hand, c.env.KV_NAME is available only in Module Workers mode. To enable it, write export default app instead of app.fire().
const app = new Hono()
//...
export default app // <---

Will this fix it?

Completely missed this. Thank you and sorry for the trouble.


stage1: set TimeoutStartSec to 0

Some pre-start jobs take a long time, set the timeout to 0 so they can
complete. If it takes too long, the user can just kill rkt.
Fixes #1515

LGTM, we may want to expose this in future but it's more predictable default behaviour for now.


WIP: test for sharing PV across domains

This test is to create 2 domains that share the same PV. Both domains are  managed by single operator  Verify

scaling for domain2 cluster from 2 to 3 servers and back to 2, plus verify no impact on domain1
cycle domain1 down and back up, plus verify no impact on domain2

Internal Jenkins passed at: http://wls-jenkins.us.oracle.com/view/weblogic-operator/job/weblogic-kubernetes-operator-javatest/1839/
external Jenkins passed at: http://build.weblogick8s.org:8080/job/weblogic-kubernetes-operator-quicktest/408/

Does shared PV work if two domains managed by two operators? If so, can the existing test testTwoDomainsManagedByTwoOperators be modified for this usecase instead of bringing up two new domains?

In order to share one PV 2 domains need to in the same namespace.

is this even a supported use case?

Do we not support two domain homes in the same  PV but in two different directories?  I would think yes.

is this even a supported use case?

I think the answer is yes.  You could two domain homes persisted to the same PV but in separate Domain Homes because the names are unique.

@maggiehe00 how about the weblogicDomainStoragePath, isn't that same for both domains when they share PV?

PV's are globally scoped, but PVC's are per-namespace.  We would have to experiment to see if it's possible to have a shared PV with different PVC's in the different namespaces.  It's likely possible and it makes sense if the volume is accessed over NFS and the domains are kept in separate directory structures.

@rjeberhard, right now the PVCs of both domains are in the same namespace. I'm going to modify the tests to put them in the different PVC and give it a try.

@rjeberhard, i tried a couple of things. These are my findings.

under our current sample PV/PVC creation template

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: %DOMAIN_UID%%SEPARATOR%%BASE_NAME%-pvc
apiVersion: v1
kind: PersistentVolume
metadata:
name: %DOMAIN_UID%%SEPARATOR%%BASE_NAME%-pv
So if PV name is same, PVC name must be same also, given for sharing PV, we have to leave domain uid empty.
2) I tried same PV/PVC name for 2 domains(namespace: default) but 2nd PVC in the different namespace(d2pvc). Both domains are created and tests passed but in fact the PVC that in the namespace d2pvc didn't bound to PV. 2 domains use the same PV/PVC.
ash-4.2$ kubectl get pv
NAME                 CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                         STORAGECLASS                    REASON   AGE
weblogic-shaing-pv   10Gi       RWX            Retain           Bound    default/weblogic-shaing-pvc   weblogic-shaing-storage-class            57m
I think this is because in the domain creation input file there is no option to specify the namespace of PVC.
Please let me know how you think about it. Thanks!

@vanajamukkara, @npanigr, @rjeberhard I hope this PR can be merged soon so that I can use it to test the fix for Bug29967859:PV/PVC CREATION LOGIC CAN'T PRECISELY DETECT IF PV/PVC EXISTS OR NOT


what is the correct keywords for mouse_modifier?

environment:
macOS 13.7.1 22H221 x86_64
yabai-v7.1.5
Poker keyboard with USB

This config not work on my computer. So is it a configuration conflict? Why?
yabai -m config mouse_modifier               fn
yabai -m config mouse_action1                move
yabai -m config mouse_action2                resize

I can changed it to shift and it worked. But how to change it to anohter key like Command or Control?
It always said unknown value 'control' given to command 'mouse_modifier' for domain 'config' So, what is the correct keywords？
And another problem.
One of the rules in the config file is yabai -m rule --add app="^Telegram$" manage=off  did not work unless execute yabai -m rule --apply in terminal. I already have yabai -m rule --apply in config file.

I am aware of these possible values for the mouse_modifier config:
ctrl, alt, cmd, shift, fn

I am aware of these possible values for the mouse_modifier config:
ctrl, alt, cmd, shift, fn

Thank you! I'll try.


Fix link error

What type of PR is this?

[ ] bug
[ ] feature
[x] enhancement

What problem(s) does this PR solve?
Issue(s) number:
Description:
The previous link is 404 not found.
How do you solve it?
Change the link.
Special notes for your reviewer, ex. impact of this fix, design document, etc:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you very much for your contribution.


Cross data source entity references

There should be possible to reference entities in other data sources

[ ] new attribute in root of documents __id__: dataSource/uuid
[ ] implement a "Reference" type used in references

{
    "_ref_": "datasource/123-34543-56756",
    "refType": "dmss://system/SIMOS/Package",
    "type": "CORE:Reference"
  }

This must be coordinated with
https://github.com/equinor/data-modelling-storage-service/issues/381

bump

Pretty sure this is fixed with the new Address system @eoaksnes


[SPARK-8908] [SQL] Add () to distinct definition in dataframe

Adding () to the definition of distinct in DataFrame allows distinct to be called with parentheses, which is consistent with dropDuplicates.

Merged build triggered.

Merged build started.

Test build #36830 has started for   PR 7298 at commit 7f0d923.

Should we change the definition of distinct in RDDApi?

/cc @marmbrus

We should just remove RDDApi ....

Test build #36830 has finished for   PR 7298 at commit 7f0d923.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Thanks - merging this.


Release to pypi

Hi all,
what an awesome library! Would it be possible to create a release, e.g. on pypi? That would be great for reproducible research. It enables people to run and compare specific versions of the code.
Thanks!
Best,
Robert

@haesleinhuepf, my bad. I tagged this commit and uploaded it to pypi.
Thanks for pointing this out.

Awesome thanks 🎉


Maven tests fail to compile out-of-the-box

Following steps here - https://github.com/Microsoft/botbuilder-java/wiki/building-the-sdk.
skipping tests as follows works: mvn package -Dmaven.test.skip=true
but running as-is with tests doesn't: mvn package --log-file log.txt
log.txt attached. log.txt
My environment:
git --version
git version 2.13.3.windows.1
java -version
java version "10.0.1" 2018-04-17
Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
mvn -version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T14:33:14-04:00)
Maven home: C:\maven\apache-maven-3.5.4-bin\apache-maven-3.5.4\bin..
Java version: 10.0.1, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk-10.0.1
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Build steps:
cd c:\microsoft\repos
git clone https://github.com/Microsoft/botbuilder-java.git
cd botbuilder-java
mvn package

Compilation errors:
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /C:/microsoft/repos/botbuilder-java/libraries/botbuilder/src/test/java/com/microsoft/bot/builder/BotStateTest.java:[376,48] incompatible types: java.lang.Object cannot be converted to com.microsoft.bot.builder.CustomState
[ERROR] /C:/microsoft/repos/botbuilder-java/libraries/botbuilder/src/test/java/com/microsoft/bot/builder/BotStateTest.java:[397,48] incompatible types: java.lang.Object cannot be converted to com.microsoft.bot.builder.CustomState
...

This was fixed.  Please reopen if you still have problems.


When LSP for RobotFrameWork is also installed it will show a big bug

when
https://marketplace.visualstudio.com/items?itemName=robocorp.robotframework-lsp
is also installed it will show a big bug.

In that case it will not find the 'Click' Keyword.


gh-294 Setting locality groups on table creation/schema update

The default will be each schema group as its own locality group, this can be changed by users in the accumulo shell if needed.

Is it possible to put some testing around this change?


Signing in on Toggle Desktop Version

Hi,
Love your app!!! However when signing in on the desktop version, I get the following error message:
'I/O error: Permission denied'
Please have a look.
Thanks,
Jacques

The error suggests that the app is unable to write to a certain file location.
Please share more details about your operating system and how you have installed the app.

outdated issue as no info was provided


Depreciation of methods for symfony 2.7.6

Hi,
i am using symfony 2.7.6 and was trying your bundles who looks promising even if i am passing a lot of time for decoding some things from documentation...
I had many DEPRECIATION warning... i ve listed the one i received on the list page from the frontend
DEPRECATED - The "_method" requirement of route "aimeos_shop_admin_file" in file "D:\xampp\htdocs\dev2\belch\vendor\aimeos\aimeos-symfony2/Resources/config/routing.yml" is deprecated since version 2.2 and will be removed in 3.0. Use the "methods" option instead.  +
DEPRECATED - The "_method" requirement of route "aimeos_shop_admin_json" in file "D:\xampp\htdocs\dev2\belch\vendor\aimeos\aimeos-symfony2/Resources/config/routing.yml" is deprecated since version 2.2 and will be removed in 3.0. Use the "methods" option instead.  +
DEPRECATED - The "_method" requirement of route "aimeos_shop_admin" in file "D:\xampp\htdocs\dev2\belch\vendor\aimeos\aimeos-symfony2/Resources/config/routing.yml" is deprecated since version 2.2 and will be removed in 3.0. Use the "methods" option instead.  +
DEPRECATED - The Symfony\Component\Form\Extension\Csrf\CsrfProvider\CsrfProviderAdapter class is deprecated since version 2.4 and will be removed in version 3.0. Use the Symfony\Component\Security\Csrf\CsrfTokenManager class instead.  +
DEPRECATED - The Symfony\Component\Security\Core\SecurityContext class is deprecated since version 2.6 and will be removed in 3.0. Use Symfony\Component\Security\Core\Authentication\Token\Storage\TokenStorage or Symfony\Component\Security\Core\Authorization\AuthorizationChecker instead.  +
DEPRECATED - Defining the initRuntime() method in the "form" extension is deprecated. Use the needs_environment option to get the Twig_Environment instance in filters, functions, or tests; or explicitly implement Twig_Extension_InitRuntimeInterface if needed (not recommended).  +
I am continuing my tests and will send you my comments about the Doc and some other tests.

The SecurityContext thing is more complicated as we want to support all versions since Symfony 2.4. For the initRuntime() method I have no clue yet where this is used. At least it's not implemented by the Aimeos Symfony bundle but maybe by another bundle we are using.

@aimeos Is the security context actually used in this package at all? And you do not have any custom Twig extensions, do you?

@xabbuh We don't use any custom Twig extensions but the security token for CSRF protection

@aimeos Can you point me to the code where this happens?

@xabbuh Here it is: https://github.com/aimeos/aimeos-symfony2/blob/master/Service/View.php#L102

I am not sure I understand. The CsrfTokenManager class is not deprecated.

@bertinl0609 Do you use any other bundles in your application?
I assume that another bundle creates the deprecation warnings

Hi,
Here are the list of bundles used...
public function registerBundles()
{
$bundles = array(
new Symfony\Bundle\FrameworkBundle\FrameworkBundle(),
new Symfony\Bundle\SecurityBundle\SecurityBundle(),
new Symfony\Bundle\TwigBundle\TwigBundle(),
new Symfony\Bundle\MonologBundle\MonologBundle(),
new Symfony\Bundle\SwiftmailerBundle\SwiftmailerBundle(),
new Symfony\Bundle\AsseticBundle\AsseticBundle(),
new Doctrine\Bundle\DoctrineBundle\DoctrineBundle(),
new Sensio\Bundle\FrameworkExtraBundle\SensioFrameworkExtraBundle(),
new AppBundle\AppBundle(),
new Aimeos\ShopBundle\AimeosShopBundle(),
new FOS\UserBundle\FOSUserBundle(),
);
    if (in_array($this->getEnvironment(), array('dev', 'test'))) {
        $bundles[] = new Symfony\Bundle\DebugBundle\DebugBundle();
        $bundles[] = new Symfony\Bundle\WebProfilerBundle\WebProfilerBundle();
        $bundles[] = new Sensio\Bundle\DistributionBundle\SensioDistributionBundle();
        $bundles[] = new Sensio\Bundle\GeneratorBundle\SensioGeneratorBundle();
    }

and the composer file:
"php": ">=5.3.9",
"symfony/symfony": "2.7.*",
"doctrine/orm": "^2.4.8",
"doctrine/doctrine-bundle": "~1.4",
"symfony/assetic-bundle": "~2.3",
"symfony/swiftmailer-bundle": "~2.3",
"symfony/monolog-bundle": "~2.4",
"sensio/distribution-bundle": "~4.0",
"sensio/framework-extra-bundle": "^3.0.2",
"incenteev/composer-parameter-handler": "~2.0",
"aimeos/aimeos-symfony2": "~1.0",
"sensio/generator-bundle": "^3.0",
"friendsofsymfony/user-bundle": "~2.0@dev"

I suspect the FOS user bundle to be the source of the remaining deprecation warnings.

@bertinl0609: Are there any news on this?

There was one remaining reference to "form.csrf_provider" in the admin interface which has been fixed now.

All deprecated parts has been removed in the Aimeos Symfony bundle and it works now with Symfony 3 without problems in dev-master


ECONNRESET when attempting bind or search even with reconnect set to true

We have been getting a Reconnect error with idle clients.
We do have reconnect: true but it only appears to reconnect after the bind or search fails which then means we need to build our own custom retry logic for the bind and search.
In general, is it advisable to use one LDAP client for all binds and searches or a new LDAP client for each bind? We are trying to decide on the best approach. We don't want to make a lot of LDAP clients that are sitting idle after they are finished being used. What would be a good way to close these connections when they are no longer needed?

In my experience, LDAP connections are generally used for a single conversation.

@jsumners we also were wondering if it's necessary to create a new ldap client for each and every request. We finally decided to create just a single client instance and pass those instance to several sub functions which call bind() unbind() for each search request

client = ldap.createClient()
bind(),   search(groupFilter), unbind() ->  in order to get a large list of groups
For all members of those groups, we asynchronously send further search requests (via promise + throtteling) in order to fetch all member detail information:  bind() search(userFiler) unbind()
process.exit()

We talk about 2000-3000 members here. We use the same client for all requests. So far it works, but when using fast throtteling settings and/or large ldapjs timeout settings (like e.g. 20000 ms)  we experience a lot of unsolicited erros like [02:07:39.620] ERROR (ldap-client/13296): unsolicited message and also errors like ConnectionError: 24__ldaps://my.server.intern:3070 closed
As a workaround we also use own retry code (using npm retry package). But the behaviour is strange.
Also tried to listen to various events: http://ldapjs.org/client.html#client-events, but it seems that events like res.on('timeout' err =>etc.) are not possible ? res.on('error') works, though.

👋
On February 22, 2023, we released version 3 of this library. As a result, we are closing this issue/pull request.
Please see issue #839 for more information, including how to proceed if you feel this closure is in error.


Blank first reference in rendered pdf

I had posted the issue of blank first reference in rendered pdf and after that found a solution to the issue. I had posted both in RStudio community site at this location. I am posting the link to it as an issue here in case it the right achemso.bst file can be used in this repository to avoid the problem for future users.

Thanks for sharing this - I've updated the extension itself to use the correct BST file as you diagnosed!

Thanks for quickly fixing this.


Prettier deletion of images, continue on error, show status of deletion

Prerequisites checklist

[x] I have read the contributing guidelines.

What is the purpose of this pull request? (put an "x" next to an item)

[ ] Documentation update
[x] Bug fix
[ ] New feature
[x] Other, please explain:

What changes did you make? (Give an overview)
Don't abort if an image can't be deleted, continue on other parts anyway. Display a short message about the deleting status and mention happening reload of the page.
Add unavailable and failed deletion of images to Photobooth log.
Also get rid of photoBooth.deleteTmpImage function.
Use own modal for general error / success messages to be displayed, don't use the print modal for that.
Todo:

[x] define time until reload via config

Is there anything you'd like reviewers to focus on?

Almost ready. Need to be tested again while the config has been added. Latest commits will be squashed and force-pushed.


Add a fuzzy/exact toggle option to search field forms

The search pop-up for references and people (and I would assume other things too) is case-specific. So if a user doesn't use the correct capitalization in the search, they will not return the results. Can we make it not-case-specific?
This is just a minor thing, no emergency, but we should try to change it as some point because it will trip people up if they don't know the entered capitalization (like in a title) or are just lazy and don't capitalize names in searches (I'm guilty as charged!).

I proposed a solution where we could toggle between exact and fuzzy search, but @doricon pointed out it may just be fine to always have it be fuzzy.

It will be very helpful to have specimens be a fuzzy search. We will probably have more specimens in the database than any other node type, which makes dropdown menus not feasible. And specimen names are often non-intuitive strings of letters and numbers, prone to typos and users not wanting to type in the whole thing.

Okay, we will do just fuzzy.

I think this has been completed?


Add job summary

Supercharging GitHub Actions with Job Summaries | The GitHub Blog
https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/

Done.


Is this still maintained?

The .NET version is somewhat outdated causing it not to work on Linux (https://github.com/madhatter22/LinqToLdap/issues/26 / https://github.com/madhatter22/LinqToLdap/issues/25), which should be fixable by a simple .NET version upgrade.
Especially as this library is recommend by OWASP and (if upgraded) a great way to access the LDAP in a cross-platform way (until https://github.com/dotnet/runtime/issues/102601 is implemented in .NET), and supports paging this is kinda sad.

Ah found WIP in branch feature/drop-support-pre-netstandard2.0... https://github.com/madhatter22/LinqToLdap/compare/master...feature/drop-support-pre-netstandard2.0
What is the status here, not ready to merge?

Hi, it's not ready to merge yet. I monitor this project, but haven't had personal time to devote to it. I plan to have a new release in the next 3 months.

Is there any update on this? We would like to migrate to Azure AppServices under linux, so an updated version would be appreciated.


rancher pipeline and alert don't work behind proxy

Rancher versions:
rancher/rancher:v2.0.8
rancher/rancher-agent:v2.0.8
Docker version: (docker version,docker info preferred)
1.13.1
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
CentOS Linux release 7.5.1804 (Core)
3.10.0-862.11.6.el7.x86_64
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Bare-metal
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes
Steps to Reproduce:

alert

create a slack notifier
click test -> OK
create a alert with slack notifier -> no alert

pipeline

enable pipeline

Results:

no alert is sent to slack
jenkins can't download required plugins

Possible Reason
alert and jenkins don't follow HTTP_PROY, HTTPS_PROXY, NO_PROXY env defined in rancher/rancher container.

There's no guarantee that rancher server and user clusters always use the same proxy server. It depends on the architect, so it would be proper to let users handle that.

It would be nice if UI can set proxy because edit system workload looks dangerous.

ok, let's keep this open to see if we can have settings to configure proxy for all system components as an enhancement.

I'm running into the same issue. Rancher Server is working fine with HTTP/HTTPS proxy, but when pipelines get triggered the Jenkins container has no knowledge of the proxy and thus fails.
I tested by created a simple stage that pulls docker:latest image and it fails.

@gitlawr Perhaps I'm missing something but this still doesn't seem to solve my issue. Jenkins still doesn't work with the proxy and throws out errors if I check the jenkins workload log:
WARNING: Failed to connect to Kubernetes at https://kubernetes.default: http://{proxy address}: Name or service not known
I've tried various values for {proxy address} including the internal k8s address for a cntlm container, a dns address that's resolvable from all other pods and a completely outside the cluster address.
@gabrielcalderon Did you manage to solve this on your side?

@Woklet Nope, I even try setting the Java proxy environment variables in the Jenkins pod. I gave uo on using the pipelines features and went back to handling CI/CD from Gitlab-CI.
I did notice the jenkins-pipeline-slave workload tries to resolve DNS using kube-dns which fails causes it tries using /etc/resolv.conf instead of using the proxy.

I was successfully able to build through jenkins by setting http proxy, but image publish is failing for me with logs:
12:43:18 Debug Mode (client): false
12:43:18 Debug Mode (server): false
12:43:18 Registry: https://index.docker.io/v1/
12:43:18 Labels:
12:43:18 Experimental: false
12:43:18 Insecure Registries:
12:43:18  <IP_ADDRESS>/8
12:43:18 Live Restore Enabled: false
12:43:18
12:43:18 WARNING: No swap limit support
12:43:18 WARNING: bridge-nf-call-iptables is disabled
12:43:18 WARNING: bridge-nf-call-ip6tables is disabled
12:43:18 + /usr/local/bin/docker build --rm=true -f ./Dockerfile -t 00000000 . --pull=true --label org.label-schema.build-date=2019-08-02T12:43:18Z --label org.label-schema.vcs-ref=00000000 --label org.label-schema.vcs-url=
12:43:19 Sending build context to Docker daemon  6.641MB
12:43:19 Step 1/5 : FROM golang:1.11
12:43:19 Get https://registry-1.docker.io/v2/: dial tcp <IP_ADDRESS>:443: getsockopt: connection refused
12:43:19 time="2019-08-02T12:43:19Z" level=fatal msg="exit status 1"
Do i need to set proxy in docker-registry service as well ?

Same issue on Rancher 2.4.3. We have Rancher on-prem and want our pipelines to pull from GitLab.com which can't be reached w/o our corporate proxy.

I'm having the same issue on Rancher 2.4.5
Is there any workaround to fix that ?
Any help would be appreciated.

Same issue here on Rancher 2.4.4 - Docker build step (npm ci) fails because npm cannot get through the corporate proxy.

@AkashEMC  you need to rebuild image used for this with correct proxy/no_proxy settings
In my example it looks like:
FROM rancher/plugins-docker:18.09
ENV HTTP_PROXY=http://proxy:81/
ENV HTTPS_PROXY=http://proxy:81/
ENV NO_PROXY=docker-registry.p-sn8n4-pipeline,<IP_ADDRESS>/8,localhost,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>/16,<IP_ADDRESS>/16,<IP_ADDRESS>/24,example.com
You need to add correct proxy and no proxy so it is able to communicate to registry.

Same issue on 2.5.2 and RKE HA. We are not be able to clone the github example repos if Rancher is behind a proxy. Please, could you provide a guide about how to configure the pipeline/workloads/whatever in that case?

Rebuild all images which are needed for pipeline and add HTTP envs and no proxy envs to dockerfiles:)
As i've written in above comment


Karma Tests fail in angular 1.2.11

I'm trying to write karma tests for my project and i'm having issues getting the tests to work.  I am using angular 1.2.11 and karma 0.12.4 with Jasmine 2.0 and karma-jasmine 0.2.2.
The biggest issue I have with the example tests is .trigger() is used to test keypress and that isn't a supported function for jqLite.
When I updated it to triggerHandler() it appears as though nothing happens...like the keypress event either doesn't fire or the page elements don't recognize the keypress.

UI.Utils modules was split in individuals repositories. If still valid, please consider re-submitting the issue on its dedicated issue tracker.
See the README for details.


Add proposal: Package Editor Commands

Forums link: https://forums.swift.org/t/pitch-package-editor-commands/42224
Implementation: https://github.com/apple/swift-package-manager/pull/3034/

@tomerd Sounds good to me, thanks! I need to make a few small edits now that SE-0294 has been accepted, but I can push those changes tonight.

okay let me know when that is done


Add UpdateRGBA that can update a texture with uint32 pixels

Add a function that wraps SDL_UpdateTexture, but takes uint32 RGBA "pixels".

Tested the functionality with this small program.

Thanks!


Predicate failure for mismatched Voter GovAction

Description
Closes #3685
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[x] New tests are added if needed and existing tests are updated
[x] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[x] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[x] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

If you want, you could squash the first 3 commits,  to have a cleaner commit history, since they are a meaningful together

Could you please rebase on master?


CCE-668: adding back lodash.

After some quick debugging, looks like we need lodash so adding it back in this PR so that we are not blocked from working on other tickets. We may need a separate ticket to look at lodash and whether or not to include it in the future.

ticket - https://jira.hybris.com/browse/CCE-668


Update: Danish

Strings.da.resx needs to be updated.
@simonclausen maybe you can assist :)

I'm just running through my stack of GitHub notifications. Better late than never, I guess - sorry for not getting back on this!
I have not used POEditor before - it looks like Danish is not in there yet, correct?


What method can repair the black hole in the depth_image?

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win10

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC

SDK Version
2.25.0

Language
python3.6

Segment
Robot

Issue Description
<Describe your issue / question / feature request / etc..>
In the process of using the depth map, I found that there are some black holes in the depth map. The data value displayed is 0. In pyrealsense, which function can be used to repair it?

The post-processing filters that I linked you to in another message can be used for hole-filling too.
https://github.com/IntelRealSense/librealsense/blob/jupyter/notebooks/depth_filters.ipynb

@Dontla

Device preset (Use the appropriate high fill rate JSON preset)
Postprocessing filters (decimation+holefilling)

Hi @Dontla Do you need further help on this?
Thanks,


Refactor original code

Refactored the code so each type of command are in separate .py files
e.g. all the bot commands to do with watchlist management are in one python file
Closes #74

Refactoring looks good, we just might need to test it out a bit more since its a pretty big refactor. Good work though, just reset the watchlist.json and should be all goods.


[APP] Add agent utility to the StatsViewer

I'm moving the main discussion points from slack here, so we don't do any accidental duplicate work
Motivation
Pitt said in the meeting that he'd like us to be able to show each agent's utility - the issue with that is we don't have a standardised way of measuring this.
Approach
Utility calculations should involve the allocation of resources
Standard utility would be a measure of the food received (each day) out of the total available food.
We have to note that utility is (in essence) similar to a transaction in that we "earn" utility (HP gain due to food) and "spend" utility (HP drain due to messaging / cost of living etc)
This gives 2 baseline approaches to modeling utility:

Use total food intake as a fraction of the total food available to it
Use "net profit" of utility = hp gain due to food - hp loss due to CofL/comms/other

It would make sense to then combine either of these with a mapping (utility function) such as U(foodIntake) = log(foodIntake) (at least an increasing, concave function). Ideally we'd have some piecewise/bounded function involving a log or a concave quadratic to account for sensitivity of obtaining further utility at various utility levels. i.e. at lower levels of utility, consuming a unit of food will grant higher utility than if this same unit of food were to be consumed at a higher level.
We would also want to normalize these by the number of deaths, to give an average utility per lifespan metric.
Consensus
Ultimately whichever approach we choose doesn't matter, just needs to be standardized over all agents.
Alternative was to use HP, however it doesn't really consider resource allocation.
Additional
This doesn't seem to have a use for agents' decision making so it's going to be just for visualization/stats purposes

One way is:

Implement the utility computation model in the backend
In base agent, modify the story state to include the utility (you will also have to modify the data struct in the logger)
In the story state logging function, use the utility variable and add it to the story log for the agent state

The story state doesn't log the agent state every tick, only when a message / death / food change happens, so if you don't want that you can add a logger in the state loggers for the utility and report the utility every tick or every day


Initial PR

This PR includes content from:

eggd_pandora (https://github.com/eastgenomics/eggd_pandora/)
submit_variants_INCA (https://github.com/eastgenomics/submit_variants_INCA/)
variant_workbook_parser (https://github.com/eastgenomics/variant_workbook_parser/)

Elements of all these scripts have been merged together to make this an all-in-one process

This change is

Hello @kjwinfield! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file pandora.py:

Line 16:1: E302 expected 2 blank lines, found 1
Line 41:5: E265 block comment should start with '# '
Line 44:30: E711 comparison to None should be 'if cond is None:'
Line 57:13: E122 continuation line missing indentation or outdented
Line 60:13: E122 continuation line missing indentation or outdented
Line 61:13: E122 continuation line missing indentation or outdented
Line 63:10: W291 trailing whitespace
Line 87:80: E501 line too long (86 > 79 characters)
Line 136:13: E122 continuation line missing indentation or outdented
Line 137:13: E122 continuation line missing indentation or outdented
Line 138:13: E122 continuation line missing indentation or outdented
Line 170:80: E501 line too long (80 > 79 characters)
Line 189:1: E302 expected 2 blank lines, found 1
Line 208:1: E303 too many blank lines (3)
Line 221:6: W291 trailing whitespace
Line 255:80: E501 line too long (85 > 79 characters)
Line 303:70: W291 trailing whitespace
Line 311:80: E501 line too long (86 > 79 characters)
Line 315:11: W292 no newline at end of file

In the file utils/utils.py:

Line 14:1: E302 expected 2 blank lines, found 1
Line 109:5: E303 too many blank lines (2)
Line 140:1: E302 expected 2 blank lines, found 1
Line 195:1: E302 expected 2 blank lines, found 1
Line 359:1: E302 expected 2 blank lines, found 1
Line 379:1: E302 expected 2 blank lines, found 1
Line 475:1: E302 expected 2 blank lines, found 1
Line 594:1: E302 expected 2 blank lines, found 1
Line 655:27: W292 no newline at end of file


Problem with validation

Method Illuminate\Validation\Validator::validateIranMobile does not exist.
Method Illuminate\Validation\Validator::validateIranPhone does not exist.

do you Add the following provider to providers part of config/app.php?
Anetwork\Validation\PersianValidationServiceProvider::class

@amirpiri Do you still have problem?


Ceph cluster authentication Error EACCES: access denied

I am running Ceph cluster in my production environment, with three Nodes (Node1, Node2, Node3)
The issue is this : I cant authenticated againist the ceph cluster
At the moment the Ceph dashboard is down and cant be accessed.
[root@node3 ceph]# sudo ceph auth import -i ceph.client.admin.keyring
Error EACCES: access denied
I had created a ceph.client.admin.keyring in the /etc/ceph where the ceph.conf is located.
Just wondering where I am getting it wrong and how to fix it,

did you able to solve it?


Using the Azure Disk example with AKS results in PersistentVolumeClaim is not bound

We are trying the Azure Disk example on Azure Managed Kubernetes and it fails with PersistentVolumeClaim is not bound
Also, it is not clear from the example documentation what storage account and what credentials are used by the Kubernetes cluster to create the disk.

Please ask questions on kubernetes-users email list or Slack (slack.k8s.io).

@ahmetb I will gladly ask questions there but the point of this issue is to improve the examples.

Sorry my bad. I misread.

@toddysm Does that mean you have successfully gotten the PersistentVolumeClaims to work? Care to share how?

I have the same problem.

I get the same warnings, seems to be a delay on the disk creation process, after a while I get confirmation about disk being mounted


PieChart cannot render value

Summary
Thanks for the fantastic work. I think this is a great alternative to nativescript-ui-chart.
Just reporting a small issue where PieChartRenderer crashes with an undefined mValueLinePaint object. In an angular project, this error is ignored and the pie chart is rendered successfully but the label value cannot be displayed due to this problem.
Demo project included in this repository crashes at below line of PieChartRenderer.ts
        if (!this.mValuePaint) {
            this.mValuePaint = new Paint();
            this.mValuePaint.setAntiAlias(true);
            this.mValueLinePaint.setStyle(Style.STROKE); <-- Crashes here.

Expected Behavior
mValueLinePaint need to be initialized.
Device (please complete the following information):

Android Version Pie 9.0

@triple-j-95 thanks a lot! should be fixed in 1.1.31