Loading cached tile data is blocked while bad reception

TO REPRODUCE THE ISSUE, FOLLOW THESE STEPS:

Open the StreetComplete app while having bad receptions, so ping time might be above 10 seconds.
Map appears (partly) blank
No new tiles are shown from the cache, while panning/zooming

RESULT:
The initial map view is sometimes loaded from cache and sometimes stuck directly after start. But most of the time the map start to get stuck after some tiles are already loaded. None new tiles are shown from the cache, after a long(!) while the problem disappears and maybe the reception got a bit better or there's a timeout which is reached and the connection is considered to be dead.
EXPECTED RESULT:
Tiles from cache should always be loaded regardless of the connection quality. If some tiles are outdated or missing, those fetches should be scheduled for a background task.
ENVIRONMENT:

What operating system and device did you produce this issue on?
Android 8.0 / ONEPLUS A5010 (OnePlus 5T)
If you used a released version, what is the version number?
I've been using tangram-es in 0.9.0 which is built into StreetComplete 4.0.

This ticket has been already submitted to the StreetComplete bug tracker under the number https://github.com/westnordost/StreetComplete/issues/846.

Hmm it's hard to know exactly what's going on here without a reproducible test case. I have a hunch that this could be related to the timeouts used for our HTTP layer on Android (see https://github.com/tangrams/tangram-es/blob/master/platforms/android/tangram/src/main/java/com/mapzen/tangram/HttpHandler.java#L129-L131). You should try to shorten those timeout values in HttpHandler or create a subclass that instantiates a OkHttpClient with different timeouts, then see if that improves the behavior in this case. We didn't put a lot of effort into finding good values for these, so I wouldn't be surprised if they can be improved!

Well, I'm not a java developer, just a user. But the developer insist that this should be a bug in tangram-es not his code. So there we are.
The timeout and http stuff isn't really the problem here, I suspect.
It just seems that loading an item from cache is blocked by an operation on the network side
So maybe one missing tile is blocking other tiles from beeing loaded or loading tiles from cache do a network operation like asking the server if they could be refreshed for example. But currently the app nearly all the time shows few or no tiles if opend on bad reception, but I know I've looked at that area just one or two days ago. After a while this bug seems to resolve itself, refreshing all tiles from cache in no time. This lead me to my assumption that there's a timeout running for an operation which then is discarded or retried, lifting the lock for other operations to happen.

A possible factor is that each of the StreetComplete tiles has a .0 file with the following line:
Cache-Control: max-age=86400
Is this something that the cache algorithm checks or that the tile provider has control over?

The StreetComplete client can accept stale cached responses with a change on the client side, I've explained more on the original StreetComplete issue. I think this is the appropriate solution for this behavior.


It's impossible to subscribe to topic after unsubscribing

Topics are not removed from mTopics map on unsubscribe. Therefore we get "Attempted to subscribe to already-subscribed path!" error when trying to subscribe again. The fix seems to be pretty easy.
Though I would still suggest automatic resubscribing to topics when sockets are connected.

Thanks for finding this! I'll publish a fix tomorrow.

Many thanks for a quick response!

Sorry I didn't publish a fix on Friday, I forgot that it wasn't a workday. I'll release a fix tomorrow, once I'm back at my work computer. Sorry for the wait.

NP. Thanks for letting us know!

Let me know if that fix doesn't work

There is a small problem with it. You're removing destination before fetching topic id. Therefore it will always result in an error when unsubscribing with null id.

Okay, yeah, I've started testing that commit and I see the problem

I've been pretty busy at work -- can you let me know whether this works for you? Committing the obvious fix now...

Thanks! I have no problem with resubscribing now. However, now after each re-connect, I receive more and more duplicate messages somehow :D I'll try to understand how share() operator works and come up with a fix. Please, advise if you see the solution at once.

Got it. We just don't disconnect from messages() on disconnect(). Therefore each new connect() will result in callSubscribers() executed as many times as connect() was called.

If you can give an access I'll create a PR with the fix.

Duplicate messages? Interesting. I've seen that before, but I had fixed it then. Good find!
Could you make a separate issue for it? Then we can work on a PR. Thanks!


Support versions besides buster

Hi there, I really love all the work by the dart team, Dart really has become one of my favorite languages (also outside of Flutter).
I am wondering why there are only buster-slim images in this repo - I require newer versions of many packages. Personally, I just copied the entire Dockerfile into my repo and changed buster -> sid, but it would be awesome to have them directly in here.
FROM dart:stabel-sid or something like that :)

Upvoting! Would also love to see an alpine flavored image for the dart sdk

Not exactly what's being asked here, but we're upgrading to bullseye:
https://github.com/dart-lang/dart-docker/pull/77
In general, we follow the latest Debian stable, based on https://dart.dev/get-dart#linux.


[ENH] - task label for ASL

[x] the asl is  similar to bold, task is also performed during some of ASL acquisitions   and it will be nice to include _task-<label> also for ASL and m0scan

[x] it is very important to keep m0scan in perf   directory not in fmap

CC @patsycle @HenkMutsaerts

CC @patsycle @HenkMutsaerts

[x]  the asl is  similar to bold, task is also performed during some of ASL acquisitions   and it will be nice to include _task-<label> also for ASL and m0scan
[x]  it is very important to keep m0scan in perf   directory not in fmap

About the task: this will be implemented in a later version for ASL. For the current version, we opted only to implement the approaches described from the White paper. Adding task in the specification is not a big job, however, it will be much more work for the validator.
About the m0scan: agree that m0scan should always be stored within the perf folder. However, in case of pe polar, the m0scan with reversed direction is a correction for the m0scan in the perf directory. Therefore, the one with reversed direction should go to the fmap directory, to be consistent with other MR modalities. So the original text was correct.

[x]  the asl is  similar to bold, task is also performed during some of ASL acquisitions   and it will be nice to include _task-<label> also for ASL and m0scan
[x]  it is very important to keep m0scan in perf   directory not in fmap

About the task: this will be implemented in a later version for ASL. For the current version, we opted only to implement the approaches described from the White paper. Adding task in the specification is not a big job, however, it will be much more work for the validator.
About the m0scan: agree that m0scan should always be stored within the perf folder. However, in case of pe polar, the m0scan with reversed direction is a correction for the m0scan in the perf directory. Therefore, the one with reversed direction should go to the fmap directory, to be consistent with other MR modalities. So the original text was correct.

I agree with @patsycle that more "features" to ASL can and should be incorporated after the initial incorporation of ASL into BIDS.
At this stage of the ASL BEP, we only accept changes if they address either:

bugs or mistakes in the currently proposed feature set
incompatibilities with the existing BIDS

Everything else (backwards compatible features) will have to wait until after the initial release.

I agree with @patsycle that more "features" to ASL can and should be incorporated after the initial incorporation of ASL into BIDS.
At this stage of the ASL BEP, we only accept changes if they address either:

bugs or mistakes in the currently proposed feature set
incompatibilities with the existing BIDS

Everything else (backwards compatible features) will have to wait until after the initial release.

I just reverse back to original docs by removing task-label

I just reverse back to original docs by removing task-label


Can a server accept a querier's terms? - Disclaimer in the query

At the moment there is a disclaimer section in the query. Can a server accept a querier's terms?
"disclaimer" : {
  	"version": "<semantic version>",
  	"text": "Disclaimer text...",
  	"terms" : "Terms text..."
  },

hey Rishi, this is really a FYI to the server and a legal piece saying what can be done with the data. It is up to the host to decide on whether to support it.
In MME we have one from each node we pass on with the query,
https://github.com/ga4gh/mme-apis/tree/master/disclaimers
we can talk about this more at next search meeting, and clarify further

I agree, a server cannot accept terms and conditions *, it's a machine.
For the response, it may make sense to include a disclaimer, but I'd want to see this as a meta component rather than a root level object.

If we use something like ADA-M it is possible we could encode consent for use. There's scope for automated discoverability of services which a given user can access. I wonder how many implementations there are of ADA-M...

For MME, originally there was a disclaimer, but this field was used to also express terms of use, so we ended up with two fields. The disclaimer says something about the data, the terms says something about what you agree to if you view and or use the data.
I think there's scope to have both, but having terms under disclaimer doesn't make any sense to me, especially in the request.

Speaking for GeneMatcher, we store terms / disclaimers for each MME instance we connect to, these are both included in the match emails we send out to our submitters (along with references to use). If the remote MME instance sends us terms / disclaimers in the MME request / response, those override what is stored.

How about this for the disclaimer section, I renamed it citation, but it would be great to have another terms for this:
"citation" : {
  	"version": "<semantic version>",
  	"disclaimer": "Disclaimer text...",
  	"terms" : "Terms text...",
  	"reference" : "Reference text...",
  },

I'm happier calling it acknowledgments, I feel it's more semantically correct.
references, do we mean "the way in which you must acknowledge this resource" or "here are some papers related to this resource"?
I think we should have the former, and not sure of the use of the latter (as that could be encoded in the former). I guess you could say that acknowledgment statements could be included in the terms, but it's more explicit as a separate field.
As an aside, should we specify the content of these fields? Text only? Markdown? HTML? (I feel we should avoid HTML).

@rishidev:

At the moment there is a disclaimer section in the query. Can a server accept a querier's terms?

No, but the user can. In my implementation of MME, we do not show the response to the user unless they accept the terms from that service.
To my mind, a server doesn't need to accept or reject terms, as it won't, or at least shouldn't, do anything with the data without confirming with a user first.
In this instance, I've viewing a "user" as someone who is interacting with a "service" which queries Search API "servers". Not as a developer which writes code to make search requests to servers.
I acknowledge there is a use case of using such a Search API in an automated fashion say in a pipeline, however an implementor / developer should read the terms presented by each endpoint to make sure they are allowed to use the data in the way they would like.
There may need to be some "best practice" policy level document built up around this aspect.

Not HTML, that would create a security vulnerability, text only.  I am ok with creating a new issue for this, happy to do this if you want.

Agreed, not HTML.
@fschiettecatte Feel free to create a new issue for a new component. I'm yet to formalise the process for creating components, but I have a general feeling in my head (assuming we merge and follow the format in #30 ).

Done, see #31

To clarify - The response side of the query-repsonse process wasn't what the issue was created for. So a service asking a user to agree terms and conditions before returning results is a debate for a different issue if it is needed.
As I understand it the having the disclaimer/terms etc in the request/query is making a a demand on the server that the server agrees to. On the query (i.e. what the user makes to the server) side I think the disclaimer/terms etc should be removed as it is either meaningless or potentially harmful. From comments above @Relequestual concurs with this. If we want to include it in I would like to have the Regulatory and Ethics Work Stream advise on this matter which might not fit with the schedule for finalising a version of the API.
So my suggestion is to take this out for now. If it wants to be put back in we create another issue to re-instate it, which would give us the chance to have the GA4GH Regulatory and Ethics WS advise.
GA4GH is starting to look at automated terms etc so there may well be a framework to go along side this API to handle this kind of requirement sensibly.

