(Dynamic Routing) Router get stuck in pending state randomly

I'm currently using dynamic routing (0.0.35) with nested routers. Both layers of routers have deferred-route targets that trigger a load and use target-ready as a post-mutation.
At random the top router will be stuck in pending state. Yesterday I tried all day to create a workspace where this behaviour is consistently happening, but I failed to do so, and can not tell what causes this issue.
It seems to be a timing issue, something that fulcro 3.0 will resolve in the future.

This is what is being logged when it will get stuck. I route to the segment ["content" "2" "info"] Where the segment ["content" :content/id] is handled by RootRouter and ["info"] is handled by the ContentRouter
At some moment when everything should be done, the RootRouter will start a deferred-route to path nil, which will never be notified to be ready.
[723.862s] [fulcro.incubator.ui-state-machines] Triggering :route! on :fulcro.incubator.routing-broken-ws/RootRouter with {:error-timeout 5000, :deferred-timeout 100, :path-segment ["content" "2"], :router [:fulcro.incubator.dynamic-routing/id :fulcro.incubator.routing-broken-ws/RootRouter], :target [:content/id 2]}
console.js:218  [723.863s] [fulcro.incubator.ui-state-machines] Triggering :route! on :fulcro.incubator.routing-broken-ws/ContentRouter with {:error-timeout 5000, :deferred-timeout 100, :path-segment ["info"], :router [:fulcro.incubator.dynamic-routing/id :fulcro.incubator.routing-broken-ws/ContentRouter], :target [:content :info]}
console.js:218  [723.865s] [fulcro.incubator.ui-state-machines] Storing :pending-path-segment -> ["content" "2"] on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [723.866s] [fulcro.incubator.ui-state-machines] Applying mutation helper to state of :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [723.869s] [fulcro.incubator.ui-state-machines] Activating state  :deferred on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [723.870s] [fulcro.incubator.ui-state-machines] Storing :target -> [:content/id 2] on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [723.871s] [fulcro.incubator.ui-state-machines] Setting timeout :error-timer on :fulcro.incubator.routing-broken-ws/RootRouter to send :timeout! in 5000 ms
console.js:218  [723.873s] [fulcro.incubator.ui-state-machines] Setting timeout :delay-timer on :fulcro.incubator.routing-broken-ws/RootRouter to send :waiting! in 100 ms
console.js:218  [723.886s] [fulcro.incubator.ui-state-machines] Storing :pending-path-segment -> ["info"] on :fulcro.incubator.routing-broken-ws/ContentRouter
console.js:218  [723.887s] [fulcro.incubator.ui-state-machines] Applying mutation helper to state of :fulcro.incubator.routing-broken-ws/ContentRouter
console.js:218  [723.890s] [fulcro.incubator.ui-state-machines] Activating state  :deferred on :fulcro.incubator.routing-broken-ws/ContentRouter
console.js:218  [723.892s] [fulcro.incubator.ui-state-machines] Storing :target -> [:content :info] on :fulcro.incubator.routing-broken-ws/ContentRouter
console.js:218  [723.893s] [fulcro.incubator.ui-state-machines] Setting timeout :error-timer on :fulcro.incubator.routing-broken-ws/ContentRouter to send :timeout! in 5000 ms
console.js:218  [723.895s] [fulcro.incubator.ui-state-machines] Setting timeout :delay-timer on :fulcro.incubator.routing-broken-ws/ContentRouter to send :waiting! in 100 ms
console.js:218  [723.972s] [fulcro.incubator.dynamic-routing] Router :fulcro.incubator.routing-broken-ws/ContentRouter notified that pending route is ready.
console.js:218  [723.972s] [fulcro.incubator.ui-state-machines] Triggering :ready! on :fulcro.incubator.routing-broken-ws/ContentRouter with {}
console.js:218  [723.975s] [fulcro.incubator.dynamic-routing] Router :fulcro.incubator.routing-broken-ws/RootRouter notified that pending route is ready.
console.js:218  [723.976s] [fulcro.incubator.ui-state-machines] Triggering :ready! on :fulcro.incubator.routing-broken-ws/RootRouter with {}
console.js:218  [723.978s] [fulcro.incubator.ui-state-machines] Storing :path-segment -> ["info"] on :fulcro.incubator.routing-broken-ws/ContentRouter
console.js:218  [723.980s] [fulcro.incubator.ui-state-machines] Storing :pending-path-segment -> [] on :fulcro.incubator.routing-broken-ws/ContentRouter
console.js:218  [723.982s] [fulcro.incubator.ui-state-machines] Applying mutation helper to state of :fulcro.incubator.routing-broken-ws/ContentRouter
console.js:218  [723.983s] [fulcro.incubator.dynamic-routing] Applying route ident [:content :info] to router :fulcro.incubator.routing-broken-ws/ContentRouter
console.js:218  [723.985s] [fulcro.incubator.ui-state-machines] Activating state  :routed on :fulcro.incubator.routing-broken-ws/ContentRouter
console.js:218  [723.987s] [fulcro.incubator.ui-state-machines] Cancelling timer  :error-timer on :fulcro.incubator.routing-broken-ws/ContentRouter due to event :ready!
console.js:218  [723.988s] [fulcro.incubator.ui-state-machines] Clearing timeout  :fulcro.incubator.routing-broken-ws/ContentRouter : :error-timer
console.js:218  [723.990s] [fulcro.incubator.ui-state-machines] Cancelling timer  :delay-timer on :fulcro.incubator.routing-broken-ws/ContentRouter due to event :ready!
console.js:218  [723.992s] [fulcro.incubator.ui-state-machines] Clearing timeout  :fulcro.incubator.routing-broken-ws/ContentRouter : :delay-timer
console.js:218  [723.995s] [fulcro.incubator.ui-state-machines] TIMEOUT on :fulcro.incubator.routing-broken-ws/RootRouter due to timer :delay-timer after 100 ms
console.js:218  [723.996s] [fulcro.incubator.ui-state-machines] Triggering :waiting! on :fulcro.incubator.routing-broken-ws/RootRouter with {}
console.js:218  [724.008s] [fulcro.incubator.ui-state-machines] Storing :path-segment -> ["content" "2"] on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [724.009s] [fulcro.incubator.ui-state-machines] Storing :pending-path-segment -> [] on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [724.011s] [fulcro.incubator.ui-state-machines] Applying mutation helper to state of :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [724.012s] [fulcro.incubator.dynamic-routing] Applying route ident [:content/id 2] to router :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [724.014s] [fulcro.incubator.ui-state-machines] Activating state  :routed on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [724.016s] [fulcro.incubator.ui-state-machines] Cancelling timer  :error-timer on :fulcro.incubator.routing-broken-ws/RootRouter due to event :ready!
console.js:218  [724.017s] [fulcro.incubator.ui-state-machines] Clearing timeout  :fulcro.incubator.routing-broken-ws/RootRouter : :error-timer
console.js:218  [724.019s] [fulcro.incubator.ui-state-machines] Cancelling timer  :delay-timer on :fulcro.incubator.routing-broken-ws/RootRouter due to event :ready!
console.js:218  [724.020s] [fulcro.incubator.ui-state-machines] Clearing timeout  :fulcro.incubator.routing-broken-ws/RootRouter : :delay-timer
***** ROOT ROUTER STARTS TO ROUTE TO nil ****** console.js:218 * [724.024s] [fulcro.incubator.ui-state-machines] Storing :pending-path-segment ->  on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [724.026s] [fulcro.incubator.ui-state-machines] Applying mutation helper to state of :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [724.030s] [fulcro.incubator.ui-state-machines] Activating state  :deferred on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [724.032s] [fulcro.incubator.ui-state-machines] Storing :target ->  on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [724.034s] [fulcro.incubator.ui-state-machines] Setting timeout :error-timer on :fulcro.incubator.routing-broken-ws/RootRouter to send :timeout! in 5000 ms
console.js:218  [724.036s] [fulcro.incubator.ui-state-machines] Setting timeout :delay-timer on :fulcro.incubator.routing-broken-ws/RootRouter to send :waiting! in 100 ms
console.js:218  [724.139s] [fulcro.incubator.ui-state-machines] TIMEOUT on :fulcro.incubator.routing-broken-ws/RootRouter due to timer :delay-timer after 100 ms
console.js:218  [724.140s] [fulcro.incubator.ui-state-machines] Triggering :waiting! on :fulcro.incubator.routing-broken-ws/RootRouter with {}
console.js:218  [724.149s] [fulcro.incubator.ui-state-machines] Activating state  :pending on :fulcro.incubator.routing-broken-ws/RootRouter
console.js:218  [729.041s] [fulcro.incubator.ui-state-machines] TIMEOUT on :fulcro.incubator.routing-broken-ws/RootRouter due to timer :error-timer after 5000 ms
console.js:218  [729.044s] [fulcro.incubator.ui-state-machines] Triggering :timeout! on :fulcro.incubator.routing-broken-ws/RootRouter with {}
console.js:218  [729.053s] [fulcro.incubator.ui-state-machines] Activating state  :failed on :fulcro.incubator.routing-broken-ws/RootRouter

So, this patch was an attempt to fix those for the time being:
https://github.com/fulcrologic/fulcro-incubator/commit/4703a75c3ceb65c5ae89624fc85583d63b9a0abc
but you're using it.  That is the exact area of code you're hitting.  You might try using :local/root with deps to pull incubator into your project and play with adding some more logging around that area.  Perhaps you can figure out the condition.

Actually, I think this might be something else. The state machine is triggering a timeout as if you've missed a deferred routing deadline:
console.js:218  [729.041s] [fulcro.incubator.ui-state-machines] TIMEOUT on :fulcro.incubator.routing-broken-ws/RootRouter due to timer :error-timer after 5000 ms
which either means you forgot to resolve the route OR you managed to resolve it before the state machine had moved to the next state that could recognize the event and the timer did not get cancelled.  That is causing the route failure timeout to fire.

Thanks for your reply, I will try to find out what is going on by adding some additional logging

I released another patch for this router into incubator yesterday.  COuld be related to the original issue, since the result was the route getting stuck (it had to do with more than one component having the same ident, but only one being a  router target). Released.


feat: add new blog Pulumi in a Cloud Native World

Proposed changes

Unreleased product version (optional)

