Functionality broken for GWorkspaceReportsAPISentinelConnector following code update

Describe the bug
A reference before assignment error for the local variable 'next_page_token' is now triggering on our GoogleWorkspace Function App.
Full Error
Exception while executing function: Functions.GWorkspaceReportsAPISentinelConnector Result: Failure
Exception: UnboundLocalError: local variable 'next_page_token' referenced before assignment
Stack:   File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/dispatcher.py", line 406, in _handle__invocation_request
call_result = await self._loop.run_in_executor(
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/dispatcher.py", line 648, in _run_sync_func
return ExtensionManager.get_sync_invocation_wrapper(context,
File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/extension.py", line 215, in _raw_invocation_wrapper
result = function(**args)
File "/home/site/wwwroot/GWorkspaceReportsAPISentinelConnector/init.py", line 342, in main
result_obj, next_page_token = get_result(line,latest_timestamp,end_time)
File "/home/site/wwwroot/GWorkspaceReportsAPISentinelConnector/init.py", line 162, in get_result
return result_activities, next_page_token
Screenshots

Azure Function App:

Runtime version: <IP_ADDRESS>
Operating System: Linux

Hi @Shammack, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 20-12-2023. Thanks!

Hi @Shammack, Could you please share exceptions from app insights and also the invocation logs details logs in text or csv format, need some details about when on wards this function app stopped, and it worked earlier or not with all the configurations in place, if needed we can have a team's meeting, please share convenient time slots and email id, Thanks.

Hi @Shammack, Could you please have a look at above comment. Thanks!

Hi @Shammack ,gentle reminder, Could you please share exceptions from app insights and also the invocation logs details logs i.e. traces from app insights in text or csv format, need some details about when on wards this function app stopped, and it worked earlier or not with all the configurations in place, if needed we can have a team's meeting, please share convenient time slots and email id,will take it forward on this issue, Thanks.

Hi @Shammack ,Since we have not received a response in the last 5 days, we are closing your issue (https://github.com/Azure/Azure-Sentinel/issues/9563  )as per our standard operating procedures. If you still need support for 	his issue, feel free to re-open at any time. Thank you for your co-operation!


Update metadata.

Update urls and version numbers in the metadata.json file.

I don't think the test-failures are related to the metadata change.

@Dan33l Tests passed.


A DTS Issue for tca9546a multiplexor driver

Hi,
I am trying to use a bme sensors over the tca9546 a multiplexor, here is the dts defination. When I call my sensor  by DEVICE_DT_GET(DT_ALIAS(temp_sensor)); macro I am getting main.c:80: undefined reference to __device_dts_ord_117 error in complining time although it works when I call mux channel instead of sensor. But this time im getting runtime error because program doesnt write/read correct sensor register addresses.
error with restart loop:
*** Booting Zephyr OS build v3.2.99-ncs1 ***
initializing...
Found device "mux_i2c@1", getting sensor data
*** Booting Zephyr OS build v3.2.99-ncs1 ***
initializing...
Found device "mux_i2c@1", getting sensor data
*** Booting Zephyr OS build v3.2.99-ncs1 ***
initializing...
Found device "mux_i2c@1", getting sensor data
*** Booting Zephyr OS build v3.2.99-ncs1 ***
initializing...
Found device "mux_i2c@1", getting sensor data

Where am I doing wrong or missing something?
aliases:
aliases {
		temp-sensor = &envir_sens;
		humidity-sensor = &envir_sens;
		pressure-sensor = &envir_sens;
};

dts:
&i2c1 {
	compatible = "nordic,nrf-twim";
	pinctrl-0 = <&i2c1_default>;
	pinctrl-1 = <&i2c1_sleep>;
	pinctrl-names = "default", "sleep";
	mux:tca9546a@70 {
		compatible = "ti,tca9546a";
		reg = <0x70>;
		status = "okay";
		#address-cells = <1>;
		#size-cells = <0>;
		ch0:mux_i2c@0 {
			compatible = "ti,tca9546a-channel";
			reg = <0>;
			status = "okay";
			#address-cells = <1>;
			#size-cells = <0>;
			yic_gnss:yic91009ebgg@42 {
				compatible = "yic,yic91009ebgg";
				vin-supply = <&pwrout6>;
				reg = <0x42>;
			};
		};
		ch1:mux_i2c@1 {
			compatible = "ti,tca9546a-channel";
			reg = <1>;
			status = "okay";
			#address-cells = <1>;
			#size-cells = <0>;
			envir_sens: bme680@76 {
				status = "okay";
				compatible = "bosch,bme680";
				// vin-supply = <&pwrout1>;
				reg = <0x76>;
			};
		};
		ch2:mux_i2c@2 {
			compatible = "ti,tca9546a-channel";
			reg = <2>;
			status = "okay";
			#address-cells = <1>;
			#size-cells = <0>;
			optical: vcnl4040@60 {
				compatible = "vishay,vcnl4040-extr";
				reg = <0x60>;
				led-current = <50>;
				led-duty-cycle = <320>;
				proximity-it = "8";
				als-it = <80>;
				vin-supply = <&pwrout7>;
				int-gpios = <&gpio0 8 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;   // connected to the io expander
			};
		};
		ch3:mux_i2c@3 {
			compatible = "ti,tca9546a-channel";
			reg = <3>;
			status = "okay";
			#address-cells = <1>;
			#size-cells = <0>;
			bq_bat: bq27z561@55{
				compatible = "ti,bq274xx";
				reg = <0x55>;
				int-gpios = <&gpio0 16 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;
				design-voltage = <3300>;
				design-capacity = <1000>;
				taper-current = <100>;
				terminate-voltage = <2800>;
			};
		};
	};
};

prj.conf
CONFIG_STDOUT_CONSOLE=y
CONFIG_GPIO=y
CONFIG_I2C=y
CONFIG_CBPRINTF_FP_SUPPORT=y
CONFIG_SENSOR=y
CONFIG_BME680=n
CONFIG_ADXL362=n
CONFIG_BQ274XX=n
CONFIG_BME680_NET=y
CONFIG_I2C_TCA954X=y
CONFIG_I2C_TCA954X_ROOT_INIT_PRIO=61
CONFIG_I2C_TCA954X_CHANNEL_INIT_PRIO=62

void main(void)
{
	printf("initializing...\n");
	bool isSensorBmeActive = true;
	int64_t timestamp = 0;
/*************************** BME680 **********************/

	//const struct device *bme_dev = DEVICE_DT_GET(DT_NODELABEL(ch1)); // no compiling error but it doesnt work
	const struct device *bme_dev = DEVICE_DT_GET(DT_ALIAS(temp_sensor));

	if (bme_dev == NULL) {
		/* No such node, or the node does not have status "okay". */
		printk("\nError: no bme device found.\n");
		return;
	}

	if (!device_is_ready(bme_dev)) {
		printk("\nError: Device \"%s\" is not ready; "
		       "check the driver initialization logs for errors.\n",
		       bme_dev->name);
		return;
	}
	printk("Found device \"%s\", getting sensor data\n", bme_dev->name);

	while (1)
	{
		/* measuring T H P */
		k_sleep(K_MSEC(1000));

		 timestamp = k_uptime_get();
		if(isSensorBmeActive)
		{
			struct sensor_value bmeValue[BME_CHANNELS];
			double value_array[BME_CHANNELS];

			sensorBme_getData(bme_dev, &bmeValue[0]);

			value_array[0] = sensor_value_to_double(&bmeValue[0]);
			value_array[1] = sensor_value_to_double(&bmeValue[1]);
			value_array[2] = sensor_value_to_double(&bmeValue[2]);
			printk ("tst: %d, tmp: %.2f, prs: %.2f, hum: %.2f \n",(uint32_t)timestamp, value_array[0],value_array[1],value_array[2]);
		}
	}
}

BTW, I am working on nrf 9160 sip based custom board with ncs 2.2.0

The Zephyr fork in nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including cd16a8388f71a6cce0cea871f75f6d4ac8f56da9, with some nRF Connect SDK specific additions. The current nRF Connect SDK main branch is based on revision cd16a8388f of Zephyr.

I fixed issue by editting sensor driver.c . rest of them are ok
static const struct sensor_driver_api bme680_api_funcs = {
    .sample_fetch = bme680_sample_fetch,
    .channel_get = bme680_channel_get,
};

static struct bme680_data bme680_data = {
    .dev.delay_ms = &k_sleep,
    .dev.write = &bme680_reg_write,
    .dev.read = &bme680_reg_read,
    .dev.intf = BME680_I2C_INTF,
};

static const struct bme680_config bme680_config = {
    .bus = I2C_DT_SPEC_INST_GET(0)
};

DEVICE_DT_INST_DEFINE(0, bme680_init, NULL, &bme680_data,
              &bme680_config, POST_KERNEL, CONFIG_BME_SENSOR_INIT_PRIORITY,
              &bme680_api_funcs);

to
static const struct sensor_driver_api bme680_api_funcs = {
	.sample_fetch = bme680_sample_fetch_netfeasa,
	.channel_get = bme680_channel_get_netfeasa,
};

static struct bme680_data bme680_data = {
	.dev.delay_ms = &k_sleep,
	.dev.write = &bme680_reg_write,
	.dev.read = &bme680_reg_read,
	.dev.intf = BME680_I2C_INTF,
};

#define BME_IDEFINE(inst)							\
	static const struct bme680_config bme680_cfg_##inst = {		\
		.bus = I2C_DT_SPEC_INST_GET(inst),				\
	};									\
	SENSOR_DEVICE_DT_INST_DEFINE(inst, bme680_init, NULL,			\
		&bme680_data, &bme680_cfg_##inst,			\
		POST_KERNEL, CONFIG_SENSOR_INIT_PRIORITY,			\
		&bme680_api_funcs);

DT_INST_FOREACH_STATUS_OKAY(BME_IDEFINE)


Custom API Schema Bodies

Hi.
Feature Request
It would be helpful if there was an option to specify the various api schemas by hand, i.e, Custom Request/Response Bodies that need to be sent to the same url(for example a viewset) but with different methods.
For example, if using a customized serializer, that involves a custom create method, It would be helpful if I could specify what the API schema would actually be: The Request Body, Request Method,  Response - Success, Request Code - Success , Response - Failure, Response Code - Failure.
For example, I have attached a screenshot in which, the POST request uses a custom request body than what's directly available in the model.Screenshot
If I could specify the request body that the request would need, as well as the sample responses (failures, success) that would be nice.
Hope I was descriptive enough.

Is this even possible? am trying to wrap my head around how to create  custom rest api endpoint documentation, for example, Oauth routes and @detail_routes

@monk8800 It isn't. That's why I opened an issue requesting this.


[crashpad] Fix build on linux

Fetch required lss package on linux
Describe the pull request

What does your PR fix?
Fix building on linux

Which triplets are supported/not supported? Have you updated the CI baseline?
linux

Does your PR follow the maintainer guide?
Yes

@MarekMaslanka Could you sign the cla?

@MarekMaslanka crashpad build failed on Linux, could you continue to fix it? You can download the error log from: https://dev.azure.com/vcpkg/c1ee48cb-0df2-4ab3-8384-b1df5a79fe53/_apis/build/builds/44538/artifacts?artifactName=failure logs for x64-linux&api-version=6.0&%24format=zip

Pinging @MarekMaslanka for response.

Sorry, I'm very busy last time and forgot about this issue. I'll look at this on weekend. Meanwhile, can you tell me what is the proper way to fetch clang++ in vcpkg-fasion way?

You could install llvm on VCPKG.

Is any other way than adding llvm to "Build-Depends" in CONTROL file?

/bin/sh: 1: clang++: not found
Need to install clang on Linux machine. sudo apt-get install clang

The compiler used is defined by the triplet; a port should not be overriding trying to use another compiler. Dropping vm-update.

If you want to do this in a way in keeping with the triplet system, you would need to edit the default Linux triplets to add something like:
if (PORT STREQUAL "crashpad")
set(VCPKG_C_COMPILER "clang")
set(VCPKG_CXX_COMPILER "clang++")
endif()

It's likely that folks who want to use crashpad themselves might be broken though since the existing contract is that the installed tree can be used with whatever the end user wants.
It would be nice too if it could be easily detected that clang is not installed and emit a help message here but I'm not sure how involved proving that the user has a working clang++ is. Perhaps the warning could be emitted unconditionally?

@MarekMaslanka
Could you please address the above suggestion?

Wouldn't a decent solution be to create a triplet, that sets the compiler to clang on linux and then have the crashpad port set so that it only accepts that specific triplet?
The downside is that people need to manually specify that triplet, while right now with this PR it "just works" if your default compiler is set to clang - which it is on my system.

@MarekMaslanka
Is work still being done for this PR?

Thanks for the PR; we're closing this for now since there's been no response. If you'd like to continue working on it, please reopen and ping us!


Component:  Image with caption QA testing - Production level version

User Story

As a [user role below]:
developer using the ibm.com Library Image with caption

I need to:
have a version of the pattern or component that has been tested for accessibility compliance as well as on multiple browsers and platforms

so that I can:
be confident that my ibm.com web site users will have a good experience

Additional information

Browser Stack link
Browser Standard
Browser versions to be tested:  Tier 1 browsers will be tested with defects created as Sev 1 or Sev 2.  Tier 2 browser defects will be created as Sev 3 defects.
Platforms to be tested, by priority:  1)  Desktop  2)  Mobile  3)  Tablet
Mobile & Tablet iOS versions: 13.1 and 13.3
Mobile & Tablet Android versions: 9.0 Pie and 8.1 Oreo
Browsers to be tested:  Desktop: Chrome, Firefox, Safari, Edge, Mobile: Chrome, Safari, Samsung Internet, UC Browser, Tablet: Safari, Chrome, Android
Accessibility Checklist
Creating a QA bug
Design specs
Functional specs
Development issue (#2361)
Image with caption optionally launches lightbox media viewer on click
User interactions when clickable
Icon to indicate it launches
whole image is optionally clickable
Caption is same as lightbox media viewer's heading

Acceptance criteria

[ ] Accessibility testing is complete.  Pattern is compliant.
[ ] All browser versions are tested
[ ] All operating systems are tested
[ ] All devices are tested
[ ] Defects are recorded and retested when fixed

@Praveen-sr @chetankan This is a new component that the team just discovered had been missed.  I have added the work to this sprint.  As we talked about earlier, we will be tracking the testing progress to help determine when the code can be frozen and the regression testing starts for the May release.
cc:  @ljcarot @jeffchew

5/14/2020:  Both function and accessibility testing are finished.


spec: explicitly require python3-koji

Fixes #503

already solved in #502

@rpitonak not really, that PR only has BR and not runtime reqs, so it doesn't solve the problem

/packit copr-build

/packit copr-build

/packit copr-build

/packit copr-build

/packit copr-build


Updating Service APIs meeting times

Based on the results of https://strawpoll.com/w5p5peyq7, it seems like Wednesdays at 11am are going to work best for most people. This updates our community page to reflect that.

/lgtm


Embedded navigation does not start navigation

It makes the route, but the navigation does not start

Are you able to share the code that you're using? or are you just using the example code?

I am using the following code:
MapBoxNavigationView(
options: MapBoxOptions(
initialLatitude: -16.715928922800856,
initialLongitude: -49.29239587178779,
zoom: 13.0,
// tilt: 0.0,
// bearing: 0.0,
enableRefresh: false,
alternatives: true,
voiceInstructionsEnabled: false,
bannerInstructionsEnabled: true,
allowsUTurnAtWayPoints: true,
mode: MapBoxNavigationMode.drivingWithTraffic,
// mapStyleUrlDay: "https://url_to_day_style",
// mapStyleUrlNight: "https://url_to_night_style",
units: VoiceUnits.metric,
simulateRoute: false,
language: "pt_BR"),
onRouteEvent: _onRouteEvent,
onCreated:
(MapBoxNavigationViewController controller) async {
_controller = controller;
                  await controller.buildRoute(wayPoints: wayPoints);
                  await _controller!.startNavigation();
                })

it looks like the navigation occurs in the background, i can hear the instruction as I navigate

Have you find any solution for this issue?

this issue should now be resolved in v0.5.4 - it was starting the navigation but just not displaying it back correctly
so now you should be able to activate the embedded navigation


vm crash in 1.24-dev-0.0+ triggered by something in dartdoc

Working on a change for dartdoc in this branch:  https://github.com/dart-lang/dartdoc/tree/warnings-update
I have encountered a crash in the dart VM, as demoed by Travis:  https://travis-ci.org/dart-lang/dartdoc/jobs/231722764
and locally (with some debug prints to show what dartdoc was writing at the time of the crash):
/tmp/sdkdocs/dart-html/DomMatrix/m33.html
Dumping native stack trace for thread 11891
/tmp/sdkdocs/dart-html/DomMatrix/m34.html
/tmp/sdkdocs/dart-html/DomMatrix/m41.html
./tmp/sdkdocs/dart-html/DomMatrix/m42.html
/tmp/sdkdocs/dart-html/DomMatrix/m43.html
  [0x00000000008e130a] dart::Assembler::j(dart::Condition, dart::Label*, bool)
  [0x00000000008e130a] dart::Assembler::j(dart::Condition, dart::Label*, bool)
  [0x00000000009baf34] dart::BinarySmiOpInstr::EmitNativeCode(dart::FlowGraphCompiler*)
  [0x0000000000962729] dart::FlowGraphCompiler::VisitBlocks()
  [0x000000000096e0f5] dart::FlowGraphCompiler::CompileGraph()
  [0x00000000008bd7fc] dart::CompileParsedFunctionHelper::Compile(dart::CompilationPipeline*)
  [0x00000000008be3c6] Unknown symbol
  [0x00000000008bf2a6] dart::Compiler::CompileOptimizedFunction(dart::Thread*, dart::Function const&, long)
  [0x00000000008c0cc6] dart::BackgroundCompiler::Run()
  [0x0000000000bf28bd] dart::ThreadPool::Worker::Loop()
  [0x0000000000bf276a] dart::ThreadPool::Worker::Main(unsigned long)
  [0x0000000000aaa8e9] Unknown symbol
-- End of DumpStackTrace

Process finished with exit code 134 (interrupted by signal 6: SIGABRT)

Running the same code with 1.23 works fine, and working without the change in the warnings-update branch works fine -- however, dartdoc's SDK documentation mode uses different input, of course, for different versions.  First broken version is 1.24-dev-0.0.
The crash seems to occur at different places somewhat non-deterministically from the Dart code's perspective but has the same backtrace in all instances; most of the time we're somewhere in the middle of documenting DomMatrix class but we never seem to crash in the exact same place.  Nothing I'm doing in the branch seems bad or obviously likely to cause a problem, but without the change, the crash vanishes.

I've narrowed it down to one bit that seems to cause the crash.  Sadly the crash is not reproducible using the dart debugger or I'd be able to get you more data:
https://github.com/dart-lang/dartdoc/blob/warnings-update/lib/src/model.dart#L223
Here, calling accessor.name will sometimes, indeterminately, cause a crash.  If I don't call accessor.name, say if I just return null, or if I call other members of accessor like nameLength or enclosingElement, there doesn't seem to be a problem.  The crash is clearly data dependent; something in the dart:html library seems to exercise this path, but since the dart debugger can't reproduce the problem I'm having difficulty localizing it.  This code is not part of the delta in the branch, but we are using it more heavily in the branch due to the new documentationFrom method.

Thanks for looking into this yourself @jcollins-g! Just to give you a bit of background - based on the stack trace, it's a crash in the optimizing JIT compiler - which runs in the background concurrently with the main execution thread and optimizes hot functions. This probably explains why the crash is non-deterministic - because background compiler is inherently racing with the execution... This also explains why you can't reproduce the bug in the debugger - whenever you use debugger VM usually stops background compiler and prevent more functions from being optimized to give you better debugging experience.
From the stack trace I can also guess that one of the most likely reasons for the crash is that we are trying to emit a jump to a NULL deoptimization label.
Could you post the command line / instructions that reproduce the crash most reliably for you? I am away today, but I will take a close look tomorrow.

Some other things I've tried that all still result in a crash:  changing the declaration of accessor to an explicit type (PropertyAccessorElement), not calling replaceFirst on the name but just calling the name in a print statement, running without checked mode.
It is almost certainly a coincidence but it seems strangely linked to #29600.  The crash will only occur if the accessor is actually a PropertyAccessorMember rather than a PropertyAccessorElementImpl, and goes away if I repeatedly call baseElement on the member and then call name on the PropertyAccessorElementImpl.

Some basic instructions that should reproduce this quickly:
First, ensure that you have a 1.24+ Linux SDK installed.  Then:
git clone git@github.com:dart-lang/dartdoc.git
git checkout origin/warnings-update
pub get
dart bin/dartdoc.dart --output /tmp/sdkdocs --sdk-docs --show-progress
[... to crash ...]

@mraleph thanks for looking at this, please let me know if I can be of further help.

I've closed the original PR motivating this but left the branch in place for you to reproduce the problem; dart-lang/dartdoc#1428 has the workaround so I can be unblocked while you investigate.

@jcollins-g thanks!
I have already figured out what the problem is - my original guess was correct. I just need to think a little bit more about how to fix it best.

CL with a fix is up for review: https://codereview.chromium.org/2891113002/

Should be fixed now.


What to do with tags?

tags are useful for grouping operations for displaying in the UI, but how can we use them for client-side codegen? Also, is there a neat way to generate them in server-side?

I'm trying out the actix-web plugin on quite a large api and tags would be really useful for grouping in the UI. Our handlers are already grouped into modules and so I think that would be a natural way to produce the grouping, ideally describing the tag with an inner macro attribute (but this doesn't exist yet - https://github.com/rust-lang/rust/issues/54726)

For actix-web plugin, we have an approach in #219


How to prevent top jsdoc comments from disappearing while compiling with --declaration flag

I'm compiling my lib for distributing , one of steps is adding banner at the top of each file. Something like this:
/**
 * @overview MegaLib v1.36.0 - 2018-04-04 22:47
 * @author SuperCompany
 * @version 1.2.3
 * @copyright 2018 SuperCompany
 * @license Private
 */

While adding banners I don't know what follows next and usually it's some import. So a file will look like this:
/**
 * @overview MegaLib v1.36.0 - 2018-04-04 22:47
 * @author SuperCompany
 * @version 1.2.3
 * @copyright 2018 SuperCompany
 * @license Private
 */
import {MyClass1} from "script-comments-refs";
import {MyClass2} from "script-nocomments-norefs";
import {MyClass3} from "script-nocomments-refs";
export interface IndexLib { Class2: MyClass2, Class3: MyClass3 }

If I compile such file with --declaration the first import will be removed (as it doesn't contribute to module API):
index.d.ts:
import { MyClass2 } from "script-nocomments-norefs";
import { MyClass3 } from "script-nocomments-refs";
export interface IndexLib {
    Class2: MyClass2;
    Class3: MyClass3;
}

As you can see the banner disappears.
So it disappears for js output:
index.js:
define(["require", "exports"], function (require, exports) {
    "use strict";
    exports.__esModule = true;
});
//# sourceMappingURL=index.js.map

Is there any way to keep top jsdoc comments for all files in *.d.ts and *.js (besides adding a fake comments)?

A comment is attached to the declaration that follows it directly. if the declaration is not emitted, then the comment is not either.
A comment can be detached if it appears at the beginning of the file, and has a line break before the first declaration. detached comments are preserved in the output..
so simply make sure you have a new line after your comment and before the first import.

Thanks. It does help for keeping comments in js, but not in .d.ts - there they are stripped out.
It's not a big problem indeed (js is more important) but it'd be nice to have the same behavior for all .d.ts.
ts:
/**
 * @overview MegaLib v1.36.0 - 2018-04-04 22:47
 * @author SuperCompany
 * @version 1.2.3
 * @copyright 2018 SuperCompany
 * @license Private
 */

import {MyClass1} from "script-comments-refs";
import {MyClass2} from "script-nocomments-norefs";
import {MyClass3} from "script-nocomments-refs";

export interface IndexLib { Class2: MyClass2, Class3: MyClass3 }

d.ts:
import { MyClass2 } from "script-nocomments-norefs";
import { MyClass3 } from "script-nocomments-refs";
export interface IndexLib {
    Class2: MyClass2;
    Class3: MyClass3;
}

Something else is going on.. here is what am seeing locally:
c:\test\23164>type a.ts
/**
 * @overview MegaLib v1.36.0 - 2018-04-04 22:47
 * @author SuperCompany
 * @version 1.2.3
 * @copyright 2018 SuperCompany
 * @license Private
 */

import {MyClass1} from "script-comments-refs";
import {MyClass2} from "script-nocomments-norefs";
import {MyClass3} from "script-nocomments-refs";

export interface IndexLib { Class2: number, Class3: number }

c:\test\23164>tsc --v
Version 2.9.0-dev.20180402

c:\test\23164>tsc --d

c:\test\23164>type a.js
"use strict";
/**
 * @overview MegaLib v1.36.0 - 2018-04-04 22:47
 * @author SuperCompany
 * @version 1.2.3
 * @copyright 2018 SuperCompany
 * @license Private
 */
Object.defineProperty(exports, "__esModule", { value: true });

c:\test\23164>type a.d.ts
/**
 * @overview MegaLib v1.36.0 - 2018-04-04 22:47
 * @author SuperCompany
 * @version 1.2.3
 * @copyright 2018 SuperCompany
 * @license Private
 */
export interface IndexLib {
    Class2: number;
    Class3: number;
}

I've tried typescript@next and it works (in the same way as in your case).
Before I was using TS 2.6, 2.7 and 2.8 (no comments in d.ts), with 2.9 comments are emitted in d.ts.

thanks. we have rewritten the declaration emitter in 2.9, let me investigate more why it was not working before.

in 2.8 and before we only emitted detached comments if they were copywriter (start with /*!). now we are emitting them correctly all the time.


Handle incoming SMS from devices as Event

Key changes:

Schema changes applies to "non-mssql" DB engines only. It "nulls" all "phone" duplicates and add unique constraint
Added map phone -> devices
Added new type of Event - textMessage

If DB is MS then behavior will be next: In case phone has duplicates last added device will be mapped.
Frankly, I do not like the changes very much, especially null phone if it is "" in addDevice and  updateDevice methods. Only multiple nulls are possible with unique constraint and it comes as "" from web-client by default.
But I do not have other more beautiful solution may be you have another idea...

Maybe we should just allow phone to be non-unique? Then either use first/last found device, like you do for MS SQL already anyway.

I have replaced the commit.
Do not require uniqueness for phone now.
Also map only not empty string.
Behavior will be the next: last added/updated device phone is actual.

Done
Moved function
Renamed variable
Removed set clearing

Replaced with Iterator

Merged, thanks.


Requirement for enum name to be ALL_CAPS

The requirement that an enumerator name be all caps is not documented. While this is the style shown in the documentation of the standard enum library, it is not enforced. Removing the .isupper() checks resolves this issue. You might, however, want to substitute checks to see if an attribute is a callable method for the .isupper() calls.

Hi, @robbmcleod
Sorry for the docs missing the notification about the requirement for ALL_CAPS for enums' members. We'll fix this ASAP.
As for the requirement itself it's just a way to avoid unresolveable cases while still following style guides. Look at the late-init example in the docs. Since we declare a non-member property halved_value that calculates to a member (different results for different members) we can't resolve this when not enforcing ALL_CAPS requirement for members.
Since then there's another issue with that: you can't declare non-members having ALL_CAPS names. They will be automatically treated as enums' members, but if and only if either check succedes:

it has a value assigned on declaration
it is type-hinted with the Enum class' name

This will avoid the mess:
In [102]: class Test(metaclass=FastEnum):
     ...:     ONE: 'Test'
     ...:     TWO: 'Test'
     ...:     THREE: 'bytearray'
     ...:     __slots__ = ('THREE', )
     ...:     def __init_late(self):
     ...:         self.THREE = bytearray(3)
     ...:

In [103]: list(Test)
Out[103]: [<Test.ONE: 1>, <Test.TWO: 2>]

In [104]: Test.ONE.THREE
Out[104]: bytearray(b'\x00\x00\x00')

In [105]: Test.ONE.THREE is Test.TWO.THREE
Out[105]: False


Latest tag doesn't point at latest real version

When I look at https://github.com/TencentCloud/tencentcloud-sdk-go, the "latest version" on the right hand sidebar lists 3.0.10.
The latest appears to actually be v1.0.x: https://github.com/TencentCloud/tencentcloud-sdk-go/releases
Please update the latest tag to point at that so that it's easier to see what is actually the latest release.

the bot just tag new update, but no release is created, those release information is manually created long time ago.
they are deleted now, please just refer to the tags


feat: Integrating probability

Builds off of #16 and #35
I've changed it to calculate probability per-row

Awesome, thank you!

Looks good, better implemented than my first lazy draft haha. About the per row probability - is this the true chance of getting that pattern? I considered calculating it like this but since the pattern is decided at first independantly from the rest of the values, shouldn't they have a chance to appear based on which patterns are remaining, rather than the number of rows remaining? I'm not sure on the stats maths on this, so feel free to correct me.

I don't believe it's quite right - because I think the actual conditional probability would also be based on where your day value is in the range, and how likely it is a pattern would have matched.
Buuut, I think it's a reasonable approximation. Definitely open to making it more accurate - but a rough guess is likely helpful anyway


[Enhancement] more timely memory release about cloud native pk table compaction

Why I'm doing:
In current implementation, we use reset_column to release column memory. But in fact reset_column will call std::vector().clear() which won't release memory immediately.
What I'm doing:
Use reset(nullptr); instead of reset_column, so I can release memory immediately.
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

Do we need to replace reset_column with reset(nullptr) in the other places of cloud native pk table?


Add a default list of headers ignore

There is some headers are known to be handled correctly by track2 SDK by default and we don't want to appear in method signature and generated code, that we might wish to document in Swagger/RestAPI doc.
This issue about when we recognized those headers, they shall not be generated in any headers of M4. This allows correct documentation for customers of RestAPI and external consumers of Swaggers, while not bloating our SDKs with things that the pipeline is handling automatically.
We shall implement that with  --ignore-spec-headers (happy to discuss the name), where the default value should be traceparent,tracestate by default (see for details). This allows for further customization if necessary.
We might add more default later, like request-id, etc. will discuss when necessary.
FYI @johanste

Would help us address https://github.com/Azure/autorest.csharp/issues/782


[BUG] TypeError: fs.readFile is not a function

Describe the bug
Updating to the latest version of tsed 7.61.1 while trying to render an EJS file, i get the error TypeError: fs.readFile is not a function
https://github.com/tsedio/tsed/blob/production/packages/engines/src/utils/cache.ts#L80
It seems that the methd read inside of cache.js now imports fs-extra but fs-extra does not have the method readFile.
It might be worth noting i am using ESM

To Reproduce

install latest TSED under ESM (might not be relevent)
set up EJS
set up a @View() in controller to ejs file
load the page

Expected behavior
the file is rendered and page loads
Code snippets
No response
Repository URL example
No response
OS
Windows 11
Node version
v20.11.0
Library version
7.61.1
Additional context
No response

Hello @VictoriqueMoe
Thanks for the detailled I’ll try to fix that tomorrow. Maybe use fs-extra in this case isn’t relevant.
I recently updated the fs-extra version but the CI haven’t detected this issue.
I’ll come back to you when the bug is solved ;)
See you

Hello @VictoriqueMoe Thanks for the detailled I’ll try to fix that tomorrow. Maybe use fs-extra in this case isn’t relevant. I recently updated the fs-extra version but the CI haven’t detected this issue.
I’ll come back to you when the bug is solved ;) See you

awesome thanks! i just reverted version for the time beaing and it works. not surw why fs-extra was introdiced here or why. but yea :)
big fan of the framework, i use it extensively on 3 of my large projects and it's wonderful! thanks for the hard work!

:tada: This issue has been resolved in version 7.61.2 :tada:
The release is available on:

v7.61.2
GitHub release

Your semantic-release bot :package::rocket:

Thank you

I can confirm this fixes the issue, thank you! <3


Hide omitted trackers

Description
If trackers are omitted in the settings, they still are visible
// An example of ConsentCookie initialized with a custom config
ConsentCookie.init({
    'connections': {
      'cc': {
        'initstate': 'disabled'
      },
      'iq': {
        'initstate': 'optout'
      },
      'ga': {
        'initstate': 'disabled'
      }//, Google Tag Manager omitted
      //'gtm': {
        //'initstate': 'disabled'
      //}
    },
    'moreinfolink': 'https://www.humanswitch.io/over/privacy/'
  });
</script>

Expected Behavior
I expected the omitted tracker to not-be-shown
Actual Behavior
It shows
Possible Fix
don't initialize trackers not mentioned in the init

That's why I created the template in English :smile:

if you are ok with it i'll try to create an pull request

You can always make pull request. I have not yet had the time to add the contributing info.
Just make sure that the code is ES6 and you are using the eslint config provided by the project as code standard.

it's somewhat more specific and debate for how to init, it specifically act's on the connection already being present in the ConsentCookie

fixed by #15


Commenting out the wifi ota to make room for BLE in flash

We really probably should optimize this more later
We already chatted about this change in another PR, but that was against master

Oops you deleted some of the telemetry code

Oh, because I rebased against the original dev-1.0 that didn't have it; let me fix that


Added a flexible appbar gallery demo

Added a "Patterns/Scrolling Techniques" demo that resembles the "Flexible Space with Image" from the Material design spec - https://www.google.com/design/spec/patterns/scrolling-techniques.html#scrolling-techniques-scrolling
Demos for the other app bar arrangements are still needed.

lgtm. this code looks really clean, it's great.
don't forget to squash your commits


Differences Between Configuration File and CLI Parameters

[X] Defect
[ ] Feature Request or Change Proposal

Defects
Make sure that these boxes are checked before submitting your issue -- thank you!

[X] Included gnatsd -DV output

[53885] 2017/09/06 22:13:19.303170 [INF] Starting nats-server version 1.0.2
[53885] 2017/09/06 22:13:19.303297 [DBG] Go build version go1.7.6
[53885] 2017/09/06 22:13:19.303419 [INF] Listening for client connections on <IP_ADDRESS>:4222
[53885] 2017/09/06 22:13:19.303503 [DBG] Server id is iO48Q6XRiHtMYpcZk6LzTj
[53885] 2017/09/06 22:13:19.303542 [INF] Server is ready

[X] Included a Minimal, Complete, and Verifiable example

$ cat minimal.conf
debug: true

cluster {
    host: '<IP_ADDRESS>'
    port: 6222

    routes = [
        nats://nats:6222
    ]
}

$ nslookup nats
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

** server can't find nats: NXDOMAIN

NOTE: The fact that nats doesn't (initially) resolve is on purpose.
Versions of gnatsd and affected client libraries used:
At least v1.0.2.
OS/Container environment:
OSX, Linux (x64), Docker.
Steps or code to reproduce the issue:
$ gnatsd -c minimal.conf
Error looking up host with route hostname: lookup nats: no such host

$ gnatsd --cluster nats://<IP_ADDRESS>:6222 --routes nats://nats:6222 --debug
[54226] 2017/09/06 23:20:11.465586 [INF] Starting nats-server version 1.0.2
[54226] 2017/09/06 23:20:11.465842 [DBG] Go build version go1.7.6
[54226] 2017/09/06 23:20:11.466074 [INF] Listening for client connections on <IP_ADDRESS>:4222
[54226] 2017/09/06 23:20:11.466087 [DBG] Server id is 5bc9CwfjHPdcQcIJiAZFL3
[54226] 2017/09/06 23:20:11.466091 [INF] Server is ready
[54226] 2017/09/06 23:20:11.466397 [INF] Listening for route connections on <IP_ADDRESS>:6222
[54226] 2017/09/06 23:20:11.466538 [DBG] Trying to connect to route on nats:6222
[54226] 2017/09/06 23:20:11.473372 [DBG] Error trying to connect to route: dial tcp: lookup nats: no such host
[54226] 2017/09/06 23:20:12.477985 [DBG] Trying to connect to route on nats:6222
[54226] 2017/09/06 23:20:12.479305 [DBG] Error trying to connect to route: dial tcp: lookup nats: no such host
[54226] 2017/09/06 23:20:13.483669 [DBG] Trying to connect to route on nats:6222
[54226] 2017/09/06 23:20:13.485205 [DBG] Error trying to connect to route: dial tcp: lookup nats: no such host
[54226] 2017/09/06 23:20:14.489127 [DBG] Trying to connect to route on nats:6222
[54226] 2017/09/06 23:20:14.490479 [DBG] Error trying to connect to route: dial tcp: lookup nats: no such host

Expected result:
I would expect both behaviours to be the same — if my understanding of configuration is correct, minimal.conf should produce the exact same behaviour as providing the --cluster nats://<IP_ADDRESS>:6222 --routes nats://nats:6222 --debug parameters to gnatsd. In the end, both commands would make gnatsd sit on a loop attempting to establish the route until nats resolves.
Actual result:
If the route is specified in the configuration file gnatsd exits upon checking only once that nats does not resolve.

This is somehow timely. I am working on some rework/fixes of command line parsing, but with my local changes, both now behave the same, but with the Error looking up host with route hostname: lookup nats: no such host failure, not going into the loop. I will have a look.

@kozlovic going into the loop would be the desired behaviour in my scenario — in a Kubernetes deployment, for instance, nats won't immediately resolve and it would be useful to have gnatsd make at least a few retries. Would that be possible?

Ok, this is caused by RemoveSelfReference() which is in main.go. When configuring cluster from the config file, Routes is the array of routes and is populated. The function was trying, as the name suggests, to remove routes to self. I had in the past make sure that a route to self is detected and ignore at runtime, so in my upcoming PR the call to this function will be removed.
Note: when you provide the routes from command line only, this function was invoked before Routes was created from the routes string, bypassing this test.

@kozlovic so what will end up being the behaviour?

On the contrary. I am going to remove the call that was making it fail right away on startup. So it will go into the loop.

@kozlovic that's great 🎉 Thanks for taking the time to look into this.


Default to Python 3.11

Once #879 merges and we let enough time pass that we're completely happy with the Python 3.11 builds, we should switch the default Python over to 3.11 ... we'd need to run all the tests using it, update the helm chart / docker compose, etc.
Probably worth waiting until after the beta rolls out to make that change though.

It's a good suggestion to wait, since I can see how a lot of libraries that users will be installing does not have support for python 3.11 :)

Given that 3.11 doesn't look like it'll be in Ray anytime soon, I'm going to close this one (we can revisit if/when we're able to get #879 in)


[Help] VRAM required for model inference and enable multiple GPUs

Wonderful job! I would love to deploy it locally with two 4090 GPUs, each with 24GB of VRAM, but I keep getting a 'cuda out of memory' error when loading clima-13b.
Therefore, I have two questions:

How much VRAM is required for each model's inference?
How can I correctly set up and enable multiple GPUs?

Thanks!

How much VRAM is required for each model's inference?

24GB is enough for 7b model inference, but for the 13b model you'd need to split it across your two GPUs (see below how to do that).

How can I correctly set up and enable multiple GPUs?

If you are asking about inference, try adding device_map="auto" to your load arguments, as is done for the
webui here. This should split your model across your two GPUs.

Thank you for the comment!
It is running normally now.


Bugfix

Fixed a bug that caused sync issues in video

Please resolve a conflict.

I just fixed the conflicts. You may now merge the pull request


[BUG] - [Object object] printed as tag value

Briefly describe the bug.
In proposal page, a space is not printed correctly, and shown as [Object object]
How can we reproduce the bug?

Go to a proposal
View the source code
Search for [Object
See error

What is the expected behaviour?
Remove the space value, as it's not a valid html property
Can you attach screenshots?

Can you provide your device specific details below?

Device Type - [ex. Desktop or Mobile]
Device OS - [ex. Android, MacOS, Windows, iOS]
OS Version - [ex. iOS 11, Windows 10]
Browser - [ex. chrome, safari]
Browser Version - [ex. 101]
Wallet - [metamask, portis, walletconnect]
Space - [ex. ENS, Gitcoin]
Any additional information we should know -

Also in notify component, there are many like this

hi

Patche-robledo6

snapshot-master.zip

(url)


Add : Weather App

@microsoft-github-policy-service agree [company="{(I'm a Student)}"]

@microsoft-github-policy-service agree

Thank you @Kunal-Khairnar-05 for your suggestion. This is a great project, and launch into React. For now, this is beyond the scope of material these lessons are intended to cover, so the best place to share would be in Show and Tell.
We also have a Intro to React workshop that would be great for you to review and provide thoughts on how better we can utilize that for new React learners.
Closing this PR so you can share this sample project within Discussions. When we build out the ability to onboard additional projects to our repo for extra practice and exercises, we will announce to the community. Thank you!


NIFI-11510 - Upgrade Box SDK to 4.1.0

Summary
NIFI-11510 Upgrade Box SDK to 4.1.0
https://developer.box.com/changelog/#2023-04-24-box-java-sdk-v410-released
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[ ] Apache NiFi Jira issue created

Pull Request Tracking

[ ] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[ ] Pull Request based on current revision of the main branch
[ ] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

LGTM and glad it doesn't require any code or logic changes. The current test failure seems unrelated, will wait for the rest of the checks then merge to 1.x and 2.x as the Jira requests.


Leaderboards appear to not render in game anymore

Need a bit more testing on this, but multiple people have claimed that they're not loading in game anymore.

One character typo...


The TestNG version is "[WORKING]" when we add TestNG into our shaded package.

TestNG Version

Note: only the latest version is supported
7.5.x/7.6.x

Expected behavior
org.testng.internal.Version.VERSION should be correct
Actual behavior
org.testng.internal.Version.VERSION = "[WORKING]"
Is the issue reproducible on runner?

[ ] Shell
[x] Maven
[ ] Gradle
[ ] Ant
[ ] Eclipse
[ ] IntelliJ
[ ] NetBeans

Test case sample

Please, share the test case (as small as possible) which shows the issue
NO

Contribution guidelines
NO

in org.testng.internal.Version
private static String initVersion() {
    String version = Version.class.getPackage().getImplementationVersion();
}

when we use shaded package, there is no TestNG version in META-INF\MANIFEST.MF.

There will be the other error when we use Eclipse TestNG plugin:
[failed to get TestNG version from class java.lang.IllegalArgumentException: invalid version "[WORKING": no-numeric "[WORKING]"

We can generate the pom.properties with TestNG class:
version=${testng.version}
groupId=org.testng
artifactId=testng

I think you'll have the same issue if you try to shade Hibernate: https://github.com/hibernate/hibernate-orm/blob/main/hibernate-core/src/main/java/org/hibernate/Version.java
Maybe you should not shade TestNG.

Hello,  we don't use hibernate and TestNG version is very important for our test framework and we use all-in-one shaded jar file in our CI flow for a long time. we can't change the way to run test cases.

@bobshie -
Am guessing that you folks rely on this version class for some such purpose within your tests (perhaps log this data somewhere or capture it in the test reports maybe? )
If the TestNG jar is being shaded by a build pipeline, why not just have your own mechanism that would embed the TestNG version into a customised way for your project which can be retrieved by you?
For e.g., since you are shading the TestNG jar, a person would have to update the version in the build file (gradle/maven) and so they can also update a text file with the TestNG version which you can later use to retrieve the value.
The only reason why that version class exists within TestNG is to help us extract out the TestNG version information from our users when they share the logs. Beyond that there's no other use that I know of.

hi @krmahadevan,
[failed to get TestNG version from class java.lang.IllegalArgumentException: invalid version "[WORKING": no-numeric "[WORKING]"  is the log from RemoteTestNG plugin.
We work on a test framework(test-based.jar) that used in the other team,  we provide a jar for them, and they can use it. but they also can use the other TestNG jar file if they want (it's not suggestion,but they still use it for the other reason), so we need to print version in log (as you said). the other thing, the RemoteTestNG plugin(for eclispe) depend on TestNG version to check the different interface.
jar -cp test-based.jar:test-case.jar

few testers using
jar -cp TestNG.jar:test-based.jar:test-case.jar
Now we add add a pom.properties for testng, it can resolve most of the problem but not all.

@bobshie - Can you please use the ManifestResourceTransformer to add the TestNG version by adding
Specification-Version: 7.6.1
Implementation-Version: 7.6.1

and see if that helps.

hello @krmahadevan , I tried the solution before. the TestNG version will be in MANIFEST.inf, but it without testng package in the file. so the version of whole jar will be replaced.
the version of testbase jar
    Implementation-Version: 1.0.2310

I didn't find a way to add such information in Manifest.inf:
     Name: org/testng/testng
     Implementation-Version: 7.6.1

@bobshie - Can you please help share a dummy project (which internally shades TestNG) so that I can try out something and share if I find something useful ?

@bobshie
Alternatively I would suggest that you try the following
Create a class called Version.java under the package org.testng.internal
and modify its getVersionString() implementation to maybe return back and hard coded value, which later gets shaded into your uber jar and see if that helps ?
package org.testng.internal;

public final class Version {

  public static final String VERSION = initVersion();

  private static String initVersion() {
    final String version = Version.class.getPackage().getImplementationVersion();
    return version != null ? version : "[WORKING]";
  }

  public static String getVersionString() {
    return VERSION;
  }

  public static void displayBanner() {
    System.out.println(
        "...\n... TestNG " + getVersionString() + " by Cédric Beust (cedric@beust.com)\n...\n");
  }
}

hi @krmahadevan ,  Before we make patch file (org.testng.internal.Version.java) in our project. it works. but it's not accepted by the other Guardians of our project.  so we now using the plugin to generate pom.properties
          <plugin>
            <!-- Generate a TestNG maven propertiesfile.java -->
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-antrun-plugin</artifactId>
            <version>${maven.antrun.plugin}</version>
            <executions>
                <execution>
                    <goals>
                        <goal>run</goal>
                    </goals>
                    <phase>generate-sources</phase>
                    <configuration>
                        <target>
                            <property name="whitespace" value=" " />
                            <property name="src.dir" value="${basedir}/target/generated-sources/properties" />
                            <property name="package.dir" value="META-INF/maven/org.testng/testng" />
                            <property name="buildtime" value="${maven.build.timestamp}" />
                            <property name="propertiesfile" value="${src.dir}/${package.dir}/pom.properties" />
                            <echo message="BUILDING : ${propertiesfile}" />
                            <echo file="${propertiesfile}" message="#Created automatically
version=${testng.version}
groupId=org.testng
artifactId=testng" />
                            <echo message="BUILD ${buildtime} : ${propertiesfile}" />
                        </target>
                    </configuration>
                </execution>
            </executions>
        </plugin>

@bobshie - In that case, can we close this issue? I dont think TestNG is going to deviate from the current mechanism in terms of embedding its version details in a simple way (Open to any suggestions though) by piggy backing on the manifest details.

I think we can close the issue because won't support the shaded usecase.

testng-test.zip
This is the example test cases.  test-case project is based on test-base project which based on TestNG.

hello @krmahadevan, I think you can close the ticket if you don't want to support such shaded user case.  we will still use the workaround solution in our project.


Embeded relationship data not loading

Hello,
Have an issue I don't understand. I've an Ember-Data model, AssetLocation that has several belongsTo relationships. I can get one relationship to load data but the others don't. I confirmed that the mirage server is creating the data behind the scenes so I think this is a config or serialization issue.
Here's my Mirage serializer for the model.
import ApplicationSerializer from './application';

export default class AssetLocationSerializer extends ApplicationSerializer {
  root = false;
  embed = true;
  include = ['location', 'asset', 'assignedTo', 'seenBy'];
}

Here the actual Ember-Data serializer for the same model.
import DS from "ember-data";
import ApplicationSerializer from './application';

const { EmbeddedRecordsMixin } = DS;

export default class AssetLocationSerializer extends ApplicationSerializer.extend(EmbeddedRecordsMixin) {
  attrs = {
    asset: { embedded: 'always' },
    assignedTo: { embedded: 'always' },
    location: { embedded: 'always' },
    seenBy: { embedded: 'always' },
  }
}

Here's a sample request made from my app.

The embedded assets get created just fine. It's the others that don't. So assignedTo and seenBy for example never get created in the store. Am I missing something here?

First I would not use ES6 classes because Mirage isn't designed to work with them yet.
Second, just to clarify what are you expecting assignedTo to be in the screenshot?

Thanks for getting back to me.

I'll make all the changes so my Mirage stuff isn't using ES6 classes. Make double sure that's not causing me any grief.

The assignedTo, location, and seenBy are all belongsTo relationships to the same model called "place". From what I can tell I've mimicked how I handled another model with a belongsTo to the same model.

Once I make the ES6 class corrections I'll let you know if that test does anything.

Just switched my Mirage Serializers to not use ES6 classes. Get the same results as before unfortunately.

@Subaku Sorry you're still having trouble.
Could you write out the exact JSON you're expecting to be returned from GET /api/v1/asset-location/?location=3?

Even better would be to share a reproduction of the issues – that's usually the fastest way to get help!

Here's a repo with a slimmed down version of my app that should replicate my issue.
https://github.com/Subaku/mirage-issue.git
I ultimately suspect I've just neglected to declare or configure something...
Thanks for your help!

So sorry for the delay! Busy holiday season.
Looks like you're just requesting all asset-location-summary models, and those only have one association, location, which is a Place model. Place only has 5 attrs, all of which are included.
So if you want the rest of the data you'll need to change your query. What data are you trying to get?

No worries. Hope your holiday was good :)
I was attempting to get all related fields back as embedded records. In my screenshots above both location and assignedTo are related to the Place model but are different Place records. I was expecting both to be included in the response given the configuration I had set on the Mirage AssetLocationSerializer. The embed and include to be precise. Given how my APIs function I may just be misunderstanding how things function here.

In your demo app the URL requested is for all asset-location-summary models. And I think Mirage is returning the whole graph, which just consists of asset-location-summary and the associated location.
Are you saying if you were to request asset-location model it's not including the other related models? If so could you update the app with the request you're having trouble mocking?


Add created time for new users to track pick up rate

PR[#40](https://github.com/aattwwss/telegram-expense-bot/pull/40

https://github.com/aattwwss/telegram-expense-bot/pull/40


[Vue3 + XState] Write announcement tweets

We need an announcement tweets to share about the new kit. This ticket is to track writing that tweet and submitting it through the form for the marketing team.
The kit needs 2 tweets:

[x] one for the kit itself
[x] one for the blog post about the kit

Link for the form to submit the tweet:
https://docs.google.com/forms/d/e/1FAIpQLSfRfi9DXLIcX4_r4DtfluYBrBlRyhVxl2c8qN5mbR7cPqtYwg/viewform

Completed and sent to content team.


made commonsparsefeatures more scalable...

at large numbers of machines and high feature counts.
See issue #183

This might be a good test case for OptimizableNode can we come up with a rule for when its better to do this vs. the old way?

Isn't the difference just that we do a treeReduce instead of a reduce ? If so it should be possible to just configure treeReduce to behave like reduce when the data is small.  Pasting the top function implementation below.
      val mapRDDs = mapPartitions { items =>
        // Priority keeps the largest elements, so let's reverse the ordering.
        val queue = new BoundedPriorityQueue[T](num)(ord.reverse)
        queue ++= util.collection.Utils.takeOrdered(items, num)(ord)
        Iterator.single(queue)
      }
      mapRDDs.reduce { (queue1, queue2) =>
          queue1 ++= queue2
          queue1
      }.toArray.sorted(ord)

Sure, I'll use that instead of the glom and sorted code.

Yeah and if you use the bounded queue we shouldn't see any perf degradation in terms of compute

Ah, spark's bounded priority queue is marked private. Should I copy the code or do something else?

According to http://stackoverflow.com/questions/7878026/is-there-a-priorityqueue-implementation-with-fixed-capacity-and-custom-comparato there is one in Guava. Not sure what our take on using guava is. (@etrain ?) Otherwise the answer suggested there or inserted into a sorted set is not bad

I like the BoundedPriorityQueue approach. While adding a dependency on Guava for this is kind of a bummer, I'd rather that than reimplementing ourselves.

@etrain BoundedPriorityQueue is a Spark private util, not a guava class. As for the guava one mentioned in the stack overflow post: It's not a full bounded priority queue implementation, and the comments on that answer warn that it shouldn't be used for bounded priority queues:
"We are giving some consideration to deprecating MinMaxPriorityQueue, just because it tends to get misused in this way."

Alright - what do we need? A thing that takes in an iterator over the partition and returns the top k elements by inserting/removing elements from a binary heap or something? I guess this is probably simple enough to implement ourselves but i don't want to go too deep down a rabbit hole here. Maybe there's another implementation somewhere we should be using?

bounded priority stuff pushed.

Hmm - do we not have unit tests for CommonSparseFeatures - seems like this would be a good time to put them in to make sure that the priority queue stuff isn't breaking some edge cases. Otherwise this LGTM.

We already do, as part of the SparseFeaturesSuite

Okay, I added an explicit guava dependency. We may have to keep an eye on this as we update Spark versions.

How did you pick the version number ?

It was what all the existing transitive dependencies on Guava had resolved to.

Sounds good. LGTM


GOBBLIN-418: Change Gobblin Service behavior to not call addSpec for pre-existing specs on FlowCatalog start up.

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-418

Description

[x] Here are some details about my PR, including screenshots (if applicable):
When Gobblin Service flowCatalog registers job scheduler, it calls addSpec() for each of the pre-existing Specs. This has the unwanted side-effect of every Spec being forwarded to the leader and being executed in case flowRunImmediately is enabled.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Tested the change on test cluster by restarting the service in slave mode and ensuring the pre-existing FlowSpecs are not forwarded to the leader instance.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

+1 LGTM


Consolidate and bump default AWS instance type (m6i.xlarge)

This commit cleans up how we handle instance types in hiveutil and e2e CI.

hiveutil create-cluster now accepts an --aws-instance-type option.
The default instance type is now m6i.xlarge. It was previously m5.xlarge for hiveutil and m4.large for the MachinePool scaling tests in our e2e CI.
This default now lives in one place, so it's easier to change later without missing things.
To allow easier noodling via CI rehearsals, e2e will feed a new $AWS_INSTANCE_TYPE environment variable through to the new --aws-instance-type param for create-cluster.

HIVE-2235

/assign @jstuever

Oh. No, that's actually broken. I think I missed a path through clusterpools somehow.

hive-operator was in a weird hot loop

This was just the namespace watch filter. We weren't actually reconciling (despite the message).

/test e2e
unrelated flake

/test coverage
known taint flake
/test e2e-pool
I have absolutely no idea what happened here. It looks like we got past the previous error, but then something weird happened with the uninstall of the ("real") pool cluster.

Looks like 4.14 starts to use OVNKubernetes. Wondering if we should generate install-config with this networkType.

This actually looks like it pretty much succeeded, but ran up against the overall 2h test timeout.
/test e2e-pool
Even if this eventually works, we're obviously skating way too close to the maximum allowable test time. I'm not even sure what we would do about that.

I'm only guessing the slowdown has something to do with having increased the instance size. (Bigger instances take longer to... provision? hibernate? resume?) I believe I found about half an hour we can trim out of the test via https://github.com/openshift/hive/pull/2080 -- will retest when that lands.

Sorry there might be a mix-up, I wan't referring to the e2e-pool job fail. What I meant is, in addition to the default AWS instance type (generated by hiveutil), do you think it's a good idea to also update the networkType (to align with Openshift Installer's default) ?

/lgtm

Sorry there might be a mix-up, I wan't referring to the e2e-pool job fail. What I meant is, in addition to the default AWS instance type (generated by hiveutil), do you think it's a good idea to also update the networkType (to align with Openshift Installer's default) ?

Gosh, I don't know. Is there a benefit to doing so? Will it make something faster or cheaper? Is OpenShiftSDN being deprecated/removed?

Gosh, I don't know. Is there a benefit to doing so? Will it make something faster or cheaper? Is OpenShiftSDN being deprecated/removed?

I'd be curious if we could remove NetworkType and let things naturally use their defaults.

I'd be curious if we could remove NetworkType and let things naturally use their defaults.

Okay, sure: https://github.com/openshift/hive/pull/2085
Note: I'm pretty sure this is only affecting hiveutil (and thereby e2e).


Remove cfg editor dead code (to be moved to galley)

jenkins cached removed code and doesn't compile anymore


Unclosed client session & Unclosed connector

Add-on just stopped working
Home Assistant 0.111.4 supervised on debian host
addon 2.8.6
tried deleting from HACS & integrations, reboot, delete pickle & file in custom_components root, reboot, reinstall through HACS, login
Unknown error, please report log info
Error doing job: Unclosed client session
Error doing job: Unclosed connecton

also ended all open sessions through amazon.com and retried..

Try to reboot HA instance after you have inserted the 2FA in HA (if you have one)

i can't get to the point it even asks anything. I enter login data, press next/save -> unknown error

Please fill out the template.

Same problem here, "unclosed client session" and "unclossed connection". It keeped me asking for a captcha and after rebooting it never worked again. I deleted the integration and tried to re-add again, it says "unknown error".
Hass 0.111.2 running under debian 10 with docker.
At the console, the errors are (I omitted some URLS, cookies and more):
An error occured accessing AlexaAPI: An exception of type ContentTypeError occurred.
2020-06-21 21:52:17 WARNING (MainThread) [custom_components.alexa_media.config_flow] Unknown error: 0, message='Attempt to decode JSON with unexpected mimetype: text/html;charset=utf-8', url=URL(....)

lol... same info though..
Describe the bug
Addon just stopped working, can't add it back in any way
add through hacs, install in integrations -> login -> FAILED with unknown error..
To Reproduce
Steps to reproduce the behavior:
open hassio
(extra: install addon and try to login to amazon account, shows instant unknown error)
Expected behavior
find working alexa media player -> instead shows entity not found
(extra: get capchta)
System details

Home-assistant (version): Home Assistant 0.111.4 supervised on debian host
Hassio (Yes/No): YES
alexa_media  (version from const.py or HA startup):
alexapy (version from pip show alexapy or HA startup):

Logs
Error doing job: Unclosed client session
Error doing job: Unclosed connecton
[custom_components.alexa_media.config_flow] Unknown error: 0, message='Attempt to decode JSON with unexpected mimetype: text/html;charset=utf-8', url=URL(....)
Additional context
No updates or whatever were executed before addon stopped working..
tried deleting from HACS & integrations, reboot, delete pickle & file in custom_components root, reboot, reinstall through HACS, login
also ended all open sessions through amazon.com and retried..

The same way  it stopped working, it just started working -_-
after the 24th time of deleting everything, rebooting, install, reboot, ..........
i got my capchta and 2fa back..
don't know what changed as i've been doing this for the past 2 days to get it working again..

I'll close this then. Without debug logs showing what is happening before the error, there is no effective way to figure out what's wrong.  It could be internet connectivity issues, it could be Amazon being down.


Import errors with newer coverage

Any coverage >= 7.0.0 breaks lcov with an import error:
Traceback (most recent call last):
  File "/home/meejah/src/txtorcon/venv/bin/coverage-lcov", line 5, in <module>
    from coverage_lcov.cli import main
  File "/home/meejah/src/txtorcon/venv/lib/python3.11/site-packages/coverage_lcov/cli.py", line 3, in <module>
    from .converter import Converter
  File "/home/meejah/src/txtorcon/venv/lib/python3.11/site-packages/coverage_lcov/converter.py", line 5, in <module>
    from coverage.files import FnmatchMatcher, prep_patterns
ImportError: cannot import name 'FnmatchMatcher' from 'coverage.files' (/home/meejah/src/txtorcon/venv/lib/python3.11/site-packages/coverage/files.py)

Should be fixed with version 0.3.0 as implemented in #14


[reactive-element] Add queryAssignedElements decorator

Fixes: https://github.com/lit/lit/issues/2292
Adds queryAssignedElements decorator and tests (that similarly match the queryAssignedNodes tests).
This change proposes a new options bag API which lets us avoid needing to use and empty string if targeting an unnamed slot.
Note that there is temporarily an asymmetry between this decorator and queryAssignedNodes which will be addressed with https://github.com/lit/lit/issues/2332.
How

The first commit introduces the new decorator, with tests matching closely what the queryAssignedNodes tests. In fact the fixture is almost identical.
Then I add the imports closely following the query-assigned-nodes references in the codebase.
Finally I updated the ts-transformer such that it can transform queryAssignedElements into JS.

Testing
Change is tested with unit tests, as well as transformer tests.

Tests are passing. The only tests failing is something to do with Sauce not connecting:
ests: Error: 3 Dec 01:36:24 - Sauce Connect could not establish a connection.
tests: 3 Dec 01:36:24 - Please check your firewall and proxy settings.
tests: 3 Dec 01:36:24 - Goodbye.
tests:     at Socket.<anonymous> (/home/runner/work/lit/lit/packages/tests/node_modules/saucelabs/build/index.js:322:25)
tests:     at Socket.emit (events.js:400:28)
tests:     at Socket.emit (domain.js:475:12)
tests:     at addChunk (internal/streams/readable.js:293:12)
tests:     at readableAddChunk (internal/streams/readable.js:267:9)
tests:     at Socket.Readable.push (internal/streams/readable.js:206:10)
tests:     at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)

I think this is unrelated to my changes.


feat: handle private network requests

This PR adds support for the additional CORS-headers introduced in the Private Network Access draft. Chrome experimenting with it, see: https://chromestatus.com/feature/5436853517811712.

Interesting although I'm not sure it's smart to already add it while support is not great?

I'm going to hold off on this now until it's more clear what the support is.


⚠ GitLab Server has degraded performance

In 237e3e3, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6290 ms

Resolved: GitLab Server performance has improved in 5aa1b07.


Is Direct Routing supported? Are there any limitations in creating a new application instance for customers using Direct Routing?

Describe the issue
We get an error, trying to create a new “New-CsOnlineApplicationInstance” for a Tenant with Direct Routing. It does not seem to be time delay.
Does the policy recording supports Direct Routing?
Tenant has not hybrid deployment with SfB on premises. It is Teams only with SBC.
The New-CsHybridApplicationEndpoint works only with SfB.
Code Snippet
  New-CsOnlineApplicationInstance   ....
  WARNING: New-CsHybridApplicationEndpoint -ApplicationId bd44f15c-da63-476b-9c70-
 22bb29f1f129 -DisplayName "aaaaaa Bot App" -SipAddress aaaabot@aaaaa com(opens in new
 tab) -OU [A_VALID_OU]
This cmdlet is for online domain only. Please run corresponding on-premises cmdlets for on-
 premises domain.
+ CategoryInfo     : InvalidOperation: (:) [New-CsOnlineApplicationInstance],
 InvalidOperationException
+ FullyQualifiedErrorId :
 Microsoft.Rtc.Management.Hosted.PlatformService.
 ApplicationInstance.NewCsOnlineApplicationInstanceCmdlet
+ PSComputerName  : admingb1.online.lync.com

Solved,   our mistake


After clicking "Deploy to Heroku", requests for admin CSS and JS results in HTTP 503 errors

After clicking "Deploy to Heroku" from this GitHub project, the site appears to load normally, but listing admin fails to load any of its JS or CSS.
Looking in the dev console, it looks like all requests for admin CSS and JS result in HTTP 503 errors.

I just did the deploy to Heroku, and it fails with a 400 "Disallowed host". Sounds like the button still needs some work.

Confirmed here. This happens because the current releases of Django as of 1st November (1.8.16, 1.9.11, 1.10.3 and above) enforce ALLOWED_HOSTS even when DEBUG is true:
https://docs.djangoproject.com/en/1.10/releases/1.10.3/#dns-rebinding-vulnerability-when-debug-true
Since everyone's hostname on Heroku is different, there's no meaningful hostname we can put in ALLOWED_HOSTS. However, I reckon it would be appropriate to set ALLOWED_HOSTS = ['*'] in this case: it means that we're bypassing the security features that Django is providing by enforcing ALLOWED_HOSTS in the first place, but anyone doing anything security-critical with wagtaildemo on Heroku ought to be reading and adjusting the settings files appropriately (if they don't, they're already falling foul of the non-secret SECRET_KEY).

I agree about setting '*'. FWIW, Heroku's router prevents hostnames not belonging to the app anyway, so this should be pretty safe.

OK, I think this is sorted now: have added ALLOWED_HOSTS = ['*'] in ede7ee09d9b33f1e9429ddc6549141338f51cce5, and fixed the issue with serving admin JS/CSS by upgrading whitenoise to >=3.1 in 5992b9e49a403fb5e7f716846f44c800b08c75d3.

Lovely, thanks Matt!
On Thu, 8 Dec 2016 at 19:54, Matt Westcott<EMAIL_ADDRESS>wrote:

OK, I think this is sorted now: have added ALLOWED_HOSTS = ['*'] in
ede7ee0
https://github.com/torchbox/wagtaildemo/commit/ede7ee09d9b33f1e9429ddc6549141338f51cce5,
and fixed the issue with serving admin JS/CSS by upgrading whitenoise to

=3.1 in 5992b9e
https://github.com/torchbox/wagtaildemo/commit/5992b9e49a403fb5e7f716846f44c800b08c75d3
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/torchbox/wagtaildemo/issues/101#issuecomment-265822555,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfF8wc01Cwsu2coCik0sMFb5evjMk-wks5rGFJqgaJpZM4KdHqS
.


Is there a java version

Is there a java version

Hello,
There is no java version of docplex.
However there are java API for cpoptimizer and CPLEX.
Please have a look at https://www.ibm.com/docs/en/icos/20.1.0?topic=cplex-java-reference-manual
and:
https://www.ibm.com/docs/en/icos/20.1.0?topic=optimizer-cp-java-api-reference-manual

Thank you～


[a11y]: Snackbar should not disappear until the user takes an action when accessibility controls are turned on

In the Bottom App Bar demo, pressing the Floating Action Button shows a snackbar.  I noticed this while writing #16238
For this to be accessible to users with a screen reader or other accessibility feature turned on, the snackbar should remain on the screen until the user takes another action.
This should be a change we make at the Snackbar level.
@goderbauer

Internal discussion of this: yaqs/5408254254645248


How to access current module path inside NormalModuleReplacementPlugin in webpack?

I am trying to extend/reimplement webpack.NormalModuleReplacementPlugin to allow using filter callback instead of RegExp.
I am able to inject into normal-module-factory/after-resolve hook and to replace resolved module path with the one I need. But the problem is that I also need to support "requiring of replaced module inside of replacing".
I mean that if module A is being replaced with B, then module B should be able to require module A without circular loop. (it is very similar to calling super inside of a subclass)
Here's an example:
//module A: ./core/A.jsx
export default class A extends React.Component {
 render() {
  return
A
;
 }
}

//module B which replaces module A: ./override/A.jsx
import A from '../core/A.jsx'; //here's a circular loop as now we are requiring ourself
export default class A extends React.Component {
 render() {
  return (

is overridden!

  );
 }
}

And here is the question: is there any way to access path of current module trying to require module A to check if it is equal to the path of the module B and skip replacement?
All I have found is result.context property inside after-resolve callback, but it's only a directory containing current module, not the module itself.
If I'm using wrong plugin hook, what should I use then? I tried to dig into ResolverPlugin and file hook but I believe it's not the proper way as long as I don't need to resolve anything but only substitute the module.
TIA

Hi,
Did you manage to progress with this? I expect the API might be a little different with webpack 2.

@bebraw Nope, I ended up with checking result.context. It turned out to be enough.
I haven't looked on webpack2 yet - waiting for release.

Webpack 2 is officially released so I'm closing this.


Maven, really executable and trampoline not working with Capsule 1.0

Sample project: https://github.com/circlespainter/capsule-1.0-sample
Resolution doesn't work; it looks like the Maven capsule task is using an older Maven caplet (1.0-rc1 I think) but forcing it with the capsule configuration will just embed the Maven caplet JAR twice.
Really executable capsules and trampolines don't seem to work, the capsule-building tasks print:
[ant:concat] /home/fabio/.m2/repository/co/paralleluniverse/capsule/1.0/capsule-1.0.jar:capsule/execheader.sh does not exist.

You would need to clear and override the mavenCaplet configuration; that is where the maven caplet dependency is defined.
And the executable capsules failed since the scripts were moved into 'capsule-util'.
I'm now working on fixing these for the 1.0 release. Thanks for the heads up!

@circlespainter 1.0.0 is out now. I also added a little utility to make it easier to override versions in the future. You can put this somewhere at the beginning of your build file and it will override the builtin version.
capsule.version = '1.1'

To the best of my knowledge reallyExecutable { trampoline() } still does not work in the 1.0.1 version.
reallyExecutable { script file('src/main/resources/trampoline.sh') } does work, as long the sh file you provide actually exists. Otherwise it will simply build a non-autoexecutable jar, without either failing or issueing any warning.
Regards

@cvarona Based upon issue #20, it looks like you need to say delegate.trampoline() to make it work. Alternatively, you may use trampolining(), which I am going to add in the 1.0.2 version.
As for the silent failure, I've opened another issue and am working on fixing that as well.


Replace which with command -v

as well as neutrinolabs/xorgxrdp#204.
Reported by: @drwilly

Good idea.
I found these ones too:-

genkeymap/dump-keymaps.sh
libpainter/bootstrap
librfxcodec/bootstrap

@metalefty - I'll have a bit of time tomorrow to do the libpainter and librfxcodec changes.
Shall I pick that up, or will you do it?

@matt335672 Can you do that?


Fix for css transform?

First of all, this is a wonderful component and thank you so much for developing it. I have a small issue with it, when the parent element is modified by the css transform property the component does not move or resize according to the cursor position. Any idea how i could fix this? Thanks!

Can you show me an example? The component registers the parent size when is mounted, so if you later try to change them through css, the calculations are not performed correctly.

Closing. Let's track it on #91


Allow Specifying AAD authentication Methods via ChainedTokenCredential in Microsoft.Data.SqlClient 3.0

Microsoft.Data.SqlClient 3.0 now supports DefaultAzureCredential.  This is very useful but I'd like to suggest providing some control over the AAD authentication methods used through ChainedTokenCredential.

I'm not sure if this pertains to to the same, but it would be ideal to be able to specify auth methods (and their order) with the new "Authentication=Active Directory Default;" connection string property. Using that with local VS Code development leads to a considerable loading time increase each time we start an application. Would be great to be able to locally prioritize VisualStudioCodeCredential via the connection string.

I think that's great idea

For local development it would be great if an actual credential type or exclusion could be configured. The credential chain causes quite a bit of noise and transient exceptions in diagnostics/logging for failed attempts (e.g. trying the MSI private network).

I believe there was a draft PR#1260 that would open up this scenario, but more resources and time is needed to develop it.

For local development it would be great if an actual credential type or exclusion could be configured. The credential chain causes quite a bit of noise and transient exceptions in diagnostics/logging for failed attempts (e.g. trying the MSI private network).

This, because at least for me Visual Studio credentials are not working, even if they should. It just keeps disconnecting, very frustrating not being able to disable it.

For further customization of token acquisition, users should use AccessTokenCallback to provide their own mechanism of acquiring an access token.


[chore] remove the need for replace statement

The builder automatically runs go get cloud.google.com/go, but with --skip-get-modules it does not, causing the ambiguious import issue to arise.

Subsumed by #102.


Noir contracts shouldn't get notes that were nullified earlier in TX

Ref -> storage_slot.remove(note) doesn't remove until the base rollup. So for the same transaction, you always get the same notes and can't spend other notes. This prevents how many transactions can happen at the same time.
https://aztecprotocol.slack.com/archives/C03P17YHVK8/p1688120000664279

Related to (probably blocked by) - https://github.com/AztecProtocol/aztec-packages/issues/919

https://github.com/AztecProtocol/aztec-packages/issues/920

Renamed the ticket from previous title. We'll need to track pending nullifiers in the ACIR simulator and check against them whenever doing getNotes.
I'd be glad to pick this ticket up if it's okay with you @sirasistant!

IMPORTANT:
We need to deal BOTH cases:

The nullifier nullifies a pending commitment (namely on created within this transaction)
The nullifier nullifies a settled commitment pertaining to a previous transaction.

In both cases, getNotes should filter notes which were already nullified during this transaction.


drivers serial nrfx: Apply workaround also for bsim targets

Or more precisely, do not remove the workaround for them.
The current HW models are accurate enough in this area for the workaround to work properly.

@anangl @nordic-krch thanks for the reviews, the last push is just a rebase + update of the west hal_nordic pointer from the PR to main.


module declares its path as: xorm.io/core

        github.com/go-xorm/core<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: xorm.io/core
                but was required as: github.com/go-xorm/core

请问这个问题如何解决?

请更新最新版本

Any answers for this?

Any answers for this?

@yunlongw I have also encountered this problem, and I would like to know how to solve it. Can you answer that?评

ok.I found the answer. Please look at this image.


truncate a string function expects str and num, some of the tests pass str and str

Challenge Truncate a string has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
function truncateString(str, num) {
  // Clear out that junk in your trunk
  if (str.length > num && num > 3) {
    return str.slice(0, (num - 3)) + '...';
  } else if (str.length > num && num <= 3) {
    return str.slice(0, num) + '...';
  } else {
    return str;
  }

}
truncateString("A-tisket a-tasket A green and yellow basket", 11);

You got this! If you get stuck, try the help button.
If you have suggestions on how to improve the description, please let us know!
Happy coding! 🙂

Systimotic- see if you can make something from this:
Long strings must be truncated; if your string (first argument) is longer than a given length (second argument) it must be truncated and given a ... ending.
Medium strings must be truncated but note that inserting the three dots to the end adds to the string length. If the given length (second argument) is less than or equal to 3, then the addition of the three dots should not be included in length count.
Tiny strings do not need to be truncated.

@m4sterbunny Thank you for your suggestions. After reviewing the description, I do agree that it is quite confusing. I'll open an issue to discuss changing this to something less confusing.
Thanks again for your input, and more happy coding!


feat(handler): implement kick command

Implementation of the kick command.

[ ] Kick reason with a modal.
[ ] Check user and bot permissions.
[ ] Send private message to the user.
[ ] Send message to the logs channel.

Replaced by #83 because of too many conflicts due to recent refactorings.


components didn't install correctly via INIT_CONFIG configuration

Describe the bug
Components didn't deployed with use of INIT_CONFIG file
To Reproduce

Docker image was build from Dockerfile in this repo GREENGRASS_RELEASE_VERSION=2.10.3

Docker run command:

 -v /home/user/IOT/config:/tmp/config/:ro \
 -e INIT_CONFIG=/tmp/config/config.yaml \
 --env-file .env \
 -e AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN=$AWS_SESSION_TOKEN \
 -p 8883 greengrass:3

.env file

AWS_REGION=eu-central-1
PROVISION=true
COMPONENT_DEFAULT_USER=ggc_user:ggc_group
INIT_CONFIG=config.yaml
TES_ROLE_ALIAS_NAME=TokenExchangeRoleAlias
DEPLOY_DEV_TOOLS=true
THING_NAME=test-thing
THING_GROUP_NAME=thing-group-vburiak
TES_ROLE_NAME=TokenExchangeRole
LOG_LEVEL=INFO

Content of config file:

  aws.greengrass.Cli:
    componentType: "PLUGIN"
    configuration:
      AuthorizedPosixGroups: null
      AuthorizedWindowsGroups: null
    dependencies:
    - "aws.greengrass.Nucleus:SOFT"
    version: "2.11.0"
  aws.greengrass.clientdevices.Auth:
    componentType: "PLUGIN"
    configuration:
      ca_type: null
      certificateAuthority:
        caType: null
      deviceGroups:
        definitions:
          AllPermissiveDeviceGroup:
            policyName: "AllPermissivePolicy"
            selectionRule: "thingName: *"
        formatVersion: "2021-03-05"
        policies:
          AllPermissivePolicy:
            AllowAll:
              operations:
              - "*"
              resources:
              - "*"
              statementDescription: "Allow client devices to perform all actions."
      metrics: {}
      security: {}
      startupTimeoutSeconds: "120"
    version: "2.4.3"
  aws.greengrass.clientdevices.mqtt.Bridge:
    componentType: "PLUGIN"
    configuration:
      mqttTopicMapping:
        CloudDeleteShadowNameMapping:
          source: "IotCore"
          target: "LocalMqtt"
          topic: "$aws/things/+/shadow/name/+/delete/+"
        CloudGetJobIdsMapping:
          source: "IotCore"
          target: "LocalMqtt"
          topic: "$aws/things/+/jobs/+/get/+"
        CloudGetJobsMapping:
          source: "IotCore"
          target: "LocalMqtt"
          topic: "$aws/things/+/jobs/get/+"
        CloudGetShadowNameMapping:
          source: "IotCore"
          target: "LocalMqtt"
          topic: "$aws/things/+/shadow/name/+/get/+"
        CloudNotifyJobsMapping:
          source: "IotCore"
          target: "LocalMqtt"
          topic: "$aws/things/+/jobs/notify"
        CloudNotifyNextJobsMapping:
          source: "IotCore"
          target: "LocalMqtt"
          topic: "$aws/things/+/jobs/notify-next"
        CloudUpdateJobsMapping:
          source: "IotCore"
          target: "LocalMqtt"
          topic: "$aws/things/+/jobs/+/update/+"
        CloudUpdateShadowNameMapping:
          source: "IotCore"
          target: "LocalMqtt"
          topic: "$aws/things/+/shadow/name/+/update/+"
        DeleteShadowNameMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/things/+/shadow/name/+/delete"
        EventsMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/rules/events_bi_rule/+"
        FaultsMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/rules/faults_bi_rule/+"
        GetJobIdsMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/things/+/jobs/+/get"
        GetJobsMappingMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/things/+/jobs/get"
        GetShadowNameMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/things/+/shadow/name/+/get"
        MetricsMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/rules/metrics_bi_rule/+"
        PropertiesMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/rules/properties_bi_rule/+"
        StartNextJobsMappingMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/things/+/jobs/start-next"
        TelemetryNameMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "dt/iotagent/#"
        UpdateJobsMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/things/+/jobs/+/update"
        UpdateShadowNameMapping:
          source: "LocalMqtt"
          target: "IotCore"
          topic: "$aws/things/+/shadow/name/+/update"
      startupTimeoutSeconds: "120"
    dependencies:
    - "aws.greengrass.clientdevices.Auth:HARD"
    lifecycle:
      startup:
        timeout: "120"
    version: "2.2.6"
  aws.greengrass.clientdevices.mqtt.Moquette:
    componentType: "PLUGIN"
    configuration:
      moquette:
        host: "<IP_ADDRESS>"
        netty.mqtt.message_size: "131072"
        ssl_port: "8883"
      netty.channel.read.limit: 524288
      netty.channel.write.limit: 524288
      startupTimeoutSeconds: "120"
    dependencies:
    - "aws.greengrass.clientdevices.Auth:HARD"
    lifecycle:
      startup:
        timeout: "120"
    version: "2.3.3"
  aws.greengrass.LocalDebugConsole:
    componentType: "PLUGIN"
    configuration:
      bindHostname: "<IP_ADDRESS>"
      httpsEnabled: "false"
      port: "1441"
      websocketPort: "1442"
    dependencies:
    - "aws.greengrass.Cli:SOFT"
    - "aws.greengrass.Nucleus:SOFT"
    lifecycle: {}
    version: "2.3.1"
  aws.greengrass.Nucleus:
    componentType: "NUCLEUS"
    configuration:
      awsRegion: "eu-central-1"
      componentStoreMaxSizeBytes: "10000000000"
      deploymentPollingFrequencySeconds: "15"
      envStage: "prod"
      fleetStatus:
        periodicStatusPublishIntervalSeconds: 86400
      greengrassDataPlaneEndpoint: ""
      greengrassDataPlanePort: "8443"
      mqtt:
        spooler: {}
      networkProxy:
        proxy: {}
      platformOverride: {}
      runWithDefault:
        posixUser: "ggc_user:ggc_group"
      telemetry: {}
    previousVersion: "2.11.0"
    version: "2.11.0"

Expected behavior
Some components files appear in  /greengrass/v2/bin and   /greengrass/v2/packages folders
Actual behavior
Folders /greengrass/v2/bin and  /greengrass/v2/packages(with subfolders) are empty
Auto-provisioning works and services: part of effectiveConfig.yaml a same as config.yaml

Hello,
If you're trying to deploy components, then you must make a deployment to the device; just changing the configuration on the device will not work. See the documentation here to create a deployment: https://docs.aws.amazon.com/greengrass/v2/developerguide/manage-deployments.html.
I may also recommend you follow a tutorial in client device usage: https://docs.aws.amazon.com/greengrass/v2/developerguide/client-devices-tutorial.html

@MikeDombo
according to manual
https://docs.aws.amazon.com/greengrass/v2/developerguide/configure-installer.html
-init, --init-config
(Optional) The path to the configuration file to use to install the AWS IoT Greengrass Core software. You can use this option to set up new core devices with a specific nucleus configuration, for example.

so as I understand, to install considered as install?)
or installation is impossible via this option?

It is for installing Nucleus, which is the core piece of Greengrass. It cannot be used to install other components; a deployment is how you install other components.


[DOCS] A demo based on webpack

Could you please come up with a document that integrates with webpack? Thank you!

It's not a priority of us to support Webpack, but it's technically possible, we have focused in Rollup / esbuild and Vite, which we have official plugins to support this.

It's not a priority of us to support Webpack, but it's technically possible, we have focused in Rollup / esbuild and Vite, which we have official plugins to support this.

Anyway, thank you for your team!

My group is going to start looking at this for module federation support with qwik


Add GxB serialize and deserialize for matrices and vectors.

These are thin wrappers as per typical for python-suitesparse-graphblas.

I'm gonna give this a go and do a release.  Post-merge reviews are welcome :)


Unacceptably large observation errors due to Surface Obs

I have pointed this out quite some time ago, but perhaps the lack for a formal issue has put the problem in the back burn.
There is something incorrect or missing in the yaml files controlling the assimilation of Surface Marine and Surface Land Stations in the sense that the observation errors come out way too large:
CostJo   : Nonlinear Jo(Surface Marine Stations) = 12142.6, nobs = 101149, Jo/n = 0.120047, err = 7.07671e+08
CostJo   : Nonlinear Jo(Surface Land Stations) = 4957.76, nobs = 74935, Jo/n = 0.0661609, err = 9.68093e+09
the numbers in the last column should be order 1 or so.

Wei, did you work on this type of obs? Are those bad data? Can you duplicate Ricardo's results?

This is most likely harmless. It indicates that some observations passed QC but were assigned very large observation errors due to the inflation procedure in surface pressure check.


Store commit message in proto

Triage: what's needed in this bug?

Update the commit proto to have a field that contains the commit message. This will need to be updated in the commit model first.
This makes it easier for people to refer to changes in the dashboard and not need to cross reference with GitHub.


test-reporter release v1.9.0

Features

Add support for the rspec-json format #398

I was thinking about merging this, tagging the release and doing a manual merge into v1 branch. This way the history of v1 releases will be kept.