Failure to decode extension Addition Group [[ .. ]] for ASN.1 PER bit aligned.

Hi
I am testing 0.9.28
I can generate LTE RRC decoder however all messages including extension Addition Group [[ ]]] fail decoding.
Error looks like
AD: Processing RRC_conn_setup.txt
AD: Decoding 39 bytes
AD: decode(0) consumed 0+0b (39), code 2
AD: Clean up partially decoded DL-CCCH-Message
AD: ofp 1, no=0, oo=0, dbl=0
RRC_conn_setup.txt: Decode failed past byte 0: Input processing error
Now if I replace the [[ ]] construct with equivalent ASN.1 syntax extensionAdditionGroup SEQUENCE {}, decoding is successful.
Issue is not blocking but annoying as I cannot directly work from 3GPP ASN.1 syntax.
Example: original 3GPP ASN.1 (decoding fails):
[[	-- DL configuration as well as configuration applicable for DL and UL
csi-RS-ConfigNZPToReleaseList-r11
CSI-RS-ConfigNZPToReleaseList-r11	OPTIONAL,		-- Need ON
csi-RS-ConfigNZPToAddModList-r11
CSI-RS-ConfigNZPToAddModList-r11	OPTIONAL,		-- Need ON
csi-RS-ConfigZPToReleaseList-r11
CSI-RS-ConfigZPToReleaseList-r11	OPTIONAL,		-- Need ON
csi-RS-ConfigZPToAddModList-r11	CSI-RS-ConfigZPToAddModList-r11	OPTIONAL,		-- Need ON
epdcch-Config-r11				EPDCCH-Config-r11				OPTIONAL,		-- Need ON
pdsch-ConfigDedicated-v1130		PDSCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
-- UL configuration
cqi-ReportConfig-v1130			CQI-ReportConfig-v1130			OPTIONAL,		-- Need ON
pucch-ConfigDedicated-v1130		PUCCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
pusch-ConfigDedicated-v1130		PUSCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
uplinkPowerControlDedicated-v1130
UplinkPowerControlDedicated-v1130	OPTIONAL		-- Need ON
]],
Modified 3GPP ASN.1 with equivalent construct (decoding works perfectly):
extensionAdditionGroup4 SEQUENCE {	-- DL configuration as well as configuration applicable for DL and UL
	csi-RS-ConfigNZPToReleaseList-r11
								CSI-RS-ConfigNZPToReleaseList-r11	OPTIONAL,		-- Need ON
	csi-RS-ConfigNZPToAddModList-r11
								CSI-RS-ConfigNZPToAddModList-r11	OPTIONAL,		-- Need ON
	csi-RS-ConfigZPToReleaseList-r11
								CSI-RS-ConfigZPToReleaseList-r11	OPTIONAL,		-- Need ON
	csi-RS-ConfigZPToAddModList-r11	CSI-RS-ConfigZPToAddModList-r11	OPTIONAL,		-- Need ON
	epdcch-Config-r11				EPDCCH-Config-r11				OPTIONAL,		-- Need ON
	pdsch-ConfigDedicated-v1130		PDSCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
-- UL configuration
	cqi-ReportConfig-v1130			CQI-ReportConfig-v1130			OPTIONAL,		-- Need ON
	pucch-ConfigDedicated-v1130		PUCCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
	pusch-ConfigDedicated-v1130		PUSCH-ConfigDedicated-v1130		OPTIONAL,		-- Need ON
	uplinkPowerControlDedicated-v1130
								UplinkPowerControlDedicated-v1130	OPTIONAL		-- Need ON
},

Thank you very much for your help
Best regards
D. Bressanelli

@dbresan2, I submitted a pull request #238 to address this extension group [[...]] issue.

