Add AIS 4G Board library

AIS 4G Board is a compact circuit board built for use in IoT development via 4G network using a market-leading microcontroller module from Espressif, model "ESP32-WROOM-32" and 4G communication module from SIMCom, model "SIM7600E-H1C", which supports LTE Cat 4 signals. This board has been designed and manufactured as a 4-Layer PCB according to engineering standards specified by IPC and includes built-in circuit protection in the form of transient-voltage-suppression of each I/O pins. The board itself has many incredible and useful functions. For example, there are two USB Type-C connectors: one for direct connection to SIM7600E-H1C, and the other for ESP32-WROOM-32 via the FTDI chip, which acts as a USB-to-Serial converter that is stable and supports all operating systems. There is an on-board temperature and humidity sensor, also includes several LED indicators, an RS485 port, GPS for location tracking, ESIM is pre-installed onto the board so no additional SIM installation is required, a MicroSD card slot for data logging. And the most unique thing about this product is its ability to promptly connect to the Microsoft Azure cloud services.
More info: https://devicecatalog.azure.com/devices/f772e8e6-d0c4-4d08-b5fc-9e4abfe712b2

@ArduinoBot plz recheck, Fixed.


Checksum mismatch

When trying to compile I'm getting a checksum mismatch:
verifying<EMAIL_ADDRESS>checksum mismatch
downloaded: h1:L+JLhJUoAwVvkEhbpETP3Mli9qiRnDHlgQibYZZes6E=
go.sum:     h1:x/2aZW6OnN60Ot7VCTShG1B7H47QaWRS7pCxkgCpfaI=
SECURITY ERROR
This download does NOT match an earlier download recorded in go.sum.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.
Is this a go version issue? Which version whould I use?
Also if you have time, there is no schema.sql anymore, so the readme is somewhat misleading.

Tried adding it and it produced
build .: cannot find module for path .
when building

This should be fixed in 8685f1a. Sorry about the delay!


Model unknown Manuf.: ABB - Model: -3P25-

Hello Alex,
Could you please add the model FIMER UNO-DM-5.0-TL-PLUS to the database, which is identified with the code -3P25-?
Also, I'm facing an issue due to an error following the installation of the latest version (2.2.1) due to pymodbus not working. Could you please help me in solving this, please?
Thanks in advance for your assistance
Domenico

Hi,
I also have the same problem, until version 2.0xx everything worked correctly, now it doesn't work anymore, and I can't even delete the device.
Thanks
Luca

Could you please add the model FIMER UNO-DM-5.0-TL-PLUS to the database, which is identified with the code -3P25-?

Ciao Domenico. As explained on the forum, I need the info from the log, you should find this kind of "error" with the data needed to update the list:
(opt_comm_model) Model unknown, report to @alexdelprete on the forum the following data: Manuf.: ABB - Model: -3P31- - Options: 0x10ED/0xFF69/ - OptModel: 0x10ED/0xFF69/ - OptModelInt: 16

Also, I'm facing an issue due to an error following the installation of the latest version (2.2.1) due to pymodbus not working. Could you please help me in solving this, please?

You need to provide me more info. "not working" doesn't help me understand what your problem is. What error do you have when installing? When do you have the error, when installing or configuring it? Or after the configuration? Try to be detailed.
Anyway, try latest version I just released: v2.3.0 and let me know. Also, make sure you're not using the modbus native integration in config.yml, other users have had problems because they forgot to disable modbus integration when they switched to this component.

I also have the same problem, until version 2.0xx everything worked correctly, now it doesn't work anymore, and I can't even delete the device.

"Doesn't work" will not allow me to help understanding what's your problem. You have to be more specific, provide log errors etc.
Also, your problem might not be the same Domenico has. Open a separate issue if needed.

Model: -3P25-
Options: 0x0FED/0xFF69/

Could you paste here the log lines from HA please? They contain some needed values.

2023-01-22 16:13:18.632 ERROR (MainThread) [pymodbus.client.sync] Connection to (<IP_ADDRESS>, 502) failed: timed out
2023-01-22 16:13:18.654 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Manufacturer: ABB
2023-01-22 16:13:18.655 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Model: -3P25-
2023-01-22 16:13:18.657 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Options: 0x0FED/0xFF69/
2023-01-22 16:13:18.671 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Slave ID: 1
2023-01-22 16:13:18.673 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Base Address: 40000
2023-01-22 16:13:18.674 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Inverter Type: 101
2023-01-22 16:13:18.676 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec.sensor] Model: -3P25-
2023-01-22 16:13:18.678 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec.sensor] manufacturer: ABB
2023-01-22 16:13:18.679 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec.sensor] SW Version: 2201A
2023-01-22 16:13:18.681 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec.sensor] Inverter Type: Single Phase
2023-01-22 16:13:18.703 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up abb_powerone_pvi_sunspec platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 281, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/abb_powerone_pvi_sunspec/sensor.py", line 20, in async_setup_entry
hub.read_modbus_data_inverter()
File "/config/custom_components/abb_powerone_pvi_sunspec/init.py", line 243, in read_modbus_data_inverter
inverter_data = self.read_holding_registers(unit=self._slave_id, address=(self._base_addr + 4), count=64)
File "/config/custom_components/abb_powerone_pvi_sunspec/init.py", line 181, in read_holding_registers
return self._client.read_holding_registers(address, count, **kwargs)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/common.py", line 114, in read_holding_registers
return self.execute(request)
File "/usr/local/lib/python3.10/site-packages/pymodbus/client/sync.py", line 108, in execute
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Failed to connect[ModbusTcpClient(<IP_ADDRESS>:502)]
2023-01-22 16:13:38.734 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Manufacturer: ABB
2023-01-22 16:13:38.736 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Model: -3P25-
2023-01-22 16:13:38.737 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Options: 0x0FED/0xFF69/
2023-01-22 16:13:38.750 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Slave ID: 1
2023-01-22 16:13:38.752 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Base Address: 40000
2023-01-22 16:13:38.754 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Inverter Type: 101
2023-01-22 16:13:58.723 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Manufacturer: ABB
2023-01-22 16:13:58.724 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Model: -3P25-
2023-01-22 16:13:58.725 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Options: 0x0FED/0xFF69/
2023-01-22 16:13:58.743 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Slave ID: 1
2023-01-22 16:13:58.744 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Base Address: 40000
2023-01-22 16:13:58.745 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Inverter Type: 101
2023-01-22 16:14:21.716 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Reading data failed! Please check Slave ID: 1
2023-01-22 16:14:21.717 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Reading data failed! Please check Reg. Base Address: 40000
2023-01-22 16:14:25.514 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Manufacturer: ABB
2023-01-22 16:14:25.515 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Model: -3P25-
2023-01-22 16:14:25.516 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Options: 0x0FED/0xFF69/
2023-01-22 16:14:25.544 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Slave ID: 1
2023-01-22 16:14:25.545 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Base Address: 40000
2023-01-22 16:14:25.546 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Inverter Type: 101
2023-01-22 16:14:25.547 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec.sensor] Model: -3P25-
2023-01-22 16:14:25.548 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec.sensor] manufacturer: ABB
2023-01-22 16:14:25.549 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec.sensor] SW Version: 2201A
2023-01-22 16:14:25.549 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec.sensor] Inverter Type: Single Phase
2023-01-22 16:14:41.787 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Manufacturer: ABB
2023-01-22 16:14:41.788 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Model: -3P25-
2023-01-22 16:14:41.790 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Options: 0x0FED/0xFF69/
2023-01-22 16:14:44.794 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Slave ID: 1
2023-01-22 16:14:44.795 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Base Address: 40000
2023-01-22 16:14:44.796 ERROR (MainThread) [custom_components.abb_powerone_pvi_sunspec] Reading data failed! Please check Slave ID: 1

Do you have in the logs lines that contain text that says to contact me to report the model etc.? Search for "alexdelprete" in the log.
I see from the log that your component doesn't connect, you didn't solve the problem? Is the Slave ID correct? Is the Base Address correct?

Alex, I searched the logs but I'm not able to find "alexdelprete" in it.
I'm currently running v. 2.0.5-beta.2 which is quite old, but I did not update because of the errors I was receiving with newer versions.
The slave ID 1 seems to be correct, communication is working and also QModMaster is able to retrieve values starting address 40000

That log above reports 3 different READ DATA ERRORS. It means it wasn't able to contact the inverter (or the VSN300). How is it working? It happens often?

No, it was today, due to an update of HACS software. After that, all is working correctly.

Did you try latest version? I'm also about to release a newer version that allows to configure the parameters at runtime. Try it and let me know...old versions are not recommended anymore. :)

Thanks Alex, I will try and let you know in case I need your great assistance

No problem. Let me know if something doesn't work.

UNO-DM-5.0-TL-PLUS

Added your model to the known list. It'll be included in next release.

2023-01-23 11:00:19.614 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-01-23 11:00:19.616 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration abb_powerone_pvi_sunspec which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

These are not an issue, it's a standard msg from HA when you use a custom component that is not an official integration. No worries.

2023-01-23 11:00:41.597 ERROR (MainThread) [homeassistant.setup] Setup failed for modbus: Unable to import component: No module named 'pymodbus.client.sync'
Also, another device which uses modbus does not work, seemingly due to some sort of conflict.

Another user reported this, he was using the component and also modbus: integration, and they conflicted (I don't know why, I used the two together in the past with no issues).
Try disabling the modbus: integration for now, commenting the lines of the other device in the config, and restart HA, so we're sure my component is working. Once you verify it's working, readd the modbus: integration for the other device and restart HA, tell me what happens.
BTW: I didn't release the new version with your model, how can it show up? Let me see the list of the sensors with the model so I can check how it's identified. Thanks.

@usrpend please open a separate issue about the modbus: conflict.
I'll close this one, ok?


Multi service grouped toc

A few points about this PR:
It relies on a fork of the Azure DevOps CI pipeline job and not the current job definition. This is because it has to support a different,larger set of inputs and steps because each moniker requires its own CI conifg, which have been renamed and added to the ci-configs directory.
the .openpublishing config changes are non-destructive and will not impact the master branch.
The docfx.json changes in the PR currently are destructive, and will need to reconcile with the docfx.json in the master branch for the content to co-exist.
Differentiated target URL path is not done - I plan on using a /docpreview slug in the URL to keep it separate from the rest of the content.
New top-level folders have been added for latest-version for the new CI outputs. I didn't want to re-use or overwrite the existing content in any way.

Docs Build status updates of commit dc57d02:
:warning: Validation status: warnings

File
Status
Preview URL
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-keyvault-v4)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-storage-v12)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-storage-v12)
Details

