feat: detect target branch using standard Git configuration

The current code forces the user to choose a single target branch which
prevents stacks from working on multiple target branches. This leverage
the standard git configuration to retrieve the target branch.
Change-Id: Ia1455d68eaa76af503b6e6cf4c24c19efcdd9b7b

This pull request is part of a stack:

feat: detect target branch using standard Git configuration (#388) 👈


multi_json 1.5.1 breaks object decoding

Commit that broke CouchRest:
https://github.com/intridea/multi_json/commit/193e28cf4dc61b6e7b7b7d80f06f74c76df65c41
Security issue:
http://seclists.org/oss-sec/2013/q1/283
CouchRest method that is now broken:
CouchRest::RestAPI#parse_response
Steps to recreate:
Update multi_json from 1.5.0 to 1.5.1. Instead of a Ruby object parsed from the JSON.create_id field, CouchRest#get now returns a Hash.
Workaround:
I couldn't figure out how to best fix the CouchRest code, but this monkey patch can be used as a workaround:
module JSON
  class << self
    alias :old_parse :parse
    def parse(json, args = {})
      args[:create_additions] = true
      old_parse(json, args)
    end
  end
end

The CouchRest.decode_json_objects attribute supports this now. Closing.


Added Azure.PostgreSQL.AADOnly

PR Summary
Fixes #2227
Added Azure.PostgreSQL.AADOnly rule.
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] Change is not breaking
[x] This PR is ready to merge and is not Work in Progress
Rule changes

[x] Unit tests created/ updated
[x] Rule documentation created/ updated
[x] Link to a filed issue
[x] Change log has been updated with change under unreleased section

Other code changes

[ ] Unit tests created/ updated
[ ] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

@BernieWhite Let me know. I've used databases instead of servers in the synopsis, same in the other PR. I felt it might made more sense, correct me if I am wrong.


Mongo support

Hi @arcuri82, I updated all the controllers with the new method getMongoConnection which is used to get the MongoClient and insert data into db. With this change, gestaohospital should now show an improvement in the experiments. @jgaleotti and I were able to reproduce errors and we are working now on finding solutions. Thanks!

@hghianni thx ;) see minor comments.


[postgres] Postgres CDC Connector support automatically identify newly added tables

Postgres CDC support automatically identify newly added tables.
close #2397

Closing this PR as it has been resolved in #3024.


Plot.save fails mysteriously if node is not present

Repro steps:

Remove node from the machine (if present). I renamed /usr/local/bin/node to node_bak.
Run the following Python code:

import turicreate as tc
sf = tc.SFrame.read_csv('https://docs-assets.developer.apple.com/turicreate/datasets/tc-clang-format-results.csv')
plt = tc.visualization.columnwise_summary(sf)
plt.save('/Users/zach/Desktop/temp.svg')

Expected:
A friendly error message about requiring Node.js (with a link to download).
Actual:
sh: node: command not found

Additionally, no file is written at the location specified.

Thanks a ton for pointing this out!


Show file when staged to add but deleted in working tree

This is the fix for https://github.com/eclipse-theia/theia/issues/7789 .
If a file is created, then staged, then deleted, it is still staged for add (being in the index) and will be included in the commit.  Changes that have been made to the working tree but not staged will not be included in the commit, this includes the deletion of the file.
In this screenshot Untitled2.txt is now shown added in the staged area and deleted in the unstaged area.  Before it was not shown in either area, even though the add was being included in the commit.

I've pushed a second commit to also fix the problem where a file is deleted, staged, then re-created in the working tree.  It now shows as D in the staged area and U in the unstaged area.  See CONTRIBUTING.md

This is the fix for eclipse-theia/theia#7789 .

Can you add a test for it?
Also, aligning the implementation with GitHub Desktop would make sense: https://github.com/desktop/desktop/blob/3551d3742753b85084a165c46ac582a4be5fd090/app/src/lib/git/status.ts#L255-L297

I was wondering where the offending code came from.  It looked like it was fixing someone's bug but it certainly was not fixing any bug in Theia.

aligning the implementation with GitHub Desktop would make sense

Not really.  GitHub Desktop presents a simpler interface to the user.  It does not show staged changes and unstaged changes.  It just presents all the changes in a single list, each file listed once only, and has check-boxes to select which files will be committed.  My 14 year old son says he won't use GitHub Desktop because it is too simple for his needs.  Theia, however, is designed to show staged and unstaged changes correctly, like vs-code, git-gui and git-kraken.
Definitely best to return the status information as git does.  Consumers can do this funky merging of staged and unstaged states if they want, but dugite-extra should not do this because then the information is lost and consumers can't present staged and unstaged states correctly
I'll get the test done tomorrow.

I said I would get the tests done last week but the tests have shown up more work.  I'll get back to this as time permits, hopefully this week.

Excellent, please name me here when it's ready for the review, and we roll out a new release. Thank you!

Hey @westbury any updates on this? :)

Hey @westbury any updates on this? :)

@RDIL sorry, it has been a while.  I'll put something in on Wednesday, in a couple of days.

See https://github.com/eclipse-theia/theia/pull/8221 .  That PR may obsolete this one.


[Components: Controls] SelectField

Allows selection of one or several items from the drop-down list. Allows you to type the item name in order to filter the available data (including requesting from the server).
Use Ant Design Select.
e2e tests required.

import {SelectField} from @haulmont/react-antd;
Use in place of
test-pup/example-react-app/form-controls/select-field.test.js


Make DDL distribution more robust

Do not allow DDL to be updated post-activation
Include a DDL comparison as part of the claimant-driven activation process so that if messages are delayed the claimant doesn't accidentally validate a node who has compiled an earlier version of the DDL but has yet to receive the later version

Requires basho/riak_core#790

Manual test that I'd like to turn into a formal one:

Define a bucket type via the cli
Wait until all nodes have had time to see/compile the beam
Retrieve the DDL from cluster metadata

DDL = riak_kv_compile_tab:get_ddl(BucketType)

Run the command sequence below via riak attach
Tweak the DDL term
Run the rpc:multicall again with the new DDL

{ok, Ring} = riak_core_ring_manager:get_my_ring(),
Nodes = riak_core_ring:all_members(Ring),
rpc:multicall(Nodes, riak_core_metadata_evt_sup,  is_type_compiled, [BucketType, DDL]).

:+1: 4224b26

@borshop merge


Use justfile to run commands

Yes makefile is more portable, but justfile is more modern and has plenty of nice features.
So I am not suggesting we rely heavily on just, yet, I would like to use it as a helper to launch many cli commands at once, and keep it as simple as possible, so we could bail out whenever we don't like it.

I don't have any experience with just but I'm up for giving it a try

Me neither. This will be the first time I use it.
I don't want to use it in a sophisticated way; I want the simplest thing so we could switch easily if we regret it :)


[CT-764] Persist Column level comments when creating views

