Ensure Migration.enumerateObjects(ofType:_:) consistently uses property mappings

Problem
When performing a Migration.enumerateObjects(ofType:_:), within the executed block (MigrationObjectEnumerateBlock) the old object and new object inconsistently use the property mappings for the given object.
Suppose the example snippet below:
class Example: Object {
    // ...
    @Persisted var someField: String = "default value"
    // ...

    override class public func propertiesMapping() -> [String : String] {
        [
            "someField": "some_field"
        ]
    }
}

Inside of a migration, when running enumerateObjects(ofType:_:), I observe the following behaviour within the MigrationObjectEnumerateBlock:

The new object can only access Example.someField by using newObject["someField"]
The old object can only access Example.someField by using oldObject["some_field"].

I understand this is probably to do with something under the hood when Realm actually maps the properties, and that changing this might be not worth the difficulty.
Even if this is decided to be the intended behaviour, this should be documented as I had to work this out through trial and error.
Solution
No response
Alternatives
No response
How important is this improvement for you?
I would like to have it but have a workaround
Feature would mainly be used with
Local Database only

Makes sense to me regarding the old objects, and yeah its a difficult one to remedy as your points are all very valid. I don't think being able to access both mapped and unmapped is what I was asking for, as collisions are possible as you say.
Given that changing the behaviour will result in legacy code being broken, I think documentation would be sufficient in this case.
I don't know what Realm's attitude to breaking changes is, but it could be staged for a future major release if still applicable?

It's the sort of breaking change that's really spooky because it has the potential for a developer to not notice the change and ship an update to their app which corrupts user data. In the worst case it leads to a migration block completing successfully but reading the wrong field, so even if the developer is testing old migrations they could possibly miss it. We could maybe do something like have a config option to opt into the correct behavior and then log a warning if property mappings are read in a migration without the option set?

Seems pretty reasonable to me! Not a huge priority now that I know what is going on, but I think this could be a nice improvement for increasing consistency and lowering cognitive load when dealing with codebases that make heavy use of mappings!


Add a section about updating Bikeshed

I've seen people forget to update Bikeshed's code, so I'd like to have a link target that says to do that.

I don't have CI for the docs. Mind building the document and including it in the PR?

Built.


Pasting an emoji in code creates an invisible error (Parse Error: Unknown character)

Godot version:
3.1 beta 3
OS/device including version:
Windows 10
Issue description:
When you paste an emoji in the code editor, it looks like it didn't accept the symbol  because no character is shown. But it's there so it throws an unkown character error. It won't happen to people often but if it does happen, it could keep people clueless of what the problem is because you don't see anything wrong.
Steps to reproduce:
Paste an emoji in the code editor

i think godot is trying to tell us something

Yeah the code doesn't need support for emojis imo, but the code should either not accept the character at all or show a "missing symbol" symbol

or show a "missing symbol" symbol

Missing char symbol is shown in other input fields (using Noto Sans UI font) but not in the code editor (using Hack font), that's probably a problem with the font.

Still valid in 05395cb


A correction to doc/usr_05.txt

In this part
GETTING A GLOBAL PLUGIN

Where can you find plugins?
- Some come with Vim.  You can find them in the directory $VIMRUNTIME/macros
  and its sub-directories.

$VIMRUNTIME/macros and its sub-directories should probably be replaced with $VIMRUNTIME/plugins since the global plugins mentioned in the previous section and linked to with the  |standard-plugin-list|  tag are located in plugins.
gvim_8.1.0189_x86.zip

Also, in the same file, section GETTING A FILETYPE PLUGIN, "macros" should be replaced with "plugins" in "The scripts in $VIMRUNTIME/macros are global ones, [...]"

The plugins in $VIMRUNTIME/plugin are (by virtue of being in the plugin subdirectory) already installed, you don't need to "get" them. OTOH, $VIMRUNTIME/macros contains additional, optional, plugins, which you may or may not want to install. Of these, matchit is also distributed as an optional package, so :packadd matchit will load it, and in fact that command (with an aditional ! to load it together with other global plugins) is found near the end of the vimrc_example.vim. (The reason this plugin is present at both places is that Vim acquired the package mechanism much later than both matchit.vim and the macros subdirectory.)
Best regards,
Tony.

Ah, sorry, I understand now. Because instead of "complete" plugins I found several small files sourcing packages in $VIMRUNTIME/macros, I somehow decided the standard plugins had resided in macros in the past, but then were moved to plugins, which for some reason wasn't reflected in the docs.
Closing the issue, thank you.

In this part
GETTING A GLOBAL PLUGIN

Where can you find plugins?
- Some come with Vim.  You can find them in the directory $VIMRUNTIME/macros
  and its sub-directories.

$VIMRUNTIME/macros and its sub-directories should probably be
replaced with $VIMRUNTIME/plugins since the global plugins mentioned
in the previous section and linked to with the
|standard-plugin-list|  tag are located in plugins.

The  plugin  directory contains files that are already being loaded.
The docs point to other plugins you could use.
It should now also point to the packages directory though.
--
hundred-and-one symptoms of being an internet addict:
260. Co-workers have to E-mail you about the fire alarm to get
you out of the building.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Unrelayed txs

Problem
I have unrelayed txs. When I try to run rly tx rly <path> I get
$ rly tx rly goz-path -d
Error: no packet data found
no packet data found

Query full-path
{
  "chains": {
    "gameofzoneshub-1a": {
      "reachable": true,
      "height": "36344",
      "client": {
        "id": "wollcojoza",
        "height": "96"
      },
      "connection": {
        "id": "jvvvcipjlz",
        "state": "OPEN"
      },
      "channel": {
        "id": "rpuqkxcrtb",
        "port": "transfer",
        "state": "OPEN",
        "order": "ORDERED"
      }
    },
    "baz-chain3": {
      "reachable": true,
      "height": "6856",
      "client": {
        "id": "vsjuqhfheb",
        "height": "30268"
      },
      "connection": {
        "id": "tfthfskhix",
        "state": "OPEN"
      },
      "channel": {
        "id": "pbreehjdip",
        "port": "transfer",
        "state": "OPEN",
        "order": "ORDERED"
      }
    }
  },
  "unrelayed-seq": {
    "src": [
      "2",
      "3",
      "4",
      "5",
      "6",
      "7",
      "8",
      "9",
      "10"
    ]
  }
}

I've been unable to reproduce this issue and we just cut a new release. I'm going to close this issue as likely solved.


Dropdown not shown on a node on opening a simple project, appears when clicked into.

https://user-images.githubusercontent.com/4699705/232742627-270bb14e-48e5-4b9c-aa07-e233eae368f6.mp4
The Table.get should show a dropdown of the column names.
If edited the dropdown appears.
On Windows 11 Pro with newest develop as of 18th April.

Tried similar cases, but always got the drop down. I will try to replicate the exact graph from the clip.

I was unable to reproduce it on the 6d3151f32da9367790e8635036ccb1f31b4b254d even on the original project (with stripped metadata, but could it influence the drop downs?). @jdunkerley do you still reproduce it on 04-20 nightly?

I can reproduce it with today nightly (20.04) for a Restaurants template. Here is the video.
https://user-images.githubusercontent.com/12892578/233347065-8d8397f7-4cb1-488d-9f92-c3e8a5cb8476.mov

Still there for me on the newest build

Indeed, Restaurants example shows me the bug.


Forms

Added some typography and fixed the form elemens - still a bit broken though.

@jasonmelgoza any idea why this can't merge?

@allancorbett did you try merging in changes from the master branch?


Filename too long error on Linux Mint with file encryption

Is there an existing issue for this?

[X] I have searched the existing infra issues

Type of Request
bug
Infrastructure Environment
flutter run
What is happening?
I have Linux Mint with /home/username encryption (default encryption provided as OS installation option).
Flutter is version 3.16. I tried using Android Studio and VS Codium both with Flutter plugin. Both produce the same error.
I've used emulator of Pixel 7 API 34. Both flutter SDK, Andorid Studio/VS Codium and flutter project are placed within /home/username directory.
I'm not the only one to face this error, I've created question on StackOverflow and other developers also have the same problem, link to question:
https://stackoverflow.com/questions/77511262/cant-run-flutter-project-on-emulator-filename-too-long-error/77518558
Other user stated that encryption limits filename length in OS to 143 characters.
If i run Flutter SDK in 3.13.9 version project runs without any problem no matter if on Android Studio or VS Codium.
Logs:
flutter run --debug

