[BUG] Cannot edit storage class when adding volume on edit VM page

Describe the bug

Cannot edit storage class when adding volume on edit VM page
To Reproduce
Steps to reproduce the behavior:

Go to edit VM page
Go volume tab
Click the "Add Volume" button

Expected behavior

"Storage class" should be editable
Support bundle

Environment

Harvester ISO version:
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

Thanks for this fix @n313893254  - this looks great :smile: :+1:
Validated on Harvester Version: master-61a6124a-head


Information extraction when bounding boxes are not present (prediction on unseen data)

Hi,
I was just exploring this model and found it useful for information extraction from scanned images. I need to know how can we make predictions on unlabelled data after we have trained the model?
By unlabelled data, I mean images where we do not have bounding box details.
I tried by not passing the 'boxes_and_transcripts_folder' param while calling the test script but then the model made no predictions at all which is strange.
Thanks in advance.

@wenwenyu It would be really great if you can help me with this.

Hi,
The bounding box and transcripts of unlabelled data can be predicted by the OCR system which means you need to train a text detection and recognition model. This is out of the scope of this paper.
Hope it can help you.

Thanks @wenwenyu for your reply.


fix fix str_to_date with specific format

Proposed changes
pick from
https://github.com/apache/doris/pull/22981

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

run buildall

run buildall

run p0


Examples of Deployment that can be done using Helm Chart

We can add examples of different values for different kinds of deployment for OpenSearch stack. It will be great for end users to directly edit those example deployment values for their use-case/purpose.

@TheAlgo Are we still planning to create a "monolithic" stack chart that brings all the components together with general options:

Master Nodes
Hot Data Nodes
Dashboards
Warm Data Nodes

If so, I think this issue has to wait until some of the deps are ready

Initially this was the thought, once we have separate chart for OpenSearch and OpenSearch Dashboards, we can have one which deploys the OpenSearch stack(OpenSearch, OpenSearch Dashboards, Logstash(maybe)) which the most commonly used features. But I will leave it up to @peterzhuamazon and @dblock to take a call on it. I will be happy to contribute to the same as well.

@TheAlgo I'd recommend avoiding third party options as I wouldn't be surprised if Fluent was more often used over Logstash. So I imagine giving people their choice for tailing etc. Should be left to them.
Sounds good though.

@peterzhuamazon @dblock instead of Logstash if we can have dataprepper. Opinions?

Initially this was the thought, once we have separate chart for OpenSearch and OpenSearch Dashboards, we can have one which deploys the OpenSearch stack(OpenSearch, OpenSearch Dashboards, Logstash(maybe)) which the most commonly used features. But I will leave it up to @peterzhuamazon and @dblock to take a call on it. I will be happy to contribute to the same as well.

@TheAlgo I'm still of the opinion you provide an all or nothing approach here.
Either we don't include any OR we include dependencies for all supported third party options as conditions that can be enabled and disabled.

Fluentd
Fluentbit
DataPrepper
Logstash
Pretty sure Grafana agent works too

My opinion is adding support for them all. Similar to how Jaeger Tracing has option for multiple backend storage options:
https://github.com/jaegertracing/helm-charts/blob/main/charts/jaeger/values.yaml
https://github.com/jaegertracing/helm-charts/blob/main/charts/jaeger/Chart.yaml
It complicates the chart, but means people can just set a component to enabled: true and be on their way.

@TheAlgo @DandyDeveloper
We have logstash working with opensearch now:
https://hub.docker.com/r/opensearchproject/logstash-oss-with-opensearch-output-plugin/tags
https://rubygems.org/gems/logstash-output-opensearch/

We can create charts to cater certain use cases for the end-users . This particular chart can be helpful for certain group of users.

We can create charts to cater certain use cases for the end-users . For example this particular chart can be helpful for certain group of users to want to set up a logging stack.

@TheAlgo we can probably contact the maintainer of that chart for help?

@peterzhuamazon @TheAlgo Yes, per my previous comment, I think it's good if we do something like:
Chart.yaml
....
dependencies:
- name: fluentd
  repository: xyz
  condition: fluentd.enabled
- name: logstash
  repository: xyz
  condition: logstash.enabled
... Other supported mechanisms

## Enable fluentd tailing on container logs and ship to OpenSearch
## Dependency chart and corresponding values can be found here: xyz (Repo link)
fluentd:
  enabled: false
  .... Defaults needed to have fluentd work with our chart
## Enable Logstash tailing on container logs and ship to OpenSearch
## Dependency chart and corresponding values can be found here: xyz (Repo link)
logstash:
  enabled: false
  .... Defaults needed to have fluentd work with our chart

Then have a conditional check to make sure there's no dupes OR just allow the child chart to manage resource deployment and if the user decides to enable 2, so be it.
This is effectively how I deploy my stack in the OpenDistro implementation I'm running in production. (fluentbit & fluentd)

@peterzhuamazon @TheAlgo Yes, per my previous comment, I think it's good if we do something like:
Chart.yaml
....
dependencies:
- name: fluentd
  repository: xyz
  condition: fluentd.enabled
- name: logstash
  repository: xyz
  condition: logstash.enabled
... Other supported mechanisms

Values.yaml
## Enable fluentd tailing on container logs and ship to OpenSearch
## Dependency chart and corresponding values can be found here: xyz (Repo link)
fluentd:
  enabled: false
  .... Defaults needed to have fluentd work with our chart
## Enable Logstash tailing on container logs and ship to OpenSearch
## Dependency chart and corresponding values can be found here: xyz (Repo link)
logstash:
  enabled: false
  .... Defaults needed to have fluentd work with our chart

Then have a conditional check to make sure there's no dupes OR just allow the child chart to manage resource deployment and if the user decides to enable 2, so be it.
This is effectively how I deploy my stack in the OpenDistro implementation I'm running in production. (fluentbit & fluentd)

@DandyDeveloper I will be happy to help and contribute in case we want a chart something like this in our dedicated helm chart repository.

We can create charts to cater certain use cases for the end-users . For example this particular chart can be helpful for certain group of users to want to set up a logging stack.

@TheAlgo we can probably contact the maintainer of that chart for help?

@peterzhuamazon  This sounds good. I see this project is also listed in the community projects page


Unknown Service.Method /bin.Biz/Signal

Your environment.

Version

pion/ion-app-web: c7e9f9
pion/ion: dcf4f1a

Browser: 95.0.4638.69（Official Build） （x86_64）
Other Information - N/A

What did you do?

clone pion/ion repo and execute docker-compose up
clone pion/ion-app-web repo and execute npm i && npm start
Open http://localhost:8080
Enter Room Id and Display Name then click Join

What did you expect?
Expected to join the room.
What happened?
Failed to join the room.
As I checked Chrome DevTools, Signal failed with the following error message.

Unknown Service.Method /bin.Biz/Signal

pls try new version


Add Trigger Campaign Functionality

This PR adds the API trigger for campaigns as stated here: https://customer.io/docs/api/#apibroadcast_trigger

Great job!


Create de_DE.lang

Looks good, will merge when I can edit the readme to add you as a translator, too!

Commit 3f081f27ceaaf823c50a481544db3dede3eef12e removed the "rows" and added a "size" setting instead. (Also the category translation key has been removed.) Please take a look at the new language file and update yours accordingly. Thank you!

I'm getting ready for the next release. Could you perhaps look at updating this PR again?

Neat! ❤


Allow to map directly from JSON string

Fixes #43

Closed in favour of #46.

I'm happy, it's my first successful open source contribution


Add support to first/last aggregators for numeric types during ingestion

Fixes #10702
Description
This PR fixes #10702 by adding support to doubleFirst/floatFirst/longFirst and doubleLast/floatLast/longLast during ingestion phase. And also reverts #10794 to bring back the UI.
The implementation is inspired by current stringFirst/stringLast implementation, so the code looks like similar. But this PR does not refactor current stringFirst/stringLast implementation to share the code with double/float/long. That might be done in the future.

Key changed/added classes in this PR

AbstractSerializableLongObjectPairSerde is provided to share serialization code for type of long/double/float
GenericFirstAggregateCombiner is provided to share first aggregator code for type of long/double/float
GenericLastAggregateCombiner is provided to share last aggregator code for type of long/double/float

What's not included in this PR

stringFirst/stringLast should also share the three base classes listed above, I will open a new PR to do this to keep changes in this PR as less as possible.
SQL query on re-indexed columns with double/float/long first and last aggregators WON'T work. This involves some changes in complex type handling which might be better in another PR.

Test Scenario
This PR contains UT and IT cases to cover all doubleFirst/doubleLast, floatFirst/floatLast, longFirst/longLast aggregators, including:

buffer aggregation
aggregate combiner
serdes
aggregation during index
aggregation during re-index
native query

This PR has:

[X] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[X] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[X] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[X] added integration tests.
[X] been tested in a test Druid cluster.

One tricky problem left is that first/last aggregators is not supported by SQL query on reindexed long/float/double columns while these aggregators work well in a native query.
The type of reindexed double/float/long/string first/last columns are marked as COMPLEX in schema, and the underlying type is lost when the type is converted into RelDataType.
https://github.com/apache/druid/blob/16acd6686a337fc9a12e9aeda443fca973bdc625/sql/src/main/java/org/apache/druid/sql/calcite/table/RowSignatures.java#L135
Since the underlying data type of the column is lost during SQL planning,  current EarliestLatestReturnTypeInference also is not able to infer correct return type, and is unable to create correct type of aggregator for double/float/long.
One way I can come up with is to define some macros such as double_latest for different data types at the SQL layer.
@gianm @clintropolis Do you have any other suggestions ?

One way I can come up with is to define some macros such as double_latest for different data types at the SQL layer.
@gianm @clintropolis Do you have any other suggestions ?

Hmm, so what I have had in mind to solve this is to be able to determine whether a RowSignature should be "finalized" or not in terms of the aggregator types. #9638 added some of the pieces needed for this (getFinalizedType, etc) and touches on this idea in the PR description, I just haven't yet got back this core refactoring work, or quite had time to fully think through how to determine when we need the 'finalized' signature or not.
#10277 also added tracking of the "name" of the complex type on ColumnCapabilities (which typically is what populates the RowSignature) so that is potentially available to give greater detail than ValueType.COMPLEX, but I think the finalized type would be the useful information here.
That said, I haven't had a look at this PR at all yet. I will try to get to it sometime soon, maybe I will have some ideas while looking over the code.

