Polybool clipping

Looks good, although I would add a message if no solution was found:
[...]
            else:
                channel(_("No solution found (empty path)"))
                return "elements", []

Yeah, I don't know if this should just be switched out. I might need to run some speed checks on the data to see if there's some performance costs or benefits. Also, I added -c to main and to this branch and sort of wonder if that should be made the default instead. Replacing the original pieces.


Weird issue with parsing when there is 'u' in a specific location/word combintion.

@when_all(m.logLine.matches('.*(usage manager memory limit).*'))
    def liveDataSlowConsumer(c):
        msg = 'usage memory limit'
        task = Task(msg)
        publish(task)

{"id": millis(), "logLine": '8490899: nov 03 09:19:06.003 cst %mivr-ss_rmcm-7-unk:usage manager memory limit (134217728) reached.Stopping prodA'}
In the above json data if we replace 'A' in the word 'prodA' with 'u' the rule does not work otherwise the rule works beautifully.
{"id": millis(), "logLine": '8490899: nov 03 09:19:06.003 cst %mivr-ss_rmcm-7-unk:usage manager memory limit (134217728) reached.stopping aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'}
In the above json data if we add 'u' the rule does not work otherwise the rule works beautifully whatever you add.

Hi, thank you for reporting this problem. I confirmed there is a bug in when generating the DFA for expressions starting and finishing with .* . I will be fixing it in the next few days.

Hi, I have published a fix for this problem. Please use version 0.33.102.

@jruizgit Thanks a lot for the update. I will check and get back to it


Redirect all traffic to http://www.domain.com and not to http://domain.com

Hi,
I want to set all my traffic to www. So, I have the domain name http://www.rallypodium.tk/ but, when someone enters my site like http://rallypodium.tk they can't do much, and I want to have all the traffic over the www. So I don't want a 'naked' domain. How can I do this?

Since this is not related to the framework, why don't you use Google to figure it out?


Copy document quality module from inner to outer repo

Search before asking

[X] I searched the issues and found no similar issues.

Component
Transforms/Other
Feature
Document quality is ready to move from inner to outer repo in V1, after we are done with V0 priorities.
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Planned for release 1


Challenge 1 Checkpoint 1: Staking - "Stake Events" table data not loading

the data in Stake Events tab isn't loading correctly after making some  staking transactions and I'm not finding any helpful errors in dev console
Any ideas on this?
https://decentralized-staking-coral.vercel.app/stakings

Is it working for you locally?
I see only one Stake event on your account, is it worked before and stopped?

i took a look at your PR and tried it with both the named and unnamed Stake event parameters in my contract and even tried updating the stakings.tsx template with the array indexes and it still wasnt working... both on my local repo and i tried spinning up a fresh repo to test it and still didn't work for me.

It works for me without named params in solidity contract event and at the same time with array indexes on your tsx file. Have you tried exactly this case?
try to console.log(stakeEvents) in your stakings.tsx. What does it show to you? What's inside args prop of events?

It worked!
https://decentralized-staking-h42nz6owu-tantodefi.vercel.app/stakings
my bad I missed updating one of the array index values
Thanks so much @rin-st


Added 1 user with 2 nodes

Added:

@colossus.digital:matrix.org with 2 nodes

@ironoa Element handle of the user was verified


Error running flutter doctor: "ProcessException: invalid directory name"

Steps to Reproduce
In windows 10

flutter doctor

This is the stdout:
C:\Users\gfran>flutter doctor
Impossibile trovare il file specificato.
Running "flutter pub get" in flutter_tools...

Oops; flutter has exited unexpectedly: "ProcessException: Nome di directory non valido.

  Command: C:\Users\gfran\flutter\bin\cache\dart-sdk\bin\pub.BAT --verbosity=warning get --no-precompile".
A crash report has been written to C:\Users\gfran\flutter_12.log.
This crash may already be reported. Check GitHub for similar crashes.
https://github.com/flutter/flutter/issues?q=is%3Aissue+ProcessException%3A+Nome+di+directory+non+valido.%0D%0A%0A++Command%3A+C%3A%5CUsers%5Cgfran%5Cflutter%5Cbin%5Ccache%5Cdart-sdk%5Cbin%5Cpub.BAT+--verbosity%3Dwarning+get+--no-precompile

To report your crash to the Flutter team, first read the guide to filing a bug.
https://flutter.dev/docs/resources/bug-reports

Create a new GitHub issue by pasting this link into your browser and completing the issue template. Thank you!
https://git.io/J1RcE

Logs
this is the log:
Flutter crash report.
Please report a bug at https://github.com/flutter/flutter/issues.
command
flutter doctor
exception
ProcessException: ProcessException: Nome di directory non valido.
Command: C:\Users\gfran\flutter\bin\cache\dart-sdk\bin\pub.BAT --verbosity=warning get --no-precompile
#0      _ProcessImpl._start (dart:io-patch/process_patch.dart:390:33)
#1      Process.start (dart:io-patch/process_patch.dart:36:20)
#2      LocalProcessManager.start (package:process/src/interface/local_process_manager.dart:44:22)
#3      ErrorHandlingProcessManager.start.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:691:24)
#4      _run (package:flutter_tools/src/base/error_handling_io.dart:567:20)
#5      ErrorHandlingProcessManager.start (package:flutter_tools/src/base/error_handling_io.dart:690:12)
#6      _DefaultProcessUtils.start (package:flutter_tools/src/base/process.dart:425:28)
#7      _DefaultProcessUtils.stream (package:flutter_tools/src/base/process.dart:444:35)
#8      _DefaultPub.batch (package:flutter_tools/src/dart/pub.dart:308:34)
<asynchronous suspension>
#9      _DefaultPub.get (package:flutter_tools/src/dart/pub.dart:248:7)
<asynchronous suspension>
#10     PubDependencies.update (package:flutter_tools/src/flutter_cache.dart:119:5)
<asynchronous suspension>
#11     Cache.updateAll (package:flutter_tools/src/cache.dart:557:9)
<asynchronous suspension>
#12     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1227:7)
<asynchronous suspension>
#13     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1125:27)
<asynchronous suspension>
#14     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#15     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#16     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:288:9)
<asynchronous suspension>
#17     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#18     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:236:5)
<asynchronous suspension>
#19     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
<asynchronous suspension>
#20     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#21     main (package:flutter_tools/executable.dart:92:3)
<asynchronous suspension>