Related issues (optional)

@SaraDPH


A problem occurred during Paytrail Api connection: Items units can't be a negative number

I have an order with 3 x 74.65 priced product, 9.90 shopping row and discount code of 10.
in file: vendor/paytrail/paytrail-for-adobe-commerce/Helper/ApiData.php::getOrderItemLines
we get a $itemSum != $orderTotal which created the rounding-row with units of -1 .
Then, in file: vendor/paytrail/paytrail-php-sdk/src/Model/Item.php::validate
we have this validation:
if ($props['units'] < 0) {
throw new ValidationException('Items units can't be a negative number');
}

Issue can be replicated with any qty 3 products that have any price and a cart discount applied of 10 euros.
On the roundings in the module, the discount is substracted from the items at line:
vendor/paytrail/paytrail-for-adobe-commerce/Model/Token/RequestData.php::getItemArgs
floatval($item->getPriceInclTax()) - round(($discountIncl / $item->getQtyOrdered()), 2),
since 10 divided by 3 it's resulting into 3.33 and sum of 3.33 + 3.33 + 3.33 = 9.99 the rounding diff of 0.01 if present there for rounding item is created in such manner that IF statement from here: $roundingItem->setUnits(($orderTotal - $itemSum > 0) ? 1 : -1); will populate the value with -1

Thanks for reporting, we will look in to this.

Issue has been fixed with new version 1.4.4


configuraiton for bitswap checks

These are options for https://github.com/ipfs/go-ipfs/issues/8157

go-ipfs-config got merged into go-ipfs repo: https://github.com/ipfs/go-ipfs/tree/master/config
If you feel this PR is still relevant, please reopen as a PR against go-ipfs


fix(plugin): support outputs without inline initialization

Previously, this script would fail with a cryptic message (cannot read property of undefined (reading includes)) for input like:
@Output() myOutput: EventEmitter<string>;

The changes support that use case and:

Uses the initialization in the constructor to infer the type (and removes it)
Creates an initialization (= output()) if it doesn't exist

@all-contributors please add @ShacharHarshuv for code

@ShacharHarshuv sorry that this falls on you but apparently the lint target fails because convert-output is affected by this change. Can you fix the lint issue? Thank you.

@nartc I believe it should be fixed now


French doc translation

i start to translate the documentation.

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

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

@Exvilia This is a great start - could you finish translating the rest of this, too? Then I can merge it.

@Exvilia If you have time to finish the translation, we would welcome it. I'm closing this for now.


Unit Upgrade Maintenance Cost

Is your feature request related to a problem? Please describe.
It would be great to know the ongoing maintenance costs of a unit before upgrading it.
Describe the solution you'd like
To see the potential maintenance costs besides the required resources to upgrade a unit.

See where exactly?

In the tooltip when you hover over the upgrade button. Is it possible at all?

Yes, it is possible.
I implemented similar functionality in Better Report Screen. When you wanna upgrade a unit then the tooltip shows besides the usual info also a resource base and maintenance costs.

Kudos to you and the main devs for allowing such level of flexibility!
On a side note, despite probable infeasibility, it could be fantastic if partial upgrade of a unit was allowed, rather than only to the latest tech. It could surely help reduce maintenance costs, and potentially, if offered at a discount, the upfront cost of the upgrade as well.

Completed.


Add entire deployment preview

Sometimes the annotators like to see the entire deployments annotations while annotating. In the old VARS there was a bulk editor that allowed that. While the plan is to add the same bulk editor, in the interm maybe just opening a non-editable, preview pane to display all the annotations in a seperate window may be useful.

Added this. There's a grid button on the toolbar to display all annotations in the same video sequence. Data load is paged so as not to overwhelm the server.  The window that is displayed will be disabled until all the annotations are loaded.


useNetInfo - isConnected initial state is false

Environment

System:
OS: macOS 10.15.2
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 280.56 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.13.0 - ~/.nvm/versions/node/v12.13.0/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.12.0 - ~/.nvm/versions/node/v12.13.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 22, 23, 24, 25, 26, 27, 28, 29
Build Tools: 22.0.1, 23.0.1, 25.0.0, 25.0.1, 25.0.2, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.3
System Images: android-24 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom, android-26 | Google Play Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8<IP_ADDRESS>10548
Xcode: 11.3/11C29 - /usr/bin/xcodebuild
npmPackages:
react: 16.12.0 => 16.12.0
react-native: 0.61.5 => 0.61.5
Platforms
Both
Versions

react-native-netinfo: 5.3.3
react-native: 0.61.5
react: 16.12.0

Description
useNetInfo returns false as initial value of the isConnected network state. After event callback isConnected takes it actual value. As far as we display a message in case if connection is not available this result in message blinking. This could be fixed by making initial state of isConnected - undefined or null.

👋 I'm not sure I fully understand the issue. Can you provide more details about what the current behaviour is and what behaviour you are expecting?

I am having the same issue. I have to render a message for offline connection that depends on the hook value and this show the first time for less than a second. I logged the values on the console and I figured out this was happening because the hook reports the following values the first time as it is not connected neither to internet nor to a network:

But after a short moment, it shows the correct values

Here is a possible workaround:
        const [isConnected, setIsConnected] = React.useState<boolean>(true);

	React.useEffect(() => {
		const unsubscribe = NetInfo.addEventListener(state => {
			if (state.isInternetReachable === false) {
				setIsConnected(false);
			} else {
				setIsConnected(true);
			}
		});

		return () => unsubscribe();
	}, []);

@matt-oakes - @StebanDev provided an additional details. Do you need anything else?

@its-wufu actually I am using that workaround but I would like to make it work using just the hook.

This also bothers me.
In my particular case I would like show a popup when isConnected === false.
Without the hook this line prevented to show the popup on startup
if (!netInfoState.isConnected && netInfoState.isConnected !== null
I can't use the isReachable since this is another use case. The app is white listed by the phone company so users can use the app without  having mb's. So connection is true and isReachable false.

+1

+1

I'm using this workaround for now btw
https://gist.github.com/julioxavierr/12ef1f153d6acc01e79d8cb8a55c0efd

these is an even better solution provided in the package already:
the result of useNetInfo() als provides a type, this type is initially set to "unknown", so you can just check that.
So only act when type is not "unkwown"

@RikSchefferOberon this is still a wrokaround)

Does anyone have any idea to solve that issue, is it able to set another default value to useNetInfo?

@ferhanakkan just write your own useNetInfo)
Copy/paste from original and adjust to your needs.

I was also dealing with this issue. My app has a banner to warn users when the app has no internet connection. So when loading a new screen, the 'false' default showed a blinking banner for about a quarter of a second. I copy and pasted the hook from the source code like so to get around it:
const [netInfo, setNetInfo] = useState({
    isConnected: true,
    isInternetReachable: true,
  });

  useEffect((): (() => void) => {
    return addEventListener(setNetInfo);
  }, []);

Hope that helps someone here.

Here is a possible workaround if you want to use isInternetReachable which can also be null or undefined:
        const [isConnected, setIsConnected] = React.useState<boolean>(true);

	React.useEffect(() => {
		const unsubscribe = NetInfo.addEventListener(state => {
			if (state.isInternetReachable === false) {
				setIsConnected(false);
			} else {
				setIsConnected(true);
			}
		});

		return () => unsubscribe();
	}, []);

this was helpful for me in my case.

it would be better if useNetInfo() have a loading kind of things

Here is a possible workaround if you want to use isInternetReachable which can also be null or undefined:
        const [isConnected, setIsConnected] = React.useState<boolean>(null);

	React.useEffect(() => {
		const unsubscribe = NetInfo.addEventListener(state => {
			if (state.isInternetReachable === false) {
				setIsConnected(false);
			} else {
				setIsConnected(true);
			}
		});

		return () => unsubscribe();
	}, []);

I also use the same solution and make isConnected null by default which means that netInfo is in loading state

Another workaround for people who need the exact value at a specific point in time but do not care about tracking the state, you can use the non hook call version:
    static hasInternetAsync = async () => {
        let netInfo = await NetInfo.fetch()
        return netInfo && netInfo.isInternetReachable
    }

It is however still a workaround..


drivers: ieee802154: Develop 15.4 native_posix radio_api with BabbleSim

Adds native_posix radio hardware model built using BabbleSim
as well as ieee802.15.4 radio api implementation. This component
enables performing tests of higher layers of networking stacks.
Due to lack 802.15.4 physical layer support in BabbleSim,
some features (like lqi, rssi) are missing. The communication
between devices is made with phy_2G4_libPhyComv1 using workarounds
(all devices share the same phy address) so phy2G4 can see packets
as they were Ble packets. Frames validation, filtering, ack generation
etc. in ieee802.15.4 radio_api driver is made using the code from
ieee802.15.4_nrf5. Sample samples/ieee802154 was made for testing
the native_posix 15.4 driver and consists of two programs: device0
and device1, which exchange 802.15.4 frames.
Signed-off-by: Filip Zajdel<EMAIL_ADDRESS>

Files with prefix nrf_802154_* were copied from https://github.com/nrfconnect/sdk-hal_nordic.

@aescolar I pushed some changes regarding your comments.

@tbursztyka
Thank you, next PRs will have better explanation.
The thing I am working on is developing the generic emulation of radio which lives in native_posix board and uses BabbleSim (physical layer simulator). The solution similar to nrf52_bsim board, but more generic; without emulation of registers etc. Then I'm going to use it for ieee802154 radio_api implementation, and finally it can be used to simulate Zigbee (and Thread maybe) using PC with no need of development kits.
I will split it into 3 commits:

will add bs_radio module in native posix board.
will add ieee802154 driver.
will add sample application.

Does it sound relevant?


feat(decide): clone user-context before calling optimizely decide

Summary
Clone the current user-context and pass it to optimizely.decide()

user context can be changed while processing the decide request.
with this fix, decide can return the copy of the original user-context as a part of the decision

Test plan

Validate user-context are copied and passed as expected

Pull Request Test Coverage Report for Build 1641

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 89.776%

Totals

Change from base Build 1633:
0.08%

Covered Lines:
4417

Relevant Lines:
4920

💛  - Coveralls

Pull Request Test Coverage Report for Build 1641

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 89.776%

Totals

Change from base Build 1633:
0.08%

Covered Lines:
4417