Hi @clintropolis , Thanks for your suggestion. I'll try to solve it.

Hi @clintropolis , Thanks for your suggestion. I'll try to solve it.

Depending on how big of a change this is, it might be worth splitting out a separate PR to go in before this one. I'll try to think about this a bit as well.

Hmm, so what I have had in mind to solve this is to be able to determine whether a RowSignature should be "finalized" or not in terms of the aggregator types. #9638 added some of the pieces needed for this (getFinalizedType, etc) and touches on this idea in the PR description, I just haven't yet got back this core refactoring work, or quite had time to fully think through how to determine when we need the 'finalized' signature or not.
#10277 also added tracking of the "name" of the complex type on ColumnCapabilities (which typically is what populates the RowSignature) so that is potentially available to give greater detail than ValueType.COMPLEX, but I think the finalized type would be the useful information here.
That said, I haven't had a look at this PR at all yet. I will try to get to it sometime soon, maybe I will have some ideas while looking over the code.

The name of complex type has been set in first/last aggregator
https://github.com/apache/druid/pull/10949/files#diff-9fedc71bcede0adcbb1deadbef33e9e1de175ee11209eb4d5d676580104f2c03R231
And I checked the code about how RowSignature works today, and found that there's no way to get that name from RowSignature because when RowSignature is instantiated , that name is not passed to RowSignature
https://github.com/apache/druid/blob/51d2c61f1cd03f2d3fe396c5bb4738293dc92107/sql/src/main/java/org/apache/druid/sql/calcite/schema/DruidSchema.java#L698
So, is it reasonable to make some changes here to pass the type name as well as its value type to RowSignature if its value type is COMPLEX ?

Hi @clintropolis @suneet-s  , Could you review this PR at any time you're convenient ? Since this PR is a little large, I think the SQL problem could be separated in another PR.

@FrankChen021 thanks for bringing this back to the top of my radar. I will look through this over the next week or so.

@FrankChen021 To help with reviewing this PR, could you update the PR description to include some notes how you chose to implement the solution for this. For example, it looks like the AbstractSerializablePairSerde was based off the SerializablePairLongStringSerde.
Also, it would help if you included a description of the different scenarios you tested, and known unsupported conditions - like your comment about first last aggregators not working in SQL queries.

@suneet-s Thanks for your review. I will address all the comments you left and update this PR later this day.

@FrankChen021 To help with reviewing this PR, could you update the PR description to include some notes how you chose to implement the solution for this. For example, it looks like the AbstractSerializablePairSerde was based off the SerializablePairLongStringSerde.
Also, it would help if you included a description of the different scenarios you tested, and known unsupported conditions - like your comment about first last aggregators not working in SQL queries.

Description of this PR has been updated. Let me know if there's anything left.

@FrankChen021 To help with reviewing this PR, could you update the PR description to include some notes how you chose to implement the solution for this. For example, it looks like the AbstractSerializablePairSerde was based off the SerializablePairLongStringSerde.
Also, it would help if you included a description of the different scenarios you tested, and known unsupported conditions - like your comment about first last aggregators not working in SQL queries.

Description of this PR has been updated. Let me know if there's anything left.

Thanks @FrankChen021 I will take a look again this week!

SQL query on re-indexed columns with double/float/long first and last aggregators WON'T work. This involves some changes in complex type handling which might be better in another PR.

What happens when a user issues the EARLIEST(expr, maxBytesPerString) function on a longFirst column - do we expect that it will fail? Is the error message in this case clear?
I'm asking because it looks like #10332 added handling of complex type columns, which used to be ok because stringFirst/Last was the only type of complex column. But now that we've introduced these column types, the expected behavior is less clear. Perhaps you can add some tests to CalciteQueryTest to validate the behavior that we want users to see when they issue sql queries on these column types.

SQL query on re-indexed columns with double/float/long first and last aggregators WON'T work. This involves some changes in complex type handling which might be better in another PR.

What happens when a user issues the EARLIEST(expr, maxBytesPerString) function on a longFirst column - do we expect that it will fail? Is the error message in this case clear?
I'm asking because it looks like #10332 added handling of complex type columns, which used to be ok because stringFirst/Last was the only type of complex column. But now that we've introduced these column types, the expected behavior is less clear. Perhaps you can add some tests to CalciteQueryTest to validate the behavior that we want users to see when they issue sql queries on these column types.

EARLIEST/LATEST both work well for stringFirst/Last columns. They also work for none double/float/longFirst/Last columns.
For double/long/floatFirst/Last columns, following exception message is returned
Error: Plan validation failed

org.apache.calcite.runtime.CalciteContextException: From line 3, column 3 to line 3, column 24: Cannot apply 'EARLIEST' to arguments of type 'EARLIEST(<OTHER>)'. Supported form(s): 'EARLIEST(<NUMERIC>)' 'EARLIEST(<BOOLEAN>)' 'EARLIEST(expr, maxBytesPerString)'

org.apache.calcite.tools.ValidationException

@FrankChen021 - have you run any performance tests/benchmark for ingestion time rollup? That will be handy to rule out any perf bug.

@FrankChen021 - have you run any performance tests/benchmark for ingestion time rollup? That will be handy to rule out any perf bug.

I have not. But I will. Thanks for pointing out this.

@FrankChen021 - This is a useful capability. would you be able to take this to completion? Perf tests will be nice but they need not block this PR.

Hi @abhishekagarwal87 , the changes in this PR was previously used in our team. I'm not working on that project now, so I don't have large chunk of time to resolve the conflicts.
Also SQL functions are not supported on rollup first/last column, this is also a restriction that needs to be resolved. (See comment above https://github.com/apache/druid/pull/10949#issuecomment-819423526) At the time this PR was created, it was not able to do that. So we use native query to bypass this problem.
It would be great if you can pick up this PR.


Adds support for node affinity

nodeSelector:
  nodetype: cache

nodeAffinity:
  requiredDuringSchedulingIgnoredDuringExecution:
    nodeSelectorTerms:
    - matchExpressions:
      - key: karpenter.sh/capacity-type
        operator: In
        values:
        - spot
  preferredDuringSchedulingIgnoredDuringExecution:
    - weight: 50
      preference:
        matchExpressions:
          - key: nodetype
            operator: In
            values:
              - cache

Thanks @digiserg


Styled Components injects forwardRef in every component generating unecessary overhead

Styled component injects forwardRef into every component, forwardRef adds an overhead and has considerably more impact on a Component's render time and JS thread time compared to a regular component, causing FPS drops, tha has been widely discussed here.
I'm wondering if the styled-components' team is aware of that and if it'd be of your interest if I were to open a PR proposing removing forwardRef from the default implementation, making it optional.

the issue you linked is over 2 years old - is it still relevant?

@jantimon  After doing some deeper digging I believe this is still relevant.. React's forwardRef uses Object.defineProperty internally, which has been reported as slower than other solutions many times in the past, even though devs assumed it to be "fixed" it still is definetely slower solution. Those extra MS can and will impact greatly for hundreds or thousands of styled elements being rendered at a given time on a screen, as well as slowing down first render times.
Speed of Object.defineProperty vs a straight setter can be seen on this example here.

the code you mentioned is only active during development - or did I miss something?
did you do any benchmarks how much slower rendering 1000 forward ref vs 1000 normal components?
would be quite interesting to understand the real impact :)

Using a sample of 10k children
Regular Component:

Forward Ref Component:

Styled:

Those results are interesting, though not for the reason I imagined styled-components seems to add significant overhead time to render time to components. Nonetheless forwardRef does not have the impact as I thought, as you mentioned it did have the defineProperty isn't called inside forwadRef on production mode, but it is called inside styled components and could be one of the reasons for that impact on render time.
Devtools profiles: profiles.zip
Code used:
import React, { forwardRef, ReactNode } from 'react';
import logo from './logo.svg';
import './App.css';
import styled from 'styled-components';

const array = new Array(10000).fill(0);

function Div({children}: {children: ReactNode} ) {
  return
{children}

}

const FowardRef = forwardRef((props: {children: ReactNode}, ref) =>
{props.children}
);

const Styled = styled.div``;

function App() {
  return (

        {array.map((_,index) => )}

  );
}

export default App;


[Snyk] Fix for 5 vulnerable dependencies

Description
This PR fixes one or more vulnerable packages in the maven dependencies of this project.
See the Snyk test report for more details.
Snyk Project: navikt/syfoperson:pom.xml
Snyk Organization<EMAIL_ADDRESS>Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

pom.xml

Vulnerabilities that will be fixed
With an upgrade:

pom.xml

<EMAIL_ADDRESS>><EMAIL_ADDRESS>
XML External Entity (XXE) Injection

<EMAIL_ADDRESS>><EMAIL_ADDRESS>
Deserialization of Untrusted Data
Denial of Service (DoS)
Remote Code Execution
Cross-site Scripting (XSS)

You can read more about Snyk's upgrade and patch logic in Snyk's documentation.
Check the changes in this PR to ensure they won't cause issues with your project.
Stay secure,
The Snyk team
Note: You are seeing this because you or someone else with access to this repository has authorised Snyk to open Fix PRs. To review the settings for this Snyk project please go to the project settings page.

Updated PR


incorrect parse of certain addr

Hi!
I was checking out libpostal, and saw something that could be improved.

My country is
israel

Here's how I'm using libpostal
parsing free text strings

Here's what I did
tried to parse 2710 N. RIDGEWAY, CHICAGO, IL, 60647-1134, US
or
2710 SOUTH RIDGEWAY, CHICAGO, IL, 60647-1134, US

Here's what I got
    "street": "n.",
    "neighbourhood": "ridgeway",

in the first case,
"street": "south",
"neighbourhood": "ridgeway",
in the second case
Here's what I was expecting

street is n. ridgeway or s. ridgeway, no neighbourhood
For parsing issues, please answer "yes" or "no" to all that apply.