Thanks @rishidev
What if the "terms" were not for displaying or viewing the data, but required to accept for using the data (beyond processing by a client for those pourposes)?
@harindra-a Any thoughts on if this should remain or be removed for 0.1.0?

@Relequestual  The issue isn't the existence of querier imposed terms per se, but how open text querier imposed terms are accepted in a legally recognisable manner. If a server makes it clear 'we will do X,Y,Z with provided data' and a querier sends this in with 'You cannot do Y,Z with the data I provide' what happens? As it stands there if there needs to be terms they are outside the scope of this API, but I would like to pass this on to DURI or Reg & Ethics for further advice.

hi guys, good discussion. Definitely important long term.
I would vote we push this for post Basel/October though, for now go with how we do things in MME. I know from DURI folks, they are pretty early stage. So let's swing back to this post first release.

Oh sure, I don't feel defining this is the responsibility of this project.
I feel it makes sense to have at least something while the finer points are being worked out by other groups.
In terms of "how we do things in MME", that could work for now, in that each node must connect with each other node, but I highly expect the majority of the nodes which implement the Search API will require no authenitcation, and be discoverable, much in the same way Beacons are.
As such, the MME way of, only authed, on a node to node bases agreement, but then you have to draw up policy saying that clients must show terms of use to their users.

Yup, I meant MME way just for the approval process demo for the next few months, and maybe even phase 2 (using real data).
But long term (into next year), you are correct, the network will be a mix of open and authenticated nodes and will need specialized agreements. I think Mike Brudno brought this up last MME meeting as well. Maybe we should start a small group to investigate this as it will be a long term thing (actually MME is still ironing this out after this many years). I know few  policy folks who are regulars at Search meetings, maybe they can take this on and take lead

I view the acknowledgments section as a convenience bucket for the transport of terms & conditions. The protocol should not define what happens with then once they are out of the pipe. As I mentioned before MME v1 has a lot of policies which repository member are required to adhere to which have nothing to do with the protocol per se, and requiring users to accept terms & conditions falls into that.

hi folks, lets push this for post-October discussion. I think there are some interesting directions we can take this, so let's hold discussion for when we have a bit more time. Maybe we nominate a subgroup to investigate it post-October.
I annotated/labeled this issue/thread to "After-1.0.0" to focus efforts for Basel, hope that's OK with everyone.


docs(examples): ignore routes.d.ts and generate it automatically in routes-gen example

In routes-gen example, it would be a better pattern to not commit the autogenerated route typings to the repo, instead generating them after install so they can be there for the CI.

@frontsideair Examples go against main branch.
Please rebase your branch onto main & set it as base branch of this PR.

Done!

@frontsideair It seems like something went wrong while rebasing.
Running the following command should fix it though:
git reset --hard main && git cherry-pick 6126f4e && git cherry-pick b5e8aea && git push -f

Should be fine now.

@frontsideair You still have some commits in your branch that aren't supposed to be here.
Please run
git reset --hard main && git cherry-pick 2170332 && git cherry-pick 1d2bcd3 && git cherry-pick de1290e && git push -f

Woah, my bad. Fixed it now, thanks!


Add tf.unravel_index as an equivalent of np.unravel_index

This fix tries to address the issue raised in #2075 where there was no implementation of  tf.unravel_index.
The tf.unravel_index could be quite useful in many places.
This fix adds the tf.unravel_index in CPU kernel. Note order in np.unravel_index has not been added yet.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Thanks @martinwicke for the review. The PR has been updated.

@yongtang could you take a look at the test failures?

Thanks @josh11b for the review. The PR has been updated.

@martinwicke good to go?


Refactor cursor positioning

It was previously possible to create a position with a null section or
an invalid section (like a list section). A position must have a section
that the cursor can be rendered at; this PR adds an assertion to that
fact.
Before this change, if the window.getSelection() pointed at the editor's
element, Position#fromNode would naively assume that the post's first
section at offset 0 was the position, but this creates an invalid
position when the first section is a list section.
This tightens up some of the cursor positioning and adds a bunch of tests for Position#fromNode in various scenarios.

add Post#headPosition and #tailPosition
add Section#isSection property
Refactor Position#fromNode
tests for Position#fromNode for text nodes, element nodes, card-related nodes
Position constructor asserts it has a valid leaft section and offset

:tada: :tada: :tada:


No highlighting and type interference for localy used enum variants.

enum TestEnum {
    VariantA,
}

Given this enum, when VariantA is used in global scope then highlighting and type interference work correctly:

However if it's used in function scope it doesn't work correctly:

Duplicate of #1165.


Docker Build of Controller Fails

I tried to build the docker image for the controller. However, the cargo build fails due to the use of an unstable Feature in a library used by a dependency. Adjusting the Image Version to rust:1.77-bookworm fixed the problem for me.

Thanks for the issue!
Has been updated in 0af65396709002a9a6e9df8e155b1f838f765708 and will be merged to main soon.


Flush redis before syncing database

Call FLUSHDB on configured redis DB (REDIS_URL) before updating database

Hello @ivan-c! Thanks for submitting the PR.

In the file manage.py, following are the PEP8 issues :

Line 68:1: E302 expected 2 blank lines, found 1


Windows Features from Config tab not geting installed

Describe the bug
Clean installation of Windows 11 ("world" setup) OS build 22631.3007 (January 2024), installed drivers and all updates.
Uninstalled most remaining bloat before starting winutil.
In winutil, first fixed winget, then ran "Desktop" recommended tweaks which all finished succesfully.
But when selecting any of the Features from "Config" tab and clicking "Install Features", I get this text in powershell window and nothing happens. Everything worked fine in previous OS build (December 2023).
===================================
---   Features are Installed    ---
---  A Reboot may be required   ---
To Reproduce
Steps to reproduce the behavior:

Install WIndows 11 OS build 22631.3007 (January 2024)
Start winutil
Click "Config" tab
Select any of the features
Click "Install Features"

Expected behavior
Selected windows features install and the world is fine.
Screenshots

Additional context
When I try clicking "Install Features" again, the info text "features being installed, a reboot may be required" is printed again, as the screenshot shows.