<EMAIL_ADDRESS>:warning:Warning
View (az-js-storage-v12)
Details

docs-ref-autogen/toc.yml
:warning:Warning
View (az-js-keyvault-v4) View (az-js-storage-v12)
Details

docs-ref-services/latest/index.yml
:warning:Warning
View (az-js-keyvault-v4)
Details

ci-configs/packages-latest.json
:white_check_mark:Succeeded

docfx.json
:white_check_mark:Succeeded

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

<EMAIL_ADDRESS>:white_check_mark:Succeeded
View (az-js-keyvault-v4)

This comment lists only the first 50 files in the pull request.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'backupCertificate'.

<EMAIL_ADDRESS>
Line 6, Column 11: [Warning-xref-not-found] Cross reference not found: 'beginCreateCertificate'.

<EMAIL_ADDRESS>
Line 6, Column 11: [Warning-xref-not-found] Cross reference not found: 'beginDeleteCertificate'.

<EMAIL_ADDRESS>
Line 6, Column 11: [Warning-xref-not-found] Cross reference not found: 'beginRecoverDeletedCertificate'.

<EMAIL_ADDRESS>
Line 90, Column 16: [Warning-xref-not-found] Cross reference not found: '7.0'.
Line 90, Column 39: [Warning-xref-not-found] Cross reference not found: '7.1'.

<EMAIL_ADDRESS>
Line 6, Column 11: [Warning-xref-not-found] Cross reference not found: 'beginCreateCertificate'.
Line 6, Column 42: [Warning-xref-not-found] Cross reference not found: 'beginDeleteCertificate'.
Line 6, Column 76: [Warning-xref-not-found] Cross reference not found: 'beginRecoverDeletedCertificate'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'createCertificate'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'createIssuer'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'deleteCertificateOperation'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'deleteContacts'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'deleteIssuer'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'getCertificateOperation'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'getCertificate'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'getCertificatePolicy'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'getCertificateVersion'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'getContacts'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'getDeletedCertificate'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'getIssuer'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'getPlainCertificateOperation'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'importCertificate'.

<EMAIL_ADDRESS>
Line 5, Column 105: [Warning-xref-not-found] Cross reference not found: 'listDeletedCertificates'.

<EMAIL_ADDRESS>
Line 5, Column 105: [Warning-xref-not-found] Cross reference not found: 'listPropertiesOfCertificateVersions'.

<EMAIL_ADDRESS>
Line 5, Column 105: [Warning-xref-not-found] Cross reference not found: 'listPropertiesOfCertificates'.

<EMAIL_ADDRESS>
Line 5, Column 105: [Warning-xref-not-found] Cross reference not found: 'listPropertiesOfIssuers'.

<EMAIL_ADDRESS>
Line 5, Column 60: [Warning-xref-not-found] Cross reference not found: 'mergeCertificate'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'purgeDeletedCertificate'.

<EMAIL_ADDRESS>
Line 5, Column 60: [Warning-xref-not-found] Cross reference not found: 'restoreCertificateBackup'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'setContacts'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'updateCertificate'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'updateCertificatePolicy'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning-xref-not-found] Cross reference not found: 'updateIssuer'.

<EMAIL_ADDRESS>
Line 5, Column 31: [Warning-xref-not-found] Cross reference not found: 'QueueClient.peekMessages'.

<EMAIL_ADDRESS>
Line 5, Column 31: [Warning-xref-not-found] Cross reference not found: 'QueueClient.receiveMessages'.

<EMAIL_ADDRESS>
Line 5, Column 31: [Warning-xref-not-found] Cross reference not found: 'QueueClient.sendMessage'.

docs-ref-autogen/toc.yml

Line 180, Column 19: [Warning-file-not-found] Invalid file link: '../docs-ref-services/latest/storage/stogez-overview.md'.

docs-ref-services/latest/index.yml

Line 21, Column 18: [Warning-file-not-found] Invalid file link: 'file1.md'.
Line 23, Column 18: [Warning-file-not-found] Invalid file link: 'file2.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@danieljurek The docfx.json has been reconciled with the master branch and the CI configs from master have been re-added.
I would now like to re-run both CI jobs to ensure that all the all the autogen is in place.

@danieljurek The CI from the master branch content is now in place and the diff between branches is now basically what I'd expect.
Once this is merged into grouped-toc, then you can make the breadcrumb and fit/finish changes you deem necessary, and we can get this moved into master as the publishing changes should not affect the live content.


Add check for raven when checking detectors

As mentioned by in https://github.com/davechurchill/commandcenter/pull/37 a check for raven is missing.
The full list of detectors is here:
http://wiki.teamliquid.net/starcraft2/Detector
The units that need one of their abilities to be active for detection are still left out.

Thanks!

Does sc2::UNIT_TYPEID::TERRAN_BANSHEE detector? Oo

@alkurbatov I guess there are banshees in the co-op missions or campaign.


Release version 1.6.0

Hello,
For the lack of a better way to ask the question, I misuse this issue section to ask for an update on the release of version 1.6.0.
I couldn't find an explicit list of blocking issues or missing features.
Is there a way to help finishing up the RC round?
The reason I'm asking is because Twirl 1.6.0 is appparently the missing bit for a release of Scalatra 3.0.0.
Thanks!

I am very sorry for the delay, urgent family related things kept me pretty much away from keyboard the last two weeks, I hope next week finally I can catch up here also with a twirl release.

Thanks for your quick reaction.
No problem, family is obviously more important than anything else.

Ping!

Hi @mkurz, I hope things are going fine at home on your side.
Do you think you could make a release in the near future? Thanks!

Release will happen this week, 100%

Twirl 1.6.0 released:
https://github.com/playframework/twirl/releases/tag/1.6.0


Betas / Nightlies?

Just wondering if we could get a nightlies / beta downloads area?
Also, a static link to the most recent stable build would be good too.  Most others label this as -latest.

Good idea, I just haven't had the time to automate this.

I like this too, because I seen a lot of changes so far and I'm still waiting for the next release.

I checked my current infrastructure and it doesn't allow the nightly builds right now. I have to refactor my infrastructure first so that nighly builds are possible ;)

@xyber411
Until that time, you can download the zip file and get go language for your OS and use "go build" and get the compile file.
I have macOS and I got Go with homebrew and after I run the "go build" it tells me some package missing inside quote and I just copy those and used "go get ..." one by one until it compile the file.
Hope that help you for time being.

@dweidenfeld
Suggest to update version number on new commit since people may compile from source themselves

@Em31Et I see. But the problem is, that I currently don't want to set the version for the next release because I don't know what kind of version it will be (http://semver.org/).
I think we should wait, till I got the process running for nightlies ;)

@dweidenfeld I've managed to get tag based commits to compile via travis on my fork, this could be done for every commit release or for point releases.
Looking to expand the build process for all os's.

@mitchelp is already working on a forum and vps setup for nighly builds.
@jaketame thank you for your work, but I think you can stop now, because there will be an official solution soon ;)

@dweidenfeld Maybe we should wait with a forum for now. It will make plexdrive bigger and it's as you said just a side project to support gdrive until rclone does.
@jaketame maybe it's not a good thing to have nightlies, because there will be a lot of less experienced users that will install and start complaining about functions that are not ready. Or other bugs and fails in the not finished for release code.
The experience users now how to build from source. So they can do that in case needed.

@mitchelp I agree... There have been too many questions about non-final versions already. So I don't think I will provide nighlies.

Since plexdrive is stable now there is an automated process for pushing nightlies / change versions to GitHub and Slack ;)


Oracle, getChangeLogLockName() return wrong handle

I have several different Liquibase changelogs, with different different liquibaseSchemaName  from liquibase.properties file.
Using plain Liquibase without this extension, it places the Liquibase tables, including changeloglock in the schema specified in the property liquibaseSchemaName.
When using the liquibase-sessionlock extension it creates the lock handle with database.getDefaultSchemaName()  which is the default schema for the connection.
Since we use one user for all migrations, we'd get a lot of unnecessary blocking of migrations.
My suggestion is to use database.getLiquibaseSchemaName() in order to get a handle that mimics the default behavior of Liquibase.
I have a fork of this repo and is currently testing this change for Oracle.

Just saw your fork, I've created a PR and merged it


no-unused-vars set to warn

Because https://github.com/nzakas/eslint-plugin-typescript/pull/84.

ae4452bf7e641fa0c8a4d5de3cdf4c687ba0868c


Mid-backup: “OSError: [Errno 22] Invalid argument” at gyb.py line 828

I’m using the latest (0.47) version of GYB on Windows 7 SP1 (64-bit) with all Windows updates. I’m attempting to do a simple backup, specifying my gmail address on the command line (using --email) and letting all other options default.  I’m using GYB for the first time.  After backing up about 9 GB (220162 messages) of my 14 GB Google Apps for Work mailbox, GYB quits with the below stack trace and messages.  I tried quitting other apps and rerunning it, but it failed with the same messages soon after reporting the number of messages it needs to backup.  I still have plenty enough free disk space for the backup to complete, so that’s not the problem.  Here is the output from the command prompt window:
Got 348315 Message IDs
GYB needs to examine 348315 messages
GYB already has a backup of 220162 messages
GYB needs to backup 128153 messages
Traceback (most recent call last):
  File "gyb.py", line 1503, in <module>
  File "gyb.py", line 969, in main
  File "gyb.py", line 460, in callGAPI
  File "oauth2client\util.py", line 135, in positional_wrapper
  File "googleapiclient\http.py", line 1435, in execute
  File "gyb.py", line 828, in backup_message
OSError: [Errno 22] Invalid argument
Failed to execute script gyb