hi @brchiu ,
Good day. I met the same issue. And with the fix #238, I still failed to decode extension Addition Group [[ .. ]] of RRC.
I tried to decode LTE RRC DL_DCCH_Message 20 02 01 80 02 C2 00 08 20 C0 but return fail.
There is some issue in handling extension Addition Group
asn:
PhysicalConfigDedicated ::=		SEQUENCE {
pdsch-ConfigDedicated				PDSCH-ConfigDedicated			OPTIONAL,		-- Need ON
pucch-ConfigDedicated				PUCCH-ConfigDedicated			OPTIONAL,		-- Need ON
pusch-ConfigDedicated				PUSCH-ConfigDedicated			OPTIONAL,		-- Need ON
uplinkPowerControlDedicated			UplinkPowerControlDedicated		OPTIONAL,		-- Need ON
tpc-PDCCH-ConfigPUCCH				TPC-PDCCH-Config				OPTIONAL,		-- Need ON
tpc-PDCCH-ConfigPUSCH				TPC-PDCCH-Config				OPTIONAL,		-- Need ON
cqi-ReportConfig					CQI-ReportConfig				OPTIONAL,		-- Cond CQI-r8
soundingRS-UL-ConfigDedicated		SoundingRS-UL-ConfigDedicated	OPTIONAL,		-- Need ON
antennaInfo							CHOICE {
explicitValue						AntennaInfoDedicated,
defaultValue						NULL
}																	OPTIONAL,	-- Cond AI-r8
schedulingRequestConfig				SchedulingRequestConfig			OPTIONAL,		-- Need ON
...,
[[	cqi-ReportConfig-v920				CQI-ReportConfig-v920		OPTIONAL,		-- Cond CQI-r8
antennaInfo-v920					AntennaInfoDedicated-v920	OPTIONAL		-- Cond AI-r8
]],
[[	antennaInfo-r10					CHOICE {
explicitValue-r10				AntennaInfoDedicated-r10,
defaultValue					NULL
}																OPTIONAL,	-- Cond AI-r10
antennaInfoUL-r10				AntennaInfoUL-r10				OPTIONAL,		-- Need ON
cif-Presence-r10				BOOLEAN							OPTIONAL,		-- Need ON
log:
//read the extensions bitmap correctly but did not handle it as extensions as I see:
Extensions 12 present in PhysicalConfigDedicated (constr_SEQUENCE.c:1200)
[PER got 12<=38 bits => span 54 +5[14..40]:c2 (26) => 0x80] (asn_bit_data.c:132)
Read in extensions bitmap for PhysicalConfigDedicated of 12 bits (8..) (constr_SEQUENCE.c:1214)
[PER got  1<=12 bits => span 1 +0[1..12]:08 (11) => 0x0] (asn_bit_data.c:132)
[PER got  1<=11 bits => span 2 +0[2..12]:08 (10) => 0x0] (asn_bit_data.c:132)
[PER got  1<=10 bits => span 3 +0[3..12]:08 (9) => 0x0] (asn_bit_data.c:132)
[PER got  1<= 9 bits => span 4 +0[4..12]:08 (8) => 0x0] (asn_bit_data.c:132)
[PER got  1<= 8 bits => span 5 +0[5..12]:08 (7) => 0x1] (asn_bit_data.c:132)
Decoding member cif-Presence-r10 in PhysicalConfigDedicated (nil) (constr_SEQUENCE.c:1238)

hi @brchiu ,
After upgraded to the latest version.
I can decode extension Addition Group now.
Thanks.


Add TAS Parliament

You know the drill at this point (it's for Tasmania).


select API backend for persistent data and configuration

wis2box-api uses Elasticsearch as a backend to manage data provided though OGC API.
For admin UI workflow, we would like the user to be able to manage the following:

discovery metadata
station metadata
data pipeline configurations

The UI (as a deploy time option) needs to be able to interact with the API to manage the above.
Considerations:

the above configurations:

are small in size
have a low transaction rate (design time)

in process (SQLite, TinyDB, DuckDB) or full blown RDBMS (PostgreSQL, MySQL/MariaDB/etc.)
resulting size of built (Docker) image
pygeoapi requirements:

plugin availability

https://docs.pygeoapi.io/en/latest/data-publishing/ogcapi-features.html (station metadata)
https://docs.pygeoapi.io/en/latest/data-publishing/ogcapi-records.html (discovery metadata)

transaction capability (PUT, POST, PATCH, DELETE)

cc @isedwards

2021-01-31

use an in process database (MySQL, TinyDB, h2)
maintain single source of truth on API backends


darwin build

Me have some experience with building OpenVPN for major platforms with differents SSL library. The main issue I find in other code is that instead of make install to the correct location, developers tend to copy SSL library files around and give OpenVPN (or other tools) weird OPENSSL_CFLAGS that end up in the binary.
Therefore when me tried to build on OSX I kinda stumbled into the python script because all the usual mistakes were present. The massive changes were because me cannot enhance code when inconsistent. It should now work with python3 as well.
Your efforts to prepare OpenVPN for the post quantum world are highly appreciated and I input is meant to help you (and others) to deploy this VPN and test it in real world environments.
The following is summary of what me did to the build.py:

refactor Python, pep8+flake8 the code
add constants, avoid copying from ../.. and use absolute directories instead.
recycle downloads - pull all before building
commandline options --verbose --skip-* --prefix etc
adapt OpenSSL build to mimic the openvpn-build/build behavior
(./Configure instead of ./config)
treat Darwin and Linux as Unix only minors (systemd stuff) are separated
add system detection script (from openvpn-build) to find the correct
OpenSSL ./Configure target

To use, on OSX install xcode then run python build.py --skip-test
The tests (make test in OpenSSL) are broken, me did not investigate why. The produced OpenVPN binary responds happily to --help and --version on 10.11.6
I did not test the windows build (one machine at a time) but while porting me found that the windows-nsis build may not pick up the custom OpenSSL library. Usually me goes with mingw and build the OpenVPN windows installer in a linux environment.
please merge or pick cherries, no need for attribution for my inputs

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: minabarret sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

The PQ algorithms will need to be a part of OpenVPN and OpenSSL in the future, but we're a long way from that. Right now the build process is a little strange. The PQ library currently uses a different build process from the rest of OpenSSL that just doesn't work properly on cross-compiling, which is why we have to undertake this strange process. It may in the future, but it's still very much a work in progress.
I'll take a look at your updated PR on Linux and Windows and see how it works, and get back to you with the results. Thanks again!

Okay, I see your points, but this means there's some substantial work beyond what you've done to get the Windows build working again. For us, keeping the Windows build working is more important than adding MacOS, and I don't want to leave your pull request in limbo.
Therefore, I propose we accept your changes into a branch for now, so people who want to build for MacOS can do so, and then we'll open an issue to track getting the Windows build working again in this branch, and then when that's working, we can merge it back to master.
If this is acceptable to you, I'll create a branch, change your pull request to target it, and accept it.


AL Snippet with intellisense

I created a simplee Snippet to create a Event Subscriber for Tables
"EventSubcriber_Table":{
	"prefix": "fscEventSubscriber_Table",
	"body": [
		"[EventSubscriber(ObjectType::Table, Database::\"${1:Object}\", '${2:Publisher}', '${3:Field}', true, false)]",
		"local procedure Tab$1_$0$2_$3()",
		"begin",
		"",
		"end;"
	],
	"description": "EventSubscrier for Tables"
}

The problem is, when I insert the snippet and want to Subscribe the table "Payment Terms". I type Pay and the intellisense opend with the suggestion Payment Terms. When i accept it with enter I got the following
[EventSubscriber(ObjectType::Table, Database::"Payment Terms", '${2:Publisher}', '${3:Field}', true, false)]
local procedure TabPay"Payment Terms"$0$2$3()",
begin
end;
In the second line is now the value who I typed and the value who I got from the intellisense
Versions:

AL Langauge: 3.0.107312

Hello,
I've also found this to be quite difficult to handle. I discovered a VS Code extension with a lot of useful snippets which might help you:
https://marketplace.visualstudio.com/itemdetails?itemName=BartPermentier.al-toolbox
Hope you like it.
Regards,
Joriek


DOC:Fix error in ode docstring example

Fixes choking on the string formatting of a complex-valued ndarray in the docstring example for Integrate.ODE.

@maniteja123 this looks fine, but would be useful to put the code to reproduce the error you see in a comment here.

The error generated when running the code in the original docstring was
>>> r = ode(f, jac).set_integrator('zvode', method='bdf')
>>> r.set_initial_value(y0, t0).set_f_params(2.0).set_jac_params(2.0)
<scipy.integrate._ode.ode object at 0x7f56978db190>
>>> while r.successful() and r.t < t1:
...    r.integrate(r.t+dt)
...    print("%g %g" % (r.t, r.y))
...
array([-0.71038232+0.23749653j,  0.40000271+0.j        ])
Traceback (most recent call last):
File "<stdin>", line 3, in <module>
TypeError: float argument required, not numpy.ndarray

r.y is a nd-array, but was wrongly passed as argument to %g in print.

Thanks @maniteja123, merged.


Progress on duration and time.

namespacing changes.
Adding support for unsigned +/- signed saturation math
Enforcing duration and time concepts.
Removing multiplication operations (we don't support saturation.
multiplication)

TODO:
finish unit tests for Monotonic time and duration.
Add UTC time abstraction.
Add media layer clock interface.

I'll work on the on-target failure. My guess is this is a problem with gtest itself.


Sprites from TextureAtlas get squished when rendered

bevy = "0.2.1"
Windows 10 v2004
I was playing with the sprite_sheet.rs example code. After updating it slightly to work with the current API, I noticed that the sprites were getting squished in the x-axis by a factor of seven - which also is the number of sprites in the spritesheet.
I have looked at the TextureAtlas::from_grid source and it seems to correctly set the sprites sizes to the passed Vec2. The bug seems to be somewhere in the renderer.
The code with my fixes:
use bevy::prelude::*;

fn main() {
    App::build()
        .add_default_plugins()
        .add_startup_system(setup.system())
        .add_system(animate_sprite_system.system())
        .run();
}

fn animate_sprite_system(
    texture_atlases: Res<Assets<TextureAtlas>>,
    mut query: Query<(&mut Timer, &mut TextureAtlasSprite, &Handle<TextureAtlas>)>,
) {
    for (timer, mut sprite, texture_atlas_handle) in &mut query.iter() {
        if timer.finished {
            let texture_atlas = texture_atlases.get(texture_atlas_handle).unwrap();
            sprite.index = ((sprite.index as usize + 1) % texture_atlas.textures.len()) as u32;
        }
    }
}

fn setup(
    mut commands: Commands,
    asset_server: Res<AssetServer>,
    mut texture_atlases: ResMut<Assets<TextureAtlas>>,
) {
    let texture_handle = asset_server
        .load("res/textures/gabe-idle-run.png") // now looks in root directly instead of assets subdirectory
        .expect("couldn't load file"); // now gives error on fail - ^ but not on "file not found"??
    let texture_atlas = TextureAtlas::from_grid(texture_handle, Vec2::new(24.0, 24.0), 7, 1);
    let texture_atlas_handle = texture_atlases.add(texture_atlas);
    commands
        .spawn(Camera2dComponents::default())
        .spawn(SpriteSheetComponents {
            texture_atlas: texture_atlas_handle,
            // Vec3::new(6.0, 6.0, 6.0) results in squishing, Vec3::new(6.0 * 7.0, 6.0, 6.0) renders as Vec3::new(6.0, 6.0, 6.0) should
            transform: Transform::from_non_uniform_scale(Vec3::new(6.0, 6.0, 6.0)), // from_scale for f32 and Vec3 now separate  functions
            ..Default::default()
        })
        .with(Timer::from_seconds(0.1, true));
}

Squished:

Should be:

In 0.2.1 the size parameter of TextureAtlas::from_grid represents the size of the entire texture rather than the size of tiles/individual sprites.
Fetching the latest master should fix it or, if you want to stick with 0.2.1, setting the size to Vec2::new(168.0, 24.0) should also fix it.

Thanks for the answer, both solutions worked perfectly.
Seems the size parameter also doesn't specify the pixel-size of the source, but rather the desired size for rendering. Setting it to Vec2::new(7.0, 1.0) in "0.2.1" / Vec2::new(1.0, 1.0) in master also worked and lets you set the precise rendering pixel-size in the character transform.


Remove custom IntegerContverter

Werkzeug now supports signed values viasigned=True for its IntegerConverter, so the workaround introduced in ea9bbc25c1ef11f5fa0697f410a250cf887e89aa is unnecessary.
Relevant lines:
https://github.com/agdsn/sipa/blob/1d5547b32752a96da1c1c164ec0a61a6eab6fc2e/sipa/base.py#L19-L27

It has been introduced to support negative values in query parameters, more specifically, to make an URL like https://agdsn.de/sipa/news/?start=-2&end=-1 work.


[ALLUXIO-2962] Use ConfigurationRule to avoid manually setting and resetting Configuration

https://alluxio.atlassian.net/browse/ALLUXIO-2962

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16104/Failed Tests: 2org.alluxio:alluxio-tests: 2alluxio.master.JournalShutdownIntegrationTest.singleMasterJournalStopIntegrationalluxio.master.JournalShutdownIntegrationTest.singleMasterMountUnmountJournal
Test FAILed.

@cmuyaol two minor comments left. PTAL
thanks for improving the testing code health!

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16125/Failed Tests: 2org.alluxio:alluxio-tests: 2alluxio.master.JournalShutdownIntegrationTest.singleMasterJournalStopIntegrationalluxio.master.JournalShutdownIntegrationTest.singleMasterMountUnmountJournal
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16127/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16132/
Test PASSed.

Merged build finished. Test PASSed.

@aaudiber  are you good with this PR?

Just the last comment of removing mFolder now that it's no longer used in BlockWorkerTest.java

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16143/Failed Tests: 27org.alluxio:alluxio-core-server-worker: 27alluxio.worker.block.BlockWorkerTest.openUnderFileSystemBlockalluxio.worker.block.BlockWorkerTest.closeUnderFileSystemBlockalluxio.worker.block.BlockWorkerTest.abortBlockalluxio.worker.block.BlockWorkerTest.accessBlockalluxio.worker.block.BlockWorkerTest.commitBlockalluxio.worker.block.BlockWorkerTest.createBlockalluxio.worker.block.BlockWorkerTest.commitBlockOnRetryalluxio.worker.block.BlockWorkerTest.createBlockLowerTieralluxio.worker.block.BlockWorkerTest.createBlockRemotealluxio.worker.block.BlockWorkerTest.freeSpacealluxio.worker.block.BlockWorkerTest.getTempBlockWriterRemotealluxio.worker.block.BlockWorkerTest.getReportalluxio.worker.block.BlockWorkerTest.getStoreMetaalluxio.worker.block.BlockWorkerTest.getVolatileBlockMetaalluxio.worker.block.BlockWorkerTest.getBlockMetaalluxio.worker.block.BlockWorkerTest.hasBlockMetaalluxio.worker.block.BlockWorkerTest.lockBlockalluxio.worker.block.BlockWorkerTest.moveBlockalluxio.worker.block.BlockWorkerTest.moveBlockNoopalluxio.worker.block.BlockWorkerTest.readBlockalluxio.worker.block.BlockWorkerTest.readBlockRemotealluxio.worker.block.BlockWorkerTest.removeBlockalluxio.worker.block.BlockWorkerTest.requestSpacealluxio.worker.block.BlockWorkerTest.unlockBlockalluxio.worker.block.BlockWorkerTest.sessionHeartbeatalluxio.worker.block.BlockWorkerTest.updatePinListalluxio.worker.block.BlockWorkerTest.getFileInfo
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16182/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16198/Build result: FAILURE[...truncated 2874 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/hdfs/target/alluxio-core-client-hdfs-1.6.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-client-hdfs/1.6.0-SNAPSHOT/alluxio-core-client-hdfs-1.6.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/hdfs/target/alluxio-core-client-hdfs-1.6.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-client-hdfs/1.6.0-SNAPSHOT/alluxio-core-client-hdfs-1.6.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/pom.xml to org.alluxio/alluxio-keyvalue-common/1.6.0-SNAPSHOT/alluxio-keyvalue-common-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/pom.xml to org.alluxio/alluxio-core-client-fs/1.6.0-SNAPSHOT/alluxio-core-client-fs-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.6.0-SNAPSHOT.jar to org.alluxio/alluxio-core-client-fs/1.6.0-SNAPSHOT/alluxio-core-client-fs-1.6.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.6.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-client-fs/1.6.0-SNAPSHOT/alluxio-core-client-fs-1.6.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/fs/target/alluxio-core-client-fs-1.6.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-client-fs/1.6.0-SNAPSHOT/alluxio-core-client-fs-1.6.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/pom.xml to org.alluxio/alluxio-core-common/1.6.0-SNAPSHOT/alluxio-core-common-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.6.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.6.0-SNAPSHOT/alluxio-core-common-1.6.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.6.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.6.0-SNAPSHOT/alluxio-core-common-1.6.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.6.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.6.0-SNAPSHOT/alluxio-core-common-1.6.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.6.0-SNAPSHOT/alluxio-core-server-worker-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/dependency-reduced-pom.xml to org.alluxio/alluxio-underfs-glusterfs/1.6.0-SNAPSHOT/alluxio-underfs-glusterfs-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.6.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-glusterfs/1.6.0-SNAPSHOT/alluxio-underfs-glusterfs-1.6.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.6.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-glusterfs/1.6.0-SNAPSHOT/alluxio-underfs-glusterfs-1.6.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.6.0-SNAPSHOT/alluxio-core-client-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.6.0-SNAPSHOT/alluxio-examples-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.6.0-SNAPSHOT/alluxio-core-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.6.0-SNAPSHOT/alluxio-core-server-proxy-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.6.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.6.0-SNAPSHOT/alluxio-core-server-proxy-1.6.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.6.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.6.0-SNAPSHOT/alluxio-core-server-proxy-1.6.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.6.0-SNAPSHOT/alluxio-shell-1.6.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.6.0-SNAPSHOT/alluxio-tests-1.6.0-SNAPSHOT.pomchannel stopped
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16199/
Test PASSed.


AoT: Failing to cast object to byte[]

Describe the bug

To Reproduce

Create a new WinUI 3 app, and enable it for AoT
Replace the MainWindow.xaml.cs code with the following:

        public MainWindow()
        {
            var settings = GetLocalSettings();
            if (!settings.Values.ContainsKey("Test"))
                settings.Values.Add("Test", new byte[] { 1, 2, 3, 4 });
            this.InitializeComponent();
        }

        private void myButton_Click(object sender, RoutedEventArgs e)
        {
            var settings = GetLocalSettings();
            var data = (byte[])settings.Values["Test"](); // BOOM! Unable to cast object of type 'WinRT.IInspectable' to type 'System.Byte[]'.
        }

        private ApplicationDataContainer GetLocalSettings()
        {
            var localSettings = ApplicationData.Current.LocalSettings;
            if (localSettings.Containers.TryGetValue("Settings", out var container))
                return container;
            return localSettings.CreateContainer("Settings", ApplicationDataCreateDisposition.Always);
        }

Run the app and click the button.
Observe the application crash: Unable to cast object of type 'WinRT.IInspectable' to type 'System.Byte[]'.

Expected behavior
App settings gets the byte[].
Version Info
WinAppSDK 1.6.0, CSWinRT 2.1.3
Additional context
Also tried:

.As<byte[]>()
.As<IEnumerable<byte>>().ToArray()
Enumerable.Cast<byte[]>((IEnumerable)settings.Values["Test"])

I was under the impression that arrays are illegal to use outside of parameters in the WinRT type system.
https://learn.microsoft.com/en-us/uwp/winrt-cref/winrt-type-system

@dongle-the-gadget are you saying we can't store any binary data in the application settings? I mean it works fine - it's only in AoT mode it doesn't. .NET Native with UWP works fine also.

It works but seems like undocumented behavior. The supported list of types in docs also doesn’t mention arrays. I suppose though that you cam probably cast the object into an IPropertyValue and get the array from there.

By any chance did you disable IReference support?

By any chance did you disable IReference support?

Not that I know off? The code is in a net8.0-windows library. No explicit reference to WindowsAppSDK.

It looks like PublishTrimmed is enough to reproduce the exception.

This works via boxing support / IReferenceArray.  It looks like even though we pass a managed array initially, the array we are getting back is a native version of it.  When we do, we are failing to construct the type to project it as on AOT due to being a generic with a value type which is guarded against on AOT and thereby fallback to IInspectable.  I am looking at doing something similar to what we did for IReference / nullable here to get it working at least for blittable array scenarios.


Fix crash in member lookup when base type contains type variables.

We were crashing during performTypoCorrection if the base type contained
type variables.
rdar://problem/28387684

@swift-ci Please smoke test

Hmmm, gotta run those validation tests.

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 8e3e7a4f2ba209d772e5e6d14e2553f22d691bef
Test requested by - @rudkx

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 8e3e7a4f2ba209d772e5e6d14e2553f22d691bef
Test requested by - @rudkx

Hmm, "EXIT WRONG SHA", any idea what's causing that @shahmishal?
https://ci.swift.org/job/swift-PR-Linux/4298/console

@swift-ci Please smoke test and merge.

Its due to https://github.com/jenkinsci/ghprb-plugin/issues/414

Ah thanks, good to know!

LLDB test failed. Seems unrelated. Perhaps it's flaky?

@swift-ci Please smoke test and merge.

@swift-ci Please smoke test Linux platform

Linux is failing due to LLDB tests, which will be disabled once this PR passes smoke test.
https://github.com/apple/swift/pull/5631

@swift-ci Please smoke test Linux platform

@shahmishal Thanks Mishal, I've kicked off tests again.


Add Section Heading for OSCAL Catalogs, Profiles, and other Document Examples in the Real World

Consider also a news section to match current events postings on social media.


About Windows XP support

Sorry if I ask this so sudden.
According to RaduMC (Also known as Chipicao) on Xentax forum, Unity Studio should be able to run on Windows XP with the .NET framework 4.0 installed. But no, the application won't run on Windows XP at all. (It doesn't shows any error message window, either.) I checked the task manager at the moment I start the Unity Studio, but the application close itself without any error message.
Someone on Xentax forum was able to modify the application to make it runs on XP (If you are curious, the post in question is in the 13th page of the thread.)
I wonder if you can modify your forks of Unity Studio to make it runs on Windows XP.
In case you are wondering, I have a PC that is runs on Windows XP Professional SP3 and I don't enough have money to brought a new PC or (for the reason that the hardware is old) upgrade the OS. I guess you will likely to tell me to brought a new PC despite my family's finance situation.
Edit: I just installed Visual Studio C# 2010 SP1 and tries to debug Unity Studio, but Visual Studio shows me the 'Error while trying to run project: Cannot start debugging: the assembly to be debugged was built with a platform incompatible with the current system' error everytime I try to debug.
Edit 2: Nevermind, I just set the whole solution to 'X86', however there's a error while I try to build it in Visual Studio: 'Invalid Resx file. The parameter is incorrect Line 836, position 5.' The error was from the file UnityStudioForm.resx. I just don't know how to fix this one.

Sorry, I don't know how to solve this problem...

@Perfare: Apparently, it was these lines that causes the application to not able to start in Windows XP:
<data name="$this.Icon" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
<value>
(This section is omitted due to overly long codes)
</value>
</data>
Removing those lines will allows the Unity Studio to run on Windows XP. I wonder why...

I found some reasons, looks like the XP system only supports less than 128x128 resolution icon, but the resolution of this icon is 256x256

@Perfare: Then how can I change the icon to the one with 128x128 resolution?
Note that I have Visual Studio 2010 Express installed in my PC.

@Perfare You can use an icon editor to generate a series of icons.
Suggested:
32bpp RGBA: 256x256 48x48 32x32 16x16
256 Colors: 48x48 32x32 16x16
Windows will try to find the first readable (and fittest) sub-icon. So with this series in an icon file, Windows XP will try to load the 32bpp 16x16 for window icon, and 32bpp 48x48 for File Explorer (tile view), etc.

Okay, I can confirmed that the latest commit have fixed the issues of not able to build and run on Windows XP PC.

@Yuuyatails Okay, thank you for your testing.


Updates frontend testing with new examples

Frontend testing was broken and outdated. The tests have been fixed, and updated to use shallow rendering where possible. Testing stubs demonstrate how to set up testing for several components with redux and drag and drop.

Previous pull requests were squashed so my commit history on my local master is different than the repo's. Hence the unrelated commits that claim to be part of this pull request.
If you would like to keep the commit log clean, feel free to squash this pull request as well. After this is merged I will sync my fork to fix the issue.


__webpack_require is not a function in upgrade to v3.0.1

From @peterennis on April 12, 2017 5:34
Ionic version:  (check one with "x")
[ ] 1.x
[ ] 2.x
[x ] 3.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Upgrade app to v3.0.1 and run in lab
Expected behavior:
Running.
How can this be debugged further?
Steps to reproduce:

Related code:
insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Cordova CLI: 6.5.0
Ionic Framework Version: 3.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.3.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.9.2
Xcode version: Not installed

Copied from original issue: driftyco/ionic#11178

Hey @peterennis, thanks for opening an issue with us. Would you mind sharing a repo with us that we can use to reproduce this issue?

The repo is on VSTS. Where do I send you an invite?

Please create a minimal recreation on Github and we'll try to fix.
Thanks,
Dan

The issue was related to translation.
See here: https://github.com/driftyco/ionic-starter-super/issues/98
and this PR: https://github.com/driftyco/ionic-starter-super/pull/95
AoT and lazy loading did not work correctly as a new version
of translate was need - ngx-translate

You can close this issue. If I run into it again I will look into creating an MVP test.


"error: implicit declaration of function ‘usleep’" on debian jessie

I am trying to build upm on debian jessie. Mraa is compiled and installed successfully. However, when I try to build upm I get the following error:
[  2%] Building C object src/utilities/CMakeFiles/utilities-c.dir/upm_utilities.c.o
/upm-src/src/utilities/upm_utilities.c: In function ‘upm_delay_ms’:
/upm-src/src/utilities/upm_utilities.c:66:5: error: implicit declaration of function ‘usleep’ [-Werror=implicit-function-declaration]
     usleep(1000 * time);
     ^
/upm-src/src/utilities/upm_utilities.c: At top level:
cc1: error: unrecognized command line option "-Wno-misleading-indentation" [-Werror]
cc1: all warnings being treated as errors
make[2]: *** [src/utilities/CMakeFiles/utilities-c.dir/upm_utilities.c.o] Error

cmake version 3.0.2
gcc version 4.9.2 (Debian 4.9.2-10)

My quick guess is that #if defined(__linux__) doesn't work on Debian as intended. Can you try building with make UPM_PLATFORM_LINUX=1 and let us know if that works for you?

Unfortunately, same error.

If you have docker you can reproduce this error yourself with this dockerfile
Download it and run: docker build -t python-mraa-upm .

We'll provide a nanosleep implementation for the delay function instead, to match the standard. Also, it might be worth giving it a try with CMake 3.1+, as it detects the standard to use a bit differently. For older CMake we set -std=c++11, but on Debian you might want to use -std=gnu++11 instead. The CMAKE_CXX_FLAGS variable can be used with CMake for that.

Some fixes have been committed that use nanosleep() instead of usleep() for delays, and also defines the appropriate POSIX_C_SOURCE standard in upm_utilities.c needed to avoid these warnings/errors.
I have tested with your Dockerfile and current master should build without issues now.
Thanks for supplying the Dockerfile to reproduce this issue!

@jontrulson Thank you, now it works. I also created repository in docker hub for python with mraa and upm included.

Unfortunately this issue has come back:
[Build]    /usr/src/upm-master/src/p9813/p9813.c: In function ‘p9813_send_byte’:
[Build]    /usr/src/upm-master/src/p9813/p9813.c:103:9: error: implicit declaration of function ‘usleep’ [-Werror=implicit-function-declaration]
[Build]             usleep(20);
[Build]             ^
[Build]    /usr/src/upm-master/src/p9813/p9813.c: At top level:
[Build]    cc1: error: unrecognized command line option "-Wno-misleading-indentation" [-Werror]
[Build]    cc1: all warnings being treated as errors

Since you are building from master, these kinds of problems may crop up from time to time.  To allow you to build, you might want to disable warnings-as-error - add
-DWERROR=NO
To your cmake command line.


Add Alt+Tab

~See title.~
This issue is to track adding "Alt+Tab" functionality.

See title.

What a title? Alt+Tab not working for me

"See title" means "the title has the info" in this case.

Where is info? I didn't see it

Where is info? I didn't see it

I've updated the text of the issue to better explain what its purpose is.

Also one related shortcut that is different in windows:
Alt + Tab: Cycle open windows on OS
Ctrl + Tab: Cycle open tabs within App
Even if you swap the Control/Command(aka alt) on mac, getting both of these shortcuts to work the as expected is quite tricky.

BUMP

On Mac, go to your user/.config/karabiner/karabiner.json
Add this piece of json to your "rules" in "complex_modifications"
{
    "description": "Option(Alt)+Tab as Switch Application (Command+Tab)",
    "manipulators": [
        {
            "from": {
                "key_code": "tab",
                "modifiers": {
                    "mandatory": [
                        "option"
                    ],
                    "optional": [
                        "any"
                    ]
                }
            },
            "to": [
                {
                    "key_code": "tab",
                    "modifiers": [
                        "left_command"
                    ]
                }
            ],
            "type": "basic"
        }
    ]
},

@dangnhdev Because sometimes I am a bit of an idiot! 😅
I didn't even realise this code had been added and have been lax in keeping up with the issues. I'll carve out some time soon to do some upkeep and add new features/merge PRs.


Fix Issue #43

Description

Added deferred reply to make sure bot does not throw error (to numberfact and joke commands).
Removed the 'n' alias accidentally added to the /joke command.
Fix the description of /numberfact command

Fixes #43
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Local Testing on a private server.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have restored .env.template
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes - Run npm run ci
[x] Any dependent changes have been merged and published in downstream modules

Looks great! Thanks @muditmahajan21


List not differentiating between TOR RELAY and EXIT nodes

Would be great not having the TOR relay nodes on the list as they are not a threat.

it is part of the strategy of reducing the attack surface. if someone is on a TOR IP address , why would you accept smtp , ssh, vpn, or any connection from them into an enterprise edge/DMZ firewall?
--
Maher Ghazzi
248-736-5000

On Nov 7, 2016, at 4:41 AM, danhusan<EMAIL_ADDRESS>wrote:
Would be great not having the TOR relay nodes on the list as they are not a threat.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I think you misunderstand what a relay does. Someone using TOR will never send traffic OUT from a relays IP address. Hence no need for blocking it in the enterprise firewall. A relay only relays traffic between TOR nodes.
What will happen is that if user X runs a TOR relay at home behind his router running NAT it will be blacklisted in all enterprises using your list. Then he will not be able to access those enterprises services when surfing normally (outside of TOR) and creating noise for the enterprises.
I completely agree that blocking TOR exits could be smart - but blocking people running relays is just unnecessary.

Hi @danhusan, please take a look at MineMeld (https://github.com/PaloAltoNetworks/minemeld). With the blutmagie feeds you can now differentiate exit nodes from all the TOR nodes.


[ROCm] Fix for a test regression on the ROCm platform - 200207 - 2

The following commit introduces a test regression on the ROCm platform
https://github.com/tensorflow/tensorflow/commit/7a931a2349591f4e2250ac2d3b6c3ca66538b740
That commit adds an explicit check for GPU device in the profiler output (if a GPU is present in the list of physical devices).
Since ROCm platform does not yet support device tracing, this test now fails on the ROCm platform
The "fix" (until ROCm adds support for device tracing) is to disable that check on the ROCm platform

/cc @whchung @chsigg

@jaingaurav can you please help merge this change internally. Thank you

gentle ping

gentle ping

@jaingaurav can you please assist this PR to submit internally ?


Listing4-2.js doesn't work

The following line:
if (fieldName.trim().length > 0) {
has this error:
TypeError: fieldName.trim is not a function

The code works OK if you iterate over headers[0] rather than headers:
headers[0].forEach((fieldName, columnIndex) => { 	if (fieldName.trim().length > 0) { 		record[fieldName] = row[columnIndex]; 	} });

I've just tried the code direct from GitHub and it works ok for me.
Here is what I did:
git clone https://github.com/Data-Wrangling-with-JavaScript/Chapter-4.git
cd Chapter-4
npm install
node listing-4.2.js

Output:
> node listing-4.2.js
[ { Mag: '9.5',
    Location: ' Bio-Bio, Chile',
    'Alternative Name': 'Valdivia Earthquake',
    'Date (UTC)': '1960-05-22',
    'Time (UTC)': '19:11',
    Latitude: '38.14°S',
    Longitude: '73.41°W',
    References: 'Kanamori & Anderson, 1975' },
  { Mag: '9.2',
    Location: ' Southern Alaska',
    'Alternative Name':
     '1964 Great Alaska Earthquake, Prince William Sound Earthquake, Good Friday Earthquake',
    'Date (UTC)': '1964-03-28',
    'Time (UTC)': '03:36',
    Latitude: '60.91°N',
    Longitude: '147.34°W',
    References: 'Kanamori & Anderson, 1975' },
  { Mag: '9.1',
    Location: ' Off the West Coast of Northern Sumatra',
    'Alternative Name':
     'Sumatra-Andaman Islands Earthquake, 2004 Sumatra Earthquake and Tsunami, Indian Ocean Earthquake',
    'Date (UTC)': '2004-12-26',
    'Time (UTC)': '00:58',
    Latitude: '3.30°N',
    Longitude: '95.98°E',
    References: 'Duputel et al., 2012' },
  { Mag: '9.1',
    Location: ' Near the East Coast of Honshu, Japan',
    'Alternative Name': 'Tohoku Earthquake',
    'Date (UTC)': '2011-03-11',
    'Time (UTC)': '05:46',
    Latitude: '38.30°N',
    Longitude: '142.37°E',
    References: 'Duputel et al., 2012' },
...

Is this how you run the code?
Maybe you have a different version of Node.js?
I have version 10.15.2.
Please open a terminal and run node --version and tell me which version you are using. If you can tell me that I'll be able to try the code with that version as well.

Hi Ashley,
I found the issue. I originally copied the listing from the the book, and
there's a discrepancy between that version and the listing in GH (which
works OK for me).
At line 12 in the book the return statement wraps the result in an array
whereas the GH version doesn't. See attachment.
Regards,
David
On Mon, 9 Sep 2019 at 22:16, Ashley Davis<EMAIL_ADDRESS>wrote:

I've just tried the code direct from GitHub and it works ok for me.
Here is what I did:
git clone https://github.com/Data-Wrangling-with-JavaScript/Chapter-4.git
cd Chapter-4
npm install
node listing-4.2.js
Output:

node listing-4.2.js

[ { Mag: '9.5',
Location: ' Bio-Bio, Chile',

'Alternative Name': 'Valdivia Earthquake',

'Date (UTC)': '1960-05-22',

'Time (UTC)': '19:11',

Latitude: '38.14°S',

Longitude: '73.41°W',

References: 'Kanamori & Anderson, 1975' },

{ Mag: '9.2',
Location: ' Southern Alaska',

'Alternative Name':

 '1964 Great Alaska Earthquake, Prince William Sound Earthquake, Good Friday Earthquake',

'Date (UTC)': '1964-03-28',

'Time (UTC)': '03:36',

Latitude: '60.91°N',

Longitude: '147.34°W',

References: 'Kanamori & Anderson, 1975' },

{ Mag: '9.1',
Location: ' Off the West Coast of Northern Sumatra',

'Alternative Name':

 'Sumatra-Andaman Islands Earthquake, 2004 Sumatra Earthquake and Tsunami, Indian Ocean Earthquake',

'Date (UTC)': '2004-12-26',

'Time (UTC)': '00:58',

Latitude: '3.30°N',

Longitude: '95.98°E',

References: 'Duputel et al., 2012' },

{ Mag: '9.1',
Location: ' Near the East Coast of Honshu, Japan',

'Alternative Name': 'Tohoku Earthquake',

'Date (UTC)': '2011-03-11',

'Time (UTC)': '05:46',

Latitude: '38.30°N',

Longitude: '142.37°E',

References: 'Duputel et al., 2012' },

...
Is this how you run the code?
Maybe you have a different version of Node.js?
I have version 10.15.2.
Please open a terminal and run node --version and tell me which version
you are using. If you can tell me that I'll be able to try the code with
that version as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Data-Wrangling-with-JavaScript/Chapter-4/issues/1?email_source=notifications&email_token=AC4JUXTYFFBC4RCNGRSCUDTQI24KPA5CNFSM4IUYOIIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6JCB6Q#issuecomment-529670394,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC4JUXRV7NKZBHCYS5POKYLQI24KPANCNFSM4IUYOIIA
.

Ok thanks for letting me know.
Hopefully at some point we'll get the book updated.
For the moment please use GitHub for the latest code examples!
If you spot other problems please report them here.

Also if you haven't already, please follow me on Twitter for updates on my new book: https://twitter.com/ashleydavis75


Investigate the test reporter with github action

Currently it is hard to find the failing tests in by scrolling the CI building logs. I think if we can find a test reporter action to hightlight the failing tests, that could be very helpful. It needs to report from the surefire and failsafe test log files.

This is something I have wanted for a long time.
I looked into it a long time ago. It's a bit tricky to implement, because our build is broken into so many different steps....

@jamesnetherton @zhfeng is anyone already started working on this ? If not I would like to help, thanks!

Thanks for taking a look at this one!

I can try to move this forward. We can keep things simple and generate a summary from the JUnit XML files after tests have completed on each job.
There's a POC of what it'd look like on my fork:
https://github.com/jamesnetherton/camel-quarkus/actions/runs/8897198115#summary-24432612744

Added an initial step for this in https://github.com/apache/camel-quarkus/pull/6076. I will try to improve it over time.


Add StorageTypeValidatorTest

Added test cases for class StorageTypeValidator.java

Can one of the admins verify this patch?

ok to test


fix Issue 14755 - Could -profile=gc also give the number of allocatio…

…ns that led to X bytes being allocated?
https://issues.dlang.org/show_bug.cgi?id=14755

LGTM

Auto-merge toggled on


Linting overhaul

This PR aims to further implement #44, improve on #645, and sorta fixes #681.

Use a shared configuration for all the student editable files: @exercism/eslint-config-javascript
Use a shared configuration for all read-only and maintainer only files: `@exercism/eslint-config-javascript/maintainers
Fix a bug where files inside .meta were not (always) linted
Run the stricter configuration when doing scripts/lint

Student rules
Furthermore, it enables the following rules (on top of the current recommended set) that often resolve actual errors (and are not really style dependent) for students:
Warnings

array-callback-return
eqeqeq
guard-for-in
no-extend-native
no-implicit-coercion
no-promise-executor-return
no-shadow
no-unreachable-loop
require-atomic-updates

These will not block the student (ever), but almost always indicate mistakes. If you'd like to discuss why these were chosen, let me know, and I can give ample examples of actual student code as well as documented examples that these rules solve. Note that none of these rules are listed under "style" rules. In an upcoming update to the analyzer, these warnings will be shown to the user as actionable.
Errors

default-param-last
no-eval
no-unsafe-optional-chaining

These are always mistakes, hence they are errors. In an upcoming update to the analyzer, these warnings will be shown to the user as essential and effectively soft-block the student.
Maintainers / Contributors
Same list as for students but everything is an error. On top of that, the following rules are added to guard for mistakes with import and export statements, which are vital in the stubs and the test files.
In a previous track-wide update we've chosen for named exports (with one or more exceptions) which is why we discourage default exports. Additionally, the extension inclusion/exclusion is for consistency. The unresolved imports ensures all stubs export all the required bindings.
Warnings

import/no-default-export

Errors

import/extensions with { js: 'never', json: 'always' }
import/no-unresolved

Fixes #681

(I intend to merge this Friday the latest but feel free to voice your concerns, ideas, and/or anything else)

reputation/contributed_code/double_major <-- you should apply this label

@neenjaw does that exist?

@ErikSchierboom @iHiD

Great work! Thanks for taking the time to work through this.
 On npm the readme is empty and it does not show a repository.
I mostly like the rules you added.
I would not have picked guard-for-in though. Imo if someone just created a simple object literal and now wants to iterate over it, for-in without guard is just fine. This object literal scenario is also what is most likely to happen when a student uses for-in in an exercise. Forcing the guard although it is not necessary kind of defeats the point of for-in as a readable, short iteration helper. Imo for-in is demonized too much. Just like many things in JavaScript, it has its pitfalls/limitations.
The second thing I am not super happy about is the new formatting for the switch statements (not sure which rule is responsible for the change here). Tbh I never understood the advantage and I thought this "no indentation for the cases" style went out of fashion a while ago. Two reasons why I am not a fan. 1. In all other occurances we always indent the code inside a code block so it makes sense to be consistent. 2. Most docs, tutorials etc show the indented version. When a student comes from a language where indentations matters, the different versions might be confusing.
Feel free to ignore my comments and merge anyway. Just giving my 2 cents.

 On npm the readme is empty and it does not show a repository.

Waiting on Jeremy to create it for me.

https://npm.runkit.com/@exercism/eslint-config-javascript/index.js?t=1618402770885
https://npm.runkit.com/@exercism/eslint-config-javascript/maintainers.js?t=1618402770885

I would not have picked guard-for-in though. Imo if someone just created a simple object literal and now wants to iterate over it, for-in without guard is just fine. This object literal scenario is also what is most likely to happen when a student uses for-in in an exercise. Forcing the guard although it is not necessary kind of defeats the point of for-in as a readable, short iteration helper. Imo for-in is demonized too much. Just like many things in JavaScript, it has its pitfalls/limitations.

@june Yeah. I struggled with this one. So I've seen mistakes in student code because they didn't know, but there are also so many cases where it's fine. I guess what we can do here is remove this one from the config, but use the analyzer to show an informative pitfall if someone uses for in. Do you like that solution?

The second thing I am not super happy about is the new formatting for the switch statements (not sure which rule is responsible for the change here). Tbh I never understood the advantage and I thought this "no indentation for the cases" style went out of fashion a while ago. Two reasons why I am not a fan. 1. In all other occurances we always indent the code inside a code block so it makes sense to be consistent. 2. Most docs, tutorials etc show the indented version. When a student comes from a language where indentations matters, the different versions might be confusing.

Nah, that's prettier, I think. I rather have it indent too. Can you point me to a line/file in this PR where this happens? I will try to find the tool responsible and "configure" it correctly, because I am 💯 % with you.

I guess what we can do here is remove this one from the config, but use the analyzer to show an informative pitfall if someone uses for in.

Sounds like a good solution to me.

Weird. https://prettier.io/playground/#N4Igxg9gdgLgprEAuEAzArlMMCW0AEAEnADYkQDqEATiQCYAUwA5tXHLlM-gLz4A6IABalyggDT5W7eHV74A5IKq06ghZIDOOEghjzUAQxKa4k6AFkI6UwHkAbnGriAvgEp8wflG-58mgHccGDAhBmkOHC4PLyg-PzBDU0URMggFJE9feL8Aelz-CABbSJ84+JdshKS4FJwMrPKc-MKS-AgYEWp8Tir8SvKBlxBxEAgAB1xoTWRQQ2pqCACABXmEGZRjAMMATxnRgCNqQzAAaw4AZXGTqOZkGGp0MxA4IoO4OjoPgBlDLnRDMw4AAxGhFQwwTh3TboGAQEbCGBFEgUITBOCaa5gOAXdbBHD2YI7ZDgTT7EBRUzUGDLY7McHIIwmZ4AK00AA8AELHM6XQwlb5ROCM4ymUZs9kXW66ACK6A6wqQTLFIGu1CpJIOhneJAR42oURgFBwdE6yAAHAAGUb6iCmCjHcYk-UYpyOBEAR3l8FpEw2ICSAFooOwvnQEWwvTg2LTAQylaLnqYijh7o8k9K4HKFSLmaMYNrjaahMgAEz5446W4AYWK8ZemgArAibHAACrajbK572J4ASSgX1gFzABsmAEFBxcYDtdLnTC4XEA seems correct to me. Is that not what you're expecting @junedev?

I looked at that commit that contains only the actual code changes that you posted. Maybe it was not reflecting the latest version. Playground example is correct.

I checked the latest version in the branch. Switch statement is correctly formatted there. Sorry for the confusion. 🙈

I checked the latest version in the branch. Switch statement is correctly formatted there. Sorry for the confusion. 🙈

I think you were right. So something removed the indentation and then formatting added it back 🤷🏽

Solved with https://github.com/exercism/eslint-config-javascript/pull/1


⚠ Bofrost.es has degraded performance

In 49c31bf, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1567 ms

Resolved: Bofrost.es performance has improved in c44f9de after 6 minutes.


Creating endpoint with CRUD for documents and chunks

I added file views.py that have declared types of response for client's CRUD request like( GET,POST,PUT,DEL) for chunks and documents, other files exclude .env.example have declared model schemas, url and routing. I think document's response for CRUD is incorect, because i didn't use foreignkey in document's schemas.
Code based on this site: https://medium.com/@hbakri/introducing-django-ninja-crud-ee937bd2ea65

@bafaurazan next time - please remember commits are formatted like this
title

some description, remember the empty space above

please, fix the commit message, here's how: https://stackoverflow.com/a/41987851

P.S. when you're ready, remember to select reviewers - I've seen this PR only because I watch all the events in the repo

and Patryk if you could send me some links, that could help me solve the problems with the code, it would help me a lot

should I add pyrightconfig.json file to the project to define how pyright should work?


no-op: Remove unused Types::all call

Motivation

This was at some point moved into DispatchResult::merge. It looks like
at that time we forgot to delete this Types::all here.
Test plan

n/a

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_QxwlYrbqv4Jn5Y
→ https://go/builds/bui_QxwlyamrbWRhEF
→ https://go/builds/bui_QxwlldDqqmpbyY


Update pulsar to 1.18.3

About this PR
📦 Updates org.testcontainers:pulsar from 1.16.3 to 1.18.3
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.testcontainers", artifactId = "pulsar" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.testcontainers", artifactId = "pulsar" }
}]

labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #186.


[untested] added Sk6822 led device support

1. Tell us something about your changes.
I've added Sk6822 led device support but haven't tested with real LEDs
2. If this changes affect the .conf file. Please provide the changed section
"device": {
"colorOrder": "rgb",
"invert": false,
"output": "/dev/spidev0.0",
"rate": 2230000,
"rewriteTime": 5000,
"type": "sk6822spi"
},
3. Reference an issue (optional)
nope

thx a lot! I also can't test it, but it looks good.

I tested the debug output and it looks correct.


https://docs.chain.link/reference results in Page Not Found (404)

Visiting page (link found via wiki : Node Operator Resources) results in 404. As far as I can tell, API documentation is kind of sparse so a working reference is pretty valuable.

Redirected to the main page for now. Several references exist in our docs but no single reference should be at ./reference right now.

Hey oh ok got it and thanks for looking into it.
The "sparse" documentation comment is referencing the Node API specifically. I've only been able to find the following links (both of which seem somewhat incomplete in terms of docs for that API afaict):

https://docs.chain.link/docs/chainlink-node-api-reference/
https://github.com/smartcontractkit/chainlink/wiki/REST-API


[Feature]: add support for Kubernetes 1.27

Requirement
Upgrade dependencies and CI to use Kubernetes 1.27
Problem
.
Proposal
No response
Open questions
No response

The idea here is to run all our e2e tests on k8s 1.27. Similar to https://github.com/jaegertracing/jaeger-operator/pull/2161


Replace non standard _itoa

This PR replaces MSVC specific _itoa with standard sprintf.
Rational for not using std::to_string or equivalent : _itoa is usually used in C strings heavy contexts, mixing C++ strings in there would only clutter the code for no good reason. Feel free to disagree, I can change my mind if necessary.
Integer formating is size limited so I used snprintf only where a buffer overflow was possible.
Code in OVP/D3D* was not modified since it will obviously needs MSVC to compile anyway.

@TheGondos please don't use sprintf. Its days in c++ are numbered. With c++20 we got the Formatting library which is the replacement for it.
But, even without the Formatting library, in many cases you can use std::to_string::data() as long as you using it in the same expression and not storing it.
Or, rewrite small bits of code to switch completely to std::string. The code actually becomes simpler.

@TheGondos please don't use sprintf. Its days in c++ are numbered. With c++20 we got the Formatting library which is the replacement for it.
But, even without the Formatting library, in many cases you can use std::to_string::data() as long as you are using it in the same expression and not storing it.
Or, rewrite small bits of code to switch completely to std::string. The code actually becomes simpler.

I'll take a rain check on that one. There was a similar issue in NASSP and trying to use C++ constructs just snowballed out of control ; it was ultimately rejected in favor of keeping good old sprintf...
Let's face it, C++ is not the most appropriate tool for working with strings. It took 20 years to introduce the glorified pointer+length that is a string_view, the very object that does not guarantee your char pointer will reference a NUL terminated string, rendering it completely useless if you need to pass it to standard functions.
Is C better? Probably not, but at least the code is already there.
This PR is about portability, not C++ guideline shininess. If the core team wants to go in that direction, that's fine, I'll adapt it ; but for now I'll wait for more comments ;-)

@TheGondos this is OT, but since we are here: Are you developing under Linux or Windows? I've been using msvc under wine, but I was thinking of switching to clang-cl. Just curious how you are doing it.

I'm currently working on Windows, I don't want to mess something up when I commit^^

@TheGondos FYI with 32-bit build I get this:
Y:\orbiter\Src\Orbiter\Mfd.cpp(1150): warning C4477: 'sprintf' : format string '%lld' requires an argument of type '__int64', but variadic argument 1 has type 'int'
Y:\orbiter\Src\Orbiter\Mfd.cpp(1150): note: consider using '%d' in the format string
Y:\orbiter\Src\Orbiter\Mfd.cpp(1150): note: consider using '%Id' in the format string
Y:\orbiter\Src\Orbiter\Mfd.cpp(1150): note: consider using '%I32d' in the format string

because INT_PTR in 32-bit mode is int and not int64_t:
https://learn.microsoft.com/en-us/windows/win32/winprog/windows-data-types#INT_PTR

Also, please give some love to the OVP clients:

OVP/D3D7Client/D3D7Enum.cpp:                strcat(cbuf, _itoa(dupeIDCount, idStr, 10));
OVP/D3D7Client/VideoTab.cpp:    SetWindowText (GetDlgItem (hTab, IDC_VID_WIDTH), _itoa (data->winw, cbuf, 10));
OVP/D3D7Client/VideoTab.cpp:    SetWindowText (GetDlgItem (hTab, IDC_VID_HEIGHT), _itoa (data->winh, cbuf, 10));
OVP/D3D7Client/VideoTab.cpp:            (LPARAM)_itoa (usebpp, cbuf, 10));
OVP/D3D7Client/VideoTab.cpp:        (LPARAM)_itoa (bpp, cbuf, 10));
OVP/D3D9Client/VideoTab.cpp:        if (_itoa_s(data->winw, cbuf, 32, 10)) return;
OVP/D3D9Client/VideoTab.cpp:        if (_itoa_s(data->winh, cbuf, 32, 10)) return;
OVP/D3D9Client/VideoTab.cpp:            if (_itoa_s (h, cbuf, 32, 10)) return;
OVP/D3D9Client/VideoTab.cpp:            if (_itoa_s (w, cbuf, 32, 10)) return;

Yes, I can work around the 32bit warning but I think the root cause is using an INT_PTR to represent either an ExternMFD pointer or an MFD Id. Maybe it would be better to use a std::variant instead (I replaced it with a struct containing a union on my linux branch)

For now I would just do an ugly #ifdef BUILD64 to handle the sprintf warning. Hopefully soon we can get rid of all sprintfs.

Yes, I can work around the 32bit warning but I think the root cause is using an INT_PTR to represent either an ExternMFD pointer or an MFD Id. Maybe it would be better to use a std::variant instead (I replaced it with a struct containing a union on my linux branch)

For now I would just do an ugly #ifdef BUILD64 to handle the sprintf warning. Hopefully soon we can get rid of all of them now that we are at c++20.

The Id can either be an ExternMFD pointer, or an integer between 0 and MAXMFD (12) for internal MFDs. This function is only valid for internal MFDs

What you did in your PR was great.


Implement rate limit handling

Implements a rate-limit function to support #233 and resolve #237
func rateLimited(err error) bool {
	if err == nil {
		return false
	}
	rerr, ok := err.(*github.RateLimitError)
	if ok {
		var d = rerr.Rate.Reset.Time.Sub(time.Now())
		//hit rate limit, sleeping
		time.Sleep(d)
		return true
	}
	aerr, ok := err.(*github.AbuseRateLimitError)
	if ok {
		var d = aerr.GetRetryAfter()
		//hit abuse mechanism, sleeping
		time.Sleep(d)
		return true
	}
	return false
}

implemented as
for {
    err := APIRequest()
    if err != nil {
        if rateLimited(err) {
            continue
        } else {
            return err
        }
    }
}

in related GitHub v3 API requests.

@itsdalmo I might be a bit pre-emptive in my implementation here, I'll see if we can mock and test this behavior later, do you have an idea on how to be proceed?

OMG, we just hit this today, :+1: for posting this patch!

@d Please lock down to v0.21.0 until this gets carefully reviewed and implemented :-)

I think the change here looks reasonable, but considering that we are hitting the abuse rate limit I take that as an indication that we are doing something we should not be doing here. Looking at the diff between v0.21.0 and v0.22.0 I noticed this line. I.e., when fetching pull requests we no longer filter out only those that are open but instead we always fetch everything, which for repositories with a lot of history and activity will always result in hitting a rate limit no matter how many times we retry.
As such, I think think the best fix here is to either roll back the change I linked above or to do the filtering in the GraphQL query (instead of fetching everything and then filtering in the resource as is currently done). And I suggest we try that before implementing a silent retry for rate limit errors 🤔

While working on updating #189 and testing it I ran into this exact issue and @itsdalmo hit the nail on the head.  Whereas before on initial fetch of PRs to filter on we only queried for OPEN ones we now query for basically ALL of them.  This resulted in a check that takes a long time to run.  I've been doing manual testing but am sure if I had it running every minute I'd for sure have hit the rate limit ... which doesn't reset for an hour I think.


Aptik not recognising youtube-dl as a package installed using apt-get

Ubuntu 14
I need to remove Ubuntu, as I need dual boot of Windows 7 & Ubuntu.
I tried to backup all PPA packages using Aptik, but it didn't show youtube-dl

How did you install youtube-dl? Have you ever updated youtube-dl by running youtube-dl -U?

This sounds like out of scope of youtube-dl. You may refer our FAQ for instructions on installation or updating. Note that youtube-dl in the official Ubuntu 14 repos is outdated.


Method [send] does not exist on view.

Attempt to display error page using the following:
return view('errors.404')
This produced the following error:
BadMethodCallException in View.php line 390: Method [send] does not exist on view.

    in View.php line 390
    at View->__call('send', array()) in index.php line 55
    at View->send() in index.php line 55

If this is in a middleware then you need to actually create a response.

return Response::make(view('errors.404'), 404);

NB, you should be doing that anyway, otherwise you'd be returning 200 OK for your error page, which isn't right.

The following resolved it:
response()->make(view('errors.404'), 404)

Yeh, that's basically the same code.

this is old, but still want to suggest >>
if ($exception instanceof NotFoundHttpException) {
return parent::render(view('errors.404'), $exception);
}

@jafaronly  Thanks :)


tag is placing [U+200E][U+200F] characters at the end of the  when rendering.

Describe the Bug
On rendering React Emails that are using the  tag, I'm getting a large string of unreadable characters ([U+200E][U+200F]).
My setup is using  CSS for formatting. I have each email created in seperate .jsx files and importing the components into a main MainEmail.jsx page for rendering and processing.   In my preview, I do not see the unreadable characters as they show as regular spaces.  (See below):
     {{FirstName}}, An account on Martet has been created for you.
However,  when the email is sent, the unreadable characters show up as [?].  Below is an example of the same text above where I copied the above text into a text document.   I've attached a screenshot of Gmail where it shows the unreadable characters as well as VSCode showing the value of the characters.
     {{FirstName}}, An account on Martet has been created for you. � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �
Setup:  My app was built using Create React App and hasn't been migrated to Nextjs yet.  Using Tailwind for CSS for the entire app.  I installed the React Email components using npm inside VSCode into my larger project.
I installed all React Email components using the npm install @react-email/components -E commands vs. installing each component seperately.  Therefore enabling me to import all with 1 import command vs. having seperate import commands for each component.
In terms of sending emails, I'm currently saving each rendered HTML file as a file on Azure and calling up the file via a backend process to fill in dynamic variables and the sending via C#.   I do not yet have an operational Email provider as I'm looking to use Resend once C# becomes available.
I'm seeing this issue in the following email clients:  Gmail Web, Yahoo Web, Outlook Web, Outlook Desktop (mac), Yahoo App for IPhone.   If needed, I can provide more screenshots.
Render Command in React:  {render(subSection, {pretty: true}).replaceAll('[','{{').replaceAll(']','}}')}

I'm doing the bracket replacements for my dynamic variables.  My back end process is currently using '{{' for the variable replacements but that gives react some fits so I use '[' in React to avoid any compile errors.   I did confirm this issue exists regardless of the replace commands, meaning it's present when I render with the replace and without the replace.

Let me know if you need any additional info regarding configuration.

Which package is affected (leave empty if unsure)
No response
Link to the code that reproduces this issue

To Reproduce
Below is an example react email I'm building.    I have separate components built for the Email Header and Footers but otherwise just straightforward React with Tailwind.
import * as React from 'react';
import {
Body,
Button,
Container,
Column,
Head,
Heading,
Hr,
Html,
Img,
Link,
Preview,
Row,
Section,
Tailwind,
Text,
} from '@react-email/components';
import { MartetEmailHeader, BusinessEmailHeader } from './EmailHeader';
import { MartetFooter } from './MartetFooter';
import { BusinessFooter } from './BusinessFooter';
export function Information() {
return (

    <Preview>
        You have an update on your account.
    </Preview>

    <Tailwind>

            <Container className='flex w-full max-w-[1080px] border border-solid border-gray-400 rounded rounded-lg overflow-hidden mx-auto'>

                <MartetEmailHeader />

                    <Text className='mb-2 flex justify-left'>
                        Hey  [FirstName]!
                    </Text>
                    <Text className='font-medium'>
                        [BodyText]
                    </Text>
                    <Text className='font-medium'>
                        Thanks,
                        Team Martet
                    </Text>

                <MartetFooter />

            </Container>

    </Tailwind>

);

}
Expected Behavior
Expect the unreadable characters to not be present and thus in Email previews, it shouldn't show the ??????.
What's your node version? (if relevant)
v16.14.2

I am not sure if this is connected to my problem, but after updating to the latest @react-email/preview I am not receiving mails in Outlook anymore. If I remove the Preview tag it works.

I'm facing the same issue, on the latest version of components v0.0.6
It seems to be this function in preview.tsx that's causing them to render:
const renderWhiteSpace = (text: string) => {
  if (text.length >= PREVIEW_MAX_LENGTH) {
    return null;
  }
  const whiteSpaceCodes = "\xa0\u200C\u200B\u200D\u200E\u200F\uFEFF";
  return
{whiteSpaceCodes.repeat(PREVIEW_MAX_LENGTH - text.length)}
;
};

I had this 'issue' but as far as I can tell, it's actually by design. They're invisible spaces, which is how a 'Preview' feature works - it adds these invisible spaces to stop the body of the email being drawn into the email preview area, e.g. in notifications.
These characters don't seem to be compatible with AWS Cognito emails, so what I've done is do a sed find/replace in the email after exporting, replacing them with    instead.
E.g. in python:
email = email.replace("\xa0\u200c\u200b\u200d\u200e\u200f\ufeff", "  ")

This has retained the Preview feature on the few clients I've tested (desktop Outlook, iOS Outlook app)

@rretlaw Could your issue be related to your font not supporting the characters we use for the white spaces? I've also tested this on Gmail but can't really replicate the same issue.


UniLinksPlugin.h:1:9: fatal error: 'Flutter/Flutter.h' file not found

My Flutter doctor report is.
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.2.0, on macOS 11.2.3 20D91 darwin-x64, locale
en-AU)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor
--android-licenses
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] Connected device (2 available)
! Doctor found issues in 1 category.

Have you tried this?
https://github.com/flutter/flutter/issues/70895#issuecomment-744734693

Have you tried this?
flutter/flutter#70895 (comment)

I'm having same issue and the fix via the link doesn't help.
This seems to be a result of having to address the IPHONEOS_DEPLOYMENT_TARGET issue by editing the ./ios/Podfile and changing the post_install method from
post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

TO:
post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '10.0'
    end
  end
end

And switching this back fixes the issue, however then I'm unable to run the app in the simulator without getting the The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.3.99 error.
Any suggestions?  This was working a few months ago..

Thanks for reply I have fix this issue.

Have you tried this?
flutter/flutter#70895 (comment)

I'm having same issue and the fix via the link doesn't help.
This seems to be a result of having to address the IPHONEOS_DEPLOYMENT_TARGET issue by editing the ./ios/Podfile and changing the post_install method from
post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

TO:
post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '10.0'
    end
  end
end

And switching this back fixes the issue, however then I'm unable to run the app in the simulator without getting the The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.3.99 error.
Any suggestions? This was working a few months ago..

Thanks for reply I have fix this issue.

Did you fix it by changing the post_install method in the ./ios/Podfile?
Are you able to run your application in the iOS simulator?

No Not this way I am adding a line in podfile where adding check related to Simulator version 8.
My Code that I added then this issue resolved is:
Adding this Line resolve my issue.
flutter_additional_ios_build_settings(target)
`
post_install do |installer|      installer.pods_project.targets.each do |target|        flutter_additional_ios_build_settings(target)        target.build_configurations.each do |config|          config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '9.0'        end      endend
`

Thanks for reply I have fix this issue.

Did you fix it by changing the post_install method in the ./ios/Podfile?
Are you able to run your application in the iOS simulator? If so, could you please share your fix?

Yes It's Installed on Simulator Alhumdulilha after putting setting line within pod file where Simulator check added.

Thanks for reply I have fix this issue.

Did you fix it by changing the post_install method in the ./ios/Podfile?
Are you able to run your application in the iOS simulator? If so, could you please share your fix?

Ok, that helped give me some insight.   I ran into some additional issues due to using OneSignal for push notifications (which requires a minimum iOS target of 10, but was throwing a building for iOS Simulator, but linking in object file built for iOS error), and managed to resolve this as well.   For anyone else running into similar issues, my updated ./ios/Podfile now looks like:
target 'OneSignalNotificationServiceExtension' do
  use_frameworks!
  pod 'OneSignalXCFramework', '3.2.1'
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
    target.build_configurations.each do |config|
        config.build_settings['ENABLE_BITCODE'] = 'NO'
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '10.0'
    end
  end

There is also an alternative method that can be used so that you are able to define the mimimal deployment target via the platform variable defined within the Podfile:
post_install do |installer|
  puts 'Determining pod project minimal deployment target'
  pods_project = installer.pods_project
  deployment_target_key = 'IPHONEOS_DEPLOYMENT_TARGET'
  deployment_targets = pods_project.build_configurations.map{ |config| config.build_settings[deployment_target_key] }
  minimal_deployment_target = deployment_targets.min_by{ |version| Gem::Version.new(version) }
  puts 'Minimal deployment target is ' + minimal_deployment_target
  puts 'Setting each pod deployment target to ' + minimal_deployment_target
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
    target.build_configurations.each do |config|
      config.build_settings[deployment_target_key] = minimal_deployment_target
      config.build_settings['ENABLE_BITCODE'] = 'NO'
    end
  end
end

And then just uncomment the second line at the top of the Podfile and replace with your deployment target version:
# Uncomment this line to define a global platform for your project
platform :ios, '10.0'


Adding API doc

The aim of this MR is to update the doc by:

adding the API documentation including typed objects from rust. This is done by adding a .pyi to the project
Add docstrings
Add notebooks examples in the doc
Update compilation_rules
Improve the main page

I have tested different thing  about API documentation with automatic type hints of rust objects used in the library:

Adding a python interface (.pyi) file is very useful for having pyqrlew rust objected type checked inside python but this is ignored completely by sphinx for generating the documentation.
There is a way to tell pyo3 the python signature with text_signature option directly on the method however this generated a ugly looking doc where the functions signature was added as docstring of the function and also not very well formatted. Playing with sphinx autodoc parameters such as autodoc_typehints didn't generated a documentation as wanted.

Finally, I opted for what seems a good compromise to me:

adding the a rich doc strings on rust objects in the google-stype format specifying the type of function arguments.
adding 'sphinx.ext.napoleon', which understands google and numpy style doc strings and 'sphinx.ext.intersphinx'  links to objects
This makes the typing of arguments clear in the description of each method even if the signature is not typed.

Merci Andi


fix kyuubi session leak caused by engine stop

Why are the changes needed?

to close https://github.com/apache/kyuubi/issues/4847
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[X] Run test locally before make a pull request

The test failure looks related, could you please fix it first? will take a detail look after dinner.

Codecov Report

Merging #4848 (0c393cd) into master (4c3c36e) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master   #4848   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         557     557
  Lines       30696   30733   +37
  Branches     3994    3998    +4
======================================
- Misses      30696   30733   +37

Impacted Files
Coverage Δ

...rk/sql/execution/arrow/KyuubiArrowConverters.scala
0.00% <ø> (ø)

.../org/apache/kyuubi/session/KyuubiSessionImpl.scala
0.00% <0.00%> (ø)

...g/apache/kyuubi/session/KyuubiSessionManager.scala
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

The test failure looks related, could you please fix it first?
I have already fixed the test failure. Could you please review it?

Thanks, the change makes sense to me.

Thanks, merged to master

There's no milestone marked on this PR. Is this merged to 1.8.0 only?

thanks for the top, updated, it was merged before cutting branch-1.8

Thanks, understand. It should be helpful for production use.


Automated cherry pick of #6531: Fix NodePortLocal rules being deleted incorrectly due to

Cherry pick of #6531 on release-1.15.
#6531: Fix NodePortLocal rules being deleted incorrectly due to
For details on the cherry pick process, see the cherry pick requests page.

/test-e2e

/skip-conformance
/skip-networkpolicy

/test-windows-e2e


Windows Server 2016 / SQL Server 2016

Hi,
please update this article according Windows Server 2016 Support in CU6 and SQL Server 2016 Support in CU7.

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 7c475b5d-09ed-7f58-86d4-27f28e33ef7a
Version Independent ID: f0ad50f3-ea93-9424-6de8-a0b778e90b23
Content: Serveranforderungen für Skype for Business Server 2015
Content Source: Skype/SfbServer/plan-your-deployment/requirements-for-your-environment/server-requirements.md
Product: skype-for-business-itpro
GitHub Login: @MicrosoftHeidi
Microsoft Alias: heidip

@irongeekger - @ - Thank you for submitting this feedback. And thanks for the engagement @JeffBrownTech.
This is a good catch now that CU7 is out. I was able to get this into the backlog for the Skype team. The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

Hi @irongeekger , this was updated. Thank you for your feedback.


gcloud SDK CLI authentication scopes

I'm having an error when generating auth tokens in the terminal with the cloud-platform scope.
When I run:
gcloud auth application-default login --scopes https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/cloud-platform

I have an error in the token generation:
ERROR: (gcloud.auth.application-default.login) There was a problem refreshing your current auth tokens: None could not be converted to bytes
Please run:

  $ gcloud auth login

to obtain new credentials.

If you have already logged in with a different account, run:

  $ gcloud config set account ACCOUNT

to select an already authenticated account to use.

The suggested actions (re-login and change account) don't work.
My colleagues (with the same permissions as myself) have no issue running this command and authentication. This issue is persistent for my account in other machines.
Both the SDK documentation and gemini suggestions have no solution. I tried all of these:
Troubleshooting Steps

Re-authenticate with gcloud auth login:

Open your terminal or command prompt.
Run: gcloud auth login
Follow the prompts to authenticate with your Google account in your web browser.
Check GOOGLE_APPLICATION_CREDENTIALS (if applicable):

If you're using a service account key file:

Ensure the GOOGLE_APPLICATION_CREDENTIALS environment variable is set correctly and points to the absolute path of your service account key file.
Verify that the key file exists and has the correct permissions.

Clear gcloud Credentials Cache:

Run: gcloud auth application-default revoke
Try the original command again: gcloud auth application-default login --scopes https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/cloud-platform

Update or Reinstall Google Cloud SDK:

Update: gcloud components update
Reinstall (if the issue persists): Follow the instructions for your operating system on the official Google Cloud SDK installation page: https://cloud.google.com/sdk/docs/install

@thekoma to review

@thekoma fixed this issue: https://github.com/GoogleCloudPlatform/genai-for-marketing/blob/main/infra/README.md by setting the right scopes as per the forum above.


mesh: notify tortoise about applying only verified layers

followup for https://github.com/spacemeshos/go-spacemesh/pull/5514
we apply layers to the state when tortoise either verified them, or in-order layer was certified by hare,
but not yet verified by tortoise.
OnApplied call is used to notify tortoise that information about consensus state was used and tortoise is free to get rid of it.
however there is a possible race, such as:

tortoise notified that hare=true
mesh applied block with hare=true
tortoise notified that valid=true
mesh called OnApplied for previous, without reading latest information.

this race would lead to missing validity field in blocks table.

bors merge

bors merge


Create tesco.txt

@leomon2009 First stage of verification passed, official domain is tecnologicodecoacalco.edu.mx as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: http://www.tecnologicodecoacalco.edu.mx/TESCO/acerca/tramitesyservicios.htm

@leomon2009 There are substantial sections at the official website, which give 404 error instead of valuable information about the school's program. Thus, I cannot verify the eligibility of the school for the trusted list.
Please apply for free educational license with an official document which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
I have to close the request without merging.
Thank you for your understanding!


feat(config): create and add translate and link element

As per discussion in #378

Couple lint errors:
/home/ubuntu/stardust/src/lib/config.js
  3:19  error  Missing trailing comma                         comma-dangle
  4:2   error  Newline required at end of file but not found  eol-last

Did you plan on wiring this in anywhere, or just adding the config for now?  Thanks much!

Current coverage is 98.86% (diff: 100%)

No coverage report found for master at 89456fa.

Powered by Codecov. Last update 89456fa...3d25348

@tomitrescak it looks like this PR includes typings also now.  We'll to merge only the config for this PR.  I suggest creating a branch off of your master that only has the config work on it so only that work will be merged.  Alternatively, you could keep this PR open and just temporarily remove the typings so only the config is being proposed.

I have removed typings from tgis PR and will create new one

In it's current state, I'm not sure this is something we should add. For the use-case referenced in #378 (usage with react-router) this won't actually have any effect. The Link doesn't actually do anything unless there's a to prop (see: https://github.com/ReactTraining/react-router/blob/master/modules/Link.js#L116).
My issues:

This is very a specific use (only elements where an href prop is passed) and it already doesn't work with one of the main React-based routing libraries. This is probably the biggest red flag.
Wherever this would be working, you're already going to be passing a path as a prop (whether via href or to or whatever your library calls for). I don't think adding as={Link} adds much more complexity so I don't think this really saves a lot of work.

@levithomason - would love your thoughts here as well.

Although the original intent of the config was for a i18n function and I think we should allow that, I agree that users should use as={Link} instead of allowing an anchorElement config option.
Thanks @jcarbo for the clarification.  Apologies @tomitrescak as I had not fully realized the goal here.  If you'd like to use an element as a Link, you should do so like this:
<Menu>
  <Menu.Item as={Link} to='/home'>
    Home
  </Menu.Item>
</Menu>

See: http://react.semantic-ui.com/introduction#augmentation


Implement MMR retrieval at cassIO level

It might make sense for the cassIO VectorTable class to offer its own MMR implementation.
(Currently for the langchain integration case this is done at langchain level, but arguably the right place is cassIO).

Let's look at LlamaIndex first before trying to do this refactoring.

Right, Llama has its own implementation and for now we'll piggyback on it :)

Langchain also has a selector https://python.langchain.com/docs/modules/model_io/prompts/example_selectors/mmr


Backwards-compatible io

This PR adds backwards-compatibility so that old OrbitDB addresses can be read.
Depends on https://github.com/orbitdb/orbit-db-store/pull/43, https://github.com/orbitdb/ipfs-log/pull/234, https://github.com/orbitdb/orbit-db-access-controllers/pull/20

LGTM :+1:


Feature/inception variable for layers

This is a:

[x] refactor of existing functionality
[ ] bug fix PR with no breaking changes
[ ] new functionality

Link to Issue

Closes #92
We also mentioned the need for this functionality in #113 and #110
Description & motivation

Allow users to modify the list/name of layers in their dbt project using variables instead of requiring them to update/deactivate/create models from the package to reflect their setup.

Integration Test Screenshot

Checklist

[x] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[ ] BigQuery
[x] Postgres
[ ] Redshift
[ ] Snowflake

[x] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)
[ ] I have added an entry to CHANGELOG.md

Does list_layers map directly to our idea of model_type in int_all_graph_resources? If so should we change the name of one of them so that the match? Either:

model_types and model_type
list_layers and layer

Updated the branch following the comments from the team


openmetadata: add nodeSelector, affinity and tolerations on test connection pod

What this PR does / why we need it :

In a cluster where all nodes use taint, test pod will fail to schedule and keep in Pending state. This PR will make sure that test pod will be scheduled on the same node as openmetadata server pod.

Type of change :

[x] Bug fix
[ ] Improvement
[ ] New feature
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[x] Title of the PR starts with chart name
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] All new and existing tests passed.

Reviewers

Thanks @riupie , shipping in 1.5.4 :raised_hands:


Add Sengled E1F-N9G

Added fingerprint for Sengled E1F-N9G
Tested as working against my Hub v2 and 2x E1F-N9G bulbs.

Added with 42786b2


CUDA issues

When trying to use JAX + GPU in a CentOS8 container, I have the following warning message show up:
>>> import jax.numpy as np
>>> a = np.ones(4)
2020-06-26 10:14:51.996044: E external/org_tensorflow/tensorflow/stream_executor/cuda/cuda_driver.cc:314] failed call to cuInit: CUDA_ERROR_SYSTEM_DRIVER_MISMATCH: system has unsupported display driver / cuda driver combination
2020-06-26 10:14:51.996405: E external/org_tensorflow/tensorflow/stream_executor/cuda/cuda_diagnostics.cc:313] kernel version 440.36.0 does not match DSO version 440.33.1 -- cannot find working devices in this configuration
/home/docker/anaconda/envs/my-project/lib/python3.7/site-packages/jax/lib/xla_bridge.py:125: UserWarning: No GPU/TPU found, falling back to CPU.
  warnings.warn('No GPU/TPU found, falling back to CPU.')

When in the container, the output of nvidia-smi is:
(base) [docker@4d16b48b1a22 ~]$ nvidia-smi
Fri Jun 26 10:14:29 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.36       Driver Version: 440.36       CUDA Version: 10.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 108...  Off  | 00000000:04:00.0 Off |                  N/A |
|  0%   25C    P8    12W / 250W |    318MiB / 11178MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+

The Dockerfile specification is available as a gist here.
I have tried asking around on Twitter some friends at NVIDIA. It seems like the host driver is 440.36, but when I install the CUDA toolkit, the version that gets installed is 440.33, resulting in the DSO version error. I am working under the assumption that I can't change the host driver, so I'm stuck with whatever I can get into the container. Have you all encountered this issue before? Is there someone on the team who has experience with XLA + CUDA?

I don't think this is an XLA or JAX issue in particular, it sounds to me like the docker file needs fixing. Do any CUDA programs work in this configuration (e.g., say TF or PyTorch)? I'm not sure there's much we can do here; is there a way you can install the matching CUDA toolkit version in the docker configuration?

I'm not sure, but I did get a pingback from the NVIDIA folks pointing me to how their containers are built. It's exactly what I needed! https://gitlab.com/nvidia/container-images/cuda/-/blob/master/dist/10.2/centos8-x86_64/runtime/cudnn7/Dockerfile
I'm going to close the issue so it doesn't clutter up the issue tracker :smile:.


Rename React methods

Everything should still work the same way as before.

I also did this before I saw it was an open PR #460 but mine converts one of these to componentDidUpdate since it appears to be be a side effect

Thanks for letting me know, @brandonc . I will take a look tomorrow.

@GeorgiSTodorov - can we close this and just use https://github.com/dcos-labs/ui-kit/pull/460?

@mperrotti , that's fine with me.