Does the input address exist in OpenStreetMap?
yes
https://www.openstreetmap.org/way/163893117
https://www.openstreetmap.org/way/234609894
Do all the toponyms exist in OSM (city, state, region names, etc.)?
yes
If the address uses a rare/uncommon format, does changing the order of the fields yield the correct result?
didnt try all combos, but given order is most common
If the address does not contain city, region, etc., does adding those fields to the input improve the result?
na
If the address contains apartment/floor/sub-building information or uncommon formatting, does removing that help? Is there any minimum form of the address that gets the right parse?
na

Here's what I think could be improved

'north' or 'south' as street name can prob. be ruled out (or assigned low prob. ) with heuristic when considering  parsing of street from input string

'north' or 'south' as street name can prob. be ruled out (or assigned low prob. ) with heuristic when considering parsing of street from input string

Certainly cannot be ruled out :)
https://en.wikipedia.org/wiki/North_Avenue_(Atlanta)

what i meant was, the cardinal directions alone shouldnt be assigned street as occurred above
(where 'north' or 'south' was listed as street)
north avenue , north ridgeway, e. ridgeway  and the like should all be taken as streets
if there's another way to fix it i'm keen to hear


PFUser logInWithUsernameInBackground not returning the latest User record data

PFUser logInWithUsernameInBackground is not returning the current PFUser data consistently sometimes.
[PFUser logInWithUsernameInBackground:email password:password block:^(PFUser *user, NSError *error) {
            if (!error) {
                resolve(user);
            } else {
                resolve(error);
            }
        }];

I have a column "userStatus" to store the user status. When I changed it in Parse Browser and login again. Sometimes it still shows the old data. Does Parse always return the current User record in the block callback?
It was working quite well in the last 9 months until recently on Tuesday 1st Sept, we saw some unusual behaviours in the Parse. We have to ask our new signup users to delete the app and download it again from AppStore in order to get the new changes in User table.
Is anything changed recently in the backend?
Thanks in advance !

Hmm. This sounds very strange. To the best of my knowledge - nothing changed. I suggest filing a FB Bug Tool issue on https://parse.com/help since we are continuing to use it for tracking backend issues.


Add capella and deneb types to pretty-print command

PR Description

Add some Capella/Deneb types to pretty-print command.
Also added BuilderBid type

Fixed Issue(s)
fixes #7800
Documentation

[X] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[X] I thought about adding a changelog entry, and added one if I deemed necessary.

I'd remove "fixes" in description, since we realized this is not related


Bugfix: encode special characters in <index.html>

Encode special characters in <index.html>. Without this modification, when you try to connect to a network with special character in SSID or password it does not work.

@LucasSBS thanks for your PR, this should got fixed after https://github.com/espressif/esp-at/commit/8722285908f61ff89a3f214c5967978f434a26e5

We assume this worked for you, and will close it. If that's not the case, please open another github pull request.


BUG: shap.plots.bar(shap_values) TypeError

Issue Description
when using barplot function from shap a TypeError occurs when calling line 260 ax.set_yticks.
set_ticks has no attribute fontsize.
Minimal Reproducible Example
import shap
shap.initjs()

model = xg.XGBRegressor()
model.fit(X_train, y_train)
explainer = shap.Explainer(model)
shap_values = explainer(X_train)

shap.plots.bar(shap_values)

Traceback
Traceback (most recent call last)
/var/folders/pk/yjvh2jtj15ldhmcxb6_ss_ch0000gn/T/ipykernel_11569/768057057.py in <module>
----> 1 shap.plots.bar(shap_values, ax=None)

/opt/anaconda3/lib/python3.9/site-packages/shap/plots/_bar.py in bar(shap_values, max_display, order, clustering, clustering_cutoff, show_data, ax, show)
    258
    259     # draw the yticks (the 1e-8 is so matplotlib 3.3 doesn't try and collapse the ticks)
--> 260     ax.set_yticks(list(y_pos) + list(y_pos + 1e-8), yticklabels + [t.split('=')[-1] for t in yticklabels], fontsize=13)
    261
    262     xlen = ax.get_xlim()[1] - ax.get_xlim()[0]

/opt/anaconda3/lib/python3.9/site-packages/matplotlib/axes/_base.py in wrapper(self, *args, **kwargs)
     71
     72         def wrapper(self, *args, **kwargs):
---> 73             return get_method(self)(*args, **kwargs)
     74
     75         wrapper.__module__ = owner.__module__

TypeError: set_ticks() got an unexpected keyword argument 'fontsize'

Expected Behavior
No response
Bug report checklist