I reran with the --debug option.  The output seems to indicate that both of the last couple of requests returned a 200/OK status.  The second-to-last request appears to be a POST containing 100 “GET /gmail/v1/users/me/messages…” requests.  The last request appears to be a “GET /gmail/v1/users/me/labels…” request.  The Reply from that last request was:
reply: 'HTTP/1.1 200 OK\r\n'
header: Cache-Control header: Pragma header: Expires header: Date header: ETag header: Vary header: Vary header: Content-Type header: Content-Encoding header: X-Content-Type-Options header: X-Frame-Options header: X-XSS-Protection header: Server header: Alternate-Protocol header: Alt-Svc header: Transfer-Encoding

I’m guessing that there must be something about one of my messages or labels that GYB can’t handle.
Expected behavior would be for GYB to handle this situation, or identify the message/label causing the problem (so that I could change or delete it from my mailbox) and ideally skip that message/label and continue with the backup operation.
I'd greatly appreciate a workaround (or a GYB patch that I could try).
Thanks for any help you can provide!

I am using also gyb version 0.47 on a Windows Server 2012R2 installation.
I've got the same error (Error 22) with the following message:
Got 79658 Message IDs
GYB needs to examine 79658 messages
GYB already has a backup of 76502 messages
GYB needs to backup 3156 messages
Traceback (most recent call last):
File "gyb.py", line 1503, in
File "gyb.py", line 969, in main
File "gyb.py", line 460, in callGAPI
File "oauth2client\util.py", line 135, in positional_wrapper
File "googleapiclient\http.py", line 1435, in execute
File "gyb.py", line 840, in backup_message
OSError: [Errno 22] Invalid argument<EMAIL_ADDRESS>om\2016\7\31\1564052821d0ecd2.eml'
Failed to execute script gyb
As far as I can see (i am not familiar with phyton) it is an open file statement. But the path is correct, the file does not yet exist and there are two other files in that folder. I tried to execute the script again but it fails at the same place, of course with another filename.
I hope this could help to find the bug.
Thomas

I also have the same issue:
Traceback (most recent call last):
File "gyb.py", line 1580, in
File "gyb.py", line 1044, in main
File "gyb.py", line 487, in callGAPI
File "oauth2client\util.py", line 137, in positional_wrapper
File "googleapiclient\http.py", line 1435, in execute
File "gyb.py", line 855, in backup_message
OSError: [Errno 22] Invalid argument
Failed to execute script gyb


#96 Combine dependencies & Re-configure npm scripts

Addresses #96
Description
Colocate client and server dependencies into the root folder and re-configure npm scripts.
Note:

To run client and server in one terminal you have to run npm run dev-concurrent
package.json is inside of both client and server folder is to allow developers to recognize what the scripts is doing and future-proofing for future refactor when necessary. It also enables developer to run the scripts as normal if they were to change directory into their respected folder.

Changes:

Removed unused dependencies & removed importing those unused dependencies (bcrypt, passport-local).
Re-configured scripts in the root folder
Added package.json in the server folder that solely contain npm scripts.
Refactored client package.json so that only npm scripts remain.
Fix incorrect path for API secrets

Breaking Changes:
The client production build folder fails to generate now that linter is correctly working.
How To Fix:

Automatically fix 90% of the linting errors with npm run lint:fix & npm run format. Then manually fix error that is remain.

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

Long day so I may have done something wrong.
Running npm run lint:fix and npm run format seems to work. After address the three manual errors, the run script breaks. I also cannot re-run lint
Also "dev-concurrent": "concurrently \"npm:watch-client\" \"npm:watch-server\"", may need to be changed to "dev-concurrent": "concurrently \"npm:watch-client\" \"npm:dev\"",

Long day so I may have done something wrong.
Running npm run lint:fix and npm run format seems to work. After address the three manual errors, the run script breaks. I also cannot re-run lint
Also "dev-concurrent": "concurrently \"npm:watch-client\" \"npm:watch-server\"", may need to be changed to "dev-concurrent": "concurrently \"npm:watch-client\" \"npm:dev\"",

The new commit in the PR fixes the scripts error. Tested the scripts at the root directory and inside of individual folder. Everything is working as expected.
Build folder successful generate after all the linting errors has been fixed. Should I make a new PR for that? (34 files modified after fixing linting errors)


Dockerfile: build arm64 variants

Closes https://github.com/cilium/pwru/issues/262

Make it possible to build both amd64 and arm64 Docker images. This can be done with:
docker build --platform linux/amd64,linux/arm64 --tag pwru  .