Output log
Launching lib/main.dart on sdk gphone64 x86 64 in debug mode...
startup failed:
/home/damian/dev_tools/flutter/packages/flutter_tools/gradle/build/classes/groovy/main/FlutterPlugin$_addTasksForOutputsAppLinkSettings_closure22$_closure48$_closure50$_closure51$_closure52$_closure53$_closure55$_closure57$_closure58.class (filename too long)

1 error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':gradle:compileGroovy'.
> Compilation failed; see the compiler error output for details.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 31s
Running Gradle task 'assembleDebug'...                             32,6s
Exception: Gradle task assembleDebug failed with exit code 1

More details:
/home/damian/dev_tools/flutter/packages/flutter_tools/gradle/build/classes/groovy/main/FlutterPlugin$_addTasksForOutputsAppLinkSettings_closure22$_closure48$_closure50$_closure51$_closure52$_closur
e53$_closure55$_closure57$_closure58.class (filename too long)
[  +30 ms] 1 error
[ +122 ms] > Task :gradle:compileGroovy FAILED
[   +2 ms] :gradle:compileGroovy (Thread[included builds,5,main]) completed. Took 17.064 secs.
[        ] FAILURE: Build failed with an exception.
[   +6 ms] * What went wrong:
[        ] Execution failed for task ':gradle:compileGroovy'.
[        ] > Compilation failed; see the compiler error output for details.
[        ] * Try:
[        ] > Run with --debug option to get more log output.
[   +7 ms] > Run with --scan to get full insights.
[   +1 ms] * Exception is:
[        ] org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':gradle:compileGroovy'.
[   +5 ms]      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:142)
[        ]      at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:282)
[   +3 ms]      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:140)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:128)
[  +10 ms]      at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
[        ]      at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
[        ]      at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
[        ]      at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
[   +6 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
[   +4 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
[        ]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
[   +2 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
[  +12 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[   +7 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
[   +7 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
[   +6 ms]      at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:69)
[        ]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:327)
[        ]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:314)
[   +1 ms]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:307)
[   +3 ms]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:293)
[        ]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:417)
[        ]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:339)
[        ]      at org.gradle.execution.plan.DefaultPlanExecutor.process(DefaultPlanExecutor.java:96)
[        ]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph.executeWithServices(DefaultTaskExecutionGraph.java:140)
[        ]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph.execute(DefaultTaskExecutionGraph.java:125)
[        ]      at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:39)
[   +8 ms]      at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:51)
[   +1 ms]      at org.gradle.execution.BuildOperationFiringBuildWorkerExecutor$ExecuteTasks.call(BuildOperationFiringBuildWorkerExecutor.java:54)
[        ]      at org.gradle.execution.BuildOperationFiringBuildWorkerExecutor$ExecuteTasks.call(BuildOperationFiringBuildWorkerExecutor.java:43)
[   +4 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[  +11 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[   +5 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[   +4 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[        ]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
[        ]      at org.gradle.execution.BuildOperationFiringBuildWorkerExecutor.execute(BuildOperationFiringBuildWorkerExecutor.java:40)
[        ]      at org.gradle.internal.build.DefaultBuildLifecycleController.lambda$executeTasks$7(DefaultBuildLifecycleController.java:161)
[        ]      at org.gradle.internal.model.StateTransitionController.doTransition(StateTransitionController.java:247)
[        ]      at org.gradle.internal.model.StateTransitionController.lambda$tryTransition$7(StateTransitionController.java:174)
[        ]      at org.gradle.internal.work.DefaultSynchronizer.withLock(DefaultSynchronizer.java:44)
[        ]      at org.gradle.internal.model.StateTransitionController.tryTransition(StateTransitionController.java:174)
[  +16 ms]      at org.gradle.internal.build.DefaultBuildLifecycleController.executeTasks(DefaultBuildLifecycleController.java:161)
[        ]      at org.gradle.internal.build.DefaultBuildWorkGraphController$DefaultBuildWorkGraph.runWork(DefaultBuildWorkGraphController.java:156)
[        ]      at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:249)
[        ]      at org.gradle.internal.work.DefaultWorkerLeaseService.runAsWorkerThread(DefaultWorkerLeaseService.java:109)
[        ]      at org.gradle.composite.internal.DefaultBuildController.doRun(DefaultBuildController.java:164)
[        ]      at org.gradle.composite.internal.DefaultBuildController.access$000(DefaultBuildController.java:45)
[  +32 ms]      at org.gradle.composite.internal.DefaultBuildController$BuildOpRunnable.run(DefaultBuildController.java:183)
[        ]      at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
[        ]      at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
[        ]      at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
[        ]      at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
[        ]      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[        ]      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[        ]      at java.base/java.lang.Thread.run(Thread.java:833)
[        ] Caused by: org.gradle.api.internal.tasks.compile.CompilationFailedException: Compilation failed; see the compiler error output for details.
[  +14 ms]      at org.gradle.api.internal.tasks.compile.ApiGroovyCompiler.execute(ApiGroovyCompiler.java:276)
[        ]      at org.gradle.api.internal.tasks.compile.ApiGroovyCompiler.execute(ApiGroovyCompiler.java:64)
[        ]      at org.gradle.api.internal.tasks.compile.GroovyCompilerFactory$DaemonSideCompiler.execute(GroovyCompilerFactory.java:97)
[        ]      at org.gradle.api.internal.tasks.compile.GroovyCompilerFactory$DaemonSideCompiler.execute(GroovyCompilerFactory.java:76)
[        ]      at org.gradle.api.internal.tasks.compile.daemon.AbstractDaemonCompiler$CompilerWorkAction.execute(AbstractDaemonCompiler.java:135)
[        ]      at org.gradle.workers.internal.DefaultWorkerServer.execute(DefaultWorkerServer.java:63)
[  +19 ms]      at org.gradle.workers.internal.AbstractClassLoaderWorker$1.create(AbstractClassLoaderWorker.java:49)
[        ]      at org.gradle.workers.internal.AbstractClassLoaderWorker$1.create(AbstractClassLoaderWorker.java:43)
[        ]      at org.gradle.internal.classloader.ClassLoaderUtils.executeInClassloader(ClassLoaderUtils.java:100)
[        ]      at org.gradle.workers.internal.AbstractClassLoaderWorker.executeInClassLoader(AbstractClassLoaderWorker.java:43)
[        ]      at org.gradle.workers.internal.IsolatedClassloaderWorker.run(IsolatedClassloaderWorker.java:49)
[        ]      at org.gradle.workers.internal.IsolatedClassloaderWorker.run(IsolatedClassloaderWorker.java:30)
[        ]      at org.gradle.workers.internal.WorkerDaemonServer.run(WorkerDaemonServer.java:87)
[        ]      at org.gradle.workers.internal.WorkerDaemonServer.run(WorkerDaemonServer.java:56)
[        ]      at org.gradle.process.internal.worker.request.WorkerAction$1.call(WorkerAction.java:138)
[        ]      at org.gradle.process.internal.worker.child.WorkerLogEventListener.withWorkerLoggingProtocol(WorkerLogEventListener.java:41)
[        ]      at org.gradle.process.internal.worker.request.WorkerAction.run(WorkerAction.java:135)
[        ]      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[   +2 ms]      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
[        ]      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[        ]      at java.base/java.lang.reflect.Method.invoke(Method.java:568)
[        ]      at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
[        ]      at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
[        ]      at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182)
[        ]      at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164)
[        ]      at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:414)
[        ]      at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
[        ]      at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
[        ]      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[        ]      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[        ]      at java.base/java.lang.Thread.run(Thread.java:833)
[        ] * Get more help at https://help.gradle.org
[  +10 ms] BUILD FAILED in 20s
[   +1 ms] 1 actionable task: 1 executed
[        ] Some of the file system contents retained in the virtual file system are on file systems that Gradle doesn't support watching. The relevant state was discarded to ensure changes to these
locations are properly detected. You can override this by explicitly enabling file system watching.
[  +42 ms] Stopped 1 worker daemon(s).
[ +642 ms] Running Gradle task 'assembleDebug'... (completed in 21,2s)
[+6474 ms] Exception: Gradle task assembleDebug failed with exit code 1
[   +4 ms] "flutter run" took 30 295ms.
[   +5 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:752:9)
           <asynchronous suspension>
           #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1350:27)
           <asynchronous suspension>
           #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:348:9)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:294:5)
           <asynchronous suspension>
           #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:112:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #10     main (package:flutter_tools/executable.dart:90:3)
           <asynchronous suspension>