[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest release of shap.
[ ] I have confirmed this bug exists on the master branch of shap.
[ ] I'd be interested in making a PR to fix this bug

Installed Versions
0.45.1

hi @JeroenWalchenbach , your example is not reproducible. (X_train, y_train are not defined).
This works, for example:
import shap
import xgboost as xg
shap.initjs()

X_train, y_train = shap.datasets.adult(n_points=500)
model = xg.XGBRegressor()
model.fit(X_train, y_train)
explainer = shap.Explainer(model)
shap_values = explainer(X_train)

shap.plots.bar(shap_values)

So it probably has something to do with how your data is defined.

I tested the example from @thatlittleboy
import shap
import xgboost as xg
shap.initjs()

X_train, y_train = shap.datasets.adult(n_points=500)
model = xg.XGBRegressor()
model.fit(X_train, y_train)
explainer = shap.Explainer(model)
shap_values = explainer(X_train)

shap.plots.bar(shap_values)

on different Matplotlib versions. It works with matplotlib >= 3.5.0 and with <3.5.0 it does not work.


Logi M585 bluetooth mouse disconnects

I'm using a Logi M585 bluetooth mouse with my snes and it works perfectly, but passed 30 sec (always), it stops working, so I have to reset my mouse pairing mode and starts working again. I'm using the last firmware (1.7.3). Other devices work OK, but 8bitdo controllers might fail sometimes.

If you can, disconnect the 5V from snes and plug the USB to a PC and get the logs:
https://github.com/darthcloud/BlueRetro/wiki/Getting-BlueRetro-debug-logs-via-Serial-port-Windows-10
Press reset (EN) on the ESP32 so I can see the boot logs, then connect the Mouse and then wait until the mouse disconnect. Save full log to a txt files and upload here by drag & drop.

awesome, I will. Do I have to keep the blueretro device connected into the snes while I do all of this?

You don't if you can reproduce without it.

OK, what about the 3.3v that feed the 74AHCT125N controllers? I think they still have to be connected, right?

leave everything as-is just don't plug it into the snes.

LOG.txt

Thanks, I think the mouse doesn't like when pairing mode ends. I'll look later what I can do.

@darthcloud thank you

any luck on this issue? with other bt mouses are supported?

Sorry for not getting back to you on this.
Try this v1.9 beta:
https://github.com/darthcloud/BlueRetro/actions/runs/6437347093
I moved the end of pairing mode to be earlier.

thanks! I'm gonna check it out 👍🏻

I just tested it but it's the same, after 30 seconds, mouse stops responding, turning mouse off and on makes it work again, and 30 seconds later stops, and so. Any other bluetooth mouse I could use? I tried using a cheap chinese bt mouse from AliExpress, it never pairs 😂 but it works fine with windows.

I use Logitech MX Master 2S

So I bought this mouse M585 and it work flawless in v1.9!
Can you try v1.9 with it?
I used it non stop 5 min no issue. Then left it idle 1 min, and it worked right away when i touch it again.
If it still doesn't work for you maybe check with the Logi tool on Windows if you can somehow update the mouse?
I got another Logi mouse, the M720 that behave exactly like you said, I'll try to update that one later and see.

Awesome! Yes, I tried it and it kept stopping again, then I used my pc as a middleman bluetooth mouse with a tool called across center, and it worked great. https://www.acrosscenter.com/

Any updates on this Darthcloud. I recently got the M720 and it does the same thing as DigiDwrf and you have mentioned.
Thanks,

I'm also having this problem with an onn. mouse I got from walmart. I've tried a Steelseries Aerox 9 (pairs, doesn't seem to provide input), the Across Center software (pairs, only keyboard registers input and seems to be stuck drifting to the left), and this "onn. 5-Button Wireless Bluetooth Ambidextrous Mouse, USB-A Nano Receiver, Black" mouse. I'm using the Bitfunx 4-port N64 adapter from Amazon, it has its own bootleg FW bin, but the official HW1 can be flashed to it and pair at least one controller. This is a livable compromise as I would like to play 64DD software with a mouse more than I really need to play N64 with an Xbox controller. I can upload a Putty log for it if it seems like something that can be fixed, or a compatibility list would be awesome as I'm really not trying to spend a ton of money on a mouse I'm not otherwise going to use a lot (hence not buying an actual N64 mouse). Any assistance is much appreciated.
Thank you.


Back repo as GDExtension

[ ] Implement AnimationNodeExtension in godot
[ ] Fix builds of MMAnimationNode
[x] Fix CI

https://github.com/godotengine/godot-cpp-template is useful!

@GuilhermeGSousa I propose we go in this order:
AnimationNodeExtension
There is a race to get this into the Godot Engine 4.4 version.
Bone features
While we wait, we can develop the bone feature.
godot-motion-matching GDExtension
When AnimationNodeExtension is in the Godot Engine master branch, we can work on this.

@fire I have some work done in godot, I needed these changes to be able to start testing things
https://github.com/godotengine/godot/pull/99181

Which version of Godot 4 will work with this GDectension?

Whichever version has this change
https://github.com/godotengine/godot/pull/99181
so probably 4.5? I dunno

Not to be unfair to you, if you could provide windows exe of this version, we could continue to follow your demo. Just a feedback


Android webview loading is slow.

Can you make it fast?
I using Expo SDK33.

I meet the same problem

Feel free to submit PRs to address this and I will gladly merge


[PE-D][Tester B] Duplicate information allowed in contacts

We can add two different contacts with different names but identical in every other field. This might not be the most reasonable behaviour as partners and clients tend to be individuals with unique emails and phone numbers, so I have labeled this as a functionality bug. However, if this is intended behaviour, then perhaps it can be mentioned in the UG so that it isn't picked up as a bug in the next round! In that case I would relabel this as documentation bug.

Labels: type.FunctionalityBug severity.Low
original: sun-ruiheng/ped#3

added in planned enhancements


updated babel preset + dev sprite test setup

Sorry about the PR, forgot to change my upstream branch!


Download webpage after executing JavaScript scripts

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question

I am trying to make a new extractor and I would like to know if (and eventually how) is possible to download a webpage after executing its own javascript scripts. This because of some fields (in my case the video url) which are loaded by the scripts and then, if you download the page without executing them (just like wget does), you'll get an empty url.
Thanks.

please provide example URL

please provide example URL

https://sxyprn.com/post/5bb443225d5ae.html try this

First, don't worry about that site. It's handled by the YourPorn extractor (or can be be with some tweaks that I have at hand).
As to the larger question that you ask, the answer is that the tools don't exist to enable it.
Actually, these days it's difficult enough to get even a browser that isn't the latest Chrome to handle general web JS. However, there are certain cases where we do need to run some specific JS for an extractor (so far, YouTube itself) and the JSInterpreter module enables that without introducing new dependencies; but it's always at the risk that some site for which it's used suddenly deploys a syntax that we haven't allowed for (or even new syntax that breaks all previous JS interpreters, like optional chaining or ES2018 regex literals).
Two extractors use the PhantomJS interpreter mentioned in the link, but that introduces platform and configuration problems, and I don't really know if it works since I don't have it installed.

Thank you for the answer @dirkf , it was all I implicitly wanted to know. I'm happy that is possible to deal with pages using JS using youtube-dl (and i should have known since YouTube uses it).
From your answer I see that an extractor for that site already exists and from what I tried it works.
I am curious about the tweaks you have in mind.


An extra action 'Set Public Access Level…' displays for blob containers under SAS attached storage accounts

Storage Explorer Version: 1.14.0-dev
Build: 20200529.3
Branch: master
Platform/OS: Windows 10/ macOS Mojave
Architecture: ia32/x64
Regression From: Previous release(1.13.1)
Steps to reproduce:

Select one non-ADLS Gen2 storage account -> Attach the storage account via SAS.
Expand the attached storage account -> Blob Containers.
Create a blob container -> Check its context menu.
Refresh Blob Containers node -> Re-check the blob container's context menu.

Expect Experience:
No extra action displays.
Actual Experience:
An extra action 'Set Public Access Level...' displays.

More Info:

Display the below activity log when executing 'Set Public Access Level...'.

The issue shares the cause with #3036.

This issue is fixed on build master/20200602.3. Close it.


Properties are not field in despite EnableParameterizedContentWithPropertyAssignments

Hi again =)
So now I'm facing denationalization issue. Type has parameterized constructor, it serializes fine, and on deserialization constructor is called, but no other properties are filled in:

Updated repository, so it contains repro code for this issue: https://github.com/maxkoshevoi/ExtendedXmlSerializer-423

Hey! 😅  Thank you for taking the time to report these issues. 👍
To start, are you sure this is using the latest preview? (https://github.com/ExtendedXmlSerializer/home/pull/424#issuecomment-672267042)
I did try reproducing it but I have a passing test here:
https://github.com/ExtendedXmlSerializer/home/blob/c560a2a0d90e3b76af395c4bcf15d6de286176f3/test/ExtendedXmlSerializer.Tests.ReportedIssues/Issue427Tests.cs#L12-L78
Is there a difference in the class/graph perhaps?  If you can provide some code again I can check it out further for you.

It's not latest preview. It's latest stable (3.2.4). Can you try downloading provided repository and executing it?

Oh, regarding the test. Your array type is wrong. It should be NewTypeInfo (base class of NewFieldInfo)

OK!  I see it now.  This is actually an issue with both EnableParameterizedContent* extensions.  Nice find. Tricky. :)  It also looks involved, so it might take a while.  I'll see if I can carve up some time this weekend to investigate further.  In the meantime, please do use arrays aligned with the same element type if you can manage.

Goodness, I gotta say that whenever a new issue is reported here now part of me freaks out as I have to dig through code I wrote over 3 years ago and get acclimated with how I was thinking back then which is NOTHING LIKE WOULD DO NOW. 😅
Anyways, this was a tricky one but I think I got it situated for you:
https://github.com/ExtendedXmlSerializer/home/pull/428#issuecomment-674376741

Thank you so much for (in no particular order) fixing this so quickly and maintaining your 3-year-old repository.
If it wasn't for this NuGet, I don't know how would I do xml serialization.
So, fix for this and previous issues are releasing this Thursday, right? Or should I use pre-release version for now. I need to store child classes in base class array.

Thank you for the kind words, @maxkoshevoi 🙏
Indeed, you should use the preview version for now until Tuesday, at which point I will release to NuGet.  Please let me know if you encounter any other/additional issues between now and then and I will look into them for you. 👍

I have merged in this PR so the main feed for the preview source should be used:
Install-Package ExtendedXmlSerializer -Version <IP_ADDRESS> -Source https://ci.appveyor.com/nuget/extendedxmlserializer-preview

Unfortunately, AppVeyor doesn't provide notifications on PR merges, only commits so I have to provide this manually.  The above should work, let me know if it doesn't otherwise.

This fix has been deployed to NuGet and can be found here:
https://www.nuget.org/packages/ExtendedXmlSerializer/
Thanks again for reporting and providing code towards discovering, diagnosing, and ultimately fixing this issue.  Please do let me know of any issues you find around this or any other issue and I will take a look into it for you.  Closing this issue for now.


[EnhancedSwitch] Fix checked prop

[ ] PR has tests / docs demo, and is linted.
[ ] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[ ] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Fixes callemall/material-ui#7261

I can't reproduce you bug.

@LeoIannacone Just navigating to the #/components/checkbox page.

@oliviertassinari I meant: not sure how did you integrate this PR with the website

I have checkout your PR (4e274a05eb8582df99247574975267a3452fbbee) and runned the documentation site on my machine.

Any luck? The regression is consistant for me. It's fin when I checkout master, it's broken when I checkout the branch.

I just pushed a fix for that.

@LeoIannacone Thanks a lot!


How to get estimated time of arrival between to points using geo coder gem?

How to get estimated time of arrival between to points using geo coder gem?
any thoughts?

It sounds like you're looking for a routing/directions API. Geocoder is only for getting lat/lon coordinates of an address, or vice versa.


pull request for e2e test at 02/04/2017 10:45:08

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add option to use data restful endpoint

Description
Hawkuar versions < 0.13.0 used a .../data endpoint, and the .../raw did not exist.
This PR allow the use of this client with older versions of Hawkular

@simon3z @burmanm please review
The Hawkular version QE is using is 0.8.x. That version does not answer to .../raw endpoint, making this library compatible with old versions will make it easier for me to work with the machine QE have.
p.s.
@simon3z do we support old hawkulars ?
@burmanm if you do not want to support old versions it's ok, I can use curl when speaking to old hawkulars :-) , just comment here, and I will close this PR.

@simon3z do we support old hawkulars ?

@yaacov for CM we support up to what was delivered with OpenShift 3.1 (Einat has an env for you to check).
I think that we need this but it should be automatic (not a parameter that gets passed).
Please check also the ruby client.

@simon3z

Please check also the ruby client.

ruby  check /metrics/status  to get the version before doing .../raw or .../data .

I think that we need this but it should be automatic (not a parameter that gets passed).

Automation can be done where we use this client, we can do a call to /metrics/status  and then set this parameter according to the version.

@simon3z @burmanm added a status method to get the Hawkular server version, this can be used to automate the raw/data endpoint usage.

@burmanm we need to support old version of Hawkular, please review.
cc// @simon3z
p.s.
I do not like the name use_data_endpoint do you have a better name ?

@zgalor please review.

Please check also the ruby client.

@simon3z @burmanm just updated this PR to be like the ruby client:
a. changed the parameter to be lagacy_api (like the ruby client)
b. change the raw and the stats endpoints (like the ruby client)
https://github.com/hawkular/hawkular-client-ruby/blob/master/lib/hawkular/metrics/metric_api.rb#L218

I don't think that the understanding of lagacy_api should be in the lib user. Do you really want every user to be familiar with the nits of the API, versions, etc?
The user just wants the data.

I totally agree with @simon3z on https://github.com/hawkular/hawkular-client-python/pull/20#issuecomment-264852317 This is not too hard to decide depending on the api version returned by the /status endpoint

@yaacov I don't see the point in passing a param for a logic that's known within the hawk-client. This can only result in errors, and gives no added value to the user.
Better if the hawk-client redirects to relevant url based on version, as in ruby client:
https://github.com/hawkular/hawkular-client-ruby/blob/08dfdc8ee23d3ff0eded32910b7bee1d80536a0b/lib/hawkular/metrics/metrics_client.rb#L43

I don't think that the understanding of lagacy_api should be in the lib user

@simon3z @pilhuhn @zgalor ok :sunglasses:
a. added an automatic check
b. will add tests tomorrow

@burmanm how do i run the tests ? i need a hawkular server on localhost:8080 ?

@burmanm please review
p.s.
I do not know how to run the tests :-(

@simon3z @pilhuhn @burmanm please review
Added tests, all tests pass


Also emit source information for paths

Previously, the location for path-based (i.e., local) packages was
redacted from metadata output. This was done way back when so that
Cargo.lock would not include path sources:
https://github.com/rust-lang/cargo/issues/7483#issuecomment-539258083
This PR makes this redaction optional so that cargo metadata and
friends will output the source location, which is useful for tools
like rustfmt which need to know the paths to local packages (see #7483
and rust-lang/rustfmt#4599).
Interestingly enough, no tests fail even though
disable_path_serialization is never currently called. I don't know if
that's because there's no test that cover where redaction is needed, or
because redaction is simply no longer needed (presumably because
lockfile generation now uses custom logic). If it is the latter, this PR
can be simplified to not support opting into redaction.
Fixes #7483

r? @alexcrichton
(rust-highfive has picked a reviewer for you, use r? to override)

The failing test is due to disable_path_serialization being unused. The tests otherwise pass. I'll push with an #[allow(dead_code)] attribute so we can tests passing for now.

I don't think this is something that can be changed, because tools will be depending on that value being null.
Also, for rustfmt's use case, it needs the path to the package.  The SourceId is intended to be opaque, and that shouldn't be used for determining the path.  I was roughly thinking of adding a new field for that path information.
As for fixing rustfmt's specific use case, there's also a problem where --no-deps doesn't include path dependencies if it is not an explicit workspace.  I seem to recall working on that, but I can't find it.

Hmm, interesting. Wouldn't adding a field be just as breaking? In what cases would consumers specifically expect the field to be null for paths specifically?
The problem with using manifest_path is, as @calebcartwright outlines in https://github.com/rust-lang/cargo/issues/7483#issuecomment-741114527, that manifest_path doesn't exist on dependency nodes, which is where rustfmt needs it I think. And presumably adding it there would also be a breaking change. I agree with you though that source should probably be considered opaque, so not sure what the best path forward here is.
I'd be happy to write up a PR that includes path dependencies even if --no-deps is given, but that also seems like it might break some downstream consumers? I suppose we could go to a --format-version=2?

Also, for rustfmt's use case, it needs the path to the package

@ehuss - we need to know where on the file system to locate the path-based dependencies, which are indeed typically local implicit workspace members, but can also be some random other package on the file system (I've no idea what that use case would be but we technically support that today)

Wouldn't adding a field be just as breaking?

New fields are allowed, as they are usually ignored by things like serde.  I thought that was documented, but I can only see it mentioned in the rustc docs.

In what cases would consumers specifically expect the field to be null for paths specifically?

Whenever it wants to collect all local packages (like this).

The problem with using manifest_path is

Yea, it's a bit of a thorny issue.  I was working on https://github.com/rust-lang/rustfmt/issues/4247, but never really finished.  The idea is that cargo fmt should use --no-deps, and Cargo should provide the path dependencies in the packages array.  There is some risk that could confuse existing tools.  That's really tough to evaluate how risky.  That might be why I didn't finish, I recall this being a little tricky.

@ehuss Hmm, yeah, that's tricky. If new fields are indeed ignored and we're willing to add one, how about just adding a manifest-path each dependency node then? I'm more inclined to go that way than include local path dependencies in packages since the latter seems like it is more likely to have an adverse impact on other tooling. I have some spare cycles and would be happy to push forward on a PR here if you think that's a reasonable path.

how about just adding a manifest-path each dependency node then?

I don't think that would address the cargo fmt use case, as the intent is to switch to --no-deps (for performance), and with --no-deps the resolve is null.

Hmm, wouldn't it be sufficient for rustfmt to look at packages[].dependencies[] if those contained a manifest_path if they are local paths? Otherwise I'm guessing that I'm missing something.

wouldn't it be sufficient for rustfmt to look at packages[].dependencies[] if those contained a manifest_path if they are local paths

if the dependency nodes (crucially with --no-deps) contain something we can use to find the local manifest path then yes, that'd solve our need

I fear I may be missing some context on this, as I don't understand why we'd need more paths available than we already have with each package's manifest path listed. Can you elaborate a bit more where the current output falls short?
(e.g. if this is a rustfmt thing, can all packages be iterated over with --no-deps and their Cargo.toml is found via manifest_path?)

(e.g. if this is a rustfmt thing, can all packages be iterated over with --no-deps and their Cargo.toml is found via manifest_path?)

We already do this today for the packages, but #7483 is about our need to be able to locate the manifest file for dependencies of those packages. Implicit workspace members are not included in the packages collection, and with --no-deps the available information on the dependency nodes is stripped, leaving rustfmt with no way to correctly and consistently locate the manifests for those implicit workspace members.
That forces us to eschew the --no-deps flags which is causing various other downsides and challenges that are unnecessary for the purposes of formatting code

Ah ok, that makes sense. I don't think that "just add the information to dependencies" is what you want to fix this, though, because you presumably want all transtive path dependencies of a crate, not just the first-level path dependencies outside of the workspace, right?
I don't think that Cargo has any equivalent to that right now, you almost want cargo metadata --just-the-path-dependencies which doesn't currently exist.

because you presumably want all transtive path dependencies of a crate, not just the first-level path dependencies outside of the workspace, right?

That's correct and currently we do that transitive walking within cargo fmt once we get the paths for the direct deps from the metadata

you almost want cargo metadata --just-the-path-dependencies which doesn't currently exist.

That would be fantastic and allow us to simplify things a bit on the rustfmt side, but even being able to get the paths for the direct dependencies without having to require network connectivity, index/performance hit, etc. would be a huge win

Ok mostly just wanted to confirm. This means that "just add info to dependencies" is not going to work for rustfmt's use case as-is I think, since it will require more invasive changes in Cargo. Unfortunately though even implementing something like --just-the-path-dependencies in Cargo would be difficult to do. We don't actually know whether path dependencies in [patch] will be used unless we run the resolver, which naturally relies on everything being online.
Would it be possible for rustfmt to run cargo metadata --no-deps multiple times? That means if we include more information about dependencies rustfmt could follow the dependency links outside of the workspace itself. This would not handle path dependencies in [patch] correctly, however.

Would it be possible for rustfmt to run cargo metadata --no-deps multiple times?

We already do this today (albeit without --no-deps for the discussed reasons) to walk any and all transitive local dependencies, we just have to run cargo metadata in the corresponding directory for every discovered local dep in that tree

This means that "just add info to dependencies" is not going to work for rustfmt's use case as-is
That means if we include more information about dependencies rustfmt could follow the dependency links outside of the workspace itself.

I'm not following the distinction between these two, could you elaborate?
At the end of the day, the most minimal thing that would solve our need on the rustfmt side is the ability to determine the manifest path for implicit workspace members (even just direct local deps on packages would suffice) from cargo without having to the required network connectivity, downloading dependencies, etc. that happens today.
We're happy to work with whatever makes sense on the cargo side (understand there's some complexity here), but if there was some field foo on the dependency nodes in the cargo metadata --no-deps output that provided the path to the manifest for local dependencies, that would indeed solve our problem.

Just for comparison, I took a stab at a PR for surfacing manifest paths just for direct local dependencies in https://github.com/rust-lang/cargo/pull/8994.

Oh interesting, @calebcartwright how come you invoke cargo metadata once-per-package? Without specifying --no-deps I thought cargo metadata would basically give you the same information every time you invoke it. (in that it should give you full information about all the dependencies).

I'm not following the distinction between these two, could you elaborate?
At the end of the day, the most minimal thing that would solve our need on the rustfmt side is the ability to determine the manifest path for implicit workspace members (even just direct local deps on packages would suffice) from cargo without having to the required network connectivity, downloading dependencies, etc. that happens today.

What I'm imagining is that rustfmt would always invoke cargo metadata with the --no-deps flag so no network stuff happens. In that scenario when you first run it you'll initially learn of all workspace members and their dependency paths. I believe with https://github.com/rust-lang/cargo/pull/8994 you could then also learn about the path dependencies those workspace members have which are not themselves workspace members. That would allow you to iteratively, for all those non-workspace members, execute cargo metadata --no-deps to discover the full local dependency graph.
Would that work for rustfmt? If so https://github.com/rust-lang/cargo/pull/8994 definitely sounds like a good PR to me! Although it also seems good in isolation :)

What I'm imagining is that rustfmt would always invoke cargo metadata with the --no-deps flag so no network stuff happens. In that scenario when you first run it you'll initially learn of all workspace members and their dependency paths. I believe with #8994 you could then also learn about the path dependencies those workspace members have which are not themselves workspace members. That would allow you to iteratively, for all those non-workspace members, execute cargo metadata --no-deps to discover the full local dependency graph

Yes, that's precisely what we'd like to be able to, and is essentially what we do today just sans --no-deps

Oh interesting, @calebcartwright how come you invoke cargo metadata once-per-package? Without specifying --no-deps I thought cargo metadata would basically give you the same information every time you invoke it

Does the metadata output contain all the target and manifest path information for all dependencies for all packages? The core data points cargo fmt is grabbing to pass to rustfmt are the entry point files (obtained from the targets) and the edition.
We first run cargo metadata in the cwd, and then if there's local deps at some foo/bar.. path (or ../../../whatever) for any of the (non dependency) packages then we run the metadata commands in those respective local dep directories, recursively as needed for all local deps.
I don't recall that initial metadata output containing all the information we need for that entire tree of local deps but could certainly be mistaken.

I thought that the metadata information contained all that, but I could also be remembering wrong!
In any case it sounds like we should perhaps close this in favor of https://github.com/rust-lang/cargo/pull/8994?

@alexcrichton I went ahead and closed this -- #8994 seems like a much simpler way to get at this then, seeing as it still solves the need that rustfmt has 🎉


Weathermap 0.98

is there an updated planned to 0.98?

Unlikely as a number of areas of network-weathermap have been changed to work for us.
We will port to the final release when it's done.

+1 to upgrade

No upgrade will be done until 1.x release is out.


Links from http://brandnewcongress.org/teams result in 404 error

Go to http://brandnewcongress.org/teams
Click on Calendar
404 error shown
The same is true for most of the links.
It looks like maybe these links should go to http://go.brandnewcongress.org/teams?

We should fix this by just moving the teams page off nationbuilder. This is happening in #79 .  @jakerockland are you able to move /teams over as well?

Just got started on #107 moving all of the nation builder files over. Plan is to try to finish this up by end of week.

Thank you!  Also are you in our slack yet?
On Wed, Aug 3, 2016 at 4:00 AM Jake Rockland<EMAIL_ADDRESS>wrote:

Just got started on #107
https://github.com/BrandNewCongress/website/pull/107 moving all of the
nation builder files over. Plan is to try to finish this up by end of week.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BrandNewCongress/website/issues/102#issuecomment-237168998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFHRltriYDh57paw-m1f3xbjbwGioo2ks5qcEmZgaJpZM4JZQud
.

I'm not yet, no, would love an invite though!

This should be fixed now.  Thanks @jakerockland, merged in your PR!


V2.4 Labels are not translated for some languages

Some of the label for common names are not translated from english.
For instance,
https://github.com/kahst/BirdNET-Analyzer/blob/main/labels/V2.4/BirdNET_GLOBAL_6K_V2.4_Labels_ar.txt
https://github.com/kahst/BirdNET-Analyzer/blob/main/labels/V2.4/BirdNET_GLOBAL_6K_V2.4_Labels_pt.txt

We pull all the names from eBird, if there is no translation it fallsback to english (see translate.py). For missing translations we have to rely on local experts (like in this pull request).


Add WGSL support

Checklist:

[x] I am adding a new language.

[x] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?q=path%3A*.wgsl&type=code

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

Bevy's Example

Sample license(s):

MIT

[x] I have included a syntax highlighting grammar: wgsl-grammar
[x] I have added a color

Hex value: #1a5e9a
Rationale: Blue is a present color in the WebGPU logo.  This shade is used in the official WGSL doc.

[ ] I have updated the heuristics to distinguish my language from others using the same extension.

I'm running into troubles trying to install the charlock_holmes gem and that seems to be the reason why the script won't fully work. For the same reason I can't run the command you sent.

charlock_holmes isn't needed for that command so you should find running gem install licensed and then licensed cache -c vendor/licenses/config.yml will do the trick too.


Updated NuGet build targets to consume PackageReference

Imagine you have a project with a single PackageReference item. This will cause us to generate a project.assets.json file in the intermediates directory. Then you remove that item, and run NuGet restore.
That should cause us to drop any references to the old item, but currently it does not. Since there are no PackageReference items we don't regenerate the project.assets.json, leaving the stale one in the intermediates directory. And since we can still find it, we still use it.
So the fix is we check for PackageReference existence and then only uses project.assets.json file otherwise look for project.lock.json and use that instead. If none of these exists, then it simply don't run this build target.
Also just to clarify, we don't need to use NuGet project style property here like NuGetProjectStyle or RestoreProjectStyle since it could happen that along with a stale assets file we also have stale NuGet props/target files which define these property and we wrongly label project based on that.
Fixes https://github.com/NuGet/Home/issues/4017
@rrelyea @emgarten @tmeschter @jasonmalinowski

Hi @jainaashish, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

I think this is trying to solve two different issues and not really solving either.

Ignoring stale data from NuGet
Keeping the build task in sync with NuGet (using the same output files)

we don't need to use NuGet project style property here like NuGetProjectStyle or RestoreProjectStyle since it could happen that along with a stale assets file we also have stale NuGet props/target files which define these property and we wrongly label project based on that.

RestoreProjectStyle is not written by NuGet, so it cannot be stale. The build task must read this to allow users to override the type if needed.
The stale data mentioned here is still going to be imported along with all package targets/props, contentFiles and everything else. Which means that the build task ignoring this doesn't really fix the issue, it just means that half of the references are going to come from one place, and half from another place. So number one above isn't fixed.
Number two also isn't fixed because this change is trying to avoid any possible output data from NuGet in this process.

Here's my suggestion:
The problem of changing between project.json and project.assets.json isn't a normal scenario. Migration tools and the NuGet UI should handle this. Everything else should depend on the user cleaning up these stale files before the build task runs.
For this build target:

Add a target to get the project style
a. Check if RestoreProjectStyle exists first, this would be set by the SDK or the user and should always be respected.
b. Otherwise check if NuGetProjectStyle exists (this is written by NuGet). If the file is stale there are already bigger problems as discussed above. The value here should be trusted.
Condition based on the project style and only check for the expected file names
If no project style properties can be found go through the same fallback in _GetProjectLockFile while also checking if the files exist as part of the target.

The current check to see if any assets file exist at the end to skip non-nuget enabled projects and packages.config projects looks good.

@emgarten I still don't see a point of using RestoreProjectStyle and NuGetProjectStyle property in this build task. And my reasoning is simple, these build targets are being executed after restore, where we have already decided for a project style ans corresponding have our output file generated (be it lock file or assets) then why we really want to rely on these properties? rather we just need to rely on existence of these output files and if both types of file exists, then we always have our precedence for assets file. Earlier I used these properties but i didn't see any usefulness of that, which is why i removed those.
The stale data mentioned here is still going to be imported along with all package targets/props, contentFiles and everything else. Which means that the build task ignoring this doesn't really fix the issue, it just means that half of the references are going to come from one place, and half from another place. So number one above isn't fixed.
Lets discuss it in person n close on this since I'm not sure what is the real issue it will cause n where.

Discussed offline, use the ProjectAssetsFile property instead to override the type if needed. Checking the existing properties and looking for PackageReferences will not be needed.

@emgarten updated to use ProjectAssetsFile property


Feature Request: print status messages within examples (documentation formatter)

Request Description
Add a method to print status messages nested below an Example's description, like:
Navigation Bar (describe)
  As an Admin (context)
    should show Admin navigation links (it)
      => in this place (step / status message)
      => in that place (step / status message)

Background
During a class project, my group found ourselves either 1) repeating complicated setup multiple times for different examples, or 2) including many expectations within a single example and accepting that the documentation formatter wouldn't provide detailed status output. We realized we'd like a way to include status (or "step") messages inline with the documentation formatter, so that the setup and interaction pattern could be completed once as we went through several expectations. I was able to monkey patch this in via a helper in spec/support.
The Monkey Patch

added a step method to RSpec::Core::ExampleGroup
added a print_steps method to RSpec::Core::Formatters::DocumentationFormatter, which was then added to the end of the example_passed and example_failed methods. (the example_pending method only appears to run when an example is skipped entirely, so no steps would ever be added to the metadata)

class RSpec::Core::ExampleGroup
  def step(message)
    metadata = current_example.metadata
    metadata[:steps] ||= []
    metadata[:steps] << message
    yield
  end

  private

  def current_example
    # Examples are added to each ExampleGroup at the time they are executed
    # so the "current" example will be the last one in the ExampleGroup.
    # Need to access from the current SubClass of the particular ExampleGroup
    # because that's where the Example inserts itself when it is initialized.
    self.class.examples.last
  end
end

class RSpec::Core::Formatters::DocumentationFormatter
  def example_passed(passed)
    output.puts passed_output(passed.example)
    print_steps(passed.example, :success)
  end

  def example_failed(failure)
    output.puts failure_output(failure.example)
    print_steps(failure.example, :failure)
  end

  private

  def print_steps(example, state)
    # The monkey patch doesn't have the ConsoleCodes constant initialized like
    # the core file, so for readability I assigned it to a variable on a
    # separate line.
    wrapper = RSpec::Core::Formatters::ConsoleCodes
    steps = example.metadata[:steps] || []
    last_step = steps.size - 1
    steps.each_with_index do |message, step|
      # Since execution of the Example block ends immediately at a failure,
      # print every step message as a :success (they must necessarily have
      # succeeded for us to have moved past them) until the last one, then print
      # the last one with the :success/:failed state of its parent Example.
      output.puts wrapper.wrap("  #{current_indentation}=> #{message}",
                               step < last_step ? :success : state)
    end
  end
end

(note: I intentionally formatted the output of step messages to be prefixed with '=> ' due to personal preference. I am a student, and I hit a wall trying to understand how I could give it a default prefix of ' ' and accept an override at the ExampleGroup- and/or step-level with arguments passed to those methods in _spec files. Because of this, I hardcoded my preferred format. I would not expect a native implementation to match my formatting, if this feature is approved.)
Usage
Within an example, you can now call the step method, and pass it a block containing the code for that step.
describe 'Navigation Bar' do
  before(:each) do
    # some substantial setup
  end

  context 'As an Admin' do
    it 'should show Admin navigation links' do
      step 'in this place' do
        # expectations relevant to 'this place'
      end

      step 'in that place' do
        # expectations relevant to 'that place'
      end
    end
  end
end

When running RSpec with the documentation formatter, it will now print these messages as shown in the feature request above.

Screenshot of console output
I threw in an intentional failure to demonstrate how this appears when a test fails. Since I got sidetracked by this very early in our project and it wasn't something we could include in the final submission, it's on an early branch where we have very little going on yet to test.

Hello @joequincy and thanks for your detailed feature request.
I understand what your are trying to do, but I am not completely convinced about how the tests will be written at the end. It looks like a breaking change on RSpec DSL. 🙂
I am wondering if your initial issues could be addressed differently.

repeating complicated setup multiple times for different examples
including many expectations within a single example and accepting that the documentation formatter wouldn't provide detailed status output.

For 1) see below with a very classic example turned into shared examples.
# frozen_string_literal: true