GHA release workflow only handles GH release artifacts, so the out-of-tree CI job or manual process used to publish images on Docker Hub will have to be updated accordingly.
Also, fix the release script used during image build to support cross-compilation of amd64 on arm64 machines.
(Note that a standalone Docker Engine has to be configured with the containerd snapshotter enabled to build multi-arch images. See https://docs.docker.com/engine/storage/containerd/)

Hm it seems I can't compile the amd64 image from my macbook, although it works properly on a Linux machine with a stock Docker Engine. I'll try to fix that.

@akerouanton I was informed by @aanm that Docker Hub, where we publish cilium/pwru images, does not support the multi-arch.

Docker Hub [...] does not support the multi-arch.

What do you mean @aanm? Docker Hub itself does support multi-arch images. For instance: https://hub.docker.com/r/albinkerouanton006/pwru/tags.

@brb @akerouanton what I meant was that hub.docker.com does not build multi-arch images but it's fine to publish.

@aanm I see. I think a build hook could do the job, but Cilium needs to have either a Docker Pro, Team, or Business subscription as is noted at the top of that doc page. Is that the case?

@aanm I see. I think a build hook could do the job, but Cilium needs to have either a Docker Pro, Team, or Business subscription as is noted at the top of that doc page. Is that the case?

@akerouanton no, that's not the case. All multi-arch builds that Cilium has are done via GitHub actions. For example here


[ADD ME TO THE ORGANIZATION]

Name: Shubham Patrick
Location: New Delhi
Interest: Design and Development
Discord username(optional):- ahthneeuhl
Why do you want to join?

I want to join because

You can also join our Discord community here
Feel free to check out other cool repositories of the Open Source Community here.

@AHTHneeuhl Thanks for your interest. Invitations have been sent to you. Kindly accept it and make your membership public.


Links should be displayed in Reminders

Reminders don’t display links (if they have one). Maybe they could show the link when I click on them.

🤔 yeah, should.

ok, that's actually a bug in Apple's api. I even left a couple of comments in the code a long time ago:

If you place your link in the reminder's Notes section, it works, because that's one of the places I check.
Perhaps with the new events+reminders integration in the next macOS, they end up fixing it.

ok, that's actually a bug in Apple's api. I even left a couple of comments in the code a long time ago:
If you place your link in the reminder's Notes section, it works, because that's one of the places I check.
Perhaps with the new events+reminders integration in the next macOS, they end up fixing it.

Have you reported this?

This bug is widely known, I found a bunch of issues open with no solution. Let's wait for the new macOS release and see if anything changes.

Does this bug still exists?

yes, if Apple fixes it, it should work automatically, because I'm trying to get the urls.

yes, if Apple fixes it, it should work automatically, because I'm trying to get the urls.

So It's not currently work.


Volume renderings are clipped in VR

Below is a screenshot generated using the CT-Cardio sample data. The volume rendering is clipping, where the controller, and the giant green sphere (which is a segment) are not.

@jbvimort Could you try to reproduce this ?

After investigating with @martinken, it looks like the issue is not specific to OpenVR. It can be reproduced in Slicer by enabling volume rendering and setting view angle to 130.
getNode("vtkMRMLCameraNode1").GetCamera().SetViewAngle(130)

We are noticing this as well.  Any update?

For reference, this is now tracked here: https://issues.slicer.org/view.php?id=4511

Thanks @sankhesh  for figuring things out :+1:

Yes, virtual reality works so well since the fix has been implemented!
Unfortunately, there is a small but in some use cases very distracting regression related to clipping - see details here: https://issues.slicer.org/view.php?id=4548. @sankhesh it would be great if you could have a look at it. Maybe it's a trivial fix.

@lassoan Sounds good. We can take a look to see if it is a quick fix.

Thank you! I've sent standalone example to Aashish that reproduces the problem using one of the VTK tests.


update signTx flow using marina.sendTransaction (psetv2)

This PR is not ready to be merged, it updates the lib using an open marina-provider PR: https://github.com/vulpemventures/marina-provider/pull/30 (not released yet). It aims to help you migrate to psetv2/new marina
We are updating Marina using psetv2 & new provider here: https://github.com/vulpemventures/marina/pull/436
Note that the new provider now returns psetv2 only, it's possible that some changes are needed in bitmatrix-app-ui
TL;DR

remove ldk from pkg.json -> we'll drop support and use only liquidjs-lib (maybe the file "ldk.ts" should be renamed)
bump liquidjs-lib & remove resolutions in pkg.json
rework signTx function using marina.sendTransaction API (marina will handle blinding, coinselection and broadcasting)

PS:

Marina, Wallet and IWallet seem to be a bit redondant: hard to get the difference between all of them at first read in my opinion.
any reason to do not commit the yarn.lock file ? I would commit it to ensure we are on the same page while developing.

We may need to update to latest deps

UPDATE
last commit bumps marina-provider to 3.0.1 (latest). The only change is the importScript method (not needed so not implemented in Wallet interface.
@afarukcali please review


Testing lock failed frequently due to API server unavailability

We are using Kured (currently version 1.4.4) on AKS-Engine cluster, K8s version 1.16.15.
The kured daemon-set restarts dozen of times and pod deletion / rollout restart doesn't help.
Looks like there are transient and frequent issues with API server availability, which causes TLS handshake timeouts.
we always get the same error message:
msg="Error testing lock: Get https://<IP_ADDRESS>:443/apis/apps/v1/namespaces/kube-system/daemonsets/kured: net/http: TLS handshake timeout"
It will be great to add some retries to requests related to API server.
And reduce the readiness/liveness sensitivity
similar issue #115 , opened new one since it's closed.

We have a similar issue:
Error testing lock: Get https://somedomain:443/apis/apps/v1/namespaces/kube-system/daemonsets/kured: dial tcp: i/o timeout
Killing the pod resolves the issue. Some retry logic would be awesome.

We have a similar issue:
Error testing lock: Get https://somedomain:443/apis/apps/v1/namespaces/kube-system/daemonsets/kured: dial tcp: i/o timeout
Killing the pod resolves the issue. Some retry logic would be awesome.


sample property in schema

Now there is a demo section, maybe this also could be part of it

Edits should be made to schema.d.ts, not to schema.json which is generated from it.
Also, I think we need more consideration around which types have samples attached to them, and what exactly should be in the sample. Is it all types. Is it code, prose, a link?
I would rather discuss this in an issue than a PR.


Feature request: Copy to clipboard as markdown with sources

Copy to clipboard is currently just raw text, and without any references/sources.
Adding an option to copy as markdown, similarly styled to the PDF generated, could make it significantly more useful and readable. Considering this is a "researcher", references is essential.

Thanks for the feedback @Xtrah! This is a feature and not a bug :)
Many users copy from the UI to some external document and therefore markdown will not be optimal.
If you'd like to get the full markdown report you can try out the package. See example here: https://github.com/assafelovic/gpt-researcher/blob/master/examples/sample_report.py
To install the package simply run pip install gpt-researcher


TerminalWithCode display

It could be nice to have the Terminal display also display the sniprun'd code along with the result.
Future discussion about the feature included in #123 can happen here, if the PR is merged into dev

@control13 I merged your PR with some improvement into master, soon to be v1.1.0
(including this Terminal/TerminalWithCode duplicated output if both key present, as well as un-indentation of the sniprun'd code bloc)
If you think this is good enough, feel free to close this issue (or let me know why otherwise)

It's nice and you were quite fast, too. We got it.

Oh, maybe it's because I was the one who created it... Nevermind then
Have a nice day and thanks for the contribution !


FEATURE: Bundle ADR Tools and expose as adr operation

Problem
Particularly relevent for the Docker distro, although a web site can be generated from a .dsl, any input architecture decisions must either be hand-written and managed, or relies on architect to have ADR Tools installed on the host machine. This latter approach departs from the Docker ethos of "everything needed is in the container".
Suggested solution
As ADR Tools is merely a set of shell scripts, there's no new dependencies to manage.  Depending on how the ENTRYPOINT vs CMD suggestion from #31 is handled, these scripts could either:

CMD: be installed and called directly via the host docker run command
ENTRYPOINT: be exposed via a new adr operation of this project, which delegates to the installed ADR Tools scripts.  This approach will bring consistency between both installed and Docker approaches, but require development & maintenance of this pass-through operation

Via either way, Docker distro users will be able to manage ADRs and generate websites via the same Docker image.
The only complication to address is that ADR Tools relies on an EDITOR environment variable to load a text editor / IDE. This assumes the script and editor are executing on the same host, which under this suggested approach, is false. However, owing to WSL2, it is possible for the Docker container's shell to start an independant process on the host. For example:
container> pwd
/var/model

container> code .

Presumably code will be stored in the EDITOR variable. And by WSL2 "magic" the host starts VS Code with the container's pwd open in context.  That is, any changes will appear to persist into the container, which in turn via the -v [host path]:/var/model mounting will realise as a change to the architect's source / input files.

I'm closing this issue. As stated in the README (since today), the intended use for the Docker image is for usage in CI pipelines. Using it for development is possible, but not an actively supported use case.


foreach() argument must be of type array|object, null given

When I call $this->client->list()->players($team->idTeam); I am getting an exception with the above error message. I see a related issue, but I'm still getting this message for 1.0.2. I'm able to catch for my use case but thought you would want to know. I believe the team just does not have any players listed.

Thanks,

Hey Clark,
thanks for opening this issue. You are right, list()->players(id) should not throw an exception if there are no team members.
Could you tell me which ID you used? Thanks in advance.

Fixed by #24


Max Profit with k transactions (DP)  | C++

Max Profit with k transactions (DP) -
what will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

I like to work on this issue

I will raise PR in this account. I mistakenly logged in from other account. Extremely sorry for this

please assign this to me i can solve this as soon as possible
thank you


Tool crashes if no complexes can be annotated

calc_biological_precision crashes in benchmark run if no complexes are annotated (e.g. if no annotations are stored for this organism; line 2221)
TODO: Go through functions relying on complex annotation and catch that case.

This now raises an error at single file analysis.


Overhaul the ToC

We'd like to overhaul the ToC for the website. This includes

[x] Make the left hand nav collapsable
[x] Add "mini ToCs" for complex pages
[x] Rearrange the ToC
[ ] Merge disparate sections and remove duplication (Tour/Reference)
[ ] Turn the Quickstart into a more "hands on tutorial," with a Tour-like style

Should we close this in favor of https://github.com/pulumi/docs/issues/831?

Will look at this as we overhaul the current architecture next sprint.

https://github.com/pulumi/docs/issues/831


Impossible to remove pre-commit hook?

Hi there,
I changed a pre-commit hook to run on pre-push, ran cghooks update, but now the hook always runs on pre-commit..
All traces of pre-commit have been removed (composer.json, cghooks.lock) yet it still runs, even when opening new terminals.
I'm out of options at this point except composer removing the dependency

@webketje you can look into your githooks folder which should be .git/hooks if you haven't changed it. Then you can remove the hooks by deleting the file

@BrainMaestro thanks, that was it.. However, isn't it a reasonable expectation that this would be handled by cghooks update automatically?


[Weak supervision] Update Weasel example with new merged support for HF

I would even recommend moving this to its own tutorial (a short one) or to the AG News tutorial (less preferred).
What do you think @dcfidalgo ?

Yes, the update of the guide is on my to-do list. Yes, I think turning this part of the guide into a small tutorial would be a nice addition to the docs.

Actually, if possible I'd like to have a code snippet (or the guide updated) with the new usage to share this before the tutorial.


Feature/multi secretary

Allows for multiple users in the 'Secretaris' group. They can edit and view each-others reviews and decisions. It's hacky, but it works (I believe).
Implemented as an additional group for the primary secretary (please suggest a better name if you can think of it). This is much simpler than making an additional group for extra secretaries, as most infrastructure remains intact.
Additionally overwrites the get_secretary() email field by the general email address.

I haven't pulled and tested it myself yet, I'll do that after this comment.
I do have a general question first about the secretary mail override:
This will also make most mails go to the fetc e-mail instead of the personal e-mail. Does Desiree know about this change? I can imagine it's actually preferable this way, but in my experience this should be announced beforehand.

Seems to work! Once the two questions I had are adressed it can be merged in my opinion :)

I haven't pulled and tested it myself yet, I'll do that after this comment.
I do have a general question first about the secretary mail override:
This will also make most mails go to the fetc e-mail instead of the personal e-mail. Does Desiree know about this change? I can imagine it's actually preferable this way, but in my experience this should be announced beforehand.

Good that you checked that, this was indeed requested by Desiree.


march not passing correctly for docker-compose run

Building on the new ASUS Tinker Edge T, running Mendel Linux 4.0 (Day). docker-compose build commands work fine with no errors:
DEBIAN=10 ARCH=arm64v8 docker-compose build debian-cpp && DEBIAN=10 ARCH=arm64v8 docker-compose build debian-python
DEBIAN=10 ARCH=arm64v8 docker-compose run debian-python - fails with the following:
-- Running cmake for pyarrow
cmake -DPYTHON_EXECUTABLE=/usr/local/bin/python  -G Ninja -DPYARROW_BUILD_CUDA=off -DPYARROW_BUILD_FLIGHT=on -DPYARROW_BUILD_GANDIVA=on -DPYARROW_BUILD_DATASET=on -DPYARROW_BUILD_ORC=on -DPYARROW_BUILD_PARQUET=on -DPYARROW_BUILD_PLASMA=on -DPYARROW_BUILD_S3=off -DPYARROW_BUILD_HDFS=off -DPYARROW_USE_TENSORFLOW=off -DPYARROW_BUNDLE_ARROW_CPP=off -DPYARROW_BUNDLE_BOOST=off -DPYARROW_GENERATE_COVERAGE=off -DPYARROW_BOOST_USE_SHARED=on -DPYARROW_PARQUET_USE_SHARED=on -DCMAKE_BUILD_TYPE=debug /arrow/python
-- The C compiler identification is GNU 8.3.0
-- The CXX compiler identification is GNU 8.3.0
-- Check for working C compiler: /usr/lib/ccache/gcc
-- Check for working C compiler: /usr/lib/ccache/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/lib/ccache/g++
-- Check for working CXX compiler: /usr/lib/ccache/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- System processor: aarch64
-- Performing Test CXX_SUPPORTS_ARMV8_ARCH
-- Performing Test CXX_SUPPORTS_ARMV8_ARCH - Failed
-- Arrow build warning level: PRODUCTION
CMake Error at cmake_modules/SetupCxxFlags.cmake:338 (message):
Unsupported arch flag: -march=.
Call Stack (most recent call first):
CMakeLists.txt:100 (include)
-- Configuring incomplete, errors occurred!
See also "/build/python/temp.linux-aarch64-3.7/CMakeFiles/CMakeOutput.log".
See also "/build/python/temp.linux-aarch64-3.7/CMakeFiles/CMakeError.log".
error: command 'cmake' failed with exit status 1

Would you mind opening a JIRA issue?

Done. Thank you.
https://issues.apache.org/jira/browse/ARROW-8992


Intro panel

thanks so much that was so fast!! we changed the font/spacing so it should be good to go but lmk if you think of any other feedback


Custom theme

Hello there,
It's possible to add custom themes? I find too dark the default dark theme, or maybe transparent background could be a solution?

There is youtube video link in Blockman page. It's an instruction for advanced coloring. Please see it first and then you can ask any additional questions.

Thanks for answer, I'll check that


Implementation of eval()

Hi,
I cannot find the implementation of function eval():
eval(args.model_name)
Can you give me some reference to the related code?

eval is the built-in function of python :)


Error - Index was outside the bounds of the array.

After uninstalling and unpublishing all extentions, an publishing the extention below ...

... I'm no longer able to use the Customer list / card.