Steps to reproduce

On PC with Linux Mint 21.2 x86_64  create new Flutter project somewhere in /home/username directory.
You can leave default code or write your own - doesn't change anything.
Run project on Android device emulator.

Expected results
I expect application to run properly on Linux Mint with file encryption  active using Flutter 3.16.'
flutter doctor -v output
[✓] Flutter (Channel stable, 3.16.0, on Linux Mint 21.2 5.15.0-76-generic, locale pl_PL.UTF-8)
• Flutter version 3.16.0 on channel stable at /home/damian/dev_tools/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision db7ef5bf9f (6 dni temu), 2023-11-15 11:25:44 -0800
• Engine revision 74d16627b9
• Dart version 3.2.0
• DevTools version 2.28.2
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /home/damian/dev_tools/android_sdk/
• Platform android-34, build-tools 34.0.0
• Java binary at: /home/damian/dev_tools/android_studio/jbr/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
• All Android licenses accepted.
[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✗] Linux toolchain - develop for Linux desktop
✗ clang++ is required for Linux development.
It is likely available from your distribution (e.g.: apt install clang), or can be downloaded from https://releases.llvm.org/
✗ CMake is required for Linux development.
It is likely available from your distribution (e.g.: apt install cmake), or can be downloaded from https://cmake.org/download/
✗ ninja is required for Linux development.
It is likely available from your distribution (e.g.: apt install ninja-build), or can be downloaded from
https://github.com/ninja-build/ninja/releases
• pkg-config version 0.29.2
✗ GTK 3.0 development libraries are required for Linux development.
They are likely available from your distribution (e.g.: apt install libgtk-3-dev)
[✓] Android Studio (version 2022.3)
• Android Studio at /home/damian/dev_tools/android_studio
• Flutter plugin version 76.3.2
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
[✓] Connected device (2 available)
• sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64 • Android 14 (API 34) (emulator)
• Linux (desktop)              • linux         • linux-x64   • Linux Mint 21.2 5.15.0-76-generic
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 2 categories.

I'm using the latest release of VSCodium but can't reproduce this. Perhaps it only happens in case the file system is encrypted as mentioned.
Per suggestion at https://stackoverflow.com/a/77518558, I will label the issue for other's input. Meanwhile, please also share the output of flutter doctor -v as well. Thanks!

@bartekpacia do you know if our Android gradle build rules are supposed to be creating files with paths like:
/home/damian/dev_tools/flutter/packages/flutter_tools/gradle/build/classes/groovy/main/FlutterPlugin$_addTasksForOutputsAppLinkSettings_closure22$_closure48$_closure50$_closure51$_closure52$_closur e53$_closure55$_closure57$_closure58.class?
Per the well-written answer in https://stackoverflow.com/questions/77511262/cant-run-flutter-project-on-emulator-filename-too-long-error/77518558, it sounds like this is how groovy works, encoding the call stack into the file paths of these compiled bytecode files. I also agree with the options listed there:

users affected by "filename too long" errors must build their app in a non-encrypted partition (here's the upstream bug in ecryptfs https://bugs.launchpad.net/ecryptfs/+bug/344878, sounds like there's a workaround for file-based encryption, but not partition based)
customize gradle to generate *.class files <= 143 characters long (not sure how easy or hard this is)
refactor our groovy to be less nested (not sure if this is worth the effort, as this is more of a workaround than a robust fix)

cc @chunhtai as I think https://github.com/flutter/flutter/commit/61242fa13b4801947c4f392b11187e8a0329f299 was the last straw that broke the camels back for certain users (this could have always happened before with users with for example very long home directory names) and @reidbaker

Same problem on Linux Mint

Same issue as described on Linux Mint. Has someone tried to move the flutter binaries out of the home dir? In my case, I have them in /home/philipp/snap/flutter and the flutter project is in /home/, too. I am wondering if it helps when I move flutter out but keep the project.

Has someone tried to move the flutter binaries out of the home dir?

@Philippdosch My $HOME is encrypted. I moved the flutter SDK to /data and kept my project in a subdirectory of $HOME, which works perfectly fine :+1:
Just remember to run flutter clean and remove any stale build artifacts after moving the SDK :sweat_smile:

Ok, let me try this later as well, thanks.

You need to install/move flutter src to external drive

Had the same problem, solved. Flutter was in subdirectory of $HOME via snap. Removed snap, reinstalled flutter in non-encrypted path
I also moved gradle home, not sure if that helped, but now no part of the build needs my home directory. It was at ~/.gradle but I moved it to a non encrypted directory. I updated "gradle home" (ctrl+shift+a in android studio). I did this twice, in both the flutter project and the android directory as an android project.
Don't forget to restart your IDE and run flutter clean

The same issue here

Had the same problem, solved. Flutter was in subdirectory of $HOME via snap. Removed snap, reinstalled flutter in non-encrypted path
I also moved gradle home, not sure if that helped, but now no part of the build needs my home directory. It was at ~/.gradle but I moved it to a non encrypted directory. I updated "gradle home" (ctrl+shift+a in android studio). I did this twice, in both the flutter project and the android directory as an android project.

I'm unable to use flutter at all. There is no way to switch to Windows or use Unencrypted disk!

moving the gradle caches to an unencrypted filesystem, and linking to there seem to work:
mv $HOME/.gradle/caches /mnt/SOME-UNENCRYPTED-FS/gradle-caches

ln -s /mnt/SOME-UNENCRYPTED-FS/gradle-caches $HOME/.gradle/caches

I encountered problems with files in the directory of my Flutter SDK installation (located at ~/flutter).
An example of the issue was:
~/flutter/flutter/packages/flutter_tools/gradle/build/classes/groovy/main/FlutterPlugin$_addTasksForOutputsAppLinkSettings_closure13$_closure41$_closure43$_closure44$_closure45$_closure47$_closure54$_closure59$_closure60.class (File name too long)

My Solution: In the file ~/flutter/flutter/packages/flutter_tools/gradle/build.gradle.kts
I redirected the buildDir to an ext4-formatted SD card (which is now inserted in my laptop’s card slot).
Here’s what I added:
buildDir = file("/media/username/SD_CARD/flutter")

Honestly, this doesn’t feel like the right solution. But for now, it works.


Sending an email

Is it possible to send an email using scotty ? How is the proper way to achieve sending an email ?

I think email is out of scope for a mini web framework like scotty. You should probably use an email library - smtp-mail for example.

Shall we close this issue?

Closing. Out of scope.


Compile RE2 from source in Fedora-based builds

It seems that we need to compile this from source, as the package included with Fedora adds -std=c++11 and that breaks the build when using newer versions of gRPC which (correctly) add RE2 as a dependency for their pkg-config files.

This is now done.


Use Google sheets API

Move the hardcoded data out of the repo and use the Google Sheets API instead to pull the data on page load.
Also, update all the instructions once this is changed.

Unfortunately, this isn't reasonably attainable due to Same-Origin Policy restrictions. See https://github.com/nfischer/framily-tree/issues/12

I was under the impression the Google Sheets API included CORS headers to allow this (source). Is this not enough?

That could work, but we would still run into the issue of publicly exposing our API key since we don't have any environment vars to hide behind.

As I recall, the web-based sheets API has a way to whitelist which URLs are allowed to call the API. So, we would whitelist our sites and personal IP addresses (for development purposes), and no other pages could actually call the APIs (google would toss away the requests). It kind of makes the key useless, since the site whitelist is the real key.

Interesting, it does seem like GH Pages supports CORS. I'll keep looking into it.


Improve mapStateToProps invariant validation error message

During refactoring of my stores I more than once hit an invariant violation like this:
Uncaught Invariant Violation: `mapStateToProps` must return an object. Instead received "A string".
Uncaught Invariant Violation: `mapStateToProps` must return an object. Instead received .

It would be nice of the name of the connected component would also be part of the error message
The latter error message above is from an "undefined" return I guess, so it should print that in the error message:
Uncaught Invariant Violation: 'ComponentName mapStateToProps' must return an object. Instead received undefined

Totally. Those messages were never considered carefully. Please feel free to work on a PR to make them user-friendly!

:+1:

Hey @BerkeleyTrue, @gaearon, is anyone working on this currently?
Would love to take a look and see if I can work on this if no one is. :smiley:
Cheers!

