v3.12.0 error with streamingXml due to non-existent user "poifiles" sub-directory

When using CF2016 w/v3.12.0 and using StreamingXml (using either the newStreamingXlsx or new methods), CF returns a "java.nio.file.NoSuchFileException" error when trying to access a temporary XML file in a non-existent "\AppData\Local\Temp\poifiles" directory.
I know that this project has moved on to v4 and now only supports CF2018+, but was wondering what may be causing this error and whether it may also exist in v4.
I tried searching the 3.12.0 library source for "poifiles" and no results were returned.
SOLUTION: I manually created a "poifiles" sub-directory in the user's "AppData\Temp" path (which was missing) and it now works. (I'm sharing here in case it may benefit other developers.)

Looks like an internal java or POI error specific to your local environment. Permissions, maybe? Sorry not really sure.
Thanks for posting the workaround anyway.


Create add_custom_log_attributes API

See #2084 instead (git mistakes made on this PR)
The NewRelic::Agent.add_custom_log_attributes API allows users to add attributes to all log events for a given agent run. It accepts key/value pairs as arguments.
This API abides by log API documentation on limits, and event data:

No more than 255 attributes can be added (limited to 240 for the agent at this time)
Keys must have less than 64 characters
Values must have less than 4094 characters
Key/value pairs with empty content will be dropped
Values longer than 4094 characters that aren't Strings/Symbols will be dropped

These attributes will be sent to the logs API in the "common"["attributes"] JSON block.
Relates to: #1141

If you’re up for it, I’d like to meet synchronously tomorrow to talk this through. I’ve been in a weird place emotionally today and I think my problems have seeped into this PR. Sent from my iPhoneOn Jun 14, 2023, at 18:02, James Bunch @.***> wrote:
@fallwith commented on this pull request.
In lib/new_relic/agent.rb:

exceeds 4094 characters and is of a

different class, the attribute pair will

be dropped.

This API can be called multiple times.

If the same key is passed more than once,

the value associated with the last call

will be preserved.

Attribute pairs with empty or nil contents

will be dropped.

@api public

def add_custom_log_attributes(params)

 record_api_supportability_metric(:add_custom_log_attributes)

 if params.is_a?(Hash)

Would you like me to change the return value to match your suggestion?
Given that a) we don't have a standard, b) you've modeled this new API closely off of a fairly similar one, and c) our communication back to the caller is traditionally done via logged messages, no. Thank you for the explanation!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

If you’re up for it, I’d like to meet synchronously tomorrow to talk this through.

Sure thing.

See #2084 instead (git mistakes made on this PR)


Trino SQL routines with multiple ; characters cannot run on Superset SQL Lab Editor

Superset SQL Lab Editor cannot run Trino SQL routines which have multiple ; statements.
How to reproduce the bug