Here's an extract of the even viewer:
Type: System.IndexOutOfRangeException
Message: Index was outside the bounds of the array.
StackTrace:
at Microsoft.Dynamics.Nav.Runtime.MutableRecordBuffer.get_Item(Int32 index)
at Microsoft.Dynamics.Nav.Runtime.RecordImplementation.GetFieldValue(NCLMetaField field)
at Microsoft.Dynamics.Nav.Runtime.NavRecord.GetFieldValue(NCLMetaField metaField)
at Microsoft.Dynamics.Nav.Service.NSRecordBase.SetCLRCellFromTableField(NsDataAccess recDataAccess, NCLMetaField metaField, Int32 fieldIndex, NavDataRow dataRow)
at Microsoft.Dynamics.Nav.Service.NSRecordBase.PopulateCLRTable(NavDataTable dataTable, NsDataAccess recDataAccess, NavDataRow dataRow)
at Microsoft.Dynamics.Nav.Service.NSPage.PopulateOneRow(NsDataAccess recDataAccess, NavDataTable dataTable)
at Microsoft.Dynamics.Nav.Service.NSPage.PopulateSpecificPage(NavDataSet dataSet, NsDataAccess recDataAccess, Boolean& moreDataInReadDirection, Boolean& moreDataInOppositeDirection)
at Microsoft.Dynamics.Nav.Service.NSPage.PopulateCLRDataSet(NavDataSet dataSet, NsDataAccess recDataAccess, Boolean& moreDataInReadDirection, Boolean& moreDataInOppositeDirection)
at Microsoft.Dynamics.Nav.Service.NSPage.GetPageData(NavSession session)
at Microsoft.Dynamics.Nav.Service.NSPage.GetPage(NavSession session)
at Microsoft.Dynamics.Nav.Service.NSService.Microsoft.Dynamics.Nav.Types.INavService.GetPage(PageRequestDefinition pageRequestDefinition, NavRecordState state)
at SyncInvokeGetPage(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.RunInTransactionCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass23_0.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.TransientErrorRetryCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.<>c__DisplayClass23_0.b__1(NSServiceBase serviceInstance, Object[] inputs, Object[]& outputs)
at Microsoft.Dynamics.Nav.Service.ServiceOperationInvoker.ErrorMappingCombinator(ServiceOperation innerOperation, NSServiceBase serviceInstance, MethodBase syncMethod, Object[] inputs, Object[]& outputs)
Source: Microsoft.Dynamics.Nav.Ncl
HResult: -2146233080

@StanislawStempin Any ideas / hints what might have caused the issue? Have you been able to reproduce the same? I'm currently stuck in publishing new extentions, most of them result in the same error.

We cannot reproduce the issue on the latest bits. Can you share in more details what steps you followed? Have you had deployment errors prior to this one? Have you used the in-client Designer to create some extensions? Have you published the same extension multiple times but with changed app.json values like version, name or publisher?
Also, could you share the contents of your Nav App and Nav App Dependencies tables?
In terms of a workaround it looks like you would need to start with a fresh VM unfortunately.

As far as I remember, I'd created a fresh VM, made a Customer table extension with 20 text[250] fields, added a second Customer table extension with 20 additional text[250] fields (to check if any record size limits still apply), and then the problems arose.
Will try setting up a new VM and reproduce the above steps.

Did you create a table in your extension with ID 70050001?
Two customer table extensions?  Is that supported?

We identified one of the root causes of this issue to be stale data cache. If you are still experiencing it we might have a workaround. Could you please try adding the following codeunit to your project and deploy it:
codeunit 70000001 ClearCaches
{
    [EventSubscriber(ObjectType::Codeunit, 1, 'OnAfterCompanyOpen', '', false, false)]
    procedure Clear();
    begin
        SelectLatestVersion;
    end;
}

The problem seems to be caused by 2 separate extensions each extending the same 'Customer' table. I was able to reproduce the issue using these steps:

Creating a first project and publishing the below extension works:

tableextension 70050000 MyCustomer extends Customer
{
fields
{
// Add changes to table fields here
field(50000;Description2;Text[250])
{
}
}
}

pageextension 70050001 MyCustomerLisExtension extends "Customer List"
{
layout
{
// Add changes to page layout here
addlast(Control1)
{
field(Description2;Description2)
{
}
}
}
}`

Create a second project with following code, makes the webclient crash (and returns an IndexOutOfRangeException)

tableextension 70050002 MyCustomer2 extends Customer
{
fields
{
// Add changes to table fields here
field(50002;Description3;Text[250])
{
}
}
}`


Issue with Footprint Generation Using ORFD Dataset and PyICP-SLAM

Thank you for sharing your great research.
I encountered an issue while trying to generate the footprint using the ORFD dataset. I used PyICP-SLAM to estimate the poses and followed the preprocessing code provided for the ORFD dataset. However, I was unable to generate the footprint.
I suspect the issue might be due to the accuracy of the pose data obtained from PyICP-SLAM.
I’m wondering if you have experienced a similar problem.

As you mentioned, the results of PyICP-SLAM were not very accurate. Therefore, it was necessary to manually validate the generated footprints and filter out the usable data.

Close this issue.

Sorry for the delayed response. It seems like your answer will be helpful.
By the way, if you have the pose information from ORFD used in the research, could you share it with me?


chromium: 88.0.4324.146 -> 88.0.4324.150

https://chromereleases.googleblog.com/2021/02/stable-channel-update-for-desktop_4.html
This update includes 1 security fix. Google is aware of reports that an
exploit for CVE-2021-21148 exists in the wild.
CVEs: CVE-2021-21148

Motivation for this change
cc @danielfullmer
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Backported to 20.09 in 22a2b332378b99461edeaf9754dc2d6b4a210148.


wont checkout on windows because of naming *

$ git clone https://github.com/brycedrennan/imaginAIry.git
Cloning into 'imaginAIry'...
remote: Enumerating objects: 2670, done.
remote: Counting objects: 100% (321/321), done.
remote: Compressing objects: 100% (135/135), done.
remote: Total 2670 (delta 193), reused 280 (delta 186), pack-reused 2349
Receiving objects: 100% (2670/2670), 177.21 MiB | 29.81 MiB/s, done.
Resolving deltas: 100% (1526/1526), done.
error: invalid path 'tests/expected_output/test_clip_masking__mask*0.5_bin.png'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

good to know. will fix

fixed


cache_dir not working

What system are you running Yazi on?
Linux X11
What terminal are you running Yazi in?
kitty v0.36.4
yazi --debug output
Yazi
    Version: 0.3.3 (af565fb 2024-11-18)
    Debug  : false
    Triple : x86_64-unknown-linux-gnu (linux-x86_64)
    Rustc  : 1.82.0 (f6e511ee 2024-10-15)

Ya
    Version: 0.3.3 (VERGEN_IDEMPOTENT_OUTPUT 2024-10-09)

Emulator
    Emulator.via_env: ("xterm-kitty", "")
    Emulator.via_csi: Ok(Kitty)
    Emulator.detect : Kitty

Adapter
    Adapter.matches: Kgp

Desktop
    XDG_SESSION_TYPE           : Some("tty")
    WAYLAND_DISPLAY            : None
    DISPLAY                    : Some(":0")
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL           : Some("/bin/nu")
    EDITOR          : Some("/usr/bin/hx")
    VISUAL          : None
    YAZI_FILE_ONE   : None
    YAZI_CONFIG_HOME: None
    YAZI_ZOXIDE_OPTS: None
    FZF_DEFAULT_OPTS: None

Text Opener
    default     : Some(Opener { run: "hx \"$@\"", block: true, orphan: false, desc: "hx", for_: None, spread: true })
    block-create: Some(Opener { run: "hx \"$@\"", block: true, orphan: false, desc: "hx", for_: None, spread: true })
    block-rename: Some(Opener { run: "hx \"$@\"", block: true, orphan: false, desc: "hx", for_: None, spread: true })

Multiplexers
    TMUX               : false
    tmux version       : No such file or directory (os error 2)
    tmux build flags   : enable-sixel=Unknown
    ZELLIJ_SESSION_NAME: None
    Zellij version     : No such file or directory (os error 2)

Dependencies
    file             : 5.45
    ueberzugpp       : No such file or directory (os error 2)
    ffmpegthumbnailer: 2.2.2
    pdftoppm         : 24.08.0
    magick           : 7.1.1-38
    fzf              : 0.55.0
    fd               : 10.2.0
    fdfind           : No such file or directory (os error 2)
    rg               : 14.1.1
    chafa            : No such file or directory (os error 2)
    zoxide           : 0.9.6
    7z               : No such file or directory (os error 2)
    7zz              : 24.08
    jq               : No such file or directory (os error 2)

Clipboard
    wl-copy/paste: 2.2.1 / 2.2.1
    xclip        : No such file or directory (os error 2)
    xsel         : No such file or directory (os error 2)

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

Describe the bug
I have three drives in my system: my root drive, a hard drive, and an ssd. I have set the cache_dir to a directory on my ssd and when I load images on my hard drive they show up in that directory, so I know that it's working correctly. However, when I reboot, the cached images remain but when I load their counterparts on my hard drive it's as if they were never cached.
Minimal reproducer
Due to the nature of this issue, I'm not sure what to put here. I suppose you could reproduce the issue if you have a setup similar to mine: the media being on one drive and the cache_dir on another, with neither of them being the root drive.
Anything else?
No response
Validations

[X] I tried the latest nightly build, and the issue is still reproducible
[X] I updated the debug information (yazi --debug) input box to the nightly that I tried
[X] I can reproduce it after disabling all custom configs/plugins (mv ~/.config/yazi ~/.config/yazi-backup)

I can't reproduce it.
Yazi uses file's path and mtime as the unique id for caching:
https://github.com/sxyazi/yazi/blob/6a4f6aa99f1c9422af68b8f5ea93082e84c12a9a/yazi-plugin/src/utils/cache.rs#L16-L22
Are you sure the mtime of your files hasn't changed?

Yes. The files haven't been edited since they've been written to the disk. I have

oops, didn't mean to close it. sorry.

I checked the mtime, checked the name of the files in my cache_dir, rebooted to see if the problem persisted (it did), deleted the files in my cache_dir, rebooted, recached the images (same names), rebooted, and the problem persisted. If you have any ideas or want anything from me then I'll be happy to provide.

Is it only happening with images? Does the issue also occur with videos or PDFs? Does it happen on a specific drive or all drives? Is that drive an external one? If it is, Windows seems to rename them based on the order they’re connected (D, E, F, etc.), which could be causing the filenames to keep changing.

I've only tested it with images and videos and it happens with all of them. It happens on every drive. All drives are internal. I'm running gentoo linux.

Please apply this patch, then send your yazi.log file:
diff --git yazi-plugin/src/utils/cache.rs yazi-plugin/src/utils/cache.rs
index 8d2155764ab7ae61d6a039cba913195b3868d158..8ce16409a4caf0292dd1e1f4ad19713ed66cebb1 100644
--- yazi-plugin/src/utils/cache.rs
+++ yazi-plugin/src/utils/cache.rs
@@ -19,6 +19,14 @@ impl Utils {
 				format!("{:x}", digest.finalize())
 			};

+			tracing::error!(
+				"file_cache: url={}, mtime={:?}, skip={}, hex={}",
+				file.url.to_string_lossy(),
+				file.cha.mtime,
+				t.raw_get("skip").unwrap_or(0),
+				hex
+			);
+
 			Some(Url::cast(lua, PREVIEW.cache_dir.join(hex))).transpose()
 		})
 	}