No time at the moment. Feel free to create a PR


Merge unit and instrumented test report in single file or directory of a multi-module Android project?

Hi, can someone help me how to merge unit and instrumented test across module/subproject for Android? Most solution I see in the internet is using JaCoCo. Which Kover Gradle task I should trigger and do I need extra configuration to achieve this? Thanks!
Sample structure

app [unitTest, androidTest]

libs

module1 [unitTest, androidTest]
module2 [unitTest]

Hi,
at the moment, running tests on the device is not supported yet. Work is in progress now.


README: update platform status

The Windows path is mature enough to support building swift-driver with swift-driver as the driver.  There is one remaining issue is a clang issue that was uncovered by the new driver.

@swift-ci please test


Automatically upload the latest nightly version of the docs

We have https://docs.ambient.run/nightly/ambient_api/index.html but I manually pushed up the docs there.
We should have this automatically pushed up for nightlies (and maybe stables, if we want to remove the docs.rs wait)

Done by @pierd in https://github.com/AmbientRun/Ambient/pull/1099 ❤


Setup

In the setup guide "The three different solutions can be found here", albeit there are only two solutions for import.

Thanks for flagging, added new version, should be resolved


License check support for pywin32

https://github.com/ansys/pyfluent/actions/runs/5716250370/job/15490116459#step:2:2601
https://github.com/ansys/pyfluent/actions/runs/5716166558/job/15489329795#step:2:2603
build-wheelhouse currently failing due to:
Invalid licenses found:

pywin32 306 has Python license

Was perhaps pypiwin32 a typo on the line below?
https://github.com/ansys/actions/blob/8ab872aa0a26d135eac38a7bf93fa4bf0bd92705/check-licenses/ignored-packages.txt#L3
Also, pypiwin32 seems to be a deprecated package (see https://pypi.org/project/pypiwin32/) compared to pywin32 (https://pypi.org/project/pywin32/)
Edit: pywin32 uses a "Python Software Foundation License":
 Name                                   Version     License
 pywin32                                306         Python Software Foundation License

Yep checking this first thing tomorrow morning. Thanks @raph-luc - also seen it in other repos


Abstract Update Case logic into separate service

Changes in this PR
Case Update logic was removed from the controller action and placed in a self-contained testable unit
Screenshots of UI changes
N/A (Nothing visual)
Next steps
N/A Merge PR (No next steps)

The definition of done would include updating the browser coverage in /spec/features/support/case_edit_spec.rb.
It might be desirable therefore to also redirect to the updated case.


connectSignals() not found

Sometimes when the GUI wallet is loaded there seems to be an issue with connectSignals.
This happens way too often on the Raspberry Pi and I believe it's due to it being called too soon when the JavaScript hasn't had a chance to do its magic.

https://github.com/shadowproject/shadow/blob/b4f701f5c5c01d8ea85d4e273e289ab486236ec8/src/qt/shadowgui.cpp#L313
I could either hackishly do this:
while(typeof connectSignals == undefined){};connectSignals();
Or we could wait for the GUI to load and then call connectSignals but I'm not sure if this is time sensitive?
@rynomster

We should wrap it in an on load. Initially it was in the page loaded, but
that causes a timing issue in the gui, as the page is loaded sometimes
before the models are available. I'll test a bit on the rpi this evening.
On Nov 28, 2016 02:33, "Kewde"<EMAIL_ADDRESS>wrote:

https://github.com/shadowproject/shadow/blob/
b4f701f5c5c01d8ea85d4e273e289ab486236ec8/src/qt/shadowgui.cpp#L313
I could either hackishly do this:
while(typeof connectSignals == undefined){};connectSignals();
Or we could wait for the GUI to load and then call connectSignals but I'm
not sure if this is time sensitive?
@rynomster https://github.com/rynomster
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shadowproject/shadow/issues/75#issuecomment-263159700,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGl7FVcjmAONz6ok7AnIaZOAgF9skfT2ks5rCiFEgaJpZM4K7M_w
.

I see, I suppose we will keep the trigger within the models but then wait for the body to load.
Looks easy enough.


Remove SapMonitor v20171103

The resource SapMonitor with version v20171103 was created during our private preview. SapMonitor is now is public preivew and using version v20200207; version v20171103 of SapMonitor is no longer used and will be deprecated soon. Removing SapMonitor resource from version v20171103.
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 commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run unifiedPipeline

Hi @PakDLiu Please fix the model validation issue first. And please get approval for your breaking change https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/342/FAQ-and-Recommendations

The breaking change has always been there, before this PR. Would I need to fix those even though it's on a different resource and has nothing to do with the PR?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@PakDLiu You are removing API from old stable version. Breaking change review is required.

/azp run automation - sdk


Replace pattern with enum to enforce singleton

As suggested by API reviewers, the enum validation produces a nicer
error message than patterns.
Tested by applying wrong names and got nicer message:
Unsupported value: "wconfig": supported values: "hierarchy"
Part of #868

/assign @adrianludwin
/assign @rjbez17

/lgtm
/approve
Out of interest, what was the error message before?

Out of interest, what was the error message before?

@adrianludwin Good question! Attaching both here:
The HierarchyConfiguration "wconfig" is invalid: metadata.name: Invalid value: "": metadata.name in body should match '^hierarchy$'

The HierarchyConfiguration "wconfig" is invalid: metadata.name: Unsupported value: "wconfig": supported values: "hierarchy"

Nice :)
On Fri, Jul 17, 2020 at 11:15 AM Yiqi Gao<EMAIL_ADDRESS>wrote:

Out of interest, what was the error message before?
@adrianludwin https://github.com/adrianludwin Good question! Attaching
both here:
The HierarchyConfiguration "wconfig" is invalid: metadata.name: Invalid value: "": metadata.name in body should match '^hierarchy$'
The HierarchyConfiguration "wconfig" is invalid: metadata.name: Unsupported value: "wconfig": supported values: "hierarchy"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/multi-tenancy/pull/903#issuecomment-660163397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE43PZFHBFRT7ILSUE7OPX3R4BTJZANCNFSM4O6JJQLA
.


Include original BSD license text

Thanks for your work on porting tinydir! However, I've noticed that tinydircpp.h no longer has the original BSD license text. Please include this text, specifically the lines here must be reproduced in the source code, as this is required by the license.

Done!

:+1: thanks!


Error getting Inventory Gsuite data

I'm trying to install and configure Forseti using all info provided from Forseti manual.
There's already some days I'm trying to create Inventory list but it still with PARTIAL_SUCCESS status. When I get an inventory detail it says:
"warnings": "GCP API Error: unable to get groups from GCP:\n<HttpError 403 when requesting https://www.googleapis.com/admin/directory/v1/groups?customer=XXXXXXXXXXX&alt=json returned "Not Authorized to access this resource/api">\n{\n "error": {\n  "errors": [\n   {\n    "domain": "global",\n    "reason": "forbidden",\n    "message": "Not Authorized to access this resource/api"\n   }\n  ],\n  "code": 403,\n  "message": "Not Authorized to access this resource/api"\n }\n}\n\n\nGCP API Error: unable to get users from GCP:\n<HttpError 403 when requesting https://www.googleapis.com/admin/directory/v1/users?customer=XXXXXXXXXXXX&viewType=admin_view&alt=json returned "Not Authorized to access this resource/api">\n{\n "error": {\n  "errors": [\n   {\n    "domain": "global",\n    "reason": "forbidden",\n    "message": "Not Authorized to access this resource/api"\n   }\n  ],\n  "code": 403,\n  "message": "Not Authorized to access this resource/api"\n }\n}\n\n\n",
"errors": ""
I already did what the FAQ says about this error and everything is as docs tell me to do. It looks like can't connect to Gsuite, but when I try it from the same API I get 200 code.
https://developers.google.com/apis-explorer/#search/v1 admin directory/m/admin/directory_v1/directory.groups.list?customer=XXXXXXXXX&domain=XXXXXXXX.com.br&_h=1&

Hi @Gribel.  Thank you for submitting this issue.  Using the API explorer is a good first step in diagnosing the issue.  In this case you likely invoked the API explorer as your user identity.  The Forseti Server calls the API as the Forsti Server service account.  This is a possible reason why you are seeing two different results.
I see that you've reviewed the documentation.  Can you please confirm for me the following.