begin
  require "bundler/inline"
rescue LoadError => e
  $stderr.puts "Bundler version 1.10 or later is required. Please update your Bundler"
  raise e
end

gemfile(true) do
  source "https://rubygems.org"

  gem "rspec", "~> 3"
end

puts "Ruby version is: #{RUBY_VERSION}"
require 'rspec/autorun'

RSpec.configure do |config|
  config.formatter = :documentation
end

RSpec.describe 'Navigation Bar' do
  context 'as an admin' do
    context 'in  place A' do
      it 'shows status bar' do
        expect(true).to eq(true)
      end
    end

    context 'in  place B' do
      it 'shows status bar' do
        expect(true).to eq(true)
      end
    end
  end
end

# with shared examples
RSpec.shared_examples "in place" do |place|
  context "in place #{place}" do
    it "shows status bar" do
      expect(true).to eq(true)
    end
  end
end

RSpec.describe 'Navigation Bar' do
  context 'as an admin' do
    include_examples "in place", "A"
    include_examples "in place", "B"
  end
end

Did you thought about using shared context for repeated complicated setups?
For 2) I don't think this is something we want to encourage but I prefer to see what @JonRowe think about it. 😊

Hi, this can be best addressed by building a custom formatter, if you take the existing format you like as a base (preferably by vendoring it within your code, extending from our classes is an unsupported API although it would work) and then adding an extra notification. You can then configure your code to send this new notification to any reporter that is registered to receive it and get the output you desire.
As this is fairly specific I'm going to close this for now, but I'm happy to help provide advice on how to build this for yourself, you could then choose to release it as a gem and if enough community support was for it we might consider it for inclusion into the core.