I cloned the latest git, compiled with the patch, cached the same videos, and the files and sums are the same as they were before. The names of the cached files are identical.
To be clear, when I cache a file and the go back to it in the same session everything works as it should. It's when I reboot and try to load those files again that things go wrong, so the system is clearly recognizing everything.

It's when I reboot and try to load those files again that things go wrong

Is the info still identical after the reboot? If not, what information has changed? Can you compare the differences between before and after the reboot in the log?

After reboot is identical, though there are more entries that are identical to each other. If you really want to get specific I can set up the cache_dir to be on my root drive, cache pictures and videos that are also on my root drive, then share every log at every step of the way (before and after reboots and changes).
Since you know how yazi works I don't know if that's necessary, but if it is then let me know and I'll get you all of that information and whatever else you need.

Just to be clear, all of this is being done with yazi's latest git and the patch you gave.

I'm confused. You mean the same info generates a different MD5?


bugfix: return error when the url is unreachable

Signed-off-by: Starnop<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
The supernode will success to register the task even though when dfget try to download an 404 URL. It‘s not make sense.
Ⅱ. Does this pull request fix one issue?

None.
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #739 into master will increase coverage by 0.47%.
The diff coverage is 53.84%.

@@            Coverage Diff             @@
##           master     #739      +/-   ##
==========================================
+ Coverage   46.85%   47.33%   +0.47%
==========================================
  Files         110      109       -1
  Lines        6321     6317       -4
==========================================
+ Hits         2962     2990      +28
+ Misses       3125     3091      -34
- Partials      234      236       +2

Impacted Files
Coverage Δ

supernode/server/result_info.go
0% <0%> (ø)
:arrow_up:

supernode/daemon/mgr/task/manager.go
20.87% <100%> (+0.87%)
:arrow_up:

dfget/core/regist/register.go
97.75% <100%> (+0.02%)
:arrow_up:

supernode/daemon/mgr/task/manager_util.go
27% <23.07%> (-0.54%)
:arrow_down:

supernode/server/metrics.go
100% <0%> (ø)
:arrow_up:

common/util/metrics_util.go

Continue to review full report at Codecov.

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


Unable to update jail since version 3.2.1

When I tried updating my jail to 11.1-RELEASE-p5 this morning I got the following error:

[00:00:00] Upgrading using ftp
/etc/resolv.conf -> /usr/local/poudriere/jails/freebsd_11-1x64/etc/resolv.conf
env: /usr/sbin/freebsd-update.fixed: No such file or directory
11.1-RELEASE-p5
[00:00:00] Recording filesystem state for clean... done

After downgrading poudriere from my package cache to 3.2.0 it worked again.

Same problem with poudriere-devel <IP_ADDRESS>71127.

3.2.2 released with fix.


Add removeEventListener method to DomMixin

I had the need to remove an event listener during the active lifecycle of a component. This can happen especially for high volume events like scroll or mousemove, where you maybe want to listen to them conditionally, not all the time.
This adds the matching removeEventListener method to the DomMixin.
Added a test just for one simple case (with and without the passive flag), not all the different cases you have provided for addEventListener. Not sure if that makes sense to duplicate all of them also for removeEventListener? If you want me to do that, just tell me!

@rwjblue had a chance to look at this?

Awesome! I'll try to release in the AM (I'm in computer free time for the night 😎).

ping @rwjblue. Can we get a new release with this?

Released in 1.0.4


Pack stage fails for all jobs

Might have been a GitHub Actions temporary problem. I have pushed today 3 commits and they were all fine, see https://github.com/cristianadam/HelloWorld/actions/


Add method for visualizing TSR

Add a method which samples a TSR and draws axes in the environment at the samples.

This is almost working pseudocode based on my TSR viewer.
https://gist.github.com/psigen/f378064818577ab9309b

This was added by @jeking04 in 088b1e7443f596f7780877fca245e3cc9a45422a.


Can not find a way of setting auth setting on WebApp

It looks like there is no way of setting the Auth Setting on the WebApp in the new azure provider. I have only checked the C# version of it, but the only result that come close is the ListWebAppAuthSettings.
Is there another way of setting it, or is there something missing? Link to MS ARM template documentation for auth config https://docs.microsoft.com/en-us/azure/templates/microsoft.web/2020-06-01/sites/config-authsettings

Hi @nicro950 thanks for reporting this.
Indeed, it looks like we don't expose the auth settings. The reason is the Auth Settings are not a "resource" in Pulumi's notion: it's a separate PUT endpoint without corresponding GET or DELETE methods.
We'll have a look at whether it's possible to extend our resource model to this kind of resources.

Thank you for the explanation, we are using auth settings for a lot of our azure apis and azure functions which means we have to continue using the Pulumi.Azure provider for creating app services at least.

Sure. Remember that you can use both providers side-by-side in the same program too.

Another related resource with the same model is Metadata in https://github.com/Azure/azure-rest-api-specs/blob/0955eca8c1288aa8220aab34db3a66bdb6ac98cc/specification/web/resource-manager/Microsoft.Web/stable/2020-09-01/WebApps.json#L1691

Another related resource with the same model is Metadata in https://github.com/Azure/azure-rest-api-specs/blob/0955eca8c1288aa8220aab34db3a66bdb6ac98cc/specification/web/resource-manager/Microsoft.Web/stable/2020-09-01/WebApps.json#L1691

These resources will ship in 0.6.0


Upgrade Psalm to 5.22

Fixes a range of Risky comparisons where possible and expands baseline for issues that are too risky to fix.
Should get CI green again with latest deps
Closes #226

Q
A

Documentation
yes

QA
yes

Thanks @gsteel!

Thanks for reviewing @Ocramius :)


CognitoYourUserPoolsSample does not persist user?

Do I manually have to store the password in the keychain then log the user in behind the scenes overtime the app runs? Or is there no built in way that caches this for me?
I find I have to log in again every time I run the code.

As long as you don't sign out, the sample will authenticate the last logged in user without prompting for a password.  You should only be prompted for a password if you sign out or your refresh token expires which by default is 30 days since you last supplied your username/password.

@behrooziAWS right, seems this only work if running on the device. I was testing in the simulator with Xcode-beta running iOS10 and Swift 3, in which case it doesn't work.


Segmentation fault when attempting to update crates.io index on WSL

Problem
I have been developing a rust application under the Windows Subsystem for Linux. I recently added a dependency on the md5 crate.
Upon trying to build, cargo will attempt to update the crates.io index and immediately segfault.
Steps

Make a new directory cargo_test
cargo init
add md5 = "0.7.0" to the dependencies section of Cargo.toml
cargo run
the following error will appear:

    Updating crates.io index
[1]    4269 segmentation fault (core dumped)  cargo run

Possible Solution(s)
No response
Notes
This error occurs specifically with WSL Debian. and I have not experienced the same issue on standard versions of Debian not installed through WSL.
Version
cargo 1.42.1
release: 1.42.1

Oh something I forgot to add:
While researching possible fixes, I did attempt to debug using lldb as suggested in other old issues similar to this one. However it completely stalls out and never reaches the segmentation fault, so I have not been able to get a backtrace at this time.

1.42.1 is quite an old release.  How did you install Rust? Can you try with the latest stable or nightly version?

Uninstalling the package from debian's repository and installing instead through rustup resolved the problem.
Thank you for the advice.


Switch search page icon to something relevant

Currently beside the search header is the icon we use to represent tools. This should be something more relevant, like a magnifying glass.

We have an icon which can be used in the Navbar, however it is too low res to work as a page icon.

Turns out bootstrap glyphicons are a good alternative


promote LocalStorageCapacityIsolationFSQuotaMonitoring to beta

Update due to https://github.com/kubernetes/kubernetes/pull/107329 and https://github.com/kubernetes/enhancements/pull/2697

There are some descriptions before.
https://people.wikimedia.org/~jayme/k8s-docs/v1.16/docs/concepts/configuration/manage-compute-resources-container/

When local ephemeral storage is used, it is monitored on an ongoing basis by the kubelet. The monitoring is performed by scanning each emptyDir volume, log directories, and writable layers on a periodic basis. Starting with Kubernetes 1.15, emptyDir volumes (but not log directories or writable layers) may, at the cluster operator’s option, be managed by use of project quotas. Project quotas were originally implemented in XFS, and have more recently been ported to ext4fs. Project quotas can be used for both monitoring and enforcement; as of Kubernetes 1.16, they are available as alpha functionality for monitoring only.
Quotas are faster and more accurate than directory scanning. When a directory is assigned to a project, all files created under a directory are created in that project, and the kernel merely has to keep track of how many blocks are in use by files in that project. If a file is created and deleted, but with an open file descriptor, it continues to consume space. This space will be tracked by the quota, but will not be seen by a directory scan.
Kubernetes uses project IDs starting from 1048576. The IDs in use are registered in /etc/projects and /etc/projid. If project IDs in this range are used for other purposes on the system, those project IDs must be registered in /etc/projects and /etc/projid to prevent Kubernetes from using them.
To enable use of project quotas, the cluster operator must do the following:
Enable the LocalStorageCapacityIsolationFSQuotaMonitoring=true feature gate in the kubelet configuration. This defaults to false in Kubernetes 1.16, so must be explicitly set to true.
Ensure that the root partition (or optional runtime partition) is built with project quotas enabled. All XFS filesystems support project quotas, but ext4 filesystems must be built specially.
Ensure that the root partition (or optional runtime partition) is mounted with project quotas enabled.