flutter doctor
[✓] Flutter (Channel stable, 2.5.3, on Microsoft Windows [Versione 10.0.19043.1348], locale it-IT)
    • Flutter version 2.5.3 at C:\Users\gfran\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (5 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\gfran\AppData\Local\Android\sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Android Studio (version 2020.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] Connected device (2 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 95.0.4638.69
    • Edge (web)   • edge   • web-javascript • Microsoft Edge 95.0.1020.53

! Doctor found issues in 1 category.

I got the problem.
It seems that in windows 10 there is a new functionality that locks all files downloaded from another computer (in my case the internet). I installed flutter downloading the zip file. Now, the zip file was locked and, extracting the content all executable files (and also those without an extension... AFAIK) were locked too. It is easy to unlock them, going in the property tab, at the bottom there is a check-box that allows you to unlock the file. The problem is that there are a lot of file to unlock, and I couldn't find any way to do this for a folder, only one by one.
Finally, I discovered googling that if you unlock the zip file before extracting the content, all executable are created correctly..
So I deleted the old flutter folder, unlocked the zip file and extracted everything a second time.
Now  flutter doctor works fine.
It is probably better to update the documentation on flutter.dev


Rename to "FSharp.Azure.CloudAgent"?

@isaacabraham  - the usual expected issue from me :)
Could we consider renaming this to FSharp.Azure.CloudAgent?  It seems the logical and consistent name for the framework?

Yes, we could - unless we were to consider Azure as a provider that the Agent framework sat on top of? e.g. Amazon or other service bus style implementations? It's unlikely I suppose.


Android camera orientation always 90 degrees clockwise

iOS is working fine, but on Android the camera preview window is always showing off by 90 degrees clockwise; eg, what the camera is picking up is wrong.
This persists even as I change between portrait and landscape.
How can I have the camera recording in the correct orientation?
There's no interesting code on my end governing this:
cordova.plugins.camerapreview.startCamera(rect, "front", tapEnabled, dragEnabled, toBack);
I haven't made any progress on this, Stripped down the camera to it's most basic and issue is still presenting; being rotated by 90 degrees all the time. The picture that's captured is correct, but the preview window is showing off. Does anyone have any ideas?

Any assistance or suggestions would be greatly appreciated. I got an older apk and the issue is not present there. I poured through the code, even copying all of the startCamera code, but no matter what I do with the new build it's rotated.
        var onDeviceReady = function () {

            var tapEnabled = false; //enable tap take picture
            var dragEnabled = false; //enable preview box drag across the screen
            var toBack = false; //send preview box to the back of the webview

            var rect = {x: 428, y: 190, width: 200, height: 150};

            cordova.plugins.camerapreview.startCamera(rect, "front", tapEnabled, dragEnabled, toBack);
        };
        document.addEventListener('deviceready', onDeviceReady, false);

This displays the preview window but 90 degrees rotated off. An older apk I have from a month or so ago shows the proper orientation, even though it appears to be using the same camera code. Any guesses on something else it could be?


Preact Component's constructor is not called when custom element is created via document.createElement

This is documented here in this comment from another PR: https://github.com/preactjs/preact-custom-element/pull/64#discussion_r770010488. document.createElement should run the component's constructor method.
class CounterPreact extends Component {
  constructor() {
    super()
    console.log('here')
  }
}

register(CounterPreact, 'x-counter-preact')

// ...

document.createElement('x-counter-preact') // no output

class CounterPlain extends HTMLElement {
  constructor() {
    super()
    console.log('here')
  }
}

customElements.define('x-counter-plain', CounterPlain)

// ...

document.createElement('x-counter-plain') // outputs here

The constructor only seems to fire when the custom element as appended to the DOM.

I was curious about this behavior and looked into it a little bit. The reason is that making an instance of the web component does not make an instance of the preact component. That only happens when the preact component is rendered the first time, and the earliest that can happen is in the connectedCallback which runs when the element is appended. Its technically possible to render the preact component in the constructor but it would only work if also using the shadow dom as attaching the shadow creates a document fragment. Without a shadow root, the constructor doesn't have access to any dom yet and its unsafe to call render.
Heres a codesandbox to demonstrate: https://codesandbox.io/s/tender-shamir-dwk4zb?file=/src/index.js
It creates a preact component that logs in the constructor, and manually wraps it in 2 web components, one with a shadow root and one without. Both web components will console.log when calling document.createElement, but the one without the shadow root will cause an error.
So I think current behavior makes sense, but curious about any scenarios where you'd want both constructors to run at the same time.


Connection becomes timed out in the loop to wait for the mission to start after startMission

I ran my agent on malmo and after 1417 peaceful episodes, it stacked by error below.
DEBUG: Sending MissionInit to <IP_ADDRESS> : 10123
DEBUG: Looking for client, received reply from <IP_ADDRESS>: MALMOOK
INFO:MalmoGym:Waiting for the mission to start
...................terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  connect: Connection timed out

How to avoid this error? Can I catch this and ignore? Did I write wrong codes?
 Looks like there was a connection issue at 20:19:22 - the Mod tries to send a video frame and fails. "Connection reset by peer" indicates that the agent host has stopped listening - probably because it has crashed?
So a possible sequence of events here was:

Mission starts successfully.
Agent somehow fails to send something and bombs out with the boost asio timeout exception.
Mod tries to keep sending data back to the agent, but fails because the connection has been lost.
Mission bails.

The question is... what caused the agent to bomb out?
I'll do some digging and see if we can reproduce this.
One (probably unrelated) thing to be wary of - I'd change this line:
while not world_state.is_mission_running:

to this:
while not world_state.has_mission_begun:

Otherwise it's possible for very short missions to both start and stop during the 0.02 seconds you are sleeping between checks.

On closer inspection, are you certain these two logs correspond to the same time frame?
The Minecraft log shows a mission that started successfully and ran for over two minutes before the socket error happened.
The python log seems to indicate that the mission was accepted, but never started.
I can't see how the two can be reconciled...
(To help with these sort of issues, I usually add a mission summary in the XML which numbers each mission, and make sure the python log spits out the number too. See, for example, patchwork_quilt.py)

OK. I add a mission summary and when i get the same error, I post again.

I'm having the exact same issue. Here is the log, with AgentHost and Malmo mod outputs mixed (I'm running Malmo as subprocess of agent process):
DEBUG: Looking for client, received reply from <IP_ADDRESS>: MALMOOK
[2016-10-15 22:49:41,011] Waiting for the mission to start
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.Client.ClientStateMachine$DormantEpisode:checkForMissionCommand:646]: Mission received: Cliff walking mission based on Sutton and Barto.
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: CLIENT request state: CREATING_HANDLERS
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: CLIENT enter state: CREATING_HANDLERS
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: CLIENT request state: EVALUATING_WORLD_REQUIREMENTS
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: CLIENT enter state: EVALUATING_WORLD_REQUIREMENTS
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: CLIENT request state: WAITING_FOR_SERVER_READY
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.Server.ServerStateMachine$DormantEpisode:checkForMissionCommand:465]: INCOMING MISSION: Received MissionInit directly through queue.
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.Server.ServerStateMachine$DormantEpisode:onReceiveMissionInit:472]: Mission received: Cliff walking mission based on Sutton and Barto.
[22:49:41] [Server thread/INFO]: Received mission: §9Cliff walking mission based on Sutton and Barto.
[22:49:41] [Server thread/INFO]: Source: §a<IP_ADDRESS>
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: SERVER request state: BUILDING_WORLD
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: SERVER enter state: BUILDING_WORLD
[22:49:41] [Client thread/INFO]: [CHAT] Received mission: §9Cliff walking mission based on Sutton and Barto.
[22:49:41] [Client thread/INFO]: [CHAT] Source: §a<IP_ADDRESS>
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: SERVER request state: WAITING_FOR_AGENTS_TO_ASSEMBLE
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: CLIENT enter state: WAITING_FOR_SERVER_READY
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.Client.ClientStateMachine$WaitingForServerEpisode:onClientTick:770]: ***Telling server we are ready - Cristina
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: SERVER enter state: WAITING_FOR_AGENTS_TO_ASSEMBLE
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.Server.ServerStateMachine$WaitingForAgentsEpisode:execute:769]: Experiment requires:
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.Server.ServerStateMachine$WaitingForAgentsEpisode:execute:772]: >>>> Cristina
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.Client.ClientStateMachine$WaitingForServerEpisode:onClientTick:770]: ***Telling server we are ready - Cristina
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: CLIENT request state: RUNNING
[22:49:41] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: CLIENT enter state: RUNNING
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: SERVER request state: RUNNING
[22:49:41] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: SERVER enter state: RUNNING
[22:49:41] [Client thread/INFO]: [CHAT] §l20...
[22:49:42] [Client thread/INFO]: [CHAT] §l19...
[22:49:43] [Client thread/INFO]: [CHAT] §l18...
[22:49:44] [Client thread/INFO]: [CHAT] §l17...
[22:49:45] [Client thread/INFO]: [CHAT] §l16...
[22:49:46] [Client thread/INFO]: [CHAT] §l15...
[22:49:47] [Client thread/INFO]: [CHAT] §l14...
[22:49:48] [Client thread/INFO]: [CHAT] §l13...
[22:49:49] [Client thread/INFO]: [CHAT] §l12...
[22:50:01] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: SERVER request state: WAITING_FOR_AGENTS_TO_QUIT
[22:50:01] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: SERVER enter state: WAITING_FOR_AGENTS_TO_QUIT
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  connect: Connection timed out
[22:51:49] [Client thread/INFO]: [CHAT] §l11...
[22:51:49] [Client thread/INFO]: [CHAT] §l10...
[22:51:49] [Client thread/INFO]: [CHAT] §l9...
[22:51:49] [Client thread/INFO]: [CHAT] §l8...
[22:51:49] [Client thread/INFO]: [CHAT] §l7...
[22:51:49] [Client thread/INFO]: [CHAT] §l6...
[22:51:49] [Client thread/INFO]: [CHAT] §c§l5...
[22:51:49] [Client thread/INFO]: [CHAT] §c§l4...
[22:51:49] [Client thread/INFO]: [CHAT] §c§l3...
[22:51:49] [Client thread/INFO]: [CHAT] §c§l2...
[22:51:49] [Client thread/INFO]: [CHAT] §c§l1...
[22:51:49] [Client thread/INFO]: [CHAT] §c§l0...
[22:51:49] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: CLIENT request state: MISSION_ENDED
[22:51:49] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: CLIENT enter state: MISSION_ENDED
[22:51:49] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.Client.ClientStateMachine$MissionEndedEpisode:sendMissionEnded:1684]: Sending mission ended message to <IP_ADDRESS>:10399.
[22:51:49] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.Utils.TCPSocketHelper:createSocket:112]: WARNING: Failed to create socket: java.net.ConnectException: Connection refused
[22:51:49] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: CLIENT request state: WAITING_FOR_SERVER_MISSION_END
[22:51:49] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: CLIENT enter state: WAITING_FOR_SERVER_MISSION_END
[22:51:49] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: SERVER request state: CLEAN_UP
[22:51:49] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: SERVER enter state: CLEAN_UP
[22:51:49] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: SERVER request state: DORMANT
[22:51:49] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:queueStateChange:143]: CLIENT request state: DORMANT
[22:51:49] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: CLIENT enter state: DORMANT
[22:51:49] [Client thread/INFO] [STDOUT]: [com.microsoft.Malmo.Utils.TCPInputPoller:clearCommands:127]: JETTISONING 0 COMMANDS
[22:51:49] [Server thread/INFO] [STDOUT]: [com.microsoft.Malmo.StateMachine:setState:101]: SERVER enter state: DORMANT

