Fix creating new milestoned query from dataspace

Summary
closes #1315

How did you test this change?

[ ] Test(s) added
[x] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

@gayathrir11  Looks good to me :)


fix:(localization): add missing props

Please describe the changes this PR makes and why it should be merged:
Adds missing props name_localized and description_localized which can be returned on specific endpoints.
Also fixed the LocalizationMap type to allow null values for localization entries.
If applicable, please reference Discord API Docs PRs or commits that influenced this PR:

commitlint moment


Fix StartChat screen transition stuttering

Details

Fixed Issues

$
PROPOSAL:
Tests

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[ ] I linked the correct issue in the ### Fixed Issues section above
[ ] I wrote clear testing steps that cover the changes made in this PR

[ ] I added steps for local testing in the Tests section
[ ] I added steps for the expected offline behavior in the Offline steps section
[ ] I added steps for Staging and/or Production testing in the QA steps section
[ ] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[ ] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[ ] I included screenshots or videos for tests on all platforms
[ ] I ran the tests on all platforms & verified they passed on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[ ] I followed proper code patterns (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[ ] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I followed the guidelines as stated in the Review Guidelines
[ ] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] I verified that if a function's arguments changed that all usages have also been updated correctly
[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

To do:

[ ] what is the reason behind useAutoFocusInput current implementation? It consist of useEffect that triggers when screen transition ends, but transition end is dictated by constant ANIMATED_TRANSITION regardless of useAutoFocusInput usage
[ ] runAfterInteractions does not work on web - is this the reason behind using timeout? If yes, this should be divided into .website and .native implementations
[ ] useFocusEffect is used to fire the timeout - why not just skip the timeout and focus the input whenever screen is being focused? If there is a race condition (which is probably why InteractionManager is used) then this should be stated somewhere
[ ] Is focusing certain input every time sensible? If user already visited screen (e.g. filled some inputs), then we should not bring back focus to the first input - it should stay where it was. Current behaviour should be preferred only on first visit or when form is still in clean state.

Is focusing certain input every time sensible? If user already visited screen (e.g. filled some inputs), then we should not bring back focus to the first input - it should stay where it was. Current behaviour should be preferred only on first visit or when form is still in clean state.

Here is a recording that shows undesired behaviour:
https://github.com/Expensify/App/assets/62747088/955223b5-09bd-41a6-b5a4-5de338adf7bf

Recording of the current state:

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/58412969/e17a6458-5dc2-4652-8692-aa35127c5b3d

Android: mWeb Chrome

iOS: Native
https://github.com/Expensify/App/assets/58412969/b0a30254-3a8b-45b3-8332-1595e6d3d52c

iOS: mWeb Safari

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/58412969/6280557d-da33-4434-83bf-babebe59c958

MacOS: Desktop
https://github.com/Expensify/App/assets/58412969/449ea2d3-64f6-4b46-8000-7e5cceb45421

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/marcaaron in version: 1.4.36-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


List of Icons Available

Is there a list of icons available?

Yes (sort of). I've just added this to the README:

For the custom tooltip values, the icon name is the name of the Font Awesome icon you want to show. You can search for icons on the Font Awesome website. Note that not all Font Awesome icons are available (FoundryVTT itself is in control over which icons are available, not this module - this module is just using the icons that are shipped with FoundryVTT).

I'll update the module to include some help text somewhere as well for this, for those who don't check the GitHub page.

And I read the ReadMe. haha! Completely glossed over that part. Thank you for clarifying.

You didn't gloss over it - that part of the readme didn't exist until after you opened this issue. I added it because you asked the question.


affectedRows and changedRows are undefined in SELECT query result

I'm using mysql v2.17.1 to access MySQL v5 DB. Here are the screenshots from my project:

In my code I log the results from a simple SELECT query: select * from users; but both affectedRows and changedRows are undefined

Please help. Thank you in advance.

The mysql protocol does not return those values for SELECT statements.


Package script not continuing after Windows Updates in Server 2016 Core

I'm using Install-WindowsUpdate in my boxstarter package, used during packer builds.  The packer build completes successfully if I'm installing the Desktop Experience, but if I'm installing Core, the build never finishes.  It doesn't seem like the windows update step inside Core is finishing correctly, and letting the system continue on to the next step in my "package.ps1" script.  If i comment out Install-WindowsUpdate, the Core build works fine, and it works fine if I let it install updates in the Desktop versions (both 2016 and 2012R2).
There is just something flakey with Core.
Any ideas?
here's a portion of my package.ps1
Install-WindowsUpdate -AcceptEula
if (Test-PendingReboot) { Invoke-Reboot }
Write-BoxstarterMessage 'Setting DNS servers...'
. a:\Set-DnsServers.ps1

I never see the "setting dns servers" and none of the other commands further down in the package.ps1 script

Unfortunately Boxstarter does not work propperly with server core because after a reboot and login, it strts itself back up via a desktop menu item in the startup group. The core SKUs do not have these groups.
You might try adapting one of my 2016 templates in https://github.com/mwrock/packer-templates which use chef instead of boxstarter and don't suffer from this limitation.


Add doc explaining the INSTALLED_APPS order importance

I couldn't find doc saying that this app needed to be included in the INSTALLED_APPS before the app that contains the actual management test command or else this app isn't picked up which is important to note.
Nice simple app that relieves a lot of headaches!  Thanks for releasing!

Since the main test command is defined by django's core you shouldn't have had any trouble with that.
Are you using another 3rd party app that also overrides the test command?

Not using any other 3rd party command that override test.  All I know is when I add it to the installed apps after the django apps it gives me the following error:
$ python manage.py test --nomigrations
usage: manage.py test [-h] [--version] [-v {0,1,2,3}] [--settings SETTINGS]
                      [--pythonpath PYTHONPATH] [--traceback] [--no-color]
                      [--noinput] [--failfast] [--testrunner TESTRUNNER]
                      [--liveserver LIVESERVER] [-t TOP_LEVEL] [-p PATTERN]
                      [-k] [-r] [-d]
                      [test_label [test_label ...]]
manage.py test: error: unrecognized arguments: --nomigrations

If I make it the first app installed apps, I don't receive the error.

It does not work with django-nose and DjangoNoseTestRunner.

Plz, open a new issue for this.

:+1: on the INSTALLED_APPS ordering

This should be fixed in #6

Fixed. Thx all!


Add a class for logging of kubernetes watch events

This will help setup the logging properties such that events can
logged in a dedicated log file.

Pull Request Test Coverage Report for Build 6358

8 of 11 (72.73%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0003%) to 45.106%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-common/src/main/java/azkaban/executor/container/watch/WatchEventLogger.java
7
10
70.0%

Totals

Change from base Build 6357:
0.0003%

Covered Lines:
17651

Relevant Lines:
39132

💛  - Coveralls


Add Oxygen Sensor to Controller Code

Basic requirements:

Analog input similar to pressure sensors, but on pin PC3
Should have a linear y= m*x + b conversion between counts and an oxygen concentration [0 - 1.0]
Output should be callable in the same way as the other sensors.

Someone could help here by finding out which existing code most resembles what is needed.

Oxygen sensor calibration narrative, assuming amplifier gain g_amp and sensor gain g_o2sensor:

Nominal values:

g_amp: 50 V/V
g_o2sensor: 0.06 V/fio2 (where fio2 is 0.0 to 1.0)

Ventilator turns on, starts self-test

Run blower for 3 seconds with both inhale and exhale valve fully open (and O2 PSOL fully closed) to flush with ambient air.

Wait at least 10s.  Can run other self-test procedures, but only using ambient air.

Record the ambient air sensor value in sensors_zero_vals_[FIO2]

Read the ambient barometric pressure sensor and record the valve (this is not yet supported in hardware, so for now assume 101.3kpa)

Oxygen concentration output expressed as a 0.0-1.0 value is:

std::clamp( (fio2.voltage() - sensors_zero_vals_[FIO2]) * (101.3/p_ambient_kpa/g_amp/g_o2sensor) + 0.21f)

I have started a sample implementation here if it helps, but note that I am not a software engineer, so this definitely needs to be screened for compliance to coding standards and correct implementation.  However a diff between the current master and this branch can help with finding all the places were modifications are needed to add the extra analog channel: https://github.com/RespiraWorks/Ventilator/tree/inceptionev/add_fio2_sensor

Sample implementation in branch https://github.com/RespiraWorks/Ventilator/tree/inceptionev/add_fio2_sensor now includes the scaling

Working on this right now, I have completed the basic framework and adding some unit tests.
I wonder whether we are using the correct correction factor (101.3 / ambient pressure) to go from partial pressure to fraction of volume...
I am not well versed in how that sensor works, but it seems to me that patient pressure should come into play at some point, as the oxygen sensor is seeing patient pressure.
Any insights on this?

Thanks for picking this up.
That's a good point.  The oxygen sensor is an electrochemical cell, so it actually measuring partial pressure of oxygen, not concentration.  It has a sensitivity of 0.00061V/kpaH20_partial_pressure.
While it is true that the sensor is seeing patient pressure, the ambient pressure has a larger effect.  At 10000ft / 305m, there is a drop of 322cmH2O vs sea level, while the max patient pressure is 35cmH2O.  We could take into account patient pressure as well, but we definitely need to make a correction for ambient pressure.

The sensor has a response time on the order of 10 seconds, so I'm not sure how a quickly-changing patient pressure correction would play out.

OK, no problem there.
Regarding the changes in patient pressure, we could approximate the response time with a similar 10 seconds low-pass filter, but without the actual dynamic of the sensor (especially in terms of phase shift), I am not sure of the actual benefits that this would bring. For now, ambient pressure will suffice.


Debian 8.4 Jessie (multi-screen) xflux blinking

I love xflux.
On Windows f.lux works excellently but on my machine (Debian 8 64bit, 2 screens: laptop + external) every time I activate xflux My displays (both) keep blinking (like there was some interference) and it's very difficult to use this way.
I am looking forward to hearing from you.
Thank you in advance and keep up the good work!

Not sure how to debug this. E.g. I'm using xflux on multiple monitors in Ubuntu 16.04 (and 15.10 in the past) with no problems.

@dragGH102: could you try running xflux manually on the command line, i.e. not via fluxgui, and report back?

@ntc2 Interesting, I reinstalled xflux-gui from scratch and both gui (I run it directly with python) and CLI seems working on both screens.
I'll close the issue for now and reopen it if it occurs again.

Glad to hear you got it working! If you have this issue again, and it also happens when you run xflux directly on the command line, then I think the bug is in xflux itself, and not in fluxgui. In that case, please file a bug upstream with the xflux maintainers. I can't find a bug tracker at justgetflux.com, but perhaps you would file the bug here: https://forum.justgetflux.com/category/7/linux.


Automatically select newly added seed

In the UI, when you call graph.addSeed() this seed should automatically be selected and all observers watching the selected seeds should be notified of the update.

Merged into develop.


Migrate 4.0/api

Migrate to 4.0.0
API updates by doc changes

AreaSeriesOptions: added invertFilledArea, crosshairMarkerBorderWidth

BaselineSeriesOptions: added lineType, crosshairMarkerBorderWidth

BaselineSeriesOptions: scaleMargins removed and overlay property removed. It's affect AreaSeriesOptions, BaselineSeriesOptions, CandlestickSeriesOptions, HistogramSeriesOptions, LineSeriesOptions,

HandleScaleOptions: axisFloatClickReset changed type to AxisPressedMouseMoveOptions

LayoutOptions backgroundColor changed to background

PriceScaleOptions: drawTicks renamed to ticksVisible

TimeScaleOptions: aded ticksVisible

LineType: added curved

added AreaData and BaselineData

serial options moved to pricescale options. details

Implemented markers and
databyindex methods for series api

MouseEventParams:   added logical,  added hoveredSeries, added sourceEvent,  seriesPrices renamed to seriesData

Refs

From v3 to v4

@JoeyChief Hi! Yes, We are in the process of testing/reviewing. We are expecting to merge this PR this month


Add all in one package

The package containing both cli and war file are included.
The following is the image of directory structure.
/bin/redpen
/bin/redpen.war
/lib/jar-files.

the war file contains all libraries.
Is /lib/* necessary?

Thank you for the comment @yusuke!

the war file contains all libraries.
Right maybe adding redpen.war to /bin/ directory in the redpen pacakge.

Is /lib/* necessary?
Currently /lib/ is needed to run redpen cli. maybe the redpen-cli jar should contains all the jar files as redpen.war.

Fixed with #450


errorCode=410012 occurred and 6 million rows of BigQuery data could not be published by export_load method

Problem Description
The following error occurred when executing BigQueryExtractor's export_load.
Specified table does not exist: updated_rows. (errorCode=410012)']
The source table had about 6 million rows, and it seemed that part of the split process at update_datasource_from_hyper_file was failed.
Checking the destination tableau online source_data, the 1.9 million rows of data was created and not all.
However, when I set sample_rows=10000000 (10M) for load_sample, it worked fine.(but, it took about an hour for local processing...)
Is there something wrong with the settings in export_load?
Or would it be better to use load_sample for large table (if there is no performance difference with export_load)
I also tried with BigQuery's Public dataset below, but got the same error.
bigquery-public-data.google_trends.top_rising_terms
*Due to a data type error, the following part of bigquery_extractor.py has been temporarily corrected.
        type_lookup = {             "BOOL": SqlType.bool(),             "BYTES": SqlType.bytes(),             "DATE": SqlType.date(),             "DATETIME": SqlType.timestamp(),             "INT64": SqlType.big_int(),             "INTEGER": SqlType.text(),             "NUMERIC": SqlType.numeric(18, 9),             "FLOAT64": SqlType.double(),             "FLOAT": SqlType.text(),             "GEOGRAPHY": SqlType.text(),             "STRING": SqlType.text(),             "TIME": SqlType.time(),             "TIMESTAMP": SqlType.timestamp_tz(),         }
version:

tableauhyperapi:0.0.14401
tableauserverclient:0.23

main.py
config = yaml.safe_load(open("config.yml"))
tableau_env = config.get("tableau_env")
db_env = config.get("bigquery")
extractor = BigQueryExtractor(
            source_database_config=db_env,
            tableau_hostname=tableau_env.get("server_address"),
            tableau_project=tableau_env.get("project"),
            tableau_site_id=tableau_env.get("site_id"),
            tableau_token_name="xxxx",
            tableau_token_secret="xxxx",
        )

extractor.export_load(
            source_table="bigquery-public-data.google_trends.top_rising_terms",
            tab_ds_name="export_load_test"
        )

Error
==================
Traceback (most recent call last):
File "/Users/yuji.yamamoto/test/load_tableau_hyper_files_2/hyper-api-samples/Community-Supported/clouddb-extractor/main.py", line 26, in
extractor.export_load(
File "/Users/yuji.yamamoto/test/load_tableau_hyper_files_2/hyper-api-samples/Community-Supported/clouddb-extractor/base_extractor.py", line 165, in execution_timer
result = func(*args, **kw)
File "/Users/yuji.yamamoto/test/load_tableau_hyper_files_2/hyper-api-samples/Community-Supported/clouddb-extractor/base_extractor.py", line 690, in export_load
self.update_datasource_from_hyper_file(
File "/Users/yuji.yamamoto/test/load_tableau_hyper_files_2/hyper-api-samples/Community-Supported/clouddb-extractor/base_extractor.py", line 584, in update_datasource_from_hyper_file
self.tableau_server.jobs.wait_for_job(async_job)
File "/Users/yuji.yamamoto/.anyenv/envs/pyenv/versions/3.9.6/lib/python3.9/site-packages/tableauserverclient/server/endpoint/jobs_endpoint.py", line 72, in wait_for_job
raise JobFailedException(job)
tableauserverclient.server.endpoint.exceptions.JobFailedException: Job 23a09876-ec23-4d88-b1fa-1314f23f2aef failed with notes ['com.tableausoftware.domain.server.exception.TableauServerException: There was a problem retrieving table information for the source table. Specified table does not exist: updated_rows. (errorCode=410012)']

I modified export_load as attached and it worked fine, so I am closing this ticket for now.
The cause was not clear to me, but I made the process similar to sample_load.
`
def export_load(
    self,
    tab_ds_name: str,
    source_table: Optional[str] = None,
    sql_query: Optional[str] = None,
    publish_mode: TSC.Server.PublishMode = TSC.Server.PublishMode.CreateNew,
) -> None:
    """
    Bulk export the contents of source_table and load to Tableau Server.

    tab_ds_name (string): Target datasource name
    source_table (string): Source table identifier
    sql_query (string): SQL to pass to the source database
    publish_mode: One of TSC.Server.[Overwrite|CreateNew] (default=CreateNew)

    NOTES:
    - Specify either sql_query OR source_table, error if both specified
    """
    sql_query = "SELECT * FROM {}".format(self.quoted_sql_identifier(source_table))
    first_chunk = True
    for path_to_database in self.query_to_hyper_files(sql_query=sql_query):
        if first_chunk:
            self.publish_hyper_file(path_to_database, tab_ds_name, publish_mode)
            first_chunk = False
        else:
            self.update_datasource_from_hyper_file(
                path_to_database=path_to_database,
                tab_ds_name=tab_ds_name,
                action="INSERT",
            )
        os.remove(path_to_database)

`


Set VERSION to 2.0.0+dev

I think it should be 1.0.0+dev - it would be cool to have the commit SHA into it

it would be cool to have the commit SHA into it

that requires some adaptions in our overall packaging automation (meaning other repos as well) but it's a good idea. i'll create a card for that

Marking as WIP due to flavios comment, will update to 1.0.0+dev


WebAssembly.Memory Error

I am using the latest version of wasm-vips
but in production I am getting the following error:
requested a shared WebAssembly.Memory but the returned buffer is not a SharedArrayBuffer, indicating that while the browser has SharedArrayBuffer it does not have WebAssembly threads support - you may need to set a flag

I am setting the headers correctly:

I also get the vips.js correctly. Also the console doesn't exactly print anything. I got it by breaking on all exceptions.
I am on latest version on mac, using it in native webview.

I don't think this is wasm-vips issue. will close this one.


llvmPackages_{9,12,13,14,15,16,17,18,git}.clang: fix libLTO.dylib path

Description of changes
Clang assumes that libLTO.dylib is located at ../lib in the same prefix as clang, but that’s not true in nixpkgs. libLTO.dylib is actually located at libllvm^lib/lib.libLTO.dylib.
This is the first piece to fixing LTO on Darwin. The other is updating ld64, which I will be doing in a separate PR later this week. This PR does not depend on that PR because there is no harm passing the correct path to ld64. It does not perform LTO by default, and trying to use -flto even with the correct path remains broken.
Testing was done using my WIP PR for ld64 with clang 16. See https://github.com/NixOS/nixpkgs/issues/19098#issuecomment-2041752524 for output. It can also be validated by setting NIX_DEBUG=1 when running clang, then confirming that the path passed to -lto_library actually exists in the store.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This is an interesting change, I'll give this a look over when I have the time. Right now, my priority is on making all LLVM subpackages common and I am hoping to get that done asap so this PR will probably take a bit for me to look over. I also don't want to have to rebase that PR heh.

Conflict :(

Conflict :(

Rebased and dropped clang 9 since it was removed.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/darwin-updates-news/42249/10

@RossComputerGuy I saw that https://github.com/NixOS/nixpkgs/pull/303948 was merged. I’ve rebased this on y

Closing because of the mass ping. I’ll reopen targeting staging with the consolidated clang.


BUG:About Us Page doesnt Match with the Theme

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Different color of the about us page than others

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@kashnx solve this issue with this issue #1221

Done


Improved support for dynamic repositories

New PR for #245 which was buggy

There are current issues with Dynamic Repositories, see #101 and #336 - and I was wondering if this PR would perhaps also aid in fixing those.
If so an ideas when this will get merged?

It needs to be rebased and the test needs to be made to work offline (i.e create a fake repo then clone it). if someone gets to that before me, great. Otherwise I hope to do it in the next few days


Missing EU Servers

The new EU Servers are missing in the Character Import.
Omega
Louisoix

Thanks, I'll add those. Do you know if XIVDB supports them yet?

Yes they're available at XIVDB


Setup MUI colour theme

Setup a new custom theme with a custom pallet set up inside it.

Colour scheme selected: https://coolors.co/3d5a80-98c1d9-e0fbfc-f1856a-293241

Colour themes, for both light and dark mode set.


console.log() always outputs a logging prefix on Windows

Consider the following script:
console.log('hello world');
require('app').quit();

Running this on OS X behaves normally. The application exits successfully with the following output:
hello world

On Windows I get the following output:
[2648:0602/172546:INFO:CONSOLE(0)] hello world

This is unexpected and I've found no way to disable it.
In essence, I'm trying to execute Electron's executable as a replacement for Node. Are there any obvious issues that I will encounter, besides this one?

On a related note, why not provide a way to simply run node without any overhead? Could be done with a command line argument to atom.exe or simply another .exe which binds to the right things.

Are you trying to make a command line application? Why not just drop Electron, install node.js and call it from command line?

Not at all. My app is indeed Electron based.
In it I spawn processes which themselves spawn other processes and read their output. I own these second-level processes, I write them in whatever tool I have at my disposal. But I do not own the ones I spawn directly: I can only tell them which sub-processes to spawn.
I've been telling them "Hey, just spawn atom.exe with these arguments", which works great on OS X. Not so much on Windows do the the output prefixing.

@joaomoreno How are you running these processes? Are you using child_process.fork?

I use cp.spawn since what I'm spawning is not Javascript based; it's actual executables. They themselves need to spawn something that returns a result via stdout. I would like to use Javascript for that.

On Windows Node.js is a console program while Electron is a GUI program, and by default you can not see the console output of a GUI program. In Electron console.log is redirected to Chromium's logging system to make sure things can be printed, if you don't want this behavior you can override it back:
console.log = require('console').log

@zcbenz That doesn't seem to help.
console.log('hello');
require('console').log('world');
require('app').quit();

Still ends up in:
[1984:0604/082931:INFO:CONSOLE(0)] hello
[1984:0604/082931:INFO:CONSOLE(0)] world

Hmm, you can try process.stdout.write which Node's console.log is implemented with, but it might not work in a GUI program.

@zcbenz It does work, but unfortunately ends up with the same prefix. All of them seem to be patched.

Sorry I forgot I had patched all of them, currently you have to create the stream by copying Node's code:
https://github.com/nodejs/io.js/blob/master/src/node.js#L616-L629
But unless you run Electron with stdout attached, like using child_process.spawn, writing to stdout would throw exception.

This was fixed in v0.33.7


Update python test action

use action logic from ALActions/pythontests
use scikit-learn instead of sklearn: https://github.com/scikit-learn/sklearn-pypi-package

Might do a quick install test (that Kiln wouldn't cover) since I am changing setup.py.

Can't get Kiln to work, but installs fine, going to merge


Add V1-V2 token swap functionality

What does this PR do and why?
This PR adds the V1-V2 token swap functionality
⚠ This feature is behind the v1TokenSwap feature flag, disabled by default.
Specifically:

Add a "Your V1 tokens" to the Tokens section of the V2 project page
Add a modal to facilitate the swap.

Closes https://github.com/jbx-protocol/juice-interface/issues/1335
(related to https://github.com/jbx-protocol/juice-interface/issues/1056)
Screenshots or screen recordings
Tokens section

default
tooltip

Swap modal

Step 1. Give permission to swap
Step 2. Swap form

How to test
Token swap
http://localhost:3000/#/v2/p/4284

Enable the feature flag
localStorage.setItem('v1TokenSwap_rinkeby', 'true')

Pay this V1 project to receive v1 tokens: http://localhost:3000/#/p/testballots

Navigate to http://localhost:3000/#/v2/p/4284. You should see the new "V1 token balance" in the Tokens section.

Click Swap for V2 tokens

Click Give permission

Swap some tokens.

Verify that the new V1 and V2 token balances are correct.

End to end (optional)

Enable the feature flag
localStorage.setItem('v1TokenSwap_rinkeby', 'true')

Create a V1 and a V2 project.

On the V2 project, configure it for V1 token migration
i ) Go to Tools > Owner tools > V1 token migration
ii ) Select Set up token migration
iii ) Complete the modal.

Pay the V1 project to receive V1 tokens.

Visit the V2 project. You should see the new "V1 token balance" in the Tokens section.

Click Swap for V2 tokens

Click Give permission

Swap some tokens.

Verify that the new V1 and V2 token balances are correct.

Acceptance checklist

[x] I have evaluated the Approval Guidelines for this PR.
[x] I have tested this PR in all supported browsers.
[x] I have tested this PR in dark mode and light mode (if applicable).

@johnnyd-eth 👋 , could you please review this when you get a chance? You'll have the most context for this 🙏

Code all looks great. Although I'm getting an error on step 5:
https://user-images.githubusercontent.com/96150256/179127797-97df7225-039b-4a3a-b67b-f81fbb527a74.mp4

span missing


Error Ionic 3

Hi, i try with ionic 3
follow the guide but not work for me
look the error:
Runtime Error
Uncaught (in promise): Error: Template parse errors: Can't bind to 'textMask' since it isn't a known property of 'ion-input'. 1. If 'ion-input' is an Angular component and it has 'textMask' input, then verify that it is part of this module. 2. If 'ion-input' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. 3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. (" Telefone <ion-input type="text" value="" [ERROR ->][textMask]="{mask: phone}" formControlName="phone">   "): ng:///ProfilePageModule/ProfilePage.html@37:40 Can't bind to 'textMask' since it isn't a known property of 'ion-input'. 1. If 'ion-input' is an Angular component and it has 'textMask' input, then verify that it is part of this module. 2. If 'ion-input' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. 3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("  Celular <ion-input type="text" value="" [ERROR ->][textMask]="{mask: cellphone}" formControlName="cellphone">  <ion-"): ng:///ProfilePageModule/ProfilePage.html@41:40 Can't bind to 'textMask' since it isn't a known property of 'ion-input'. 1. If 'ion-input' is an Angular component and it has 'textMask' input, then verify that it is part of this module. 2. If 'ion-input' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. 3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("  CEP <ion-input type="text" value="" [ERROR ->][textMask]="{mask: zipcode}" formControlName="zipcode">  <ion-item"): ng:///ProfilePageModule/ProfilePage.html@45:40 Error: Template parse errors: Can't bind to 'textMask' since it isn't a known property of 'ion-input'. 1. If 'ion-input' is an Angular component and it has 'textMask' input, then verify that it is part of this module. 2. If 'ion-input' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. 3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. (" Telefone <ion-input type="text" value="" [ERROR ->][textMask]="{mask: phone}" formControlName="phone">   "): ng:///ProfilePageModule/ProfilePage.html@37:40 Can't bind to 'textMask' since it isn't a known property of 'ion-input'. 1. If 'ion-input' is an Angular component and it has 'textMask' input, then verify that it is part of this module. 2. If 'ion-input' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. 3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("  Celular <ion-input type="text" value="" [ERROR ->][textMask]="{mask: cellphone}" formControlName="cellphone">  <ion-"): ng:///ProfilePageModule/ProfilePage.html@41:40 Can't bind to 'textMask' since it isn't a known property of 'ion-input'. 1. If 'ion-input' is an Angular component and it has 'textMask' input, then verify that it is part of this module. 2. If 'ion-input' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. 3. To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("  CEP <ion-input type="text" value="" [ERROR ->][textMask]="{mask: zipcode}" formControlName="zipcode">  <ion-item"): ng:///ProfilePageModule/ProfilePage.html@45:40 at syntaxError (http://localhost:8100/build/main.js:83601:34) at TemplateParser.parse (http://localhost:8100/build/main.js:94713:19) at JitCompiler._compileTemplate (http://localhost:8100/build/main.js:108758:39) at http://localhost:8100/build/main.js:108678:62 at Set.forEach (native) at JitCompiler._compileComponents (http://localhost:8100/build/main.js:108678:19) at http://localhost:8100/build/main.js:108565:19 at Object.then (http://localhost:8100/build/main.js:83591:148) at JitCompiler._compileModuleAndComponents (http://localhost:8100/build/main.js:108564:26) at JitCompiler.compileModuleAsync (http://localhost:8100/build/main.js:108493:37)

public zipcode = [/\d/, /\d/, '.', /\d/, /\d/, /\d/, '-', /\d/, /\d/, /\d/];
public phone = ['(',/\d/, /\d/,')', /\d/, /\d/, /\d/, /\d/, '-', /\d/, /\d/, /\d/, /\d/];
public cellphone = ['(',/\d/, /\d/,')', /\d/, /\d/, /\d/, /\d/, /\d/, '-', /\d/, /\d/, /\d/, /\d/];

angular2 text mask version: 0.8.2 and IONIC version: 3.4.0

That looks like you forgot to import the textMask module into your module.

@PerfectPixel thanks a lot

@fredroo : Could you please share the code how you were able to fix you issue.

I am trying to use textMask on  in ionic 3, but it's not working, not showing any error in console. I have added the TextMaskModule in the import section of app.module.ts.
It works fine, if i use  tag instead of .
my ionic configuratio is below:
cli packages: (/usr/local/lib/node_modules)
@ionic/cli-utils  : 1.14.0
ionic (Ionic CLI) : 3.14.0

global packages:
cordova (Cordova CLI) : 6.5.0

local packages:
@ionic/app-scripts : 3.0.0
Cordova Platforms  : ios 4.3.1
Ionic Framework    : ionic-angular 3.7.1

System:
ios-deploy : 1.9.2
ios-sim    : 5.0.13
Node       : v7.8.0
npm        : 4.2.0
OS         : macOS Sierra
Xcode      : Xcode 9.0.1 Build version 9A1004

Misc:
backend : pro

@yogeshbansal could u figure it out? having same issue here

Same issue here

in app (IONIC) folder inside of \src\app\app.module.ts
add this line in imports
import {TextMaskModule} from 'angular2-text-mask';
and of course before in your folder project add
npm i angular2-text-mask --save

don't fix for me...

The error persists.

Open file: app.module.ts
inside @NgModule{[]} and insde imports: add new line:
TextMaskModule

It doesn't work. My app uses module for every page (lazy loading). When I move the import to page module it works!

@victorwpbastos  for me works when I use in both


Run secrets tests only when secrets are available

Currently E2E tests on PRs are failing because... well, okay, lots of reasons right now, but a fundamental one is that PRs don't have access to the secret needed to run the image pull secrets test, and there's no way we know of to grant that access to 'approved' PRs.
This PR therefore separates the build.yml workflow that does public E2E tests and can run on every PR and a new ci.yml workflow that also runs tests that use secrets, and runs only after a PR merges to the main branch.
Ironically, I can't see a way to test the on-merge-to-master workflow without, er, merging it to master.
REVIEWERS: It's a bit awful duplicating the bodies of the workflows, but I couldn't see a way to conditionally set environment variables depending on the trigger, nor to pull out the bulk into a shared workflow with configurable knobs.  Let me know if you know ways of doing one of these!

Merging on approval alone because the test failures are ongoing and unrelated.  Will review duplication once we have this in main and have confirmed it works.


flake8 returning oddly encoded data

Hi, i installed this plugin and it doesn't work .

As you can see, 0 issues found, but...

Can you open Atom's Developer Tools, place a breakpoint here and report back with what result contains?

@Arcanemagus when i'm trying to place a breakpoint it jumps to another line

also in "Watch" bar it seems unavailable

oh, i did it

but there are encoding troubles it seems

couldn't decode it, sorry(

Wow, that's a new one 😮.
What shell are you using in the screenshot above where you are running flake8? Does it work from the "Command Prompt" shell?

Standard Windows 10 shell

@Arcanemagus
Standard Windows 10 shell
Yeas, it works

I've updated it few mins ago

but still having the same output

What language is Windows set to?

Russian

Can I somehow set the encoding for this string to utf-8 to make it readable?

Hmm, I'm betting that that is the "flake8 can't be found" message, can you try putting the output of where.exe flake8 in the Executable Path setting?

Yeah, now it works!)
Thanks again!

Awesome, glad that was it!


Frontend: create jsx page to list user's existing trips + button to create a new trip

Fetches user trips with GraphQL query GET_USER_TRIPS.
Displays loading or error messages if necessary.
Renders trips with destination name and attractions.
Shows a "No trips found" message if no trips exist.
Includes a button to create a new trip.

PR : https://github.com/HashemE1999/locus/pull/99

rough idea of how it should render:

My Trips

[ Trip Card 1 ]

----------------

Paris

- Eiffel Tower

- Louvre Mu...

[ Trip Card 4 ]
[ Trip Card 5 ]
[ Trip Card 6 ]

London
Rome
Barcelona

- Big Ben
- Colosseum
- La Sagrada

- Buckingham
- Vatican City
- Park Guell

                [Create New Trip Button]
                (Floating Bottom-Right Corner)


update scriptApproval.xml from Jenkins

Just a 1-to-1 copy from the server.
Should contain the approval for the Groovy script from ros-infrastructure/ros_buildfarm#541.

@nuclearsandwich friendly ping


Run a rollback instead of a reset when refreshing migrations

This is the same change as https://github.com/nWidart/modules/pull/4 that was merged in to the master branch instead of the feature/5.1 branch

Thanks! :+1: Didn't see it was on master on #4  :smile:

That was my bad. I had to use php artisan module:migrate-refresh again yesterday and I noticed it was still doing it the wrong way around while I was sure that my PR for it was already merged ;)


docs: skipNuxtState paramater added to lazy option

Docs in regard to pending feature #1149

Thanks. Will re-use in another PR with some changes.

Continuation in #1153


add kubectl checks to limits:set tests

As per https://github.com/deis/workflow-e2e/blob/003e0e6b12398707174caad8cdb556e8227cce3f/tests/limits_test.go#L10, we need to add checks to kubernetes to validate that the correct limits have been applied to the deployed pods.

The tags_test.go now uses kubectl successfully--the only hitch was resetting $HOME to the original user so that the proper configuration is found. The kubectl code there provides an example that might be useful here.

This issue was moved to teamhephy/workflow-e2e#15


Repository: Fix-up 74b6a60e

The intention of the mentioned commit obviously was to compare the
type of both instances.
Signed-off-by: Frank Viernau<EMAIL_ADDRESS>

This change is

Nit: The commit message title should not contain the fixed-up commit but a summary of the semantics of the fix, like "Repository: Fix matching of VcsInfo" and the commit message body should contain a reference to the fixed-up commit. Approving anyways to get the fix in quickly.

Merged even if there was one test failing on appveyoer which was unrelated to the change.


wrong version IRI in Mondo

Note - the Ontology version IRI in Mondo is wrong:

@matentzn can this be closed?

Yes, done:
        <owl:versionIRI rdf:resource="http://purl.obolibrary.org/obo/mondo/releases/2021-01-29/mondo-base.owl"/>

        <owl:versionIRI rdf:resource="http://purl.obolibrary.org/obo/mondo/releases/2020-12-18/mondo.owl"/>


HTTP::pool response returned without the PSR response when accessing a URL with an expired SSL cert.

Laravel Version: v9.3.1
PHP Version: 8.0.12
Database Driver & Version: N/A

Description:
When using the HTTP::pool to access a site with an expired SSL cert, I was expecting a GuzzleHttp\Exception\RequestException to be returned, but instead we get a Illuminate\Http\Client\Response but it is missing the internal PSR response, so accessing any of the response details fails.
Steps To Reproduce:
use Illuminate\Http\Client\Pool;
use Illuminate\Support\Facades\Http;

$responses = Http::pool(fn (Pool $pool) => [
    $pool->get('https://expired.badssl.com')
]);

$responses[0]->status();

I would expect the $response[0] to be a type of GuzzleHttp\Exception\RequestException but we get a valid looking Illuminate\Http\Client\Response
The call to ->status() results in an error because the Illuminate\Http\Client\Response internal PSR response property is null:
Call to a member function getStatusCode() on null in ....
At present my solution to detect this failure is to check for a null return on the response->toPsrResponse() and then check for a non zero in the handlerStats ssl_verify_result, but this is fragile as it depends on using the curl supplied ssl_verify_result.
...

if ($responses[0]->toPsrResponse() === null && $responses[0]->handlerStats()['ssl_verify_result']) {
   // SSL error occurred during request
}

Any help or pointers to more detail would be greatly appreciated!

This indeed seems like a bug to me as well. Would appreciate PR's for this.

Created a PR for this issue: #41412


Window.GetWindow returns null

Replace UserControl with another on without closing main window.
If i set this.DataContext = new model() then i get exception
private void ChromiumFxControl_Loaded(object sender, RoutedEventArgs e)
{
    this.Loaded -= ChromiumFxControl_Loaded;
    _Window = Window.GetWindow(this); > returns null
    _WindowHandle = new WindowInteropHelper(_Window).Handle;
    _Window.Closed += Window_Closed;
    _Window.LocationChanged += _Window_LocationChanged;
    _Window.StateChanged += Window_StateChanged;
    UpdateDpiMatrix();
}

Im not really sure what that means however, if i dont set the datacontext than everything works fine. If i also check for null and return
_Window = Window.GetWindow(this);
if (_Window == null)
{
return;
}
Everything loads and works properly. Can you also implement this check?

If this is hapenning that means that the component is loaded has it is not yet inserted in a window.
This is not something supported and simply ignoring this case may result in further bugs when window is resized or location changes as necessary events won't be listened. So this really an edge case that I am not sure this is a good idea to support.
The only thing I can think of rigth now would be change the corresponding code to raise a more explicit exception when this is hapenning.
Could you explain better your scenario? Why are you "replacing" UseControl?
Why not use the same and update the ViewModel?
Could check what is the callstack resulting in the loading of the usercontrol? Then could change your creation sequence to first add the usercontrol to the window.

ok, i found my issue. I set the model before setting the view. So possible a better execption message would show the mistake. thanks


chore(docs): update naming to match new branding initiative

use Composable Commere in most places
use commercetools Composable Commere when it makes better sense

I am curious, the platform-sdk wasn't touched as there are instances of platform, like here and here is this by choice?

Yeah, just saw them. I must have missed them.

Hi @jherey @ajimae! Thank you so much this looks awesome. 🥳 Left some comments and some questions, please let me know if anything is unclear. Thanks 🙏 🙏

@melindafekete thank you for your review. All your comments have been addressed, kindly take another look 🙏🏽

@melindafekete thank you for your review. All your comments have been addressed, kindly take another look 🙏🏽

Thanks @jherey! super nice! I think we missed one small thing, but otherwise in a good place. Not sure if the changes need to go out at the same time as in the main docs repo, let me check that, and I'll get back to you.

Hey @jherey! Thank you! 🤗  I checked with the docs team and it's good to go. 💪


Auto sync issue

After installation and adding it to settings following error occured.
ERRORS:
djangocms_owl.OwlCarousel.cmsplugin_ptr: (fields.E300) Field defines a relation
with model 'CMSPlugin', which is either not installed, or is abstract.

Is this using the version from PIP?
Any chance you could give me Django / CMS version numbers please and i shall take a look.


error in running demo.py

I downloaded the provided models, but got the following error when running demo.py
F0307 09:43:56.870270 21473 net.cpp:767] Check failed: target_blobs.size() == source_layer.blobs_size() (2 vs. 1) Incompatible number of blobs for layer conv0
*** Check failure stack trace: ***
Aborted (core dumped)

You should Run merge_bn.py to generate your own deploy caffemodel before running demo.py

solved, thx

Can I ask how it is solved? @hao522

RuntimeError: Could not open file MobileNetSSD_train.prototxt

solved, thx

hello，when I run
python merge_bn.py --model example/MobileNetSSD_deploy.prototxt --weights snapshot/mobilenet_iter_10000.caffemodel
there is an error, "Incompatible number of blobs for layer conv0". Have you ever had this problem?

Did you change the .prototxt fille manually?

solved, thx

hello，when I run
python merge_bn.py --model example/MobileNetSSD_deploy.prototxt --weights snapshot/mobilenet_iter_10000.caffemodel
there is an error, "Incompatible number of blobs for layer conv0". Have you ever had this problem?

Man, did you solve it?

Man, did you solve it? @yesyu

I'm having the exact same problem as @yesyu. Are these the right parameters for merge_bn.py?

I don't know why merge_bn.py isn't working from this repository, but I was able to find that this
works for me.


XML Sitemap getServerSideProps: 404 in production #3596

Almost everything in my NextJS is getStaticProps.
I only generate the dynamic XML Sitemaps with getServerSideProps. If I check it localhost it is working, in production the URL it is giving a 404.
Also did a test without .xml extensions, just a getServerSideProps test page. Also gets a 404.
Looks like the page is nog generated on the server with getServerSideProps.

Any ideas to fix this?
SST: 2.38.7
OpenNext v2.3.1
Next.js v14.0.2
https://discord.com/channels/983865673656705025/1027265626085019769/threads/1170375439664025773

I found the "issue".
I have a dynamic route [slug].tsx directly after the root in pages folder.
So I think that was the issue, and why it gaves 404 errors for other pages directly after the root in pages folder.
I have put the sitemaps in a separated folder in pages directory. Now everything is working fine.
Previous
pages
- [slug].tsx
-- sitemap-blogs.xml.tsx
--- sitemap-categorie.xml.tsx

Now
pages
- [slug].tsx
-- sitemap
--- sitemap-blogs.xml.tsx
--- sitemap-categorie.xml.tsx

I found the "issue".
I have a dynamic route [slug].tsx directly after the root in pages folder.
So I think that was the issue, and why it gaves 404 errors for other pages directly after the root in pages folder.
I have put the sitemaps in a separated folder in pages directory. Now everything is working fine.
Previous
pages
- [slug].tsx
-- sitemap-blogs.xml.tsx
--- sitemap-categorie.xml.tsx

Now
pages
- [slug].tsx
-- sitemap
--- sitemap-blogs.xml.tsx
--- sitemap-categorie.xml.tsx

I'll keep this open. We need to investigate the .xml files, I think we may have overlooked that.


Orran's profile story

Draft story for edits/comments: https://docs.google.com/document/d/1NyMqKXDOycZOC5HxtfKOuL0lPFJq6L-GAjQ_5_d7wOQ/edit


Refresh tokens draft

Refresh tokens article draft. Complete text. Missing diagrams, example and logo.

I know this is what we currently implement, but our use of /delegation to exchange a refresh token for a new id token is ill-advised and not to spec.
Refresh tokens are specified part of OAuth 2.0, and should be sent to /token, with a grant type of refresh_token.  When used in the context of OpenID Connect, refreshing id_tokens is described in this section of the spec: http://openid.net/specs/openid-connect-core-1_0.html#RefreshTokens

Added draft diagrams

Added example (please review). Still missing: redesigned diagrams and icon.


Implement as_raw_fd function in WpaController

I need to read messages from the file descriptor of wpa_controller in a separate thread to check events from unsolicited messages!
For doing that I think you should add this:
impl WpaController {
    pub fn as_raw_fd(&self) -> std::os::unix::io::RawFd {
        self.socket.as_raw_fd()
    }
}

Then I can start reading recvfrom(fd, &mut buffer)  from it by:
let fd = wpa_controller.as_raw_fd();

Is there a reason you cannot use https://github.com/DoumanAsh/wpa-ctrl/blob/master/src/lib.rs#L634C45-L634C62 ?

Yes!
I used that so far to receive the messages from wpa! But now I need a separate thread to just monitor unsolicited messages and act based on the received events!
This thread should be able to monitor separately from the main thread that responding to regular commands like add_network!
For example I want to call add_network and do the entire job there including receiving the response to make sure everything is Ok! And at the same time in my other function I want to monitor_unsolicited_messages that can read the wpa file descriptor and extract the events!
I can't do that through the provided recv message! I can't read wpa_controller by recv function from multi threads and receive the message on both!

I guess I should refactor it not to use internal buffer or make it optional to enable it to be thread safe
There is no need for raw file descriptor as it is badly usable for regular user

Or maybe just provide another function like monitor_unsolicited_messages() to return those in a separate channel then user doesn't need to have access to self.socket.as_raw_fd()!.
I only need a way to read those WPA Events separately if you can come up with another function fro that, would be great!

There is slight problem wit that approach is that you cannot really control order of messages so having multiple readers might be problematic
In any case I will need to think on that


AES-256 encryption not supported with Storage account names greater than 15 characters in length

Was working on a support ticket and found this TSG - https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/495033/1396-Mount-Error_Storage
Pasting the relevant content from the Wiki above
"Issues Description
Azure files supports Kerberos authentication with AD auth with RC4-HMAC and AES 256 encryption. AES 256 encryption support is currently limited to storage accounts with names <= 15 characters in length and needs to be manually enabled  for accounts which already have AD Auth enabled. AES 128 Kerberos encryption is not yet supported.
Due to group policy that enforces AES encryption type (or another encryption type), the domain controller may either 1) issue all service tickets to Azure Files identities encrypted as AES or 2) refuse to issue tickets for Azure Files identities due to not supporting the identity's default encryption type. In either of these cases, if AES 256 based encryption is not enabled on the account, the mount command will fail."
Azure files PG advised that 15 characters limitation still applies, and customers are being affected. This should be properly called out and documented under "support scenarios and pre-requisites"

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

ID: fba964be-3f77-d80c-f1a5-35bb1430bb8f
Version Independent ID: fe70b11e-10fe-5a8c-1fad-b22a83693503
Content: Overview - On-premises AD DS authentication to Azure file shares
Content Source: articles/storage/files/storage-files-identity-auth-active-directory-enable.md
Service: storage
Sub-service: files
GitHub Login: @khdownie
Microsoft Alias: kendownie

@haider392
Thanks for your feedback! We will investigate and update as appropriate.

@haider392
We recommend explicitly specifying $SamAccountName in addition to $StorageAccountName. If you don’t specify $SamAccountName, the script will fail if the $StorageAccountName is > 15 characters in length. Storage account names can be up to 24 chars if $SamAccountName is specified, but $SamAccountName is recommend to be 15 characters or less due to AD limit.
The planning doc you referenced is intended to be high level and isn't the right place for this kind of detail. Can you tell me where in the documentation you ran into Join-AzStorageAccount? Was it here:
https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-ad-ds-enable

@haider392 you can find more detail about the $SamAccountName parameter here:
https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-ad-ds-enable
That said, I am going to look into this about AES 256. The wiki could be out of date, but I'm not 100% sure.

@khdownie - Again, the issue is not with configuration of AD-DS. The customer was able to configure AD-DS auth for their storage account which has more than 15 characters. The issue was mounting it on their Windows machine. As per Azure files PG, if storage account name has more than 15 characters, then AES-256 is not supported. Customer enabled RC4 encryption and it worked for them!

@haider392 thanks for clarifying this. I will reach out to Azure Files PMs and get this clarified in the docs. Appreciate you calling this out.

@haider392 I believe we address this issue at the link below. I know you had an email thread with Yun and others. Is there anything we should add to the article to clarify?
https://learn.microsoft.com/en-us/azure/storage/files/storage-troubleshoot-windows-file-connection-problems?tabs=azure-portal#azure-files-on-premises-ad-ds-authentication-support-for-aes-256-kerberos-encryption

@haider392
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


getaddrinfo ENOTFOUND “db”

Have deployed nginx on portainer stacks with below mentioned code :-
version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    environment:
      DB_MYSQL_HOST: “db”
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: “myusername”
      DB_MYSQL_PASSWORD: “mypassword”
      DB_MYSQL_NAME: “nginx”
    volumes:
      - /mnt/nginx/data:/data
      - /mnt/nginx/letsencrypt:/etc/letsencrypt
  db:
    image: 'jc21/mariadb-aria:latest'
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: 'mypassword'
      MYSQL_DATABASE: 'nginx'
      MYSQL_USER: 'myusername'
      MYSQL_PASSWORD: 'mypassword'

    volumes:
      - /mnt/nginx/data/mysql:/var/lib/mysql

But getting this error log for both app & db.
Nginx App Error Log :-
[12/22/2021] [9:57:44 AM] [Global   ] › ✖  error     getaddrinfo ENOTFOUND “db”

Nginx Db Error Log :-
[i] pre-init.d - processing /scripts/pre-init.d/01_secret-init.sh
[i] mysqld not found, creating....
[i] MySQL data directory not found, creating initial DBs
[i] Creating database: nginx
[i] with character set: 'utf8' and collation: 'utf8_general_ci'
[i] Creating user: myusername with password mypassword
2021-12-21 22:02:33 0 [Note] /usr/bin/mysqld (mysqld 10.4.15-MariaDB) starting as process 52 ...
2021-12-21 22:02:33 0 [Note] Plugin 'InnoDB' is disabled.
2021-12-21 22:02:33 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-12-21 22:02:33 1 [Warning] 'user' entry '@042c97d53ec4' ignored in --skip-name-resolve mode.
2021-12-21 22:02:33 1 [Warning] 'proxies_priv' entry '@% root@042c97d53ec4' ignored in --skip-name-resolve mode.
2021-12-21 22:02:33 1 [Warning] 'user' entry '@042c97d53ec4' ignored in --skip-name-resolve mode.
2021-12-21 22:02:33 1 [Warning] 'proxies_priv' entry '@% root@042c97d53ec4' ignored in --skip-name-resolve mode.
/scripts/run.sh: ignoring or entrypoint initdb empty /docker-entrypoint-initdb.d/*

MySQL init process done. Ready for start up.

exec /usr/bin/mysqld --user=mysql --console --skip-name-resolve --skip-networking=0
2021-12-21 22:02:33 0 [Note] /usr/bin/mysqld (mysqld 10.4.15-MariaDB) starting as process 1 ...
2021-12-21 22:02:33 0 [Note] Plugin 'InnoDB' is disabled.
2021-12-21 22:02:33 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-12-21 22:02:33 0 [Note] Server socket created on IP: '::'.
2021-12-21 22:02:33 0 [Warning] 'user' entry '@042c97d53ec4' ignored in --skip-name-resolve mode.
2021-12-21 22:02:33 0 [Warning] 'proxies_priv' entry '@% root@042c97d53ec4' ignored in --skip-name-resolve mode.
2021-12-21 22:02:33 0 [Note] Reading of all Master_info entries succeeded
2021-12-21 22:02:33 0 [Note] Added new Master_info '' to hash table
2021-12-21 22:02:33 0 [Note] /usr/bin/mysqld: ready for connections.
Version: '10.4.15-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 3306  MariaDB Server

What is the issue...? I am not able to login to nginx-proxy-manager admin portal. It shows me "BAD GATEWAY"

Are both the npm and the database container in the same docker network so they can connect to each other? You can also use the SQLite database, since the issue can't occur then.

I think so. How to check the same..? Below docker compose was used which gave 2 containers.
version: '3'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
environment:
DB_MYSQL_HOST: “db”
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: “myusername”
DB_MYSQL_PASSWORD: “mypassword”
DB_MYSQL_NAME: “nginx”
volumes:
- /mnt/nginx/data:/data
- /mnt/nginx/letsencrypt:/etc/letsencrypt
db:
image: 'jc21/mariadb-aria:latest'
restart: unless-stopped
environment:
MYSQL_ROOT_PASSWORD: 'mypassword'
MYSQL_DATABASE: 'nginx'
MYSQL_USER: 'myusername'
MYSQL_PASSWORD: 'mypassword'
volumes:
  - /mnt/nginx/data/mysql:/var/lib/mysql

Ah, the issue is your normal quotation marks were converted to left and right quotation marks (“ instead of "). Make sure your your environment variables only have single quotes ' or double quotes " but no left “ and right ” quotation marks.


Dropbox: Failed to grab locks

After doing a sync with a large folder (188451 files), I received a few errors (56 files). Out of these few errors most where due to a "Failed to grab locks". I did some research and it looks like this is a generic API error as explained here: https://www.dropboxforum.com/hc/en-us/community/posts/204555365-Failed-to-grab-locks. Their recommended solution is to simply retry the failed files. Does rclone attempt to retry? If not, can it? Here are some samples of the errors I was receiving:
2015/08/18 14:17:08 wp-content/uploads/random-photo1.jpg: Failed to copy: Upload failed: Failed to grab locks for 586858203: lock held by connection 4744768.Please re-issue the request.
2015/08/18 14:19:22 wp-content/uploads/random-pdf.pdf: Failed to copy: Upload failed: Failed to grab locks for 586858203: lock held by connection 1407014.Please re-issue the request.
2015/08/18 14:19:22 wp-content/uploads/random-photo2.jpg: Failed to copy: Upload failed: Failed to grab locks for 586858203: lock held by connection 1407014.Please re-issue the request.
2015/08/18 14:37:51 wp-content/plugins/google-analytics-for-wordpress/languages/google-analytics-for-wordpress-pl_PL.mo: Failed to copy: Upload failed: Failed to grab locks for 586858203: lock held by connection 1406972.Please re-issue the request.
2015/08/18 14:43:39 wp-content/plugins/jetpack/modules/widgets/facebook-likebox/style.css: Failed to copy: Upload failed: Failed to grab locks for 586858203: lock held by connection 4554587.Please re-issue the request.
2015/08/18 14:57:15 wp-content/plugins/woocommerce/templates/myaccount/form-login.php: Failed to copy: Upload failed: Failed to grab locks for 586858203: lock held by connection 1407011.Please re-issue the request.

Thanks for the report.
If you retry the sync it should tidy up the 56 files.
Currently rclone doesn't retry, but I'm considering a --retries flag to automatically retry for every backend.
Also I could make dropbox retry for this specific case - I'll take a look at the API docs.

After running the same sync multiple times, I was able to slowly lower the error count. After running it 10+ times, I'm still left with ~17 errors. The odd thing is the same files seem to upload even tho the file set is the same. Here is the output of running the same sync 3 times.
Transferred:     10869623 Bytes (  47.46 kByte/s)
Errors:                17
Checks:            188456
Transferred:           50
Elapsed time:  3m43.652556927s

Transferred:      7029029 Bytes (  25.14 kByte/s)
Errors:                17
Checks:            188457
Transferred:           49
Elapsed time:  4m33.065457712s

Transferred:     10862907 Bytes (  47.72 kByte/s)
Errors:                18
Checks:            188457
Transferred:           49
Elapsed time:  3m42.316870934s

Here is a full log file. It looks like some persistence file lock errors no matter how many times I run the sync and lots of  .DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:40:58 Dropbox root 'backup/Sites/anchor.network': Building file list
2015/08/19 04:42:50 Dropbox root 'backup/Sites/anchor.network': Waiting for checks to finish
2015/08/19 04:42:58 Transferring:  wp-content/blogs.dir/103/files/2013/12/STORMWATER-MANAGEMENT-ORDINANCE-<IP_ADDRESS>4.pdf, wp-content/blogs.dir/106/files/2014/01/Cover-to-post-on-blog-150x150.jpg, wp-content/blogs.dir/106/files/2014/01/Cover-to-post-on-blog.jpg, wp-content/blogs.dir/106/files/2014/01/Cover-to-post-on-blog1-150x150.jpg
2015/08/19 04:43:00 wp-content/blogs.dir/106/files/2014/01/Cover-to-post-on-blog.jpg: Failed to copy: Upload failed: Failed to grab locks for 586858203: lock held by connection 4482258.Please re-issue the request.
2015/08/19 04:43:58 Transferring:  wp-content/blogs.dir/103/files/2013/12/STORMWATER-MANAGEMENT-ORDINANCE-<IP_ADDRESS>4.pdf, wp-content/blogs.dir/127/files/2014/09/DSC_0141.jpg
2015/08/19 04:44:08 wp-content/plugins/advanced-custom-fields-pro/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:10 wp-content/plugins/advanced-custom-fields-pro/admin/updates/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/admin/updates/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:10 wp-content/plugins/advanced-custom-fields-pro/admin/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/admin/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:13 wp-content/plugins/advanced-custom-fields-pro/admin/views/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/admin/views/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:13 wp-content/plugins/advanced-custom-fields-pro/assets/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/assets/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:16 wp-content/plugins/advanced-custom-fields-pro/assets/inc/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/assets/inc/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:16 wp-content/plugins/advanced-custom-fields-pro/assets/css/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/assets/css/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:17 wp-content/plugins/advanced-custom-fields-pro/assets/inc/datepicker/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/assets/inc/datepicker/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:18 wp-content/plugins/advanced-custom-fields-pro/assets/inc/select2/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/assets/inc/select2/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:19 wp-content/plugins/advanced-custom-fields-pro/assets/js/.DS_Store: Failed to copy: Upload failed: Failed to grab locks for 586858203: lock held by connection 1406973.Please re-issue the request.
2015/08/19 04:44:20 wp-content/plugins/advanced-custom-fields-pro/fields/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/fields/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:20 wp-content/plugins/advanced-custom-fields-pro/forms/.DS_Store: Failed to copy: Upload failed: Failed to grab locks for 586858203: lock held by connection 4483853.Please re-issue the request.
2015/08/19 04:44:21 wp-content/plugins/advanced-custom-fields-pro/lang/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/lang/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:23 wp-content/plugins/advanced-custom-fields-pro/pro/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/pro/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:24 wp-content/plugins/advanced-custom-fields-pro/pro/assets/js/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/pro/assets/js/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:24 wp-content/plugins/advanced-custom-fields-pro/pro/admin/.DS_Store: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/advanced-custom-fields-pro/pro/admin/.DS_Store is on the ignored file list, so it was not saved.
2015/08/19 04:44:25 wp-content/plugins/gravityformspaypalpaymentspro/images/Thumbs.db: Failed to copy: Upload failed: The file /backup/sites/anchor.network/wp-content/plugins/gravityformspaypalpaymentspro/images/Thumbs.db is on the ignored file list, so it was not saved.
2015/08/19 04:44:39 Dropbox root 'backup/Sites/anchor.network': Waiting for transfers to finish
2015/08/19 04:44:39 Dropbox root 'backup/Sites/anchor.network': Not deleting files as there were IO errors

If I try uploading a file called .DS_Store through the website I get "Sorry! This file name is not allowed.".
A bit of searching and this is the best list I can find of file names which aren't allowed - see Ignored files.  I've also seen people saying to avoid windows tempfile names.
Of 18 errors above, there are 15 to do with the ignored file list.  That leaves 3 lock errors.  However 2 of those are to do with directories called .DS_Store so there is actually only 1 file missing from the sync.
Perhaps if rclone ignored the files which dropbox doesn't like that would go through too.
You could always try a more narrow sync to get it to go through, eg
rclone -v copy wp-content/blogs.dir/106/files/2014/01/ dropbox:wp-content/blogs.dir/106/files/2014/01/

Anyway I think that is two bugs now

retry the lock fails
add an exclude list for files dropbox can't upload

Makes sense. Maybe adding an exclude option like rsync's --exclude? Unless that already exists.
I synced the individual folder as you recommend. I ran it 4 times with varying outputs. Take a look here: https://cloudup.com/cJ_sUMBbhrH.

Ok digging deeper, I think I discovered the root bug. On my file system, it appears I have 2 files with the same name and different file sizes.
-rw-r--r--. 1 root root  59K Jan 25  2015 cover-to-post-on-blog.jpg
-rw-r--r--. 1 root root  32K Jan 25  2015 Cover-to-post-on-blog.jpg

Everytime I run the rclone sync to Dropbox it's randomly picking one. Sometimes is deletes the file, sometimes it uploads file 1 and sometimes it upload file 2. Take a look at this file's revisions on Dropbox: https://cloudup.com/ciQJVyK6se7. I'm not sure the best way to handle this considering Dropbox will not store both files. Is it possible to have rclone know if there are multiple files with the same name, different case sensitivity? If so then maybe rclone can attempt the "first" alphabetical order option and ignore the rest.

I've encountered the initial error when uploading hundreds/thousands of files in one go. Second attempt works OK after that. +1 for adding a "--retries" option though.

@austinginder well done - good investigation - that sounds spot on.
rclone could give a warning quite easily.  It would be fairly tricky to pick the first alphabetically as the internals of rclone are concurrent and it doesn't actually get the listing then transfer files, it does everything all at once.
I'll make a separate ticket for that

@darren12345 I made a ticket for --retries in #109 so I don't forget!

Super. Although I noticed today you had the forethought to make rclone return a non-zero exit code in the event of any errors so I've been able to wrap it in an while loop.

On 20 Aug 2015, at 16:42, Nick Craig-Wood<EMAIL_ADDRESS>wrote:
@darren12345 I made a ticket for --retries in #109 so I don't forget!
—
Reply to this email directly or view it on GitHub.

Since the lock problem happens very rarely and is difficult to detect, I'm going to implement --retries #109 in favour of this ticket.
Since the other issues have been split out into #107 and #108 that leaves nothing left in this issue so I'm going to close it.
Thank you very much for taking the time to report the issues, and do follow the issues above if you are interested.

Sounds good. Thanks for all your work! It's much appreciated.


clarify docs for schedule_in param of configure()

Hi! great library.
The schedule_in docs say 'a dict describing a time interval', here:
https://github.com/procrastinate-org/procrastinate/blob/781cbdf0ce272f9bc449acbccc8caa65108c6649/procrastinate/tasks.py#L162
Might be clearer to say explicitly these are kwargs for a timedelta? I had to dig in code to figure this out:
https://github.com/procrastinate-org/procrastinate/blob/781cbdf0ce272f9bc449acbccc8caa65108c6649/procrastinate/tasks.py#L28
thanks again for publishing this

You're definitely right !
Are you interested to contribute this ?

sure! I'll submit a PR in the next few days


Add Continuous Integration (CI) using GitHub actions

Summary of code changes

This GitHub actions workflow automates the process of building and testing new code changes to the tudat repository. It is triggered upon push and pull request to master and develop.
Closes #199
ccache is used to cache previous compilation results to speed up the build process across subsequent runs.
Three tests were found to be failing for MacOS. They will be reported as separate issues upon merging this pull request. The test failure is not related to the CI workflow.
The CI workflow runs in parallel for the three operating systems defined in the matrix. The time taken for the workflow to finish execution is determined by the OS that takes the most time.

Results

The CI workflow takes a total of 2 hours to run for the first time. The compiler cache is stored at the end of the first run.
After a compiler cache hit, the CI workflow takes approximately 20 minutes to finish its execution across all the three operating systems. Execution time per operating system is the following:

Linux: 10 minutes
Windows: 20 minutes
MacOS: 15 minutes

Note: There is a cache limit of 10GB for the repository. If the workflow fails to store cache, it could be due to the lack of storage space for the cache. Compiler cache entries are deleted automatically by GitHub after 1 week, but, they may need to be deleted manually if the storage fills up before a week. You can monitor and manage the cache storage for the repository here

Thanks! This looks awesome :) I'm merging this now, and will test it out soon!


Improve the language support in migration library

In the current migration library, the language feature is not fully utilised. Three of the error messages still use strings. I suggest to add these entries into migration_lang.php so that we can provide more support to multiple languages. Meanwhile, languages should be loaded before any error messages showing up.

Looks good to me.

These 3 errors are triggered by show_error() (which means they're fatal and stop script execution), while the others that already have translated messages are runtime ones.
I know this doesn't seem important, but it is. show_error() will be replaced by exceptions in CI3.1 and using language translation in there can cause a lot of problems.
Only messages that may be seen by an end user should be translated, while fatals should only be seen by application developers, who pretty much must know English or they just won't be able to understand CodeIgniter or programming in general.


YARN-10632. Make auto queue creation maximum allowed depth configurable

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m 15s

trunk passed

+1 :green_heart:
compile
1m 11s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
1m  1s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 50s

trunk passed

+1 :green_heart:
mvnsite
1m  4s

trunk passed

+1 :green_heart:
javadoc
0m 56s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 47s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 11s

trunk passed

+1 :green_heart:
shadedclient
24m  2s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 58s

the patch passed

+1 :green_heart:
compile
1m  5s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
1m  5s

the patch passed

+1 :green_heart:
compile
0m 56s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 56s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 44s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: The patch generated 1 new + 34 unchanged - 0 fixed = 35 total (was 34)

+1 :green_heart:
mvnsite
0m 57s

the patch passed

+1 :green_heart:
javadoc
0m 46s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 42s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m  9s

the patch passed

+1 :green_heart:
shadedclient
23m  8s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
97m 48s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 34s

The patch does not generate ASF License warnings.

195m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3859/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3859

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux f0564ea7d8a8 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 5aa48d8391f4fb5d44213d1bc3af9fdf289c9d5e

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3859/1/testReport/

Max. process+thread count
1001 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3859/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 19s

trunk passed

+1 :green_heart:
compile
1m 15s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m  1s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
0m 54s

trunk passed

+1 :green_heart:
mvnsite
1m  4s

trunk passed

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 47s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
1m 54s

trunk passed

+1 :green_heart:
shadedclient
21m 15s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 56s

the patch passed

+1 :green_heart:
compile
0m 58s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
0m 58s

the patch passed

+1 :green_heart:
compile
0m 49s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
0m 49s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 38s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: The patch generated 1 new + 34 unchanged - 0 fixed = 35 total (was 34)

+1 :green_heart:
mvnsite
0m 53s

the patch passed

+1 :green_heart:
javadoc
0m 40s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 37s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
1m 58s

the patch passed

+1 :green_heart:
shadedclient
20m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
96m 27s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

186m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3859/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3859

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux c93546a21df2 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 5aa48d8391f4fb5d44213d1bc3af9fdf289c9d5e

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3859/2/testReport/

Max. process+thread count
945 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3859/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

@9uapaw On second thought: templating support for deeper than 2 allowed depths should would with the current wildcard, or does it need an update?

@brumi1024 I think that will need to be addressed in a followup patch, because currently wildcard only makes sense in a depth 2 limit scenario.

Can you make a followup jira for that?

LGTM Thanks @9uapaw for contribution and @brumi1024 for review.
Merged to trunk.


Bug: AddressInput is sending multiple invites

When initiating from the React app to  the iOS example app, I noticed three different invites coming in, with three different topics for the same peer address. Looking at the network tab, it seemed to confirm this. I added this following console.log:

Then pasted an address into the address input and got the following in the console output:

I was also able to verify this using a test script that I ran once to publish the user contact and verify there were no conversations, then again after I pasted the script's wallet address into the address input on the website.
import Client from './Client'
import { PrivateKey } from './crypto'
import { Wallet } from 'ethers'

const keyBytes = [
  53, 222, 207, 146, 166, 40, 92, 218, 85, 194, 222, 186, 136, 216, 78, 73, 40,
  85, 195, 225, 86, 141, 136, 37, 221, 38, 120, 159, 231, 95, 14, 244,
]

const wallet = new Wallet(keyBytes)
console.log(`OUR WALLET ADDRESS IS ${wallet.address}`)

async function checkAll() {
  const client = await Client.create(wallet, { env: 'dev' })
  await client.publishUserContact()
  const conversations = await client.conversations.list()
  console.log('conversations', conversations)
}

checkAll().then(() => console.log('Done'))

When I ran it a second time I was able to verify that there were three conversations created.

View script output

Expected behavior
I think I'd only expect to see 1 invite sent. There's probably some work to be done on the other end in the iOS SDK to handle multiple invites from the same sender with the same conversationId, so I'll open an issue over there as well.

Oof. That's a good catch. Will fix