But I cannot find them in master branch.

/milestone 1.25
/assign @sethmccombs
/cc @kcmartin

@pacoxu @xing-yang
Please see Tim's comment

Do we also need an update to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#local-ephemeral-storage or to some page within https://kubernetes.io/docs/concepts/storage/?

eod tomorrow, August 9th, is the 1.25 Docs Ready for Review deadline
Please make any documentation updates associated with LocalStorageCapacityIsolationFSQuotaMonitoring to beta by eod tomorrow

Do we also need an update to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#local-ephemeral-storage or to some page within https://kubernetes.io/docs/concepts/storage/?

Updated. Thanks.

@sftim do you have time to take a look again? Thanks.

/lgtm

/approve

Rebased. @reylejano ack.


fix: bug report yaml parsing Yes as Boolean

Closes: #

[ ] Docs
[ ] Tests

Testing Strategy:

Oups, thank you for picking this up @xHomu 🙌


VSCode hangs randomly while idling

VSCode Version: 1.10.2
OS Version: Ubuntu 16.04.2 LTS

Steps to Reproduce:

Launch VSCode and have some files in the file tree and some open in tabs.
Wait between 1 minute and 1 hour.  Editing files is not required.  User input is not required.
VSCode hangs.  Requires kill -9 of session leader PID and a restart of code.

This has been happening since 1.8 or so, but it's become much more frequent with 1.9 and 1.10.  Basically VSCode ALWAYS hangs.  It's just a matter of time.  100% reproducible.
I unloaded all my extensions but the hangs persist.  Not extension related.  Also doesn't seem related to the number of files in the file tree.  (large tree of ~4000 files and small directory with 10 files both lead to hangs)
I'm not sure which process is hanging or how to get a call stack of the hang.  Please advise and I can provide more info.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

Yes, I downloaded the insiders build and the issue is still present.  It seemed less willing to hang while idling.  But I opened a few python files and it hung while I was editing them.

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

As mentioned in the original post, I disabled extensions to insure they were not the cause.  I used the UI originally.  I re-tested with "--disable-extensions" and it still hangs.  Definitely a bug in the editor not the extensions.  Sometimes it hangs within 5 minutes, sometimes it take a little longer.

@mdeter how about running code --disable-gpu?

--disable-gpu doesn't help.

@mdeter does it still reproduce? does it happen with any file you open?

Yes, this bug is still present in 12.1.  It doesn't seem to matter what kind of file I work on, although I am mostly editing C and Python files.  The source tree is very large (75k files).  Maybe that has something to do with it?  It's odd, because sometimes it will hang very soon after opening (within an hour) and other times it will last the whole day (8-10 hours) without hanging.  But unless I close it myself, it will eventually hang given enough time.

I am using 1.12.2 now and have not seen the hang so far.  Too early to close this, but I will check back in a while longer with another update.  crosses fingers