Describe the feature
The persist_docs config works for tables by materializing a model as a table and then running ALTER TABLE statements to update the comment on each column. This method does not work for views because ALTER VIEW doesn't support adding comments. Instead, comments need to be defined when running the CREATE OR REPLACE VIEW statement. There should be an option to handle column level comments for models materialized as views.
I originally opened this issue in dbt-databricks but they told me to open it here instead
Describe alternatives you've considered
I tried creating a macro that adds the necessary comment clause and put it at the top of my model but the SQL gets inserted after the AS in CREATE OR REPLACE VIEW AS
Who will this benefit?
This will benefit anyone using column level comments on views in databricks
Are you interested in contributing this feature?
Yes! I've created a macro to do this. Attaching below:
{# This macro replaces the regular create view macro databricks uses to create views #}
{# The goal of this macro is to persist column level comments #}
{# In general, dbt will only add or update comments on columns for tables. It does this by creating the table and then running #}
{# alter table <tbl> change column <col> comment <comment> #}
{# But there's no corresponding option to add/update comments on columns for views. So column level comments don't get applied #}
{# However, it is possible to assign comments on view columns when creating the view by running #}
{# 'create view <view> (col_1 comment <comment>, col_2 comment <comment> ...)'. Call this extra sql the 'column_comment_clause' #}
{# This macro does just that- it edits the DDL run by dbt to include the column_comment_clause #}
{# The simple approach would be to edit the ddl used when creating views by just inserting the column_comment_clause, but this runs into some issues #}

{# Macro Breakdown: #}
{# 1. aggregate_cols, a macro that returns a list of columns and descriptions to reference when generating the column_comment_clause #}
{# 2. column_comment_clause, a macro that checks if the model has the persist_docs config set to True for columns and generates the column_comment_clause_sql #}
{# 3. comment_clause, a macro that is unchanged from the original create view macro. This generates the view level comment #}
{# 4. databricks__create_view_as_with_comments, the main macro we're 'overwriting'. This generates the 'create view ...' sql #}
{#    To help apply this macro more easily in dbt_project.yml, this macro first checks if the model is being materialized as a view #}
{#    Then, it inserts the column_comment_clause into the view ddl #}

{# This macro works by: #}
{# 1. Getting a list of columns in the model in the same order as the select clause #}
{#    The column_comment_clause must list the columns in the same order as the select clause, otherwise comments will be applied to the wrong column. #}
{#    In order to get the columns in the correct order, we run a 'DESCRIBE TABLE <tbl> and store the results in a variable, ddl_column_names.' #}
{# 2. Iterating over the column names in ddl_column_names adding them to a dict called ddl_column_dict_list that we'll reference in the column_comment_clause #}
{# 3. Getting a list of columns and their descriptions from a model's associated yml file using 'model.columns.values()' #}
{# 4. Searching for column name matches between the ddl_column_dict_list and model.columns.values() #}
{#    When we find a match, we update ddl_column_dict_list with the column description.  #}
{#    Doing this ensures that our columns and descriptions retain the correct ordering #}
{# 5. Iterating over ddl_column_dict_list and adding a generic 'missing description' message to any columns missing comments in the yml #}
{#    If we didn't do this then the ddl wouldn't compile since all columns need to have descriptions (descriptions can be blank) #}
{# 6. Checking that the model has the persist_docs config set to True and escaping single quotes in column desriptions #}
{# 7. Generating the create view ddl and adding the column_comment_clause #}
{# 8. Checking if the model is being materialized as a view. If it is then the ddl gets run, otherwise the macro exits #}
{#    We perform this check to make it easier to apply this macro in dbt_project.yml #}
{#    That way, even if some models in a path are being materialized as tables and some as views, this will only run when appropriate #}

{# Important Notes #}
{# This macro must run as a post hook. This is necessary to ensure any new or removed columns get included or excluded form the column_comment_clause#}
{# If the macro only ran as usual then the 'DESCRIBE TABLE...' query would only include the columns that were ALREADY in the model #}
{# It wouldn't account for columns you've added or removed, the resulting column_comment_clause would have the wrong number of columns, generating an error  #}
{# dbt has some weird syntax when calling macros that use {{this}} in post hooks. See https://github.com/dbt-labs/dbt-core/issues/2370 #}
{# As a result, the correct syntax to use is (quotes and whitespace included): " {{ databricks__create_view_as_with_comments(this, sql) }} "  #}

{# How to use this macro #}
{# 1. Add this sql script to your macros folder #}
{# 2. Add the post hook in the usage notes to either your model config or dbt_project.yml #}

{% macro aggregate_cols(sql) %}
    {% set ddl_column_dict_list = [] %}
    {# Step 1. generate DESCRIBE TABLE statement to get columns in same order as select clause  #}
    {% set existing_cols_query %}
      describe table {{this}}
    {% endset %}
    {% set col_query_results = run_query(existing_cols_query) %}
    {% if execute %}
      {# Return the view's column names and assign to variable  #}
      {% set ddl_column_names = col_query_results.columns[0].values() %}
    {% endif %}

    {# Step 2 #}
    {% for ddl_col in ddl_column_names %}
      {% do ddl_column_dict_list.append({"name":ddl_col, "description":""}) %}
    {% endfor %}
    {% for ddl_dict in ddl_column_dict_list %}
      {# Step 3 #}
      {% for yml_col in model.columns.values() %}
        {# Step 4 #}
        {% if ddl_dict["name"] == yml_col["name"] %}
          {% do ddl_dict.update({"description":yml_col["description"] }) %}
        {% endif %}
      {% endfor %}
      {# Step 5 #}
      {% if ddl_dict["description"] == "" %}
        {% do ddl_dict.update({"description":"No Description in yml" }) %}
      {% endif %}
    {% endfor %}
    {{return(ddl_column_dict_list)}}
{% endmacro %}

{% macro column_comment_clause() %}
  {# Step 6 #}
  {%- set raw_persist_docs = config.get('persist_docs', {}) -%}

  {%- if raw_persist_docs is mapping -%}
    {%- set raw_relation_column_comments = raw_persist_docs.get('columns', false) -%}
      {%- if raw_relation_column_comments -%}
      (
        {% for col in aggregate_cols(sql) %}
        {{col["name"] + ' comment ' + "'" + col["description"] | replace("'", "\\'") + "'" }}
        {% if not loop.last %},{% endif %}
        {% endfor %}
        )
        {% endif %}
    {%- elif raw_persist_docs -%}
      {{ exceptions.raise_compiler_error("Invalid value provided for 'persist_docs'. Expected dict but got value: " ~ raw_persist_docs) }}
    {% endif %}
{% endmacro %}

{% macro comment_clause() %}
  {%- set raw_persist_docs = config.get('persist_docs', {}) -%}
  {%- if raw_persist_docs is mapping -%}
    {%- set raw_relation = raw_persist_docs.get('relation', false) -%}
      {%- if raw_relation -%}
      comment '{{ model.description | replace("'", "\\'") }}'
      {% endif %}
  {%- elif raw_persist_docs -%}
    {{ exceptions.raise_compiler_error("Invalid value provided for 'persist_docs'. Expected dict but got value: " ~ raw_persist_docs) }}
  {% endif %}
{%- endmacro -%}

{% macro databricks__create_view_as_with_comments(relation, sql) -%}
  {# Step 7 #}
  {%set model_materialization = config.get('materialized') %}
  {%set sql %}
    create or replace view {{ relation }}
    {{ column_comment_clause() }}
    {{ comment_clause() }}
    as
    {{sql}}
  {% endset %}
  {# Step 8 #}
  {% if model_materialization == 'view' %}
    {% do run_query(sql) %}
  {% else %}
  {%endif%}
{% endmacro %}

Perhaps it should be classified as a "bug" rather than an "enhancement" because there is currently no word in the docs about this limitation and I'd argue that it is quite unexpected for the user (it took my quite a while to figure out that it's not me doing something wrong and arrive here).

Any plans or timelines that could be shared, @jtcohen6?

Sorry for the delay in following up here!
I think we'd need to implement this similar to how we implemented persist_docs for views on Snowflake in dbt-snowflake==1.0. On that platform, we also don't have the ability to run alter / comment statements after a view is created. Instead, we need to run the model SQL first, with where false limit 0, just to introspect the column schema of the query result, and then provide that full column schema plus user-provided descriptions to the actual create view as statement.
Relevant code is here. The specific entry point within the create_view_as macro looks like:
    {% set query_columns = get_columns_in_query(sql) %}
    {{ get_persist_docs_column_list(model_columns, query_columns) }}

I'm going to mark this as help_wanted, since I think this could be contributed by a community member, following that same basic implementation. In the meantime, I have updated the docs to reflect that this is not supported (https://github.com/dbt-labs/docs.getdbt.com/pull/1666).

Wouldn't it be better to run a DESCRIBE SELECT ... for the introspection purposes?

Commenting so the issue wouldn't be closed. Btw, on Databricks I see some field descriptions synced while others not now 🤷.

We have several column descriptions that are persisted from table models downstream in the pipeline. This is nice since we don't need to rewrite the same definitions in multiple yml files. When using the macro suggested in this issue, I don't think these descriptions persist. Also something to take into account in the final solution.

created PR(https://github.com/dbt-labs/dbt-spark/pull/866) according to @jtcohen6 suggestion

Closing; this has been backported to v1.5 and released to PyPI.

The documentation still points to this as an issue.  https://docs.getdbt.com/reference/resource-configs/persist_docs#support

@mikealfare, just a quick note the documentation website still says views are not supported: https://docs.getdbt.com/reference/resource-configs/persist_docs


Filter Should De-emphasize, Rather than Hide Icons

Describe the problem
When you search for, or filter a location, everything filtered out disappears, which makes you lose context.
Describe the solution
Instead, turn filtered-out to white icons, with a thin colored outline. This will de-emphasize them, while still providing context I'm pretty sure these have been designed. Touch base with Maria on Slack.
When you zoom out, filtered-out dots should also turn white with a thin outline.
Additional context and instructions

Just so you know, this will be a fairly large change, because it will change the underlying way the map works and also basically mean that all cases will be shown at all times. So I imagine this might take a bit of time to think through and implement

Cool.  :-)

One thing to also consider is that this is the way the SVI Slider will work. So it may be worth building the SVI slider component as a part of this issue... or at least the viewing portion.
Implementing SVI on intake, or the equation to equally split a non-linear curve into equal parts will be a separate issue.


[BUG] remove # from tags within YAML frontmatter does not work

The purpose of removing # from tags within  frontmatter is aimed at restoring valid YAML code.
Linter however only seems to act when the frontmatter already is valid YAML code. A catch 22.
Tried several ways could not make it work.

fixed now, thanks


ssh private key no password not working

Can't get app to work with private key used by ConnectBot app on Note 4.

What kind of private key is it? Standard OpenSSH / PKCS keys are working.

Just bitten by the same issue: It seems an ssh password is required. If you leave the ssh password field empty, you can't exit configuration. Or is the password used to unlock the private key instead? If so, where can the app be configured to use a key for login?

There is a dropdown in the configuration dialog where you can choose between

password authentication
private key auth
password protected private key auth
Am 30.05.2016 09:14 schrieb "vasyugan"<EMAIL_ADDRESS>

Just bitten by the same issue: It seems an ssh password is required. If
you leave the ssh password field empty, you can't exit configuration. Or is
the password used to unlock the private key instead? If so, where can the
app be configured to use a key for login?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/eidottermihi/rpicheck/issues/122#issuecomment-222427065,
or mute the thread
https://github.com/notifications/unsubscribe/ACpuQHvVDigDOdTEePU_xDS0p8XVIr8eks5qGo5LgaJpZM4IDluo
.


Require disk statistics paramters like '% Disk Time' and '% Idle Time'  for linux system.

We are capturing system statistics and this library is being very helpful for that. We are capturing data for windows and linux system.
We want to capture data for disk statistics with below parameters:
1) % Disk Time - Percentage of time the disk is processing read or write request.
2) % Idle Time - % of time it was idle.
3) Disk Read Bytes/sec - disk read bytes per second (I suppose avaiable in si.disksIO() - rIO )
4) Disk Write Bytes/sec - disk write bytes per second(I suppose avaiable in si.disksIO() - wIO )
Of out above 1) and 2) are not available in library for linux system, we have captured the same for windows system using  powerShell commands as explained in "(https://github.com/sebhildebrandt/systeminformation/issues/138)".
Can you please check point 1) & 2) if it can be available for linux system.

@hk4git will have a look on it ... please give me some time to make a research.

@hk4git will have a look on it ... please give me some time to make a research.


Where did the estimated installation time go?

I don't think I have my terminal colors configured in a strange way, but I haven't been able to see the estimated installation time since the install progress bar got all "fancy":

It used to be the same color as the x/y count.

On this project I am using 6.x.

It's black — which should be off-black in your terminal. This is only on Python 3.

make your black a dark grey and everything will look much nicer :)

I get why the unfilled boxes are "off-black", but why is the time estimate?

FYI: I think I'm using one of the default iTerm themes.

i believe i am as well.

I can sort of see the estimate when that tab is in the background:

it's not going to change.

Readability of some of the other text with a light theme isn't so good either:

(iTerm "Light Background")

Everyone should stop using themes which have illegible text colors configured. If you find yourself in this situation, tweak the colors of your theme. Your terminal theme should not allow text to be illegible.

On Sep 22, 2017, at 10:25 PM, Josh Friend<EMAIL_ADDRESS>wrote:
Readability of some of the other text with a light theme isn't so good either:
(iTerm "Light Background")
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

PIPENV_COLORBLIND is always an option as well.
FWIW, I am also using the default iTerm2 preset which is default all black. I switched to 30% Grey which makes it more visible.

i recommend changing black, instead of your background.

I find it amusing that people would give a 'thumbs down' for being given the advice to change a setting if it is resulting in a color you can't read.  Terminal colors are 100% in the control of your color theme.  If you picked a color theme that ignores the legibility of certain colors, then you need to fix it.

Because people should not have to know about how to configure ANSI colors in their terminal to figure out why they cannot read the output from a tool that is supposed to be easy to use.

People should have properly configured terminals. If there's a way to detect that the background is white, i'm all ears. otherwise, it's staying.

FWIW, I just set up a new MacBook with iTerm using the default theme and can't see some of the text. I think we're going to be dealing with thousands of users every month "using themes which have illegible text colors configured".
Maybe some would consider this a change request for iTerm, but if pipenv is to be ubiquitous, I think it should behave nicely in the the common cases.

We've vastly improved this. The count-down timer is a nicety, and far from required.
I'm more than fine with it only being shown to people who have their terminals nicely configured.

Not to mention, it's far from accurate, so not showing it a lot of the time might be a feature, not a bug :)

I just started using pipenv and find the colors make its output completely unreadable. It's not only about the missing UI elements: I've seen many programs which look like pipenv, and it's always been a case of the developer testing on one particular colorscheme (often Solarized). But it's a new level of arrogance to not even acknowledge this bug and suggest that all other colorschemes are wrong.
If you want to argue that my color scheme is wrong, you can take that discussion up with the scheme's authors. Maybe you write a mailing list post somewhere to change the default colors of the Linux TTYs while you're out there. But as a user I certainly don't want to die on the hill of discussing whether black should really be black. I want to use a development tool for writing my Python program.
I guess I will set PIPENV_COLORBLIND before I become colorblind for real.

Y'all realize terminals do more than just carefully pre-crafted themes right?
For example, some people do things like randomized terminal background colors. We can imagine other use cases, like background commands changing terminal color to signal something to the user. Etc. Terminals are often flexible and programmatically controllable, and the range of uses is wide.
And it's fine if you just say "we don't wish to or simply cannot support those use cases, because they're too hard and variable to get right". Heck, you can even argue justifiably that a solution which changes terminal background colors ought to also change all the other standard colors too. You'd need to be compassionate for how that's inherently technically harder for a user, but it's a sound argument from a software design/engineering/architecture perspective.
But don't be dickishly dismissive just because the only use cases you can conceive of are ones where the obvious solution is to just configure black to be something other than literal black.

Actually, it is wrong to assert that the users/themes are responsible for making all their foreground colors readable on the default background.
It is just as defensible to say that the program has the responsibility to simultaneously change the background color if it is changing the foreground color!

When you come to a website you expect it to set the background color it needs. It would be considered unacceptable for a website to let your browser/user default CSS set the background color, hardcode black for the text color, and then blame you when it wasn't visible just because your user CSS is a dark theme.
This is admittedly further from the conventions we are used to with command-line tools - we don't expect a CLI tool to change the terminal background color for the duration of its entire output! - but it is not obviously or automatically wronger that way. Just different.
There are reasonable tradeoffs to this approach. Tools which change the terminal background color for the duration of their run need to be mindful to set it again after executing any external command which might also do so. On the other hand, this makes it vastly easier to see where the output of one command ends and the output of another command begins.

Alternatively, command-line tools that use color have the responsibility to be themable.
This is also pretty defensible. Maybe even more defensible than either of the other stated positions. It's not even technically hard, and it would give users flexibility to resolve problems like this while still freeing the default/preferred implementation to implicitly assert things like "if black is not visible on your background that's your problem".


[LIGHTNODE] ReDeploy LightNode Sales contract and updates config in CW, backend script

steps

[x] deploy contract
[x] create job
[ ] new vyper contract vote
[ ] once vote finished, then update job id
[ ] set paloma
[ ] set promo code
[ ] sync paloma address in vyper contract
[ ] update db network field
[ ] update nodesale contract address in fiatfactory contract
[ ] reenable the base chain in backend api
[ ] update address in frontend side, api side

deployed nodesale smart contract
arb - https://arbiscan.io/address/0x249cE7e8c5A0f7300f9c45Af70c644b39dABa4dB#code
eth - https://etherscan.io/address/0x8050371F14Bb6E2395E936611615BE41237faF02#code
bsc - https://bscscan.com/address/0x2f78AfAdD7E58052c4a8789dc01A1eD49848cc0C#code
matic - https://polygonscan.com/address/0x496C48d24a33B1Fd45782537eBd42157Bf265703#code
base - https://basescan.org/address/0x2f78AfAdD7E58052c4a8789dc01A1eD49848cc0C#code
op - https://optimistic.etherscan.io/address/0x496C48d24a33B1Fd45782537eBd42157Bf265703#code

created job with new nodesale address
ethnodesale15 - 5DFE5958BC34B79976F132DF4CCD333F4779FEED3BF9882AC7600EA8D5C4D155
arbnodesale15 - B192906651549D0294C8679AC908955D05FE0274F1A70295D1964A53AB484B05
bnbnodesale15 - 4C9ED5C5EAB8E29EF249A3EC09513A40BDC4572DEE82CC7C74DC71063F367BEA
maticnodesale15 - 0AD7D67D15A45B3685A9C5242CAB1D6A9B2722A1FD15676145843D6FDC84CDE7
basenodesale15 - 08C387EE83287C04150462C9989C0511E9F8C1F5144F5575D8DE37DF2E6A852C
opnodesale15 - DC7E6A6FF67B8DE135E05947F45A67EA35EC44FA0EB17240D28F7C22FDE4F5A5

sync failed in matic, bnb chain


gcc45 fails to build on Mac OS X 10.11.2

gcc45 fails to build on Mac OS X 10.11.2
configure: error: unsupported system, cannot find sizeof (omp_lock_t)
make[2]: *** [configure-stage1-target-libgomp] Error 1
make[1]: *** [stage1-bubble] Error 2
make: *** [bootstrap] Error 2
https://gist.github.com/ahyattdev/19cc744fb9f9d17362f6

configure: error: unsupported system

That suggests it's simply too old to build on El Capitan.  If you want to ask the GCC developers if they'll consider releasing an updated 4.5.x that'd be great, but I'm afraid there's probably nothing we can do otherwise.

Thank you for clarifying.

I know it's too late but maybe it will help someone else.
Download Xcode6 and use xcode-select -s to switch to it. Also, if it's a clean installation of 10.11 (not upgrade), you'll need to do cd /usr/local/lib && ln -s ../../lib/libSystem.B.dylib libgcc_s.10.5.dylib. Then you gcc45 will install successfully.


Incorrect opening selection

Current Behavior

When you select the right element, the list from the left opens.
Expected Behavior

    <DemoContainer>
        <CardsReportIssue />
    </DemoContainer>

    <DemoContainer>
        <CardsReportIssue />
    </DemoContainer>

Steps To Reproduce
When you select the right element, the list from the left opens.
Link to Reproduction / Stackblitz (reproduction template)
No response
More Information
No response

Oh it looks like we're rendering that component twice! Will fix!

It's because you are rendering the same component, and the example component has an id associated with it, so you need to make sure they have unique IDs, or don't pass one at all and one will be automatically generated for you.


feature/coding standard

Hello!
This PR introduces php-cs-fixer to fix and check for PSR2 compliance.
I've also removed the outdated composer.lock file as it's not necessary for libraries to commit it to source.
In addition to this, I've added make targets covering fix and test, where all runs both targets.
Thanks,

This is awesome! Thanks @anthonysterling!


IFTTT (If This Then That) Integration

I would love to see IFTTT integration it would make Jasper's possibilities endless.
This is purely a suggestion, I currently do not have to knowledge on how to achieve / code this.

@Verpz  you should check this for running IFTTT in pi with Jasper you have to create module for this check out Documentation section for more help..
1).  https://github.com/enkydu/raspi_runner
2). http://jasperproject.github.io/documentation/api/standard/


Customize the style of index pages

Feature Request
Is your feature request related to a problem? Please describe.
Currently, the style of a specific instance of a widget can be customized with CSS, using the following syntax:
advanced:
  css_style: ''
  css_class: ''

There's no way to customize the style of a specific index page (like post/_index.md), such as adding for example a gradient background, as they use the common .page-body class, shared by many other parts of the theme.
Describe the solution you'd like
To be able to customize the style of our index pages with CSS in a similar way as it's possible now with specific instances of a widget.

I'm still interested in this. Will try to take a look at it to see if it's easy to implement


Add VNA APIs

What does this Pull Request accomplish?
Adds VNA support
Why should this Pull Request be merged?
Adding this as a part of WI: User Story 2787958: Generate  gRPC server code for RFmx VNA
What testing has been done?
PR + built output in grpc-device

Please review this PR as we need this to go in before release branch is created for ni-central.
@reckenro @astarche


[Feature]: Grouping pages for navigation

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
Creating a group
Deleting a group
Ungrouping
Adding homepage to group
Related
https://github.com/appsmithorg/appsmith/issues/17766

Duplicate of #2282


Reordering values in view results

We need a way to reorder values in the result of views.
For example, given the following view:
Question            gender
Values              @
Question    Values
q1          1       7.201447
            2       9.64925
            3       55.662665
            4       72.663656
            5       4.704566
            6       11.496034
            7       21.69883
            8       3.178551
            9       0.099151
            96      2.199429
            98      2.497416
            99      8.949005

We need a way to specify a new values order in the index. For example, in this case the values 1-9 have been reversed.
Question            gender
Values              @
Question    Values
q1          9       0.099151
            8       3.178551
            7       21.69883
            6       11.496034
            5       4.704566
            4       72.663656
            3       55.662665
            2       9.64925
            1       7.201447
            96      2.199429
            98      2.497416
            99      8.949005

I'll implement this using column meta tags that are picked up by paint_dataframe.

I've implemented this in a new meta object called rules, using an option called slicex.
The rules object is a dict with x and y keys for axis-specific rules application. Internally slicex results in a call to a function of the same name. The contents of the slicex object becomes that function call's kwargs.
def slicex(df, values, keep_margins=True):
    """
    Return an index-wise slice of df, keeping margins if desired.

    Assuming a Quantipy-style view result this function takes an index
    slice of df as indicated by values and returns the result.

    Parameters
    ----------
    df : pandas.DataFrame
        The dataframe that should be sliced along the index.
    values : list-like
        A list of index values that should be sliced from df.
    keep_margins : bool, default=True
        If True and the margins index row exists, it will be kept.

    Returns
    -------
    df : list
        The sliced dataframe.
    """

Given the following crosstab:
print crosstab(meta, data, 'income', 'income_cb')

Question                income_cb
Values                        All    1    2    3    4    5    6   7   8   9   10   11   12  901  902  903
Question    Values
income      All              2078  425  204  187  146  119  103  89  68  59  226  101  351  425  848  353
            1                 425  425    0    0    0    0    0   0   0   0    0    0    0  425    0    0
            2                 204    0  204    0    0    0    0   0   0   0    0    0    0    0  204    0
            3                 187    0    0  187    0    0    0   0   0   0    0    0    0    0  187    0
            4                 146    0    0    0  146    0    0   0   0   0    0    0    0    0  146    0
            5                 119    0    0    0    0  119    0   0   0   0    0    0    0    0  119    0
            6                 103    0    0    0    0    0  103   0   0   0    0    0    0    0  103    0
            7                  89    0    0    0    0    0    0  89   0   0    0    0    0    0   89    0
            8                  68    0    0    0    0    0    0   0  68   0    0    0    0    0    0   68
            9                  59    0    0    0    0    0    0   0   0  59    0    0    0    0    0   59
            10                226    0    0    0    0    0    0   0   0   0  226    0    0    0    0  226
            11                101    0    0    0    0    0    0   0   0   0    0  101    0    0    0    0
            12                351    0    0    0    0    0    0   0   0   0    0    0  351    0    0    0

Set up the slicex rules:
meta['columns']['income']['rules'] = {
    'x': {'slicex': {'values': [1, 3, 5, 7, 9, 11]}}
}

meta['columns']['income_cb']['rules'] = {
    'y': {'slicex': {'values': [12, 10, 4, 6, 2, 901, 902, 903]}}
}

Apply the rules using crosstab:
print crosstab(meta, data, 'income', 'income_cb', rules=True)

Question                income_cb
Values                        All   12   10    4    6    2  901  902  903
Question    Values
income      All              2078  351  226  146  103  204  425  848  353
            1                 425    0    0    0    0    0  425    0    0
            3                 187    0    0    0    0    0    0  187    0
            5                 119    0    0    0    0    0    0  119    0
            7                  89    0    0    0    0    0    0   89    0
            9                  59    0    0    0    0    0    0    0   59
            11                101    0    0    0    0    0    0    0    0

The rules object also supports sortx (#15) and dropx (#18), all of which may be used in any combination.

When drawing chains out of a stack, rules can be applied to what is extracted in the same way:
chains = stack.get_chain(..., rules=True)

rules will currently only be applied to chain items if the parameter post_process is also True (which it is by default).

Resolved by #40


Support file paths in CLI invocations of scripts

Allow paths without quotes, allow paths to inputs.

could you add examples of what you are trying to do?

Here are some examples of the failure.  I'm in a directory tmp, I have a local .env file (same directory).  I have another directory ..\inputs with 2 pdf files in it.  I'm trying to run a script with the files in inputs as inputs to script.

npx --yes genaiscript run .\gen-tweet.genai.js ..\inputs*.pdf
no files matching ..\inputs*.pdf
npx --yes genaiscript run .\gen-tweet.genai.js "..\inputs*.pdf"
no files matching ..\inputs*.pdf

If the files are local to the current directory, it works:

npx --yes genaiscript run .\gen-tweet.genai.js *.pdf
prompting model gpt-4
undefined
"Discover GenAIScript: a new language integrating AI into scripting, making LLMs accessible for robust, innovative software development! #AI #Coding"undefined
undefined
"Discover GenAIScript: a new language integrating AI into scripting, making LLMs accessible for robust, innovative software development! #AI #Coding"
genaiscript generated 32 tokens

(Also, not sure where the "undefined" output is coming from)

Fixed by https://github.com/microsoft/genaiscript/commit/9525ecd25bcec5c6b52cc411fdc47256155a1553


SCRUM-2248 Fail loads with invalid URL with correct status

@markquintontulloch not sure if this fully fixes the issue... or what happens when there is an error... but at least there will not be any null pointers.


No way to refer project root name

Hi,
I have a project composed of few platforms that looks like the following:

MyProject.Shared
MyProject.UWP
MyProject.Droid
etc.

I need to add a reference in all projects that point to the shared project. The problem is that the generated csproj (for instance in the UWP one) replaces $safeprojectname$.Shared with the full project name, so instead of adding MyProject1.Shared, MyProject1.UWP.Shared is added.
How can I overcome this?

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

ID: 5b76e208-2a2a-9fc3-98ff-147540157f32
Version Independent ID: 5f5c9adf-da1d-ec0b-8af3-ccd2e27eaadc
Content: Create multi-project templates for Visual Studio - Visual Studio
Content Source: docs/ide/how-to-create-multi-project-templates.md
Product: visual-studio-dev15
GitHub Login: @gewarren
Microsoft Alias: gewarren

Isn't that what the ext_ prefix is for, to get the parent's variables?

So you would use: $ext_safeprojectname$.Shared

Yes it does. But it's not mentioned in the docs whatsoever.
Here's my Q/A in SO.

@weitzhandler Thanks for confirming that works. I'll add this to the backlog to update the article.

@rhyous Thanks for providing the solution!


Data Science with Python : Iris Classification

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes #1525

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Datascience with Python

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Please Review my PR😊

Changes to be done :

Instead of ending it abruptly in .ipynb file, show the final outcomes at end of all the algorithms along with accuracies.
Create  a README.md, and write a brief tutorial of your project.

Kindly work on it. @srini047

Yes mam definitely😊

I have done the changes as per your feedback. Please review the PR. If there are any changes to be made do let me know.😊

Mam kindly look into the changes I have updated the ReadME File. @prathimacode-hub


Install MAUI exe on server 2019 not seen the fonts

Issue moved from dotnet/maui#10899

Please respond to @danies8.

From @danies8 on Tuesday, October 25, 2022 2:51:33 PM
Description
Install MAUI exe on sever 2019 not seen the fonts!!!
Steps to Reproduce

Create MAUI app.
Install it as described in this ticket: https://github.com/dotnet/maui/issues/8830
The fonts are not seen.
How do I install the fonts ?

Link to public reproduction project repository
....
Version with bug
6.0.486 (current)
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
...
Did you find any workaround?
No,
How do I install the fonts ?
Relevant log output
No

Issue moved from dotnet/maui#10899

Please respond to @msftbot[bot].

From @msftbot[bot] on Tuesday, October 25, 2022 6:08:18 PM
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

Issue moved from dotnet/maui#10899

Please respond to @danies8.

From @danies8 on Tuesday, October 25, 2022 6:14:25 PM
@PureWeen is there solution for this problem?
If yes how?

Is there any solution for this problem ?
Is it connected to fonts?
If yes how I install the fonts ?

@danies8 we moved this from the .NET MAUI repo to this repo because we believe this is more to do with the various WinUI related APIs. Unfortunately I'm not aware of what the solution is.

I believe this is related to unpackaged apps. I have a repo here with DLSS Swapper. In case I commit to the repo after this post, the last commit I am referring to is 81703296c6a3f48bab7991a440ed79f37738ef14. This app is not MAUI but it is WinUI3.
DLSS Swapper has 4 build configs:

Debug
Debug_WindowsStore
Release
Release_WindowsStore

I have set it up so if you use *_WindowsStore it will load a packaged app, otherwise it loads as an unpackaged app (see xcopy in csproj for how I am doing that).
Debug build looks like: (note the controller icon on the left and refresh icon in the top right)

Debug_WindowsStore build looks like this:

I think that is why this issue is an unpackaged vs packaged.

It connected to unpackaged.

I was able to get around this in the above issue by setting Copy to Output Directory to Copy if newer. I still have Build Action set to Content but it may be ok to move it to None. This was also only tested in debug mode, unsure if release is going to bite me in the bum.
Hope this helps.

What about this issue ? ant time when it will be fixed ?

Any advance,does you fix the fonts in unpackaged app?


Added Questions for Experienced

Please check if this PR fulfills these

[ ] The commit message is descriptive of changes
[ ] You have tried at least one local test (this includes viewing the changes on your local fork)
[x] Docs have been added / updated as needed (for bug fixes / features)

What kind of change does this PR introduce?

[ ] Typo / Doc Update
[ ] Bug Fix
[x] Feature / New Item

What is the new behavior (if this is a feature change)?

[x] Added Interview Technical Question
[ ] Added Interview Whiteboard Question
[ ] Corrected existing items
[ ] Other

Other information:

Hi @malleshthota! Thanks for your contributions! I see what you're going for here, but there are a few issues with this markup.
+Skip to content
 +This repository
 +Search
 +Pull requests
 +Issues
 +Marketplace
 +Explore
 + @malleshthota
 + Sign out
 + Unwatch 1
 +  Star 0  Fork 46 malleshthota/software-interview-prep
 +forked from approachable-io/software-interview-prep
 + Code  Pull requests 0  Projects 0  Wiki  Insights  Settings
 +Branch: master Find file Copy pathsoftware-interview-prep/views/questions/technical/recursion.html
 +2e4dc00  a day ago
 +@k0R73z k0R73z Create recursion.html
 +1 contributor
 +RawBlameHistory
 +48 lines (42 sloc)  2.13 KB

These lines at the top of the views are probably from a copy paste from GitHub. I like the other content, but I won't be able to merge this as is.
The h1 and title tags are also not matching the content. If you make those corrections and resolve the merge conflicts by pulling the latest version of the project into your branch, I'll gladly get this merged in!

Hi @malleshthota! I'm going to close this for now. If you're still interested in following up by making changes to this code, let us know and I can reopen this PR.


174266170 implement pyquil conversions (Orquestra native gates -> pyquil gates)

This implements singledispatch-based approach for converting gate objects to PyQuil.
If this gets approved, I'll add dispatch for Circuit object.
Basic idea: there is convert_to_pyquil function that dispatches on the type of the object passed and converts it to respective representation in PyQuil.

Looks good to me, but I think @simonwa7 should also take a look at that :)


Issue 46: Support for Contained Resources

Description
Resolves #46.
Adds support for Contained Resources by allowing the user to declare a static listing of Resources that will be Contained. Encoder functions are then generated to inline Contained Resources to the Parent resource.
FHIR views Contained Resources as a List having a Resource type. Spark Schema won't meaningfully understand that parent type, so we create a "contained" struct having a field for each declared Resource type to serialize to. Deserialization puts the elements of the Struct back into the FHIR Contained list.
Tests
Tested by adding new unit tests. Ran a Jupyter session testing the extract_entry method over both STU3 and R4 content for bundles having Contained resources.

+1, LGTM!

Merged! Thanks for the review.


When fineturning, if I set max_train_steps=10000, and if Its training was interrupted when steps=5000, can this code support continue training from  steps=5000?

As the title. waiting for your reply, thank you

Not supported, you can try adding that by saving the optimizer state and adding a resume option


Bug: TypeError when calling 'chi_square' argument

Bug
''TypeError: 'bool' object is not callable'' when calling 'chi_square' argument→
Bug-TypeError of chi_square.ipynb.zip
Platform
MacOS Catalina 10.15.1
Python 3.7.1
benford-py 0.2.6

Thanks for reporting it.
I'll check it out

Fixed and included in latest version (0.2.7)
pip install benford_py
should deal with it.
Cheers


chore: require MinGW to build Etcher on Windows

Using MinGW allows us to re-use the build scripts we've been developing
for GNU/Linux and OS X, which are much more robust than their *.bat
counterparts (due to Batch limitations).
This commit does the following changes:

Documents MinGW as a requirement in RUNNING-LOCALLY.md
It setups MinGW in Appveyor CI
Transforms windows/sign.bat into windows/electron-sign-exe.sh
Re-uses dependencies-npm.sh and dependencies-bower.sh in
build/windows.bat

Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

Does this mean that one must download and install the whole MinGW package to build Etcher? If so, it would be optimal if you could streamline this to at least mention what specific components are required, and preferably deliver the executables without installation at all.

I've added a list of packages that we require at the moment (in the middle of the transition), but I'll update the list as we go. Luckily very few packages need to be installed, so I'll investigate if we can somehow ship the binaries with Etcher.

Unless they're very small I'd be :-1: on shipping the mingw binaries with Etcher, but having some kind of externally-hosted etcher-mingw-dependencies.zip file linked to from the instructions would IMHO be okay.

I'm thinking that you could host the executables (in whatever format you choose) in the Amazon S3 storage you already have. The build script could download it as needed.

@WasabiFan I didn't suggest that because I didn't know if they'd need to be "installed" or anything first? If it's just a case of download-extract-execute then yeah it probably would make sense to have them auto-downloaded by the build script (just like the AppImage tool is).
Oh! Except of course one of the packages is wget, and we need to use wget to download the other files... ;-)

Oh! Except of course one of the packages is wget, and we need to use wget to download the other files... ;-)

Nah, Windows has this covered with a much more elegant solution.
@powershell -NoProfile -ExecutionPolicy Bypass -Command "(New-Object System.Net.WebClient).DownloadString('http://my/path/to/files') > \my\local\file"

I mean, who wouldn't think of that?

More seriously though, PowerShell is the rightful parallel to the UNIX world's shell scripts -- in the next Windows 10 update, it will even become the default shell. If you guys are looking for elegant ways to write native Windows scripts, PowerShell is a great option.

I mean, who wouldn't think of that?

Yeah, just rolls off the tongue :tongue: :laughing:
Is PowerShell included pre-installed on all version of Windows on which Etcher is supported though :question:

Is PowerShell included pre-installed on all version of Windows on which (building) Etcher is supported though ❓

It's definitely pre-installed on Windows 7 up, however I believe the version in Windows 7 is version 2 and each successive release (8, 8.1, 10 Anniversary Update) incremented the major version, so there might be incompatibilities. Of course, testing with Windows 7 is difficult, because the only people who still have it are people who either are required to use it by their employer or are avoiding all new updates since 2009 -- it's no longer sold to normal consumers (and rightfully so). The main thing to keep in mind is that the default ExecutionPolicy for PowerShell prevents you from running remotely-downloaded scripts, so you sometimes have to have the user change that security setting before using it.

Of course, testing with Windows 7 is difficult

The only Windows device that I have (an old Lenovo Thinkpad) is still on Windows 7 :smiley: :stuck_out_tongue:  (I keep it up to date, but I didn't want the "free upgrade" to Windows 10)
With the direction @jviotti is going (which I agree with), we're going to be using Makefiles and Bash as much as possible across all 3 platforms (for maximum code re-use), rather than using bash on Linux & OSX, and PowerShell on Windows. But if we can use PowerShell to "bootstrap" the process on Windows by downloading bash and wget, that might be useful :)
@jviotti Something else that's just occurred to me: it may already be on your radar, but if we're going to be using msys-unzip then I guess we can get rid of the 7zip dependency.

With the direction @jviotti is going (which I agree with), we're going to be using Makefiles and Bash as much as possible across all 3 platforms (for maximum code re-use), rather than using bash on Linux & OSX, and PowerShell on Windows. But if we can use PowerShell to "bootstrap" the process on Windows by downloading bash and wget, that might be useful :)

Yeah, I think that's the best approach right now; use PowerShell as the Windows bootstrapper for whatever else you need to download in the background. It would be nice to use one of the existing build dependencies (e.g. Python) for all of it, but that conversation was had before and the decision was made to stick with Bash and an emulation layer. In the end, I'm just here to provide some user insight when I can and to generally make sure I understand Etcher -- I have no stake in the internals of the thing, so I have no reason to get involved in it :laughing:

Something else that's just occurred to me: it may already be on your radar, but if we're going to be using msys-unzip then I guess we can get rid of the 7zip dependency.

🎉 🎈 🍾

Your help and comments are very much appreciated @WasabiFan  :clap: :grinning:

Sounds good! I'm happy to dive into PowerShell as a bootstrapped for the whole process. Re-writing all the Windows scripts in PowerShell sounds appealing as well, but at least for the time being, being able to re-use all the bash scripts we've been working on would be a big deal for us. Windows 10 also has bash support (although unstable as far as I've heard of), so maybe in that version, we can make use of it.

@jviotti Something else that's just occurred to me: it may already be on your radar, but if we're going to be using msys-unzip then I guess we can get rid of the 7zip dependency.

Yeah, I noticed that as well :) I'll update the dependencies list once I get to that point.
In any case, is this PR good to merge? I'll move forward with PowerShell for bootstrapping purposes later on.


Converted AKS VMSS arm template example has type property that conflicts with alias

Converted https://github.com/Azure/azure-quickstart-templates/blob/master/101-aks-vmss-systemassigned-identity/azuredeploy.json which has a type property.  Publish-PSArmTemplate encounters this and, as expected, tries to execute the type alias as it takes precedence over a function.
May need to consider detecting aliases and using fully qualified function?

https://github.com/PowerShell/PSArm/pull/133 implements one solution to this issue

Duplicate of https://github.com/PowerShell/PSArm/issues/126


added warnings for some syntaxes of ALTER TABLE and CREATE DATABASE statements

Added a warning for using CHARACTER SET, COLLATE or ENCRYPTION syntaxes when creating database. The database is still created.
Added a warning for using DISABLE KEYS or  ENABLE KEYS options for alter table statement. Nothing changes for the table being altered.
Added a system variable that mysqldump uses, innodb_stats_auto_recalc

LGTM!


DOC: Missing put_writes and aput_writes Method in "Create a Custom Checkpointer Using Redis"

Issue with current documentation:
In the documentation "Create a Custom Checkpointer Using Redis"  there is no implementation of the put_writes and aput_writes methods.
This is causing the following error: NotImplementedError: This method was added in langgraph 0.1.7. Please update your checkpoint saver to implement it.
link to referred doc: https://langchain-ai.github.io/langgraph/how-tos/persistence_redis/
Idea or request for content:
Request implementation of put_writes and a_putwrites methods on persistence_redis.ipynb.
https://github.com/langchain-ai/langgraph/blob/main/examples/persistence_redis.ipynb?short_path=e42963f
Both methods are implemented in persistence_postgres.ipynb for example:
https://github.com/langchain-ai/langgraph/blob/main/examples/persistence_postgres.ipynb?short_path=5874aa8
def put_writes(
        self,
        config: RunnableConfig,
        writes: Sequence[Tuple[str, Any]],
        task_id: str,
    ) -> None:
        with self._get_sync_connection() as conn:
            with conn.cursor() as cur:
                cur.executemany(
                    self.UPSERT_WRITES_QUERY,
                    [
                        (
                            str(config["configurable"]["thread_id"]),
                            str(config["configurable"]["thread_ts"]),
                            task_id,
                            idx,
                            channel,
                            self.serde.dumps(value),
                        )
                        for idx, (channel, value) in enumerate(writes)
                    ],
                )
            conn.commit()

async def aput_writes(
        self,
        config: RunnableConfig,
        writes: Sequence[Tuple[str, Any]],
        task_id: str,
    ) -> None:
        async with self._get_async_connection() as conn:
            async with conn.cursor() as cur:
                await cur.executemany(
                    self.UPSERT_WRITES_QUERY,
                    [
                        (
                            str(config["configurable"]["thread_id"]),
                            str(config["configurable"]["thread_ts"]),
                            task_id,
                            idx,
                            channel,
                            self.serde.dumps(value),
                        )
                        for idx, (channel, value) in enumerate(writes)
                    ],
                )
            await conn.commit()

the above method is not working for redis.   The above code only works for postgres. I am still facing same error.. please let me know if you have any solution for it

the above method is not working for redis.

No one said they work for redis

@Glinte check the latest issue #1221. I have updated the code if you'd like to use

Fixed in #1286


IMP: tabulate viz additions

A few nice-to-haves in composition's tabulate visualization:

Description on log-fold change positive vs. negative meaning (enriched vs. depleted relative to the chosen intercept i.e. reference level(s))

ln(A/B) = ln(B) - ln(A)

A > B -> + (enriched)

A < B -> - (depleted)

Description on what W score is (lfc/se)
Toggle on viz or command line param to show intercept column (default to False)

1 & 2 targeted for Feb release, 3 can be included in April release with additional viz features/updates within composition


Azure Snapshot Repository

Pull request acceptance prerequisites:

[x] Signed the CLA (if not already signed)
[x] Rebased/up-to-date with base branch
[ ] Tests pass
[ ] Updated CHANGELOG.md with patch notes (if necessary)
[ ] Updated CONTRIBUTORS (if attribution is requested)

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Jenkins test this please

updated with requested changes.


UTMCA: Create initial draft of the core annotation mocks

:tada: This issue has been resolved in version 0.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Documentation: Cloning and running the example fails

Hello,
I tried to get the example mentioned in https://github.com/zostera/django-bootstrap4/tree/master/example to run, but it completely fails.
From the documentation in README.rst it is not clear if the git command and the consecutive cd ... command should be run as one or not. In any case after cloning the repository one needs to run "cd django-bootstrap4/example" manually from the right place, otherwise it fails. "pip install -r requirements.txt python manage.py migrate python manage.py runserver" Does not install the required Django dependency, not sure what it is good for?
I tried to do a manual "pip install django" but then I get: "ModuleNotFoundError: No module named 'bootstrap4'" after trying to run the server.
Running a separate pip install django-bootstrap4 in the example folder solved this, but somehow this does not feel right...

Hi, it looks like you might need some help getting set up. The best place to ask for help is StackOverflow. You will receive answers from a community of programmers!
If you ask your question on StackOverflow and use the tag django-bootstrap4, we'll be happy to reply over there!


Update to latest WebGPU WebIDL

Update to latest WebGPU WebIDL as of July 29.
There are some changes from the upstream WebIDL (mostly to match Gecko's snapshot of the WebIDL/implementation status):

Define GPUCode as typedef (USVString or Uint32Array) GPUCode; to allow both SPIR-V and WGSL for now
Continue to use the old signature for set_index_buffer because that's what Gecko is currently using
Continue to use the old signatures for buffer mapping because that's what Gecko is currently using

Thanks!


[proposal] Support abstract resource

Currently we only support CPU and memory as resource type. In docker/swarm users have been asking to support arbitrary resources. Docker/swarm added a containerslots to limit number of containers as a mitigation. It falls short of supporting multi-category resource allocation. Here is an example https://github.com/docker/swarm/issues/2223.
It'd be great to allow user specify any resource, bandwidth, GPU count, disk space, or artificial ones. It could be scalar like 0.25 CPU,  or discrete like GPU-1 (don't divide GPU). Swarm can handle these resource without knowing the physical meaning. CPU and memory are 2 resource instances.
@vieux provides pointer to Mesos resource description.
http://mesos.apache.org/documentation/latest/attributes-resources/

Case study: NVDIA GPU support https://github.com/docker/docker/issues/23917

@dongluochen I posted docker/docker#24750 before, but think maybe this issue is more appropriate discussed here:
I am considering using Docker Swarm to orchestrate Swarm Cluster which supports GPU feature. Per my understanding, to implement this function, Docker need to envelope GPU resource like CPU and memory (E.g., add GPU in Cluster.Engine structure), and passes it to Docker Swarm when Swarm manager issues manage command. And Swarm manager and Docker engine-API all need do corresponding modifications to explain and use GPU resources (E.g., add GPU in node.Node structure).
My questions are as follows:
(1) Do my above statements make sense? Or are there some important technical issues which I ignore?
(2) What is the current status of Docker Swarm community supportting GPU feature?
Thanks very much in advance!

@NanXiao Docker support for GPU is under discussion in docker/docker#23917. I don't see problem in your statement but there are technical problems need solutions. The proposal on abstract resources should accommodate GPU as a resource type so Swarm cluster can manage it. It's based on Docker's GPU support.

@dongluochen Thanks very much for your reply! So per my understanding, Swarm project won't make the first move unless Docker support GPU first. Is it right? thx!

@NanXiao This proposal (abstract resource) can be independent of GPU support. We haven't fixed plan on it.

@runshenzhu ,
I agree with @dongluochen that Scalar type can't handle Set type, and Set type is a very important case to consider.
Take GPU as an example, if there are 2 GPU resources (gpu0 and gpu1) in the same node. The end user only need to ask for 1 GPU, but the scheduler should determine which GPU has been assigned, and ask the provisioner to provision with the left one.
My point is Scalar is good, but it may be not so helpful in the real case. Can you please also consider Set as the key feature. Thanks very much.

Implemented in #2090.


[gpio] Implement a GPIO DIF library

This change introduces a GPIO DIF library. I will send a new PR for unit tests.
See also: #1389 (tracking), #1043 (DIF RFC), #1111 (UART DIF), #1135 (SPI DIF), #1224 (DIF tests)
Signed-off-by: Alphan Ulusoy<EMAIL_ADDRESS>

let's make sure @weicaiyang is aware of this work too.

let's make sure @weicaiyang is aware of this work too.

Thanks, Scott.

Hi @alphan I have left a comment regarding the unit tests on #1224 .
Thank you very much, for starting the unit test implementation, we now have a solid starting point.
I will do a more thorough review tomorrow.

Oh one more small thing, it's not register.{h,c} anymore, it's now mmio.{h,c}. Please see #1187

This is mostly a first-pass style review. I'd like to discuss the testing strategy in more detail; do you have a design doc somewhere?

@alphan I said that will review this PR properly today, but unfortunately didn't get to it today. I will try to review it before the software meeting tomorrow, otherwise on wednesday. Thanks

@silvestrst No worries, thanks for letting me know!

@silvestrst Thanks a lot! I will implement your comments and update the PR after getting the new mmio library.

@alphan I just came across issue #41 . Don't know if you have come across it, or if it is relevant in terms of this change, but decided to mention it just in case.

@alphan another small stylistic comment, as discussed in #1043 - could you please remove const to scalars in function parameters?

Simplified init, introduced reset, and implemented functions for configuring interrupts.
@gkelly, ready for your review.

Implemented recent comments (@gkelly, @silvestrst)

Implemented recent comments (@lenary, @silvestrst).

This PR should be ready to merge.

Thank you for reviewing this!
On Fri, Feb 7, 2020 at 3:09 AM Silvestrs Timofejevs <
<EMAIL_ADDRESS>wrote:

@silvestrst approved this pull request.
LGTM! Thank you @alphan https://github.com/alphan for your patience.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/1254?email_source=notifications&email_token=AN2D23Q5EJGJKMR7D2C7YVTRBUJNNA5CNFSM4KBSQ4JKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCUUKQDI#pullrequestreview-354985997,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN2D23S5PZTID3UJA3UY5ALRBUJNNANCNFSM4KBSQ4JA
.

--
Best,
alphan
_

Thanks @lenary!

Rebased changes.


feat: add size-limit

Add size-limit and its actions workflow.
close #13
wait #12 for full bundle & basic bundle size analysis

https://github.com/LinbuduLab/nx-plugins/issues/55


[ACCESSIBILITY] Button is in improper sequence and incorrectly announced

Describe the bug
When swiping through the Color Definition popup window, the swipe order takes the user through the initial text and then directly to the Close button. In stead, it should go through ALL the text as shown in the screen capture and then to the Close button. Blind users will assume there's no more text when they encounter the close button. Also, the close button on the Status Card Color Definition window is announced as "Multiplication sign, double-tap to activate". This is incorrect and not an accurate description.
To Reproduce
Steps to reproduce the behavior:

Open sceen reading software
Swipe to the Information window on the Status Card
Swipe to through the text and then to the close button on the Status Card Color Definition window
See the incorrect Swipe order and hear the screen reader incorrectly identify the button.

Expected behavior
Swipe order should be logical and go through the text before reaching the close button. Also, buttons and links need to be properly labeled.
Screenshots
See below.
Smartphone (please complete the following information):
• Device: Google Pixel
• OS: Android
• Version 2.5.8

Fixed


Make middle breadcrumbs clickable

See: https://docusaurus.io/docs/creating-pages

@Selflocking


Logs explorer header cleanup

Description
In log explorer, moves the granularity selector down and includes a date&time range next to it, in order to bring the UI closer in line with the rest of Opensearch. Date&time range does not change upon selection in the plot, will be dealt with in the plot selection revamp PR
Issues Resolved
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

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

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

@paulstn Can you please signoff your commits https://github.com/opensearch-project/dashboards-observability/pull/937/checks?check_run_id=15925255567

@paulstn Can you please signoff your commits https://github.com/opensearch-project/dashboards-observability/pull/937/checks?check_run_id=15925255567

Signed off on all commits

Please address the failing tests.

The failing tests were due to me not signing off on all of my commits, fixed that issue

Please address the failing tests.

The failing tests were due to me not signing off on all of my commits, fixed that issue

Not signing off is only part of the failures, the test and build CI also fails with errors that need to be addressed. I'm seeing errors like 'FAIL public/components/event_analytics/explorer/timechart_header/tests/timechart_header.test.tsx (15.685 s)' which seems like changes in count distribution header caused the issue.


Circular reference resolving attached macro 'Godot'

This is easy enough to work-around but it's really strange, so I thought I'd file it anyway.
import SwiftGodot

@Godot class SomeClass: Node {}

extension SomeClass {
    struct SomeScopedStruct {}
}

extension SomeClass.SomeScopedStruct {
    static let asdf = Self()
}

This code will spew a lot of errors about circular references.
Here are 3 different changes that will make it compile happily

remove @Godot
leave @Godot in but remove the last extension
keep it exactly as it is, but move the extensions into a their own file (that file must have no @Godot anywhere in it)

I don't know if this is something we're doing in the @Godot macro, or a Swift bug. It feels more like a Swift bug to me.

I found https://forums.swift.org/t/peer-macros-on-a-protocol/65469/10
And, as an experiment, I tried removing arbitrary from the names parameter here:
@attached(member,
          names: named (init(nativeHandle:)), named (init()), named(_initClass), arbitrary)
public macro Godot() = #externalMacro(module: "SwiftGodotMacroLibrary", type: "GodotMacro")

This seems to make the issue go away... but it comes right back when I add a @Callable inside the class and the same trick does not save us there.
I still amn't sure if this is just a Swift bug 🤷

The reason we need to use arbitrary is because the Godot macro is the one that generates the assorted helpers that are referenced by the other macros like Callable.
one thing worth a try is to explore having the Godot macro assume the other bits are generated elsewhere and just rely on the generated code.

I can try to dig into this more later next week and maybe build a minimal-repo project to ask the Swift folks about.

Mhm, actually, I do not think we need the arbitrary at all.

I dropped the arbitrary, as we declare the other generated parts elsewhere - this might have been an early design decision that was never revisited.

The fact that this goes away when the definitions are shuffled into separate files really points towards this being a Swift bug. We can close this issue here I think, especially with arbitrary removed from GodotMacro.


XML indentation after comment line is reset if syntax on/enable

vim --version: 8.1.178
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 12 2018 23:51:06)
Included patches: 1-178
Compiled by kwsm@host
Huge version with GTK2 GUI.  Features included (+) or not (-):
+acl               +farsi             +mouse_sgr         -tag_any_white
+arabic            +file_in_path      -mouse_sysmouse    -tcl
+autocmd           +find_in_path      +mouse_urxvt       +termguicolors
-autoservername    +float             +mouse_xterm       +terminal
+balloon_eval      +folding           +multi_byte        +terminfo
+balloon_eval_term -footer            +multi_lang        +termresponse
+browse            +fork()            -mzscheme          +textobjects
++builtin_terms    +gettext           +netbeans_intg     +timers
+byte_offset       -hangul_input      +num64             +title
+channel           +iconv             +packages          +toolbar
+cindent           +insert_expand     +path_extra        +user_commands
+clientserver      +job               -perl              +vartabs
+clipboard         +jumplist          +persistent_undo   +vertsplit
+cmdline_compl     +keymap            +postscript        +virtualedit
+cmdline_hist      +lambda            +printer           +visual
+cmdline_info      +langmap           +profile           +visualextra
+comments          +libcall           -python            +viminfo
+conceal           +linebreak         -python3           +vreplace
+cryptv            +lispindent        +quickfix          +wildignore
+cscope            +listcmds          +reltime           +wildmenu
+cursorbind        +localmap          +rightleft         +windows
+cursorshape       -lua               -ruby              +writebackup
+dialog_con_gui    +menu              +scrollbind        +X11
+diff              +mksession         +signs             -xfontset
+digraphs          +modify_fname      +smartindent       +xim
+dnd               +mouse             +startuptime       +xpm
-ebcdic            +mouseshape        +statusline        +xsmp_interact
+emacs_tags        +mouse_dec         -sun_workshop      +xterm_clipboard
+eval              -mouse_gpm         +syntax            -xterm_save
+ex_extra          -mouse_jsbterm     +tag_binary
+extra_search      +mouse_netterm     +tag_old_static
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/home/kawasima/usr/local/vim/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12     -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L/usr/local/lib -Wl,--as-needed -o vim   -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0   -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm -ltinfo -lelf -lnsl  -lselinux -lacl -lattr -ldl

How to Reproduce
vim -N -u NONE -c'setf xml' -c'ru indent/xml.vim' -c'syntax enable' -c'exe "normal! =G"' - << EOF
<?xml version="1.0" encoding="utf-8"?>
<tag0>
<tag1>
<!-- comment -->
<tag2>
<tag3/>
</tag2>
</tag1>
</tag0>
EOF

which gives
<?xml version="1.0" encoding="utf-8"?>
<tag0>
        <tag1>
<!-- comment -->
<tag2>
        <tag3/>
</tag2>
</tag1>
</tag0>

If :syntax off and =G again, the content is indented as expected:
<?xml version="1.0" encoding="utf-8"?>
<tag0>
        <tag1>
                <!-- comment -->
                <tag2>
                        <tag3/>
                </tag2>
        </tag1>
</tag0>

On the other hand, vim can indent correctly if comment and tag are in same line, e.g.,
<?xml version="1.0" encoding="utf-8"?>
<tag0>
<tag1>
<tag2> <!-- comment -->
<tag3/>
</tag2>
</tag1>
</tag0>

Please make sure to have a line of :filetype plugin indent on in your .vimrc to have the xml indenting runtime file sourced. That should make indentation work properly.

Minimal vimrc is
syntax on
filetype plugin indent on

which doesn't work as expected.
I'm not sure why, but indentation doesn't work if a comment has 0 leading and 0 or 1 trailing characters:
<?xml version="1.0" encoding="utf-8"?>
<tag0>
                <tag1>
 <!-- no trailing character but a leading character, will be indented -->
                </tag1>
                <tag1>
<!-- no leading character but trailing characters, will be indented -->12
                </tag1>
                <tag1>
<!-- no leading character and a single trailing character, indention will have NO effect -->1
                </tag1>
                <tag1>
<!-- no leading nor trailing character, indention will have NO effect -->
                </tag1>
</tag0>

vim indents comments of HTML (and XHTML) as expected, so I think this behaviour should be fixed, namely be consistent with (X)HTML.

as you seem to be using xml indenting. You might try the change and check, whether that works for you well enough. Once you are satisfied, you can propose the change here and we might include it. I might become new maintainer, as I already maintain the xml ftplugin. But please test the change a while.

#3248


dependencies mismatch when doing pre-release

We've just pushed titiler.core/titiler.mosaic/titiler.application 0.4.0a0. This is a pre-release which then cause dependencies problem within titiler.mosaic and titiler.application.
https://github.com/developmentseed/titiler/blob/c54b0613673c80b273beae155aa8d95e17fb0c90/src/titiler/mosaic/setup.py#L8
https://github.com/developmentseed/titiler/blob/c54b0613673c80b273beae155aa8d95e17fb0c90/src/titiler/application/setup.py#L10-L11
☝ will only try to install the non-pre version and thus fails to install 0.4.0a0
Note: right now to make it work you either have to do:
python -m pip install titiler==0.4.0a0

# or

python -m pip install titiler.core==0.4.0a0 titiler.mosaic==0.4.0a0 titiler.application==0.4.0a0

fixed in https://github.com/developmentseed/titiler/commit/1a4946b1349b7015da4bb56370975c0faa840e81


Warning upon proving False

Being able to prove False is probably a "user error" most of the time. In my case it was a typo which boils down to the following:
module Test

noeq abstract type test_package =
  | TP: i:int{i > 0} ->
        j:int{i < 0} ->
        test_package

val lemma_false: tp:test_package -> Lemma
  (requires True)
  (ensures False)
let lemma_false tp =
  assert(False)

In the actual code it was a bit more complicated and it took me quite a while to debug. Would it be possible to have a mechanism that generates a warning if the verifier can prove assert(False)?
Right now I'm getting paranoid when things verify too easily and insert assert(False) in many places just to make sure I didn't make that kind of mistake.

As Nik said on slack, this is related to #71

I don't quite get what the outcome of the discussion of that threat is. Is it just infeasible to have such a mechanic due to the way F* queries work?

This came up before, but I can't find any open issue.
I think that it wouldn't be hard to implement something similar to Why3 --smoke-detector option (http://why3.lri.fr/doc-0.87.3/manual007.html#sec56) to systematically look for inconsistencies in the global context, or in premises of proof obligations.

This also came up in a recent Zulip discussion here:
https://fstar.zulipchat.com/#narrow/stream/184683-questions-and.20help/topic/Unsatisfiable.20preconditions


Notebooks 1 and 4-7 for LSST workshop

Removed all .pyc files.
Removed pycache directories.
Because of time constraints, I could not convert .png images to .jpg. I did however standardize .jpeg into .jpg. .png conversion will begin following the LSST event.
I could not find the 'numpy as N' standardization error. I had already worked on standardizing imports away from the way they were originally written. Are there specific imports that should be changed?
README file updated.
Organized accessory data and image files into folders.
Changed notebook filenames to better match their titles.

In 05_Gravitational_Lensing/Data/lensdemo_funcs.py. And in 05_Gravitational_Lensing/lensdemo_funcs.py.
Which also brings up the question why the same code is there twice in two directories? Can you do away with one?
Finally: before I merge, you can push to the same branch (your master branch), and the additional changes will be included in the PR. I.e. no need to make a new PR each time :)

Thank you for pointing that out. I had never opened that file; I have only worked on the .ipynb files.
Also, thank you for the tip on the PR. I am still learning parts of git I have not had the chance to see yet!


Document restrictions for CollectionName

I tried to use an underscore, but those are apparently not allowed.
Would also be interested to know why?

The requirements are currently documented on Name, but as you rightfully note, should definitely be either linked to or included on all the types that use it.

Would also be interested to know why?

In short, I wanted to reserve characters for internal use, and those two are . and _. There are only so many characters that are safe for the filesystem. I suppose we could escape unsafe characters now that I'm writing that... I might end up doing that and removing almost all name restrictions.
Great feedback.

Alright, I'd add whatever restrictions will be there in the end to the derive macro as well so that they'll be a compile time error.

I've made up my mind to remove all restrictions this morning. I'll reference this issue from the commit when I push it.


AADAuthenticationFilter.doFilterInternal treats an accessToken as an IdToken

Environment

Spring boot starter:

active directory spring boot starter

OS Type: all

Java version: 11, 1.9, 1.8

Summary
When calling a REST API with HTTP header Authentication Bearer xxxxxxx, the AADAuthenticationFilter.doFilterInternal treats the accessToken as an JWT idToken and the call on line 71 principalManager.buildUserPrincipal(idToken) throws an exception since it tries to parse it as JSON.
Reproduce steps

Use the sample azure-active-directory-spring-boot-sample
Use Postman to get an OAuth2 access token to your registered app (do not use the UI login)
Call an API

Expected Results
Authenticate using the accessToken passed in the HTTP Header Authirization Bearer xxxxxx
Actual Results
You will get an exception
java.text.ParseException: Invalid serialized unsecured/JWS/JWE object: Missing part delimiters
at com.nimbusds.jose.JOSEObject.split(JOSEObject.java:222) ~[nimbus-jose-jwt-6.7.jar!/:6.7]
at com.nimbusds.jose.JWSObject.parse(JWSObject.java:414) ~[nimbus-jose-jwt-6.7.jar!/:6.7]
at com.microsoft.azure.spring.autoconfigure.aad.UserPrincipalManager.buildUserPrincipal(UserPrincipalManager.java:63) ~[azure-spring-boot-2.1.3.jar!/:na]
at com.microsoft.azure.spring.autoconfigure.aad.AADAuthenticationFilter.doFilterInternal(AADAuthenticationFilter.java:71) ~[azure-spring-boot-2.1.3.jar!/:n

Hi,
I'm facing a similar issue. Did you solved it or why was it closed?
Regards

Hi,
I am facing the same issue as well.
did anyone find a solution for this?
Thanks

Hi,
I am facing the same issue as well. Did anyone find a solution for this?
Thanks

@desertTown
The AADAuthenticationFilter is designed to accept ID token instead of the access token.

Hi,
I am facing the same issue as well. Why closed the issue, have any solution?
Thanks

@pandajiangbao
Could you share more details about your issue?


SP5: Need WinUI Quickstart

I want to help @lnf83515 resolve #2698 but there isn't a great resource in place to help new WinUI users get started and I don't know much about WinUI myself.
If someone more familiar with WinUI gets to this before I do, it would be fanastic to have a WinUI Quickstart for ScottPlot 5 on the website!
I created a page to get it started, but it's currently empty:

https://scottplot.net/quickstart/winui/
https://github.com/scottplot/scottplot.net/blob/main/content/quickstart/winui/index.md

The WinUI package is on NuGet and everything so this may be pretty easy:

https://www.nuget.org/packages/ScottPlot.WinUI/5.0.5-beta

Additional Resources:

https://learn.microsoft.com/en-us/windows/apps/winui/winui3/create-your-first-winui3-app

Hi @swharden , Can you update the WinUI Quickstart?
It's very similar to WPF
Step1: Make new WinUI project.

Step2: Open nuget manager and install the ScottPlot.WinUI.  (need to check 'Include prerelease')

Step3:  Add this to the root element of XAML file:
xmlns:ScottPlot="using:ScottPlot.WinUI"
Step4:  Add WinUIPlot to layout:
<ScottPlot:WinUIPlot x:Name="WinUIPlot1"/>
Step5: Plot some data in XAML.CS file
            double[] sin = Generate.Sin(51);
            double[] cos = Generate.Cos(51);
            WinUIPlot1.Plot.Add.Signal(sin);
            WinUIPlot1.Plot.Add.Signal(cos);

            WinUIPlot1.Refresh();

MainWindow.xaml

MainWindow.xaml.cs

result

Additionaly, There is two problems using ScottPlot.WinUI on my system.

On project property, if Target OS version is 10.0.20348.0 or lower then the project build fails.
Its works on 10.0.22200.0 or higher.

ScottPlot works on Gird layout, but its not works on stackpanel

Im not sure if this is a bug or problem with my system.
My system information is below.
Windows11 22H2 OS Build 22621.1848
Microsoft Visual Studio Community 2022 (64-bit) - Current Version 17.6.4
WindowsAppSdk 1.3.230602002
ScottPlot.WinUI 5.0.5-beta
.net v6.0.314 and .net v7.0.305

@lnf83515

ScottPlot works on Gird layout, but its not works on stackpanel

This is not a ScottPlot bug, this is bug in your XAML code.
A Grid will try to take as much space as it can, but the StackPanel will only use the required space according to the items it holds.
To overcome this, you can force StackPanel to take all space:
<StackPanel Margin="0,0,0,0" VerticalAlignment="Stretch" HorizontalAlignment="Stretch" Width="Auto" Height="Auto">
    <ScottPlot:WinUIPlot />
</StackPanel>

Or force ScottPlot dimensions:
<StackPanel>
    <ScottPlot:WinUIPlot MinWidth="640" MinHeight="480"/>
</StackPanel>

@KroMignon
Thanks for your comment.
I already tried strech, but it didn't work. (I think it works but not shown)

Force width and height is working.
But other controls (like button) are working without setting width and height.

I'll test more diffrent cases.

Is the ScottPlot.WinUI package description good?

https://github.com/ScottPlot/ScottPlot/blob/0376f523dc1082a4af5a7f3273037caeefebd758/src/ScottPlot5/ScottPlot5 Controls/ScottPlot.WinUI/ScottPlot.WinUI.csproj#L16
I always find the relationship between WinUI and Uno confusing. Should this say something better, or is it good?

Thanks everyone! I updated the quickstart page. Take a look and let me know if you have any suggestions for improvements! (There's an edit button at the bottom of the page)
https://scottplot.net/quickstart/winui/
resolved by https://github.com/ScottPlot/ScottPlot.NET/commit/442375b123c1f0e3d7a9db491251276a9111e0d5


Tensors must have same number of dimensions: got 2 and 1

Traceback (most recent call last):   File "main.py", line 101, in      run(vars(args))   File "main.py", line 96, in run     train(train_iter, test_iter, model, criterion, optimizer, config)   File "/home/jupyter/time-series-autoencoder/train.py", line 44, in train     output = model(feature.to(config["device"]), y_hist.to(config["device"]))   File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 550, in call     result = self.forward(*input, **kwargs)   File "/home/jupyter/time-series-autoencoder/model.py", line 254, in forward     outputs = self.decoder(encoder_output, y_hist.float())   File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 550, in call     result = self.forward(*input, **kwargs)   File "/home/jupyter/time-series-autoencoder/model.py", line 222, in forward     dim=1))  # (batch_size, out_size) RuntimeError: Tensors must have same number of dimensions: got 2 and 1
What could be the reason of the following error
Here are my args
python main.py --batch-size 2 --output-size 2 --label-col T --input-att true --temporal-att true  --seq-len 5 --hidden-size-encoder 5 --hidden-size-decoder 5 --reg-factor1 0.1 --reg-factor2 0.2 --reg1 true --reg2 true --denoising true --do-train true --do-eval true --data-path data.csv --output-dir output_dir

Hey @jawwada thanks for opening a new issue.
I suspect that y_history[:, t] is only one dimensional. You might need to unsqueeze one dimension by modifying it to something like:
y_tilde = self.fc(torch.cat((context.to(device), y_history[:, t].unsqueeze(1).to(device)),dim=1))  # (batch_size, out_size)

Let me know if that helps. Otherwise try to print the tensors shape after each layer.

Hi JulesBelzeve, thanks a lot for the prompt answer. Your work indeed sounds amazing, although I have been unable to run it. I will get back to you.

After some debugging, the error is produced at this line in dataset.py
features.append(torch.FloatTensor(X[i:i + self.seq_length, :]).unsqueeze(0))
sparse matrix length is ambiguous; use getnnz() or shape[0]
File "/home/jupyter/time-series-autoencoder/dataset.py", line 56, in frame_series
features.append(torch.FloatTensor(X[i:i + self.seq_length, :]).unsqueeze(0))
File "/home/jupyter/time-series-autoencoder/dataset.py", line 81, in get_loaders
train_dataset = self.frame_series(X_train, y_train)
File "/home/jupyter/time-series-autoencoder/main.py", line 87, in run
train_iter, test_iter, nb_features = ts.get_loaders(batch_size=config["batch_size"])
File "/home/jupyter/time-series-autoencoder/main.py", line 103, in
run(vars(args))
At this point, X is number of rows by 30 columns. y_hist is empty

that error did not appear again, however another error that sparse matrix length is ambiguous surface. It got resolve by changing the following line
features.append(torch.FloatTensor(X[i:i + self.seq_length, :]).unsqueeze(0))
to
features.append(torch.FloatTensor(X[i:i + self.seq_length, :].todense()).unsqueeze(0))

This has finally started to run. I had to model my parameters exactly as in your config.py and run the program as python main.py without any arguments. Just giving the arguments in config.py where I wanted. May be I do not understand the model in full yet. Had to do a little bit of debugging. Thanks a lot for the help. I will connect with you over linkedin.

Glad to hear that you managed to have it working 😄
I definitely need to add some examples to the repo though!


chore: update subject type for authz

Description
ENG-1826
The subject proto message in the authorization service has changed.
Checklist

[ ] make test passes
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message follows commit guidelines

CHANGELOG

I don't think chore is the right commit prefix here. Should probably rather be refactor or fix


gnu-tests/F-headers: increase number of attempts

Related PR #3618
Since this test is still not stable, I propose to try to increase the number of attempts from 7 to 9, and total delay will increase from 12.7 seconds to 51.1 seconds.
As I understand tests are being run in parallel, there are three tests with this delay, so this won't result in too much additional running time, 2 minutes tops for this test. And when it succeeds it stops, so it's only slow when it fails. And it sleeps most of the time not using resources.

I don't know, probably try with even bigger timeout limit for some time, made the limit equal to 409.5 seconds.

Let's see if it sticks


MoveToAsync is not working in methods

Thanks for making the package public. I am a little puzzled with a strange behavior. I was wondering if this is a bug. Here is what I am trying to do. I need to draw many lines, so I delegate the drawing job to a static method:
public static async void Line(Context2D context, Line line)
{

    await context.BeginPathAsync();
    await context.MoveToAsync(line.startX, line.startY);
    await context.LineToAsync(line.endX, line.endY);
    await context.LineWidthAsync(line.thickness);

    // set line color
    await context.StrokeStyleAsync(line.color);
    await context.StrokeAsync();

}

I am trying to draw a V. When I call this the first time to draw the left arm of V, it works. The seocnd time I call it to draw the right arm, I use the same startX and startY coordinates, but the line does not start from the fork of V, instead it starts drawing at the top of the left arm.
Happy to put something on GitHub in case you need more info.

I just checked the code for moveTo and as far as I can see, it's correctly implemented. Can you share the code that calls this method? The issue might be there.

thanks for the quick response, Stefan, here is a simple Blazor server app with the problem:
https://github.com/aadurham/Blazor.Canvas.Demo
Notice that, the first line is black, the second is red, but it draws both red.

I have also added a screenshot of the issue

Looking at the coordinates that you pass to the method that draws the lines, it looks like the method is doing exactly what you ask it to do. Remember that in html canvases, the (0,0) coordinate is in the top left corner.

I have added a few lines to write the coordinates to the console. Here is the console output:
Line Color: black
Move To: X = 10 Y = 150
Line To: X = 100 Y = 100
Line Color: red
Move To: X = 10 Y = 150
Line To: X = 100 Y = 200
As you see, the color of the first line is black at time of drawing, but it turns to red at the end.
I have put these numbers into plain js here:
https://www.w3schools.com/html/tryit.asp?filename=tryhtml5_canvas_tut_path
and added a jpg file of how it looks (I have also added the console output there). Here is my code in case you want to copy paste.
`

Your browser does not support the HTML canvas tag.

`

the jpg files should be self explanatory. My V is supposed to be rotated 90 degrees clockwise.

You need to await.
Change public static async void Line(Context2D context, Line line) into public static async Task Line(Context2D context, Line line) and then await when drawing them: await DrawOnCanvas.Line(context, line1/2) .  That means the change of color to red can happen before the stroke of the line that's supposed to be black.

That solves the issue. I am glad it was me, not a bug! Thanks for your incredibly prompt response!