Relevant Lines:
4920

💛  - Coveralls


fix(ecau): drop images without jQuery

So apparently my previous experimentation didn't go far enough and it turns out we don't actually need jQuery to get MB to handle the drop event. The reason we were using jQuery was that we can't "officially" instantiate our own DropEvents with a FileList with our own files in the dataTransfer property (either because of read-only properties, private constructors, or some other security precaution). However, I never tried just defining the necessary properties using Object.defineProperty, which can circumvent the readonly status. Turns out, that just works. :tada:
Fixes #440.
Tested with Firefox/Violentmonkey, will test with the other popular combinations of browser/userscript engine after deploying the preview.

/deploy-preview please.

Tested successfully with all major browser/userscript engine combinations :tada:
Greasemonkey was being naughty again though, but that's also been fixed.

/deploy-preview because the bot doesn't listen to edited comments 🙄

Good point, I actually only tested with VM Beta on Firefox (Chrome was the non-beta version). I have no reason to believe it won't work on VM stable in FF or VM Beta in Chrome, but I'll double-check before merging.

Well, you already did more tests than I would have done, so I definitely won't complain 😂
I just wanted to make sure that it actually fixes the problem with VM Beta (which I still haven't installed in any browser).

I really needed to downgrade VM to the stable version anyway to verify whether #465 was because of VM beta. Can confirm this fix works on Chrome/VM beta and FF/VM stable too.


For consideration: Support of UART type of network devices.

for example:
cheap UART WiFi - http://www.instructables.com/id/Using-the-ESP8266-module/

as additional information take a look at https://github.com/r-map/rmap/blob/master/arduino/sketchbook/libraries/PubSubClient/PubSubClient.h#L12
uncommenting those lines I can use a pached PubSubClient library to use sim800 with this library:
https://github.com/r-map/rmap/tree/master/arduino/sketchbook/libraries/sim800
A virtual class definition should be better to change type of TCPCLIENT

@pat1 alternatively, the sim800 library could properly declare it implements Client.h and no changes would be needed in this library...

thaks @knolleary
sim800 library I have written declare:
class sim800Client : public SIM800
at
https://github.com/r-map/rmap/blob/master/arduino/sketchbook/libraries/sim800/sim800Client.h
I have to study I how to do it


Don't use splash minimum display time in editor

Solves https://github.com/godotengine/godot/issues/22073#issuecomment-1633036619

Thanks!

Cherry-picked for 4.1.2.


Run with -? for options

-------------------------------------------------------------------------------
integration: analytics index management
-------------------------------------------------------------------------------
/home/couchbase/jenkins/workspace/c-cpp/cxx/cxx-scripted-build-pipeline/ws_centos8/couchbase-cxx-client/test/test_integration_management.cxx:1154
...............................................................................

/home/couchbase/jenkins/workspace/c-cpp/cxx/cxx-scripted-build-pipeline/ws_centos8/couchbase-cxx-client/test/test_integration_management.cxx:1154: FAILED:
due to a fatal error condition:
  SIGABRT - Abort (abnormal termination) signal

===============================================================================
test cases: 1 | 1 failed
assertions: 1 | 1 failed

test this please


Updaqted note to clarify storage impact

Category

[x] Content fix
[ ] New article

Related issues

fixes #460

Contents of the Pull Request
Added info to note explaining impact of storage from versions

Docs Build status updates of commit 4f3f024:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/versioning-basics-best-practices.md
:bulb:Suggestion
View
Details

CHANGELOG.md
:white_check_mark:Succeeded

Community/versioning-basics-best-practices.md

Line 78, Column 48: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/sql/relational-databases/track-changes/about-change-data-capture-sql-server' will be broken in isolated environments. Replace with a relative link.
Line 92, Column 14: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/sharepoint/governance/versioning-content-approval-and-check-out-planning' will be broken in isolated environments. Replace with a relative link.

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


UAA-Release v77+ Breaking Changes Planning

In consideration for v77

Feature removal: UAA functions as a SAML IDP

Deprecation notice: Published in README.
Progress: https://github.com/cloudfoundry/uaa/pull/2638

Feature removal: New Relic integration

Deprecation notice: None but asked around.
Progress: https://github.com/cloudfoundry/uaa-release/pull/760

Feature removal: UAA native MFA

Deprecation notice: Published in README.
Progress: Not started.

Other candidates

removal: user_token grant

discussion here: https://github.com/cloudfoundry/uaa/pull/2193

removal: password, implicit_grant
removal of already-deprecated SAML IDP configs:

config.socketFactoryClassName
config.samlConfig.certificate
config.samlConfig.privateKey
config.samlConfig.privateKeyPassword
config.links.logout.disableRedirectParameter

Deprecation notice: Published on UAA API docs.

removal of the already-deprecated Introspect Token endpoint's "Authorization header = Basic authentication" option

Deprecation notice: Published on UAA API docs.

removal of The /check_token endpoint

Deprecation notice: Published on UAA API docs.

remove k8s related support
remove option to use empty string as client secret
formal removal of MySQL 5 support (flyway upgrade)
fix introspect (maybe create a v2 endpoint but deprecate the old one)

https://github.com/cloudfoundry/uaa/issues/1229

@peterhaochen47 is there a plan, when you will release v77 ?

@strehle, on our side, the only outstanding item is the MFA feature removal, which is underway (ETA = a few days). Your colleagues said in our last OSS sync that your team had no outstanding item for v77 but was also not in urgent need to release, is that accurate?

Your colleagues said in our last OSS sync that your team had no outstanding item for v77 but was also not in urgent need to release, is that accurate?

No urgency, correct but after 3 weeks now I simply would think about a release simply that we have CI into cf-deployment
So after next sync on Thursday I suggest we release. MFA removal is ok, I assume it should be less effort than SAML IDP.


storageClass in values.yaml not used correctly in platform.yaml

https://github.com/odpi/egeria-charts/blob/main/charts/egeria-base/templates/platform.yaml
In above link the last lines contain a typo.
the first line below has storageClass (start with lowercase)
then 2nd line below has StorageClass (start with uppercase).
Since it is case sensitive the value will not be used to set the storageClassName
{{ if .Values.egeria.storageClass }}
storageClassName: {{ .Values.egeria.StorageClass }}
{{ end }}

thanks for spotting!

Storage Class setting is not supported across all charts - some extras are commented out
This work needs completing across all charts - will keep issue open to track

Fixed by #252


Fix wrong syntax

Current syntax for target_include_directories is wrong, and causes the followin exception:
target_include_directories called with invalid arguments

@Mergifyio backport foxy galactic rolling


SIGABRT when using @google-cloud/resource-manager, with trace events, and doing a process.exit(0)

Environment details

which product (packages/*):  @google-cloud/resource-manager
OS: macosx
Node.js version: v18.14.2
npm version: 8
google-cloud-node version: 4.3.0

Steps to reproduce
If you use the google-cloud/resource-manager and then also implement shutdown hooks within your application that gracefully stop things like a webserver, before doing a process.exit(0); then you end up with a SIGABRT:
❯ NODE_OPTIONS="--trace-events-enabled --trace-event-categories v8" node test.js
hi
hi
hi
hi
hi
^C[1]    55453 abort      NODE_OPTIONS="--trace-events-enabled --trace-event-categories v8" node test.j

This code reproduces the issue:
const Crm = require('@google-cloud/resource-manager')
const client = new Crm.ProjectsClient()

const interval = setInterval(() => {
  console.log('hi')
}, 500)

const shutdown = () => {
  process.exit(0)
}
process.on('SIGINT', shutdown)
process.on('SIGTERM', shutdown)

I've also raised https://github.com/nodejs/node/issues/48598; which could be related


feat: ✨  icon for ruff config file

Description
File Icon for ruff config file.
Closes: #2755
Contribution Guidelines

[x] By creating this pull request, I acknowledge that I have read the Contribution Guidelines for this project
[x] I have read the Code Of Conduct and promise to abide by these rules

In my fork, I had two variations for light and dark themes using light green and purple (both are brand colors).

But here I went with a 1 svg file solution using a darker green.
Let me know what you guys think.


node_type_id field in the NewCluster Section States "This field is required"

In the NewCluster section the documentation states This field is required.  This is not the case when an instance_pool_id is provided.

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

ID: 94757e87-8be2-3279-4a7e-51fbbaf7d678
Version Independent ID: 9cfad152-bba2-390c-edce-63d3aba3f4fa
Content: Jobs API - Azure Databricks - Workspace
Content Source: databricks/dev-tools/api/latest/jobs.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

We have assigned the issue to the content author . They will evaluate & update the document as appropriate

Thanks for providing feedback that helps improve our documentation. This issue has been resolved and we are closing the issue.
#please-close

#please-close


documenting XLA flags used by MaxText

Added the XLA Flags that MaxText uses to the README

Sorry folks -- I messed this PR up with manual merges.  I'll resubmit a new one.


Create deployment task for deploying in Azure Devops pipelines

It would be useful to have a deployment task for deploying .bicep files from pipelines within Azure Devops.

Closing and tracking in https://github.com/Azure/bicep/issues/1341


display_plan is not implemented

Can you take a look at this?
Traceback (most recent call last):
  File "run_dialog.py", line 494, in <module>
    main(args)
  File "run_dialog.py", line 463, in main
    runner.run(args)
  File "run_dialog.py", line 380, in run
    self.one_run(run_id)
  File "run_dialog.py", line 223, in one_run
    self.display_plan(plan, save_name=f"vis_llm_plan_{i}", save_dir=step_dir)
  File "run_dialog.py", line 156, in display_plan
    raise NotImplementedError
NotImplementedError

I got the following error when enabling --skip_display.
INFO:root:Stesp: 0 Plan success: True, reason: ReasonDirect_time1.5149331092834473_iter1
INFO:root:Execute the plan for 43 steps
Traceback (most recent call last):
  File "run_dialog.py", line 494, in <module>
    main(args)
  File "run_dialog.py", line 463, in main
    runner.run(args)
  File "run_dialog.py", line 380, in run
    self.one_run(run_id)
  File "run_dialog.py", line 273, in one_run
    obs, reward, done, info = env.step(sim_action, verbose=1)
  File "/Users/zwhe/GitRepo/robot-collab/rocobench/envs/base_env.py", line 646, in step
    if error_dict['error'] < self.error_threshold and step > self.render_freq * 2:
IndexError: invalid index to scalar variable.

I had the same problem, have you solved it yet?

Not yet
Katuwawala @.***>于2023年9月10日 周日17:11写道：

I had the same problem, have you solved it yet?
—
Reply to this email directly, view it on GitHub
https://github.com/MandiZhao/robot-collab/issues/5#issuecomment-1712760651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH6XQCD5XW5PUDSQTPV7F3DXZV72LANCNFSM6AAAAAA4EHWQCA
.
You are receiving this because you authored the thread.Message ID:
@.***>

hi @zwhe99 @BrahamVictor ! sorry for the late reply, the issue should be fixed in this commit: https://github.com/MandiZhao/robot-collab/commit/12b8dc9f2cc34a59cca48aae05df52782aea0c49, please let me know if you are able to run the script now

also, check out this commit for (preliminary) code for enabling display_plan: https://github.com/MandiZhao/robot-collab/commit/9943870298e650de7ff1f9231ed279b35f196ddc, it requires install open3d, and basically shows the plan and the workspace as a voxelized 3D scene


sphinx.ext.viewcode source links missing

I have the problem that sphinx.ext.viewcode sourcelinks show up in my local build (using the readthedocs theme) but not on readthedocs builds.
I am not sure if this is a bug report or a question, but I really am running out of ideas what I could be doing wrong. I am a new user of readthedocs so I might be missing something obvious, but there are other bug reports about this (1, 2) and google does not come up with much help either.
source: https://github.com/obestwalter/mau-mau (conf.py)
readthedocs project: http://readthedocs.org/projects/mau-mau/
build (from same code version where it works locally): https://readthedocs.org/projects/mau-mau/builds/3905985/
example (of not working on readthedocs): http://mau-mau.readthedocs.org/en/doc-with-sphinx/code/mau_mau/#submodules

Also having this problem: http://zarr.readthedocs.org

@obestwalter last link you provided works properly to me. Was this problem fixed?
@alimanfoo it seems that sourcelinks are working properly in your build. Am I right? Do you still have this problem? What did you change to fix it?
Can I close this issue?

@humitos If you refer to my example (http://mau-mau.readthedocs.io/en/doc-with-sphinx/code/mau_mau/#submodules): no: there are no links leading to the sourcecode (or if there are some, I don't see them, or we are talking about two different things). This is no surprise either as it is still the same build.
Whether the problem is fixed now I couldn't say as I changed the docs tool and hosting the docs somewhere else (MkDocs and Github pages).

@humitos no, there are no source links I can see (e.g., http://zarr.readthedocs.io/en/latest/api/creation.html), this is still a problem AFAIK.

Sorry, I got confused. I build mau-mau and zarr in my own computer and I was able to see what you mean. I have a [source] link that works properly and goes to the code.
I'm not sure why this is happening in RTD and I think we will need to research a little. If you have any suggestion or possible cause, I would appreciate.
I'm marking this as a Bug at the moment.

Hi @humitos, thanks for following this up. I don't have any clue why this would only happen on RTD, sorry.

Hello,
I also had this problem and the source code and links started appearing after I added my src directory (which contains the directory for the package i'm documenting) to sys.path.
Before that source links did not appear even though I was building with virtualenv and autodoc worked just fine.

That is it! since my package has the source explicitely in a source folder, I had to update conf.py with   the magic redirect sys.path.insert(0, os.path.abspath('../src'))
out package contains ./src and ./docs with ./docs/conf.py (see https://github.com/schubergphilis/data-migrator/)

I can see the source link working on other projects without updating the conf.py file (http://pynvim.readthedocs.io/en/latest/api/nvim.html)
So, closing this. Anyone else having this issue, feel free to ask to reopen.

@stsewd - perhaps this is to do with the .readthedocs.yml file - https://github.com/neovim/python-client/blob/master/.readthedocs.yml

I don't think so, those settings (from the linked file) don't have anything to do with sphinx.

@stsewd  - the setup_py_install setting from that file does seem to have a lot to do with sphinx and its ability to produce 'source' links. It determines whether or not to install a project before building documentation, which could make a big difference as to whether your code is importable or not, which is how sphinx.ext.viewcode works. So, for example, when I am building docs locally, if I don't do a ./setup.py install first and there are missing dependencies, when building docs the source links disappear.
Anyway, I tried with this .readthedocs.yaml file:
python:
  version: 3.5
  setup_py_install: true

And it didn't fix it for me.  I also tried with exactly the same .readthedocs.yml file as the one linked, and this also didn't work.
So my projects still don't work - see for example http://parsy.readthedocs.io/en/latest/ref/primitives.html - this should have a [source] link, and it is present when I build locally with a range of Sphinx versions, but not present on readthedocs. I have tried various sys.path changes in docs/conf.py but these also don't work. It's still broken for me :-(

@spookylukey I'll see if I can research a little more on your project.

I wasn't able to make the source link work locally. How are you testing this?

@stsewd
mkvirtualenv --python=`which python3.5` parsy-docs-test
git clone git@github.com:python-parsy/parsy.git
cd parsy
./setup.py develop
# (or ./setup.py install, both work)
cd docs
pip install sphinx
make html
firefox _build/html/ref/primitives.html

This worked with the repo as it was. To make it easier, I've just explicitly [re-added]( a 'sys.path' change to the docs/conf.py file, and now you don't need to do ./setup.py develop (but it doesn't harm if you do). I've pushed my change to sys.path but it still doesn't work on RTD - http://parsy.readthedocs.io/en/latest/ref/primitives.html

@spookylukey hey, I just saw that there is a source link now :)

OK, I see that now. There must have been some caching because it wasn't there before, meaning I'm not sure which thing finally fixed it.  (I've just realised there is a revision number at the bottom of the docs pages which helps check whether you've got the latest version!).
In this case, I think the fixes must have been:

a .readthedocs.yml file that enabled Python 3 (without which I'm probably getting import errors, since this project is Python 3 only)
having the sys.path.insert hack explicitly in the docs/conf.py. My project is different from the one you linked in that the source lives in project_root/src, not project_root, which could be the difference here.

In addition, I've just tried with another project, which has dependencies that need to be installed for the code to be importable. For this case, I also needed to add a .readthedocs.yml file with:
python:
  setup_py_install: true

Thanks for your help, hope this helps other people!

I'm also having this problem: https://whiskerpythonclient.readthedocs.io/ . A local build shows the [source] links, but the RTD version doesn't. The project is configured to use setup.py install via the web interface, and has identical RTD settings (except also enabling "Give the virtual environment access to the global site-packages dir", because it looks for numpy) as https://cardinalpythonlib.readthedocs.io/ -- which works.
Things that have not worked:

restricting setup.py to Python 3.5
changing the Sphinx theme to classic
poking the source directory into sys.path as described here

It's puzzling...

@RudolfCardinal
My current .readthedocs.yml file, which works for my case, is:
build:
  image: latest

python:
  version: 3.6
  setup_py_install: true

In addition I have the sys.path hacking in docs/conf.py

I've been trying to patch the same issue with my repo and tried the fixes presented in this issue, but without success.
adding to sys.path did not fix my problem. Neither did an installation of the pre-built wheel before starting the RTD-build. On a local virtenv I was able to build it without any problems, it's only the online RTD version that fails...
@alimanfoo Since it works in your referenced project (Zarr), what was your final fix?
@spookylukey Did it work for your RTD-version as well, or was it just local?


toco model

The toco model just doesn't run due to some error and due to that we just cannot deploy our models in android!

Can you please provide more information on the error and also on what it changed from when it was working vs now (e.g. upgraded to newer version of tf? trying to run on a new machine?).

"Doesnt build" does not help. Post the build error.

Closing this as there is no response received about the build error.
Please retry with the latest version of hub and create a new issue(if there are any errors). Thanks !


Azure Search: Resource Manager: Support 'None' Identity type

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

FYI @brjohnstmsft

Can one of the admins verify this patch?

Hello,
Could someone please approve this this very short changehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F5319&data=02|01|Nati.Nimni%40microsoft.com|cee5c68bd2164a84b4ff08d6a1979b84|72f988bf86f141af91ab2d7cd011db47|1|0|636874069852432948&sdata=%2Fc8p0NBx4ePZPmO0OIhyLBv5SxvEzD2yNc1LG%2BB58I8%3D&reserved=0? (opened for 2 days now)
Thank you,
Nati
From: Azure Builder<EMAIL_ADDRESS>Sent: Monday, March 4, 2019 6:51 PM
To: Azure/azure-rest-api-specs<EMAIL_ADDRESS>Cc: Nati Nimni<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-rest-api-specs] Azure Search: Resource Manager: Support 'None' Identity type (#5319)
Can one of the admins verify this patch?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F5319%23issuecomment-469514921&data=02|01|Nati.Nimni%40microsoft.com|6ac7cab423a54f7a62bf08d6a115721b|72f988bf86f141af91ab2d7cd011db47|1|0|636873510814871216&sdata=q7gcIlQipjaPYCid6k%2FT%2Bn5riyFmcD%2BQSCBrXH6uUhY%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZYRS9HvaS51Fk71VfS-dSISYK3QY4xuks5vTdungaJpZM4bdi3w&data=02|01|Nati.Nimni%40microsoft.com|6ac7cab423a54f7a62bf08d6a115721b|72f988bf86f141af91ab2d7cd011db47|1|0|636873510814871216&sdata=tSsTPdRFuRd4neri2fEu8aRiSsobxS2rkdUIhFPXT%2BQ%3D&reserved=0.

@sarangan12 Can you please review & merge this?

Done
From: Nati Nimni
Sent: Wednesday, March 6, 2019 10:15 AM
To: Azure/azure-rest-api-specs<EMAIL_ADDRESS>Cc: Sarangan Rajamanickam<EMAIL_ADDRESS>Subject: RE: [Azure/azure-rest-api-specs] Azure Search: Resource Manager: Support 'None' Identity type (#5319)
Hello,
Could someone please approve this this very short changehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F5319&data=02|01|sarajama%40microsoft.com|a0daa99cfe294538b5d308d6a25fa944|72f988bf86f141af91ab2d7cd011db47|1|0|636874929102227732&sdata=zm0wHUw7wDCg%2Fw0KRbDtpIJYIJCUiwKAo%2Brlj6MgbJE%3D&reserved=0? (opened for 2 days now)
Thank you,
Nati
From: Azure Builder <notifications<EMAIL_ADDRESS>Sent: Monday, March 4, 2019 6:51 PM
To: Azure/azure-rest-api-specs <azure-rest-api-specs<EMAIL_ADDRESS>Cc: Nati Nimni <Nati.Nimni<EMAIL_ADDRESS>Author <author<EMAIL_ADDRESS>Subject: Re: [Azure/azure-rest-api-specs] Azure Search: Resource Manager: Support 'None' Identity type (#5319)
Can one of the admins verify this patch?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F5319%23issuecomment-469514921&data=02|01|sarajama%40microsoft.com|a0daa99cfe294538b5d308d6a25fa944|72f988bf86f141af91ab2d7cd011db47|1|0|636874929102237745&sdata=fH46%2FFYbwsKGVqL1vcnbiGPhnUcpmsFAfZa8BHu2wbA%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZYRS9HvaS51Fk71VfS-dSISYK3QY4xuks5vTdungaJpZM4bdi3w&data=02|01|sarajama%40microsoft.com|a0daa99cfe294538b5d308d6a25fa944|72f988bf86f141af91ab2d7cd011db47|1|0|636874929102237745&sdata=Ml724xtn2L8r24G1iDMWdn3Im2NFAnAwa33MzXlbwbQ%3D&reserved=0.


write tests

Need to find a good amqplib mock..

I'm not thrilled with the tests, but they exist: #23..


feat(runtime-core): *.vue component type declaration

Added *.vue component type declarations

It is useful to have this inside the actual vue package, so developers don't have to create a declaration file, if they want to use Typescript.

Thanks for the PR - however, this is not the right file to place the declaration. (global.d.ts is for source code only). Also, this may not be needed in all cases (see https://github.com/vitejs/create-vite-app/pull/17#issuecomment-707447288)


Prepare Tables June 2024 Patch Release

API change check
API changes are not detected in this pull request.


Communal Helper Re-usable Spikes Bug

Bug Description
When Reusable spikes are used on a falling block, the reusable timer doesn't seem to work every time, sometimes it won't work.
Installed version of Communal Helper: PR 178
Details:
The first time this spike reset after triggered, the timers work fine, but the second and the third time, the spikes would reset 0.1 seconds after the spikes were triggered, ignoring the Reusable Timer, then surprisingly the 4th time the spikes worked again
Steps to Reproduce
Conditions:

Falling block fallen down
Reusable Timer was set to 2 seconds
Delay was set to 0.1 seconds
Grouped Spikes

Is this bug reproducible in the latest version? IIRC it's a bug of UnderDragon's repos


If we can upgrade version of bitflags in optee-utee

In cargo.toml of optee-utee crate, it lock the version of bitflags(set it must to 1.0.4):

However, in some other crates will require a newer version, for example, the raw-cpuid require version upper 1.2, and result in confliction:

So I wonder why optee-utee lock the version of bitflags and if it can upgrade the version of bitflags

I don't think upgrading dependencies should cause any issues, please feel free to propose corresponding PR.


Set the overwrite flag with true for the unknown multiple resources c…

…onfig
Some android mobile phone manufacturers will modify the aapt tool, it will lead to decode unsuccessfully.
If the overwrite flag is true, the decoded files is not complete fully, but decode successfully.

It was tested on the huawei honour 6 device successfully.

This may be something to look into for -m \ --match-original for researchers as this will allow custom apks to be decoded.
However, it should be very clear with a message. "Duplicate resource decoded (Possible incorrect decode) Ignoring _____ resource". With a flag to only activate if -m is used.
However, at that point we have -k / --keep-broken-res which would be the same as this. Appending ERR suffixes and keeping the resource. I might have to think this out more, but this is something that shouldn't go into mainline as we want to find out when the decode fails.

I can not understand it.

Your patch isn't a fix. Its intentionally skipping parts of code. We can't just skip resources. That means we have detected resources, but don't understand the qualifiers hence the why the duplicate resource arises.
The correct fix is to understand what Huawei does, which requires the source or some black box digging around their build tools to understand what qualifiers they added and what they mean.

I know that is not a perfect fix. If we can understand what huawei does, we should fix it as you said. But today is huawei , tomorrow may be lg, the day after tomorrow may be samsung.
The fix is a upset. We can not know what Huawei does, may never know, as we are passive.
The fix is useful for patchrom,  such as the miui patchrom project. I try the -m and -k option, the result is shown in the picture above.

I don't think LG or Samsung will ever have this problem. It seems to be a trait of Chinese based OEMs (Xiaomi & Huawei) to modify Android AOSP beyond what is required. AOSP has more than enough qualifiers to use and I see no reason for the changes that Huawei currently has.
This patch may work, but you are building APKs that don't match the original by throwing out resources that couldn't be identified.

I keep my opinion. I will build the 'apktool' by myself, as the 'patchrom' project  need to adapt the Huawei device. There are a large number of Huawei mobile phones in the world, as the market share of Huawei  is second only to Samsung.


STM32U5: Add PWR peripheral

Not quite ready yet - there are 4 registers that aren't in any SVD files, so I'll probably have to manually check on which devices they are available...
(FORCE_USBPWR, JPEGRAMPDS, VDD11USBDIS and SRAM6PDSx, see last lines of pwr_u5.yaml)

Well that was painful... I was able to use AN5766 as a guide but it was still quite annoying to go though those SVDs to check where it was correct and where not. Hopefully I got it right now.

Rebase on master branch, please.

Would you like me to squash the commits so far or leave them separate for now?

Let's squash.


Use more admin filters and search fields

Cute animal pic

Link to Trello card (if applicable)
https://trello.com/c/ocDP15n7/290-improve-admin-search-and-filters
Description
The commit messages say what you did; this should explain why and/or how.

[x] Description is in Trello card

Steps to test/reproduce
Visit the admin and search/filter away on all models!
Show me

 Improve admin search and filters


simple-build-dgcode installed but dgcode bundle not found

In short:
simple-build-system versions from 0.0.25 to 0.0.36 can't find dgcode as a dependency eventhough the simple-build-dgcode package is installed.
Longer version:
I've tried to use dgcode_projects with different version of the simple-build-system and simple-build-dgcode. I've found that I can only build the packages using a simple-build-system that is older than version 0.0.25.
The actual error message when trying to use sb  is:
 ERROR: Could not find dependent project: "dgcode"
The version of simple-build-dgcode (from 0.0.1 to 0.0.3) doesn't seem to matter.
The change from v0.0.24 to v0.0.25 included "Change py-plugin search pattern", so that could be the source of the problem.
The environment was created with:
name: dgcode
channels:
  - nodefaults
  - conda-forge
dependencies:
  - compilers
  - bash
  - simple-build-system
  - ncrystal
  - matplotlib
  - zlib
  - geant4
  - expat
  - openscenegraph
  - scipy
  - hdf5
  - pysimplegui
  - pip
  - pip:
    - simple-build-dgcode

The version of the packages were changed with:
pip install --force-reinstall -v "simple-build-system==0.0.25"

Ah yes, this is simply because the simple-build-dgcode package is not yet ready for usage (as the documentation says, "DO NOT USE YET!" :-) ). Please only use the latest simple-build-system package (I.e. reinstall the latest, currently v0.0.36), and wait ~a few days for the simple-build-dgcode package to have a new version.
In the meantime, if you are brave, you can try to use the tk_volatile branch of simple-build-dgcode, which should in principle work (although it is... you guessed it... volatile).
Maybe a command like:
python3 -mpip install git+https://github.com/mctools/simplebuild-dgcode@tk_volatile

You can now install from main as well, I am currently debugging the pypi deployment so the pypi packages are still still on the old.

Ok, it is working! Now please make sure you use the latest simple-build-system (0.0.36) and the latest simple-build-dgcode (0.0.6) packages, and I believe it should just work!


Fix attributes UUID stuff - I went a little too fast

Objective
I went a bit too fast yesterday and forgot a few Uuid::new_v4() at one location. @DasLixou pointed that out to me. Thx.
Solution
Fix it.

np :>


There should be a way to bypass words-cache in order to avoid permissions issues

Hi,
I have several operating system users that can access my python environment and I would like to be able to import my code from all of them. When I try to import safe I face the following issue:
  File "/my_code", line X, in <module>
    import safe
  File "python2.7/site-packages/safe/__init__.py", line 68, in <module>
    WORDS = _load_words()
  File "python2.7/site-packages/safe/__init__.py", line 63, in _load_words
    with open(_cache_file, 'wb') as f:
IOError: [Errno 13] Permission denied: '/tmp/safe-0.4.words.cache'

I am able to bypass the issue by creating a temporary file every time so my new user can import and generates a new file.
try:
   import safe
except IOError:
   os.environ['PYTHON_SAFE_WORDS_CACHE'] = os.path.join(tempfile.gettempdir(),"safe-%s.words.cache" % time.time())
   import safe

That means it creates a different file:
testrunner@7b827fc0c77e:/code$ ls -lrt /tmp/
total 392
-rw-rw---- 1 userX userX 197151 Oct 29 16:06 safe-0.4.words.cache
-rw-rw---- 1 userY userY 197151 Oct 29 16:17 safe-1572365877.62.words.cache

I've been taking a look on the performance improvements on loading the cached file or not and in my use case the benefits are not worth it.
I would prefer to have a more secure environment, do not use pickle so no-one can execute arbitrary code in case someone modifies this file, instead of having the file of words cached. As the link shows in the documentation: Warning: The pickle module is not secure against erroneous or maliciously constructed data. Never unpickle data received from an untrusted or unauthenticated source.
I think Safe should allow a way of avoiding the cache to be generated or at least not do it on import time so the application doesn't fail in my use case.
I would be happy to work on a PR if that sounds a good idea and we can reach a design agreement.

The issue has been solved with the merge of the PR above.


JSON serialization and deserialization?

I figure serialization should be pretty trivial with object mapping solutions such as Gson and Jackson
But deserialization (at least in Jackson) requires some boilerplate + some type information in the JSON tree itself (http://www.studytrails.com/java/json/java-jackson-Serialization-polymorphism.jsp)
Do you have any thoughts on this?

I don't know the answer to your question. You can try to tinker with custom TypeIdResolvers to implement deserialization.
At first it seems easier to include required annotations to generated code, but it may be better to feather explorer the problem and try to find more extensible solution that can be adapted to other serialization frameworks...


Add a custom user-agent header

Add a custom string for MSAM in the user-agent header through config of botocore library.

I reviewed all the applicable .py source files that are used from Core and it all looks good to me. Thank you! I will close this one.

We'll need to update the format to match other AWS solutions.


Removing 'rawNvConfig' to refrain of unstable NIC states in DPU mode

Removing 'rawNvConfig' since it was causing BF3/2 NICs to enter an unstable state once changing NIC mode from NIC to DPU
We should add and fix unstable states on next releases

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 59.064%

Totals

Change from base Build<PHONE_NUMBER>2:
0.3%

Covered Lines:
1792

Relevant Lines:
3034

💛  - Coveralls


Creating a new edge creates another useless edge

Title
Creating a new edge creates another useless edge
Expected Behavior
Only created Edges are displayed.
Current Behavior
In addition to the created Edge, another Edge will be created at (0, 0) position.

Possible Solution
In src/utils/graph.ts, return of add Edge function fix.
export const addEdge = (edgeParams: Edge | Connection, elements: Elements, defaults?: DefaultEdgeOptions) => {
  if (!edgeParams.source || !edgeParams.target) {
    console.warn("[vueflow]: Can't create edge. An edge needs a source and a target.")
    return elements
  }

  let edge
  if (isEdge(edgeParams)) {
    edge = { ...edgeParams }
  } else {
    edge = {
      ...edgeParams,
      id: getEdgeId(edgeParams),
    } as Edge
  }
  edge = parseEdge(edge, defaults)
  if (connectionExists(edge, elements)) return elements
  elements.push(edge)
  return elements
  // return [...elements, edge]
}

As I said in the PR: I would in general recommend not using addEdge and instead using addEdges provided by useVueFlow.
addEdge is just a "legacy" version of addEdges and will most likely be removed in the future as it a) skips creating an actual change for Vue Flow (i.e. no EdgeChange of Type AddEdgeChange is triggered) and b) it skips applying default edge options that have already been defined as an option/prop.
If you're using Vue Options API try using it like this:
<script>
import { VueFlow, useVueFlow } from '@braks/vue-flow'

const { addEdges } = useVueFlow({ id: 'options-api' })

export default defineComponent({
  components: { VueFlow },
  data() {
    return {
      elements: [
        {
          id: '1',
          label: 'Node 1',
          position: { x: 0, y: 0},
        }
      ]
    }
  },
  methods: {
    // regular event handler
    handleConnect: (params) => {
      addEdges([params])
    }
  },
})
</script>

<template>
  <VueFlow v-model="elements" id="options-api" @connect="handleConnect" />
</template>

That should work and be more future proof :)
Though I would generally recommend just switching to composition API - you'll be better off using composition in the long run.

Fixed with #154

Thank you for your suggestion!
I will use addEdges


this repo is done

We are no longer maintaining this repo.  make it obvious.
fixes #85

we can also use the newish github archive feature


docs: fix open an issue link reference

Hi 👋
I noticed that the reference to of the link to open an issue in README.md had a missing u. I added it.

Landings this since it’s minor fix and it’s been opened for over 24hrs. Thank you @ricguti


[Enhancement] Refactor AllocateMachineRoomNearby

Before Creating the Enhancement Request

[X] I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary
Refactor
Motivation
Make the code better and better
Describe the Solution You'd Like

Consistency in abstraction levels
Use method names instead of comments
Make the code more concise: inline the result returned by a successful condition into a block of code.

AllocateMachineRoomNearByTest ran successfully
Describe Alternatives You've Considered
none
Additional Context
No response

fixed by #7789


Language Model

Hey!
In the paper you mention that you had a relative CMOS increase of 0.22 when using ELECTRA vs BERT as the pretrained language model.
Do you have any audio samples demonstrating text inputs that have noticeable improvement?

Bump!

The datas are in my previous company, and it's difficult to retrieve it now because I have left the company. I would appreciate your understanding.
By the way, according to the policy of my previous company, we have decided to upload only the RWEN-related code, excluding the TTS module (e.g. fastpitch, vits).
It is scheduled to be uploaded within this month, so please wait for it.
Thank you.


How can I install this program？

Sorry to bother,I know this is a stupid question but I a fresh in Python works,I really want to know how I can change the whole py files into exe and open it.

Pre-built exe is deployed in actions (find it on the top menu bar of this repo), no need to learn python anyway.

I don't know what to say, but please accept my gratitude,I found it.


Bump framework version

Bump framework version: 5.25.348 -> 5.25.349

PR Builder passed with https://github.com/wso2/carbon-identity-framework/pull/4937#pullrequestreview-1635993410


typo

lil typo

Current dependencies on/for this PR:

master

PR #1384   👈

This comment was auto-generated by Graphite.


Does a configuration exist within knip, akin to resolve.extensions in webpack, that could potentially be utilized?

When I use knip in vue project, it's imperative to inscribe the comprehensive directory, analogous to 'xx/xx/xx.vue', to ensure the file's detectability.
Does a configuration exist within knip, akin to resolve.extensions in webpack, that could potentially be utilized?

Not 100% sure what you mean, but did you see https://knip.dev/features/compilers/? This explains how you can include .vue files in the analysis.

Sorry. the example below is working as expected
import ComponentA from './ComponentA.vue'

when remove '.vue' in code, ComponentA will report as Unused files
import ComponentA from './ComponentA'

I consider knip can add feature like resolve.extensions to detect file in order,otherwish many project need much work to use knip.

In theory I think this would be possible, but I don't plan to support this. It introduces complexity and it's not good for performance.
I recommend to be explicit and use extensions. This is better for performance and module resolution. CommonJS did not, but ESM also requires extensions.
The framework Vue itself also shows the .vue extenions in their docs and examples, right? So let's follow best practices.


Fix #796 (A13-3-1) - Consider reporting overloaded functions that are at different locations.

Description
This PR fixes #796. In some cases CodeQL returns an overloaded function (from getAnOverload) of a candidate function that has the same location as the candidate function. The condition of occurrence is not yet concluded. However, this behavior causes confusion about which function is being referred to in the alerts generated by A13-3-1. In such cases, the overload and overloaded Function objects end up referring to the same function, which doesn't seem correct. Hence, it is proposed to add a check that examines the location of the overloaded functions and consider to report it only when they are different.
Change request type

[ ] Release or process automation (GitHub workflows, internal scripts)
[ ] Internal documentation
[ ] External documentation
[x] Query files (.ql, .qll, .qls or unit tests)
[ ] External scripts (analysis report or other code shipped as part of a release)

Rules with added or modified queries

[ ] No rules added
[ ] Queries have been added for the following rules:

rule number here

[x] Queries have been modified for the following rules:

A13-3-1

Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:

The structure or layout of the release artifacts.
The evaluation performance (memory, execution time) of an existing query.
The results of an existing query in any circumstance.

If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?

[x] Yes
[ ] No

🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.

[ ] Confirmed

Reviewer: Confirm that either a change note is not required or the change note is required and has been added.

[ ] Confirmed

Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author

[x] Have all the relevant rule package description files been checked in?
[x] Have you verified that the metadata properties of each new query is set appropriately?
[-] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
Since the minimized test case couldn't be created, the tests are not updated. However, the changes proposed are an additional fail-safe rather than any change in the existing algorithm.
[x] Are the alert messages properly formatted and consistent with the style guide?
[x] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[x] Does the query have an appropriate level of in-query comments/documentation?
[x] Have you considered/identified possible edge cases?
[x] Does the query not reinvent features in the standard library?
[x] Can the query be simplified further (not golfed!)

Reviewer

[ ] Have all the relevant rule package description files been checked in?
[ ] Have you verified that the metadata properties of each new query is set appropriately?
[ ] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[ ] Are the alert messages properly formatted and consistent with the style guide?
[ ] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[ ] Does the query have an appropriate level of in-query comments/documentation?
[ ] Have you considered/identified possible edge cases?
[ ] Does the query not reinvent features in the standard library?
[ ] Can the query be simplified further (not golfed!)

Hi @lcartey : Thanks for your help and support as always! Kindly let me know your valuable opinions on this PR.


Back-port v2.1 features to v1.3 for Rails 6 users

Please see #26 for details.

(Self-merged as it's just pulling already-reviewed code in and tests all pass).


No Sound?

General troubleshooting tips
Before logging an issue please check that:

[ ] You have the latest version installed (There may be a beta version that fixes your issue), see here for the latest releases and bug fixes: https://github.com/JohnCoates/Aerial/releases
[ ] Your issue isn't already mentioned in our issues. You may find a workaround there or a similar request already made.
[ ] Your problem isn't mentioned in the troubleshooting section.

If none of this fixes your issue, tell us about the problem you are experiencing or the feature you'd like to request.
Required information
In order to help us sort your issue, we ask that you provide the following information:

[ ] Mac model: IMac Retina 5K, 27 inch, 2019
[ ] macOS version: Catalina 10.15.4
[ ] Monitor setup:

If appropriate, please enable Debug mode and Log to disk in Advanced tab and replicate your bug, then attach the AerialLog.txt file (You can access this file through the Advanced tab).
Description of issue / Feature request
I get no sound with my videos. They are .mov and they have sound, but not when used for screen saver. What am I missing? Is there no sound with this app? Thanks.

Hi @cptwalker1
Do you mean with Custom Videos you've added yourself ?
The Apple TV videos have no sound, and by request from others I do mute the sound on custom videos (the general feeling was that it was distracting for a screensaver). Is that your issue ?

Yes. Thank you for the quick response. A function to turn on or off the sound would be nice. That way ASMR videos would be nice as a screensaver.

Yes. Thank you for the quick response. A function to turn on or off the sound would be nice. That way ASMR videos would be nice as a screensaver.

Ha I see. Yep that would definitely make sense for those videos. I'll get back to you tomorrow, should be an easy fix.

@cptwalker1 give a shot to beta5 : https://github.com/JohnCoates/Aerial/releases/download/v1.8.3beta5/Aerial.saver.zip
There's a new checkbox in advanced tab, uncheck to unmute sound.

Perfect!
Sent from my iPad

On Apr 23, 2020, at 10:03 AM, Guillaume Louel<EMAIL_ADDRESS>wrote:

@cptwalker1 give a shot to beta5 : https://github.com/JohnCoates/Aerial/releases/download/v1.8.3beta5/Aerial.saver.zip
There's a new checkbox in advanced tab, uncheck to unmute sound.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


How to watch in a docker container remotely

i already added the icons dependency on adapter level.
now the build is working.
now i look for a solution for the watch command, because
i use a docker container on a remote machine (not wsl on windows)
Originally posted by @oweitman in https://github.com/ioBroker/adapter-react/issues/22#issuecomment-914473325

@oweitman What is exactly your setup and why do you need to run the adapter in a container on a remote machine?

I have various docker containers running on my nuc with a lot of main memory.
In addition to my productive iobroker, I also have my test iobroker running, with which I can quickly delete everything and start over again
I would like to have the same as development, so that ideally I can develop the adapters separately from each other.
the development of the adapter part works perfectly with the help of the portainer console to start and stop the adapter in debug mode. I am currently still using chrome as a debugger but would like to switch to vs code
Half a year ago, I built a less than optimal solution for the adapter react part, in which the react build starts after each save and "iob uplod adapter name" is then automatically executed. that would be the part that I would like to optimize. the release of the port 1234 did not work, but have not yet investigated why. The ´dev web server is probably only available locally and the configuration must be adapted.
the development of the adapter in a docker container under wsl did not work, as you may have remembered, due to adverse circumstances and we did not find a solution together either.


about get the imu and stereo image separately at the same time

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ R200 / F200 / SR300 / ZR300 / D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>
Hi，i can not get the imu and stereo image at the same time, some imu are dropped. Can you update a sample or give me some clue?

If you activate the Stereo and Motion modules at the same time, are you getting frame drops on the IMU streaming, please?
What computer device are you using the camera with please?   (PC / Mac / Raspberry Pi / Jetson / Android etc)
And which operating system?  (Windows / MacOS / Linux etc)

If you activate the Stereo and Motion modules at the same time, are you getting frame drops on the IMU streaming, please?
Are you using a T265 or a D435i camera?
What computer device are you using the camera with please? (PC / Mac / Raspberry Pi / Jetson / Android etc)
And which operating system? (Windows / MacOS / Linux etc)

D435i, PC, Ubuntu. Now,  i have not the dropping imu or image. Now i wanna get the same frequency of gyro and acc.

Thank you very much.  You would like to align the IMU data to depth data, please?

Thank you very much. You would like to align the IMU data to depth data, please?
I wanna get the Infrared image and the IMU data.

Ok, thanks.  You are trying to do this with programming, like C++, and not with the RealSense viewer program?

Ok, thanks. You are trying to do this with programming, like C++, and not with the RealSense viewer program?
en

I do apologise.   What is 'en' please?

Sorry. I mean “Yes”.
发自我的iPhone
------------------ Original ------------------
From: MartyG-RealSense<EMAIL_ADDRESS>Date: Sat,Apr 18,2020 8:01 PM
To: IntelRealSense/librealsense<EMAIL_ADDRESS>Cc: jyzhong<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [IntelRealSense/librealsense] about get the imu and stereo image separately at the same time (#6264)
I do apologise.   What is 'en' please?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ok, thank you very much.  So you would like a C++ sample program that shows the infrared image and the IMU data of the D435i.  I will search for information for you.  Thank you for your patience.

@MartyG-RealSense
Sorry. I mean "Yes". I wanna the same frequency of gyro and acc as the version of ROS do. If i should set some paras so the imu and infrared image is synchronous ?

Thank you.   I hope the very detailed discussion in the link below about aligning IMU measurements to IR frames will be helpful.
https://github.com/IntelRealSense/librealsense/issues/3942

Thank you. I hope the very detailed discussion in the link below about aligning IMU measurements to IR frames will be helpful.
#3942

Hi, after i run sample "motion". I found that the of frequency of gyro and acceleration is unstable. For example, i set 400hz for gyro, i get many drop frame and the interval of data isn't 2.5ms, maybe 3ms or 2ms. So do the acceleration. I wish get your help. Is this the right data ?  Is my sdk wrong?

I thought about your case very carefully.  As you are trying to use IMU and infrared data together, the discussion in the link below may help you to program ways to generate a better output.
https://github.com/IntelRealSense/librealsense/issues/4386
If you are testing the IMU on its own in the "Motion Module" controls of the RealSense Viewer at 400hz and getting a time period of worse than 2.5 ms and dropped frames ... Doronhi the RealSense ROS developer has suggested checking whether your PC is overloaded at the time (for example, whether your CPU usage is close to or at 100%).

@MartyG-RealSense  Thanks. The  CPU usage is bigger than 100%. Actually i just run the sample. How can i get the right imu data without dropped frame? BTW, when i install the SDK,  "./scripts/patch-realsense-ubuntu-lts.sh " is failed because of "fatal: index-pack failed", but i still finished installation.

To avoid the need for patching, you could try the 'bypass' method of installation that is confirmed to work with D435i.  This method is also not reliant on Linux versions or kernel versions, so it is a good choice to try if you have problems with the usual Linux installation process.  The bypass installation needs an internet connection to work.
https://support.intelrealsense.com/hc/en-us/community/posts/360037657234/comments/360009799533

@MartyG-RealSense thanks! i install the source code using the "bypass". Open the "realsense-viewer", i found i can get the "hardware time". i click on the button "global time", but it's still have "hardware time". When i use the "dkms"

I do not have an Ubuntu setup to test with as I am a Windows user.  I ran some tests with 'Global Time' togled on and off in the RealSense Viewer on my Windows setup, at the bottom of the "Controls" section of the stereo module's side-panel options.
When 'Global Time Enabled' was enabled, this was reflected in the stream information by showing it to be using 'Global Time'.

When the 'Global Time Enabled' option was disabled, the Viewer automatically changed 'Global Time' to 'Hardware Clock'.  Toggling 'Global Time Enabled' back on during streaming automatically switched the information back from 'Hardware Clock' to 'Global Time'.

Are you unable to get Global Time on your own Viewer on Ubuntu, please?

@MartyG-RealSense yes.  when i try "cmake ../ -DBUILD_EXAMPLES=true".  The acceleration get the two types. But the gyroscope　only have the "system" and mention "Per-frame metadata is not enable at the OS level, please follow the installation guide for details". BTW, i install the SDK according to the "DKMS", the realsense-viewer  work well. Actually, Maybe the issue trouble me is the that when i use the "callback" rather than "wait_for_stream", i can get the IR frame and imu data, but just like i say, the gyroscope have lots of dropped frame. Maybe the next version will give a sample about "align the IR and imu", or "color and imu". Thanks your for your nice reply.

My understanding is that the "backend" bypass method installs support for metadata on Linux, but when using the normal installation method metadata support for Linux has to be patched in (metadata is supported by default on Windows).
https://github.com/IntelRealSense/librealsense/issues/3686#issuecomment-515775903
If you would like to make a request for the sample programs that you described, I recommend creating a new issue just for that request, with the words 'Feature Request' in the title.  I can then label the issue as a feature request so that the RealSense developer team can track it.   Thanks!

Thanks.
发自我的iPhone
------------------ Original ------------------
From: MartyG-RealSense<EMAIL_ADDRESS>Date: Tue,Apr 21,2020 7:45 PM
To: IntelRealSense/librealsense<EMAIL_ADDRESS>Cc: jyzhong<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [IntelRealSense/librealsense] about get the imu and stereo image separately at the same time (#6264)
My understanding is that the "backend" bypass method installs support for metadata on Linux, but when using the normal installation method metadata support for Linux has to be patched in (metadata is supported by default on Windows).
#3686 (comment)
If you would like to make a request for the sample programs that you described, I recommend creating a new issue just for that request, with the words 'Feature Request' in the title.  I can then label the issue as a feature request so that the RealSense developer team can track it.   Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Air mini +

Hi,
I installed this plugin, and while it is able to show "Valid Login Credentials", no devices are shown in the home app. I am using an Air mini+. Any way I can fix this?

[17/11/2023, 08:19:12] [homebridge-molekule] HTTP GET STATUS: 200

[17/11/2023, 08:19:12] [homebridge-molekule] HTTP GET STATUS: 200

Can you post the log of homebridge in debug mode so I can see what is the server response?

Hello i attached the .txt file. Odesláno z iPhonu21. 11. 2023 v 0:37, Chiripol S. @.***>:
[17/11/2023, 08:19:12] [homebridge-molekule] HTTP GET STATUS: 200
Can you post the log of homebridge in debug mode so I can see what is the server response?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Hello i attached the .txt file. Odesláno z iPhonu21. 11. 2023 v 0:37, Chiripol S. @.***>:
[17/11/2023, 08:19:12] [homebridge-molekule] HTTP GET STATUS: 200
Can you post the log of homebridge in debug mode so I can see what is the server response?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I can't see your text file unfortunately. Maybe you can do it from the GitHub website.

Look at the e-mail I sent it attached.Odesláno z iPhonu21. 11. 2023 v 11:45, Chiripol S. @.***>:
Hello i attached the .txt file. Odesláno z iPhonu21. 11. 2023 v 0:37, Chiripol S. @.>:
[17/11/2023, 08:19:12] [homebridge-molekule] HTTP GET STATUS: 200
Can you post the log of homebridge in debug mode so I can see what is the server response?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.>
I can't see your text file unfortunately. Maybe you can do it from the GitHub website.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

homebridge.txt

I know of two other air cleaners that are waiting for this error to be fixed.
However, I am afraid that it will be a problem with the API from the molekule, that perhaps it is only blocking traffic from Central Europe.

homebridge.txt

It seems like you don't even have any devices registered so nothing is being passed via the API. Would you confirm if devices are added in the app on your phone?

Yes of course the deviace has been successfully added in the Molekule application and can be controlled in the application without any problems.Odesláno z iPhonu25. 11. 2023 v 5:02, Chiripol S. @.***>:
homebridge.txt
It seems like you don't even have any devices registered so nothing is being passed via the API. Would you confirm if devices are added in the app on your phone?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

@csirikak is there technical documentation somewhere for the molecule purifier API? I would like to help.

@csirikak is there technical documentation somewhere for the molecule purifier API? I would like to help.

There's 0 documentation available. What you can do is to use the an app like Proxyman to snoop on requests from the Molekule app.
You can also clone the repository and make changes.
Finally, if you're willing, you also can dm me your Molekule credentials and I can try to figure out why you're having issues.


fix(client-presence): Remove connectionId for self attendee disconnect

Description
We currently use Audience to listen for when remote clients disconnect from the session before removing their connection Id and setting their status to disconnected.
This works perfectly fine for remote clients, but for the local client this is not possible since "removeMember" event is not sent to the local client that disconnected.
To fix this we can listen to "disconnected" event on the ephemeral runtime (same way we listen to "connected") to know when the local client disconnects.

I think the best way to test this would be through unit testing and manual testing of external controller. I will redirect conversation to this PR https://github.com/microsoft/FluidFramework/pull/23006 since this change is apart of it and this is where all the test reworking is.


Add editorconfig

I noticed different coding styles across files, so... Here is editorconfig to make it more easy to force your CS rules on contributors.

thanks!


Any way to cache results from fzf listing?

Category

[x] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[ ] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Windows Subsystem for Linux
[ ] Etc.

Shell

[x] bash
[ ] zsh
[ ] fish

I thought it would be useful for another issue i'm having here to cache the result from fzf's listing, to a file for example, so i could just pipe that to it in a script, and dedupes with new entry.
I'm just unsure on how to pipe the said listing to a file in bash.

Hi @nordmagnus999, you've probably fixed it by now, but you can pipe the command with a big output into awk/sed/a script to trim the list down before passing it to fzf instead of using a cache files.
If you managed to solve it some other way, do let us know.


Make sure all the handlers are idempotent

[ ] Make sure every handler can be re-triggered in any state of the execution.

[ ] Fix the easy problems.
[ ] Create issues for the more complicated problems.

Some notes regarding what actions are done in the handlers code and potential improvements:
Firstly we have the handlers that report the state of the task to the user and only update the state of existing models in DB (+ in some, we are doing GET requests to get e.g. end time of the Copr build). As for the reporting, as discussed, creating the commit statuses/checks is almost idempotent (there is only different timestamp on the check) and as for commenting, we have methods that check existing duplicate comments.

KojiTaskReportHandler
KojiBuildReportHandler
TestingFarmResultsHandler
VMImageBuildResultHandler
CoprBuildStartHandler
CoprBuildEndHandler - here is an extra step: creating TF handler task(s)

these 2 are just a little bit different, they are creating or updating the DB entries
7. GithubAppInstallationHandler
8. GithubFasVerificationHandler

in these, the code could be updated so that in the beginning, we always check whether the state in DB is different than the one about to report and update the state in DB at the end of the handler code; the CoprBuildEndHandler could be problematic because of the creation of TF handler task(s).

Then, there are tasks where we are making POST requests to external services, creating new models in the DB, ... I think with these, we cannot make many improvements:

DownstreamKojiBuildHandler - submitting build in Koji
CoprBuildHandler - submitting build in Copr
TestingFarmHandler - submitting TF run
BodhiUpdateHandler - submitting updates in Bodhi
KojiBuildHandler - submitting build in Koji
VMImageBuildHandler - submitting the image build

AbstractSyncReleaseHandler - this one is a little bit different; we are uploading new sources (if not present) and then doing changes on Git repo (using a deterministic branch) and, in the end, force pushing.

The question to me seems what do we do when a network error happens while submitting a build: do we submit another one? do we check if there is a pending one a reuse it?

As we were discussing during the last week's architecture that, we could decide for some handlers to not ensure the idempotency (and when implementing the mentioned Celery acks_late do not mark these).
In my opinion, for the second group (the 7. may be an exception), changing all the submitting code to check already existing submissions and make these also consistent with the database would require much more complex solution to do it correctly and personally, I would currently not go that way.
After implementing #1328, this could be maybe easier.
WDYT?

As we were discussing during the last week's architecture that, we could decide for some handlers to not ensure the idempotency (and when implementing the mentioned Celery acks_late do not mark these).

Ah, right! Forgot about it. We can totally do that incrementally.

In my opinion, for the second group (the 7. may be an exception), changing all the submitting code to check already existing submissions and make these also consistent with the database would require much more complex solution to do it correctly and personally, I would currently not go that way. After implementing #1328, this could be maybe easier.
WDYT?

Yes agreed. Retrying manually or using the mechanism we already have in place sounds the current path forward.

@lbarcziova Thanks for finishing this! Since the PR is merged, can we mark some handlers with acks_late?


Use a cache for timezone loading rather than relying on weakrefs.

Codecov Report
Attention: Patch coverage is 80.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 97.20%. Comparing base (0f81270) to head (5f039a7).

Files
Patch %
Lines

gcal_sync/model.py
80.00%
2 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #548   +/-   ##
=======================================
  Coverage   97.19%   97.20%
=======================================
  Files           9        9
  Lines         962      965    +3
=======================================
+ Hits          935      938    +3
  Misses         27       27

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix background for SpotifyControls player

For the SpotifyControls plugin.
Before:

After:

Not 100% on how things are compiled for your pages. Feel free to make any changes to make this work.

Depending on how the plugin injects, this could just be patched on the theme overall (especially if Discord ever plans to add extra stuff to the user area). Ideally, the plugin should inject directly into .panels__58331, then it's possible to update this file to have to this:
div {
     background-color: var(--background-primary);
}

As far as I know, that shouldn't conflict with anything.

Ideally, the plugin should inject directly into .panels__58331,

It is! :D

then it's possible to update this file to have this:
:is(.theme-dark, .theme-midnight) .sidebar_ded4b5 {
    .panels__58331 {
        background-color: var(--background-primary);
        > div {
            background-color: var(--background-primary);
        }
    }
}

We should do this

EDIT: Turns out it was more than this because of how they theme the panel, had to use !important.

Actually, seems like this worked for me without !important

Actually, seems like this worked for me without !important

Just to be safe, I'll leave !important in due to the issue I was having with it applying.


Reconfigure VSCode to use UNIX Linebreaks

Since when this is deployed we are going to be targeting a Linux installation the use of Windows linebreaks could cause problems, especially when we are sending messages etc.
This we can configure in our VSCode application based on this blog https://qvault.io/clean-code/how-to-get-consistent-line-breaks-in-vs-code-lf-vs-crlf/
Basically we have to enter the .vscode/settings.json file and make changes to use only Linux linebreaks instead of Windows.

[ ] William Completed
[ ] Jason Completed

You can also configure git to convert crlf to lf when checking out
https://www.cylindric.net/git/force-lf
i had to do the reset commands too because of cache


提供的预训练模型stage1和stage2的checkpoint文件是一样的，能修改重新发布下载链接吗

Hello, is there any news about this issue?

I have found the same issue when I am runing their code to make some test.


The render sequence is wrong when passing CSS classes to child

Let's assume we have ComponentA and ComponentB in different files.
// file1.tsx
const useStyles = makeStyles()(({ palette, breakpoints }) => ({
  extra: {
    color: "red"
  }
}));

const ComponentA = () => {
  const { classes, cx } = useStyles();
  return <ComponentB extraClasses={classes.extra} />;
}

// file2.tsx
const useStyles = makeStyles()(({ palette, breakpoints }) => ({
  root: {
    color: "blue",
    [breakpoints.up("sm")]: {
      color: "yellow"
    }
  }
}));

export const ComponentB = ({ extraClasses }: { extraClasses?: string }) => {
  const { classes, cx } = useStyles();
  return
Hi
;
};

Ideally when using JSS, the extraClass in ComponentA will override the root class in ComponentB which can produce the right result on screen, which is that the text should be in "red" color.
Problems:

If using clsx to merge classes, then two classes will be generated but in wrong sequence. The root class in ComponentB will always override extraClass in componentA and display "blue" color which is wrong.

If using cx to merge classes, then one merged class will be generated in right sequence, but if there's any breakpoint related css in ComponentB, then it will not work well because the css priority is always breakpoint first, so it will display "yellow" color which is also wrong.

Thanks for building this amazing package and this is the only issue we have so far.
Hope you can provide a fix or let us know if there's any workaround. Our project is huge so finding them and changing them one by one is kind of impossible..
Cheers
CJ

Would it be an easy thing to fix or it might affect too many code?

I think I can pull it off but it's a big feature that will require at least a day of work. I prefer to think of it as a feature since it is currently working as expected... but we'd like TSS to perform some extra magic. I wrote a test case that fails for this issue but I will leave it at that for now I have to get back to work. I'll try to get this done this week end.
In the meantime, I know it's less than ideal but you could use && to increase specificity

Tons of thanks mate, we will use the windowInnerWidth workaround for now and wait for the proper fix. && is not quite ideal as it needs to be added in too many places and also it could not work with the classes been passed to more than two hierarchies.

You are welcome 👍🏻
about useWindowInnerSize() don't use the implementation of powerhooks, it's not SSR compatible.
Use an implementation more like this one:
function useWindowSize() {

  const [windowSize, setWindowSize] = useState({
    //It's up to you to figure out what is the best default values here
    width: 0,
    height: 0,
  });

  useEffect(() => {
    // only execute all the code below in client side
    if (typeof window !== 'undefined') {
      // Handler to call on window resize
      function handleResize() {
        // Set window width/height to state
        setWindowSize({
          width: window.innerWidth,
          height: window.innerHeight,
        });
      }

      // Add event listener
      window.addEventListener("resize", handleResize);

      // Call handler right away so state gets updated with initial window size
      handleResize();

      // Remove event listener on cleanup
      return () => window.removeEventListener("resize", handleResize);
    }
  }, []); // Empty array ensures that effect is only run on mount
  return windowSize;
}

Well understood,
If SSR is involve my proposed workaround isn't really one.
I'm going to spend a couple of hours on it now.

for the proper fix

Sorry to insist on the status of this issue but this is a feature request. A good feature request but a feature request still. TSS currently works as advertised.

Tons of thanks for all your supports so far :)

You are welcome 😊

I got a POC working but it still needs work for being production ready.

Tons of thanks bro :)

Thank you for you appreciation 😊