Thank you both very much for the feedback.
@benoittgt I was not aware that functionality existed. If I understand correctly, I could then (within the context 'as an admin') have a before(:all) block which would run the complicated setup a single time and maintain that state through each example just within the context 'as an admin'? That would make sense.
@JonRowe I do want to explore this path, as it wouldn't require a change to the core, but it solves the problem of how to easily include it in future projects (also, building a gem is something I already wanted to explore). Thank you for your offer of help! I'll see how far I get on my own first, but would it be all right to tag you in an issue on that project to seek (help if I completely hit a wall)?

You could also use custom matchers and aggregate failures to have messages for different step failures. Happy to be tagged in issues but beware there may be delays in replies!

@joequincy We tend to say to avoid using before(:all) because it creates sort of global state. On big test suite it can cause painful problems, hard to debug. You should make your test independent also don't try to make your test too DRY. :)

I know this is from long ago (and far away) but I would really love to see this, if not as part of core rspec, as a gem plugin for it.  Bouncing this around the office, it could have a couple of variations (including subclassing the example group to provide a context with: :multiple_steps or having it ... then_it sets where then_it would run like an after hook. The whole thing is a little beyond my ken, or I think I would do it myself, given how long we have talked about this, particularly for feature, system, and request setups that for various reasons require large datasets/fixtures/setups that take a long time to run, or for bigger flows that document and capture bad emergent behavior in more complex use flows.

Given the open design of the formatter, I suggest anyone interested to write an RSpec extension as a grm that would introduce a custom formatter and the ‘step’ method.


Cloud Vision docs for Ruby feedback: typo perhaps.

The very first sentence is the following:
"Google Cloud Vision allows easy integration of vision detection features developer applications, including image labeling, face and landmark detection, optical character recognition (OCR), and tagging of explicit content."
The "...developer applications..." sounds a bit off. I wonder if you meant to say "... to develop applications..." or perhaps something else.

Just noticed the right sentence in this page: http://googlecloudplatform.github.io/google-cloud-ruby/#/docs/google-cloud-vision/v0.20.2/google/cloud/vision/project
I guess you are missing the word "within", such as "...features within developer applications..." in the original page:
http://googlecloudplatform.github.io/google-cloud-ruby/#/docs/google-cloud-vision/v0.20.2/google/cloud/vision

Yes, a typo, thank you for the thorough review! Fixing now.


[Request] Ex5

Hey! Is it possible to maybe get the new Extreme 5 added?
Especially the spinning circle phases are to fast for my brain xD

seconded

Ex5 should be available in v80.


Add NOT_SET to GameModes

@bloodmc told me to add this.

We don't seem to have any getters or setters for the player's game mode, so if you want to implement that you could also just add it together with this.

What is this NOT_SET gamemode for a gamemode? I never stumbled over this one. Does it resets a player to the worlds default Gamemode?

@ST-DDT https://github.com/SpongePowered/Sponge/pull/114#discussion_r22441739

@bloodmc @Aaron1011 I remember discussing the reaction of representing a fake Player in SpongeAPI with @Zidane and @Deamon5550 when writing #363. We all agreed that "fake" players represented by mods and plugins should be interfaced as Human rather than Player since the following conditions are met:

Human provides all usable entity related methods necessary to interface with Player-like entities
Players are specifically instances of Humans with an attached networking handler, separate offline storage, and recipients of sounds and particles.
Players also are Users such that they implicitly should be modifiable while offline.
Fake players have no persisted data beyond their entity location in the world
Fake players do NOT have a networking handler, they do NOT receive packets, they do NOT bode well with plugins attempting to communicate with a client with custom payloads.

So, I'll have to say that overall, any ideas of "fake players" should be written with Human in mind and not Player. This directly applies to GameModes since "fake players" should not be considered for event handling if their game mode is changed, etc.

This is really hard to prevent the Player interface because it is required in some impls like CB did it.
On the other hand you can add gamemodes in the server impl without specifing them in the API. This is probably the way we should go here.


No numbers show up

I am not able to get this to work.  No numbers show up, despite it being checked in options.

These conditions need to be fulfilled:
if opts.sd_grid_add_image_number and opts.save_images_add_number and opts.samples_save:
So:
1.

Are these all set for you?

Aha.  No, I do not set always save all generated images.  I'll just make a quick commit change in my local repo to review that check.  Thanks.


The outline doesn't remember folded/unfolded items after collapse

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.81.1
OS Version: Windows_NT x64 10.0.14393

Steps to Reproduce:

Open a file with code (e.g. JavaScript)
Press "Outline" on the left panel
Press "Collapse All"
Unfold some items in the tree
Press "Outline" to collapse it
Press "Outline" again

Estimated result: the same tree view as it was before the outline was collapsed
Factual result:  all items are open

I tried to move the Outline to individual tab on the right side. It have moved perfectly. But when I switch to the explorer and come back to the Outline, it forgets the tree configuration and resets it to the default view  (all is open for my configuration). I don't change an opened file or anything else.

folding into https://github.com/microsoft/vscode/issues/197251

This is not a duplicate of #197251, please reopen this issue.


[camera] flash triggers when changing flash mode (Android)

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Install and execute the camera plugin example project (-> https://github.com/flutter/packages/tree/main/packages/camera/camera/example/camera/camera/example) on an android smartphone
Select back camera
Select flash mode "FlashMode.always" (flash does not trigger, ok)
Take a picture (flash triggers, ok)
Change flash mode to  "FlashMode.auto" (flash triggers, not ok)

=> Flash tiggers everytime when you change the flash mode to "FlashMode.always" or "FlashMode.auto"
Expected results
When changing the flash mode to "FlashMode.always" or "FlashMode.auto" the flash should not trigger.
Actual results
Flash tiggers everytime when you change the flash mode to "FlashMode.always" or "FlashMode.auto"
Code sample
Just install and execute the camera plugin example project -> https://github.com/flutter/packages/tree/main/packages/camera/camera/example
Screenshots or Video
No response
Logs
No response
Flutter Doctor output
Doctor output

[✓] Flutter (Channel stable, 3.7.7, on macOS 13.2.1 22D68 darwin-arm64, locale en-DE)
    • Flutter version 3.7.7 on channel stable at /Users/felix/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2ad6cd72c0 (7 weeks ago), 2023-03-08 09:41:59 -0800
    • Engine revision 1837b5be5f
    • Dart version 2.19.4
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/felix/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • Java binary at: /Users/felix/Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.12.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Users/felix/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Ultimate Edition (version 2022.2.5)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 72.1.3
    • Dart plugin version 222.4560

[✓] VS Code (version 1.77.3)
    • VS Code at /Users/felix/Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • SM A047F (mobile) • R58TB15K7TF • android-arm64  • Android 13 (API 33)
    • macOS (desktop)   • macos       • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)      • chrome      • web-javascript • Google Chrome 112.0.5615.137

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Hi @felixriehm, what device are you experiencing this issue on?
I tested the example code and I do not see the behavior you're reporting. See the recording below
What version of camera & camera_android do you have in your project? You can find the camera_android version in
your pubspec.lock.

recording
https://user-images.githubusercontent.com/88313112/234572458-7a184577-d359-4113-95d6-402e3b62e293.mp4

Hey @danagbemava-nc thanks for the reply. I have attached a recording of the issue.
Smartphone: Galaxy A04s
Model name: SM-A047F/DSN
One UI Core Version 5.1
Android Verion: 13
camera: camera: 0.10.4
camera_android: 0.10.5
https://user-images.githubusercontent.com/13718034/234633720-d98e30a3-17a5-4776-a20b-dd4bc56cbbaa.mp4

Hi @felixriehm, is this issue only reproducing on the galaxy a04s?
I attempted to reproduce this on another device (a Poco X3 NFC), but I ran into https://github.com/flutter/flutter/issues/97501 so I couldn't verify this on that device.

@danagbemava-nc unfortunately i only have the galaxy a04s

Thanks for the info.
Labeling for further investigation as I cannot reproduce this locally. I tested on a Pixel 7, Poco X3 NFC & a Nokia 6.
The Nokia 6 and Pixel 7 both behave the same, i.e, the flash isn't triggered when toggling the flash mode and when I tested on the Poco X3 NFC, I run into another issue as reported in https://github.com/flutter/flutter/issues/125550#issuecomment-1524959130.
This could be affecting just a specific set of devices, currently galaxy a04s.

for all coming to this via google:
i have used this now https://pub.dev/packages/camerawesome
supports image stream via "image analysis"

This issue should be fixed in the CameraX implementation of the camera plugin, so please try it out!
If you find a similar issue with that implementation (or any other issues), please feel free to file a separate issue.

I have tested it with my Galaxy A04s. Works now! Thanks @camsim99!


Android Forms fix for OAuth sample

Added static property to the MainActivity class to provide the app context.

Hey @nCastle1
I implemented a fix for the problem reported in the OAuth sample. I only updated a few lines of code, let me know if this looks OK.


make all fails to build kube-scheduler

I am trying to build kubernetes from source and I get an error building kube-scheduler for more recent releases (v0.11.0 and HEAD).  When I try the same procedure on an earlier release (v0.8.1) the same steps, and the same machine compiles kube-scheduler.
Here are the recreate steps:
$ git clone https://github.com/GoogleCloudPlatform/kubernetes.git
$ cd kubernetes
$ make all WHAT='plugin/cmd/kube-scheduler'

The error I get is the following:
hack/build-go.sh plugin/cmd/kube-scheduler
+++ Building go targets for linux/amd64:
    plugin/cmd/kube-scheduler
# github.com/GoogleCloudPlatform/kubernetes/pkg/probe/http
_output/local/go/src/github.com/GoogleCloudPlatform/kubernetes/pkg/probe/http/http.go:46: unknown http.Client field 'Timeout' in struct literal
!!! Error in /home/ubuntu/kubernetes/hack/lib/golang.sh:305
  'go install "${goflags[@]:+${goflags[@]}}" -ldflags "${version_ldflags}" "${binaries[@]}"' exited with status 2
Call stack:
  1: /home/ubuntu/kubernetes/hack/lib/golang.sh:305 kube::golang::build_binaries(...)
  2: hack/build-go.sh:26 main(...)
Exiting with status 1
!!! Error in /home/ubuntu/kubernetes/hack/lib/golang.sh:240
  '( kube::golang::setup_env; local version_ldflags; version_ldflags=$(kube::version::ldflags); local host_platform; host_platform=$(kube::golang::host_platform); local goflags; eval "goflags=(${KUBE_GOFLAGS:-})"; local use_go_build; local -a targets=(); local arg; for arg in "$@";
do
    if [[ "${arg}" == "--use_go_build" ]]; then
        use_go_build=true;
    else
        if [[ "${arg}" == -* ]]; then
            goflags+=("${arg}");
        else
            targets+=("${arg}");
        fi;
    fi;
done; if [[ ${#targets[@]} -eq 0 ]]; then
    targets=("${KUBE_ALL_TARGETS[@]}");
fi; local -a platforms=("${KUBE_BUILD_PLATFORMS[@]:+${KUBE_BUILD_PLATFORMS[@]}}"); if [[ ${#platforms[@]} -eq 0 ]]; then
    platforms=("${host_platform}");
fi; local binaries; binaries=($(kube::golang::binaries_from_targets "${targets[@]}")); local platform; for platform in "${platforms[@]}";
do
    kube::golang::set_platform_envs "${platform}"; kube::log::status "Building go targets for ${platform}:" "${targets[@]}"; if [[ -n ${use_go_build:-} ]]; then
        local output_path="${KUBE_GOPATH}/bin"; if [[ $platform != $host_platform ]]; then
            output_path="${output_path}/${platform//\//_}";
        fi; for binary in "${binaries[@]}";
        do
            local bin=$(basename "${binary}"); if [[ ${GOOS} == "windows" ]]; then
                bin="${bin}.exe";
            fi; go build -o "${output_path}/${bin}" "${goflags[@]:+${goflags[@]}}" -ldflags "${version_ldflags}" "${binary}";
        done;
    else
        go install "${goflags[@]:+${goflags[@]}}" -ldflags "${version_ldflags}" "${binaries[@]}";
    fi;
done )' exited with status 1
Call stack:
  1: /home/ubuntu/kubernetes/hack/lib/golang.sh:240 kube::golang::build_binaries(...)
  2: hack/build-go.sh:26 main(...)

It looks like you aren't using a very recent version of the Go compiler
(1.2). The build is failing because it doesn't recognize the http.Client's
Timeout field, which was added in Go 1.3 (see
https://golang.org/doc/go1.3#minor_library_changes). Try upgrading your Go
install to 1.3 (or better yet, 1.4) and see if that helps.
Robby
On Thu, Mar 5, 2015 at 10:08 AM, Matt Bruzek<EMAIL_ADDRESS>wrote:

On the same system, I can build kube-scheduler version 0.8.1
git checkout -b v0.8.1 tags/v0.8.1
Switched to a new branch 'v0.8.1'
root@ip-172-31-16-130:/home/ubuntu/kubernetes# make all WHAT='plugin/cmd/kube-scheduler'
hack/build-go.sh plugin/cmd/kube-scheduler
+++ Building go targets for linux/amd64:
plugin/cmd/kube-scheduler
+++ Placing binaries
What changed in kube-scheduler to make this not work?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5098#issuecomment-77416240
.

Thanks for taking a look @roberthbailey
That is the version of go that is installed using the Ubuntu package repository for trusty.  I will follow the instructions at https://golang.org/doc/install to get a more current version.

Have same error on CoreOS stable (557.2.0) with this instruction https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-kubernetes-on-top-of-a-coreos-cluster

@roberthbailey I had the time to try out the latest 1.4.2 go compiler and as you indicated that fixed the problem.  Thanks for the help.

Awesome! Hopefully that will help @Suvitruf as well.


PHOENIX-4878 Remove SharedTableState and replace with PTable

Thanks for the patch @yanxinyi . Looks pretty good, can you please create a patch and submit it on the JIRA so that we can get a a test run? Also can you file a follow up JIRA to remove SharedTableState in two releases (4.17) ?

rebase from the master


Update recipe

This PR updates the recipe and cleans up a few things, notably

remove the bld.bat script for windows, we don't need it
remove the runtime requirement on ligo-common, we don't need it for python >=3

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


OFFER STATUS (DATING ULTRASOUND SCAN): Permitted National Codes and National Codes

OFFER STATUS (DATING ULTRASOUND SCAN) has Permitted National Codes and National Codes (https://www.datadictionary.nhs.uk/data_elements/offer_status__dating_ultrasound_scan_.html)
It should only have Permitted National Codes, see the 2 images below.
@jamesrwelch - is this one for you or Likin?
The Data Element is linked to 2 Attributes: ACTIVITY NOT OFFERED REASON FOR MATERNITY and ACTIVITY OFFER STATUS

8/7/22 - I spoke to Bob to clarify the situation with Likin. Work is progressing on the pipeline. He is working on the internal proof of concept. Likin is not available to work on any tickets until this work is complete. This could be November as that is when the next dictionary release is due. Bob says if Likin is distracted it could affect dictionary publication. Bob will obviously let us know if this changes.

15/8/22 - James has spoken to Likin and identified an issue with Data Elements where the html around the Permitted National Codes is not correct.
Items checked and html made consistent with other items that work. Will not be able to check this until the November 2022 release.

@jamesrwelch and @likin1
This still isn't right: https://dduat.dev.dataproducts.nhs.uk/data_elements/offer_status__dating_ultrasound_scan_.html
Who needs to fix this?

Message from Likin:
The text is present as “Permitted National Codes:”. For this also I will have to alter the code to handle this. So, this is also for me.

This has been wrong for 2 years so can be fixed for the December 2022 release.

fixed for december release

@likin1 - this still doesn't look right: https://dduat.dev.dataproducts.nhs.uk/data_elements/offer_status__dating_ultrasound_scan_.html
Do we leave this for January as the December release needs to be added to the website this week?

This hasn't been fixed so Likin is investigating for the January 2023 release.

Fixed in the January 2023 release: https://www.datadictionary.nhs.uk/data_elements/offer_status__dating_ultrasound_scan_.html
Issued closed.


Make C-h C-o always find Elisp definitions

Currently just displays the useless TAGS table prompt unless you're in an Elisp file. The desired behavior is to have C-h C-o always do Elisp, and M-. be mode-specific.

Fixed in fc34840792acf82264185b427a9c5ad6eef9fcbb.


Feature Roadmap

Amazing job guys for building this product, overall it was super smooth and the performance is very impressive.
I'm personally curious about the feature roadmap for this product, specifically for native spreadsheet interactions available on Google Sheets/Excel like the following:

Ctrl/Command + Click for multiple disjointed cell selection
Select + Drag to copy values across multiple cells
Drag to resize columns and rows

Thank you very much, I'm planning to use react-datasheet-grid and missing these features, it's holding me back from committing to it, otherwise, I love the development experience of it.

Hello @drixta ,
Thanks for your feedbacks ;)
Performance-wise, version 2 is coming up as described in #37 which should drastically improve performance.
Now concerning your points, I'm happy to discuss and find the best approach (this will help speeding up development in the right direction):
Ctrl/Command + Click for multiple disjointed cell selection
I haven't looked into it as I do not see the use-case, but I would be more than happy to think about it if you can justify it with some real-world example.
My first impression is that it makes everything very complicated regarding copy / pasting and Select + Drag. I guess just testing it in Excel might shine some light on the subject.
Select + Drag to copy values across multiple cells
Definitely a very demanded feature that I plan to include in V2. Today you can copy a value and paste it on several rows already, but everyone is instinctively trying to drag the corner...
There might be some tricky use cases:

It only makes sense to drag vertically right? DSG is column-based and dragging a date into a number for instance does not make sense.
What if you select several rows and drag it down? Should just duplicate the last value?

Not quite sure how the API should allow customizing the behavior of this.
Drag to resize columns and rows
Today column size is defined in flex with a min and max width. How do you imagine the API would be to support this resizing feature?

Ctrl/Command + Click for multiple disjointed cell selection
I haven't looked into it as I do not see the use-case, but I would be more than happy to think about it if you can justify it with some real-world example.

For this feature, I would agree that even though the feature exists for Excel and Google Sheet, it isn't a critical one for my use case.

Select + Drag to copy values across multiple cells
Definitely a very demanded feature that I plan to include in V2. Today you can copy a value and paste it on several rows already, but everyone is instinctively trying to drag the corner...

It only makes sense to drag vertically right? DSG is column-based and dragging a date into a number for instance does not make sense.
What if you select several rows and drag it down? Should just duplicate the last value?

I think the drag should just copy the underlying data as string and let the renderer decides on what to do with the data.

Not quite sure how the API should allow customizing the behavior of this.

I don't think for now, you'll need any customization for this feature.

Drag to resize columns and rows
Today column size is defined in flex with a min and max width. How do you imagine the API would be to support this resizing feature?

You could potentially do flex: 0 0 100px for columns to set the width. As for api, width and defaultWidth could be 2 attributes to add to the column data.

Hello @nick-keller,
This is absolutely great work!
I was thinking about using the React Table library https://react-table.tanstack.com/
But now I think I will keep my eyes on your solution.
But in order to outbid React Table I think we all need more basic features like React Table has.
For example: sub-headers, expanding, row drag&drop (actually with your rows copy/paste it is now possible)
See more example: https://react-table.tanstack.com/docs/examples/basic
Thanks for your effort.

Thanks for the feedbacks,
Today the best way to help (besides writing PRs of course 😜 ) would be to write some specs for the features you think are missing.
The most difficult part I think is designing the API trying to balance simplicity and flexibility.
I'll open some issues, feel free to contributes with ideas!

@Limurezzz can you please create issues for "sub-headers" and "expanding", I'm not sure I understand what you need.


Code | Alphabetic Pattern 91

@aryashah2k kindly assign this one to me.

@aryashah2k kindly assign this one to me.


OSSL_CMP_MSG_read(): Fix mem leak on file read error

SSIA

This pull request is ready to merge

Merged - thanks @paulidale and @t8m for the quick approval


Fixing broken links in the security section

I had problems with the merge conflicts so created a new PR - https://github.com/wunderkraut/WunderWay/pull/66


Allow adding extra curl args while keeping default behavior

We use curl commands to validate the curated packages installations in E2E tests. The default command used is just curl <endpoint>, but this was changed to curl -I <endpoint> (which gets only curl headers) in #7332 for fixing ADOT tests, which caused other packages to fail since they expect output present in the full curl output. This PR allows to pass in custom  curl options to the ValidateCurlEndpoint method so that each package can customize how the curl command is run.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve
/woof

/lgtm

/approve


Prevent borrowing from the current module

e.g.: When attempting to borrow a series for Architectural Engineering, if should only be possible to borrow a series from any module except Architectural Engineering. (The current module should not show up in the borrowing modal)

Reassigning to @oszkarnagy to tell us what should be showing up instead.

Assigning to @bp323 for review

Changes Unknown when pulling 7f193ac4d81a10574dbe9f8e974f9f5030746f72 on Coenego:issue-303-prevent-borrowing into ** on CUL-DigitalServices:master**.