Maybe I should have added that I used OS.click website (https://os.click/en) to download the latest Windows build ISO (currently 22631.3007).

Same issue here, downloaded windows 11 from official site and used microwim too on it.

I just tried installing some windws features with winutil on a separate machine that is still on Windows 11 21H2, and it didn't work there either.
I guess there must have been some pull request that misbehaved because I used winutil in the past on that machine with no problems, and windows there has not been updated for ages.

After some testing the issue seems to have started at the  commit to main branch made by Chris in 2024-01-12. The logic of checking if the checkboxes are selected changed a lot in that commit, and it seems to be causing it.

Same here on Windows 11 Pro 22H2 (official iso not MicroWin):

Fixed in last update.


High rate of incorrect predictions

Hello,
I'm not sure if this is something I'm doing wrong or you've encountered this before. Consider the following actions:
In the adult dataset I put aside a validation set, which neither my model nor DiCE has seen. From those, I select a number of samples whose age = 31, and use those to generate counterfactuals by varying everything other than age. Other than this I am not using any weights.
After that, I use my model to get a prediction on these generated counterfactuals. In a lot of the cases my model's prediction is not what DiCE thinks it would give.
Is there any way for me to increase DiCE's fidelity to my model?
Thanks

That's not possible, DiCE explanations are always truthful to the ML model by definition. In other words, we are simply tweaking the input instance until we get a different prediction from the same ML model. It is difficult to say anything more without looking at your code. Perhaps, you are missing out on something while creating a validation set. For instance, are you normalizing the continuous features and one-hot-encoding the categorical features in the validation data? You can use DiCE's data interface to create a validation set as follows
dataset = helpers.load_adult_income_dataset()
d = dice_ml.Data(dataframe=dataset, continuous_features=['age', 'hours_per_week'], outcome_name='income')
train, test = d.split_data(d.normalize_data(d.one_hot_encoded_data))
X_test = test.loc[:, test.columns != 'income']
y_test = test.loc[:, test.columns == 'income']

For your reference, I have included a sample code implementing your logic that gave me valid results.
import dice_ml
from dice_ml.utils import helpers

import tensorflow as tf
from tensorflow import keras

print(tf.__version__) # 2.1.0

# creating a testing dataset - the inbuilt ML model in DiCE for adult data is trained only on the 'train' data below
dataset = helpers.load_adult_income_dataset()
d = dice_ml.Data(dataframe=dataset, continuous_features=['age', 'hours_per_week'], outcome_name='income')
train, test = d.split_data(d.normalize_data(d.one_hot_encoded_data))
X_test = test.loc[:, test.columns != 'income']
y_test = test.loc[:, test.columns == 'income']

# get normalized age=31
normalized_age = (31-d.train_df['age'].min())/((d.train_df['age'].max()-d.train_df['age'].min())) # should print 0.1917808219178082

# we can verify if the above number is correct using the following
# (normalized_age*(d.train_df['age'].max() - d.train_df['age'].min())) + d.train_df['age'].min() # should give you 31

my_test = X_test[X_test['age']==normalized_age]
print(my_test.shape) # (187,29)
# there are 187 instances with age =31 in our data, I'm choosing the first one below as an example.

# create a test instance dictionary
my_test_instance = {}
for feature in d.feature_names:
    if feature in d.continuous_feature_names:
        my_test_instance[feature] = (my_test[feature].iloc[0]*(d.train_df[feature].max() - d.train_df[feature].min())) + d.train_df[feature].min()
    else:
        encoded_features = [feat for feat in d.encoded_feature_names if feat.startswith(feature)]
        for encoded_feat in encoded_features:
            if my_test.iloc[0][encoded_feat] == 1.0:
                my_test_instance[feature] = encoded_feat.split(feature+'_')[1]

print(my_test_instance)
# {'age': 31.0,
#  'workclass': 'Private',
#  'education': 'HS-grad',
#  'marital_status': 'Single',
#  'occupation': 'Blue-Collar',
#  'race': 'White',
#  'gender': 'Female',
#  'hours_per_week': 40.0}

d = dice_ml.Data(dataframe=dataset, continuous_features=['age', 'hours_per_week'], outcome_name='income')

backend = 'TF'+tf.__version__[0] # TF2
ML_modelpath = helpers.get_adult_income_modelpath(backend=backend)
m = dice_ml.Model(model_path= ML_modelpath, backend=backend)

exp = dice_ml.Dice(d, m)

# changing every feature except age
dice_exp = exp.generate_counterfactuals(my_test_instance, total_CFs=4, desired_class="opposite", features_to_vary=['workclass', 'education', 'marital_status', 'occupation', 'race', 'gender', 'hours_per_week'])

# visualize the results
dice_exp.visualize_as_list(show_only_changes=True) # prints the following
# Query instance (original outcome : 0)
# [31.0, 'Private', 'HS-grad', 'Single', 'Blue-Collar', 'White', 'Female', 40.0, 0.019464194774627686]
#
# Diverse Counterfactual set (new outcome : 1)
# ['-', 'Self-Employed', '-', 'Married', 'White-Collar', '-', '-', 48.0, 0.75]
# ['-', '-', 'Doctorate', 'Married', '-', '-', '-', 26.0, 0.697]
# ['-', '-', 'Masters', 'Married', '-', '-', '-', '-', 0.749]
# ['-', '-', 'Prof-school', 'Married', '-', '-', '-', 58.0, 0.858]

# To check that the predictions are indeed equal
for ix, cf in enumerate(exp.final_cfs):
    model_pred = exp.predict_fn(cf)
    cf_pred = exp.cfs_preds[ix]
    print(model_pred, cf_pred)
# prints the following
# [[0.75035185]] [[0.75035185]]
# [[0.69670826]] [[0.69670826]]
# [[0.73952144]] [[0.73952144]]
# [[0.85771877]] [[0.85771877]]

Thanks! It's very kind of you to provide the code. It helped me find my bug.


Vehicle Routing with modified distance matrix does not compute objective function correctly?

What version of OR-Tools and what language are you using?
Language: Python
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
Routing Solver
What operating system (Linux, Windows, ...) and version?
MacOSX Monterey
What did you do?
I tried solving the Hamiltonian Path Problem (AKA "open TSP").  I followed directions here: https://developers.google.com/optimization/routing/routing_tasks about how to modify the distance matrix of this example: https://developers.google.com/optimization/routing/vrp#model
I adapted it to my own problem and ran the following example shown below, which is intended to solve Hamiltonian path problem, with arbitrary start/end vertices.

from ortools.constraint_solver import routing_enums_pb2
from ortools.constraint_solver import pywrapcp

def create_data_model():
    """Stores the data for the problem."""
    data = {}
    distance_matrix = np.array([[0,0,0,0,0],[0, 0., 4., 5., 5.], [0, 5., 0., 3., 3.], [0, 5., 3., 0., 4.], [0, 5., 5., 5., 0.]])
    data['distance_matrix'] = distance_matrix
    data['num_vehicles'] = 1
    data['depot'] = 0
    return data

def print_solution(data, manager, routing, solution):
    """Prints solution on console."""
    print(f'Objective: {solution.ObjectiveValue()}')
    max_route_distance = 0
    for vehicle_id in range(data['num_vehicles']):
        index = routing.Start(vehicle_id)
        plan_output = 'Route for vehicle {}:\n'.format(vehicle_id)
        route_distance = 0
        while not routing.IsEnd(index):
            plan_output += ' {} -> '.format(manager.IndexToNode(index))
            previous_index = index
            index = solution.Value(routing.NextVar(index))
            route_distance += routing.GetArcCostForVehicle(
                previous_index, index, vehicle_id)
        plan_output += '{}\n'.format(manager.IndexToNode(index))
        plan_output += 'Distance of the route: {}m\n'.format(route_distance)
        print(plan_output)
        max_route_distance = max(route_distance, max_route_distance)
    print('Maximum of the route distances: {}m'.format(max_route_distance))

def main():
    """Entry point of the program."""
    # Instantiate the data problem.
    data = create_data_model()

    # Create the routing index manager.
    manager = pywrapcp.RoutingIndexManager(len(data['distance_matrix']),data['num_vehicles'], data['depot'])

    # Create Routing Model.
    routing = pywrapcp.RoutingModel(manager)

    def distance_callback(from_index, to_index):
        """Returns the distance between the two nodes."""
        # Convert from routing variable Index to distance matrix NodeIndex.
        from_node = manager.IndexToNode(from_index)
        to_node = manager.IndexToNode(to_index)
        return data['distance_matrix'][from_node][to_node]

    transit_callback_index = routing.RegisterTransitCallback(distance_callback)

    # Define cost of each arc.
    routing.SetArcCostEvaluatorOfAllVehicles(transit_callback_index)

    # Setting first solution heuristic.
    search_parameters = pywrapcp.DefaultRoutingSearchParameters()
    search_parameters.first_solution_strategy = (routing_enums_pb2.FirstSolutionStrategy.PATH_CHEAPEST_ARC)

    # Solve the problem.
    solution = routing.SolveWithParameters(search_parameters)

    # Print solution on console.
    if solution:
        print_solution(data, manager, routing, solution)
    return solution

What did you expect to see
I expected to see a non-zero objective function value.
What did you see instead?
The objective is 0:
Objective: 0
Route for vehicle 0:
 0 ->  4 ->  3 ->  2 ->  1 -> 0
Distance of the route: 0m

Maximum of the route distances: 0m

It doesn't seem to be computing the distance between consecutive indices correctly:
routing.GetArcCostForVehicle(previous_index, index, vehicle_id) returns 0 regardless of the inputs provided.
Is this the expected behavior?  From what I can tell, my callback should compute the distance correctly.  What else can I do to get the correct distance of the route?

The solver is integral
All floats are rounder to 0.
Asked so many times :-(

If its been "Asked so many times" then maybe there should be a warning message.  Perhaps that's a feature request.


Use --key=value to pass args to sidecar

Fixes #4
Requires https://github.com/projectriff/function-sidecar/pull/16

LGTM

squashed and merged as https://github.com/projectriff/function-controller/commit/a2ffd7584ddc9f26dfd3d694528ad81adea38271


Checking a RadioGroup.Item doesn't update the input's checked attribute

Bug report
Current Behavior
Checking a RadioGroup.Item does render a RadioGroup.Indicator,  but doesn't update the input's checked attribute (check the DOM)
Expected behavior
Checking a RadioGroup.Item should add a checked attribute to the input; and clicking another should remove it
Reproducible example
Check this Codesandbox  for a minimal reproducible example:
Suggested solution
Additional context
Your environment
check Codesandbox

Software
Name(s)
Version

Radix Package(s)
@radix-ui/react-radio-group
0.0.14

React
n/a

Browser

Assistive tech

Node
n/a

npm/yarn

Operating System

My bad, I learned it wasn't the native behaviour. Closing.

My bad, I learned it wasn't the native behaviour. Closing.


Please make the capacity column proportional and centred!

I would like to suggest improving the channel depiction in the capacity column.
Please make all bars proportional to each other and centred around the zero point.
In order to clearly show what I mean here are two pictures. First as it is now, and second how I would like to see it
As is

As should be

I also suggest shortening the amounts to 1 decimal place using "M" for million
so 2.1M <-------> 37.9M


forbid empty case conditions list

Resolves issue #1501: a case clause with no when clause must be rejected
First yarp patch, please lmk what I messed up!

Closing in favour of PR#1508!


[MM-28729] Fix days calculation for duration

Summary
Fixes the days calculation for duration by using the asDays() function as opposed to days() to get the accurate count of days when the duration has exceeded a month's length of time. asDays() is needed since days is the largest unit of time being displayed here. The value of days is rounded down to the nearest integer since the remainder is displayed as hours and minutes.
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/15785

Hello @jmakhack,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@lieut-data @crspeller @itao  I don't have permissions to add reviewers, but this would be for your team :)
Please also add hacktoberfest-accepted label, thanks!

@jmakhack, just a heads up that we will wait after we release v1.0.0 (which we are testing now) to merge this PR. I'll add the Do Not Merge label and we can remove it when v1.0.0 is tagged and released.

/update-branch

Thank you again for your contribution, @jmakhack!


[kudu1] No key input accepted

Problem

After recent factory repair https://github.com/130s/hut_10sqft/issues/440, and upgrading all deb pkgs, kudu1 stopped reacting to keyboard input after OS reboot.
Can't even log on to each user at the display manager's login console. Issue already happening there, meaning this is irrelevant to each user account's setting.
Only exceptional key is caps key, as assigned in Ubuntu's k/b config (i.e. caps-ctrl are swapped), seems to be reacting.

Impact
This makes the laptop headless, which I don't intend. And I'm planning kudu1 to be one of main daily computers. So this is critical.

I don't find any unusual behavior when typing in over ssh.

Screen saving mode got canceled when I touched a random key. So Ubuntu IS detecting key stroke.

syslog is surprisingly short for today (8:40 is likely when I turned the power on).
Feb 22 08:40:26 fussili-kudu1 rsyslogd:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="1360" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Feb 22 08:40:28 fussili-kudu1 colord[3234]: failed to get session [pid 11843]: No data available
Feb 22 08:40:34 fussili-kudu1 anacron[9978]: Job `cron.daily' terminated
Feb 22 08:40:34 fussili-kudu1 anacron[9978]: Normal exit (1 job run)
Feb 22 08:40:42 fussili-kudu1 system76-daemon[1352]: 2021-02-22 08:40:42,460  INFO  saving brightness at 137
Feb 22 08:45:18 fussili-kudu1 boinc[2506]: No protocol specified
Feb 22 08:45:18 fussili-kudu1 boinc[2506]: dir_open: Could not open directory '/dev/input/mice' from '/var/lib/boinc-client'.
Feb 22 08:45:18 fussili-kudu1 boinc[2506]: 22-Feb-2021 08:45:18 [---] Resuming network activity
Feb 22 08:45:19 fussili-kudu1 boinc[2506]: No protocol specified
Feb 22 08:47:55 fussili-kudu1 boinc[2506]: message repeated 157 times: [ No protocol specified]
Feb 22 08:47:56 fussili-kudu1 boinc[2506]: No protocol specified
Feb 22 08:53:15 fussili-kudu1 boinc[2506]: message repeated 317 times: [ No protocol specified]
Feb 22 08:53:16 fussili-kudu1 boinc[2506]: 22-Feb-2021 08:53:16 [---] Suspending network activity - computer is in use
Feb 22 08:53:22 fussili-kudu1 system76-daemon[1352]: 2021-02-22 08:53:22,531  INFO  saving brightness at 464
Feb 22 08:53:32 fussili-kudu1 system76-daemon[1352]: 2021-02-22 08:53:32,532  INFO  saving brightness at 137
Feb 22 08:54:49 fussili-kudu1 systemd[1]: Started Session 13 of user nfussili.

I see `dir_open: Could not open directory '/dev/input/mice' from '/var/lib/boinc-client'.`.

I see dir_open: Could not open directory '/dev/input/mice' from '/var/lib/boinc-client'..

I misread boinc with bionic :p...It is about the boinc app and it seems to be resolved https://github.com/BOINC/boinc/issues/2335. That shouldn't be causing my issue?

Tried xord-input thing but no.
https://askubuntu.com/questions/1033767/keyboard-not-working-after-update-to-18-04
$ sudo apt-get install xserver-xorg-input-all
:
The following NEW packages will be installed:
  xserver-xorg-input-all
0 upgraded, 1 newly installed, 6 to remove and 0 not upgraded.
Need to get 4,112 B of archives.
After this operation, 383 kB disk space will be freed.

$ startx
xauth: (stdin):2:  unknown command "fd834d67c9d4b0a628110cccddbde93b"

/usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server

Invalid MIT-MAGIC-COOKIE-1 keyxinit: giving up
xinit: unable to connect to X server: Resource temporarily unavailable
xinit: server error
Couldn't get a file descriptor referring to the console
$

I found it stranger than I thought.

IIRC, first time I observed was AFTER I was able to log on at the display manager and moved the cursor over synergy.
At the password input field that I thought was display manager's login console, I clicked "Switch Account", which lead to another view where I see the list of existing users with my main account selected. This is expected. Then, there I was able to type. But typing in the password would lead to the same previous view where only the password was requested and no k/b input was taken.

Anyways, now, after https://github.com/130s/hut_10sqft/issues/522#issuecomment-783398546, I rebooted OS and it seems to be working. Maybe the missing xserver-xorg-input-all was the key?

Happened again out of blue. It persisted for 2 OS reboots (with MATE) so I ended up switching display manager to something like "Ubuntu default" or something. So far it's been ok (for 30 mins).


[CUDA] Enable async copy along with aggressive pipelining

This start using async copy ops for tensorcore pipeline which is enabled
for sm80+ targets.
This also enabled more aggressive pipelining in order to take advantage
of the async ops.
This adds a pass for multibuffer transformation needed for pipelining. This
change is under review upstream and once it lands the pass will only call the
upstream transformation.
Note that this cherry-pick one llvm commit, based on timing this will probably not be needed. If needed this can go in a separate PR.

Dont really follow all the details here. So stamping.

Thanks, let me know if there is something I can do to make it clearer going forward.

nice!!!


Crash on shift clicking seeds from chest

I got the following crash while mucking about my chests. There was a recent Terrafirmacraft update though, so maybe it was fixed there. I had just salted some beef, but the crash happened shift clicking some carrot seeds.
http://pastebin.com/Y9tgGxeJ

TFC has just updated and the update does fix quite a few obscure crashes. We'll be updating once the ATLauncher server (currently having issues) is up again. Please let me know if you can reproduce the bug then. I would need a lot more information to try and replicate it myself. SSP or SMP? Single or double chest? Clicking in or out? I'm guessing it is some odd interaction with Inventory Tweeks.

Please reopen if you experience this bug again. I've not been able to replicate this in current or past builds.


🚀 Create Qodana TypeScript GitHub Action

Added the initial TypeScript version of our GitHub Action.
It can

run Qodana images (as before)
automatically upload the report (so the logs won't be lost anymore)
automatically set up GitHub caches
add annotations

Every added step is enabled by default but can be easily disabled by action parameters. Note: I changed action.yaml – let's discuss it (I believe we should be able to allow any Docker image names)

Tests (here I'm testing things I can locally and via provided GitHub Action to run the Action in Actions 🤯) – https://github.com/tiulpin/qodana-action/runs/4511564215
Example run – https://github.com/tiulpin/dokker/runs/4511638796?check_suite_focus=true
Annotations preview in Pull Request view – https://github.com/tiulpin/dokker/pull/2/files

LGTM


[WFCORE-6637] Upgrade commons-lang3 from 3.13.0 to 3.14.0

Jira issue: https://issues.redhat.com/browse/WFCORE-6637

Thanks @yersan and @fjuma


use case: transfer learning / finetuning

Most people don't train models from scratch but fine-tune a pretrained model instead.
The resulting dynamics of the model might therefore be different. On a different note: is not completely clear whether the observed oscillations are due to changes in the convnet filters or in the fully connected parts of the network

In this context it might be interesting to compare the learning / fine tuning of an image classifier on summer and winter images.

We would need a dataset with summer and winter images for this use case.

we can illustrate similar effects by experimenting on different random folds, i.e. cross validation.


Could you make a Letterpaper version?

Hello, these are great resources! I was wondering, however, if you could make a letterpaper-sized version so that North Americans can print this as well?

Hi. I'll keep only the A4 version for now but you can convert it easily to letter paper size on sites like https://docupub.com/pdfresize/


Build errors on latest Master for ot-br-posix on Ubuntu 20.10

Build errors on latest Master for ot-br-posix on Ubuntu 20.10
Followed the build instructions at (https://openthread.io/guides/border-router/build)
Platform used : Ubuntu 20.10 VM
Build Error logs -
[2/33] Building CXX object src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o
FAILED: src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o
/usr/bin/c++  -DOTBR_ENABLE_BACKBONE_ROUTER=1 -DOTBR_ENABLE_DBUS_SERVER=1 -DOTBR_ENABLE_DNSSD_DISCOVERY_PROXY=1 -DOTBR_ENABLE_MDNS_MDNSSD=1 -DOTBR_ENABLE_REST_SERVER=1 -DOTBR_ENABLE_SRP_ADVERTISING_PROXY=1 -DOTBR_PACKAGE_NAME=\"OPENTHREAD_BR\" -DOTBR_PACKAGE_VERSION=\"0.3.0\" -I../../include -I../../src -Ithird_party/openthread/repo/etc/cmake -I../../third_party/openthread/repo/etc/cmake -I../../third_party/openthread/repo/include -I../../third_party/openthread/repo/src/posix/platform/include -I../../third_party/openthread/repo/src -Wall -Wextra -Werror -Wfatal-errors -Wno-missing-braces -std=c++11 -MD -MT src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o -MF src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o.d -o src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o -c ../../src/mdns/mdns_mdnssd.cpp
../../src/mdns/mdns_mdnssd.cpp: In function 'const char* otbr::Mdns::DNSErrorToString(DNSServiceErrorType)':
../../src/mdns/mdns_mdnssd.cpp:174:10: error: 'kDNSServiceErr_BadSig' was not declared in this scope; did you mean 'kDNSServiceErr_BadTime'?
  174 |     case kDNSServiceErr_BadSig:
      |          ^~~~~~~~~~~~~~~~~~~~~
      |          kDNSServiceErr_BadTime
compilation terminated due to -Wfatal-errors.

Other set of errors -
FAILED: src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o
/usr/bin/c++  -DOTBR_ENABLE_BACKBONE_ROUTER=1 -DOTBR_ENABLE_DBUS_SERVER=1 -DOTBR_ENABLE_DNSSD_DISCOVERY_PROXY=1 -DOTBR_ENABLE_MDNS_MDNSSD=1 -DOTBR_ENABLE_REST_SERVER=1 -DOTBR_ENABLE_SRP_ADVERTISING_PROXY=1 -DOTBR_PACKAGE_NAME=\"OPENTHREAD_BR\" -DOTBR_PACKAGE_VERSION=\"0.3.0\" -I../../include -I../../src -Ithird_party/openthread/repo/etc/cmake -I../../third_party/openthread/repo/etc/cmake -I../../third_party/openthread/repo/include -I../../third_party/openthread/repo/src/posix/platform/include -I../../third_party/openthread/repo/src -Wall -Wextra -Werror -Wfatal-errors -Wno-missing-braces -std=c++11 -MD -MT src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o -MF src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o.d -o src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o -c ../../src/mdns/mdns_mdnssd.cpp
In file included from ../../src/mdns/mdns_mdnssd.cpp:36:
../../src/mdns/mdns_mdnssd.hpp:43:10: fatal error: dns_sd.h: No such file or directory
   43 | #include <dns_sd.h>
      |          ^~~~~~~~~~
compilation terminated.
[344/377] Building CXX object src/dbus/server/CMakeFiles/otbr-dbus-server.dir/dbus_thread_object.cpp.o
ninja: build stopped: subcommand failed.

Did you run "script/bootstrap"?
BRs,
Kangping
On Thu, May 6, 2021 at 2:51 PM saurabhst @.***> wrote:

Build errors on latest Master for ot-br-posix on Ubuntu 20.10
Followed the build instructions at
https://openthread.io/guides/border-router/build
Platform used : Ubuntu 20.10 VM
Build Error logs -
[2/33] Building CXX object src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o
FAILED: src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o
/usr/bin/c++  -DOTBR_ENABLE_BACKBONE_ROUTER=1 -DOTBR_ENABLE_DBUS_SERVER=1 -DOTBR_ENABLE_DNSSD_DISCOVERY_PROXY=1 -DOTBR_ENABLE_MDNS_MDNSSD=1 -DOTBR_ENABLE_REST_SERVER=1 -DOTBR_ENABLE_SRP_ADVERTISING_PROXY=1 -DOTBR_PACKAGE_NAME="OPENTHREAD_BR" -DOTBR_PACKAGE_VERSION="0.3.0" -I../../include -I../../src -Ithird_party/openthread/repo/etc/cmake -I../../third_party/openthread/repo/etc/cmake -I../../third_party/openthread/repo/include -I../../third_party/openthread/repo/src/posix/platform/include -I../../third_party/openthread/repo/src -Wall -Wextra -Werror -Wfatal-errors -Wno-missing-braces -std=c++11 -MD -MT src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o -MF src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o.d -o src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o -c ../../src/mdns/mdns_mdnssd.cpp
../../src/mdns/mdns_mdnssd.cpp: In function 'const char* otbr::Mdns::DNSErrorToString(DNSServiceErrorType)':
../../src/mdns/mdns_mdnssd.cpp:174:10: error: 'kDNSServiceErr_BadSig' was not declared in this scope; did you mean 'kDNSServiceErr_BadTime'?
174 |     case kDNSServiceErr_BadSig:
|          ^~~~~~~~~~~~~~~~~~~~~
|          kDNSServiceErr_BadTime
compilation terminated due to -Wfatal-errors.
Other set of errors -
FAILED: src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o
/usr/bin/c++  -DOTBR_ENABLE_BACKBONE_ROUTER=1 -DOTBR_ENABLE_DBUS_SERVER=1 -DOTBR_ENABLE_DNSSD_DISCOVERY_PROXY=1 -DOTBR_ENABLE_MDNS_MDNSSD=1 -DOTBR_ENABLE_REST_SERVER=1 -DOTBR_ENABLE_SRP_ADVERTISING_PROXY=1 -DOTBR_PACKAGE_NAME="OPENTHREAD_BR" -DOTBR_PACKAGE_VERSION="0.3.0" -I../../include -I../../src -Ithird_party/openthread/repo/etc/cmake -I../../third_party/openthread/repo/etc/cmake -I../../third_party/openthread/repo/include -I../../third_party/openthread/repo/src/posix/platform/include -I../../third_party/openthread/repo/src -Wall -Wextra -Werror -Wfatal-errors -Wno-missing-braces -std=c++11 -MD -MT src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o -MF src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o.d -o src/mdns/CMakeFiles/otbr-mdns.dir/mdns_mdnssd.cpp.o -c ../../src/mdns/mdns_mdnssd.cpp
In file included from ../../src/mdns/mdns_mdnssd.cpp:36:
../../src/mdns/mdns_mdnssd.hpp:43:10: fatal error: dns_sd.h: No such file or directory
43 | #include <dns_sd.h>
|          ^~~~~~~~~~
compilation terminated.
[344/377] Building CXX object src/dbus/server/CMakeFiles/otbr-dbus-server.dir/dbus_thread_object.cpp.o
ninja: build stopped: subcommand failed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openthread/ot-br-posix/issues/832, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOYD4SPSSQZHTEDNVBKKY3TMI4ANANCNFSM44GNGBEQ
.

@wgtdkp  yes I ran script/bootstrap.
I got the build working after I uninstalled libavahi-compat-libdnssd-dev on my Ubuntu VM . I did have a previous version of ot-br-posix installed before though.  Maybe that was the reason . Thanks for the help .I'll go ahead and close the issue.


zeto: update to v0.0.11 and fix lock functionality

Caveats: does not yet work with nullifier variants, and needs additional unit test coverage. However, locking behavior is likely to change further based on pending discussions in https://github.com/hyperledger-labs/zeto/issues/119.

Test failure in https://github.com/LF-Decentralized-Trust-labs/paladin/actions/runs/12564194673/job/35027006246?pr=494 is https://github.com/LF-Decentralized-Trust-labs/paladin/issues/254

Test failure in https://github.com/LF-Decentralized-Trust-labs/paladin/actions/runs/12564194673/job/35031167786?pr=494 was a 403 when attempting to download from GitHub.

Test failure in https://github.com/LF-Decentralized-Trust-labs/paladin/actions/runs/12566206225/job/35031345122?pr=494 is https://github.com/LF-Decentralized-Trust-labs/paladin/issues/495


WIP: Try asserting on weights and fees

Adding pallet_transaction_payment to the mocked environment during unit testing isn't going to work I think. Looking at https://github.com/paritytech/substrate/blob/master/frame/transaction-payment/src/lib.rs#L893 I think we will end up with a mocked implementation of fees (or will have to duplicate the implementation from runtime) in order to be able to use this pallet.


audit logging

audit logging with revert-to functionality
currently WIP, please take a sneak preview and give feedback

Trying to upgrade our production DB
    cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) Cannot add a NOT NULL column with default value NULL [SQL: 'ALTER TABLE advisory ADD COLUMN changed DATETIME NOT NULL'] (Background on this error at: http://sqlalche.me/e/e3q8)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) Cannot add a NOT NULL column with default value NULL [SQL: 'ALTER TABLE cve ADD COLUMN changed DATETIME NOT NULL'] (Background on this error at: http://sqlalche.me/e/e3q8)

The README should describe the updating steps :)

./trackerctl db upgrade should update my DB models right? Tried it with our production db and it kinda did not work :(

Ok,
log view:

I think the displayed username is too small it's pretty hard to read on my laptop.
/user/$name/log view, hide "« prev 1 next »" when there is no paging?
log view, only show + / - fields and hide default empty fields?
scheduling an advisory shows an empty change. Only "12 Feb 2019 20:16:46 ASA-201902-16 by jelle"

So this looks fine to me @anthraxx, shall we merge it?!

There is just a tiny bug i nearly fixed, right now entries like AVG keep changing the changed date even if the entry doesn't contain any modifications -- which results in empty log entries where nothing has changed. This is quote annoying but once i push the fix we can happily merge it.

Ok, god to hear! :+1:


Issues using it with postgres on ubuntu

I setup the django app following the steps, I also use postgres but when I try to makemigrations and migrate I get this error
(decomagna) sam@sam-Lenovo-G51-35:~/code/DECOMAGNA/decomagna$ python3 manage.py migrate
/home/sam/.local/lib/python3.6/site-packages/psycopg2/__init__.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: <http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>.
  """)
Operations to perform:
  Apply all migrations: admin, auth, common, contenttypes, inventory, pages, sessions
Running migrations:
  Applying inventory.0008_previousjob_location...Traceback (most recent call last):
  File "manage.py", line 15, in <module>
    execute_from_command_line(sys.argv)
  File "/home/sam/.local/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/home/sam/.local/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/sam/.local/lib/python3.6/site-packages/django/core/management/base.py", line 316, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/sam/.local/lib/python3.6/site-packages/django/core/management/base.py", line 353, in execute
    output = self.handle(*args, **options)
  File "/home/sam/.local/lib/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
    res = handle_func(*args, **kwargs)
  File "/home/sam/.local/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 203, in handle
    fake_initial=fake_initial,
  File "/home/sam/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "/home/sam/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "/home/sam/.local/lib/python3.6/site-packages/django/db/migrations/executor.py", line 244, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/home/sam/.local/lib/python3.6/site-packages/django/db/migrations/migration.py", line 124, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/home/sam/.local/lib/python3.6/site-packages/django/db/migrations/operations/fields.py", line 84, in database_forwards
    field,
  File "/home/sam/.local/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 421, in add_field
    definition, params = self.column_sql(model, field, include_default=True)
  File "/home/sam/.local/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 157, in column_sql
    db_params = field.db_parameters(connection=self.connection)
  File "/home/sam/.local/lib/python3.6/site-packages/django/db/models/fields/__init__.py", line 697, in db_parameters
    type_string = self.db_type(connection)
  File "/home/sam/.local/lib/python3.6/site-packages/django/contrib/gis/db/models/fields.py", line 105, in db_type
    return connection.ops.geo_db_type(self)
AttributeError: 'DatabaseOperations' object has no attribute 'geo_db_type'

This is what I have in the models file
from django.contrib.gis.geos import Point
from location_field.models.spatial import LocationField

class PreviousJob(models.Model):
    ...
    location = LocationField(based_fields=['city'], zoom=7, default=Point(1.0, 1.0))
    ...

I think you're not using a spatial database (PostGIS in this case):
https://docs.djangoproject.com/en/2.1/ref/contrib/gis/tutorial/#configure-settings-py
If you're using Postgres but not PostGIS, you should be using PlainLocationField


Fix recording events

There is an issue with writing events in different namespaces: GitHub Issue https://github.com/kubernetes-sigs/container-object-storage-interface-provisioner-sidecar/issues/140
This happens because events are created with a specified namespace, and the EventRecorder also has a namespace option set.
This PR removes the namespace option from the EventRecorder so events can be created in namespace they have specifyed.
Similar change can be found in this project
https://github.com/tsuru/remesher/commit/a8ccfa05b86a6d15b48546092c93f507f3121ad1#diff-243ebed2765f75e6a54f57167212fefb08c3b2a85967ad2acbc0eb78919019c1

@kvaps could you please add more description to the commit and github description? What are the symptoms of the issue, and how does this PR fix the issue?

@kvaps we really appreciate your contribution. There is a complication that makes this challenging right now. We are in the process of migrating from separate API/spec/controller/sidecar repos into a monorepo at https://github.com/kubernetes-sigs/container-object-storage-interface-api. We are still working on merging the controller into the monorepo, and the sidecar will come after that.
In the interest of ensuring your contribution gets recorded, I will propose this:
Could you change the merge target from kubernetes-sigs:master to kubernetes-sigs:monrepo (the monorepo branch)? We can then merge this, and the inclusion of the change will be handled once we finish moving the controller/controller.go code into its new location where it will be a better-named basis for shared code between controller and sidecar.

sure PR rebased

Also requesting @shanduur 's review since he worked on adding event recording

Ah, right! Must have missed that bit, thanks!

/approve

/lgtm


Asuswrt continuous ssh

Description:
An update to the Asus WRT device tracker component, which changes its low-level behavior: instead of connecting to the SSH or Telnet server upon each iteration, the connection is maintained, and the commands are issued over it.
This change fixes issue #7713, and eliminates the need for repetitive (and unnecessary) logins/logouts.
Related issue (if applicable): fixes #7713
Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Wow, awesome work, thanks for knocking that out. Will really help.


Latest version 1.5.3 is missing

The only change in v1.5.3 is related to FreeBSD:

Rebuild gitstatusd-freebsd-amd64 with clang to make it work on FreeBSD 13 (#262).

This fix which lannded after 1.5.2
https://github.com/romkatv/gitstatus/commit/7001409ed3d363373fce09e95e6ddb00787bcae8
fixes an issue with the terminal width not being reported correctly  for me in bash.

Sorry about that. I've released v1.5.3.
P.S.
If you mentioned that up front, that would've helped. In general, I hold in very low esteem issues and PRs that don't do anything useful for the reporter. The issue and the PR you've filed looked just like that. "Latest version is missing" doesn't say why you care. It looks like a random drive by.

Thats Fair I was just making the commits super late at night here so I was looking to just get it out I'll try and keep that in mind when opening future PRs in yours and others repos. Thanks


Auto Attribute removal in TagHelpers

Attributes that in normal razor code gets automatically removed gets special treatment with TagHelpers.

Only attributes that are not bound to tag helper properties will keep the existing razor behavior.
These attributes will generate the "naive" string and populate the TagHelperContext.AllAttributes
Expression Values that are result in false, null or string.Empty are stripped from TagHelperOutput.Attributes.
Example input:

TagHelperContext.AllAttributes will include [class, "false"]
TagHelperOutput.Attributes will not include class.

For other examples follow unit tests for WriteAttribute.

think we tested these scenarios and found<EMAIL_ADDRESS>resulted in attribute="" with a regular (non-tag helper) attribute.  only attribute="@null" and attribute="@false" lead to no generation for the attribute.  tag helper attributes should do the same thing.
FYI, see special-cases at:

https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.Razor/RazorPage.cs#L336 (for null)
https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.Razor/RazorPage.cs#L358 (for false)

4604c807c49daa560b92868503922bb89096a40d
https://github.com/aspnet/Mvc/commit/a0da6ec19f17dd0579ab0424044778608e483997


Upgrade mech SDK and actor template to 0.7.x

Upgrade to the latest actor SDK, codec, etc to bring in sync with newest waSCC

This has been fixed, closing


 It only escapes the 5 most common cases (the ones that usually cause parsing issues in HTML I believe): <>&"'
It is far from finished. I only went for it because I noticed the TODO note in HTML::Builder

Thanks!
We need a way to escape HTML, so this pull request is very handy.
However, why not just have HTML.escape(str : String) #=> String. I'm not sure I see the need for an HTML::EscapedString.
On a side note, I would leave it as two methods, something like this:
module HTML
  def self.escape(string : String)
    String.build { |io| escape string, io }
  end

  def self.escape(string : String, io : IO)
    string.each_char do |char|
      io << SUBSTITUTIONS.fetch(char, char)
    end
  end
end

That way you can escape a string and write it to an IO at the same time, without having to build a string. And you can use this in the HTML::Builder, because you are writing it to a StringIO.
I'd also not add the method String#html_escape, it's almost as short as doing HTML.escape(string).
What do you think?

Sure, I'm ok with that
As for the String#html_escape, I added it as more of a suggestion. I wasn't sure if I liked it either, but my moving the escape method to the HTML class, the call does get short enough that we don't need it

Sorry for the delay, I had totally forgot about this! :blush:


az webapp create ACR support

az webapp create ACR support
Fixes #7261
Adds ACR / private registry support to the webapp create command.
This checklist is used to make sure that common guidelines for a pull request are followed.

[X] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[X] I adhere to the Command Guidelines.

Thanks @Nking92 for getting this started.

ACR integration still not working well... I am trying using a docker-compose file via the following params:
az webapp create \
-g $RG \
-p $ASP \
-n $NAME \
-i $TAG \
-s $REG_USER \
-w $REG_PASS \
--multicontainer-config-type "compose" \
--multicontainer-config-file ./docker-compose-deploy.yml

With or without -i -s -w flags there are failures regarding ACR credentials.
The only way to get this working is to run the above without -i -s -w flags then update the container config via 'az webapp config container set' and add the repo credentials that way.
Seems clunky. Would be better to have this in one command.
Also there doesn't appear to be a way to make slot deployments with a docker-compose file... we're having to make a new web app deployment to work around. Feels like docker-compose could be better implemented to level up Web Apps IMO.


Downloading on flaky connections -- getting stuck

This is similar to #84
Sometimes on a poor internet connection the download gets stuck. I'm not able to reproduce it regularly but it happens from time to time
Platform Mac OS x 10.12.5
Python - 3.7
By the way I implemented a time-out mechanism that skips the download after 25 minutes of waiting  as a last ditch attempt to solve it using interuptingcow
Please check my fork and let me know your feedback :
https://github.com/smart-lemon/udemy-dl/commits/master
(Ideally it would be nice to have a back-off retry implementation for this ..
Thanks for developing this tool 💯

@smart-lemon i will check this and implement in next version the timeout mechanism as well.


Canadiens de Montréal Livery Fix

Is it a real livery or a fictional one?

Fiction
On Tue, May 7, 2024 at 2:31 AM kolos26 @.***> wrote:

Is it a real livery or a fictional one?
—
Reply to this email directly, view it on GitHub
https://github.com/kolos26/GEOFS-LiverySelector/issues/626#issuecomment-2097546218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A642O5QGSMMMA3QECNHH7CTZBBYLLAVCNFSM6AAAAABGXX4NPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXGU2DMMRRHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


[WIP][Enhancement]Optimize find_buckets_to_move to make sure find a move solution

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #7577 #4775
Problem Summary(Required) ：

Currently, find_buckets_to_move using a brute force search algorithm to search buckets to move, only search 1/2/3 bucket movements which may can't find a solution.

run all

run starrocks_be_unittest


PSQL: NOT NULL constraints of later added columns to existing tables are not detcted by sqlx::query!

Bug Description
Given an already existing table, e.g:
CREATE TABLE person (
	first_name TEXT NOT NULL
);

when adding a second column to the table, and adding a NOT NULL constraint, e.g.
ALTER TABLE person ADD COLUMN last_name TEXT; -- Add column without constraint for existing rows
UPDATE person SET last_name = ''; -- Add default value for existing rows
ALTER TABLE person ALTER COLUMN last_name SET NOT NULL; -- Add constraint

sqlx::query! will not throw a compile time error for the following query:
sqlx::query!(
    r#"INSERT INTO person (first_name)
    VALUES ($1)"#,
    "John"
);

While the new column itself is detected (e.g. for select queries), any later added NOT NULL constraints are apparently completely ignored.
Minimal Reproduction
Minimal github project
Info

SQLx version: 0.7.4
SQLx features enabled: ["postgres", "runtime-tokio"]
Database server and version: psql (PostgreSQL) 15.2 (Debian 15.2-1.pgdg110+1)
Operating system: Arch Linux 6.6.2-arch1-1 x86_64
rustc --version: rustc 1.76.0 (07dca489a 2024-02-04)

This is not a bug. If Postgres returns a successful parse result, we have no way of knowing the query is invalid. SQLx doesn't null-check bind parameters or do any sort of analysis on the query itself, only the metadata that Postgres returns.
In this situation, Postgres is likely returning a non-fatal warning message alongside the parse result, which we currently don't have a good way to surface. Unfortunately, emitting lint warnings from proc macros has been unstable for 6 years and doesn't look to be getting stabilized anytime soon. And turning any non-fatal warnings into compiler errors for all users would be an unacceptable breaking change.
We've talked about implementing a Clippy-like linter for SQLx, but that's a whole project in and of itself.
We could use the sqlx_macros_unstable/procmacro2_semver_exempt cfg-flags to conditionally enable the use of the proc_macro::Diagnostic API, but I have a feeling most people don't use those flags,
I think instead, we could make it optional to elevate these warnings to errors, either using an environment variable (e.g. SQLX_DENY_WARNING_NOTICES=1) or by setting a key in a config file committed to the project, e.g. a sqlx.toml.

Despite having already read issues about SQLx not null-checking, I had the illusion it did in my case and only altering the table was the issue. Yeah, should've definitely rechecked that.
Either way, the latter idea to provide an option to elevate warnings to errors sounds very useful to me. I think the ability to store the option to a file is crucial for reliability (opposed to remembering setting the environment variable every new session).
If using an environment variable includes the option to write it into e.g. the .env file, that sounds like the easier implementation.


ci: test only diff with GPU

What does this PR do?
Trying to limit testing scope as @awaelchli asked

Before submitting

[x] Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure to update the docs?
[x] Did you write any new necessary tests?

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.

Did you have fun?
Make sure you had fun coding 🙃

📚 Documentation preview 📚: https://torchmetrics--2359.org.readthedocs.build/en/2359/

btw, GH copilot is really bad :(


Your First Component

Page: https://id.react.dev/learn/your-first-component
Assignee: @Cikang44

Closed by @Cikang44 in #338


Update configuration_files.md

Short Description:
Improve documentation regarding allowed master values for TelegramTask.

in code strung username not allowed. only id

Check https://github.com/PokemonGoF/PokemonGo-Bot/blob/master/pokemongo_bot/event_handlers/telegram_handler.py#L80 looks like username allowed to me.

https://github.com/PokemonGoF/PokemonGo-Bot/blob/master/pokemongo_bot/event_handlers/telegram_handler.py#L125
not support username

https://github.com/PokemonGoF/PokemonGo-Bot/blob/master/pokemongo_bot/event_handlers/telegram_handler.py#L82 checks if username is string and restarts telegram handler with user id of provided string username.

why this duct tape? use id.

I think username is more intuitive but yeah nevermind then.

but work only after message to bot


Add the sendAnonymousStatistics parameter to the SafeBrowsing configuration

Also, let's distinguish the safebrowsing-related parameters within the AGProxyServerConfigC into the separate SafeBrowsingConfiguration (e.g. as ParentalControlConfiguration is implemented)

Testing instructions:

Enable setting in UI
Go to malicious site and see that this parameter is present in page source


Mili 19.2 compile error on Pascal

Describe the bug
Building mili 19.2 works fine on Pascal, but errors crop up when VisIt tries to compile against it. All errors are of the form:
"'some_file' can not be used when making a shared object; recompile with -fPIC".
The odd thing is that both VisIt's CXXFLAGS and CFLAGS are being used when compiling mili, which should include -fPIC.
To Reproduce

Build visit libraries (including mili)
Try to build visit.

Expected behavior
This works on mac (and now Windows, I believe). This should also work on Linux.
Desktop
Pascal (RedHat)

This hit me on CentOS 7 too.
I took a quick look and as far as I can tell it is down to the mili 19.2 Makefile.Library setting CC_FLAGS to @CC_FLAGS_OPT@ for the opt target whereas in 15.x it included @CFLAGS@ as well.
opt:   CC_FLAGS = @CFLAGS@ @CC_FLAGS_OPT@
I suspect patching this back in via bv_mili.sh would do the trick but I haven't tried it

@selbypa Thanks! I'll try this out today.

Adding the CFLAGS back in appears to resolve this issue. I'll go ahead and let the mili developers know about this.

The Mili library has been updated with the fix from above.

@biagas is still seeing this error when compiling with gcc-6.1.0 on pascal.

The third-party release appears to still be pointing to the old tag. I'll try to update it again.

I believe it gets it from the release. The files are manually copied to the release, so you would need to replace it yourself.

Yeah, I just realized that. I updated the release, and I'll open a PR with the updated checksums.

I downloaded the mili tarball directly from github, and tried again. It works, thanks!


-Zcompile-progress: Use the target name in the progress bar when building a test/binary.

Thus fixes hilarious output like
https://twitter.com/ManishEarth/status/1015479576670027776.
New output: https://asciinema.org/a/F1rkCk0bTWKQMr1NEScia3IYx

r? @matklad
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+
👍

:pushpin: Commit a40a5c70d7130587211481b93779850532040de6 has been approved by alexcrichton

:hourglass: Testing commit a40a5c70d7130587211481b93779850532040de6 with merge 50032b9a5908bb7426201f7d2afa6a880b9174f1...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 50032b9a5908bb7426201f7d2afa6a880b9174f1 to master...


Update search-sku-tier.md

Updating region status and suggested alternatives

@HeidiSteen
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Please make 'webpack-dev-server' an optional peer dependency

For projects such as ours we already have a dev server and will never use webpacks.
It would be really great if we can make 'webpack-dev-server' an optional peer dependency so we don't have download it unnecessarily.
https://docs.npmjs.com/files/package.json#optionaldependencies
What do you think?
Thanks
Jenna

Thanks for bringing that up. We already have an open ticket for that in #70 and we will definitely change that.

Great.. sorry i should have looked before opening. Feel free to close and ill watch that one.
Thanks.

This is now done in version 2.0 for webpack 2.0


Quartz in Android

StdSchedulerFactory in Quartz requires some classes from java.beans that aren't included in Android. There is a jar file available from Google to add the classes, but the import path to the classes needs to be changed in the Quartz files which are read-only. Any help in resolving this would be appreciated.

Although this is an old issue, as it turned up in a search for me, I'll post an answer.
Even if you get Quartz to compile on Android, it probably won't do what you want. Android will destroy applications shortly after the user leaves them (whether or not they were explicitly closed). Quartz can't execute anything if it's not running.
If you want to execute tasks on a schedule on Android reliably, you need to use Android's APIs to do so (such that your task will execute at the desired time). JetPack WorkManager is the way to do that: https://developer.android.com/topic/libraries/architecture/workmanager


feat: surface additional hub-spoke dns sharing outputs

Description

Add additional hub and spoke outputs
Renaming "hub spoke vpc" example

Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

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


Intermediaries - Calculation of v.L

v.L should actually be [5993x4 double]. The problem is coming from the fact that my dependent variable is specified as [10x1].

@Hickles02 Was this issue resolved?

@tmlouw No this hasn't been resolved. I think this is also the reason why my mol fractions aren't correct (the one is above one).

@tmlouw Hi Professor.
Would you please take a screenshot of what you changed in my code this morning? I remember it wasn't that much.
I'm struggling to get it right, so thought just want to see what you did again.
Thanks.

@tmlouw Hi Professor.

Everything is now as it should be. The only problem I've got left is my liquid mol fraction that is being calculated is still above one.

I've updated my code in Github, with the updated naming. So if you would please have a look and let me know if you spot something that's not right.  Thanks for all the help.


Multiple access nodes  in multi-node cluster

Hi,
Why the multi-node chart only allows one access node? Shouldn't it be possible to have several replicas of the access node to ensure HA? What happens if this single access node goes down?

Hi,
Have you found anything related to this? I'm also checking if a single access node goes down. Then can I create a new access node for the existing cluster, or can we have an option to use streaming replicas and patroni for access_node failover?

Multinode helm chart is deprecated and not supported anymore. If you want to see this chart supported then we are looking for community maintainers - https://github.com/timescale/helm-charts/tree/master/charts/timescaledb-multinode#call-for-maintainers

@paulfantom is currently promscale support multi-node timescale now? If so we are happy to help

Promscale does support multi-node timescale. However, we are not accepting any contributions to a multinode helm chart as it is unmaintained. @zfy0701 do you want to become a community maintainer of that chart?

I am closing this issue as TimescaleDB-Multinode helm chart is no longer maintained and deprecated. We are looking for potential community maintainers who could help us in getting that helm chart working again. If you wish to become a maintainer, please contact us on slack.
Keep in mind that TimescaleDB is not and will not be dropping multinode setup. Deprecation is only about helm chart.


Buttons sliders havana

Codecov Report

Merging #173 into master will increase coverage by 0.27%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #173      +/-   ##
==========================================
+ Coverage   87.61%   87.88%   +0.27%
==========================================
  Files          80       79       -1
  Lines        2841     2905      +64
  Branches      537      610      +73
==========================================
+ Hits         2489     2553      +64
  Misses        348      348
  Partials        4        4

Impacted Files
Coverage Δ

src/container/NGLContainer.tsx
96.22% <ø> (+0.52%)
:arrow_up:

src/data/AminoAcid.ts
97.29% <ø> (ø)
:arrow_up:

src/component/widget/ComponentCard.tsx
93.22% <ø> (+0.76%)
:arrow_up:

src/component/PredictedContactMap.tsx
96.49% <ø> (+7.75%)
:arrow_up:

src/helper/PlotlyHelper.ts
92.59% <ø> (-2.76%)
:arrow_down:

src/component/widget/ComponentMenuBar.tsx
80% <ø> (-0.89%)
:arrow_down:

src/helper/DataHelper.ts
65.54% <ø> (-1.13%)
:arrow_down:

src/component/NGLComponent.tsx
88.28% <ø> (ø)
:arrow_up:

src/container/TensorTContainer.tsx
76.72% <ø> (+0.4%)
:arrow_up:

src/data/BioblocksPDB.ts
63.57% <ø> (+0.52%)
:arrow_up:

... and 26 more

Continue to review full report at Codecov.

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


Custom date field in tasks that can be filtered via the GUI

Currently it's possible to filter tasks by "Created at" which opens up a calendar window where one can select "is after" e.g. 06.12.2023 00:00
If add a custom date to the "data" field in the json file only regex expression are available
{
"id": 3,
"data": {
"image1": "xxx1.jpg",
"image2": "xxx2.jpg",
"custom_field":"a_b_c"},
"image_creation_date":"2019-06-27T17:25:20.084014Z"
}
is it possible to have a custom date field in the task json that can be filtered via dei GUI (e.g. I'd like to label images acquired in 2019, independent of what date they were added to the db)?

I have tried to enter a custom date in the input task json for the field ("created_at":"2019-06-28T12:52:14.703569Z") but that value is overwritten in the db (understandably)
It is possible to use regex for data ranges, but it is a bit cumbersome

Thank you

Thanks for your feature request. We'll forward this to the product team to see if we can add it to the roadmap.


Add LiteJet (a lighting control system) component

Description:
Add a new LiteJet component and light, switch, scene, and automation platforms for controlling that lighting system.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#1361
Example entry for configuration.yaml (if applicable):
litejet:
  url: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A501JNX3-if00-port0
  exclude_names:
  - 'Button #'
  - 'Scene #'
  - 'Timed Scene #'
  - 'Timed Scene#'
  - 'LV Rel #'
  - 'Fan #'

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass [Note: My test VM is having trouble with a few core async tests, but these tests also fail on the unmodified dev branch.]
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

This is my first time programming in Python, using Git, and submitting to Home-Assistant.

Awesome! 🎉 🐬

Thanks. :)


[Zeta][Tool] Move generate_client_protocol.sh to engine module

Purpose of this pull request
This PR move generate_client_protocol.sh to engine module. Because it is a tool only for zeta engine.
Also do some change so the generated file will in seatunnel-engine-core/src/main/java/org/apache/seatunnel/engine/core/protocol/codec. Don't need copy it any more.

Does this PR introduce any user-facing change?
no

How was this patch tested?
Tested in local. It work fine.

Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

cc @EricJoy2048 @ic4y


Mentions of feature gates do not mention which components they are for

It is not clear for which components "CSIMigrationAzureFile" feature gate is intended.

https://kubernetes.io/docs/concepts/storage/volumes/#azurefile-csi-migration

It is not clear which controller manager is meant — cloud controller manager or kube-controller-manager. According to this page section it's intended for kube-controller-manager.

https://kubernetes.io/docs/concepts/storage/volumes/#aws-ebs-csi-migration-complete (InTreePluginAWSUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#azuredisk-csi-migration-complete (InTreePluginAzureDiskUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#azurefile-csi-migration-complete (InTreePluginAzureFileUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#openstack-csi-migration (InTreePluginOpenStackUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#gce-csi-migration-complete (InTreePluginGCEUnregister)
https://kubernetes.io/docs/concepts/storage/volumes/#vsphere-csi-migration-complete (InTreePluginvSphereUnregister)

It is not clear for which components "CSIMigrationRBD" feature gate is intended.

https://kubernetes.io/docs/concepts/storage/volumes/#rbd-csi-migration

It is not clear for which components "SizeMemoryBackedVolumes" feature gate is intended.

https://kubernetes.io/docs/concepts/storage/volumes/#emptydir

P.S. I understand that you can enable every feature gate on every component, but that is not what this issue is about.

This issue related to https://github.com/kubernetes/website/issues/42127.

/language en

We don't have that information (as in: I believe that nobody has it, anywhere), so adding it would be a big undertaking.
If https://github.com/kubernetes/website/pull/41793 merges, we have a place to put that information, and we can look at incoming KEPs to find out what components new feature gates use. So we can get to a point where all feature gates that are still active have docs showing where you need to set them.
As I say, it's not a small piece of work.

I would say that the cloud-controller-manager is kinda deprecated and you should use a vendor specific cloud controller manager instead (in which case, the feature gates to use there are whatever that particular code wants to accept).

Also see https://github.com/kubernetes/website/issues/49134
/reopen

Also see https://github.com/kubernetes/website/issues/42102


SQS - "Error: Failed to get the current sub/segment from the context."

We're trying to implement X-Ray and it's causing issues accessing SQS. The code is running on an EC2 instance. I don't see any additional tips in the README, yet I am unable to make this work.
Sample code:
const aws = require('aws-sdk');
const xray = require('aws-xray-sdk');
const modified = xray.captureAWS(aws);
const sqs = new modified.SQS({
    region: 'us-east-1'
});
sqs.receiveMessage({
    QueueUrl: 'https://sqs.us-east-1.amazonaws.com/.....hidden...../.....hidden.....',
    VisibilityTimeout: 600
}, (err, response) => {
    if (err) {
        console.log('Error');
        console.log(err);
    } else {
        console.log('Success');
        console.log(response);
    }
});

Result:
/home/user/test-program/node_modules/aws-xray-sdk-core/lib/context_utils.js:21
        throw new Error(message);
        ^

Error: Failed to get the current sub/segment from the context.
    at Object.contextMissingRuntimeError [as contextMissing] (/home/user/test-program/node_modules/aws-xray-sdk-core/lib/context_utils.js:21:15)
    at Object.getSegment (/home/user/test-program/node_modules/aws-xray-sdk-core/lib/context_utils.js:92:45)
    at Object.resolveSegment (/home/user/test-program/node_modules/aws-xray-sdk-core/lib/context_utils.js:73:19)
    at features.constructor.captureAWSRequest [as customRequestHandler] (/home/user/test-program/node_modules/aws-xray-sdk-core/lib/patchers/aws_p.js:60:29)
    at features.constructor.addAllRequestListeners (/home/user/test-program/node_modules/aws-sdk/lib/service.js:279:34)
    at features.constructor.makeRequest (/home/takins5/user/test-program/node_modules/aws-sdk/lib/service.js:203:10)
    at features.constructor.svc.<computed> [as receiveMessage] (/home/user/test-program/node_modules/aws-sdk/lib/service.js:677:23)
    at Object.<anonymous> (/home/user/test-program/test.js:8:5)
    at Module._compile (internal/modules/cjs/loader.js:955:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)

Hi @fidian,
This problem is occurring because when you make a request with an instrumented AWS SDK client like yours, the X-Ray SDK attempts to automatically begin a subsegment to trace that SQS request. The X-Ray SDK expects a segment to be started before any subsegments are created. If there is no segment available, as in your case, it throws the error you see.
If you're using an express app and defining routes, the SDK will automatically create a segment for you within those defined routes. Otherwise, see our section on developing custom solutions to manually begin a segment, and then once you have begun the segment, you should be able to make instrumented AWS SDK requests. Please let us know if this resolves your issue.

I have added the following lines to my test program and it is still not working. I'm trying to follow the docs but am having a very difficult time with getting this to work. Searches on Google for people using X-Ray all seem to focus on using it as middleware. Sorry to be a pain, but could you help point me to what is wrong?
...
const modified = xray.captureAWS(aws);

// Begin added code
const segment = new xray.Segment('job-runner');
const ns = xray.getNamespace();
ns.run(() => {
    console.log('setSegment');
    xray.setSegment(segment);
});
// End added code

const sqs = new modified.SQS({
...

Running the test program still produces the same error during the call to SQS.

No problem, all you need to do is move your SQS requests inside the ns.run block. Something like:
const modified = xray.captureAWS(aws);

// Begin added code
const segment = new xray.Segment('job-runner');
const ns = xray.getNamespace();
ns.run(() => {
    console.log('setSegment');
    xray.setSegment(segment);
    const sqs = new modified.SQS({
        // config
    });
    sqs.receiveMessage(...);
    ....
    segment.close();
});
// End added code

That was the crucial bit I needed. Thank you for helping me out! I didn't get that impression from reading Ttis section of the documentation. I don't read anything that implies that my calls to AWS need to be within the namespace. Or maybe an example somewhere that doesn't rely on middleware?
Anyway, you've been extremely helpful and quick with your responses even though the issue tracker isn't a great spot for questions. Thank you for your assistance!


Up to 0.1.4

Versioning for https://github.com/peterhurford/checkr/pull/31

[Current coverage][cc-pull] is 99.45%

No coverage report found for master at 2814b1f.

Powered by Codecov. Last updated by [2814b1f...0f6d97c][cc-compare]
[cc-base-branch]: https://codecov.io/gh/peterhurford/checkr/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/peterhurford/checkr/compare/2814b1fa4ddf041307c13753145c1cafc3c8e5e9...0f6d97cca01da9eb44a425d201d1d94e6d31c579?src=pr
[cc-pull]: https://codecov.io/gh/peterhurford/checkr/pull/32?src=pr


Should the external links check perform HEAD requests?

While I understand HEAD requests allow speeding up the checks, and the 405 HTTP response is handled, many web servers don't handle HEAD requests, and won't send a 405 either.
This basically makes the elinks check useless, as it can't be relied upon.
Steps to reproduce

Create a page with a link to https://redis.io/topics/protocol inside it.
Run nanoc check elinks

Expected behavior
This page does exist, and if users were to click the link, they wouldn't get a 404. The test should therefore not fail,
Actual behavior
Because the server doesn't handle HEAD requests, and doesn't return 405, the test fails, when the page actually exists.
Fixing this
I'm absolutely fine opening a PR fixing this, either by entirely removing the HEAD request, or any other solution proposed.
I want to make sure this kind of change would be approved though. And a quick search didn't show any other similar issue.

Makes sense!
An alternative could be to perform a HEAD request and fall back to GET if the HEAD returns a 404, but I don’t see the benefit of doing that over doing a GET in the first place.
I’ve opened PR #1179 to fix this.

Awesome!
If I may make another suggestion, how about setting an user agent?
Like nanoc/link_checker?

@dmathieu I don’t think that setting a custom user agent would bring much. Do you have a use case for it?

Not specifically. It's just a way to be a better citizen.
Thanks for the HEAD fix! 🌷


implement Avail DA

implement Avail as an option for data availability

Ethereum 4844 DA support should be added with this PR - #7. Adding new DA layers should be very similar to this approach. The steps would be

Create a new crate inside da_clients

Implement the DaClient trait from da-client-interface

publish_state_diff: push the data on chain and return the txn_hash
verify_inclusion: taking the txn_hash as input, check if the txn has been finalized on chain

@apoorvsadana Can I take this issue?

Hey @0x5ea000000
Someone else is also working on this issue. Closing this for now.
Thanks


Interface typecasting and/or creating an instance from PropertyInfo.PropertyType

Okay, this is a little complicated.  The following code will fail on the Console WriteLine of the ItemCapacity (ItemArray.Length -> ItemArray is null).
If you swap the commented out lines on either the ListType assignment or the List assignment, it works correctly.
Maybe there are two issues?  The casting to an interface and the creating an instance from the PropertyInfo.PropertyType when it is a type with generic parameters?
  static class Program
  {
    static void Main(string[] args)
    {
      var StorageType = typeof(DataStorage);

      var ListType = StorageType.GetProperty("List").PropertyType;
      //var ListType = typeof(DataList<>).MakeGenericType(typeof(DataItem));

      //var List = (DataList<DataItem>)Activator.CreateInstance(ListType, 1);
      var List = (IDataList)Activator.CreateInstance(ListType, 1);

      Console.WriteLine(List.ItemCapacity);
    }
  }

  public class DataStorage
  {
    public DataList<DataItem> List { get; set; }
  }

  public interface IDataList
  {
    int ItemCapacity { get; }
  }

  public class DataList<T> : IDataList
  {
    public DataList(int Capacity)
    {
      this.ItemArray = new T[Capacity];
    }

    public int ItemCapacity
    {
      get { return ItemArray.Length; }
    }

    private T[] ItemArray;
  }

  public class DataItem
  {
  }

I don't think the interface typecast could be causing this, it's probably a bug in Activator. But I'm not sure.

Problem is inside Activator (or probably in object public interface creating).
In JSIL.CreateInstanceOfType$CacheMiss, that builds type constructor, passed "_ctor" as a constructor name. Constructor with "_ctor" key is Object..ctor, when DataList<DataItem> ctor is under _ctor$30=void key.
Have not yet looked what will be if uncomment commented lines.

Suppose that now Activator will be broken for constructors with more then 0 arguments :)

Yeah, I don't think I ever tested it with multiple arguments.

@callanh, as I'm not sure that anybody will fix it soon, I can suggest you try to create object using constructor resolved through reflection as a workaround (I hope it will work).

@iskiselev and @kg, in trying to find a workaround, I've discovered that the Activator is not calling the constructor with 0 arguments either.
Add this constructor to DataList and remove the second argument '1' from the call to CreateInstance.  This case also fails with 'ItemArray' is null.
    public DataList()
    {
      this.ItemArray = new T[0];
    }

I'm wondering if Activator is broken for types with generic parameters, where you got the type from reflection. eg. PropertyInfo.PropertyType?

By the way, I can confirm that invoking the constructor through reflection is a viable workaround.

There is at least one difference in behaviour between Activator.CreateInstance and instantiating through the default constructor in C#.
In particular this struct can be instantiated with Activator.CreateInstance but there is no default constructor.
  public struct Clock : IComparable
  {
    private Clock(long Turns)
    {
      this.Turns = Turns;
    }


A browser extension is required (for video downloading).

A browser extension is required (for video downloading like IDM).

That would be perfect, to be honest. Hope to see it added sooner or later.

https://github.com/gautamkrishnar/motrix-webextension

https://github.com/gautamkrishnar/motrix-webextension


Setting labels on a file system without Xattr support shouldn't retur…

…n an error
If we mount a volume into a container that does not support Xattrs (SELinux), we
need to check for ENOTSUP and not return an error
Signed-off-by: Dan Walsh<EMAIL_ADDRESS>

This is an attempt to fix
https://github.com/docker/docker/issues/18005

I don't think this fixes the mentioned issue, as the volume path may not even exist at this point.
It also seems like we should error out here since the user is explicitly asking for the relabel and it can't relabel it.

Your right. never mind.  Where it the volume setxattr happening...


 I understand because the DUnitXIDEExpert290 package is already installed.
But which package is better ? the former or the later ?

Since you are here, use the one on github - removed the one supplied with the IDE.


Modified Mesos and Docker configuration in the Agent.

Instead of relying on the information sent by the Master, we create
Mesos and Docker networks based on the configuration given by the
operator.

The branch name DCOS-11982-HACK gives me great confidence 😛 .
Looks reasonable to me.

@jieyu @kaysoky added a unit-test to test the behavior of the agent when its network config is changed in between agent restarts.

Merged this.

commit 3d185b433c999a448f5648876b498cc2537ba554
Author: Avinash Sridharan<EMAIL_ADDRESS>Date:   Fri Dec 9 22:16:24 2016 +0000
Modified Mesos and Docker configuration in the Agent.

Instead of relying on the information sent by the Master, we create
Mesos and Docker networks based on the configuration given by the
operator.

With this change the semantics of Master Agent interaction change to
the overlay configuration being sent to the agent being treated as a
request that the agent will try to comply to as long as the operator
allows the agent to apply the configuration requested by the Master.

commit 1073246c3dd9a9098ad79918048543a79ef22520
Author: Avinash Sridharan<EMAIL_ADDRESS>Date:   Sat Dec 10 01:24:27 2016 +0000
Added unit-test to verify behavior of `AgentNetworkConfig`.

The test verifies that when agent is restarted with an
`AgentNetworkConfig` different than the one with which it has
registered with the Master, though the Master might send an overlay
configuration that is contrary to what the `AgentNetworkConfig`
demands (E.g., `AgentNetworkConfig` has `mesos_bridge` and
`docker_bridge` disabled but Master sends an overlay configuration
with both enabled) the agent always honors the configuration specified
in `AgentNetworkConfig` over what the Master sends.


Sampling strategy for boosting

Add a first sampling strategy as uniform sampling is really slow
@deerzq

LGTM!


Out of the box cross-platform PE data edition for Windows exports

Operating system or device, Godot version, GPU Model and driver (if graphics related):
All systems who can run the Godot editor, current master branch (3fd1c0c)
Issue description:
We now have the possibility to edit PE data for Windows binaries using the Windows-specific rcedit tool (#14437), which thankfully works fine via WINE and can be used from other systems too.
It would be cool however to have out of the box support for editing PE data from any platform when exporting Windows (and UWP?) binaries, without the need to download and set an external platform-specific tool.
This is a follow-up to #1211 which has some information about that topic.
In the past we have tried pe_bliss (#2518), which seemed to do what we need, but also came with a lot of bloat and introduced various issues, so it was finally reverted. If there aren't any alternatives, an interested dev could try to fork pe_bliss to make it more lightweight and friendly to a C-with-classes project like Godot.

Can someone either close this OR assign this to milestone 4.0 just like this and this?


remove the email logo

Description

Related Issue

Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

test environment: locally via the inbucket container

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

:boom: Acceptance test wopiValidatorTests-ocis failed. Further test are cancelled...