The version of Forseti you have deployed.
You've enabled Domain Wide Delegation on the forseti-server service account.
In the GSuite admin console, you have added the API scopes to the client
The Client Name specified in the "Manage API client access" in the GSuite Admin Console is not the service account name but rather the DwD IAM Client ID from GCP IAM.

@Gribel Please respond to the previous comment when you get a chance so we can investigate this issue further. Thanks!

@Gribel Following up to see if you were able to follow the steps above and get this working.

@Gribel we have not heard back from you in 2+ weeks. Closing the issue for now. Please reopen and provide feedback regarding the steps provided by kevensen with his Aug 13 comment.


Remove misleading manpage and update README.md.

Remove misleading manpage.
Added a related projects section at the end.
Added blank line after header where missing.
Added extra blank line before header to make them easier to spot in plain-text mode.
Changed line-length for Contributing section, to make it more readable as plain-text.

Pkgcheck CI is failing...
Need to remove this from CMakeLists.txt
if(NOT SKIP_INSTALL_FILES AND NOT SKIP_INSTALL_ALL)
    install(FILES zlib.3 DESTINATION "${MAN_INSTALL_DIR}/man3" RENAME zlib${SUFFIX}.3)
endif()

@nmoinvaz Thanks, completely forgot to add that to the commit.

Configure nows seems to be failing as well..

Makefile.in.. just search for ".3" and you will see all the references.

Also need to remove zlib.3 from INDEX.md.

Configure:
# Cleanup these files if building outside source tree
    @if [ ! -f zlib.3 ]; then rm -f zlib.3.pdf Makefile; fi

I assume this checks for zlib.3 not existing to mean it is outside the source tree. We'll need a different file to check against, ideas? Maybe just check for deflate.c , or perhaps README.md?

I think README.md would work as a good check.

The point of the filename is that it only exists in root of zlib source tree, not in any other source tree or build directory.


Lambda@Edge construct

It's unclear to me if LLRT is able to run on Lambda@Edge yet, but a construct would be nice if/when available.

Hi @xhci, I guess we cannot use LLRT at the moment. because Lambda@Edge does not currently support provided.al2023 runtime (doc), which is required to use a custom runtime such as LLRT.

Hi @tmokmss - thanks for looking into this! I'll close the issue for now, but hopefully it's supported by AWS in the future.

I wondrered if we could use the wrapper script feature to use LLRT on Node.js managed runtime, but it was also impossible because Lambda@Edge does not support environment variables.


doesn't compile on Ubuntu

# make
clang++ -std=c++11 -O2 -o obj/io_service_pool.o src/io_service_pool.cpp -c -I
clang: error: argument to '-I' is missing (expected 1 value)
Makefile:22: recipe for target 'obj/io_service_pool.o' failed
make: *** [obj/io_service_pool.o] Error 1

Looks like the path to the boost library is not provided to the -I argument. Solution is to defined the BOOST_ROOT environment variable, or edit the Makefile to change the path.

thanks, I'll try this


Remove all .NET Framework dependencies

In 2024 .NET Framework is a thing of the past. We are on .NET Core now with NET 9 coming out soon and it's cross platform so this package needs to be able to run on Linux, etc. and not have dependencies that use .NET Framework such as the FubarCoder packages in use. This is a blocker and is breaking integrations. We need an update ASAP please.

easy there...  i'm still using .net framework 4.6.2.

.NET Standard is the better choice than .NET Framework.

I have reached out the brevo support about their plans with the C# SDK. I haven't heard back from them. Does anybody know if they plan to maintain and / or further develop it?

I've also reached out to Brevo support and am waiting for their response. Despite the development time it might take, I believe it’s safer to create our own C# library by wrapping the CURL API.

You can just generate your own client using a code generator. I personally use openapitools/openapi-generator.
For example:
docker run --rm -v ".:/local" openapitools/openapi-generator-cli generate -i https://api.brevo.com/v3/swagger_definition.yml -g csharp -o /local/Brevo.Api -p packageName=Brevo.Api
This will generate pretty much the same code as this repo but with much moire up to date references.
See here for config options


Website is down