The symptoms are exactly the same - first timeout in agent which causes Boost to terminate client immediately, followed by connection refused from Malmo mod. It happens completely randomly, but more often when CPU resources are tight.
I'm willing to help debugging it, if you can give me some pointers where to start.

Hi @tambetm
I cannot explain the mechanism but I suppressed this error by putting time.sleep(0.5) (more detail, see #307).
Actually, I had tried to make OpenAI-gym like wrapper for malmo too but abandoned finally. The reasons are below. (Please do not get angry. This is just one user's honest opinion...)

malmo is too slow to train my agent (0.5 seconds for every episode!?)
malmo runs more slowly after some hours (GC problem?)
malmo seems not stable yet.

Other Minecraft-based environment that I found: https://github.com/junhyukoh/icml2016-minecraft/tree/master/environment
My Rogue-like alternative: https://github.com/okdshin/Yender
Yes. malmo supports multiple agents and non-discrete actions so I expect much of malmo.
However, when only single agent and discrete actions are needed, I cannot say malmo is good choice currently.

Thanks for your reply @okdshin! Actually my experiences are not that bad:

I was able to resolve my issue by just moving to different servers. Previously I was running Docker images on AWS, which probably introduced some weird lagging issues. Now I'm running it on physical servers and so far no problems with crashing any more.
I was able to successfully overclock Minecraft/Malmo up to 1000 steps/sec. On beefy servers I could set MsPerTick to 1ms, on my i7 laptop the max was 2ms. Actually the bottleneck was my training code, which couldn't handle more than 100 steps/sec, therefore I trained with MsPerTick=10ms. Some tuning tips here.
I haven't noticed particular slowdowns after long training sessions (1-2 days). I haven't paid close attention tough.

Malmo might be a bit rough on edges, but so far it seems like a good starting point. I've been able to successfully solve basic.xml and cliff_walking_1.xml using policy gradients in continuous action space (only move and turn commands). In cliff walking I had to turn off negative rewards for commands though, otherwise it was easier for the agent to jump into lava right away, without accruing additional penalty for moving around. I guess something like "optimism in the face uncertainty" would help to learn it in original formulation, but I couldn't figure out how to incorporate that into PG.
Your Rogue-like environment is interesting, made a note for myself.

@tambetm Thank you for your advice. I tried a simple DQN agent for cliff_walking but in some maps, my agent leaned merely walking around the start point. I think I should regulate the delta of epsilon more.
Your gym-minecraft seems to be very good. I really wanted it. I'll try later.


time.parse cann ot parse RFC3339 reference string (or any other I tried)

Go version
go version 1.22.0 linux/amd64
Output of go env in your module/workspace:
MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/user/.cache/go-build'
GOENV='/home/user/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/user/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/user/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
<EMAIL_ADDRESS>GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
<EMAIL_ADDRESS>GOVCS=''
GOVERSION='go1.22.0'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/user/Dokumente/devel/evcc/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'

What did you do?
t, err := time.Parse(time.RFC3339, time.RFC3339)
if err != nil {
   fmt.Print(err)
} else {
  fmt.Printf("Formatted %s", t.Format(time.RFC3339))
}

What did you see happen?
parsing time "2006-01-02T15:04:05Z07:00": extra text: "07:00"
What did you expect to see?
No error, correctly parsed value in t
Expected output:
Formatted: 2006-01-02T15:04:05Z07:00

Maybe related to #205555

Related Issues and Documentation

time.RFC3339 does not even parse with time.Parse #21443 (closed)
time.RFC3339* cannot be parsed using time.RFC3339* as a format in time.Parse #38469 (closed)
time.RFC3339 does not support space between date and time #41461 (closed)
time: documentation shows incorrect formatting of RFC3339 that does not parse #22135 (closed)
time: Weird behavior with RFC3339 parser #30341 (closed)
time: doesn't parse RFC3339 properly #9346 (closed)
time: no Parse format for GNU style RFC3339 #25937 (closed)
time.Parse error with time.RFC3339 & time.RFC3339Nano #5294 (closed)
time: layout string parser doesn't support all needed features to cover the RFC 3339 standard #63488 (closed)
time: RFC3339 time.Parse can not parse string that come from time.Format #20555

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Duplicate of #9346


Issue using pipenv 3.3.1 with Python 3.6

Hello,
I updated pipenv this morning and I encoutered the issue below.
It works fine using pipenv 3.3.0 :)
Traceback (most recent call last):
  File "/usr/bin/pipenv", line 11, in <module>
    load_entry_point('pipenv==3.3.1', 'console_scripts', 'pipenv')()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 560, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2642, in load_entry_point
    return ep.load()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2296, in load
    return self.resolve()
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2302, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3.6/site-packages/pipenv/__init__.py", line 6, in <module>
    from .cli import cli
  File "/usr/lib/python3.6/site-packages/pipenv/cli.py", line 721
    print e
          ^
SyntaxError: Missing parentheses in call to 'print'

Regards,

It looks like you fixed it in https://github.com/kennethreitz/pipenv/commit/0d3a7510fb19616a32f4f4713f855db3fc2ff2e8


How should I set up to make if my prometheus  down and  the sidecar can alert to me

How should I set up to make if my prometheus  down and  the sidecar can alert to me

Hi, unfortunately the sidecar can not send alert to you. If the prometheus instance is down, there is no alerts would be alerted builtin prometheus.
There are two solutions you can try to:

Use a Prometheus HA solution, such as prometheus-operator or two prometheus instances scraped the same targets. Then set rule to check each other.
Use Thanos ruler component as global rule evaluation, and add rules to check the availability of all components of Thanos, include prometheus. Notice for the risk to use ruler you can see here.

About how to set a rule to check the availability, you can read the blog post for further information.

You should probably set up some kind of dead man's switch - Prometheus can continuously send alerts to an AlertManager, and it should forward those to some kind of webhook thing. If it does not receive any alerts in X minutes -> Prometheus can be pronounced dead. This is similar to how watchdogs work on some hardware systems. However, this is not under Thanos scope so I am closing this.

Next option is to use thanos rule or next prometheus instance in HA pair to watch for each other.


Update the example image in the documentation

What
Improve the example image with a newer version!
Why
The old demo gif was very old, it's looking way more appealing now.

Looking good, I, accept your offer mortal!


demo error. _C.cpython-37m-x86_64-linux-gnu.so: undefined symbol:

I followed the step-by-step installation. (https://github.com/ying09/TextFuseNet/blob/master/step-by-step installation.txt)
I got an error for running the demo.
Traceback (most recent call last):
File "demo/icdar2013_detection.py", line 12, in
from detectron2.data.detection_utils import read_image
File "/home/ubuntu/source/TextFuseNet/detectron2/data/init.py", line 4, in
from .build import (
File "/home/ubuntu/source/TextFuseNet/detectron2/data/build.py", line 13, in
from detectron2.structures import BoxMode
File "/home/ubuntu/source/TextFuseNet/detectron2/structures/init.py", line 2, in
from .boxes import Boxes, BoxMode, pairwise_iou
File "/home/ubuntu/source/TextFuseNet/detectron2/structures/boxes.py", line 7, in
from detectron2.layers import cat
File "/home/ubuntu/source/TextFuseNet/detectron2/layers/init.py", line 3, in
from .deform_conv import DeformConv, ModulatedDeformConv
File "/home/ubuntu/source/TextFuseNet/detectron2/layers/deform_conv.py", line 10, in
from detectron2 import _C
ImportError: /home/ubuntu/source/TextFuseNet/detectron2/_C.cpython-37m-x86_64-linux-gnu.so: undefined symbol: _ZN3c105ErrorC1ENS_14SourceLocationERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE

I resolved this issue.

@jireh-father how do you solve it? Could you share your solution with me? Thank you very much!

@jireh-father can you please tell how did you solve it?


It would be nice to have the names database as other tools

Done.
It is actually a map also, so I put it initially among the other maps.


Message keep fall in the Queued, User never receive the communication

I have successfully deployed the author and user app. The author app is opening and I can able to send the communication message however it keeps staying in Queued state and the User is not able to get any communication sent by the author.

I have successfully deployed the author and user app. The author app is opening and I can able to send the communication message however it keeps staying in Queued state and the User is not able to get any communication sent by the author.

I have successfully deployed the author and user app. The author app is opening and I can able to send the communication message however it keeps staying in Queued state and the User is not able to get any communication sent by the author.

@bungleweed

@bungleweed

Hi, i have the same issue. Did you find an answer to this issue?.

Hi, I got the same issue, yesterday.
After I synced the  prep-function application in Deploy Center(classic), it was  solved.
Company Communicator sent all queued messages.
Please see #248

Does anyone know what the issue here is as i am also experiencing this after the upgrade to V4.

Is there any update on this issue? I have a customer who is experiencing this exact thing. Any information that this will get solved in the next update?

Hello @doshijay,
This issue seems to be solved for some users after restarting azure functions and app service.
We are not able to repro this issue. Can you please share some logs or step to repro.
Thanks

I am working with a client and we have this deployed into a Beta Environment and we are facing the queued message issue. We have  restarted the functions and the app service, but then has not helped


Csv upload styling and adding functionality

This is looking great! I found that when I downloaded a CSV and then reuploaded it, all of the colors were different, and I'm not sure why yet.

@mgoadric I am still working on getting the upload to read in the colors. Right now it still generates random colors


Reuse Audit Log app registration when installing a new version of the COE

Hi,
I am trying to install the latest version of the COE in a separate , newly created , environment.
I have it running in an old environment with the Audit logs feature enabled. I created an app registration for thies way back when and it working
I am trying to reuse the App registration that I used with the old environment in my new environment. When I get to the step in the docs where it says Start a new Subscription I enter the tenant and Publisher and click 'Test Operation'  and I get this response:
{
"error": {
"code": "AF20024",
"message": "The subscription is already enabled. No property change."
}
Can I use  the same App registration in two environments running the COE? If not how do I delete the old subsription.

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

ID: 1855a9ee-8713-c8e6-2091-bc972f877c13
Version Independent ID: c87a0108-4de6-49df-8ba3-3bdb06216ad8
Content: Set up audit log components - Power Platform
Content Source: power-platform/guidance/coe/setup-auditlog.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Thanks for your comment, @russgove. This issue has been assigned to the doc author for review.

Hello this is an expected and documented error when you already have the subscription enabled, see

You can use the same app registration in multiple environments, yes.


Search Results: Select columns

Allow the user to select which columns to display in the results.
This setting should be saved to localstorage.
https://inclusive-components.design/data-tables/
Note that this is a big task, because it means implementing columns for all of the remaining fields, and an API querystring field for columns.

The size of this task simply makes it out of scope for this project. This would be weeks' worth of work.


Jump Address

I'm new at this. I need to jump to the original program code, why does the jump address become different?
c.jmp(0x0262A377);
jmp 05A2A377

That instruction is an IP-relative instruction, so my guess is that you didn't initialize decoder.IP to the correct address of the instruction when decoding it (and later disassembling it). See the README examples on how to do this.
If that didn't fix it, add a minimal repro.


Some Exceptions related to misconfigured Entities are swallowed

With the latest changes made to implement #77, some exceptions are swallowed. For example, if an Entity has a field for which no default mapper exists, the NoSuitableMapper exception is swallowed.

Made a few changes and added test a few test cases.


Dashboard example does not work as Python script due to --nopass inconsistency

Hi Ran,
I'm trying to run examples/dashboard.py as-is and it crashes:
bcbrock@ubuntu-xenial$ python dashboard.py
Traceback (most recent call last):
  File "dashboard.py", line 35, in <module>
    dashboard.run()
  File "/home/bcbrock/miniconda3/lib/python3.6/site-packages/qtpylib/reports.py", line 358, in run
    if not self.args['nopass'] and self._password != "":
KeyError: 'nopass'

I believe it will currently only work if called with the explicit --nopass argument:
bcbrock@ubuntu-xenial$ python dashboard.py --nopass
 * Serving Flask app "qtpylib.reports" (lazy loading)
 * Environment: production
   WARNING: Do not use the development server in a production environment.
   Use a production WSGI server instead.
 * Debug mode: on
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 875-155-193

Thanks,
Bishop Brock

Hi @bcbrock,
PR #101 fixes this

Thanks!


chef-service-manager: Should it be run as Administrator?

Currently, the chef-service-manager -a install creates a service that runs as the LOCAL_SERVICE user.
This can cause problems with things like environment variables, etc. Especially if chef-client is ever run directly by the administrator.
Should the service run as Administrator? Or should chef-client refuse to run unless as LOCAL_SERVICE?
To see this you can try running chef-client via cmd as Adminstrator vs. the Service and then check it with:
knife search os:windows -a current_user

Ciao!

Hi adam, we have encountered the same issue now with having the local account being used by chef following to having a server bootstrapped whilst using Azure knife. Just to clarify, is there a way to pass any parameters to knife azure so that it will bootsrap using the right service account, as without it we have chef recipes failing to perform actions that require more access to the domain and things like importing certificates fail for instance.

@eranlevinzon, I think to understand the relevance of this particular issue to what you're seeing, we'll need answers to some of the questions below. In general, you can configure any service, including chef-client, to run as an arbitrary account using the service resource. You'd need to specify that in a recipe to make it work, and potentially restart the service after the configuration.
Here are a few additional questions that might clarify things:

What command line (minus password of course) are you using?
What response do you get?
What versions of knife-azure and knife-windows are on the workstation from which you are initiating the bootstrap?
What version of chef-client is being used on the node?


Fix getPeerCertificates() method to return the right peer certificates

Fix getPeerCertificates() and getPeerHost() and getPeerPort() methods which have failed to return the right values.

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

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

@JacksonTian
Please review and merge the PR

@JacksonTian
Please review and merge the PR

Thank you @mlkui . We released the v1.0.1 after merge it.

Thank you @mlkui . We released the v1.0.1 after merge it.


support gpt-4o-mini

@exsilium In my tests, the 4o-mini experience is not as good as the 4o. Claude is still writing code


Update defaults for RDPG sim

Reference Issues/PRs
None
What does this implement/fix?  Definitely shouldn't be the default
Any other comments?
Also changed loops to False by default since most other sims we have do that

Codecov Report

Merging #339 into master will decrease coverage by 0.33%.
The diff coverage is 62.06%.

@@            Coverage Diff             @@
##           master     #339      +/-   ##
==========================================
- Coverage   88.42%   88.08%   -0.34%
==========================================
  Files          40       41       +1
  Lines        2608     2635      +27
==========================================
+ Hits         2306     2321      +15
- Misses        302      314      +12

Impacted Files
Coverage Δ

graspy/simulations/rdpg_corr.py
57.69% <57.69%> (ø)

graspy/simulations/__init__.py
100.00% <100.00%> (ø)

graspy/simulations/simulations.py
96.10% <100.00%> (-0.39%)
:arrow_down:

Continue to review full report at Codecov.

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


Update nf-libloaderapi-loadlibraryexw.md

Fix the backslash

@RussKie : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Refactor visualization implementations

All of our visualizations have the same basic layout and data flow. This should be encapsulated in a component that handles the layout and data flow.
Overview
All visualizations have the same basic layout, as illustrated in the image below:

The Heading section is provided by the VisualizationsContainer component, so we can ignore that. The other two sections are handled by individual visualization components. The goal is to create a component that can render these two sections with a minimal amount of configuration.
The Inputs section is typically rendered using the InputVariables component. In most visualizations, the specification for the inputs can be statically declared. However, there are increasingly more cases where this can be dynamic, either based on inputs provided by the App (computed variables), or based on the selection of other variables (see Y-aggregation options for line plots).
The Plot and controls section generally has the same structure across all visualizations: a plot and controls on the left, and legend and summary elements on the right.
Proposal
Implement a StandardVisualization component. This component will be responsible for rendering the sections Inputs and Plot and controls sections detailed above. Each visualization will specify how to render inputs, and how to render the plot and controls. StandardVisualization will wire the pieces together, handling data flow from inputs to plots, and will render the layout, included the summary elements.
We will likely want to incorporate some changes desirable for better handling integration with Apps. For example, an App instance can provide one or more variables to the visualization. This should be handled in a generalized way.
TODOs

[ ] Prototype StandardVisualization to determine what the props should be.
[ ] Cost what is involved with keeping things backward compatible. This has to do with how the viz config is specified.
[ ] Specify changes for Apps integration.

Additional details (copied from confluence doc)
A collection of thoughts about the viz refactor and how apps may want to interact with visualizations in web-eda
Apps may bring their own computed variables, opinions about plot options, and axes titles into a visualization. Below is a compiled list of all the overrides I currently know about or expect based on our planned apps. Note that the following is a union of all the app declarations, and each may not be applicable to all apps.
Known overrides
Variables:

xAxisVariable. Example: Ranked abundance boxplot sets its own xAxisVariable boxplot.config.computedVariableMetadata.collectionVariable.collectionVariableDetails
yAxisVariable. Example: Alpha diversity box specifies the yAxisVariable boxplot.config.yVariableDetails
overlayVariable. Example: Ranked abundance scatter sets its own overlay variable
facetVariable. Example: Beta diversity scatter does not allow any faceting

Plot metadata:

x axis title. Example: Ranked abundance boxplot has info that should appear as x axis title
x axis display range. Example: Differential abundance (b60 app) could set the x axis display range
x axis vocabulary (used for reordering the x axis). Example: Ranked abundance boxplot should use the order of the boxplot.config.computedVariableMetadata.collectionVariable.collectionVariableDetails
y axis title. Example: Alpha diversity box sets the y axis title based on the computed variable’s display name boxplot.config.computedVariableMetadata.displayName[0]
y axis display range. Example: Alpha diversity box gets display range info boxplot.config.computedVariableMetadata.displayRangeMin
overlay (legend) title. Example: Ranked abundance scatter. Derived from computation.configuration.collectionVariable
overlay vocabulary (used for reordering the legend labels). Example: Ranked abundance scatter. Should use the order found in boxplot.config.computedVariableMetadata.collectionVariable.collectionVariableDetails
plot title. Example: Ranked abundance boxplot should say if it cutoff the data (see live site for examples). Open to other suggestions of where this info could appear!

Plot modes:

Hide any scatterplot trend line options. Example: Beta diversity scatterplot should not allow trend lines
Hide show missingness toggle. Example: Ranked abundance scatter (under discussion, see Apps: allow no data toggle with computed variables? · Issue #1089 · VEuPathDB/web-eda )
Allow statistics table to be toggled “on” in boxplot. Example: Ranked abundance boxplot

Others:

Apps set a “base entity” for vizs Apps: Enable app instance to set a "base" entity · Issue #952 · VEuPathDB/web-eda . Example: Ranked abundance the base entity should be the collection variable’s entity.

One issue to think about at the same time is to try to avoid making many checks on data consistency like in the fixes for the ticket below, when inputs have been changed but the default axis ranges have not yet been returned from the back end (or something like that).
https://github.com/VEuPathDB/web-eda/issues/1003

Today, we discussed the need to control the disabled attribute of the showMissingness toggle. This toggle is based on the data response for the viz.
I had suggested the Plot and controls section would handle getting data, but doing so means the StandardVisualization component does not have access to the data.
I think another approach we can take is that StandardVisualization takes a callback to get data, as a prop. This callback would take the current visualization config object as an argument. StandardVisualization could then call this callback when the configuration changes, allowing it to control the state of the toggle based on the response. Plot and controls would simply be responsible for updating the visualization configuration.

One issue to think about at the same time is to try to avoid making many checks on data consistency like in the fixes for the ticket below, when inputs have been changed but the default axis ranges have not yet been returned from the back end (or something like that).

I think this can be handled by waiting to update the viz config until after the data is fetched. Thus, Plot and controls we get a callback to update the vizConfig, and StandardVisualization would orchestrate fetching data and updating the config.

Cool. Sounds even more important to split the vizConfig object into two parts: client-side and server-side configs. Only changes in the latter trigger new data requests.  Trouble is, this is likely a breaking non-backwards compatible change.

Could StandardVisualization allow for props like title, xAxisLabel, includePlotModes? Apps will often define variables, but also have information that could be an axis label or that affects if scatter plot trend lines, for example, should be allowed

It's possible that the ShowMissingness toggle could be provided as a CustomInputSection?

Cool. Sounds even more important to split the vizConfig object into two parts: client-side and server-side configs. Only changes in the latter trigger new data requests. Trouble is, this is likely a breaking non-backwards compatible change.
ETA: though us changing a configuration from server to client (or vice-versa) - which might happen in the future - shouldn't be a breaking change either (but it would be under my suggestion)

I don't think we need to split things out like that. Part of the API for that callback could be that if undefined is returned, we just use the current value, so we wouldn't make a new request every time. Or something like that.

It's possible that the ShowMissingness toggle could be provided as a CustomInputSection?
Not sure if that helps or hinders!

I'm not convinced this would be a good thing. If this is a standard option, then we should keep it as-is and figure out the best way to determine if it is enabled. To me, the way to do that is to ensure all viz responses include the same set of properties describing missingness. I think this is already the case, we just need to encode that in our types (i.e., make a base response type) so that we can access it in a visualization-generic way.

small note: Instead of "plot title" we can just have "plot info". Plot info is more descriptive of the goal anyways. The point is that sometimes the computation returns interesting information that would be helpful to the user when they read the viz. That info does not have to go in the plot title, but should go somewhere. One option for implementation was added in #1173

Should we be thinking about axes and colormaps here, too? If we do full screen eda with the map, where the map is the main plot but it has smaller subordinate plots that share the same colormaps, would it be useful to be able to have the main viz tell the small viz what their colormap should be?
To be fair i have no idea how that main-viz-with-component-viz would all work but throwing it out there in case it helps with the current refactor!

Should we be thinking about axes and colormaps here, too? If we do full screen eda with the map, where the map is the main plot but it has smaller subordinate plots that share the same colormaps, would it be useful to be able to have the main viz tell the small viz what their colormap should be? To be fair i have no idea how that main-viz-with-component-viz would all work but throwing it out there in case it helps with the current refactor!

It's not clear to me how the map will be implemented. I was thinking it could be an app, since they are already containers for visualizations. It is also natural for a viz to provide specific variables (such as overlay, in the case of the map).

I was thinking it could be an app, since they are already containers for visualizations

That makes sense! And also how i expect scRNASeq would work (very down the line, to be fair) as well.
The colormap part would be the app determining what colormap to use for all of its vizs. So if the main viz (map, let's say), is coloring points with a particular colormap, then we want all the other vizs to also use that colormap (see page 7 of Bob's mockups).
But perhaps these colormap things are all too far in the future for us to worry about in this refactor?

It's good to think about now, for sure! What's becoming clear is that we need to allow apps to specify these things dynamically, based on the app instance's configuration. The challenge we face right now is determining an interface between an app instance and its visualizations such that we can specify these things in a streamlined way, for any viz. I suppose that is the most critical task, at the moment.

Forever in progress, but dropping another confluence doc full of thoughts here


Change calling function, wrap -> retain in NSString

Hello, while I'm testing whether desktop notification works if I use cacao (testing in my cacao_playground repo), I found user_notifications/mod.rs has called deprecated function of NSString.
I looked up the file history and found that NSString once had a function wrap but it seems to be replaced into reatin function.
So I made a simple change :D

Yep just faced this issue too, thanks @24seconds

Signing can be confusing but isn’t too bad…

Oh my god, it is ... still going at it

Appreciate the PR, but this wound up getting handled in merging the 0.3 branch. Closing!


Improve Readme

See the commit messages for what I've done.

Note I removed the Mac OS reference to not be biased ;) I think "suitable image viewing application" is on point.


Added tornado <6.0 as an explicit dependency

Description
Add Tornado <6 to dependencies.
Rationale
Tornado 6 breaks flower 0.9.2. They have fixed their requirements on github but not released to pypi. This is a bodge round it till they do.
Use case(s) / visualization(s)
Newly built docker images will pickup tornado 6.0 and therefore flower doesn't run. This might be better as an issue incase upstream is fixed, but they haven't released since 2017 so maybe not quick.

I was about to commit this, good job!

@keithjeb please, can you add yourself in the https://github.com/pydanny/cookiecutter-django/blob/master/CONTRIBUTORS.rst

@luzfcb I'm already there ;)

Looks good, thanks for this.
They plan to do a new release in a few days. I'll wait for next week before merging this, if there is no new release by then, we'll implement this in the template. Until then, people with the problem can implement in their generated project.

A new version of Flower has been released with the fix.
We should receive a pull request from Pyup soon with the fix. Strange that there is still nothing ~2 days after though... We should look into it.

Closing as we've upgraded to the latest version of Flower with the fix.
Thanks for the report!


Celsius spelling

Minor point, but "Celsius" is spelled wrong in the description and code. This detracts from wanting to use the sketch.
Thanks for posting it.

@WarthogARJ Fixed! #3


Implement Trapped Rain Water using Dynamic Programming Strategy.

Checklist

[x] Added description of change
[x] Added file name matches File name guidelines
[x] Added tests and example, test must pass
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[x] Relevant documentation/comments is changed or added
[x] PR title follows semantic commit guidelines
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Let's take a look on this PR @realstealthninja & @Panquesito7


Minor bugfix

Remove include=['stainlib'] from find_packages in setup.py to properly detect all submodules.
I left it there by mistake.

fixes #1 on top of #3


Add 7room Aya

Microsoft Reviewers: Open in CodeFlow

Please see #411 to fix the validation issue.

Hi, I have found a fix for your validation issue, see https://github.com/microsoft/winget-pkgs/issues/411 :)

Fixed:
https://www.microsoft.com/en-us/wdsi/submission/3daec44c-a8f2-44ea-9399-809f7dc5e897
https://www.microsoft.com/en-us/wdsi/submission/ca31e52c-9469-44f0-874e-3e5c0b3cfdac


Advocate gotestsum for running go test

Since it allows both progress and json, at the same time (not either / or).
It also has a default format that is more friendly on the eyes than go test.
$ gotestsum --jsonfile test_report.json

https://github.com/gotestyourself/gotestsum

Main issue is recording the current date and execution time "somewhere"...

#21

Duration (should be the test execution time, not the report execution time)
testExecutionDate (should be the test executation date, not the current date)

gotestsum --jsonfile test_report.json --post-run-command 'sh -c "go-test-report <$GOTESTSUM_JSONFILE"'

@afbjorklund I saw the following PR :https://github.com/vakenbolt/go-test-report/pull/62, that will allow users to specify the path to the test2json file produced by gotestsum, which is great! Currently I am running the innovovation you shared above, which is dependent on the env vars being set, but I am still getting:
 Error: ERROR: missing ≪ stdin ≫ pipe. GOTESTSUM_JSONFILE I am manually setting before execution GOTESTSUM_ELAPSED is set by gotestsum itself.

You should not have to set GOTESTSUM_JSONFILE, it should be exported by gotestsum when you use the --jsonfile parameter. There was a small change needed to the GOTESTSUM_ELAPSED variable, to add the "s" (for seconds)
$ gotestsum --jsonfile test_report.json --post-run-command env | grep GOTESTSUM
GOTESTSUM_JSONFILE=test_report.json
GOTESTSUM_JSONFILE_TIMING_EVENTS=
GOTESTSUM_JUNITFILE=
GOTESTSUM_ELAPSED=0.208s

Then what I did is to add two new parameters to go-test-report, and have them default to these environment variables. You can also specify them explicitly, like go-test-report -i test_report.json -e 0.208s, if not using post-run
$ go-test-report -i test_report.json -e 0.208s
[go-test-report] finished in 81.253371ms
$ grep Duration: test_report.html
        ⧉ Total: 18Duration: 208ms

@afbjorklund That is true, it is one or the other. I currently don't see any references to the GOTESTSUM_JSONFILE env var in master, which is likely why I am getting the stdin pipe error, unless I missed it while reviewing the code. Is that dependent on  https://github.com/vakenbolt/go-test-report/pull/62 getting merged ?

You can do something like sh -c "go-test-report <$GOTESTSUM_JSONFILE“ (or just hardcore the file), until it is...

I think we want to the name the file something other than "test_report.json"


Incompatible with neovim stable due to use of lua-fs

This module only works with vim nightly as it uses lua-fs in order to find the correct rc file. The offending code is here

Yeah, I knowingly used vim.fs which is nightly only feature (as I am a nightly user). I'll put requirement on README.

Alright, will this be a requirement for ever or will this be usable on stable from 0.8 going forward?

Yes, vim.fs is technically a v0.8 API so you need to wait for it to be released as stable.

Yeah, I more meant will you try to not use new nightly only APIs going forward? Say once 0.8 is out, some new feature is requested,;would you try to only use stable APIs to implement or can we expect the following version of the plugin to again only work on nightly?

will you try to not use new nightly only APIs going forward?

I also, almost, follow this principle unless something is really required like vim.fs. And the plugin is relatively stable, i hope, so I don't think any other nightly features will be required afterwards once 0.8 is released.


Add support for microseconds

In our project we need seconds with higher precisions - microseconds, e.g. for storing and formatting best time of athlets.
This PR adds support for microseconds without BC break.
The code is also reformatted according to PSR1/PSR2.
Diff without whitespace changes: https://github.com/kevinkhill/php-duration/pull/12/files?w=1

Coverage increased (+0.1%) to 97.727% when pulling 50400de51e006a759aed420529bc7ea71d97d003 on pulzarraider:microseconds into 9fbb2eaf584d0e04f9d49e008c6abe56e2915625 on kevinkhill:master.

Coverage increased (+0.1%) to 97.727% when pulling 50400de51e006a759aed420529bc7ea71d97d003 on pulzarraider:microseconds into 9fbb2eaf584d0e04f9d49e008c6abe56e2915625 on kevinkhill:master.

Looks good to me. Thank you for your contribution!

@kevinkhill Thank you for accepting the PR.


RDF4J failed to parse (probably) valid sparql query.

Here is sparql query which RDF4J fails to parse properly:
select ?Concept where {
  ?Concept a 1.
  ?Concept2 a 1.
} LIMIT 100

Probably this is a bug in RDF4J parser, but I'm not quite sure.
Tested with RDF4J workbench v2.1.2.
See also discussion at https://github.com/RubenVerborgh/SPARQL.js/pull/33

The Turtle and Trig parsers were both updated to handle the horrible "1." syntax but the SPARQL-1.1 parser may not have been done.

It looks as if the SPARQL grammar was silently tweaked at some point to deal with this. Our implemented grammar accepts a decimal with a floating point but no decimal digits (e.g. '1.'). However this production does not exist in the current spec.


upgrade all postgres 9.6 databases in oodikone

Upgrade to the latest postgres version. Support for 9.6 will be dropped in autumn.

Removed "server" from title: Update staging and dev env at the same time, otherwise things will break again.


refactor: #400 http-server store packages

closes #400

exposed user and token stores under a common root directory
exposed cookie store under the same common root directory

Signed-off-by: George Aristy<EMAIL_ADDRESS>

@Baha-sk @talwinder50 let's defer fixing the linting issues for #384 so that @talwinder50 isn't blocked.
I now know what the issue is - check_lint.sh is not checking /pkg nor /test/bdd.

@Baha-sk @talwinder50 let's defer fixing the linting issues for #384 so that @talwinder50 isn't blocked.
I now know what the issue is - check_lint.sh is not checking /pkg nor /test/bdd.

@llorllale I'm ok with fixing linter later, I'm still for updating imports to be properly ordered in this PR.

@Baha-sk

@Baha-sk @talwinder50 let's defer fixing the linting issues for #384 so that @talwinder50 isn't blocked.
I now know what the issue is - check_lint.sh is not checking /pkg nor /test/bdd.

@llorllale I'm ok with fixing linter later, I'm still for updating imports to be properly ordered in this PR.

I'm still deferring to #384 anyway - I think there is a new linter (gci) with different rules for imports.


Addition of a build system generator

I suggest to reuse a higher level build system than your current small make file so that powerful checks for software features will become easier.

CMake
Autotools

I have thought of this but I've let it be as-is for now. CMake can be amazing, I agree completely. I just don't have any experience about it.
In the future I will surely create a more sophisticated way of building the project with the help of cmake. Some evening, when I have the interest and spare time to do so.

Could be nice to use in the future, for better multi OS support, but the Makefile isn't that clustered yet, so I don't see any benefit at the moment either.

Does a tool like "autoscan" show any software dependencies that you find worth for further considerations?
How do you think about to support more development environments by the reuse of build system generators?

I haven't had time to try out autoscan yet, sorry. I will though.
Anyways, old Makefile is now gone and CMakeLists.txt is the only way to generate a build environment. It seems to work fine on Windows 10 and Debian testing x64 but since it's the first CMakeLists.txt I have ever created it may need some refining.

Thanks for your improvements around the CMake build script.


hexify() function emits conversion warning

Hello,
Using gcc 6.1.0.
Compilation error (-Wconversion -Werror):
./deps/json.hpp:9995:25:   required from here
./deps/json.hpp:5957:72: error: conversion to 'char' from 'int' may alter its value [-Werror=conversion]
                             : ('a' + static_cast<char>((v - 10) & 0x1f));
                                                                        ^
./deps/json.hpp:5957:72: error: conversion to 'char' from 'int' may alter its value [-Werror=conversion]

hexify:
const auto hexify = [](const int v) -> char
{
  return (v < 10)
  ? ('0' + static_cast<char>(v))
  : ('a' + static_cast<char>((v - 10) & 0x1f));
};

Could be written as something like:
const auto hexify = [](const int v) -> char
{
    static const std::array<char, 16> hex = { '0', '1', '2', '3',
                                              '4', '5', '6', '7',
                                              '8', '9', 'a', 'b',
                                              'c', 'd', 'e', 'f' };
    return hex[v];
};

Would you be interested in a PR for such a change?

Hi @dtoma, thanks for reporting. Yes, a PR would be great!

Hi @dtoma, if you like, I can add the change myself.

Hi, I'll do it tonight, just got my dev environment setup.


Las Vegas, NV Officer-involved shootings

Someone has requested help on a data project:
Submission notes
Requestor needs help manually researching and investigating officer-involved shootings in the Las Vegas area and maintaining a community-run database.
Location
Las Vegas Police Department , North Las Vegas Police Department, and Henderson Police Department - NV
Requirements
Officer-involved shooting records
How to help
Leave a comment if you'd like to help. Do you have ideas, questions, or need any more information to get started?

We connected the requestor with a volunteer via email.


bug

Hi, there is another bug in the code.
I added Update Plugins option to the dashboard custom center and it works fine but when I update plugins using the option then the cursor changes its position when I close the Packer window and the cursor then starts moving in the empty lines. Please fix

this is my config

this pic is of before updating plugins.

and after updating plugins when I close packer by 'q' then the cursor is on empty lines.

I can't reproduce your problem. then there has issue template you must fill issue template not post lots of image ? please learn how to use github


(GH-2875) Add batch-mode config option for native-ssh

This adds a new batch-mode configuration option for the native-ssh
transport. When set to false, BatchMode is disabled, which allows
SSH to fall back to querying for a password when key authentication
fails. This config option can be set in conjunction with the
ssh-command option to allow users to provide a password
non-interactively to SSH when using native-ssh.
!feature

Add batch-mode configuration option for native-ssh transport
(#2875)
The native-ssh transport has a new batch-mode configuration option
that can be used to enable or disable BatchMode. For more
information, see the
documentation.

Opted for calling this batch-mode over password-only since:

It's a 1:1 name for the BatchMode SSH config option
Disabling BatchMode does not disable authenticating with keys, it just allows falling back to password querying

[x] Documented example works
[x] Sets batch-mode option based on config option
[x] Overrides system SSH config


Make target_desired_distance affect the navigation of NavigationAgent2D/3D

Make target_desired_distance affect the navigation of NavigationAgent2D/3D.

If the target is reachable, end the navigation only when the target is reached
If the target is unreachable, end the navigation when the last waypoint is reached (same as before)

I created a test project to compare the old and new behavior.
Navigation agent tests.zip
Below are screenshots of running the test scenes on 4.1 and this branch.

Test scene screenshots
NavigationAgent2D
4.1

This branch

NavigationAgent3D
Legend

red sphere -> waypoint area
red cylinder -> position where a waypoint_reached signal was emitted
blue sphere -> target area
blue cylinder -> position where the target_reached signal was emitted
white cylinder -> position where the navigation_finished signal was emitted

4.1

This branch

Notes

The diff is bigger than I would have liked but a good chunk of it is because I extracted some code from update_navigation to individual functions (either out of necessity or to be able to express the algorithm with higher level methods). There isn't actually that much new code.
I also updated the documentation of the signals/methods/properties that were affected by this change. Some of the changes are because the behavior changed, others are because the documentation wasn't actually 100% correct from the start.

Fixes #82560

This is unrelated to the PR but I have some questions about the implementation of NavigationAgents.

Is there a reason NavigationAgent2D/3D are Nodes and not Node2Ds/Node3Ds ? IMO making them Node2D/3Ds will remove the need to set a parent and allow to get the position directly in the node. It should then simplify the implementation / remove the possibility for usage errors.
Currently the state update happens through calls to get_next_path_position/is_navigation_finished/get_final_position and to some degree when a NOTIFICATION_INTERNAL_PHYSICS_PROCESS is received. This way you only pay for what you use but this can lead to some finicky behavior. The same update function can also end up running several times a frame. What about updating everything on a NOTIFICATION_INTERNAL_PHYSICS_PROCESS and making the above methods const ? The API doesn't really need to change. Should I open a proposal for that ?

I think what should change is to make sure that the target_desired_distance is never allowed to be lower than the path_desired_distance. The NavigationAgent defaults should be updated to match this. Maybe print a warning if a user tries to set the value lower but clamp it anyway.
Users can set a target_position that is impossible because it is never reachable, e.g. because there is no connected navigation mesh in reach of that position. The current changes in this pr would make the distance check run forever every physics tick for an impossible check or for a path that already has ended and reset state. That should imo not be applied like that.
@ershn
You could join the navigation channel in the Godot Contributors Chat (https://chat.godotengine.org/) if you have general questions about the navigation system so we don't derail this pr. The short answer to your questions is physics / node / legacy jank.

I think what should change is to make sure that the target_desired_distance is never allowed to be lower than the path_desired_distance. The path following is stopped and the state reset when the path end is reached, there shouldn't be random checks running after this point. The NavigationAgent defaults should be updated to match this. Maybe print a warning if a user tries to set the value lower but clamp it anyway.

Yes, that's a reasonable fix. But aren't there genuine use cases where you would want the agent to loosely follow the path but still end up close to the target ? I honestly don't need that in my project right now but that doesn't seem to be an unreasonable requirement.
I just thought of another way to fix the problem. In case the target is reachable, for the last waypoint distance check use target_desired_distance instead of path_desired_distance. This way we can have target_desired_distance to be lower than path_desired_distance without having to run a check after the navigation is finished. It also doesn't seem to contradict the class documentation. What do you think ?

You could join the navigation channel in the Godot Contributors Chat (https://chat.godotengine.org/) if you have general questions about the navigation system so we don't derail this pr.

Sure ! I didn't know about that chat. I'll ask my questions there then. Thank you !

But aren't there genuine use cases where you would want the agent to loosely follow the path but still end up close to the target ?

Yes there could. To support this the pathfollowing would need to be changed so that it does not reset immediately on the last path array point. So this would need to change the check in a way similar like you already outlined. E.g. use the target_desired_distance if feasible but use the path_desired_distance still if the target is not right or reachable.

Ok, I'll update the PR to do that then.

I updated the PR to implement the behavior I described in a previous comment.

In case the target is reachable, for the last waypoint distance check use target_desired_distance instead of path_desired_distance.

Please note that this will slightly change the timing at which the waypoint_reached and navigation_finished signals are fired (maybe link_reached too ?). Until now, in case the target was reachable, for the last waypoint these signals were fired when the agent's position changed to be within path_desired_distance to target_position. Now they will be fired when the agent's position changes to be within target_desired_distance to target_position.
I think that change is ok because the documentation said nothing about this and the new behavior makes sense to me.
Additional notes:

I also updated the class reference to add more details and make it read a bit better. Also changed though to but to make it sound more professional.
I had to do some refactoring to avoid code duplication / having update_navigation call itself.
I took the opportunity to rename update_navigation to _update_navigation to stick with private methods' naming convention.

Also, I'm not sure if we still need to call _check_distance_to_target in NOTIFICATION_INTERNAL_PHYSICS_PROCESS since we are now using target_desired_distance for distance checks directly. It's probably necessary if the agent teleports to the target_position without following the path but do we have to account for that ?

I pushed a small fix to the class reference. I was confusing e.g. with i.e.

Thinking about the problem again, I think the fix in its current form would lead to surprising behavior in some specific cases.
Until now, target_desired_distance didn't affect the navigation. It just controlled when is_target_reached changes to true, when target_reached is fired, and the value of is_target_reachable. This fix would make it affect the navigation too, and therefore make reasoning about NavigationAgents more difficult. IMO the effect target_desired_distance has on the agent shouldn't change with this PR (target distance related methods/properties are actually pretty independent from the rest of navigation agents, they are just convenience methods you could easily implement in user scripts).
Also, in case target_desired_distance is large enough that it encompasses a waypoint with its path_desired_distance radius, the timing at which navigation_finished is fired would be a bit surprising.
The diagram below shows how the navigation agent behaves currently.

red circle: path desired distance
blue circle: target desired distance
orange line: path taken by the agent
grey line: path taken by the agent if it doesn't stop on navigation_finished
blue dot: target_reached signal + is_target_reached turns to true
green dot: waypoint_reached signal
purple dot: navigation_finished signal + is_navigation_finished turns to true + last waypoint_reached signal

Below is how the behavior would change with this fix.

Conceptually the current fix would make it so that navigation_finished signals when we reached the target. However as you can see in the diagram above, this wouldn't always hold true. In the above scenario, I also don't think that stopping the navigation when the blue circle is reached is the correct solution.
@smix8 I think now that we should just make it so that the target distance check runs until necessary, i.e. when the target is reachable, keep running the target distance check on NOTIFICATION_INTERNAL_PHYSICS_PROCESS until the target is reached. I cannot think of other easy ways to fix the problem. What do you think ?

For reference, the diagram below illustrates the problem I'm trying to fix with this PR.

As you can see there is no blue dot. The target_reached signal is never fired and is_target_reached never turns to true.

I also don't think that stopping the navigation when the blue circle is reached is the correct solution.

I think it would be. The target_desired_distance was designed to control when the pathfollowing should end at the last path position and override the path_desired_distance behavior for that position. That is the entire reason why this was separated into its own property.

I see. If that's the intended effect of target_desired_distance, the current behavior definitely needs a fix.
Before making changes, I'd like your opinion on the following scenario. What do you think should happen here ?

If we end the navigation when the blue circle is reached, the last returned waypoint will actually be outside of the target's radius. But maybe there isn't much we can do here ? (and we should let the user be responsible for stopping the movement when the target is reached ?)

If we end the navigation when the blue circle is reached, the last returned waypoint will actually be outside of the target's radius. But maybe there isn't much we can do here ?

For that to even happen users would need to set the target_desired_distance willingly to such a large value so the result is on them.

I agree that users are responsible for the settings they use and that common cases should be prioritized.
But what I was trying to make sure with that example is that the algorithm is sound, i.e. it makes sense in all cases. IMO testing an algorithm at its limits is a good way to check if it's actually correct (that's how I found the bug above).
We seem to agree that there is no problem here, so I'll proceed with the changes 👍

This proved to be more work than I expected but the PR should be ready for review now.
I also updated the PR description with test scene screenshots.

I see ! If that's the intended effect of target_desired_distance, the current behavior definitely needs a fix then.
Before making changes, I'd like your opinion on the following scenario. What do you think should happen here ?

If we end the navigation when the blue circle is reached, the last returned waypoint will actually be outside of the target's radius. But maybe there isn't much we can do here ? (and we should let the user be responsible for stopping the movement when the target is reached ?)

I originally thought navigation should finish once the destination waypoint is reached:

path to all waypoints using path_desired_distance
if the next waypoint is the last one, then consider it reached if within target_desired_distance instead of path_desired_distance

I like this implementation though, since it allows you to preempt the pathfinding if you get within target_desired_distance (if that is greater than path_desired_distance) - possibly allowing an agent to (maybe only incidentally) avoid pathing around a wall if unnecessary.
I'm fine with this fix because it solves my particular problem - I don't want my agents to be picky about hitting their path waypoints, but I want them to stop almost exactly where they're told. The 4.1 implementation doesn't take this difference into account, and I'm excited to see this change.

I tested it for the discussed changes and it works in general fine for the target desired distance as I would expect but what worked unexpectedly is that target desired distance seem to not reliably or at all overrule the path desired distance for the last path position.
E.g. if I set a NavigationAgent target_desired_distance to 0.5 and the path_desired_distance to 5.0 the agent does never move in to 0.5 distance of the target. It stops the path at 5.0 distance to the last path position. Since in my test I immediately query a new path to the next patrol position when the path ends my agent basically never even comes close to the target position.

@smix8 I can't reproduce the problem you're seeing on my side. Could you provide a test project to reproduce the behavior you are seeing ? Or maybe the source code you are using for the agent ?

if I set a NavigationAgent target_desired_distance to 0.5 and the path_desired_distance to 5.0 the agent does never move in to 0.5 distance of the target. It stops the path at 5.0 distance to the last path position.

The only reason I can see this happening is because the target is unreachable. If the target is unreachable the target_desired_distance doesn't override path_desired_distance.
Or maybe it's because you are requesting a new path directly when reaching the last waypoint ? E.g. even after this change and even if target_desired_distance < path_desired_distance, waypoint_reached will be sent when the agent moves within path_desired_distance of the last waypoint. If you want the agent to reach the target you need to wait for the target_reached or navigation_finished signal.
The test project I uploaded in the description tests for the scenario you are describing but everything seems to be working as expected. In the images below, the white cross/cylinder is also the final position of the agent.

I tested the 3D scene with path_desired_distance = 2.0 and target_desired_distance = 0.1.

The agent stops at the path desired distance circle.
I noticed that the problem happens with any target desired distance value below 0.5 in that scene. If the value is >= 0.5 it works as expected.

Ah I see ! In that scene 0.5 is the y distance between the scene geometry and the computed navigation mesh.
The problem was that get_final_position didn't subtract path_height_offset from the position it returned. This position was then used by is_target_reachable which resulted in the target being considered unreachable when target_desired_distance < 0.5. This bug should be fixed now.
It seems this problem has been there for a while but it became more apparent with this PR, since is_target_reachable now affects navigation.
On an unrelated note, I took this opportunity to also change the order in which the target_reached and navigation_finished signals are sent (target_reached first now). This will allow using is_target_reached in navigation_finished signal callbacks. Re-tested everything after this change.

I tested the change with the 3D demo scene but with any target_desired_distance below 0.5 is enough to get the agent stuck on the last path_desired_distance red circle instead of moving closer to the target_desired_distance blue circle.

Sorry but I really can't reproduce the problem this time. Could you provide more info ?
I did a fresh build on this branch, downloaded the zip in the description, and run every 3D scene with values of 0.1 (the minimum), 0.4, 0.5 for target_desired_distance. I also tested a bunch of different combinations with path_desired_distance but I couldn't find a case where it doesn't work as expected.
It also doesn't seem like I forgot to push a commit.

Please note that you need to have a path_height_offset of 0.5 (the default) in the 3D test scenes, otherwise the target won't be considered reachable.

Sorry but I really can't reproduce the problem this time.

It is fine and works. I noticed I made a mistake. I set some properties in script from testing. When I started to print those values I noticed that they did not match what I set on the NavigationAgent node.

When can we hope a release ? I think I'm affected by this bug

Thanks!

When can we hope a release ? I think I'm affected by this bug

I am trying to create an agent that utilizes Path Desired Distance with .1 and Target Desired Distance with .1 but it just seems to get stuck in a re-loop 99.99% of the time, the goal is to have 99.99% precision in my case . Hopefully this fixes that issue if I understand this thread correctly.  I have not tested or reviewed the code being implemented here.
I have read documentation and example code  possible for setting up a simple navigation region 3d on simple geometry with basic settings with character controlled agent that simply clicks a position on a map and uses the navigation system to get there. I also cannot get the navigation mesh to properly work with default settings on very smooth geometry for hills inclines/slopes without setting the cell height to .01-.1f which seems to cause other issues I cannot fathom. I personally am using Terrain3D for terrain but had exact same issues on a default plane/block

Any news ?


GitHub actions

Should I change the action to run on pull requests against any branch instead of just against dev and main?


Allow overriding ciphers for https servers

See https://groups.google.com/g/mountebank-discuss/c/PkCCeK4XOSY/m/jOcyYaDXAQAJ?pli=1

Is cipher option available for HTTPS IMPOSTER after this fix? Please someone confirm. TIA.


Android MSAL Configuration and Authority URL

Thanks for this document. It mostly works as captured. However, there are 2 areas that I need help on:

The MSAL Configuration that is generated in the Android configuration page on the AD portal is not similar. The "type" tag that is autogenerated is "B2C" but the documentation refers to "AAD"
The authority URL specified in the document is "https://login.microsoftonline.com/common" which is deprecated.

I have attempted to substitute the AAD reference to B2C and authority URL to b2clogin.com but it doesn't work. Is there a different documentation that supports the new type and authority elements?

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

ID: aecf9610-b6e2-75fc-a674-869d9b95702c
Version Independent ID: 360def71-eacf-185b-4f6d-41e60e57e610
Content: Tutorial: Create an Android app that uses the Microsoft identity platform for authentication - Microsoft identity platform
Content Source: articles/active-directory/develop/tutorial-v2-android.md
Service: active-directory
Sub-service: develop
GitHub Login: @mmacy
Microsoft Alias: hahamil

@onyand Thank you for your feedback . We will have this reviewed and update the thread.

@onyand It sounds like you're working in an Azure AD B2C tenant, while this tutorial is intended for Azure AD tenants.
Have you taken a look at this article in the B2C documentation, by chance?
Sign-in using an Android application in Azure Active Directory B2C
Cc: @msmimart
#reassign:mmacy

Closing due to inactivity. If you still have questions, please refer to the B2C documentation mentioned in https://github.com/MicrosoftDocs/azure-docs/issues/64423#issuecomment-709396413. Thanks!

Have you taken a look at this article in the B2C documentation, by chance?
Sign-in using an Android application in Azure Active Directory B2C

#please-close


Only validating custom parameters if algorithm has been selected

Fixes #2003
Changes proposed in this PR:

Only validating custom parameters if algorithm has been selected

looks good, i'll approve after we merge #2004 and do one more test


 That's bad in general, but it's also bad specifically because it means the flutter create test is slow, and that makes all our tests slow.

It's not that bad these days.

It really is, It took 15mins to create a project.

@yassinya That is definitely not normal; please file a bug and provide as much information as you can (e.g. what your network speed is, what your device speed is, etc).

Slow for me running command from Shanghai.