Defect still present.  3 hangs today alone, all within an hour of launching.  (One time the window didn't even finish initial startup painting before it hung.)  Version 1.12.2 with all plugins disabled.  I now wrote a script which kill -9's the hung process and restarts code because it happens so often.  :(

Here is a checklist to find out more about the freeze/slow/crash

[ ] it reproduces with extensions disabled (code --disable-extensions from the command line - NOT the integrated terminal of Code)

if it does not reproduce with extensions disabled, you can stop testing and report this!

[ ] it was not happening in the previous stable release
[ ] it reproduces in insiders builds (get it from here)
[ ] there is no suspicious output when running from the command line (code --verbose)
[ ] there is no suspicious output in the window itself (Help | Toggle Developer Tools | Console)
[ ] it reproduces on Windows, Linux and Mac
[ ] it reproduces after deleting <appdata>/User/keybindings.json and <appdata>/User/settings.json (backup first! see below for paths)
[ ] it reproduces when opening empty (code -n from the command line)
[ ] it reproduces opening any folder
[ ] it reproduces opening any file
[ ] it reproduces when only having a single window open
[ ] it reproduces by just using Code without external tools running on the same folder
[ ] it reproduces from a workspace that is not under Git version control
[ ] it reproduces independently if a file is opened or not after startup
[ ] it reproduces when running with GPU disabled (code --disable-gpu)
[ ] it reproduces when being offline
[ ] it reproduces when disabling the file watching (set files.watcherExclude to "**/**": true)
[ ] it reproduces after uninstalling and reinstalling
[ ] it reproduces after deleting the application data directory (backup first! see below for paths)
[ ] I have not played around with permissions or ran Code as administrator
[ ] I am seeing a single CPU process spin high (please share the full command line arguments)
[ ] I am seeing Code consuming lots of memory in a short time

Application Data Directory for VS Code:

Windows: C:\Users\<user>\AppData\Roaming\Code
Mac: /Users/<user>/Library/Application Support/Code
Linux: /home/<user>/.config/Code

Application Data Directory for VS Code Insiders:

Windows: C:\Users\<user>\AppData\Roaming\Code - Insiders
Mac: /Users/<user>/Library/Application Support/Code - Insiders
Linux: /home/<user>/.config/Code - Insiders


Add ability to use Docker Dev Container locally

Summary

Adds ability to run npm commands locally on a Docker container using VScode devcontainers setup

MPAGESCORE-88019
Thank you for contributing to Terra.
@cerner/terra

Failing build is an existing issue and is not related to code changes in this PR.


CVE-2007-4559 Patch

Patching CVE-2007-4559
Hi, we are security researchers from the Advanced Research Center at Trellix. We have began a campaign to patch a widespread bug named CVE-2007-4559. CVE-2007-4559 is a 15 year old bug in the Python tarfile package. By using extract() or extractall() on a tarfile object without sanitizing input, a maliciously crafted .tar file could perform a directory path traversal attack. We found at least one unsantized extractall() in your codebase and are providing a patch for you via pull request. The patch essentially checks to see if all tarfile members will be extracted safely and throws an exception otherwise. We encourage you to use this patch or your own solution to secure against CVE-2007-4559. Further technical information about the vulnerability can be found in this blog.
If you have further questions you may contact us through this projects lead researcher Kasimir Schulz.

Hi all.
I would like to appreciate you for your comment on the bug named
CVE-2007-4559 https://github.com/advisories/GHSA-gw9q-c7gh-j9vm.
CVE-2007-4559 https://github.com/advisories/GHSA-gw9q-c7gh-j9vm.
Thank you.
2022年10月1日(土) 15:42 TrellixVulnTeam @.***>:

Patching CVE-2007-4559 https://github.com/advisories/GHSA-gw9q-c7gh-j9vm
Hi, we are security researchers from the Advanced Research Center at
Trellix https://www.trellix.com. We have began a campaign to patch a
widespread bug named CVE-2007-4559
https://github.com/advisories/GHSA-gw9q-c7gh-j9vm. CVE-2007-4559
https://github.com/advisories/GHSA-gw9q-c7gh-j9vm is a 15 year old bug
in the Python tarfile package. By using extract() or extractall() on a
tarfile object without sanitizing input, a maliciously crafted .tar file
could perform a directory path traversal attack. We found at least one
unsantized extractall() in your codebase and are providing a patch for you
via pull request. The patch essentially checks to see if all tarfile
members will be extracted safely and throws an exception otherwise. We
encourage you to use this patch or your own solution to secure against
CVE-2007-4559 https://github.com/advisories/GHSA-gw9q-c7gh-j9vm.
Further technical information about the vulnerability can be found in this
blog
https://www.trellix.com/en-us/about/newsroom/stories/research/tarfile-exploiting-the-world.html
.
If you have further questions you may contact us through this projects
lead researcher Kasimir Schulz @.***>.
You can view, comment on, or merge this pull request online at:
https://github.com/atlan-antillia/EfficientDet-Slightly-Realistic-Japanese-RoadSigns-90classes/pull/1
Commit Summary

2e9921f
https://github.com/atlan-antillia/EfficientDet-Slightly-Realistic-Japanese-RoadSigns-90classes/pull/1/commits/2e9921f66d212d366ac8f9961978763c9d595117
Adding tarfile member sanitization to extractall()

File Changes
(2 files
https://github.com/atlan-antillia/EfficientDet-Slightly-Realistic-Japanese-RoadSigns-90classes/pull/1/files
)

M DownloadCkpt.py
https://github.com/atlan-antillia/EfficientDet-Slightly-Realistic-Japanese-RoadSigns-90classes/pull/1/files#diff-13b7476483de678436d1d85aa223f7991b41645b3b2e77fd01889240e95771dc
(21)
M DownloadCkpt_d0.py
https://github.com/atlan-antillia/EfficientDet-Slightly-Realistic-Japanese-RoadSigns-90classes/pull/1/files#diff-dfedb8b06f36c606f77b28def3e8981de7da2f2bb9481ca6eb2718d1659bcb39
(21)

Patch Links:

https://github.com/atlan-antillia/EfficientDet-Slightly-Realistic-Japanese-RoadSigns-90classes/pull/1.patch
https://github.com/atlan-antillia/EfficientDet-Slightly-Realistic-Japanese-RoadSigns-90classes/pull/1.diff
—
Reply to this email directly, view it on GitHub
https://github.com/atlan-antillia/EfficientDet-Slightly-Realistic-Japanese-RoadSigns-90classes/pull/1,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALPI2IJH22NUNZMVU7QCACDWA7MNPANCNFSM6AAAAAAQ2KDSH4
.
You are receiving this because you are subscribed to this thread.Message
ID:
<atlan-antillia/EfficientDet-Slightly-Realistic-Japanese-RoadSigns-90classes/pull/1
@github.com>


There is no audit.k8s.io/v1 API group

It would be great to have audit.k8s.io/v1 group in MicroK8s to configure requests\response logging policy.

Hi @adubkov,
You can enable auditing following the instructions in [1]. The arguments to the API server go in /var/snap/microk8s/current/args/kube-apiserver. For the new arguments to take effect you need to restart MicroK8s with sudo microk8s.stop; sudo microk8s start or just the k8s services with systemctl restart snap.microk8s.daemon-kubelite.
Is this what you are looking for? If not can you please provide more info on this issue?
[1] https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/

@ktsakalozos hm, I don't think that providing policy file in kube-apiserver parameters will work because there is no CRD for audit.k7s.io. maybe I'm wrong, haven't actually tried it yet.

Hi @adubkov
The audit.k8s.io/v1 API group is not available through the API server, but it is indeed the format to use for the audit policy config file. You can see https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/#audit-policy for more details


Update resource-metrics-pipeline.md

This pr adds a note to inform that Metrics API is beta.
closes #32183

/lgtm

Preview of updated page:
https://deploy-preview-32373--kubernetes-io-main-staging.netlify.app/docs/tasks/debug-application-cluster/resource-metrics-pipeline/
Metrics API targets 1.25 for GA/stable per Enhancement tracking issue 3048
/approve

Preview of updated page:
https://deploy-preview-32373--kubernetes-io-main-staging.netlify.app/docs/tasks/debug-application-cluster/resource-metrics-pipeline/
Metrics API targets 1.25 for GA/stable per Enhancement tracking issue 3048
/approve

/approve cancel
Looks like there is a merge conflict
This PR may need a rebase

@reylejano #32467 is the new pr for the same🙂


Submit form refresh

User story

As a developer
I want / need to solve an issue with submit of form
So that the page does not refresh.

Acceptance criteria

Explore strategies to solve the bug

Definition of done

Code review from peers has been completed and passed

Code is fully implemented and commented
Adheres to coding guidelines
Commits are not squashed
Code is checked into the repository

Unit tests for backend have been written and are passing
Manual performance tests on the browser are passing
No critical bugs are open

Completed on 26.05.2021


execution time output

your execution time node is great! What i'm trying to find is a way to geta combined output of run time, and inject it into the file name of my generations. is it possible to get a tallied time as a string output, and only combine on the way in and out? I'd like to be able to append this to file names so that i can compare run times between tweaked settings

wanted to bump this, see if its possible to return a string or dict as an output from ExecutionTime

Sorry for the late reply. ExecutionTime is a virtual node. I can’t think of any way to add text output.


tableacl: Panic with a more specific error message when no AclFactory…

… at all is registered.
@guokeno0

I addressed this in another way in https://github.com/youtube/vitess/pull/1279 . We don't depend on these panics at all so I just removed them

Closing this because Jeff will take care of it in his PR.


Display user statuses in the top navbar

When viewing the messages with a user the top navbar currently only displays their name. I think it would make sense to also display their status (akin to how we display stream descriptions in stream narrows).

For anyone pickint it up, It would make sense to work on #15682 and this together.

These are two separate issues, so they do not necessarily need to be addressed at the same time.

What I have in mind is, displaying a semi-userprofile for the current user in the right-sidebar, which would include showing the user's avatar, his full name, status icon and other things based on feedback.

Sure, this issue however is about displaying other users statuses in private messages. That's unrelated from the sidebar.

Oh! I think I didn't read the issue correctly. My bad :)

I added statuses to the compose box a while ago. Some of that could be reused here (PR #12866).
I can probably work on this tonight if no one picks it up by then. Probably @YashRE42? But I believe he is unavailable for a little while. :)

the relevant files here are tab_bar.hbs and tab_bar.js the correct fix will need to edit both of them:

the change for the js file, the case should probably be has_operator("pm-with") ... and we append the user status(es?) to tab_data.rendered_narrow_description via user_status.get_status_text(...),
we don't need to handle "group-pms" (searching narrow)
the change for the hbs file will likely just need an another conditional after the stream_settings_link one which handles PMs.

@zulipbot claim

@zulipbot claim

@zulipbot claim

@zulipbot claim

@zulipbot claim

@zulipbot claim

@zulipbot claim

@zulipbot claim

This is actually a nice idea. To use status/icon as it is in the DM instead of general DM icon:

For a group case we just use group icon

I started a design discussion thread: https://chat.zulip.org/#narrow/stream/101-design/topic/availability.20and.20status.20emoji.20in.20DM.20views/near/1642984


Extending Font and Text to support multiple textures (no more discarded glyphs)

Extending Font and Text to support multiple textures so that glyphs are not discarded in case one texture gets filled.
This can be useful in any of the following scenarios:

Big text
Large alphabets
OpenGL implementations with a small maximum texture size (e.g. software renderers)

Discussed in this forum thread.

Just something to keep in mind, text outlining #840 will affect this. To outline a character a second glyph is created just for the outline and (at the moment) stored in the same page as the other glyphs.

Indeed some parts will need to be rewritten due to #840 - should be quite easy to do.

Is your decision final to not update this branch?

Is your decision final to not update this branch?

Since the initial commit I have switched to using a duplicate of the involved files with my changes, which is "good enough" for me. But if this fix is ultimately going to be merged into master then sure, I can reimplement it over the up-to-date SFML version. It's mostly your call.

Yes, it would be great if you could update this PR! 🙂

See #1333


[Feature]: Move action routes in own route

Contact Details
No response
What do you like to be improved?
We have some routes (actions only) like add-child in /event/$slug/settings/events. Maybe we can move them to a own global route. This could also be an API entry.

Another topic came up here https://github.com/mint-vernetzt/community-platform/pull/349#issuecomment-1231806323


Timedelta to businesshours support

First of all, thank you very much for your work on this library.
I found myself slightly confused when trying to extract business hours from the timedelta result.
>>> d1 = datetime.datetime(2017, 5, 23, 9, 0)
>>> d2 = datetime.datetime(2017, 5, 24, 9, 0)
>>> r = BusinessTime().businesstimedelta(d1, d2)
datetime.timedelta(1)
My immediate thought to extract the business hours (which in this case it's 8) was to call
timedelta.total_seconds() method on the result, but this will return the equivalent of 24 hours in seconds, not 8 hours - given it has no knowledge of the business_hours in the BusinessTime object.
This experience proved a bit confusing and was wondering if you might be able to suggest a solution to this? Would a PR would be accepted for this sort of functionality?

Go for it.


Update contribution guide

This makes it clear that images must use oraclelinux:7-slim when a more specific product image is not applicable.
The 7-slim variant has the smallest attack surface because it has the least amount of packages installed and is updated whenever a CVE patch is released for any package within the image.
Signed-off-by: Avi Miller<EMAIL_ADDRESS>

@gvenzl I'll wait for your sign off on this as well.


single namespace deployment does not work due to hard coded namespace acme-controller

Deployed to OCP V4.3.x today, using the single namespace approach, just copy pasted from the docs.
Did not work, in the openshift-acme controller pod, I saw tons of failure "not permitted to list Routes in namespace acme-controller".
Could work arround by editing the deployment and changeing
https://github.com/tnozicka/openshift-acme/blob/1e8bdea1527baee50f3866be458619f6a3251cb5/deploy/single-namespace/deployment.yaml#L27
to point to my namespace
@tnozicka - great work btw!

Thanks.
Yeah, that was on my list as well. looks like @rbo already has a PR https://github.com/tnozicka/openshift-acme/pull/114

Solved since merged PR.


Fix: mistyping in 'separated' word

Mistyping in word 'separated' in "Waypoint: Iterate with JavaScript For Loops".

:blush:

@SaintPeter This should have not been merged into master.
@Takumar In the future always PR to staging, not master.

Of course, thank you @BerkeleyTrue for information.


Project delete explicitly looking for service catalog instances

/kind bug

What versions of software are you using?
Operating System:
Not a specific OS issue
Output of odo version:
master
How did you run odo exactly?
Login as kubeadmin
$ odo login -u kubeadmin -p ***** https://****:6443
[...]
Using project "default".

$ odo project create test123 -v 4
✓  Project 'test123' is ready for use
 ✓  New project created and now using project: test123
[...]

$ odo project delete test123 -f -v 4

I0610 15:25:42.325920   25789 application.go:49] Unable to list Service Catalog instances: unable
to list ServiceInstances: the server could not find the requested resource (get
serviceinstances.servicecatalog.k8s.io)

✓  Deleted project : test123
 [...]

Login as developer
$ odo login -u developer -p **** https://****:6443
Connecting to the OpenShift cluster
Login successful.
[...]

$ odo project create test123 -v 4
 ✓  Project 'test123' is ready for use
 ✓  New project created and now using project: test123
[...]

$ odo project delete test123 -f -v 4

I0610 15:07:24.963914   25586 application.go:49] Unable to list Service Catalog instances: unable to
 list ServiceInstances: serviceinstances.servicecatalog.k8s.io is forbidden: User "developer" cannot
list resource "serviceinstances" in API group "servicecatalog.k8s.io" in the namespace "test123"

✓  Deleted project : test123
 [...]

Actual behavior
As mentioned in the steps
Expected behavior
@dharmit @girishramnani Is the expected behaviour as observed in the steps ?
Any logs, error output, etc?

IMO this is not expected behaviour. I'm seeing this showing up a LOT in CI (probably because of the numerous odo project delete calls). I think this needs to be fixed.

We're not seeing this behaviour any longer. Closing. Feel free to re-open if it pops up again.
/close


TATSettings name and position are now customizable

I feel like I should fix some lines but nothing serious. I'll merge it right after


\n in first "echo" or output causes flickering of status bar display, example "brew-services"

For example this kind of output, ruby code from brew-services
puts """
#{started != 0 && BAR_COLORS ? green(started) : started}/#{total}
---
#{menus}
---
#{all}
#{REFRESH}
"""

This will flicker in the menu bar or intermittent display of that first line. Not really a bug, but the fix is simple
puts """#{started != 0 && BAR_COLORS ? green(started) : started}/#{total}
---
# ....

@AddictArts I agree this could be neater. What do you think would be the ideal behaviour?