Go to 'SQL Lab' (http://localhost:8088/superset/sqllab)
Run a Trino SQL Routine with multiple ; characters, such as this one from example docs

WITH FUNCTION simple_case(a bigint)
RETURNS varchar
BEGIN
  CASE a
    WHEN 0 THEN RETURN 'zero';
    WHEN 1 THEN RETURN 'one';
    WHEN 10 THEN RETURN 'ten';
    WHEN 20 THEN RETURN 'twenty';
    ELSE RETURN 'other';
  END CASE;
  RETURN NULL;
END
SELECT simple_case(0);

Sees error emssage

Expected results
SQL Routine to run successfully and return 0
Actual results
Website error message:
Trino Error
trino error: line 5:30: mismatched input '<EOF>'. Expecting: '%', '*', '+', '-', '.', '/', ';', 'AT', '[', '||'

This may be triggered by:
Issue 1002 - The database returned an unexpected error.

Superset Error message:
2023-12-01 12:52:33 Triggering query_id: 41
2023-12-01 12:52:33 2023-12-01 20:52:33,077:INFO:superset.sqllab.commands.execute:Triggering query_id: 41
2023-12-01 12:52:33 SQLite Database support for metadata databases will be removed             in a future version of Superset.
2023-12-01 12:52:33 2023-12-01 20:52:33,098:WARNING:superset.utils.celery:SQLite Database support for metadata databases will be removed             in a future version of Superset.
2023-12-01 12:52:33 Query 41: Executing 8 statement(s)
2023-12-01 12:52:33 2023-12-01 20:52:33,113:INFO:superset.sql_lab:Query 41: Executing 8 statement(s)
2023-12-01 12:52:33 Query 41: Set query to 'running'
2023-12-01 12:52:33 2023-12-01 20:52:33,113:INFO:superset.sql_lab:Query 41: Set query to 'running'
2023-12-01 12:52:33 Query 41: Running statement 1 out of 8
2023-12-01 12:52:33 2023-12-01 20:52:33,126:INFO:superset.sql_lab:Query 41: Running statement 1 out of 8
2023-12-01 12:52:33 2023-12-01 20:52:33,152:DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): host.docker.internal:8080
2023-12-01 12:52:33 2023-12-01 20:52:33,163:DEBUG:urllib3.connectionpool:http://host.docker.internal:8080 "POST /v1/statement HTTP/1.1" 200 328
2023-12-01 12:52:33 2023-12-01 20:52:33,176:DEBUG:urllib3.connectionpool:http://host.docker.internal:8080 "GET /v1/statement/queued/20231201_205233_00062_fcdsq/y76761f7eb08c441e8c30f713ad964721e8eb9a87/1 HTTP/1.1" 200 1063
2023-12-01 12:52:33 SupersetErrorsException
2023-12-01 12:52:33 Traceback (most recent call last):
2023-12-01 12:52:33   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1823, in full_dispatch_request
2023-12-01 12:52:33     rv = self.dispatch_request()
2023-12-01 12:52:33   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1799, in dispatch_request
2023-12-01 12:52:33     return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
2023-12-01 12:52:33   File "/usr/local/lib/python3.9/site-packages/flask_appbuilder/security/decorators.py", line 95, in wraps
2023-12-01 12:52:33     return f(self, *args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/views/base_api.py", line 127, in wraps
2023-12-01 12:52:33     raise ex
2023-12-01 12:52:33   File "/app/superset/views/base_api.py", line 121, in wraps
2023-12-01 12:52:33     duration, response = time_function(f, self, *args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/utils/core.py", line 1526, in time_function
2023-12-01 12:52:33     response = func(*args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/views/base_api.py", line 93, in wraps
2023-12-01 12:52:33     return f(self, *args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/utils/log.py", line 255, in wrapper
2023-12-01 12:52:33     value = f(*args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/sqllab/api.py", line 310, in execute_sql_query
2023-12-01 12:52:33     command_result: CommandResult = command.run()
2023-12-01 12:52:33   File "/app/superset/sqllab/commands/execute.py", line 121, in run
2023-12-01 12:52:33     raise ex
2023-12-01 12:52:33   File "/app/superset/sqllab/commands/execute.py", line 103, in run
2023-12-01 12:52:33     status = self._run_sql_json_exec_from_scratch()
2023-12-01 12:52:33   File "/app/superset/sqllab/commands/execute.py", line 161, in _run_sql_json_exec_from_scratch
2023-12-01 12:52:33     raise ex
2023-12-01 12:52:33   File "/app/superset/sqllab/commands/execute.py", line 156, in _run_sql_json_exec_from_scratch
2023-12-01 12:52:33     return self._sql_json_executor.execute(
2023-12-01 12:52:33   File "/app/superset/sqllab/sql_json_executer.py", line 111, in execute
2023-12-01 12:52:33     raise SupersetErrorsException(
2023-12-01 12:52:33 superset.exceptions.SupersetErrorsException: [SupersetError(message="trino error: line 5:30: mismatched input '<EOF>'. Expecting: '%', '*', '+', '-', '.', '/', ';', 'AT', '[', '||'", error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'Trino', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]
2023-12-01 12:52:33 2023-12-01 20:52:33,191:WARNING:superset.views.base:SupersetErrorsException
2023-12-01 12:52:33 Traceback (most recent call last):
2023-12-01 12:52:33   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1823, in full_dispatch_request
2023-12-01 12:52:33     rv = self.dispatch_request()
2023-12-01 12:52:33   File "/usr/local/lib/python3.9/site-packages/flask/app.py", line 1799, in dispatch_request
2023-12-01 12:52:33     return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
2023-12-01 12:52:33   File "/usr/local/lib/python3.9/site-packages/flask_appbuilder/security/decorators.py", line 95, in wraps
2023-12-01 12:52:33     return f(self, *args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/views/base_api.py", line 127, in wraps
2023-12-01 12:52:33     raise ex
2023-12-01 12:52:33   File "/app/superset/views/base_api.py", line 121, in wraps
2023-12-01 12:52:33     duration, response = time_function(f, self, *args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/utils/core.py", line 1526, in time_function
2023-12-01 12:52:33     response = func(*args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/views/base_api.py", line 93, in wraps
2023-12-01 12:52:33     return f(self, *args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/utils/log.py", line 255, in wrapper
2023-12-01 12:52:33     value = f(*args, **kwargs)
2023-12-01 12:52:33   File "/app/superset/sqllab/api.py", line 310, in execute_sql_query
2023-12-01 12:52:33     command_result: CommandResult = command.run()
2023-12-01 12:52:33   File "/app/superset/sqllab/commands/execute.py", line 121, in run
2023-12-01 12:52:33     raise ex
2023-12-01 12:52:33   File "/app/superset/sqllab/commands/execute.py", line 103, in run
2023-12-01 12:52:33     status = self._run_sql_json_exec_from_scratch()
2023-12-01 12:52:33   File "/app/superset/sqllab/commands/execute.py", line 161, in _run_sql_json_exec_from_scratch
2023-12-01 12:52:33     raise ex
2023-12-01 12:52:33   File "/app/superset/sqllab/commands/execute.py", line 156, in _run_sql_json_exec_from_scratch
2023-12-01 12:52:33     return self._sql_json_executor.execute(
2023-12-01 12:52:33   File "/app/superset/sqllab/sql_json_executer.py", line 111, in execute
2023-12-01 12:52:33     raise SupersetErrorsException(
2023-12-01 12:52:33 superset.exceptions.SupersetErrorsException: [SupersetError(message="trino error: line 5:30: mismatched input '<EOF>'. Expecting: '%', '*', '+', '-', '.', '/', ';', 'AT', '[', '||'", error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'Trino', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]
2023-12-01 12:52:33 <IP_ADDRESS> - - [01/Dec/2023:20:52:33 +0000] "POST /api/v1/sqllab/execute/ HTTP/1.1" 500 337 "http://localhost:8088/superset/sqllab" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
2023-12-01 12:52:33 <IP_ADDRESS> - - [01/Dec/2023:20:52:33 +0000] "PUT /tabstateview/4 HTTP/1.1" 200 1 "http://localhost:8088/superset/sqllab" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"

Screenshots

Environment
(please complete the following information):

browser type and version: Chrome Version 119.0.6045.159 (Official Build) (arm64)
superset version: 3.0.1
python version: Python 3.9.18
node.js version: N/A
any feature flags active: N/A

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
I was able to track this down to the SQL statement parsing logic. Specifically, the db_engine_spec.run_multiple_statements_as_one variable is used to determine whether to parse SQL with ; characters into multiple SQL statements.
The TrinoEngineSpec  and PrestoBaseEngineSpec both do not include this variable. So run_multiple_statements_as_one is set to False by the BaseEngineSpec.
I was able to set run_multiple_statements_as_one to True in TrinoEngineSpec and got the SQL above to work. However, this changes the default behavior of SQL Lab for Trino which allows running multiple SQL statements separated by ;.

Thank you for filing this @kevinjqliu !

Btw here is the logic to figure out the details from the Trino CLI https://github.com/trinodb/trino/blob/master/client/trino-cli/src/main/java/io/trino/cli/lexer/StatementSplitter.java

@betodealmeida do you think the sqlglot migration would help at all with this sort of issue?

Seems like sqlglot can help solve this issue.
It doesn't work out of the box though.
from sqlglot import parse

sql = """FUNCTION simple_case(a bigint)
  RETURNS varchar
  BEGIN
    CASE a
      WHEN 0 THEN RETURN 'zero';
      WHEN 1 THEN RETURN 'one';
      ELSE RETURN 'more than one or negative';
    END CASE;
    RETURN NULL;
  END
"""

parse(sql, dialect='trino')

Returns an error
sqlglot.errors.ParseError: Invalid expression / Unexpected token. Line 1, Col: 21.
  FUNCTION simple_case(a bigint)
  RETURNS varchar
  BEGIN
    CASE a
      WHEN 0 THEN RETURN 'zero';
      WHEN 1 THEN RE

Even if this is not supported by sqlglot it should work in Superset as is — at least if DML is enabled. Let me take a look.


RuntimeError: Cannot load library 'libopenvino_intel_myriad_plugin.so

I have a script test_exp.py contining following commands
ie_core = Core()
model = ie_core.read_model(model=converted_model_path)
compile the model for the CPU (you can choose manually CPU, GPU, MYRIAD etc.)
or let the engine choose the best available device (AUTO)
#compiled_model = ie_core.compile_model(model=model, device_name="CPU")
compiled_model = ie_core.compile_model(model=model, device_name="MYRIAD")
I run it with
python test_exp.py
and the get
RuntimeError: Cannot load library 'libopenvino_intel_myriad_plugin.so
the same script with
compiled_model = ie_core.compile_model(model=model, device_name="CPU")
runs correctly
** Environment information **
Pip version: 22.1
OpenVINO source: /home/fenaux/openvino_env/lib/python3.9/site-packages/openvino
OpenVINO IE version: 2022.1.0-7019-cdb9bec7210-releases/2022/1
OpenVINO environment activated: OK
Jupyter kernel installed for openvino_env: NOT OK
Python version: 3.9 OK
OpenVINO pip package installed: OK
OpenVINO import succeeds: OK
OpenVINO development tools installed: OK
OpenVINO not installed globally: OK
No broken requirements: OK
Ubuntu 20.04.4 LTS
I could not run
source ~/intel/openvino/bin/setupvars.sh
cd ~/intel/openvino/install_dependencies
./install_NCS_udev_rules.sh
as i do not find setupvars.sh
nor install_dependencies
thanks for your help

Hi @fenaux! I don't think that its something that we are able to fix in this repository. Can you report this issue to OpenVINO repository?

I agree. thanks


Update tslib peer dependency to support 2.x versions (Angular v12)

Hey Dmitry,
Can you update this to support version 2.4.0 of tslib?
Thanks!

I'm investigating the need to have it as a dependency at all. I'll see if it can be removed first

it appears that Angular recommends keeping tslib as a direct dependency for Angular libraries. Furthemore, the suggested version today is "^2.0.0". That's what is specified in the package.json file of ngx-errors as well. Notice the carrot: ^ in the version. It means that any 2.x.x version is acceptable - including the requested 2.4.0.
Was there a particular reason for the request?

I get the error:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
when I use "tslib": "^2.4.0",

Oh dang this may be because I'm using "@ngspot/ngx-errors": "^2.0.2",

Cool, please try upgrading and let me know if still have issues


⚠ Bofrost.de has degraded performance

In 20419e8, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1424 ms

Resolved: Bofrost.de performance has improved in 59ca6fa after 6 minutes.


Implement the styles/theme according to work of the designers

Some designers in Copenhagen are working on the design of the overall service package website for the VIRT-EU project.
We will be provided with a design document that says what design elements should look like: colours, typefaces, buttons, input fields and so on. We will have to match the look of PESIA with the look given to us by the designers

I think this is pretty much complete.  Let me know if there are any visual glitches.

I think it looks fine. I haven’t checked all pages but we can close

On 20 Dec 2019, at 02:01, Daniel Ramsay<EMAIL_ADDRESS>wrote:
I think this is pretty much complete. Let me know if there are any visual glitches.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/openrightsgroup/alidade/issues/74?email_source=notifications&email_token=AAIDREM2XJ6GZW3TUCY4XTLQZQRQ3A5CNFSM4JN43LLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHLUEIY#issuecomment-567755299, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIDREJ4W7BIW7YVJG7PBQTQZQRQ3ANCNFSM4JN43LLA.


Fix typo app version

Codecov Report

Merging #104 (a003997) into main (8563248) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #104   +/-   ##
=======================================
  Coverage   91.33%   91.33%
=======================================
  Files          28       28
  Lines        1396     1397    +1
=======================================
+ Hits         1275     1276    +1
  Misses        121      121

Flag
Coverage Δ

unittests
91.33% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

ggshield/text_utils.py
100.00% <ø> (ø)

ggshield/status.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


KLC Prep Team & Volunteers page

@aharris88
Please add to top of  KLC Prep Team & Volunteers page:
LOTS OF WAYS TO HELP!
We need candy!
We are prepping invitations so that you can invite your friends and neighbors to Kids Life Camp! Please bring the following space-themed candy to the lobby on Sunday mornings NO LATER THAN JUNE 4TH:

Starbursts
Atomic Fireballs
Orbit gum
Milky Way or Mars Bars (bite size or fun size)
If you would like information about serving on one of the following teams, please register below:
Prayer Team
Decorations Team
KLC  Volunteers July 10-14
Clean Up Crew July 16th

Oh, I didn't realize we needed a klc volunteer page. I guess the volunteer link from the klc page should link there.

that’d be great.

On May 18, 2017, at 12:50 PM, Adam Harris<EMAIL_ADDRESS>wrote:
Oh, I didn't realize we needed a klc volunteer page. I guess the volunteer link from the klc page should link there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Mountainview-WebDesign/lifestonechurch/issues/109#issuecomment-302508088, or mute the thread https://github.com/notifications/unsubscribe-auth/AXfBrXepqKI4EttNOUMmIhefcv9DHkhMks5r7JLsgaJpZM4NfpYI.

All For Jesus,
Keely Williams
Administrative Assistant/ Youth Coordinator
Lifestone Church Riverton
817.598.9567
lifestonechurch.net


Update teams-store-validation-guidelines.md

Added update in Tab navigation.
Please also change heading for this image to 'Left navigation in the tab conflicts with Primary Teams Validation'

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
94
80
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 64cb428:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
94
80
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 4827bb7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/submission/validation-navigation-left-navigation.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
94
80
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 10f2f29:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/submission/validation-navigation-left-navigation.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
94
80
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 37113d2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/submission/validation-navigation-left-navigation.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

As the PR is having issues with Build. Raised a new PR 7683 with the same changes and merged the PR.


Error when trying to run from a root folder: ./gradlew build

I just ran from a root folder with debug/stacktrace options and this is the error seen:
       at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
Caused by: groovy.lang.MissingPropertyException: Could not get unknown property 'sourceCompatibility' for project ':wherehows-backend' of type org.gradle.api.Project.
        at org.gradle.internal.metaobject.AbstractDynamicObject.getMissingProperty(AbstractDynamicObject.java:85)

How to fix this?

Dear issue owner,
Thanks for your interest in WhereHows. We have recently announced DataHub which is the rebranding of WhereHows. LinkedIn improved the architecture of WhereHows and rebranded WhereHows into DataHub and replaced its metadata infrastructure in this direction. DataHub is a more advanced and improved metadata management product compared to WhereHows.
Unfortunately, we have to stop supporting WhereHows to better focus on DataHub and offer more help to DataHub users. Therefore, we will drop all issues related to WhereHows and will not accept any contribution for it. Active development for DataHub has already started on datahub branch and will continue to live in there until it's finally merged to master and project is renamed to DataHub.
Please check the datahub branch to get familar with DataHub.
Best,
DataHub team


[ruff] Detect redirected-noqa in file-level comments (RUF101)

Summary

Fixes #14531, where ruff was not reporting diagnostics on  file-level # ruff: noqa comments with redirected rule codes.
The main change here is making ParsedFileExemption closer in structure to Directive, with a sequence of Codes with TextRanges instead of just &str for diagnostic reporting.
Test Plan

The changes were tested against the example code from #14531 to make sure the diagnostic is now emitted.

Perfect. Let me know when it's ready to merge and I hit the button

Awesome, thanks for the reviews! I just noticed that the snapshot metadata is not correct anymore after the signature change (the expression lines should look like expression: "ParsedFileExemption::try_extract(TextRange::up_to(source.text_len()), source,)" now). I ran cargo insta test --force-update-snapshots, but it changed the metadata in a ton of other snapshots too. Should I just update the ones I actually changed here, or ignore this for now?
Otherwise ready to merge!

I think the newest version of insta might be the problem (mitsuhiko/insta#676; adding snapshot_kind: text to the metadata now), but I just added the real changes I caused.

I think the newest version of insta might be the problem (mitsuhiko/insta#676; adding snapshot_kind: text to the metadata now), but I just added the real changes I caused.

Oh interesting: I thought I updated all snapshots to use the new format but quiet possible that I missed some.

Oh interesting: I thought I updated all snapshots to use the new format but quiet possible that I missed some.

I think some of them have been changed back (and some new ones with the old ones have been added) because not all contributors have the latest version of cargo-insta installed


[IAST] Test nodejs and rate limiter (temp)

Temp PR to test the test and rate limiter.
I will remove this PR. I won't merge it

It was only for internal test purpose....close and remove


immutable scopes + orderby

Immutable scopes!
** Scope.set() now returns a new scope instead of modifying the existing one
** Scope.builder() for setting multiple
** New scopes are chained off their parents, and lookup variables by traversing up the parent heirarchy
Evaluating QualifiedExpressions produces Sequence
Visit/Accept passes now pass along a context
Evaluator passes 'current scope' as context
OrderBy does the following
** Map selectors to a lambda of Scope -> Comparable by evaluating the Paxel selector with respect to the scope
** Constructs a new (restarted) sequence over the sorted scopes

/gcbrun

/gcbrun

/gcbrun


add spectrum support

Is your feature request related to a problem? Please describe.
Any plans to add support for the spectrum mode of the A6?  Maybe a drop down menu (like VU Style) for setting the spectrum option and then a way to turn it on and cycle through the different spectrum related views  (the function button does this on the stock remote)?
Describe the solution you'd like
n/a
Describe alternatives you've considered
n/a
Additional context
n/a

@glc650 Thank you for the request!
I will check what I can do. Unfortunately, I won't have time until the weekend so it will take a couple of days.
Chris

No worries.  Thanks for just responding and looking into it.

@glc650 Check out update v0.4.0 🎉!
This adds 2 entities:

Cycle screen mode (Spectrum) as a button entity
Spectrum mode as a select entity

Unfortunately the API doesn't provide a more elegant for combining the VU screen cycle and Spectrum screen cycle. That's the best I can provide right now. Let me know if it works as expected.
In case you like the integration, you star it and/or buy me a coffee: https://www.buymeacoffee.com/hchris1
Chris

Works good thanks.
They are supposed to be improving the API.  Hopefully when that happens you will have more to work with.

Thank you for your feedback. I'll close the issue :)


cache:clear flushes redis db

cache:clear command flushes redis db completely, including sessions, while it's supposed to clear just cache.
Could we change default keys prefix for cache and sessions, something like laravel:cache and laravel:sessions?

It's advised to use different redis databases for different cases, sessions, cache, queue, etc...

Can't find this advise anywhere in docs.
Anyways, I think that there should be some separation by default. Just one more thing not to think about :)

Yeah we'll mention this by the release of 5.5, since Horizon queue must be housed in a separate DB.

Nice, thanks!

So is it mentioned now? I see this:
https://laravel.com/docs/5.5/cache#removing-items-from-the-cache

Flushing the cache does not respect the cache prefix and will remove all entries from the cache. Consider this carefully when clearing a cache which is shared by other applications.

It doesn't mention this. Also, the CacheManager etc uses the same connection by default, so it is a bit confusing. Especially when deployments usually clear the cache for a new release, but that would drop all queues?


network-mode: container:<container_name_without_prefix> does not work

Hi!
Thank you for making containerlab, it's a great project to get into networking.
Problem
I found a problem when trying to use network-mode: container:<container_name_without_prefix>.
The early validation of the container name here works.
But later when trying to get the container status there the cID used is the raw one.
I added some warn locally to make sure I identified the problem correctly and got this:
[...]
WARN[0002] Container [worker2] not found
INFO[0002] node "server2" depends on external container "worker2", which is not running yet. Waited 2s. Retrying...
[...]

You can see that the container is not found at this step, and that it's the short name which is used, not the prefixed one.
Even though the early identification of the container worked and the prefixed container is still running:
$ docker container ls
[...]
dcabb4c3fc8f   kindest/node:v1.27.3   "/usr/local/bin/entr…"   About an hour ago   Up About an hour                               clab-bgp-cplane-demo-worker2

I could try to send a PR to fix this, but I'm not sure which way you would like to handle this.
I can think of two methods:

Isolate the code used to find the container name in a dedicated method and reuse it
Change the container name in the configuration to reflect the real one

The first solution seems easier but does not guarantee that the problem won't happen again elsewhere, I am not sure to know all the impacts of the second one.
Workaround
As a simple workaround, it's still possible to use the full container name.

Hi @pyaillet
if the container you're attaching to is not defined in the clab file, then you must use container name as seen in docker ps output (aka full container name).
Is your parent container defined in the clab file or is it launched outside of clab?

Please provide the topology file.

@hellt the container is not defined in the clab file. It's created with kind, but it used to work with previous versions like 0.31.1 with the attached files.
@steiler I attached the topology file and although the cluster configuration that I use with kind
topo.yaml
name: minimal-reproduction
topology:
  kinds:
    linux:
      cmd: bash
  nodes:
    tor:
      kind: linux
      image: frrouting/frr:v8.2.2
      exec:
        # peer over this link with cilium
        - ip addr add <IP_ADDRESS>/24 dev net0
        # Boiler plate to make FRR work
        - touch /etc/frr/vtysh.conf
        - sed -i -e 's/bgpd=no/bgpd=yes/g' /etc/frr/daemons
        - /usr/lib/frr/frrinit.sh start
        - >-
          vtysh -c 'conf t'
          -c 'debug bgp neighbor-events'
          -c 'debug bgp updates'
          -c 'debug bgp zebra'
          -c '! peer with Cilium'
          -c 'router bgp 65000'
          -c ' no bgp ebgp-requires-policy'
          -c ' bgp router-id <IP_ADDRESS>'
          -c ' neighbor <IP_ADDRESS> remote-as 65001'
          -c ' address-family ipv6 unicast'
          -c '  neighbor <IP_ADDRESS>  activate'
          -c ' exit-address-family'
          -c '!'
    cp:
      kind: linux
      image: nicolaka/netshoot:latest
      network-mode: container:control-plane
      exec:
        # peer over this link with tor
      - ip addr add <IP_ADDRESS>/24 dev net0
  links:
    - endpoints: ["tor:net0", "cp:net0"]

cluster.yaml
kind: Cluster
name: clab-minimal-reproduction
apiVersion: kind.x-k8s.io/v1alpha4
networking:
  disableDefaultCNI: true
nodes:
- role: control-plane
  kubeadmConfigPatches:
  - |
    kind: InitConfiguration
    nodeRegistration:
      kubeletExtraArgs:
        node-ip: "<IP_ADDRESS>"
containerdConfigPatches:
- |-
  [plugins."io.containerd.grpc.v1.cri".registry.mirrors."localhost:5000"]
    endpoint = ["http://kind-registry:5000"]

However if you think that it was just by chance that it worked in older version, and that it's not really a feature, I can still use the full container name.

Let us have a closer look @pyaillet
Maybe indeed we can make short name to work (again), but using a full name is an easy solution to get you unblocked.

@pyaillet Took a look at the whole scenario now.
TLDR; The implementation is correct as it is right now.
So what you can do is reference same topology file based containers via its short name like so:
cp references l1's network namespace.  (Although it is missing clab specific labels etc.).
External containers even though referenced in the network-mode. Must be referenced via its full name. If that stuff did work at some point in time it was pure luck and not intended to work that way. Sorry.


Deposits to VEGA appear in associated too section of ETH wallet (they should not)

To recreate.
Use a ETH key to populate the reward pool https://www.notion.so/vegaprotocol/Contracts-Cheatsheet-2fb290daaa4d4b71993c3ef49dfa57ff
(probably the same if you do a deposit.
e.g. of depositing to the reward pool on Stagnet1 https://ropsten.etherscan.io/tx/0x3daafcb30e69952e13e274b511525cc74914b9de3bf606ad853225b332592eda
Go to token front end. notice the association to 0x0000

Reward pool deposits and general deposits should not show up in this list. only Association actions.

This has been fixed


Add support for Razor Pages and custom endpoint path

I noticed that this lib, while it does work with Razor Pages and shows their routes, it does not show the real page name (view engine path) compared to Controller and Action being shown for Action methods. So I added a new entry to the JSON that shows the page name.
I also added support for custom endpoint path, so users can use something else than the default /route-debugger.
Some other minor improvements:

removed unnecessary async-await
made the StreamReader dispose
added link to Bootstrap CDN to the sample app as the link pointed to non-existing files and the page looked unnecessarily ugly
made the JSON output be indented for better readability; on the screenshot I see that in Edge it probably is formatted by default, but Chrome outputs one unreadable auto-wrapped line so now it's readable even there :smile:
I noticed that the Developer Exception Page does not work if registered earlier in the pipeline than this lib, so I added a note about it to the readme

PS: Cool profile picture 😎

Looks good, thanks! @bramborman


Issue 2114 - Update spotbugs plugin in ingest-batcher-submitter module

Make sure you have checked all steps below.
Issue

[x] My PR addresses the following issues and references them in the PR title. For example, "Issue 1234 - My Sleeper
PR"

Resolves https://github.com/gchq/sleeper/issues/2114

Tests

[x] My PR adds the following tests OR does not need testing for this extremely good reason:

Fixed spotbugs issues

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it, or I have linked to a
separate issue for that below.
[x] If I have added, removed, or updated any external dependencies used in the project, I have updated the
NOTICES file to reflect this.

Closing as we'll disable the Spotbugs rule instead, see issue:

https://github.com/gchq/sleeper/issues/2133


Uncaught Invariant Violation: Unable to find node on an unmounted component

Hi all. Need help with issue when using "@material-ui/core": "3.9.3"
The issue is that in some random cases i got an error - "Uncaught Invariant Violation: Unable to find node on an unmounted component." at ref (webpack:///./node_modules
/@material-ui
/core/Slide/Slide.js?:261:52) .
It looks like findDomNode is deprecated in react 16, any updates to
@next
or latest versions are not helpful.
How can i resolve it ?

@vsshaposhnikov I would encourage you to try v4. The problem might have been resolved.


ENH small cleaning and optimizations accross the repo

[x] Replace signature exposing sizes with a signature exposing one argument shape
[x] Where applicable, use 2D grid of work items rather than 1D + divisions

note: found this piece of information: https://stackoverflow.com/a/15044884 suggesting that:

2D grid really are better for performance because doing // and % ops in the kernel is expensive
it indexes work items in a "row major order" meaning that items in the same row belong to the same sub group (/warp)

even if the previous information applies to cuda. I assume it's also true for numba-dpex/ sycl

[x] some kernels are now written only for a given shape and reused for other dimension with reshaping tricks.
[x] also use 2D grids for kmeans kernels
[x] document better the use of centroids_private_copies_max_cache_occupancy and improve the heuristic using device.max_compute_units
[x] a couple more nitpicks

It's WIP because using 2D groups for the sum over axis 0 kernel seems to trigger weirg bugs like in https://github.com/IntelPython/numba-dpex/issues/892 in some of the tests.
Out of WIP, remaining issues were unrelated, PR is green.

Out of WIP. See the top level post for the list of changes.

Something is wrong with sum(axis=1) on CPU when work_group_size is >=8. Maybe another bug in the JIT or something we don't understand about group sizes on CPU (or a bit of both). In both cases the investigation looks complicated and CPU is not the priority target so the latest commit propose forcing work_group_size == 8 with work_group_size was set to max.
I'll also run this branch on the dev cloud with the flex170 to see if it shows any performance improvement, and play with the group size to see if it affects performance more than it seems to do on local iGPU.

I've reduced the last failure on the pipeline to what appear to be a JIT issue. The merge will be blocked until it's fixed. It's likely the same JIT issue we've seen before and it gave a much nicer reproducer. See https://github.com/IntelPython/numba-dpex/issues/906 .

TY for the careful review @ogrisel @jjerphan the last commit should address your suggestions and I've answered some of your comments.

Perfect. :+1:
I leave @ogrisel merge.

The tests are still red. Ok for merge once fixed.

The tests that fail because of https://github.com/IntelPython/numba-dpex/issues/906 we can merge as soon as it's fixed and we can bump
If there's a conflict with other branches before that we can merge except the diff on the 2d sum kernel.

Closed via https://github.com/soda-inria/sklearn-numba-dpex/pull/98 and https://github.com/soda-inria/sklearn-numba-dpex/pull/96


Add authentication directive to authenticate users

This commit adds a directive to handle authentication. Authentication is
handled in the following way.
If a JSON web token provided in the Authorization header then one of
three things can happen:

Token Valid and User in Database: request proceeds
Token Valid and User not in Database: rejected
Token Invalid: rejected

If no Authentication is provided then an anonymous user is attached to
the request.
Also slightly cleans up the routes by converting them to traits.
We still need to do some work on Authorization, creating users if they are not in the database yet, and also determining what endpoints should allow anonymous users and not.
Testing

Start up a development environment, running vagrant up --provision after switching to this branch
Start up the webpack server and log in
After logging in, grab your JWT

Start up the application server (./scripts/server)
Make the following requests and observe their output

Request
Response

curl localhost:9000/api/users
The supplied authentication is invalid

curl localhost:9000/healthcheck
Returns healthy status

curl -H "Authorization: Not" localhost:9000/api/users/
The supplied authentication is invalid

curl -H "Authorization: <TOKEN>" localhost:9000/api/users/
The supplied authentication is invalid

At this point you can create your user with your email address with some SQL:
psql -h localhost -U rasterfoundry
# password rasterfoundry

CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
INSERT into users VALUES (
        uuid_generate_v4(),
        '2016-08-25T17:43:21+00:00',
        '2016-08-25T17:43:21+00:00',
        true,
        true,
        '<YOUR EMAIL>',
        '<YOUR FIRSTNAME>',
        '<YOUR LASTNAME>',
        '<UUID of ROOT ORG>'
);

Finally, make the request to the users endpoint with your token again: curl -H "Authorization: <TOKEN>" localhost:9000/api/users/. This time it should succeed.

:+1:

shouldn't it be Authorization: Bearer {TOKEN}? I think that's the standard way to use jwt tokens in headers.
https://jwt.io/introduction/#how-do-json-web-tokens-work-

Good point, I'll switch this up


Utility suggestion: fetchPatchFromGitHub

In a quick search I have found 1780 instances of patches from GitHub repos.
I think it deserves a thin abstraction.

I'm somewhat on the fence about this, I don't think the added attributes to juggle really add much in terms of readability versus fetchpatch, given GitHub's convenient patch URLs.
fetchPatchFromGitHub {
  name = "fix-gcc13-build";
  owner = "InsightSoftwareConsortium";
  repo = "ITK";
  rev = "9a719a0d2f5f489eeb9351b0ef913c3693147a4f";
  hash = "sha256-dDyqYOzo91afR8W7k2N64X6l7t6Ws1C9iuRkWHUe0fg=";
}

doesn't really look much better compared to:
fetchpatch {
  name = "fix-gcc13-build";
  url = "https://github.com/InsightSoftwareConsortium/ITK/commit/9a719a0d2f5f489eeb9351b0ef913c3693147a4f.patch";
  hash = "sha256-dDyqYOzo91afR8W7k2N64X6l7t6Ws1C9iuRkWHUe0fg=";
}

This single example triggered the sliding bar from GitHub web interface.
Also we have fetchDebianPatch,  a rarely used function - 37 hits, some of them being re-implementations.
If fetchPatchFromGitHub looks bad, then fetchDebianPatch looks equally bad.

should it be named fetchGitHubPatch for consistency with fetchDebianPatch?

I believe we should give names to those functions in the following fashion:

low level: fetch<object>

fetchurl  fetchzip  fetchbzr  fetchpatch

high level: fetch<object>From<place>

fetchFromSavannah fetchFromGitLab

In this case fetchDebianPatch should be called fetchPatchFromDebian
But it's a little too late to retcon this.  The best we can possiblly do is to create fetchPatchFromDebian later.

fetchPatchFromDebian is visual noise to me, it's too many short camel-case words. it also implies "debian" is a place, which i would argue it is not.
i also think fetchYFromX looks too close to fetchFromX when skimming code.

Short camel-case is typical on Nixpkgs, since it is hard to pass kebab-case variables to shell. dontUseCmakeConfigure and friends come to mind.

yes, "short" and "camel case" are the two adjectives which can't really be changed, however we can easily use less words by making it just fetch*Patch.

I'd recommend we not waste time bikeshedding about a function name when it's debatable if it's even useful to have.

Then I vote for removing fetchDebianPatch.

I will remove fetchDebianPatch, then.


Added logic for the calculation.

In this milestone, I added the following changes :

According to the project requirements:

[ ] Created a new directory called logic inside the project.

[ ] Copied the files calculate.js and operate.js into the logic/ directory that is suggested.

[ ] Installed big.js using NPM install command.

[ ] Implemented click event handlers using the math logic from calculate.js and operate.js in all React components.

[ ] Tested my math-magicians app in the browser. The Calculator has been able to perform math operations.

Hello @BregornOriginal,

[ ] Thank you for the approval with appreciation.😍😍😍


Dont crash when rules in role is null

Was getting this with kubectl 1.14.6

Thanks a lot @Quiark and LGTM … any objections @luksa?


Write a set of code solutions: "php pcntl" (php-pcntl)

Please write code solution for this topics:
php pcntl (technology: php-pcntl)
Fast way
Just write the code solution(s) in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

How to use PCNTL alarm in PHP?
How to install PCNTL for PHP using Brew?
How to check if PCNTL is enabled in PHP?
How to use PCNTL fork to manage MySQL connection in PHP?
How to dispatch PCNTL signals in PHP?
How to install PHP PCNTL extension in Docker?
How to create a daemon using PCNTL fork in PHP?
How to use PCNTL signals in PHP?
How to install PCNTL for PHP in Debian?
How to use the PCNTL_EXEC function in PHP?
How to use the PCNTL_FORK function in PHP?
How to use shared variables with the PCNTL_FORK function in PHP?
How to use shared memory with the PCNTL_FORK function in PHP?
How to prevent zombie processes with the PCNTL_FORK function in PHP?
How to get the process ID with PHP PCNTL?
How to kill a process with PHP PCNTL?
How to use pcntl_signal in PHP?
How to use pcntl_fork in PHP?
How to use pcntl_waitpid in PHP?
How to use pcntl_wait in PHP?
How to use pcntl_wifexited in PHP?
How to use pcntl_wexitstatus in PHP?


networkx + pywebview + py2exe = 💣

self rendered version (tag 0.0.1) works with py2exe  as well as with py2exe.freeze but as soon as there is a dependency to networkx and/or pywebview the creation of an exe breaks...

also try pygraphviz and py2exe.freeze


E2E: clusterFirst DNS liveness probe

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

E2E: clusterFirst DNS liveness probe

LGTM. Are we going to merge this?

I think it's unfinished. The problem reported was that ClusterFirst DNS + external resolvers was broken. So we want to add the external resolvers.


npm release and programmatic API hooks

I think it would be nice if we'd have programmatic API hooks so that a developer of an HMR library can register a callback that is called after a Web Component mutated:
import {registerOnUpdate, applyPolyfill} from "@vegarringdal/customElements-hmr";
import {someVirtualDOMAPI} from "@some-org/some-framework";

// somewhere in bootstrap of the app
applyPolyfill();

// some HMR lib we have no control over
registerOnUpdate((elementTagName: string) => {

    // re-render elements which have changed
    someVirtualDOMAPI.clearAndRenderByTagName(elementTagName);
});

Something like that.
someVirtualDOMAPI.clearAndRenderByTagName could be application code or framework code, depending on the integration.
Finally, it would be nice to release this polyfill and it's API as an npm package, so everybody can use it.
Fuse-box could require it per default -- but -- if the developer has no direct control over what to do after Web Component code change, the application might break (in case we would basically throw away and re-apply the whole  content like we do atm)

Yes, good idea.
If we release it we can call it just customelements-hmr or custom-element-hmr.
This way its easy to remember.
Ill reorginize the repo so it will be easy to publish and have samples running when developing
Ill continue on the dev repo.
Ill send a update when Im done.


[python][bug] Dynamic Property bug with DYNAMIC_PROPERTY_GRADING_PRIMARY

Hello,
Executing the following snippet :
import PyOpenColorIO as ocio

# ! REPLACE CONFIG_PATH !
config = ocio.Config().CreateFromFile(CONFIG_PATH)

gp = ocio.GradingPrimary(ocio.GRADING_LIN)
gp.clampBlack = 0.5
trsfm = ocio.GradingPrimaryTransform(
    gp,
    ocio.GRADING_LIN,
    dynamic=True,
)
proc = config.getProcessor(trsfm)
print("proc created.")

shader_desc = ocio.GpuShaderDesc.CreateShaderDesc(language=ocio.GPU_LANGUAGE_GLSL_4_0)
ocio_gpu_proc = proc.getDefaultGPUProcessor()
ocio_gpu_proc.extractGpuShaderInfo(shader_desc)

dyn_prop_type = ocio.DYNAMIC_PROPERTY_GRADING_PRIMARY
if shader_desc.hasDynamicProperty(dyn_prop_type):
    dyn_prop: ocio.DynamicProperty = shader_desc.getDynamicProperty(dyn_prop_type)
    dyn_prop.setDouble(2.66)
    print("DynamicProperty updated.")

print("Success")

Raises :
line 25, in <module>
    dyn_prop.setDouble(2.66)
PyOpenColorIO.Exception: Dynamic property value is not a double.

And I think it's not expected ?
Perhaps there is a missing float/double conversion is the cpp API ?
CONTEXT:

Windows 10
PyOpenColorIO 2.1.1

Cheers.
Liam.

Hmm or perhaps the error is on my side haha, opened the issue to quick this time my bad !
I think I'm supposed to do :
    ...
    dyn_prop.setGradingPrimary(gp)
    ...

Which seems more logical.
I was just confused by the error which doesn't explicitly tell me that I did something wrong.


Default to http-stream format for new functions

Should probably wait for a few more FDKs, but this is here when we want it.

@rikgibson what about --runtime docker

actually... looks like that creates a funcfile with no format

 --runtime value                Choose an existing runtime - go, java8, java9, java, node, python, python3.6, python, python3.7, ruby, kotlin
docker is not a supported value at this time - if the CLI is still accepting it as such then that should be removed too.


add few lines in readme about development experience

how do you run it in dev mode?
how to install into other project while keeping live-reload on change to lib ?

that's kind of up to you. this is just a baseline to get it to generate types and proper outputs.
it sounds like you want something like vite or parcel for that level of use.


deps: fix release pipeline

My understanding was maven-publish was enough to run these scripts. It got staged. Would you mind taking a look?


Question about Table behaviour

The question concerns the behaviour of the KeepWith property of rows.
If I don't set this property I get a nice table that flows over to the next page.
Simple example 1:

            var document = new Document();
            var section = document.AddSection();
            var tableFlowToNextPage = section.AddTable();
            tableFlowToNextPage.Comment = "This is a table that is allowed to flow over to next page and does that nicely."; ;
            var column = tableFlowToNextPage.AddColumn();
            var range = Enumerable.Range(0, 70);
            foreach (var value in range)
            {
                var row = tableFlowToNextPage.AddRow();
                var pdfCell = row.Cells[0];
                pdfCell.AddParagraph(value.ToString());
            }

If I want my tables to behave such that they keep together while they can, it is foreseen that the property KeepWith it set to index of the last row. The default behaviour is that the whole table is grouped together then. This works perfect for tables shorter than one page. But as they are larger than one page the behaviour is such that it isn't drawn on the page.
See underneath simple example 2 (this can be added to the above code):

            var firstRow = tableFlowToNextPage.Rows[0];
            firstRow.KeepWith = tableFlowToNextPage.Rows.Count - 1;

My question is now: Would a hybrid solution considered as a feature. i.e. one would be able to set the KeepWith property to the index of the last row and keep the table together while it is shorter than one page. But as the whole table doesn't fit on the page fall back to the flow over to the next page?

The current implementation of KeepWith is simple: The rows keep together and will never break apart. So use KeepWith with care.
Feel free to come up with an implementation where the page border overrides KeepWith.


A  basic solution to challenge

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

I've made a minor change to number the solutions

Thanks @Samueltommzy  for contributing to this repo! 👍
We're glad to accept your changes and look forward to more contributions from you!

Thank you


Updates Spring to 5.3.23 on the 1.5 branch

Description
Updates Spring to 5.3.23.
This was probably updated via dependabot and thus not backported.
Issues Resolved
N/A
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed with a real name per the DCO

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.

The WhiteSource check appears to be validating against main where we have some additional updates to testing / performance code.


Include content blocks in website search broken for SS4 - waiting got fulltextsearch upgrade

Currently architecture will be fragile once we add https://github.com/dnadesign/silverstripe-elemental/issues/84

Progress for SS4 on fulltextsearch: https://github.com/silverstripe/silverstripe-fulltextsearch/pull/141

cc @nicolewilliams16 - this is blocked by a fulltextsearch upgrade to SS4 at the moment

Full text search is now SS4 compatible, and once https://github.com/silverstripe/silverstripe-fulltextsearch/pull/173 is merged should be testable with this module.
I've tested by indexing element data and returning it in a frontend search context, which is fine.
I've suggested that we add an indexer that will use combined element content for a page and index it in Solr as the page content, to ensure default frontend search queries will show matched content under the context of the page that owns the matched content.


docs(examples): update firebase example to use .env

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add import.meta.env support

This'll be required to consume glimmer-vm as it is published today.
Work spawned from: https://github.com/emberjs/ember.js/pull/20561

gonna pursue an alternate route where glimmer-vm packages use proper conditional exports (package.json config)


Immer - Immer forbids circular references

I am trying to query some post and I keep running into the same error: [Immer] Immer forbids circular references
import { DataStore } from '@aws-amplify/datastore';
import { Post } from '../../models'
export default function HomeScreen ({ navigation }) {
const [post, setPost] = useState([]);
const fetchPost = async () => {
const results = await DataStore.query(Post);
setPost(results);
};

useEffect(() => {
fetchPost();
}, []);

Correct, as documented Immer is designed for immutable trees. Something that has circular references is not a tree. If there are mutable objects in your tree that should be ignored, see the immerable symbol in the documentation on how to ignore those.

https://immerjs.github.io/immer/complex-objects


feat: add config.prelude to allow setting default role/session

For those who want aichat to enter a session after startup, you can set it as follows:
prelude: session:mysession

For those who want aichat to use a role after startup, you can set it as follows:
prelude: role:myrole

close #220

How to set prelude in order for aichat to enter a session and a role by default after startup?

@meawal  Impossible
The session includes the role.


Ability to ignore pod errors related to Ec2 spot instance use

Overview
Currently we are using Ec2 spot instances which take time to spin up and cause false positive errors. To reduce noise in slack channel we would like a feature to ignore pod error related to,
0/6 nodes are available: 1 Insufficient memory, 5 node(s) didn't match Pod's node affinity.
Node is not ready
Readiness probe failed:
Liveness probe failed:
Acceptance Criteria
Ability to ignore pods by event.reason using custom yaml file.

Hey @AliHas78, please upgrade to the latest Botkube version and use event constraints for Kubernetes source. See the docs here: https://docs.botkube.io/configuration/source/kubernetes#event-and-resource-constraints
Hope that fixes your problem. If not, feel free to reopen this. Cheers!


Upgrade Kratos dependency to v0.10.1

What does this PR change?

Upgrade Kratos sdk to v0.10.1

Does the PR depend on any other PRs or Issues? If yes, please list them.
Part of https://github.com/paralus/paralus/issues/92
Checklist
I confirm, that I have...

[ ] Read and followed the contributing guide in CONTRIBUTING.md
[ ] Added tests for this PR
[ ] Formatted the code using npm run format (if applicable)
[ ] Updated documentation on the Paralus docs site (if applicable)
[ ] Updated CHANGELOG.md

Moved commit to https://github.com/paralus/dashboard/pull/152


Error on Before Save and After Save at cloud code

Using this code on beforeSave and afterSave methods, saves a blank row with no data :
Parse.Cloud.beforeSave(Parse.Object.extend("Look"), function(request,response) {
	 // Set up to modify user data
 	alert("Calling before save for look");

	//For Expiring a look when look marked rejected
	for (var i in request.object.dirtyKeys()) {
		 	alert("Calling before save for look 1");

  		var dirtyKey = request.object.dirtyKeys()[i];
  		alert("dirty key for look aftersave"+dirtyKey);
 		if(dirtyKey == "eventState" && request.object.get("eventState") == 2){
 			//Also expire this look
 			request.object.set("expired",true);
 			alert("Look expired");

			var pushQuery = new Parse.Query(Parse.Installation);
 			var userIdQuery = new Parse.Query(Parse.User);
			var message = "Your look has been rejected by the event administrator.";
			var fromUser=request.object.get("fromUser");

			userIdQuery.equalTo("objectId", fromUser);

			pushQuery.matchesQuery('user', userIdQuery);
			Parse.Push.send({
					where: pushQuery,
					data: {
						alert: message,
						type:"lookRejected"
					}
			}, {
				success: function() {
					alert("Push went successfully For Look Rejection!");
				},
				error: function(error) {
					alert("Error executing: " + error.code + " " + error.message);
				}
			});

 		}
 	}

 	response.success();

});

Parse.Cloud.afterSave(Parse.Object.extend("Look"), function(request) {
	 alert("Calling before save for look");

	var userId = request.object.get("fromUser");
	var inappropriate = request.object.get("inappropriate");
	var like = request.object.get("likes");
	var dislike = request.object.get("dislikes");
	var pushQuery = new Parse.Query(Parse.Installation);
	var userIdQuery = new Parse.Query(Parse.User);
	var message = "The results are in! See what people think of your latest look.";
	var typeObj="like";
		 alert("Calling before save for look 1");

	if(typeof dislike != "undefined"){
		like = like + dislike;
	}
	userIdQuery.equalTo("objectId", userId);
	userIdQuery.equalTo("lookResponse", like);

//	if(typeof inappropriate != "undefined" && inappropriate != '' && inappropriate){
//		message = "Your look has been marked inappropriate!!";
//		typeObj="inappropriate";
//	}else{
//		userIdQuery.equalTo("lookResponse", like);
//		message = "Hey! your looks are fetching likes!"
//		typeObj="like";
//	}

		 alert("Calling before save for look 2");

	pushQuery.matchesQuery('user', userIdQuery);
	Parse.Push.send({
			where: pushQuery,
			data: {
				alert: message,
				type:typeObj
			}
		}, {
			success: function() {
				alert("Push went successfully!");
			},
			error: function(error) {
				alert("Error executing: " + error.code + " " + error.message);
			}
	});

});

Hi @manishnath, thanks for your code snippet. Is it possible for you to figure out which part of your code does not work? If not, could you copy paster your logs? Thanks.

Hello Mengyan,
The problem is that when I uncomment the beforesave method it does not give
any logs. This is happening only on Ios and not Android whereas both are
following same saving pattern. The issue is in the beforesave method only -
but even if I comment the entire method , it does not work.
I hope that gives you something to work with.
Regards,
Manish
On Oct 10, 2015 3:05 AM, "Mengyan Wang"<EMAIL_ADDRESS>wrote:

Hi @manishnath https://github.com/manishnath, thanks for your code
snippet. Is it possible for you to figure out which part of your code does
not work? If not, could you copy paster your logs? Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/ParsePlatform/Parse-SDK-JS/issues/46#issuecomment-146991037
.

Hi @manishnath, it is very helpful for us to know the beforeSave does not work well in your case. But it seems you do lots of stuffs in beforeSave, like loop dirty keys, do ParseQuery and send pushes. Is it possible for you to tell use which part of the beforeSave does not work?

Hey , Thanks for responding. The issue is that this code is working for
Android but not for iOS. Both platforms are using same query mechanism.
Using this same code in afterSave works beautifully. Also I am unable to
print any logs so cant pin point where the problem lies :(
On Wed, Oct 14, 2015 at 1:36 AM, Mengyan Wang<EMAIL_ADDRESS>wrote:

Hi @manishnath https://github.com/manishnath, it is very helpful for us
to know the beforeSave does not work well in your case. But it seems you
do lots of stuffs in beforeSave, like loop dirty keys, do ParseQuery and
send pushes. Is it possible for you to tell use which part of the
beforeSave does not work?
—
Reply to this email directly or view it on GitHub
https://github.com/ParsePlatform/Parse-SDK-JS/issues/46#issuecomment-147836852
.

--
MANISH NATH

Hi @manishnath,

What do you mean you can not print any logs? If alert does not work, could you try to replace alert with console.log to see what happens?
It seems your cloud code does not return any value to clients, so what do you mean this code is working for Android but not for iOS? Android can receive the push but iOS can not?

It works when I put the same code in afterSave
When I put this code in beforeSave  - The same code works when a save
query is made from Android but not from iOS
I can check by putting console.log

On Wed, Oct 14, 2015 at 11:26 PM, Mengyan Wang<EMAIL_ADDRESS>wrote:

Hi @manishnath https://github.com/manishnath,

What do you mean you can not print any logs? If alert does not work,
could you try to replace alert with console.log to see what happens?
It seems your cloud code does not return any value to clients, so what
do you mean this code is working for Android but not for iOS? Android can
receive the push but iOS can not?

—
Reply to this email directly or view it on GitHub
https://github.com/ParsePlatform/Parse-SDK-JS/issues/46#issuecomment-148135773
.

--
MANISH NATH


Backmerge upstream

What I had to do:

Sync branch upstream-main branch with SE-2 (in the GitHub UI... but you can also add the remote locally and do it locally)
Pull upstream-main locally
Create backmerge-upstream branch from the main branch
Merge upstream-main => backmerge-upstream
Fix conflicts

This will be particular for every case, maybe we should document it (if it's not already). In this case I had to "accept yours" in the root package.json file and add the next:serve manually into the template/base package.json.
6 Run yarn add changeset to create the changeset file (selectect "patch")

Create PR. Since this is a fork, it automatically points to the SE-2 repo, so I have to manually change it (not sure if there is a way to default to this repo, even if it's a fork).

Some of this can be used to update the Contributing guide #4

I think we need to merge this (without squash) to keep the commits from SE-2 (if not we'll encounter weird conflicts).
If we merge:

A PR will be automatically created. e.g. https://github.com/scaffold-eth/create-eth/pull/5
When that PR is merged, the NPM package will be published
If we don't want to merge, we can still keep PRing other PRs into main (with changeset) and the "version packages" PR will update automagically.

Open to new workflows if you all can think of something better. This one is not simple, but it works for now :D

Lgtm!

Create PR. Since this is a fork, it automatically points to the SE-2 repo, so I have to manually change it (not sure if there is a way to default to this repo, even if it's a fork).

As I understand if you're forked repo, there is no way to change default to this repo. I think good way is to just duplicate the repo. It allows to do everything you mentioned, but it won't point to se-2 repo since it's not a fork.
Example of duplicated repo.
Since there's already changes in this repo (create-eth), probably it's worth

To synchronize it with se-2
Rename it to some "new-repo-name"
Create new repo "create-eth"
Duplicate "new-repo-name" to "create-eth"

or smth like that. Maybe 2. duplicate to "new-repo-name" 3. Duplicate "new-repo-name" to "create-eth"
But keep in mind that issues/prs are not copied, so it need to be stored somewhere before copying

. I think good way is to just duplicate the repo.

This might be a good idea @rin-st
I guess the only thing that we'll lose is the UI sync?

Which I guess is ok, we can do it on our computer (we can add the SE-2 core as remote and sync from there)
And I guess if someday we want to sync the other way around (create-eth => se-2) having a fork is handy.
Let's hear what @technophile-04 thinks too!


FALCON-2274 Job list in extension

dev-tested
falcon extension -list
Hadoop is installed, adding hadoop classpath to falcon classpath
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/local/falcon/falcon-distributed-0.11-SNAPSHOT/client/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/hdp/<IP_ADDRESS>-2/hadoop/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
4
sampleAsc    extension-example
sampleAsc2    extension-example


What happens with result publication and the COVID WAM rule?

How do marks excluded from the WAM calculation due to COVID appear on the results page, and how does this app see them? Will it complicate any future attempts at solving #17?
I don't have any results from this semester yet, and none from last semester, so if someone already knows what this all looks like on the results page, please feel free to fill me in. Alternatively, I'm sure I'll be able to see for myself what a lower-than-current-WAM result looks like some time in the next few days.

Not totally across the details - but can confirm this is what currently sits in my results.txt (made up results):
(Started degree at beginning of 2020. Completed two subjects in Semester 1 and no WAM yet)
"Master of Information Technology": {
    "wam": null,
    "results": [
      {
        "subject": "COMP90041 Programming and Software Development",
        "date": "2020, Semester 1",
        "mark": "95",
        "grade": "H1^",
        "credits": "12.500"
      },
      {
        "subject": "INFO90002 Database Systems & Information Modelling",
        "date": "2020, Semester 1",
        "mark": "95",
        "grade": "H1^",
        "credits": "12.500"
      }
    ]
  },

Let me know if there's something particular that'll be useful to check.

Thanks for this sample.
It's interesting that you have no WAM yet. When I completed the first two subjects of my Master of Science (CS) in 2019, I certainly got a WAM. Maybe there's part of the COVID rules for new students' WAM calculation which I missed (probably because it wouldn't apply to me), which is why your average has not been calculated yet?
As for the subjects, that '^' character next to the grade must come from the COVID rule. I guess it means 'this result was excluded from the WAM calculation'. My results.txt has grades without '^' (from 2019 and earlier) and this caret symbol is the symbol that I understand to be used on official transcripts for the same purpose.
In conclusion, I suppose 2020 does indeed complicate #17. That project will need to take into account that 2020 subjects are only included in certain situations when it is reverse-engineering the WAM calculation. At least all the necessary information is contained in the data we already record :).

To complete the picture it seems:

This semester, the results are released regardless of the current WAM, and the WAM is updated,
The '^' and revision to the WAM will apparently happen at a later date.

Assuming the COVID rule disappears after this semester, this might not be relevant for #17.


Is this project discontinued?

Hi Guys
I'm really interested to know if there is any plan to update this SDK based on latest changes on Partner Center REST API or do any minor bug fixes and improvements. Based on the state of issues and the only open pull request that has not been even reviewed after 7 month, it looks like that this is a sort of abandoned project.
I was thinking about doing some improvements in this SDK (on behalf of my company) but it's not clear if our pull requests would be merged at all. Of course we can fork it and start developing our own branch, but the changes/improvements we need, can easily be implemented in a more general way so that it could be used by others (and vice versa).
@tameemansari Your input is appreciated
Regards
Ehsan

Let me check and follow up. can you drop me an email tansar at Microsoft. Thanks.

@isaiahwilliams has offered to help the broader community and has recently updated the codebase to bring it to parity with the .net sdk.


Option for s3.end_date_interval and other minor enchancement

Created an option for explicit default in s3.end_date_interval
Using S3.start_end_date in hrm_credential

@flavour  Made the Changes. Any other Suggestions?
@nursix Please Review

@flavour Done. Please Review

@flavour Please Review

Very close now :)

@flavour Done, Please Review


Upgrades the react-mega-menu sample to SPFx version 1.6.0

Q
A

Bug fix?
no

New feature?
yes

New sample?
no

Related issues?
fixes #X, partially #Y, mentioned in #Z

Upgrades the react-mega-menu sample to SPFx version 1.6.0

thx Velin, appreciated.


stroke and stroke-width should be moved up to the svg element.

The user of the library needs to be able to set the color of the icon if the "stroke" is declared in the "path" element of the svg we won't override it with attribute splatting.
Instead the script should move the stroke and stroke width values up to the svg so they can be overriden.
See https://blazor-university.com/components/replacing-attributes-on-child-components/
Similar to the following:

fixed in PR #16


GPTTreeindex: limit # of active async llm calls, balance chunks per node, remove non-utf8 chars from doc_text

suggest two tiny improvement for building GPTTrees, for problems I ran into:

problem 1: with num_children 10 and 11 nodes on level 1, tree would build root node 1 with 10 childs, root node 2 with 1 child; performs better if balanced: root node 1 and 2 with 5 children each.
problem 2: when having many chunks, e.g. ingesting whole books, async is important for indexing performance, but hundreds of async llm api calls mean chaos (rate limits, retries, timeouts), so idea: limiting number of active async jobs as possible fix.

sure, added the test for node balancing. as for the async job limit, I'm not sure. Looks like you patched out all async calls for testing right now... you want to test that, too? Now sure how to do that without messing with your test setup too much :-)

added small fix, mongo db cannot persist chunks that contain invalid characters such as surrogates, which seem to occur in texts that include mathematical formulas.

@mesa-ai would you be able to help resolve merge conflicts?

I'm going to close this for now, since the recent factor to how tree summarize works kind of invalidates the work here
Feel free to open another PR with the async limiting stuff though!


Ecx htl v0.8 test

添加monitor-type=3 axescripttype

Could you please rebase the branch? Thanks!

/close


Add more detailed instructions for 'yum' and 'zypper' package managers.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

latest/docs-ref-conceptual/install-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest)

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


Fix status issue for GitLab Merge Requests

Issue:
https://github.com/openshift-pipelines/pipelines-as-code/issues/1421
When users create Merge Requests in GitLab, there is currently no indication of success or failure.
Fix:
This commit addresses the issue by adding eventType as Merge Request
Signed-off-by: Savita Ashture<EMAIL_ADDRESS>
Changes

Submitter Checklist

[ ] 📝 A good commit message is important for other reviewers to understand the context of your change. Please refer to How to Write a Git Commit Message for more details how to write beautiful commit messages. We rather have the commit message in the PR body and the commit message instead of an external website.
[ ] ♽ Run make test before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI. (or even better install pre-commit and do pre-commit install in the root of this repo).
[ ] ✨ We heavily rely on linters to get our code clean and consistent, please ensure that you have run make lint before submitting a PR. The markdownlint error can get usually fixed by running make fix-markdownlint (make sure it's installed first)
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

/retest


Deprecate badge

Shouldn't we get rid of the text altogether? Just a note that it's been deprecated?

We should probably also run this via the council, I will integrate it into the slides for next week.


LSTMCell base article at rnn_cell_impl.py

The implemented LSTMCell makes use of the "forget gate". The base article pointed out in both comments (lines 650 ~ 661) and tensorflow's documentation does not cover the concept of "forget gate".
This concept was introduced by Gers et al. only in 1999 with "Learning to forget: Continual prediction with LSTM".

I signed it!

Hi Eugene, any insights where the implementation came from?

LGTM

Hi Vinícius, thanks for the pull request.
Can you submit this to the master branch? This release branch has already been cut and the build team is not accepting docs cherry-picks.
Thanks!


Automatically logged out after less then 2 minutes.

Hello all,
When I use this package, it throws me out of the backoffice every two minutes or so.
I don't even have this plugin enabled, only installed.
When i monitor the console, I see that after it requests https://localhost:44326/umbraco/backoffice/UmbracoTrees/ContentTree/GetNodes?id=1094&application=content&tree=&isDialog=false, it gives the following 401:
)]}',
{"Message":"Authorization has been denied for this request."}

is there some kind of timeout parameter I need to set for it to not throw me out every two minutes?

Also experiencing this issue. It doesn't appear to be cookie expiration. I'll see if I can debug, but any thoughts would be appreciated!

The only thing that I can see at the moment that might be this:
https://github.com/Offroadcode/Umbraco-2FA/blob/master/Umbraco2FA/Umbraco/Fortress/Startup/FortressOwinStartup.cs#L66
app.UseTwoFactorSignInCookie(global::Umbraco.Core.Constants.Security.BackOfficeTwoFactorAuthenticationType, TimeSpan.FromMinutes(5));

will try adjusting the 5 minute cookie timeout

The only thing that I can see at the moment that might be this:
https://github.com/Offroadcode/Umbraco-2FA/blob/master/Umbraco2FA/Umbraco/Fortress/Startup/FortressOwinStartup.cs#L66
app.UseTwoFactorSignInCookie(global::Umbraco.Core.Constants.Security.BackOfficeTwoFactorAuthenticationType, TimeSpan.FromMinutes(5));

will try adjusting the 5 minute cookie timeout

I saw that too about a week ago. But since it times out within two minutes, I don't think that is our problem.. I will also continue investigating this :)

@tommyw  Did you find anything yet? I'm still searching but i cant find the problem..

@reense nope, afraid not. haven't spent a huge amount of time on it though. will hopefully be able to find a bit more time next week.

@reense I just realised that there's mean to be an umbraco2FA admin section, but when I assign it to the administrators group, it causes the back office to fall over.

So.... I'm really not sure where to go from here. Neither of the Fortress DB tables offer any settings for timeout. I think it must be something to do with the authenticate API call, and found this: https://github.com/Offroadcode/Umbraco-2FA/blob/master/Umbraco2FA/Umbraco/Fortress/Controllers/TwoFactorAuthController.cs#L70
but that's not included in the .csproj, so I guess it's old.
I'll try to get the whole solution, with the JS/grunt running locally, might provide some clues.

@tommyw  Hmm, that's what I found as well. However, I'm still clueless why this issue is occurring. There is nothing in the code that suggests it automatically logs out. I think it could also be some exception that is silently occurring, and then logging out because of that. Still investigating..

Hey folks, its been pretty flat out crazy busy here at Offroadcode Towers so sorry for the lack of response.
For a little history the 2FA stuff was originally part of a bigger project which had a collection of security goodies in it that we called Fortress hence all the references. We chose to release the 2FA stuff separately but to do that we had to rip out some of the other goodies but we did it in a bit of a hurry. As a result there are some left over artefacts in there which might prove to be red herrings, sorry.
Timeout wise I can't think of anything off the top of my head but that cookie timeout would certainly be worth bumping up to see if it did anything. I'll ask around in the office this week and see what we can come up with.
Thanks for your interest in the package though and your keenness to help us get to the bottom of these issues :)

Cheers Pete, appreciate it. Would be a great addition to U7, and hopefully will be rolled into U8!

se the 2FA stuff separately but to do that we had to rip out some of the other goodies but we did it in a bit of a hurry. As a result there are some left over artefacts in there which might prove to be red herrings, sorry.
Timeout wise I can't think of anything off the top of my head but that cookie timeout would certainly be worth bumping up to see if it did anything. I'll ask around in the office this week and see what we

Great, thank you! Looking forward to hearing what your colleagues said ;)

Any Solution for the above issue?

Having the same issue as stated above, being logged out of the backoffice after about a minute.
When can we expect this bug to be fixed?

Sorry folks, it's been put on my backburner for a little while. I'll see what I can do about it this week.

@benjaminhowarth1 have you had any time to fix this bug? I want to implement this package for a client but in the current state it's a no go for us.

Hello @benjaminhowarth1 - do you have an update on this issue? This is an issue that is stopping us from completing a project. Is there a commercial support contract that you offer for this package and if so we are interested in that. Please let me know if that is a viable option and that case, I can reach out to you directly.
Thank you.

Hi folks, I'm taking another look at this tonight. @naresh-msc commercial support for OSS components is always appreciated, do feel free to drop me a line about helping to financially support the project going forward :)

Benjamin - Thank you for the efforts to fix this issue. Please let me know if we can setup some type of support contract for this component and we can look into it.
Thank you.
From: Benjamin Howarth<EMAIL_ADDRESS>Sent: Tuesday, February 19, 2019 11:37 AM
To: Offroadcode/Umbraco-2FA<EMAIL_ADDRESS>Cc: Naresh Kumar Narendran<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Offroadcode/Umbraco-2FA] Automatically logged out after less then 2 minutes. (#16)
Hi folks, I'm taking another look at this tonight. @naresh-mschttps://github.com/naresh-msc commercial support for OSS components is always appreciated, do feel free to drop me a line about helping to financially support the project going forward :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Offroadcode/Umbraco-2FA/issues/16#issuecomment-465209221, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKKjLHfpkTbyfvbB1gE9BfaPo84BLAhFks5vPCgkgaJpZM4Yb6ia.

Hey all,
I found some nice standalone project that here - https://github.com/nul800sebastiaan/YubiKey2Factor
but with some bugs. so I fork it and remove all the unnecessary code (yubik key), you are welcome to give it a review.  [((https://github.com/ng-soft/YubiKey2Factor))]

Hi folks, I'm taking another look at this tonight. @naresh-msc commercial support for OSS components is always appreciated, do feel free to drop me a line about helping to financially support the project going forward :)

Do you have any update yet?

@ng-soft I looked at your repo. It would be much nicer to have just the dll's\code we would need for our own install's.

@kgiszewski, That true, but I tried to do it as a standalone solution that all you have to do is just download it without any installation. I guess that to do it as a plugin is a much better approach, but this it would take some time. In the meantime, all you have to do is copy the 2FactorAuthentication folder into your solution and it should work too without a lot of configurations.

Has any progress been made to rectify the user timeout issue? Or perhaps a recommended work around. Current the plugin is unusable. Thanks

See my the comments above

Thanks very much @ng-soft, I will try your forked repo https://github.com/ng-soft/umbraco-2fa-with-google-authenticator as a workaround. Is there any update on the progress of the issue for this plugin however?

I can confirm @ng-soft 's solution is working. In order to fix this package, remove the FortressOwinStartup.cs file and add the TwoFactorEventHandler.cs  code from @ng-soft to your ApplicationStartup.cs file.

I can confirm @ng-soft 's solution is working. In order to fix this package, remove the FortressOwinStartup.cs file and add the TwoFactorEventHandler.cs  code from @ng-soft to your ApplicationStartup.cs file.

@filipesousa20 After doing this I have to revert the owin:appStartup value back to UmbracoDefaultOwinStartup - correct? After doing this I no longer get prompted for my 2FA.

I can confirm @ng-soft 's solution is working. In order to fix this package, remove the FortressOwinStartup.cs file and add the TwoFactorEventHandler.cs  code from @ng-soft to your ApplicationStartup.cs file.

@filipesousa20 After doing this I have to revert the owin:appStartup value back to UmbracoDefaultOwinStartup - correct? After doing this I no longer get prompted for my 2FA.

I have a number of existing Umbraco7 sites that I need to add 2FA to.
They all have an existing complex custom applicationstartup config (overriding ApplicationStarting and ApplicationStarted).
I've tried to deal with the timeout issue as detailed above, but at the risk of sounding like a dummy, I am struggling to follow what needs to be copied from the forked repo and how it should be applied to this plugin.
Can anyone please advise what is the minimum changes required to make this package work and not timeout ?

Hello from the future!
Is there a working solution for this that is build as a Umbraco PlugIn package for V7 ? I'm also getting the 60sec logout issue.

It's been a long time so I can't easily tell what I did but I do have a working solution. However, taking a quick look it looks more like it is based on the repository here.

Having the same issue here with a brand new Umbraco 13 installation. Note: I have two Umbraco projects running locally, at the same time.


fix(main): fix EndOfBuffer highlight as well

Description
The EndOfBuffer highlight group can dominate the overlay, making it appear that the window.backdrop setting has no effect (see comment).
To fix this, we should set not only NormalFloat to ZenBg, but EndOfBuffer too.
Alternative workaround: set EndOfBuffer to something else.
Related Issue(s)

https://github.com/folke/zen-mode.nvim/issues/115

Screenshots
In the following, window.backdrop is set to 1.
Before this PR, with a scheme that has Normal with bg=#181818 and EndOfBuffer set to bg=0:

After:

Can I get a review before the stale bot reaps this?

ty


added support for null and boolean values

To specify a null value, use the keyword null. To specify the boolean true value, use the keywords true, yes, on. To specify the boolean false value, use the keywords false, no, off.
The keywords must be used without quotes.
If used with quotes, the actual string will be used instead.

Thanks, but this has already been discussed, and strings are fine. You just need to interpret them how you want when you use them.

Sorry, I could not see the discussion in the issues. Where can I find it? I'd be interested in understanding the reasons why this aspect was decided against. I do notice that getenv always returns a string or a literal value, (eg '' for null and 0 or 1 for booleans.
In any case, may I insist? To "interpret" the values is not very convenient, unfortunately. This is our use case:
We use symfony 2.8|3.1.
app config is stored in app/config/config.yml with entries such as:
# Swiftmailer Configuration
swiftmailer:
    transport:  "%mailer_transport%"
    host:       "%mailer_host%"
    username:   "%mailer_user%"
    password:   "%mailer_password%"
    encryption: %mailer_encryption%
    port:       "%mailer_port%"
    auth_mode: %mailer_auth_mode%

The parameters (eg %mailer_encryption%) are defined in our .env file as :
SYMFONY__MAILER_ENCRYPTION=null

Symfony automatically transforms evn vars prefixed with `SYMFONY__`` into the relevant parameter.
Unfortunately this does not allow for strings to be interpreted as null or boolean values. Note that using quotes or not makes no difference.
Now we could try and fix the symfony side of things, but it seems a lot easier to fix dotenv.

I could only find this MR: https://github.com/vlucas/phpdotenv/pull/177 which is not quite the same as mine.
Could you at least point me to the relevant discussion so that I can understand the issue?


Aidan git test4

Can someone please merge in my pull request?

@aidanvray I'll leave this for you to pull in to complete the series, since you're doing this some weeks late.


'utf-8' codec can't decode

Hello: I'm facing the following error while running infer.py on ubuntu 16.04, CUDA 10, Python 3.5, opencv 3.4.
Full error in : https://pastebin.com/ax47FAUU
File "/home/pavithra/Downloads/caffe2-pose-estimation/utils/utils.py", line 35, in initialize_gpu_from_weights_file
src_blobs = pickle.load(f)
File "/home/pavithra/.virtualenvs/cv/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 0: invalid start byte
Modifications:
I tried modifying the codec.py file where I changed fileread mode from 'r' to 'rb'. I also changed the errors='strict' to errors='ignore' . Please help me fix this issue. Thank you.

I was able to solve this error. I had to uninstall tensorflow. Then, manually remove all tensorflow files from site-packages and then re-install tensorflow.
The error was caused due to files from previous versions of tensorflow still remaining.
I hope this helps.

@pavithraezhil , this error should be caused by python 3. I have updated the utils/utils.py for python 3.5. The updated file is here: https://drive.google.com/file/d/1AxkKnZsK1cxX3BHrdjU6cE7DegKxP-fS/view?usp=sharing. You can download it and replace the original one. Thanks.

@pavithraezhil , this error should be caused by python 3. I have updated the utils/utils.py for python 3.5. The updated file is here: https://drive.google.com/file/d/1AxkKnZsK1cxX3BHrdjU6cE7DegKxP-fS/view?usp=sharing. You can download it and replace the original one. Thanks.


installation problem

i follow all steps
how to use this
$printJob = Printing::newPrintTask()
->printer($printerId)
->file('path_to_file.pdf')
->send();
$printJob->id();
in class how to access printing class

Class 'App\Http\Controllers\Printing' not found

use Rawilk\Printing\Printing
-_-


Add PolarClass implementation for uuid::Uuid

Adds implementation for foreign type uuid::Uuid.  This is behind a feature gate uuid.  Tests have been added to the /languages/rust/oso/tests/test_polar_rust.rs suite.  Tests require running cargo test with --features uuid option. (e.g. $ cargo test --features uuid)
Note: Cargo.toml in /languages/rust/oso/ specifies version 0.6.5 of uuid.  The latest version is 0.8.1 at the time of writing, but the version currently used in diesel orm is 0.6.5.  Because of the popularity of diesel, and the likelihood of persisting UUID's to the database in a web application context, I used 0.6.5 for compatibility with diesel.
PR checklist:

[ ] Added changelog entry.

I have read the CLA Document and I hereby sign the CLA

recheck

recheck

Thanks again @johnhalbert ! Credited you in the changelog 🙂


Move some ui tests from auto_enums

This crate has historically been part of auto_enums repo, and some testing is still done by auto_enums repo. This increases the maintenance burden on auto_enums repo, so it is preferable to move it to this repo.

bors r+


fix: user tools to the top & toast on successful tool addition

Addresses #481.

creates toast when adding tool is successful
user created tools is at top

TIL: This is called a "toast"
nit: might be nice for the checkmark to be green to intensify the "pat on the back" effect.

Will get that checkmark green!


Add v0.17.0

This adds a release for version 0.17.0.

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

Went ahead and merged this as it has been sitting for a week and have gotten no comments.


Add support for EventListener Object

Support for native javascript eventListener.handleEvent()
See issue #10773
See: MDN
Can someone help me with the typedef ? I have tried several, but I am stuck.

https://microsoft.github.io/PowerBI-JavaScript/interfaces/_node_modules_typedoc_node_modules_typescript_lib_lib_dom_d_.eventlistenerobject.html

I added two commits to fix the types and the code.

ouch.... duplicated for loop.....
I am sooooooo sorry!!! 😖 😳


Adding SQL to 2.7 manifest

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.

Codecov Report

Merging #3278 (4483c11) into main (95bb1e7) will decrease coverage by 0.29%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #3278      +/-   ##
==========================================
- Coverage   91.74%   91.46%   -0.29%
==========================================
  Files         172      172
  Lines        4991     4991
==========================================
- Hits         4579     4565      -14
- Misses        412      426      +14

Impacted Files
Coverage Δ

src/system/temporary_directory.py
64.44% <0.00%> (-28.89%)
:arrow_down:

src/system/os.py
94.73% <0.00%> (-5.27%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.