As the title says. I was excited to see that someone had taken over, but now the new website/documentation seem just as dead as the old one :(

Hello @Aeolun
We at Commandprompt Inc. have forked Omnidb and actively working on its development. The new name of project is PgManage, feel free to check it out:
https://github.com/commandprompt/pgmanage/releases
https://pgmanage.readthedocs.io/
Bug reports, feature requests and any other feedback is appreciated!


Proposal: Replace numerical values in examples with preprocessor macros from ch32v003fun.h

I notice that most of the examples ignore #defined values from the header file, in favour of simply using a number; example:
GPIOC->CFGLR &= ~(0xf<<(4*1));
instead of
GPIOC->CFGLR &= ~(0xf<<(4*GPIO_PinSource1));
where this already exists in the header:
ch32v003fun/ch32v003fun.h:3428:#define GPIO_PinSource1                ((uint8_t)0x01)
Or:
ADC1->SAMPTR2 |= 7<<(3*7);	// 0:7 => 3/9/15/30/43/57/73/241 cycles
instead of
ADC1->SAMPTR2 |= ( ADC_SampleTime_241Cycles << (3 * ADC_Channel_7 ) );	// 0:7 => 3/9/15/30/43/57/73/241 cycles
My asks:
I feel like using the macros makes for more easily understood code, and that (for the purposes of 'canonical' examples), this is a desirable thing. Does anyone else feel like this is a useful thing? and if so:

I propose the creation of a 'style guide' for examples and contributions, stressing the use (where possible) of macros instead of digits
I'm not much of a coder, but I can start grooming the existing examples when I have time and motivation, and opening up PRs. Would this be acceptable?

I spend a lot of time with grep-ing for structures and macros that I can use wherever possible. At least they follow a somewhat predictable and consistent naming convention.
grep -rin adc ch32v003fun/*
I'll start prettying up a few of the examples when I get some time. Maybe I'll write a script to semi-automate things.
Thanks.

consts/defines are usually nice - as long as they don't cause confusion when trying to make heads or tails of they code you're reading and at the same time looking at the datasheet. Compare the defines here with the names of the corresponding bits in the datasheet.
I had to hover over them in the code to get the popup with their hex values, and then matching the hex value to the bit-number in the dox so I could see the description.
I mean - how is even CR_OPTPG_Set close to OBER - that is the real name from the datasheet?
#define CR_PAGE_ER                 ((uint32_t)0x00020000)
#define CR_PAGE_PG                 ((uint32_t)0x00010000)
#define CR_OPTER_Set               ((uint32_t)0x00000020)
#define CR_OPTPG_Set               ((uint32_t)0x00000010)

We are poised to make some of these decisions.  In general I have gone in the direction of more permissive instead of more constrained regarding style.  I.e. where constants in place make sense, just use them, but keep the things from the EVT available for anyone copy-pasting code.
I am also frustrated by the tire fire that the flash system definitions are :(.  The reference manual is missing an entire register :(


Create java data tests

Have I forgot to add some exceptions? I have no idea what are those big changes in "Change tests names".... i just replaced 2 lines.


Add BazelTestEngine for arcanist [phab:D250]

Created by schroederc at 2015-05-14 17:32:31:
This change only adds the engine.  It doesn't make arcanist use it yet.
To do so, replace "CampfireTestEngine" in .arcconfig with
"BazelTestEngine".
The main difference between the engines is that the new engine does not
list non-test targets in the test results.  They are, however, built
during testing and a failure to build them will throw an exception.

schroederc wrote at 2015-05-14 17:34:20:
Add newlines

schroederc closed via commit ee04cb59f583f83182b56989b832978b68facd00 at 2015-05-14 18:34:56


Split API and Ingester into separate Kubernetes deployments

This will make this service a bit more reliable (as one failing won't cause the other to fail) & let us adjust resource allocation more granularly.

Done


dbca not found error in Oracle 12c ee

/scratch/kg>docker run --name orcldb -p 1521:1521 -p 5500:5500 -e ORACLE_SID=orcl -e ORACLE_PDB=ORCLIDM -e ORACLE_PWD=Welcome1 -e ORACLE_CHARACTERSET=AL32UTF8 -v /scratch/dockerdb:/opt/oracle/oradata oracle/database:<IP_ADDRESS>-ee
ORACLE PASSWORD FOR SYS, SYSTEM AND PDBADMIN: Welcome1

LSNRCTL for Linux: Version <IP_ADDRESS>.0 - Production on 27-SEP-2017 19:54:24

Copyright (c) 1991, 2014, Oracle.  All rights reserved.

Starting /opt/oracle/product/<IP_ADDRESS>/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
System parameter file is /opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/listener.ora
Log messages written to /opt/oracle/diag/tnslsnr/4bf347f91753/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
Start Date                27-SEP-2017 19:54:24
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/listener.ora
Listener Log File         /opt/oracle/diag/tnslsnr/4bf347f91753/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))
The listener supports no services
The command completed successfully
Look at the log file "/opt/oracle/cfgtoollogs/dbca/orcl.log" for further details.
cat: /opt/oracle/cfgtoollogs/dbca/orcl/orcl.log: No such file or directory
Database Configuration Assistant failed to detect options for this Oracle Installation.
There is an error in creating the following process:
/opt/oracle/product/<IP_ADDRESS>/dbhome_1/bin/sqlplus -S -N /NOLOG
The error is:
Error 46 initializing SQL*Plus
HTTP proxy setting has incorrect value
SP2-1502: The HTTP proxy server specified by http_proxy is not accessible

Due to this failure some Database Configuration Assistant features will not be available. Do you want to continue?

Unique database identifier check passed.

/opt/oracle/oradata/ has enough space. Required space is 7665 MB , available space is 98009 MB.
/ has enough space. Required space is 0 MB , available space is 10255 MB.
File Validations Successful.
Cannot create directory "/opt/oracle/oradata/fast_recovery_area".
Error 46 initializing SQL*Plus
HTTP proxy setting has incorrect value
SP2-1502: The HTTP proxy server specified by http_proxy is not accessible
mkdir: cannot create directory '/opt/oracle/oradata/dbconfig': Permission denied
mv: cannot stat '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/dbs/spfileorcl.ora': No such file or directory
mv: cannot stat '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/dbs/orapworcl': No such file or directory
mv: cannot move '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/sqlnet.ora' to '/opt/oracle/oradata/dbconfig/orcl/': No such file or directory
mv: cannot move '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/listener.ora' to '/opt/oracle/oradata/dbconfig/orcl/': No such file or directory
mv: cannot move '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/tnsnames.ora' to '/opt/oracle/oradata/dbconfig/orcl/': No such file or directory
cp: cannot create regular file '/opt/oracle/oradata/dbconfig/orcl/': No such file or directory
ln: failed to create symbolic link '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/sqlnet.ora': File exists
ln: failed to create symbolic link '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/listener.ora': File exists
ln: failed to create symbolic link '/opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/tnsnames.ora': File exists
cp: cannot stat '/opt/oracle/oradata/dbconfig/orcl/oratab': No such file or directory
Error 46 initializing SQL*Plus
HTTP proxy setting has incorrect value
SP2-1502: The HTTP proxy server specified by http_proxy is not accessible
#####################################
########### E R R O R ###############
DATABASE SETUP WAS NOT SUCCESSFUL!
Please check output for further info!
########### E R R O R ###############
#####################################
The following output is now a tail of the alert.log:
tail: cannot open '/opt/oracle/diag/rdbms/*/*/trace/alert*.log' for reading: No such file or directory
tail: no files remaining

Hi @krishnagkashyap, your install fails because of the following error:
There is an error in creating the following process:
/opt/oracle/product/<IP_ADDRESS>/dbhome_1/bin/sqlplus -S -N /NOLOG
The error is:
Error 46 initializing SQL*Plus
HTTP proxy setting has incorrect value
SP2-1502: The HTTP proxy server specified by http_proxy is not accessible

Closed due to lack of response.


[distributed] add batch decoding

This PR:

enables batch decoding such that multiple prompts can be run and processed at the same time.
moves the dst/src calcs for pp comms out of the decoding loop
updates final display to show each respective prompt and result.

If pp_degree = 1, the change in this PR would cause prompt_length to be incremented twice per iteration.
That's why in PR #1149 I consolidated the increments in one place.


Null Reference Exception when creating a new Flare Asset

Hey I'm using Unity 2020.2.6f1. If you import your project and run the Sample scene, everything works fine. But as soon as you create some new Flare Assets and set them up in a new scene a bunch of null reference exceptions start happening and the flare doesn't work.

I thought that you didn't set a flare asset to flare launcher or you just set an empty flare asset with no texture to a launcher.
These two situations will sure cause null reference exceptions.
I wonder if you can reply some screen shot so that I can find the question more clearly.

So here is a snapshot of the issue. I create a new flare asset (image in 'Resources/Lensflare'), then assign the necessary scripts to both my scenes light source (URPLensFlareLauncher - with the new lens flare asset attached), and my scene camera (URPLensFlare - with the LensFlare material). Then when I run it, the new lens flare asset I created gets wiped clean/reset (see pic related). However, if I use the Lens Flare Asset you provide in the example folder this never happens.

So here is a snapshot of the issue. I create a new flare asset (image in 'Resources/Lensflare'), then assign the necessary scripts to both my scenes light source (URPLensFlareLauncher - with the new lens flare asset attached), and my scene camera (URPLensFlare - with the LensFlare material). Then when I run it, the new lens flare asset I created gets wiped clean/reset (see pic related). However, if I use the Lens Flare Asset you provide in the example folder this never happens.

Please choose a texture to this asset and add at least one flare block to it, or the launcher can't find any data in flare asset

@Reguluz I'm not sure I was clear enough. The URPFlareAsset Scriptable Object gets reset whenever the game exits play mode or when you save the unity editor.
For instance, I create a fully loaded Flare Asset (pic related):

Then I assign it to my in-game URP Flare Launcher. Then I press play.
When I exit play mode, the URPFlareAsset now looks like this:

So I deleted the URPFlareLauncher +and URPLensFlare scripts, so that just the URPFlareAsset and URPFlareAssetEditor scripts were left. Same thing occurs, when you create a new URPFlareAsset and fill it out with an image and make some field + setting, then you hit play, exit play, the new URPFlareAsset is all reset. So I think in Unity 2020.2 that your editor script is reseting the Scriptable object somehow.

t

@Reguluz I'm not sure I was clear enough. The URPFlareAsset Scriptable Object gets reset whenever the game exits play mode or when you save the unity editor.
For instance, I create a fully loaded Flare Asset (pic related):

Then I assign it to my in-game URP Flare Launcher. Then I press play.
When I exit play mode, the URPFlareAsset now looks like this:

That's so weired. I'll soon check it out. I'm so sorry about that.

So I deleted the URPFlareLauncher +and URPLensFlare scripts, so that just the URPFlareAsset and URPFlareAssetEditor scripts were left. Same thing occurs, when you create a new URPFlareAsset and fill it out with an image and make some field + setting, then you hit play, exit play, the new URPFlareAsset is all reset. So I think in Unity 2020.2 that your editor script is reseting the Scriptable object somehow.

I wonder which version did you use. Did you download the repository or just use the unitypackage I have released?

Hey Reguluz, sorry for the slow response (got distracted by my day job). I downloaded this repo (master) branch. I will check out the unity package!


board.Refresh() generate an TypeInitializationException for 'Manatee.Trello.Json.DefaultJsonSerializer'

Hello
I restarted my application since 2020, and I have now an error when executing this code:
_factory = new TrelloFactory();
_board = _factory.Board(TodoBoardId);
AsyncHelper.RunSync(() => _board.Refresh());

I get the following exception at : _board.Refresh()
System.TypeInitializationException : Une exception a été levée par l'initialiseur de type pour 'Manatee.Trello.Json.DefaultJsonSerializer'.
   at Manatee.Trello.Internal.DataAccess.JsonRepository.ValidateResponse(IRestResponse response)
   at Manatee.Trello.Internal.DataAccess.JsonRepository.<ProcessRequest>d__7`1.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Manatee.Trello.Internal.DataAccess.JsonRepository.<Execute>d__1`1.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Manatee.Trello.Internal.Synchronization.SynchronizationContext`1.<GetData>d__16.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Manatee.Trello.Internal.Synchronization.DeletableSynchronizationContext`1.<GetData>d__7.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Manatee.Trello.Internal.Synchronization.SynchronizationContext`1.<GetBasicData>d__20.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Manatee.Trello.Internal.Synchronization.SynchronizationContext.<Synchronize>d__22.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at TimeTracking.AsyncHelper.RunSync(Func`1 func) in C:\Users\EFD3\source\repos\TimeTracking\TimeTracking\AsyncHelper.cs:line 25
   at TimeTracking.Trello.TrelloService..ctor() in C:\Users\EFD3\source\repos\TimeTracking\TimeTracking\Trello\TrelloService.cs:line 47
   at TimeTracking.Main.<InitializeServices>b__5_0() in C:\Users\EFD3\source\repos\TimeTracking\TimeTracking\Main.cs:line 65
   at TimeTracking.Main.loadingBackgroundWorker_DoWork(Object sender, DoWorkEventArgs e) in C:\Users\EFD3\source\repos\TimeTracking\TimeTracking\Main.cs:line 152

I have the following NuGet packages installed
Manatee.Trello	: 4.1.1
Manatee.Json	: 12.0.2
I don't know if it is a change at Trello level.
My app was working well in 2019, end of December.
I don't know if there is a link...
I can provide you an extract of my application if you want.
Best regards

Thanks for reporting.
Two additional things would help greatly:

any inner exceptions
the data that Trello is returning

If you like you can DM me on Slack or email me.

All of my tests are passing, so it's not a global issue.  Please let me know what additional details you can find.

Did you recently update Manatee.Json?

Yeah, that's it. I haven't updated Manatee.Trello to use v12 of Manatee.Json yet.  You'll need to downgrade to v11.

Hello and sorry for late response, time zone difference.
Thank a lot for your investigation, it successfully solve my problem.
I forgotten I had made an upgrade of Manatee.Json...
Thank again for your work on those libs
Have a nice new year.
Bye


S3E5 meeting minutes have problem to show the PDF files.

Separated from #358
@fuyunfuyun666 @CyFeng16 The reason of the PDFs in S3E5 can not be displayed is not related to this deploy issue.
It's because the URL of the PDF is not right. @gaojiuy had made the same mistakes as the @ArronHZG before: use the Github file url(wrong) instead of it's AMC URL(right).
From https://github.com/BUPT/ai-ml.club/blob/master/docs/_posts/2019-09-08-seminar-meeting-minutes-3-5.md:
高久怡 @gaojiuy

分享了论文Axiomatic Attribution for Deep Networks and Saliency Maps

![高久怡]({{ '/assets/2019/seminar-3-5/seminar-3-5-talk-gaojiuy.jpg'| relative_url }})

<iframe src='{{ '/assets/js/viewer-js/#https://github.com/BUPT/ai-ml.club/blob/master/docs/assets/2019/seminar-3-5/seminar-3-5-integrad.pdf' | relative_url }}' width='560' height='315' allowfullscreen webkitallowfullscreen frameborder="0" style=" position: absolute; top:0; left:0; width:100%; height:100%; " ></iframe>

It should be fixed as I demonstrated from the blowing DIFF.
- /assets/js/viewer-js/#https://github.com/BUPT/ai-ml.club/blob/master/docs/assets/2019/seminar-3-5/seminar-3-5-integrad.pdf
+ /assets/js/viewer-js/#/assets/2019/seminar-3-5/seminar-3-5-integrad.pdf'

Is there anyone who wants to help @gaojiuy to send a PR to fix it?

S3E5 meetings' pdf are good to go now, thanks for @gaojiuy effort!

Great.
I'd like to suggest that we should reference the ISSUE in our PR so that we can connect everything together. (which I had just modified the PR of @gaojiuy


Add QSIPrep 0.14.2

Adds QSIPrep 0.14.2, closes #60

eh, thank you ! I wish it was this simple... due to singularity-hub going readonly and we are hosting only older images, I need to adjust my mighty bash prototype script to also build those images "locally" instead of relying to singularity-hub -- I am hosting/providing them all (including singularity-hub archive) anyways from datasets.datalad.org... will try to accomplish that tune up today.
"good news" is that qsiprep 0.14.2 listed on http://bids-apps.neuroimaging.io/apps/ so the script should automagically handle it and no such PR would be needed

Ok, this is very good to know! We're also using fmriprep 20.2.3, will your next run also add that image?

both should be in, please check if usable ;-)

FWIW -- all bids-apps updated, and job is now a cron job so they should stay updated ;-) let's see how that goes


On which branch to fix Spelling Errors

Title is topic. As you might have seen I have fixed standart in a few places, creating pull-requests all over the place. This wasn't very thought through, so I stopped after the third or fourth PR.
I noticed I pushed one to master and one to develop. While no real issue by itself, it might in a rare occurence disturb Gits workflow (no expert, just imagining the worst).
So my question: On which of those two branches is a direct file-edit from the GitHub-Website best made?
In my personal fork of the BrainSimulator-Repository I think I now found out how to not spam PRs but instead create a single big one, but I do not always have easy access to it (for example on other computers).

Please wait for the next source release (it will probably be this month), and base your fixes there. Please put all related documentation fixes in one branch based on the master branch.
GitHub website edits are not the best, but the commits can be cherry-picked when necessary.


Export of multiple dashboards at once fails the first time

If the dashboards are not created in sequential order they will fail.  I attempted to create 4 dashboards at once.
wizzy export datasources
Output:
{
  "id": 1,
  "message": "Datasource added"
}
✔ Datasource export successful.
Output:
Grafana API response status code = 500
No error body from Grafana API.
✘ Datasource export failed.
Output:
Grafana API response status code = 500
No error body from Grafana API.
✘ Datasource export failed.
Output:
{
  "id": 2,
  "message": "Datasource added"
}
✔ Datasource export successful.

The issue is - https://github.com/go-xorm/xorm/issues/161
And if you see grafana server logs, you must see the following:
EROR[12-20|09:36:40] Request Completed                        logger=context userId=1 orgId=1 uname=admin method=PUT path=/api/datasources/7 status=500 remote_addr=<IP_ADDRESS> time_ms=39ns size=41

This should be fixed now!


Replacing cssom with mensch (because conversion to object model loses important stuff)

For mosaico I'm evaluating a "browser-side" css inliner. I did a lot of evaluation of existing tools (i'm writing a blog post too).
Now, given I need to do that in javascript and in the client my best option is Juice. The main issues with Juice are related to CSSOM: CSSOM loses many informations from the CSS so prevent Juice to do the "right thing".
I found specific use-case issues that have already been reported:
https://github.com/Automattic/juice/issues/205
https://github.com/Automattic/juice/issues/27
Now I've just forked juice and I'll try replacing cssom with mensch (a CSS parser we already happily use in mosaico because it preserve multiple properties, it preserve comments and let us manipulate the CSS preserving the formatting and most things we may not understand).
With regard to "multiple property declarations" (ofen used for flex or linear-gradient, but also used for rgba... like "color: #ccc; color: rgba(128,128,128,.8)" my plan was to do something similar to styliner and inline multiple values only when they are declared in the same "declaration group" (same rule). This keeps the inlined code "small" but most time it will do what the user expects.
Another thing I'd like to do is be able to use jquery instead of cheerio, so that I don't need to bring cheerio (and its dependencies) on the client  (we already do this in mosaico, running cheerio in the backend but jquery in the browser). This needs some abstraction in the library but it worked in mosaico.
I know this is a major change, so I wanted to introduce this ASAP (I still have to put my hands in the code). What do you think? Is juice interested in similar changes? Should I try to work with PR in mind, or should I simply fork and forget?

There are a few open issues that are related to CSSOM, such as you pointed out, that I'd like to see resolved. Replacement with Mensch or something else would be really interesting to me.
I'm not opposed to the jQuery/Cheerio change, but the current API exposes Cheerio directly, so that might require some thought about either changes to the API or making some reasonable assurance that jQuery and Cheerio behave the same - though it sounds like maybe you've already done that on your other project.
In any case, the current dependencies are clearly causing some issues and if you'd like to try and resolve them, please open a PR.

I just complete my first run replacing "cssom" with "mensch".
Tests are passing but the one that checks the cssom object structure result (of course) and those checking the "PreservedContents" because using mensch I keep the formatting of "preserved contents" AS IS, and I don't need to "rebuild" it, so the formatting is different but the content is the same (I also have been able to remove some code from juice because I don't need to understand @media e @font-face content in order to preserve them) . Is this OK or you would prefer to reformat that "preserved content" to mimic the CSSOM behaviour?
Also, with mensch it would be easy to keep @supports, @keyframes, @import and other @at-rules not being currenlty preserved... shouldn't we preserve anything we don't understand instead of selectively keep @media and @font-face ?
While I wait for your opinions about this I'll start to dig in the "client.js" logic because I can't use key=>value when I want multiple occourences of key to be supported.

I don't feel a need to mimic the CSSOM behavior unless the breaking changes there would cause users really legitimate problems, mainly, loss of features they rely on currently.
With the @ rules, historically, there have been a lot of requests to preserve certain parts of CSS and get rid of others in order to have the most efficiently sized output. I think the most reasonable default is to preserve all of them. I'm not totally convinced what the best options are on top of that default, but if you can remove the current @ options and just include a preserveAtRules options that defaults to true I feel like that would cover any use cases I'd be interested in.

#220 merged, cool! So this one, #44, #74 and #216 can be closed too.
I'll open new issues for my next steps as soon as I'll have something to say ;-)


Refactoring: Prefix URLs pointing to the backend

Describe the bug
The server side rendered frontend serves our images at /api/uploads. All requests to /api are proxied to the backend, which serves images at /uploads/. Right now, the backend mutates all URLs in the response to be prefixed with /api. This is a design flaw as the backend knows how the frontend proxies requests.
Expected behavior
We should prefix all <img src="URL"> urls in the frontend with /api so the backend does not need to do it for the frontend.
Screenshots

@roschaefer having a look at this issue - in the seeded data all the images associated with posts are from the https://lorempixel.com site (presumably from the faker module) - we couldn't find any in the seeded data that have urls like /api/uploads, or /uploads or anything.
Looking at the alpha system we did see URLs like this:
https://img-alpha.human-connection.org/3wFqNObuo-R9WQINClzV-8Cw17g=/243x100/smart/filters:blur(30):background_color(fff)/https://api-alpha.human-connection.org/uploads/teaserImg_59970fe0-3f95-11e9-b57e-39c2729f39e9.jpeg
Is this issue not one that specifically concerns the situation when a user uploads a new image through the system?  that functionality is not yet present in the new system, so difficult for us to test perhaps?
Perhaps this is something we could examine more easily if we were importing the alpha data into the new system?

@tansaku did you take a look 👀 on the badges? They are coming from the api.

@appinteractive we did not - the example shows image posts so that's where we focused our attention, but that's a good tip - thanks :-)

@tansaku the image paths of the seeds in the backend are fine BUT on their way out, the backend middleware adds a prefix /api/ to all strings that look like a url. That's the ~problem~ the code smell (violation of the law of demeter).
Here's the middleware:
https://github.com/Human-Connection/Nitro-Backend/blob/master/src/middleware/fixImageUrlsMiddleware.js
Here's the test:
https://github.com/Human-Connection/Nitro-Backend/blob/master/src/middleware/fixImageUrlsMiddleware.spec.js#L14
The returned string of the backend should be the same except the unnecessary prefix.
The responsibility of the frontend is to add the prefix /api to all image tags that get their url from the backend. The frontend knows the endpoint that is proxied to the backend here thus it should be responsible for adding these prefixes.

Literally every string that contains one of the legacy urls is substituted with /api. It should be substituted with empty string.

thanks @roschaefer - I think we understand all that - the problem is that we don't see any urls of that form when we run the system locally, and we can't upload images to test.  The issue is we want to be able to see that the fix we make has actually worked.   Did you upload the original screenshot?  Was that with imported data?
Anyway, perhaps we can do as @appinteractive suggests and look at badges to find an example of the rewriting taking place ...

Ah! I'm so driven by test-driven development that I forgot one might also want to try out the software. Excuse my ignorance, yes, I confirm @appinteractive that the only occurence I know of are the .svg files of the badges.
Just double-checked and there seems to be more images.

You can see the badges coming from the api. You can find the .svg files in the /uploads folder.
@tansaku do you like getting distracted? More problems:

The /uploads folder does not get deployed along with the backend. Therefore we get 404 for every badge on all our kubernetes deployments.
The backend cannot be scaled horizontally. If backend reads files from disk, e.g. the /uploads folder, then we need a kubernetes volume. Digital Ocean does not support multi-stage access on volumes. Hence, only one pod can claim a persistent volume at a time and we're not able to scale the backend. Solution: Don't let the backend do the /uploads.


New sample json column formatting: blurred field

Q
A

Bug fix?
no

New sample?
yes

Related issues?
N/A

What's in this Pull Request?
New sample I use quite often when doing demos. It may be useful for other people.

Thanks for the awesome sample @JulienVLC 🤩🤩✨
There are times when I do a demo and think, "Oh, I don't want to show this data...". That's when I will try to use this sample!

If you are interested, please register for the following program. When you register, you will get a digital badge!
M365 Platform & Power Platform Community Recognition Program
※Even if you register, it will not be distributed immediately. It will take some time before it is distributed.

Great! Thank you @tecchan1107 !


fix k8s policy-only toleration for master node

Description
The daemonset doesn't apply to the master node and hence the master node network doesn't become ready when these two values aren't present - at least in my testing on a 1.7.5 and 1.8.0 cluster.
These values seem to be missing on previous versions and in different places, so might want or need to retrofit the yaml files for different installation options.  Just initiating this PR to get the conversation started.

 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.

According to the k8s docs, the operator defaults to Equal if not specified. So specifying it looks fine to me.
For the value, kubeadm sets it to an empty string. I think that is the default as well.
Can you dump kubectl get nodes -o yaml so I can take a look at the taint on your cluster? That will help determine the taints that exist in ACS.

FWIW this is what exists on the latest kubeadm:
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master
    timeAdded: null

That's also what I understood the convention to be.

yes, I believe the problem is when you deploy a K8s cluster not using kubeadm the value does not get set.

Thank you for pointing this issue out @dtzar and having a go at a fix.
What is the next step for this PR? I'm thinking this one should be closed as I think the fix should be to document that the tolerations in the manifests need to match the taints on the master, with perhaps a note that the manifests were written using kubeadm.  Actually even if we merge this PR we should document that requirement, see #1164.

I don't believe this PR is a toleration/taints problem with the specific cluster deployment, although I agree with implementing your 1164 because it might be a problem for some deployments.
I believe the solution should be to simply modify the places where the tolerations are present to have at least the value: "true" field present or both lines (in the event that there actually is a problem with the Operator: Equal isn't actually the default or take effect for whatever the reason with K8s).

I just wanted to follow up, though I'm assuming since you closed the PR @dtzar that maybe you tested or reconsidered the taints and tolerations. I setup a k8s v1.8 cluster, deployed with kubeadm, and tried installing https://docs.projectcalico.org/v2.6/getting-started/kubernetes/installation/hosted/kubernetes-datastore/calico-networking/1.7/calico.yaml though with the addition of operator and value as had been suggested and my calico-node pod was not deployed to my master, after removing those and applying my manifest then it was deployed to my master.

I think I found out why it was this way for ACS-Engine.. Due to this taint put on the master node:
    taints:
    - effect: NoSchedule
      key: node-role.kubernetes.io/master
      timeAdded: null
      value: "true"


"Alerts" does not appear as a selection in the side menu.

[Enter feedback here]

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

ID: b667465c-46d2-f1b1-97fa-6fd23c65a534
Version Independent ID: 72635a60-157d-d3dc-8b9e-db90ada90bba
Content: Filter and manage alerts from the Alerts page - Azure Defender for IoT
Content Source: articles/defender-for-iot/organizations/how-to-view-alerts.md
Service: defender-for-iot
GitHub Login: @shhazam-ms
Microsoft Alias: shhazam

Hi Vincel, Thanks so much for writing.
Can you provide more info on this? I see the Alert in the side menu?

Sorry, my mistake.
We are new users of Azure Sentinel.
In following links to help with “Alerts” we somehow landed on a “Defender for IoT” help page.
Please ignore my request for assistance with finding the “Alerts” link/button.
Thanks

On Jul 25, 2021, at 7:47 AM, shhazam-ms @.***> wrote:
Hi Vincel, Thanks so much for writing.
Can you provide more info on this? I see the Alert in the side menu?
https://user-images.githubusercontent.com/73219914/126897868-97248d6e-fd94-490e-bda9-3273e1f49ddc.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-docs/issues/78806#issuecomment-886189757, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMCULAD43SVA22GQ55I22TTZP2UNANCNFSM5A6ORLIQ.

Thanks for getting back to me. All the very best


[SPARK-41899][CONNECT][PYTHON] createDataFrame should respect user provided DDL schema

What changes were proposed in this pull request?
Make createDataFrame respect user provided DDL schema
Why are the changes needed?
consistency
Does this PR introduce any user-facing change?
yes
How was this patch tested?
added UT and enabled tests

merged into master
thank you @HyukjinKwon