TextField isn't usable with Flutter 2.8.0 beta on iPhone 15 simulator

TextField isn't usable on the iOS 15 iPhone simulator with Flutter beta 2.8.0-3.2.pre.
Steps to Reproduce
Running the following code on an iOS 15 iPhone simulator results in a an unusable TextField.
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  final _controller = TextEditingController();
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(primarySwatch: Colors.blue),
      home: Scaffold(
        body: Padding(
          padding: const EdgeInsets.symmetric(horizontal: 16),
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            crossAxisAlignment: CrossAxisAlignment.start,
            children: [
              const Text('Please enter a thing:'),
              TextField(controller: _controller),
            ],
          ),
        ),
      ),
    );
  }
}

Logs
Version
$ flutter --version
Flutter 2.8.0-3.2.pre • channel beta • https://github.com/flutter/flutter
Framework • revision 2901cd7208 (5 days ago) • 2021-11-18 11:15:09 -0800
Engine • revision bcc2b7f12c
Tools • Dart 2.15.0 (build 2.15.0-268.18.beta)

Flutter doctor
$ flutter doctor -v
[✓] Flutter (Channel beta, 2.8.0-3.2.pre, on macOS 12.1 21C5031d darwin-x64, locale en)
    • Flutter version 2.8.0-3.2.pre at /Users/brettmorgan/flutter
    • Upstream repository https://github.com/flutter/flutter
    • Framework revision 2901cd7208 (5 days ago), 2021-11-18 11:15:09 -0800
    • Engine revision bcc2b7f12c
    • Dart version 2.15.0 (build 2.15.0-268.18.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/brettmorgan/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • 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-7281165)

[✓] VS Code (version 1.62.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (3 available)
    • iPhone 8 (mobile) • EFDF3255-2EA1-4762-92A7-A1A4712A9950 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-0 (simulator)
    • macOS (desktop)   • macos                                • darwin-x64     • macOS 12.1 21C5031d darwin-x64
    • Chrome (web)      • chrome                               • web-javascript • Google Chrome 96.0.4664.55

• No issues found!

FYI @csells

CC @LongCatIsLooong

@HansMuller @LongCatIsLooong
Descroiption
This looks like an issue input from the raw keyboard. The issue can be reproduced on a physical or simulator when using the physical keyboard instead of the soft keyboard.
25th Oct
Initial regression was introduced in https://github.com/flutter/flutter/pull/92441, which includes an Engine PR https://github.com/flutter/engine/pull/29108 related to iOS input

Good commit
Regression commit

https://github.com/flutter/flutter/commit/1daae0b0ae0e819019100415e53e574e5d154dbd
https://github.com/flutter/flutter/commit/6434f8e84accdda85c9f507f93b01ddb95caebc3

21 days ago
Then the issue persisted until it was fixed late from a PR https://github.com/flutter/engine/pull/29464 in another engine https://github.com/flutter/flutter/pull/92977

Bug commit
Fix commit

https://github.com/flutter/flutter/commit/607d7934c728afef9a6cc8d329b6f50b3c479466
https://github.com/flutter/flutter/commit/136592ae79e7ed5dee251e712b2f37a6bd10b8ae

https://github.com/flutter/engine/pull/29464 was the fix. It should be relatively safe to cherrypick and the pull request only removes code.

@HansMuller (and @LongCatIsLooong); when was this regression introduced? What's the impact of not taking it for stable? We have a very high bar for this week - can you talk about taking it now vs. delaying to consider it for a batch or cherry picks after the stable release?

The regression was introduced in flutter/engine#29108. It prevents iOS hardware keyboard events from being properly sent to flutter text input fields, I'd expect it will affect these: people

developers that use a simulator to debug their apps (there's an easy workaround, you can choose to use the onscreen keyboard in the simulator, but it's still going to be an annoyance).
actual users that connect a hardware keyboard to their ipads. It's a definitely not the best user experience if they're forced to use the onscreen keyboard instead, and developers would have to find a way to tell them about this workaround.

The patch itself should be relatively safe. flutter/engine#29108 replaced a quirk in the ios text input plugin with a proper implementation, but there was a workaround for that quirk in the code that wasn't removed at the time. The fix simply removed that and the code changes only affect hardware keyboard events handling (which wasn't working prior to the fix so it almost can't be worse unless the fix would introduce a crash. I've been using ios simulator for debugging flutter apps since then and haven't seen anything strange so far).

This is no longer reproducible on stable 2.8.1 or master, 2.9.0-1.0.pre.93, TextField works with both physical and virtual keyboard on ios 15.
https://user-images.githubusercontent.com/31410839/147068226-883bf9bb-5e28-4633-9326-c4b35dc222b0.mov

flutter doctor -v
[✓] Flutter (Channel stable, 2.8.1, on macOS 12.1 21C52 darwin-arm, locale en-GB)
    • Flutter version 2.8.1 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (6 days ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • 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.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 60.1.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.61.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.29.0

[✓] Connected device (3 available)
    • iPhone 8 (mobile) • A55680BB-E46F-425E-B803-ACB8DEA8A239 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-15-0 (simulator)
    • macOS (desktop)   • macos                                • darwin-arm64   • macOS 12.1 21C52 darwin-arm
    • Chrome (web)      • chrome                               • web-javascript • Google Chrome 96.0.4664.110

• No issues found!

[✓] Flutter (Channel master, 2.9.0-1.0.pre.93, on macOS 12.1 21C52 darwin-arm, locale en-GB)
    • Flutter version 2.9.0-1.0.pre.93 at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1be7f1ea56 (7 days ago), 2021-12-14 22:14:07 -0500
    • Engine revision e444009bf4
    • Dart version 2.16.0 (build 2.16.0-109.0.dev)
    • DevTools version 2.9.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • 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.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 60.1.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.61.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.29.0

[✓] Connected device (3 available)
    • iPhone 8 (mobile) • A55680BB-E46F-425E-B803-ACB8DEA8A239 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-15-0 (simulator)
    • macOS (desktop)   • macos                                • darwin-arm64   • macOS 12.1 21C52 darwin-arm
    • Chrome (web)      • chrome                               • web-javascript • Google Chrome 96.0.4664.110

• No issues found!

Closing as fixed.


inpainting mode

Add a tab or checkbox in img2img for inpainting mode.
This will need a way to draw or upload the mask.
Params:

mask image
edge blur radius, pixels

This is mostly implemented with a mask painting component, but still needs two separate file upload fields.

when the source image changes, and a mask image has been set, do not modify the canvas
when the source image changes, and a mask image has not been set, copy the source to the canvas
when the mask image changes, copy the mask image to the canvas

Mostly done, with blurred/soft brushes deferred until https://github.com/ssube/onnx-web/issues/30


Completing partial feasible solutions

I'm working on a model with binary variables X[i] and Y[j]. The model has the following property: if the values of X[1] , ... , X[I] for some feasible solution are given, then the values of Y[j] completing that feasible solution are uniquely determined and can be efficiently computed.
The model is taking too long because I'm not exploiting the aforementioned property. I want to help SCIP to find feasible solutions by informing the values of Y[j] once the values of X[i] have been fixed during the B&B process. I'd like SCIP to do these two things:

branch only with respect to variables X[i]
if the solver is processing a node at which all the variables X[i] have fixed 0-1 values, then fix the values of Y[j] to the unique 0-1 values giving a feasible solution at this node (so SCIP can stop working on this branch)

Any suggestions on how to proceed?

Hi. SCIP has the function SCIPchgVarBranchPriority but it is not in the interface (we would be very happy if you open a PR with the addition).
So, as a quick hack, I would declare the Y variables to be implicit integer instead of binary.
As for the second point, you can implement a simple heuristic that checks whether all X vars are fixed and then sets the value of the Y vars. You can have a look at tests/test_heur.py

OK. Two questions then:

What do you mean by "implicit integer"? Defining them to be continuous and enforcing integrality in a lazy way (e.g. inside a constraint handler by calling chgVarType)?
I get the idea, but will that force SCIP to stop working on the node? Imagine a situation were the linear relaxation at the node gives a value for the objective function that is both better than the unique integer-feasible solution at that node (i.e. the one informed by the heuristic) AND also better than the best integer-feasible solution found so far.

Implicit integer is a type of variable in SCIP https://scip.zib.de/doc-7.0.0/html/FAQ.php#implicitinteger
I see. Ok, so I think you should implement a constraint handler then, that checks whether all X vars are fixed and then fixes all the Y variables.
To implement a constraint handler you can have a look at:
examples/finished/lotsizing_lazy.py
tests/test_alldiff.py
tests/test_conshdlr.py
tests/test_tsp.py

please reopen if there is still an issue

So, as a quick hack, I would declare the Y variables to be implicit integer instead of binary.

Is it possible to declare a variable implicit integer in pyscipopt? It seems that addVar in scip.pyx only recognizes 'C', 'B' and 'I' as types. It would be useful to have implicit integer type too.


⚠ Bofrost.be has degraded performance

In 4c63f68, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1106 ms

Resolved: Bofrost.be performance has improved in 3dcba5e after 52 minutes.


Use Atomic* variables for cross thread updates

This is an attempt at fixing test flakiness.

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

I'm closing this PR without merging because I don't think the problem is a race condition with the counts or callbacks for the locks.
The flakiness was in only one test method:
https://ge.gradle.org/scans/tests?search.relativeStartTime=P28D&search.timeZoneId=America/New_York&tests.container=org.gradle.cache.internal.DefaultFileLockManagerContentionIntegrationTest&tests.sortField=FAILED&tests.unstableOnly=true
If you drill down into the test, it's happening in lots of different environments (Windows, Linux and EC2) and executors:
https://ge.gradle.org/scans/tests?search.relativeStartTime=P28D&search.timeZoneId=America/New_York&tests.container=org.gradle.cache.internal.DefaultFileLockManagerContentionIntegrationTest&tests.sortField=FAILED&tests.test=if the lock was released by one lock holder, but taken away again, the new lock holder is pinged once&tests.unstableOnly=true
The other thing I noticed is that it would be very strange for atomics to help here because the assertions are inside a poll(120) {}, which means that the test will continuously poll the value of the variables (e.g., requestReceived) and I think it would be unlikely that the separate thread would never see the right value after polling for 2 minutes.
So I took a closer look at the failing test and saw that it happens in the second poll(). The behavior we're trying to test here is...

Lock owner 1 has the lock.
Build requests the lock from owner 1.
Lock owner 1 releases the lock.
Lock owner 2 grabs the lock.
Build requests the lock again from owner 2.
Lock owner 2 releases the lock.
Build grabs the lock and finishes.

If you look at the logs, the build never pings owner 2, but you can see that it does successfully get the lock anyways. This means the build is beating "lock owner 2" sometimes due to a race between step 3 and 4:
https://github.com/gradle/gradle/blob/bdcf8e3861b305f80d6186da9b535c1fbb10c173/subprojects/persistent-cache/src/integTest/groovy/org/gradle/cache/internal/DefaultFileLockManagerContentionIntegrationTest.groovy#L210-L211
I can make this test fail every time by inserting a 5 second sleep between those two lines.
I think we should just delete this test since we have coverage for the behavior otherwise (we ping the owner once). I've done that here:
https://github.com/gradle/gradle/commit/49c7747f7b6abbd670403bb4a722db28761ad76f


home-assistant-addon "Music providers issue"

What version of Music Assistant has the issue?
version: "2.0.0b39"
The problem
The Filesystem (local disk) does not show the HA local mapped subdirectories. It only shows the top 2 directories (i.e /media/Music/.
Home assistant shows all the mapped paths under the Media including SMB shares and the mounted directories, subdirectories and associated files.
Thanks
How to reproduce
N/A
Relevant log output
No errors
Additional information
No response
What version of Home Assistant Core are your running
2023.6
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Raspberry Pi

Addition to the above.
Installed today the docker version and had the same problem with the local providers. This time the setup doesn't even map the local media folder.
Here is the log:
"2023-07-05 19:52:21 INFO  music_assistant  -- Loaded player provider Airplay
2023-07-05 19:52:31 WARNING asyncio  -- Executing <Task finished name='Task-1' coro=<run..new_coro() done, defined at /usr/local/lib/python3.11/site-packages/aiorun.py:227> exception=EventLoopBlocked()> took 10.677 seconds
2023-07-05 19:52:31 ERROR asyncio  -- Task exception was never retrieved
future: <Task finished name='Task-1' coro=<run..new_coro() done, defined at /usr/local/lib/python3.11/site-packages/aiorun.py:227> exception=EventLoopBlocked()>
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/zeroconf/_utils/asyncio.py", line 86, in run_coro_with_timeout
return asyncio.run_coroutine_threadsafe(aw, loop).result(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/concurrent/futures/_base.py", line 458, in result
raise TimeoutError()
TimeoutError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiorun.py", line 237, in new_coro
await coro
File "/usr/local/lib/python3.11/site-packages/music_assistant/main.py", line 106, in start_mass
await mass.start()
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/server.py", line 123, in start
self._setup_discovery()
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/server.py", line 512, in _setup_discovery
self.zeroconf.register_service(info)
File "/usr/local/lib/python3.11/site-packages/zeroconf/_core.py", line 623, in register_service
run_coro_with_timeout(
File "/usr/local/lib/python3.11/site-packages/zeroconf/_utils/asyncio.py", line 90, in run_coro_with_timeout
raise EventLoopBlocked from ex
zeroconf._exceptions.EventLoopBlocked"

I’m not sure that error is related but @marcelveldt ?

Is there a way to map any local source folders like "docker run --network host --privileged -v /media:/media ghcr.io/music-assistant/server"?
Since MA runs privileged in host mode there should be no access restrictions to root folders.
Remote shares like samba aren't find either.
If MA has the DLNA media render implemented and discovers automatically the speakers, then why my nas servers (i.e. synology) with DLNA media servers enabled are not discovered and automatically mapped as media sources?

They are not mapped automatically you need to add them as local providers

Is the stand alone docker version mapping the local /media folder to the root folder of the OS, or is trying to map the /media folder to a HASS container with docker? Does the MA container has its's own local /media folder which needs to be mapped with the OS /media folder?
I still can't figure out how to map a local folder within the OS root media folder from within the MA settings!

You can map whatever you want and then you van add that path in the "Local files" provider.
So e.g. map your music files into /media and then add the Filesystem provider and at the path you enter /media

Thanks Marcel, it works just fine!
One thing I would suggest for the docker version is an "About" button or any provided information regarding the installed MA version.
Overall great job!


used python-futurize on python files for python 3 compatibility

Merged, with some additional reworking of the old code to support both 2 and 3 at once.
Thanks!


How do I list objects in a nested folder in S3?

I tried with listed_objects by using a bucket_name that included the nested folder and then using the prefix option as well but no cigar. Wondering if this is possible? If yes, how? Thank you,

If you happen to be wondering this is how you can do this:
ExAws.S3.list_objects("bucket_name", [{:prefix, "folder_name"}]) |> ExAws.request!

FYI this is equivalent to the more idiomatic syntax:
ExAws.S3.list_objects("bucket_name", [prefix: "folder_name"]) |> ExAws.request!

Cool, thank you Ben. You're the man!


How to limit output token generated: Phi model

From a given context + query, the model generates well the answer, but very long -> around 2000 chars.
Is there any way to do max_output_tokens=200 like pplx or openAI API?
This is my prompt template:
_template = "You are an assistant that delivers short answers to the user inquiry from the provided context.\n\n
            context: {conditioned_passages}\n\n
            query: {query}
            answer:"

num_predict:
https://github.com/ollama/ollama/blob/main/docs/modelfile.md
I think the default is actually -1 even though the API docs say it's 128 (I had the Llemma model run all night once by accident!).

Thanks :), i'm goint to put num_predict: 40
I noticed a kinda infinite token generation and stopped generating at some point. Maybe to prevent the early stop, could be to use stop System:
From
ollama show phi --parameters

Output
stop                           "User:"
stop                           "Assistant:"
stop                           "System:"

@bm777 Did num_predict fix your issue? If so, do you mind closing (or me closing) the issue?

@bmizerany somehow yes.

in somehow, it doesn't cut properly. @bmizerany

@metamec did you find a solution?

The problem with the num_predict 'solution' is that you end up with a truncated final sentence.

did you find a solution to this?

Unfortunately not, sorry.

I'm going to close this since it's pretty stale a this point. I think the problem was the template wasn't correct, although it does work reasonably well with phi3, although phi3 seems to have problems when it hits the context size.


Upgrade Xunit for Nullable annotations

The latest versions of XUnit have Nullable annotations which would more easily enable us to manage nullables in our test classes. Once a stable version of 2.4.2 is released (with the accompanying extension packages) we should upgrade.

I see that the <XunitVersion> property in eng\Versions.props has now been updated to 2.4.2 which is the stable release for xunit.assert.
Now that the razor compiler source code has been merged into the new razor repo they have brought across changes to eng\Versions.props which includes <XunitAssertVersion>$(XunitVersion)</XunitAssertVersion>
So it looks like all that is needed now is to add the package reference to the required test projects e.g.
<PackageReference Include="xunit.assert" Version="$(XunitAssertVersion)" />

Actually it seems xunit 2.4.2 depends on xunit.assert 2.4.2, so I think the Compiler merge upgrading us solved everything here.
I'll close the issue, thanks for calling attention to this!


Added a featherFloatIn and featherFloatOut animation to function in a…

…nimate.css

Please see this

dear author, you have to provide us a codepen demo of it.

I'm considering closing this as there's no answer to what was requested.

yeah I think I can do it... and check if it is fit to animate.css let me work on this.


Simplify Hawktracer boilerplate

Hawktracer already has a feature, "profiling_enabled",
which controls whether it performs profiling or performs a no-op.
With the feature disabled, it performs the equivalent of our
noop_proc_macro. Therefore, we can remove our extra layer of
boilerplate.

Coverage increased (+0.1%) to 66.037% when pulling 031b4e59f4c15e16e7ff638022e3ef40e9b51ad6 on shssoichiro:simplify-hawktracer-boilerplate into b6a488fe0afb75690ecd389ce663faee210c3ca0 on xiph:master.

Sounds a good idea. Thank you :)


Fix surface view height

Bugfixs

The child view controller in FloatingPanelController can use the bottom of safe layout guide expectedly.

Modify FloatingPanelController.adjustedContentInset value

Fix a critical bug on only full and half anchor position support
Fix FloatingPanelLayout.{topInteractionBuffer,bottomInteractionBuffer}
Modify Examples/Maps to fix a blank space and a clip of cells issue in #1.  Thank you, @jaimeealmanza!

Improvements

Improve the shadow layer of FloatingPanelSurfaceView
Add a sample scene with TabBar in Samples.app.
Update README

Add shields
Add TOC
Add Notes section
Update Usage section

@SCENEE  Thanks for the fix! 👏🏼


Scaling langevin noise

Hi @JavierAntoran  @stratisMarkou ,
I am currently using SGLD in another project. I have some example code, where the noise added to the parameters is scaled by the learning rate:
noise = torch.randn(n.size()) * param_noise_sigma * lr.
I belive, this is wrong and so I scaled the noise with the square root of the learning rate:
noise = torch.randn(n.size()) * np.sqrt(lr)
This works well. However, you scale the learning rate by
1/np.sqrt(sigma)
If I do this, the noise gets way too big and the network does not learn. Also, in the initial paper by Welling et al. it seems to me that the first approach is right, though I already found out that the variance of the noise scales with lr**2, which is why the square root is necessary.
I hope you can explain to me, why the ()^-1 is necessary. Thank you in advance!

Hi @maltet96,
By default pytorch uses the Tensor.add_ method to update weights.  The first argument is multiplied by the second argument and added to the tensor. In this case -group['lr'] is going to multiply both the weights' gradients and the additive noise. As you correctly point out, we need to multiply unit variance noise by the square root of the learning rate such that the resulting variance matches the learning rate. Thus, in the previous step, we divide the noise term by the square root of the learning rate.
langevin_noise = p.data.new(p.data.size()).normal_(mean=0, std=1) / np.sqrt(group['lr'])
p.data.add_(-group['lr'], 0.5 * d_p + langevin_noise)

I do understand, thank you very much for explaining it!


Proposal for sharing source between apps

This proposal is to support a simple and generic way to share code between create-react-app apps.
It can support monorepos and arbitrary source directory layout (e.g. for cleaning up relative import paths).
Example:

monorepo
  |--cra-app1
     |--package.json: srcPaths: [“../shared”]
     |--src
       |--file1.js: import comp1 from ‘comp1’ ← ok, shared/comp1
       |--file2.js: import comp1 from ‘../../shared/comp1’  ← naughty, fails
  |--cra-app2
     |--package.json: srcPaths: [“../shared”, "./packages"]
     |--src
       |--file1.js: import comp1 from ‘comp1’ ← ok, shared/comp1
       |--file2.js: import comp3 from ‘comp3’ ← ok, packages/comp3
     |--packages
       |--comp3
  |--shared
    |--comp1
    |--comp2

Proposal:

srcPaths are specified in package.json.
Modules found in srcPaths are treated essentially the same as /src modules.
** transpiled using same cra config
** do not have their own package.json, do not specify own dependencies, .babelrc, etc.
** all tests in modules are included when running app tests
Modules in a srcPath are imported between /src or another srcPath using absolute import paths.
Keep us sane?...don't allow overlapping srcPaths

The implementation to support this has a smallish footprint:

see https://github.com/bradfordlemley/create-react-app/commit/709dc407e2855f5dbdd982bde19dc0141e0d8e7c

More info on this proposal including a working monorepo is here:
https://github.com/bradfordlemley/cra-share
I think the best part of this proposal is that it puts a lot of flexibility and power within the grasp of a novice developer.  I think it works approximately how a novice developer would expect shared source to work.  ...but...what are the issues with this proposal that I'm not seeing?

What do you see as the major differences between your proposal and something like Yarn Workspaces (https://yarnpkg.com/blog/2017/08/02/introducing-workspaces/)? I think it will become a more 'conventional' approach to javascript monorepo's and offers enough flexibility for novice developers to be productive with.

@rmhartog
Longer-term, the js community will surely come up with a generic way to manage source package dependencies, but it doesn’t seem to have arrived yet.
Yarn workspaces is a step in that direction, but I think if you try to do this with yarn workspaces, you’ll find it’s not (yet) ideal for this use case.  In my opinion, the root of the problem is that npm packages don’t carry the necessary metainfo to be used as source packages...they are intended as buildable libraries.  Package.json could carry that extra metainfo, and I think it probably will in the future.  But, that’s just my theory on yarn workspaces, I haven’t put time into proving it out, maybe you or someone else can add more info or disprove my theory.
On the other hand, I think this srcPaths proposal provides an instant developer-friendly experience for create-react-app users -- basically, everything works the same as your standard /src, just from a different spot.  The major drawback is probably that it doesn’t support dependencies of included srcPaths -- it totally punts to the top-level included to have all of the dependencies of the srcPaths that in includes.  I convinced myself to be ok with this because: (1) that’s the same as any other sources under /src, (2) if the included thing has a lot of dependencies, maybe it does belong in it's own package, and (3) dependency management is hard.  Dependency management would be (is?) a major win for using yarn workspaces.

Would there be a way to have versioned dependencies managed through package.json with this approach? Say for example you have two CRA projects in separate repos, and a one-way dependency, could you publish one to npm, add it to package.json from the other and consume it from a srcPath inside node_modules?

@raycohen I don't think that will work because the build won't be able to pick up cra2's dependencies (from cra1/node_modules/cra2/node_modules).  (If cra1 contained cra2's dependencies, I think it would work, but I don't think that's what you were asking.)

@bradfordlemley, thanks for kicking this off. I've successfully given it a try, but have a few questions:
Given the following project structure (a Lerna monorepo):
packages
├── parent-app
├── component-1
└── component-2

All packages are bootstrapped with Create React App and  parent-app's package.json contains:
"srcPaths": [
  "../component-1/src",
  "../component-2/src"
]

If both component-1 and component-2 contain e.g. a User component, can they both be imported in parent-app? I would assume one would take precedence over the other and so we'd need a way to namespace imports, maybe:

"srcPaths": {
  "component1": "../component-1/src",
  "component2": "../component-2/src"
}

When using separate repos (not a monorepo), can we include node_modules without transpiling? It appears something is not currently supported (due to https://github.com/facebookincubator/create-react-app/issues/1125):

"srcPaths": {
  "node_modules/component-1/src"
}

@tlvince

You could achieve that w/ srcPaths=[".."], then import User1 from 'component-1/src/User'.  Or you could add another dir under component-x/src, e.g. component-1/src/comp1/User, then import User1 from 'comp1/User'.  The namespace/aliasing suggestion could make the import a bit prettier without adding the extra dir (import User1 from 'component1/User'), but I think it would complicate the dev experience, e.g. to debug that import, you'd normally look for a component1 directory somewhere, but it wouldn't exist.
This should work, but I haven't tried it.  (Files from "node_modules/component-1/src" would be transpiled -- I think that's what you were asking.)  The catch is that component-1's dependencies would not be available, so, e.g. if component-1 needs moment.js, moment would have to be included in the top-level app's dependencies.  (some other comments in this thread also discuss this dependencies issue.)

Closing as dupe of https://github.com/facebookincubator/create-react-app/issues/1492. Please add new proposals there.


error: LateInitializationError: Field 'connector' has not been initialized.

Hello,
I followed your example for running JS code from dart:
I've added this code:
 return WebViewX(
      width: 320,
      height: 500,
      initialContent:
          'someUrl',
      onWebViewCreated: (controller) => webviewController = controller,
      onPageFinished: (_) {
        webviewController
            .callJsMethod('testPlatformSpecificMethod', <dynamic>['Hi']);
      },
      jsContent: const {
        EmbeddedJsContent(
          webJs:
              "function testPlatformSpecificMethod(msg) { CaptchaMessenger('Web callback says: ' + msg) }",
          mobileJs:
              "function testPlatformSpecificMethod(msg) { CaptchaMessenger.postMessage('Mobile callback says: ' + msg) }",
        ),
      },
      dartCallBacks: {
        DartCallback(callBack: recaptchaCallback, name: 'CaptchaMessenger')
      },
    );

But  when I run this code I always get this error:
error: LateInitializationError: Field 'connector' has not been initialized..
Additional info:

I'm running the app on Web

Hi, I found out where the problem is coming from
view/impl/web.dart:164
...
if (widget.initialSourceType == SourceType.html ||
    widget.initialSourceType == SourceType.urlBypass ||
    (widget.initialSourceType == SourceType.url &&
        widget.initialContent == 'about:blank')) {
   // This function sets the `connector` everytime the page is loaded
  _connectJsToFlutter(then: _callOnWebViewCreatedCallback);
} else {
  // Here the `connector` doesn't get set, so it ends up `null` inside the WebViewXController.
  //
  // We reach this part of the code when the `sourcetype` is url
  // and the url is not `about:blank`
  _callOnWebViewCreatedCallback();
}
...

As you can see inside the else block, the connector doesn't get set and because of that, it ends up being null inside the controller.
Now, there's a small problem here: The connector cannot be set when using SourceType.url and the URL is not about:blank. This is noted here https://github.com/adrianflutur/webviewx/issues/27, precisely:
Calling any method that will interact with the page's source (i.e. call JS methods, callbacks, execute JS etc) from the controller only works when using SourceType.urlBypass or SourceType.html. This is because only in theese 2 situations the package can actually inject that JS code inside the page source. When using SourceType.url, iframe's content does not actually belong to us - it is loaded from a different domain so we're not allowed to do that.
I could add a partial workaround for this, such that the connector actually becomes the browser page, and not the iframe page. This would mean that you would have access to the browser's window object, not the iframe's one. But I'm not sure this would really solve anything, as you would get a NoSuchMethodError when calling any methods because they won't exist in the browser's window object.
A solution would be to change the sourceType to SourceType.urlBypass. This will allow the package to inject EmbeddedJsContent and DartCallbacks inside the page.

thank you for your response. I have to try using SourceType.urlBypass and I'll let you know if this fits my needs

Closing this for now, please open another issue if you encounter any more issues.

@adrianflutur why is this important issue closed? The most important function in this whole plugin is NOT WORKING!


Design Analytics Playlist View

Design the playlist view for the analytics application.

The same as the normal library view with a filter applied.


Solves the failing test of SS-SRM

This PR resolves an issue between Theano and MKL 2018 that requires an environment variable for MKL to run Theano.
Fixes #304 .

Jenkins, retest this please.

Jenkins, retest this please.

I could successfully run pr-check from my account on the Jenkins machine once. The second time I tried, it failed with the same error seen in Jenkins. Very strange.

Maybe we should move to non-conda? Although that is valuable, there could be some issue with conda packages at the moment.

As a temporary fix, we could switch to Python 3.4 from EPEL, but I think it is important to test on Anaconda as well, given that it is popular with our users. If I cannot fix the issue until the end of the day, I will make the switch.

I agree with you, but macOS is installing with conda, right?
There should be something wrong with the linux version.
Also, we should start fixing the versions of some tools.


Metro+TS: support additional package.json fields when resolving a module to a file

What happened?
In @rnx-kit/typescript-react-native-resolver, the function resolveModule (src/resolve.ts) looks for "default" entry point files in package.json -- fields like "main", "types", and "typings".
Repos using newer or custom tech may have other custom fields in their package.json files which refer to additional entry points. For example, Apollo uses the "module" field to refer to the main ES6 module in the package.
This should be an optional configuration parameter which defaults to no additional fields.
Affected Package
@rnx-kit/typescript-react-native-resolver
Version

Which platforms are you seeing this issue on?

[X] Android
[X] iOS
[X] macOS
[X] Windows

System Information
N/A

Steps to Reproduce
N/A
Code of Conduct

[X] I agree to follow this project's Code of Conduct

TypeScript doesn't support this type of extension, though they do have a more sophisticated resolver. With https://github.com/microsoft/TypeScript/pull/48189 being imminently accepted into TS main, I will be deprecating typescript-react-native-resolver.


Need the ability to display the price of the product at the time it was placed in cart

As a customer
I need the ability to display the price of a product when it is placed in my cart
So that I can keep an eye on how much I am going to spend
Details and Assumptions

associate a shopcart with a product through a product id

Acceptance Criteria
Given the customer is logged into their account
When the customer adds an item to their cart
Then the price of the item will be reflected in the cart

Is this still relevant? If not maybe we can close it?


Support for higher order components

I'm struggling to implement https://reacttraining.com/react-router/web/api/withRouter
It seems like we need support for some kind of higher order components to succeed here.

@hejfelix can you try using ReactComponentClass as a props type for withRouter as per https://slinky.shadaj.me/docs/external-components/ ? That method has worked for other higher order components like Apollo.

I tried something like that with no success -- I'll give it another go and return here with the results + some code

Right, so I tried some stuff:
@JSImport("react-router", JSImport.Default)
@js.native
object ReactRouter extends js.Object {
  val withRouter: js.Function1[ReactComponentClass,ReactComponentClass] = js.native
}

There's my withRouter def. When I try to use it:
    val clazz: ReactComponentClass = withRouter(Demos)
    val element = div(withRouter(Demos))
    ReactDOM.render(element, container)

which yields

[error] /Users/dkfepaha/repos/slinky-wrappers/demo/src/main/scala/com/lambdaminute/slinkywrappers/web/Main.scala:37:19: overloaded method value apply with alternatives:
[error]   (elems: slinky.core.facade.ReactElement*)slinky.core.facade.ReactElement
[error]   (mod: slinky.core.AttrPair[slinky.web.html.div.tag.type],remainingMods: slinky.core.AttrPair[slinky.web.html.div.tag.type]*)slinky.core.WithAttrs
[error]  cannot be applied to (slinky.core.ReactComponentClass)
[error]     val element = div(withRouter(Demos))
[error]                   ^
[error] one error found
[error] (demo / Compile / compileIncremental) Compilation failed
[error] Total time: 5 s, completed May 14, 2018 12:50:19 PM

I also tried to apply the ReactComponentClass instance:
    val clazz: ReactComponentClass = withRouter(Demos)
    val element = div(withRouter(Demos).apply())
    ReactDOM.render(element, container)

but that also doesn't work:

[error] /Users/dkfepaha/repos/slinky-wrappers/demo/src/main/scala/com/lambdaminute/slinkywrappers/web/Main.scala:37:41: value apply is not a member of slinky.core.ReactComponentClass
[error]     val element = div(withRouter(Demos).apply())
[error]                                         ^
[error] one error found
[error] (demo / Compile / compileIncremental) Compilation failed
[error] Total time: 6 s, completed May 14, 2018 12:52:20 PM

Are you saying I should treat withRouter as a component?

Right, so tried to model it as a component:
@JSImport("react-router", JSImport.Default)
@js.native
object ReactRouter extends js.Object {
  val withRouter: js.Object = js.native
}

@react object withRouter extends ExternalComponent {
  override type Props = ReactComponentClass
  override val component = ReactRouter.withRouter
}

And this compiles with client code:
    val element = withRouter(Demos)
    ReactDOM.render(element.apply(), container)

However, the javascript console gets me:

Warning: Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render. Or maybe you meant to call this function rather than return it.
in withRouter

@JSImport("react-router", JSImport.Default)
@js.native
object ReactRouter extends js.Object {
  val withRouter: js.Function1[ReactComponentClass,js.Function1[js.Object,ReactElement]] = js.native
}

This works, however, I would like to give a better guess about the js.Object type. I wonder if I can have parameterized methods implemented as js.native

@hejfelix so looking at the docs it appears that withRouter isn't a React component, which explains the error you got.
For the RouteProps, one way you can have it also extract out the T values would be to define a custom Reader that reads both the default props as well as T from the same JS object. Then you could have the component take type Props = RouteProps[MyExtraType]. One issue there is that the ReactComponentClass is completely untyped so you lose safety there; I'll try to take a look and see if that can be improved.

Cool, thanks. In case you want to have a look at the current state of my code, here it is:
https://github.com/hejfelix/slinky-wrappers/tree/master/react-router/src/main/scala/com/lambdaminute/slinkywrappers/reactrouter
Particularly, you can save the trouble of writing this:
case class Match(params: js.Object, isExact: Boolean, path: String, url: String)
case class Location(key: UndefOr[String], pathname: UndefOr[String], search: UndefOr[String], hash: UndefOr[String])
case class History(length: Int,
                   action: String,
                   location: Location,
                   push: js.Function,
                   replace: js.Function,
                   go: js.Function,
                   goBack: js.Function,
                   goForward: js.Function,
                   block: js.Function)
case class RouteProps(`match`:Match, location: Location, history: History)

Closing because this appears to have been resolved.


Supports "users use their email as their username".

New Issue Checklist

[x] I am not disclosing a vulnerability.
[x] I am not just asking a question.
[x] I have searched through existing issues.
[x] I can reproduce the issue with the latest version.

Issue Description

Parse-server supports "users use their email as their username" :
On the resetting passwords section of parse-server JS SDK document,

This will attempt to match the given email with the user’s email or username field, and will send them a password reset email. By doing this, you can opt to have users use their email as their username, or you can collect it separately and store it in the email field.

On the signing up section,

You are free to use an email address as the username. Simply ask your users to enter their email, but fill it in the username property — Parse.User will work as normal. We’ll go over how this is handled in the reset password section.

Email adapter have to handle username as an email in this case.
When the adapter got there user object as recipient and email filed of user is empty, use username as an email.
Parse-server check below code of parse-server:

https://github.com/parse-community/parse-server/blob/260290409e747414c703ddec755d5cba73be5e83/src/Controllers/UserController.js#L205
https://github.com/parse-community/parse-server/blob/260290409e747414c703ddec755d5cba73be5e83/src/Controllers/UserController.js#L308
https://github.com/parse-community/parse-server/blob/260290409e747414c703ddec755d5cba73be5e83/src/Controllers/UserController.js#L226-L229

If you want check the early discussion of this issue, please check this
Steps to reproduce

Setup parse-server with this email adapter.
Sing up : use their email as their username

Request password reset

<EMAIL_ADDRESS>
Actual Outcome

You can't not get any email.
Expected Outcome

You can get an "reset password email".
Failing Test Case / Pull Request

#54
Environment

API Mail Adapter version: 2.10
Parse Server version: 4.10.4

Logs

Thanks for opening this issue. That's an interesting behavior of Parse Server. I understand the intention of that behavior, but I am not sure it should be that way, because its an unclean approach in terms of data separation, and it creates a lot of issues down the road. It probably also breaks the email verification logic for that user. If the user has an email in the username field and a different email in the email field, it's unclear which email would be verified. So this looks much like a bug in Parse Server, which should be fixed.
If Parse Server currently behaves that way, and we want to propagate the bug into this email adapter, we would need to consider the order of the fields checked. Is it email || username or username || email?


Error installing rebar3

Using the following:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Set up Elixir
  uses: erlef/setup-beam@v1
  with:
    elixir-version: '1.13.3' # Define the elixir version [required]
    otp-version: '24.1' # Define the OTP version [required]

I get the following error:

Am I doing something wrong?

The error stays, even if I add install-rebar: false

Hm... let me test this.

https://github.com/paulo-ferraz-oliveira/setup-beam-example/blob/setup-beam/issues/99/.github/workflows/ci.yml
Is this the same as your example? I don't see it error'ing out (maybe I'm missing something?)
Initially I thought it could be from the v3 (for the checkouts action), but seems not to be so.

In particular, I have https://github.com/paulo-ferraz-oliveira/setup-beam-example/runs/5821121108?check_suite_focus=true#step:3:24, which seems to be different from your output.

hmmm, strange, I still have the same error. It has worked before, and suddenly stopped working, without any hanges in the yaml file. And the yaml files seems to look the same.
Is it an idea to give you temporarily access to the repository where I have the problem?

I can fork it and test it out (if I know where stuff is), but I see no real reason for this to fail, atm.
Can you copy-paste from my example repo. and test again?

I tried the copy-paste, and only changed the on: push to on:workflow_dispatch, and I still get the same error.
I have send you an invite to collaborate on my private repository. It would be great if you have the time to check it out.

even if I add install-rebar: false

seems like an action issue, since it shouldn't try to install stuff we told it not to.

@hermanius, after the fix proposed by #100 (still needs discussion and merge), using install-hex: false and install-rebar: false means that the action already runs past the installation part (in your case), but I still can't understand why it fails otherwise. The only difference I see is that your repo. is private, but I'm not sure how that would influence it. (I actually went ahead, created a private repo and tested this: still no issue!). I'm not sure why the Elixir function is getting nil instead of a binary() 🤷

@paulo-ferraz-oliveira , I really appreciate the effort you are doing to find a solution. It's a curious issue indeed, and even stranger is that it worked for a few days, and then suddenly stopped working. As if Github has made a change somewhere.
At some point I'm going to need hex/rebar so I hope, after the fix, I can get them installed later in the workflow using RUN commands. Getting them installed through your action still would be the preferred solution, but if I can do it with a few RUN commands it would be a decent work-around.

Yeah, I'm sorry I can't help further. I can ask @ericmj for help, since this is Elixir and he probably knows where the issue is apparent, but not what is causing it. Close at will if you feel this is no longer an issue.

I'm hoping #100 gets approved soon, so I can see wether I can install hex/rebar with RUN commands.

I was able to run the workflow with paulo-ferraz-oliveira/setup-beam@fix/booleans and install rebar/hex with RUN's further down the workflow.
For me this a good-enough work-around, and I hope of course you will be able to fix the issue someday.
Thanks for helping me out.

@hermanius, 1.11.1 is released. Cheers.


feat: add environment configuration via prefix

This will allow to set all settings with a CHEQD_DID_RESOLVER_ Prefix

Superseded by #40


feat: adds dynamic mod type lookup

What

Adds dynamic mod type lookup to /get-mod-data-for-last-year

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Show shorter completions

Hi there. For a while now, the completions Tabnine provides are much longer and forces me to type more 😆
In the image below, it would be great if "saveHandler" was an option, in addition to those suggested:

Is it possible to show shorter completions and also show the longer completions so I can just type a few letters then Tab, and a few letters and Tab etc?
Thank you.
gz#24805(related to Zendesk ticket #24805)

Hi @turiondolby
Have you tried our inline completions? it's a more suitable UX for these longer completions.
I presume you have "Use Hybrid suggestions rendering mode" enabled in the hub, so open the Hub -> Settings -> Advanced Settings, and toggle off this option


Are links to web pages allowed in the book element?

Both in the /package/boards/board/book and in the /package/devices/family/.../book description it is not clear if the links to web pages can be used.
In the description of the name attribute there is only the reference to the file extension of the document and its path in the package.
Instead, in the description of the public attribute it is reported: "Links to web pages are assumed to be public." so I'm led to think that also the external URLs can be used.
Could this point be clarified?
If the URLs are allowed, maybe a short sentence like the following one could be added to the description of the name attribute:
"The link to a document on an external web site is also allowed."

The straight answer is: YES
https://open-cmsis-pack.github.io/Open-CMSIS-Pack-Spec/main/html/pdsc_boards_pg.html#element_board_book
https://open-cmsis-pack.github.io/Open-CMSIS-Pack-Spec/main/html/pdsc_family_pg.html#element_book
Needs to be extended to explicitly mention the option to specify a url.

Hi @jkrech, if you agree I can open a PR with the explicit mention to the url in the book element description.

Documentation got updated.


[BUG]Error: API Error Updating Resource Service Instance (Subaccount)

Is there an existing issue for this?

[X] I have searched the existing issues

What version of the Terraform provider are you using?
1.7.0
What version of the Terraform CLI are you using?
1.9.7
What type of issue are you facing
bug report
Describe the bug
Run a tf configuration with a gh action.
When trying to update the destination service instance the btp provider always fails:
https://github.com/quovadis-btp/btp-automation/blob/main/btp-context/provider-context/modules/sap-hana-cloud/main.tf#L268
This looks like a buffer overflow problem knowing the destination service instance payload is more than 8kB (but way below 256kB json payload limit on BTP CLI server side)
2024-10-10T12:22:54.747Z [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-10-10T12:22:54.748Z [INFO]  provider: plugin process exited: plugin=.terraform/providers/registry.terraform.io/hashicorp/local/2.5.2/linux_amd64/terraform-provider-local_v2.5.2_x5 id=1775
2024-10-10T12:22:54.748Z [DEBUG] provider: plugin exited
2024-10-10T12:22:56.508Z [DEBUG] provider.terraform-provider-btp_v1.7.0: 2024/10/10 12:22:56 [DEBUG] Waiting for state to become: [succeeded]
module.provider_context.btp_subaccount_service_instance.dest_provider: Still modifying... [id=c451d956-7dde-4966-a2b6-da1fe2f73fa7, 10s elapsed]
Error: -10T12:23:06.616Z [ERROR] provider.terraform-provider-btp_v1.7.0: Response contains error diagnostic: diagnostic_detail="API error during service instance update - Failed to update the destination service instance with the user provided configuration." diagnostic_severity=ERROR diagnostic_summary="API Error Updating Resource Service Instance (Subaccount)" tf_proto_version=6.6 tf_provider_addr=registry.terraform.io/sap/btp tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-go@v0.24.0/tfprotov6/internal/diag/diagnostics.go:58 @module=sdk.proto tf_req_id=cdadb48c-e075-612f-69a2-4e9bb1eade69 tf_resource_type=btp_subaccount_service_instance timestamp=2024-10-10T12:23:06.616Z
2024-10-10T12:23:06.617Z [DEBUG] State storage *cloud.State declined to persist a state snapshot
Error: -10T12:23:06.617Z [ERROR] vertex "module.provider_context.btp_subaccount_service_instance.dest_provider" error: API Error Updating Resource Service Instance (Subaccount)
2024-10-10T12:23:06.617Z [DEBUG] cloud/state: state read serial is: 19; serial is: 19
2024-10-10T12:23:06.617Z [DEBUG] cloud/state: state read lineage is: 2c09f9ca-47dc-a37a-ddbb-de32eaf5183b; lineage is: 2c09f9ca-47dc-a37a-ddbb-de32eaf5183b

Error: API Error Updating Resource Service Instance (Subaccount)

  with module.provider_context.btp_subaccount_service_instance.dest_provider,
  on .terraform/modules/provider_context/btp-context/provider-context/modules/sap-hana-cloud/main.tf line 268, in resource "btp_subaccount_service_instance" "dest_provider":
 268: resource "btp_subaccount_service_instance" "dest_provider" {

API error during service instance update - Failed to update the destination
service instance with the user provided configuration.
2024-10-10T12:23:07.186Z [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-10-10T12:23:07.187Z [INFO]  provider: plugin process exited: plugin=.terraform/providers/registry.terraform.io/sap/btp/1.7.0/linux_amd64/terraform-provider-btp_v1.7.0 id=1789
2024-10-10T12:23:07.188Z [DEBUG] provider: plugin exited
Error: Process completed with exit code 1.

Expected Behavior
The same flow works if started locally in a terminal window
Plan: 1 to add, 1 to change, 1 to destroy.
module.provider_context.local_file.subaccount_id: Destroying... [id=e05b9982c132b237742b1a5436087bc26275e1f7]
module.provider_context.local_file.subaccount_id: Destruction complete after 0s
module.provider_context.local_sensitive_file.provider_sm: Creating...
module.provider_context.local_sensitive_file.provider_sm: Creation complete after 0s [id=b90cfb6519579f264a41c776e8e5488e862a66a7]
module.provider_context.btp_subaccount_service_instance.dest_provider: Modifying... [id=c451d956-7dde-4966-a2b6-da1fe2f73fa7]
module.provider_context.btp_subaccount_service_instance.dest_provider: Still modifying... [id=c451d956-7dde-4966-a2b6-da1fe2f73fa7, 10s elapsed]
module.provider_context.btp_subaccount_service_instance.dest_provider: Modifications complete after 12s [id=c451d956-7dde-4966-a2b6-da1fe2f73fa7]

Apply complete! Resources: 1 added, 1 changed, 1 destroyed.

Steps To Reproduce
https://github.com/quovadis-btp/btp-boosters/actions/runs/11273909018/workflow
User's Role Collections
Global account admin
Add screenshots to help explain your problem

Additional context
No response

@ptesny Can you please give access to the GH Action you are using? The link to the actions run mentioned above gives me a 404 (private repo?)
If the flow works locally, I do not see how the provider could fix this when being executed in a GH Action, as it is the same binary that gets executed

Can you please give access to the GH Action you are using? The link to the actions run mentioned above gives me a 404 (private repo?)

done

If the flow works locally, I do not see how the provider could fix this when being executed in a GH Action, as it is the same binary that gets executed

I do not have explanation why. The local terminal is on MacOS - arm64, the gh action runs on ubuntu amd64 linux...that's the only real difference....
When the remote workflow fails the failed destination service instance update is also reflected on BTP side with the following error message I copied from the BTP cockpit:
Failed update instance request context: map[crm_customer_id: env_type:sapcp global_account_id:d9d2dd55-8f25-4f6f-9175-f620d8ed8412 instance_name:dest_provider license_type:TRIAL origin:sapcp platform:sapcp region:cf-us10 service_instance_id:c451d956-7dde-4966-a2b6-da1fe2f73fa7 signature:RZqOKNSENb9c83nzunCTv5nTwadh84WZy6f7GLSNSwvjrpKqbTJdgB3vQF7lJPMbrIzqoeT0vWku1ilmKtLK3tEWeninlRqGjE8ZIj20aQNLpOltjIonExdEIk8s+1IKfCXZr+ZF73HJjCqM+8qN3A+SkG/xT4x3HAejAQLuC7zIHOyy3wpUFY9pHaw8H28Z46b8gEdW10xQ+TBiXkHbx+JkJ729W8OG0T0cJHl17tDcUNTT26J8qnve5TdFdAgpCOsQII9QPN1Yfki+ea/UGFfuVV80LiIsPaGRHnhJkXy8PFWZ8u8khCBgB6x3I9XVYkGKD5oT0AXgUg8q99S84QT/7OR1JpI2Uy7nK5sAaILsRLox+kfPHczM00zosQaM/FQvnL0AnfdpAPurKiSfyuqJciOAqVGtz25Xi4ssD4SU3l3cCnv/NX0i7rRlk1ngLL2R64ObywVsmEAvbh7jymBShWhcNen2NiqW+m7Nz3KNJoZButLUEHQdBOocfM6mGCyEzC7KQ2T/e3IImOSPIAfewtLsj/zRVgYxigvcHCyCBT5BNlDVwlUXIhpCD4XWghcEwqlaCycDn9UB5QP37nIQO0F7pBRT5sDBWOr78FwvpEJLKQslF0H0jYyDjT/zlvDeQDHVv8+tY+qaAevL+328S8MXdQS96aTF7QTdopM= subaccount_id:805d64ce-2732-40e4-bea4-940ceca48f02 subdomain:btp-provider-quovadis-31341397 zone_id:805d64ce-2732-40e4-bea4-940ceca48f02], instanceID: c451d956-7dde-4966-a2b6-da1fe2f73fa7, planID: b3440416-15f9-11e7-bdac-02667c123456, serviceID: a8683418-15f9-11e7-873e-02667c123456, acceptsIncomplete: true: Status: 500; ErrorMessage: <nil>; Description: Failed to update the destination service instance with the user provided configuration.; ResponseError: <nil>

Then if I rerun the configuration locally this fixes the failed update...

@lechnerc77
For a test, I switched the runner to macos-latest and bingo the flow works....
Feel free to change the runner back to ubuntu-latest to reproduce the bug....
2024-10-10T17:25:32.183Z [INFO]  Starting apply for module.provider_context.btp_subaccount_service_instance.dest_provider
2024-10-10T17:25:32.183Z [DEBUG] skipping FixUpBlockAttrs
2024-10-10T17:25:32.184Z [DEBUG] module.provider_context.btp_subaccount_service_instance.dest_provider: applying the planned Update change
module.provider_context.btp_subaccount_service_instance.dest_provider: Modifying... [id=c451d956-7dde-4966-a2b6-da1fe2f73fa7]
2024-10-10T17:25:34.199Z [DEBUG] provider.terraform-provider-btp_v1.7.0: 2024/10/10 17:25:34 [DEBUG] Waiting for state to become: [succeeded]
module.provider_context.btp_subaccount_service_instance.dest_provider: Still modifying... [id=c451d956-7dde-4966-a2b6-da1fe2f73fa7, 10s elapsed]
2024-10-10T17:25:44.396Z [DEBUG] provider.terraform-provider-btp_v1.7.0: Value switched to prior value due to semantic equality logic: @caller=github.com/hashicorp/terraform-plugin-framework@v1.12.0/internal/fwschemadata/value_semantic_equality.go:91 @module=sdk.framework tf_attribute_path=subaccount_id tf_provider_addr=registry.terraform.io/sap/btp tf_req_id=6568b79a-4017-e9d8-792e-11443b190598 tf_resource_type=btp_subaccount_service_instance tf_rpc=ApplyResourceChange timestamp=2024-10-10T17:25:44.396Z
2024-10-10T17:25:44.396Z [DEBUG] provider.terraform-provider-btp_v1.7.0: Value switched to prior value due to semantic equality logic: @module=sdk.framework tf_provider_addr=registry.terraform.io/sap/btp tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-framework@v1.12.0/internal/fwschemadata/value_semantic_equality.go:91 tf_attribute_path=serviceplan_id tf_req_id=6568b79a-4017-e9d8-792e-11443b190598 tf_resource_type=btp_subaccount_service_instance timestamp=2024-10-10T17:25:44.396Z
2024-10-10T17:25:44.396Z [DEBUG] provider.terraform-provider-btp_v1.7.0: Value switched to prior value due to semantic equality logic: tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-framework@v1.12.0/internal/fwschemadata/value_semantic_equality.go:91 @module=sdk.framework tf_attribute_path=parameters tf_provider_addr=registry.terraform.io/sap/btp tf_req_id=6568b79a-4017-e9d8-792e-11443b190598 tf_resource_type=btp_subaccount_service_instance timestamp=2024-10-10T17:25:44.396Z
2024-10-10T17:25:44.396Z [DEBUG] provider.terraform-provider-btp_v1.7.0: Value switched to prior value due to semantic equality logic: @module=sdk.framework tf_provider_addr=registry.terraform.io/sap/btp tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-framework@v1.12.0/internal/fwschemadata/value_semantic_equality.go:91 tf_attribute_path=id tf_req_id=6568b79a-4017-e9d8-792e-11443b190598 tf_resource_type=btp_subaccount_service_instance timestamp=2024-10-10T17:25:44.396Z
2024-10-10T17:25:44.396Z [DEBUG] provider.terraform-provider-btp_v1.7.0: Value switched to prior value due to semantic equality logic: tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-framework@v1.12.0/internal/fwschemadata/value_semantic_equality.go:91 @module=sdk.framework tf_req_id=6568b79a-4017-e9d8-792e-11443b190598 tf_attribute_path=name tf_provider_addr=registry.terraform.io/sap/btp tf_resource_type=btp_subaccount_service_instance timestamp=2024-10-10T17:25:44.396Z
2024-10-10T17:25:44.396Z [DEBUG] provider.terraform-provider-btp_v1.7.0: Value switched to prior value due to semantic equality logic: @caller=github.com/hashicorp/terraform-plugin-framework@v1.12.0/internal/fwschemadata/value_semantic_equality.go:91 @module=sdk.framework tf_req_id=6568b79a-4017-e9d8-792e-11443b190598 tf_resource_type=btp_subaccount_service_instance tf_attribute_path=timeouts.delete tf_provider_addr=registry.terraform.io/sap/btp tf_rpc=ApplyResourceChange timestamp=2024-10-10T17:25:44.396Z
2024-10-10T17:25:44.396Z [DEBUG] provider.terraform-provider-btp_v1.7.0: Value switched to prior value due to semantic equality logic: tf_req_id=6568b79a-4017-e9d8-792e-11443b190598 @caller=github.com/hashicorp/terraform-plugin-framework@v1.12.0/internal/fwschemadata/value_semantic_equality.go:91 @module=sdk.framework tf_attribute_path=timeouts.update tf_provider_addr=registry.terraform.io/sap/btp tf_resource_type=btp_subaccount_service_instance tf_rpc=ApplyResourceChange timestamp=2024-10-10T17:25:44.396Z
2024-10-10T17:25:44.397Z [DEBUG] provider.terraform-provider-btp_v1.7.0: Value switched to prior value due to semantic equality logic: @module=sdk.framework tf_resource_type=btp_subaccount_service_instance tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-framework@v1.12.0/internal/fwschemadata/value_semantic_equality.go:91 tf_attribute_path=timeouts.create tf_provider_addr=registry.terraform.io/sap/btp tf_req_id=6568b79a-4017-e9d8-792e-11443b190598 timestamp=2024-10-10T17:25:44.396Z
2024-10-10T17:25:44.397Z [DEBUG] provider.terraform-provider-btp_v1.7.0: Value switched to prior value due to semantic equality logic: @module=sdk.framework tf_resource_type=btp_subaccount_service_instance @caller=github.com/hashicorp/terraform-plugin-framework@v1.12.0/internal/fwschemadata/value_semantic_equality.go:91 tf_provider_addr=registry.terraform.io/sap/btp tf_req_id=6568b79a-4017-e9d8-792e-11443b190598 tf_rpc=ApplyResourceChange tf_attribute_path=timeouts timestamp=2024-10-10T17:25:44.396Z
2024-10-10T17:25:44.399Z [DEBUG] State storage *cloud.State declined to persist a state snapshot
2024-10-10T17:25:44.400Z [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-10-10T17:25:44.401Z [INFO]  provider: plugin process exited: plugin=.terraform/providers/registry.terraform.io/sap/btp/1.7.0/darwin_arm64/terraform-provider-btp_v1.7.0 id=2489
2024-10-10T17:25:44.401Z [DEBUG] provider: plugin exited
2024-10-10T17:25:44.402Z [DEBUG] cloud/state: state read serial is: 21; serial is: 21
2024-10-10T17:25:44.402Z [DEBUG] cloud/state: state read lineage is: 2c09f9ca-47dc-a37a-ddbb-de32eaf5183b; lineage is: 2c09f9ca-47dc-a37a-ddbb-de32eaf5183b
module.provider_context.btp_subaccount_service_instance.dest_provider: Modifications complete after 12s [id=c451d956-7dde-4966-a2b6-da1fe2f73fa7]
Apply complete! Resources: 1 added, 1 changed, 0 destroyed.

@ptesny The error you are referring to is stating that the API could not work with parameters you provide. It seems like some encoding of the parameters is done differently on MacOS vs. Linux. This means that the provisioning in the configuration is causing the trouble
First thing that might cause the trouble is that you use colons instead of "=" when assigning the values in the configuration . The official documentation uses the "=", see https://developer.hashicorp.com/terraform/language/functions/jsonencode#examples. Maybe exchanging this might already help
If this doesn't do the trick I would recommend to trim down you destination to less entries to see which change in the entries leads to the invalid JSON that is reported by the API.

That was a tricky one, but good to know


calculator.c

add calculator program in c language

hey ! can you assign me

Assign this to me, I can help.

Can you please assign this issue to me?

I would love to be assigned this task

Check my repository - "Calculate"


Tex Live from tlnet-archive (roollback/pretest)

Hi, at the moment the historical versions of TeX Live are loaded from https://ftp.math.utah.edu/pub/tex/historic/... which stores the last updated version before it freezes and moves to the next version.
In general this is what one wants, but, in some situations it is necessary to test with a specific update date, either because of
kernel, package dependencies or other conflicts.
In texlive.info we can find tlnet-archive whose description is:

"a daily archive of all TeX Live packages updated since 2019-09-01, plus earlier final releases"

from which you can install the versions by year and update date, including the pretest version of this 2024.
I imagine something like:
- uses: teatimeguest/setup-texlive-action@v3
  with:
    version: 2024
    date: 2024/03/04

with which you could use the pretest version, or something like:
- uses: teatimeguest/setup-texlive-action@v3
  with:
    version: 2022
    date: 2022/09/09

so that we can use an earlier version at a specific date.
While I understand the specific meaning is continuous CI integration, I think it would be a good addition (especially in the pretest period of TeX Live).
Saludos

Thanks for the suggestion! It sounds like a good idea.
I would like to add such a functionality, along with #283, to allow more flexibility in specifying a repository (but it might take some time as it would require several changes in the codebase).

This feature has not been implemented yet, but you can now use tlpretest and daily archives by using the repository input:
- name: Use tlpretest
  uses: teatimeguest/setup-texlive-action@v3
  with:
    repository: https://ftp.math.utah.edu/pub/tlpretest/
    version: 2024

- name: Use the archive as of 2024-01-01
  uses: teatimeguest/setup-texlive-action@v3
  with:
    repository: https://texlive.info/tlnet-archive/2024/01/01/tlnet/


Dragonrage: Watch poxo.in

Dragonrage requests the watch of the watch_keyword poxo\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

poxo\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


Install build dependencies before creating operator-gen image

See https://github.com/solo-io/wasme/runs/981348603?check_suite_focus=true

/skip-changelog


fix some syntax and link in the docs

doc: various doc updates

Fix some some old documentation notation for :keyword:, :numref: and :ref: and so on and fix some broken links.
Added new doc on "types" which fans out to all the various topics about types.
Added some examples to lexical_structure and removed some unnecessary back ticks inside triple back-ticked blocks there (which may also have been a carry over from other doc formats).
Added missing documentation of \uxxxx syntax.
Added missing documentation on Floating point literal syntax.

Note that it's not clear to me if we should even keep the "Lexical Structure" chapter (in its current form) since Lean 4's approach is so radically different from Lean 3's, but this is certainly an improvement.

Note that it's not clear to me if we should even keep the "Lexical Structure" chapter (in its current form) since Lean 4's approach is so radically different from Lean 3's, but this is certainly an improvement.

Every new programming language needs to explain the basic syntax to new users.  I found this kind of information critical to understanding how to read lean code.     What is your concern?  Is it because the syntax is also extensible?  We could add more of a pointer to that concept in this chapter then point to syntax.md.


STACK_ as prefix; wrong case in dir; NAME instead of PROJECT

:wave:
I personally prefer TITILER_ as prefix instead of STACK_, if you agree I can change the PR to use TITILER_. But as it is it make things consistent with STACK_.

@fredliporace thanks for this PR.
I think it will be good to use TITILER_STACK instead of STACK or TITILER.
https://github.com/developmentseed/titiler/blob/c952bd445e545bc8390c413d5f6fb0b6258dd071/deployment/AWS/cdk/config.py#L71
we can also change the env of the API to TITILER_API (instead of API)
https://github.com/developmentseed/titiler/blob/c952bd445e545bc8390c413d5f6fb0b6258dd071/titiler/settings.py#L27

@vincentsarago I was working on a branch based on 0.1.0a14 and commiting simple documentation updates I flagged while updating my own deployment. Changing to TITILER_API seems to affect some testing and in my environment the testing fails for some reason I have to investigate... This last commit seems to be cover all the needed changes but right now I'm unable to run all tests locally as I would like.

@fredliporace the tests seems to work on CI 🤷
Maybe I'll wait for you to 👍 before merging.

@fredliporace the tests seems to work on CI
Maybe I'll wait for you to  before merging.

I like to run the testing locally and on my repo CI before submitting the PR. Seems to be OK.

@fredliporace run the test on my computer and everything looks 👌. I'll merge this great PR 🙏


Write documentation for the proof generation

📚 Context
The proof generation is very cryptic, and I have explained it multiple times, but we need a de-facto reference.
✔ Solution
Write documentation explaining the proof generation.
Here is the diagram for the proof generation from our former Miro board.
Rollups (1).pdf
📈 Subtasks

[ ] Write documentation.

The rollups proofs will change completely in https://github.com/cartesi/rollups-contracts/issues/86


Track and report on transactions

Query log:
begin
update tblA set apa = 'toto' where foo = 12 and id = 43;
update tblB set monkey = 'pippi' where bar = 12 and id = 44;
commit
begin
update tblA set apa = 'toto' where foo = 43 and id = 5;
update tblB set monkey = 'pippi' where bar = 43 and id = 16;
commit

begin
insert user (id, name) values (1, 'toto');
insert user_extra (user_id, age) values (1, 666);
commit

Report:
Transaction Pattern:
1: 66%
 tblA WHERE foo = <1> AND id = <2>
 tblB WHERE bar = <1> and id = <3>

2: 33%
user WHERE id = <1>
user_extra WHERE user_id = <1>

Fixed with #63


Feature/sorted imports

Running yarn lint will now run prettier with improved imports.
For instance, SwapWidget imports will look like this:
import { useState, FormEvent, useEffect } from "react";
import { useTranslation } from "react-i18next";
import Modal from "react-modal";

import { findTokenByAddress } from "@airswap/metadata";
import { toDecimalString } from "@airswap/utils";
import { toAtomicString } from "@airswap/utils";
import { useMatomo } from "@datapunt/matomo-tracker-react";
import { Web3Provider } from "@ethersproject/providers";
import { useWeb3React } from "@web3-react/core";

import { BigNumber } from "ethers";
import { parseUnits } from "ethers/lib/utils";

import { useAppSelector, useAppDispatch } from "../../app/hooks";
import Timer from "../../components/Timer/Timer";
import TokenSelection from "../../components/TokenSelection/TokenSelection";
import { Title, Subtitle } from "../../components/Typography/Typography";
import {
  requestActiveTokenAllowances,
  requestActiveTokenBalances,
} from "../../features/balances/balancesSlice";
import {
  selectBalances,
  selectAllowances,
} from "../../features/balances/balancesSlice";
import {
  selectActiveTokens,
  selectAllTokenInfo,
  addActiveToken,
  removeActiveToken,
} from "../../features/metadata/metadataSlice";
import {
  approve,
  request,
  take,
  selectBestOrder,
  selectOrdersStatus,
} from "../../features/orders/ordersSlice";
import {
  SubmittedApproval,
  selectTransactions,
} from "../../features/transactions/transactionsSlice";
import { setActiveProvider } from "../../features/wallet/walletSlice";
import WalletProviderList from "../WalletProviderList/WalletProviderList";
import StyledSwapWidget, {
  Header,
  QuoteAndTimer,
  StyledTokenSelect,
  SubmitButton,
} from "./SwapWidget.styles";

This is great. For some reason though the yarn command doesn't seem to match some of the files for me - I can't understand why.
Files not matched include:

src/components/TokenSelection/filter.ts
src/components/TokenSelection/sort.ts
src/features/balances/balancesSlice.ts
src/features/metadata/metadataApi.ts
src/features/metadata/metadataSlice.ts
src/features/metadata/metadataSubscriber.ts
src/features/orders/orderAPI.ts

(There are others).
If you run yarn lint then stage the changes and afterwards run prettier --write ./src, do you end up with further (i.e. unstaged) changes?
Regardless, to me it makes sense just to use ./src as the prettier argument as it will only deal with the files that it understands how to format.
I also wrote a test that checks if all files have been formatted by prettier with the idea that they will fail CI checks on PRs if they haven't. I didn't want to commit this without discussion though, but the code is here:
// ./src/prettier.spec.ts

import { exec } from "child_process";

jest.setTimeout(20000);

describe("Prettier conformance", () => {
  it("all files should have been formatted by prettier", (done) => {
    exec(
      "prettier --check ./src --plugin @trivago/prettier-plugin-sort-imports",
      (err) => {
        expect(err).toBeNull();
        done();
      }
    );
  });
});


Is linting possible?

Hi! Thank for this plugin - very useful having syntax highlighting in my Bicep files 🙂
I have no idea what's involved with lining - so this might be a silly question - but when vscode gives very powerful linting functionality when editing Bicep files. Is this even possible with Vim?

Hey!
Glad you find it as useful as I do! :slightly_smiling_face:
You have great timing, I just added a configuration for Bicep in the lint engine ALE. If you install that, messages should pop up in your editor out of the box as long as you have bicep installed. I messed it up a bit so it currently shows all module imports as errors, but that will be fixed when this is merged: https://github.com/dense-analysis/ale/pull/4311.

Magic! That works! ❤
I haven't used it properly yet - it does seem to be showing warnings for bicep module references where the reference definitely exists on the file system - but that's probably me not fully reading the docs yet :)
Eg...

That will be fixed by the PR I linked above :)
Feel free to give it a thumbs up!

Ah sorry! I totally misread what you meant above! 🤦♂
Added both 👍 and ❤ ! :)

Another instance where I feel Github needs this...
https://twitter.com/dracan/status/1570363060967346177
:)


PYIC-5759: add parsed claimsSet property to VerifiableCredential class

Proposed changes
What changed

adds parsed claimsSet property to VerifiableCredential class which uses the new VerifiableCredentialParser
updates some unit tests to use stub data that is more representative of real VCs

Why did it change
Making a property available for the parsed claimsSet will make it easier to access the properties within it as currently, they are only accessible as JSON objects. Using the parser means we can enforce stricter type checking on the VCs and easier access to the properties.
Issue tracking

PYIC-5759

Some broken things that need to be further investigated + fixed:

Passport CRI consumer tests in the process-cri-callback lambda are failing
Failing unit tests: buildScoreShouldReturnCorrectScoreForDcmawCredential and getContraIndicatorsVCJwtThrowsErrorWhenNoVcBlock which I think is the reason test-java is failing int he pipeline


object propertyNames support

OpenAPI v3.1 supports the ability to configure an object schema with propertyNames that can restrict the property keys allowed for an object. A common case is where an enum schema is used as the list of available properties on an object.
See this StackOverflow article for instance: https://stackoverflow.com/questions/46552863/how-to-write-openapi-3-swagger-specification-for-property-name-in-map-object/46553255#46553255
I notice that there is no ability to configure propertyNames in the ObjectBuilder, and I also notice that the ToSchema derive macro does not properly handle the case of an object or map type such as HashMap<MyEnum, MyValue> where the key type is a Rust enum of unit variants. Adding in the support for propertyNames into the spec implementation first would be a good start, followed by the proper handling of the ToSchema derive macro for a type that looks like this (notice the new usage of additional_properties too, to handle Refs and not just FreeForm):
#[derive(ToSchema)]
enum MyEnum {
    VariantOne,
    VariantTwo,
}

#[derive(ToSchema)]
struct MyValue {
    x: i32,
    y: i32,
}

#[derive(ToSchema)]
struct MySchema {
    #[serde(flatten)]
    #[schema(additional_properties = MyValue)]
    properties: HashMap<MyEnum, MyValue>,
}

which generates an object schema that looks like this:
{
  "type": "object",
  "propertyNames": {
    "enum": ["VariantOne", "VariantTwo"]
  },
  "additionalProperties": {
    "$ref": "#/components/schemas/MyValue"
  }
}

I am running into a similar situation, where I end up with:
my-field:
  type: object
  additionalProperties:
    $ref: '#/components/schemas/BTreeSet'

And it seems there's no way to override the of additionalProperties.

This would be nice to have. Or is there a  way to achieve something similar? I am trying to use a HashMap<MyEnum, bool>

Since utoipa is moving to OpenAPI 3.1 from 5.0.0 version onwards this seems to be quite reasonable thing to implement to further enhance map support.


chmod .gotron/assets: operation not permitted

Hi
A new problem was just found using Goland IDE on Mac with Gotron.
When running the application I get this panic message:
chmod .gotron/assets: operation not permitted:
.gotron and .gotron/assets both have 777 permissions.
What can I do about this issue?
Thanks

same issue here

I had the same problem with GoLand on Linux. Solved it by changing permissions (in my case 644) on the next level lower directory 'js' and any files that were in that directory.


Create Test Tools To Allow Developing Individual Armada Components In Isolation

Traditionally all Armada development has been done by running the entire armada system.  As Armada becomes larger and more complex, this becomes increasingly difficult to do.  instead, as each subcomponent has a well defined role and a clear interface it should be possible to develop them in isolation.
As an example consider Lookout development.  This could be done either by just having a tool to populate the database (in which the only components needed is sql server) or alternatively by also running lookout-ingester and pulsar and just having a tool to publish messages onto pulsar.
Each component probably needs analysis to see what it would need, but I think we could get a long with with:
a) having some easy way of starting up a subset of components
b) having an easy tool to publish messages onto pulsar
c) having an easy tool to view messages on pulsar
d) having an easy tool to directly put data into the lookout db.

Hey team! Please add your planning poker estimate with Zenhub @suprjinx @dejanzele @richscott @kannon92 @jayofdoom

Convert this epic.

This ticket has been converted to an epic - see the epic "Test Tools for Component Development" at
https://app.zenhub.com/workspaces/armada-62c744dc3b819100132ca032/epics?activeEpic=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMTA2MDcz&state=OPEN&state=TODO&state=IN_PROGRESS


Make backoff cap configurable

The current backoff algorithm is quite effective, but I think it would benefit from supporting configuration of the 'cap' used for the time limit. It's very possible a cluster of proxies could go down for several days, but the fixed cap used at present ensures they'll be checked around once every half hour at minimum, which isn't terribly sensible in this use case.
The fix would be to simply support the ROTATING_PROXY_BACKOFF_CAP setting, which would be used in the same way as the existing ROTATING_PROXY_BACKOFF_BASE to initialize the backoff function.

Yeah, a good suggestion. +1 to add this option.

Fixed by https://github.com/TeamHG-Memex/scrapy-rotating-proxies/pull/10 - thanks @petermoore14!


Firestore crashed when call addDocument

I'm using iOS SDK 4.3.0. Install everything manually (not Cocoapods).
When trying these codes
        let db = Firestore.firestore()
        var ref: DocumentReference? = nil
        ref = db.collection("users").addDocument(data: [
            "first": "Ada",
            "last": "Lovelace",
            "born": 1815
        ]) { err in
            if let err = err {
                print("Error adding document: \(err)")
            } else {
                print("Document added with ID: \(ref!.documentID)")
            }
        }

the app crashed with following logs
2017-10-08 01:51:01.873555+0200 Manu[20434:364081] +[FSTImmutableSortedSet keySet]: unrecognized selector sent to class 0x1006ddda0
2017-10-08 01:51:01.940053+0200 Manu[20434:364081] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[FSTImmutableSortedSet keySet]: unrecognized selector sent to class 0x1006ddda0'
*** First throw call stack:
(
	0   CoreFoundation                      0x000000010247e1cb __exceptionPreprocess + 171
	1   libobjc.A.dylib                     0x0000000101de0f41 objc_exception_throw + 48
	2   CoreFoundation                      0x00000001024fe854 +[NSObject(NSObject) doesNotRecognizeSelector:] + 132
	3   CoreFoundation                      0x0000000102401178 ___forwarding___ + 1432
	4   CoreFoundation                      0x0000000102400b58 _CF_forwarding_prep_0 + 120
	5   Manu                                0x00000001004d2a5f -[FSTMutationBatch keys] + 61
	6   Manu                                0x00000001004be8d8 -[FSTLocalStore locallyWriteMutations:] + 300
	7   Manu                                0x00000001004a66b9 -[FSTSyncEngine writeMutations:completion:] + 112
	8   Manu                                0x00000001004a00b2 __48-[FSTFirestoreClient writeMutations:completion:]_block_invoke + 181
	9   libdispatch.dylib                   0x00000001062b13f7 _dispatch_call_block_and_release + 12
	10  libdispatch.dylib                   0x00000001062b243c _dispatch_client_callout + 8
	11  libdispatch.dylib                   0x00000001062ba95b _dispatch_queue_serial_drain + 1162
	12  libdispatch.dylib                   0x00000001062bb2df _dispatch_queue_invoke + 336
	13  libdispatch.dylib                   0x00000001062b707d _dispatch_queue_override_invoke + 733
	14  libdispatch.dylib                   0x00000001062be1f9 _dispatch_root_queue_drain + 772
	15  libdispatch.dylib                   0x00000001062bde97 _dispatch_worker_thread3 + 132
	16  libsystem_pthread.dylib             0x00000001067755a2 _pthread_wqthread + 1299
	17  libsystem_pthread.dylib             0x000000010677507d start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException

Install Firebase/Core & Firebase/Firestore again using Cocoapods, I have no crash anymore. Maybe the binary framework files are corrupted?

Are you linking in all the dependent libraries for Firestore as described by the README?
Firestore (~> Analytics)

BoringSSL.framework
FirebaseAuth.framework
FirebaseFirestore.framework
GTMSessionFetcher.framework
Protobuf.framework
gRPC.framework
gRPC-Core.framework
gRPC-ProtoRPC.framework
gRPC-RxLibrary.framework
leveldb-library.framework

Analytics

FirebaseAnalytics.framework
FirebaseCore.framework
FirebaseCoreDiagnostics.framework
FirebaseNanoPB.framework
FirebaseInstanceID.framework
GoogleToolboxForMac.framework
nanopb.framework

Yes, I linked everything as you said, and also the libstdc++ so that I can compile.

@peacemoon can you share your project?

Reopen if still an issue.

Im have the same problem :S

@ingscjoshua, we've been unable to reproduce this issue internally. Could you share your project with us so we can debug it?

I'm also seeing this crash, though not sure it's exactly the same (I can create a new issue if not). My console when calling addDocument is
[Firebase/Core][I-COR000025] FIRAuth getUID implementation wasn't set. and the crash is in the thread in gRPC.

That points very strongly toward your project not having FirebaseAuth.framework installed. The crash in gRPC seems like a different symptom though, because the default is just to act like everything is unauthenticated.
However, if you're using Firebase 4.10.0, there's a critical regression in Firestore in that release so I'd wait for the hotfix we're spinning before putting much effort into a repro.

Thanks, I'll wait for the hotfix to look into it deeper.
On Thu, Mar 8, 2018 at 11:31 PM, Gil<EMAIL_ADDRESS>wrote:

That points very strongly toward your project not having
FirebaseAuth.framework installed. The crash in gRPC seems like a different
symptom though, because the default is just to act like everything is
unauthenticated.
However, if you're using Firebase 4.10.0, there's a critical regression in
Firestore in that release so I'd wait for the hotfix we're spinning
https://github.com/firebase/firebase-ios-sdk/commits/release-4.10.1
before putting much effort into a repro.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-ios-sdk/issues/344#issuecomment-371735594,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMdd9L_f_youkQIM4v6j6VdY6r8VxUaks5tci-9gaJpZM4PxiUv
.

--
Seth Sandler

Blog: sethsandler.com
Twitter: www.twitter.com/sethsandler
Linkedin: http://www.linkedin.com/in/sethsandler
Skype: sethsandler

@cerupcat Firebase 4.10.1 is now available.

Thanks @paulb777. I'm still seeing the same issue. Not sure if I should open a new issue or not. After I call addDocumentWithData, I get a crash inside BoringSSL.

@cerupcat can you open a new issue with the full stack trace and, if possible, a demo project that reproduces the issue?

@morganchen12 Will do. Thanks.

I am facing same issue.
I don't use cocoapods.
Are there any solution?
2018-04-08 14:22:53.719122+0900 Telegram[45558:1669067] +[FSTImmutableSortedSet keySet]: unrecognized selector sent to class 0x105966408
2018-04-08 14:22:53.724536+0900 Telegram[45558:1669067] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[FSTImmutableSortedSet keySet]: unrecognized selector sent to class 0x105966408'
*** First throw call stack:
(
	0   CoreFoundation                      0x000000010720a1cb __exceptionPreprocess + 171
	1   libobjc.A.dylib                     0x0000000106b6cf41 objc_exception_throw + 48
	2   CoreFoundation                      0x000000010728a854 +[NSObject(NSObject) doesNotRecognizeSelector:] + 132
	3   CoreFoundation                      0x000000010718d178 ___forwarding___ + 1432
	4   CoreFoundation                      0x000000010718cb58 _CF_forwarding_prep_0 + 120
	5   Telegram                            0x00000001058156c2 -[FSTMutationBatch keys] + 60
	6   Telegram                            0x00000001057fc27d -[FSTLocalStore locallyWriteMutations:] + 286
	7   Telegram                            0x00000001057e0c1d -[FSTSyncEngine writeMutations:completion:] + 113
	8   Telegram                            0x00000001057d8795 __48-[FSTFirestoreClient writeMutations:completion:]_block_invoke + 184
	9   Telegram                            0x0000000105833ea3 -[FSTDispatchQueue enterCheckedOperation:] + 81
	10  libdispatch.dylib                   0x000000010a4933f7 _dispatch_call_block_and_release + 12
	11  libdispatch.dylib                   0x000000010a49443c _dispatch_client_callout + 8
	12  libdispatch.dylib                   0x000000010a49c95b _dispatch_queue_serial_drain + 1162
	13  libdispatch.dylib                   0x000000010a49d2df _dispatch_queue_invoke + 336
	14  libdispatch.dylib                   0x000000010a49907d _dispatch_queue_override_invoke + 733
	15  libdispatch.dylib                   0x000000010a4a01f9 _dispatch_root_queue_drain + 772
	16  libdispatch.dylib                   0x000000010a49fe97 _dispatch_worker_thread3 + 132
	17  libsystem_pthread.dylib             0x000000010a9575a2 _pthread_wqthread + 1299
	18  libsystem_pthread.dylib             0x000000010a95707d start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException

please help @morganchen12

@hiragram can you make a new issue and share the project?

Same issue for me. Any Firestore read or write operation leads to crashing. Any fix so far @morganchen12 @hiragram ?

@kiranb47 This issue was closed as we were never able to reproduce it. If you have a way to reproduce it, please open a new issue and include a repro project and we'll be happy to take a look. Thanks!


Update README.md

correct link to TIP OC page
added link to ocforum

No longer need. Closing this.


Battery consumption

Longer battery life by not updating the screen every second. Instead back to every minute - it is enough.
Real quickview support instead that hacky animation trick. https://developer.pebble.com/guides/user-interfaces/unobstructed-area/

Maybe the minutes will not tick excactly on real minute change so that 9:00 is half time on the bottom, half on the top


Zero-byte SECTIONS print differently in the .map file

From pokecrystal:
ROM0 bank #0:
  SECTION: $0000-$ffffffff ($0000 bytes) ["NULL"]
           $0000 = NULL

I would expect $0000 not $ffffffff, which matches the valid address space and would not break existing parsemap.py and parsemap.c tools.

This seems like an evil case of underflow.

The problem is that the range boundaries are inclusive, so there is no valid number for the upper bound. (Try a 1-byte section at $0000 and you'll see)
Best I can do is only print the upper boundary, but I'll still break some tools.

Perhaps $FFFF would be better than $FFFFFFFF... although I agree that the only sensible implementation is to show no end point at all.

No end point sounds like the best option to me too. It would require some tool updates, but actually the changes of ROM Bank to ROM0 bank/ROMX bank and $0001 bytes to $0001 byte also broke parsemap.py, so may as well break it some more.


chore: bump version

Checklist

[ ] JIRA - <link>
[ ] Proper tests implemented
[ ] Screenshots added.

Proposed solution
Explain how does this PR solves the problem stated in JIRA ticket.
You can also enumerate different alternatives considered while approaching this task.
Testing
Describe here, how the new implementation can be tested.
Provide link or briefly describe User Acceptance Criteria/Tests that need to be met
Screenshots
Attach screenshots here if implementation involves some UI changes

coverage: 52.934%. remained the same
when pulling 0aaa24ff18a739f30e0e5697c343473d0c273076 on chore/bump-version
into 53cb5030131fc10bc8b99ad0a7b3a48ab80ba4be on release/extension/1.8.x.


Shuffle vs. Select Mode

As a larger feature, I'd like to make a workflow that instead of randomly selecting a few, you're able to pick from a list after initially fetching.
This way you can get those results and check if particular items are available.

This will require a pretty significant refactor of certain things, so I'll outline key areas that need to be adjusted to make this happen:
Routing
I'm thinking we may want to introduce routing or a new page. It may be possible to keep this all a single page, but it might end up a little too complicated to switch up the behavior of buttons. This will be a decision to make: new search page or some dynamic toggle.

Counterpoint: It could be simple enough to hide/show the search bar w/ results based on a toggle, and then determine a different path for the Results components.

Shelf Data Refactor
Need to update the cached data from a shelf from a List into a typed dictionary to ensure we have a O(1) search vs. O(n).

Thinking the datastore will be a dictionary, where the key is the "Title - Author", and the value is the Book object
When in Shuffle mode, it will randomly select from the dictionary's values
When in Select mode, you will pick from the dropdown, and the list that you've selected will be displayed.

App Considerations

Return all of the results to the browser for search mode? Or query BE given a list of values when selecting each?

Analytics Considerations

New column on "shelf_searches" to represent what "mode" the search was done in
In the above app considerations, may want to keep things in the BE so the FE doesn't need to send an event.

Don't want to expose analytics topics or creds
Keeps the emission of events from the BE and not the client/browser

How to track books in the database - Likely want to only track those that are "selected" by the UI, which might necessitate calling the BE with the list


Updated Tachyon and Spark versions in Vegrant config and doc

Updated the Tachyon and Spark versions in the Vagrant configuration and documentation
Tachyon version: 0.5.0 => 0.6.4
Spark version: 1.3.1 => 1.4.0

Can one of the admins verify this patch?

thanks for so instance update since spark just releases 1.4.0.
but it may have merge conflict with PR:https://github.com/amplab/tachyon/pull/983 which rewrites documentation.

+1 LGTM

Jenkins, test this please.

ok to test

@uronce-cc I will update again if #983 overwrites.


Added reverse order capability

Hey @casvanluijtelaar , thank you for this amazing library. I took the chance to implement the reverse order feature and since I wasn't able to run the project with the latest Android Studio version, I bumped the Android dependencies to support API 33.
Let me know if everything is ok from your point of view
Fixes #41

normally I'd leave the dependency/constraint updates to a separate PR, but I am extremely busy, so we can include them here.
Looks good, simple fix, works fine. make sure you dart format . the project. and it can be merged
LGTM

normally I'd leave the dependency/constraint updates to a separate PR

I agree, but I couldn't properly run the project without bumping them.
Code reformatted as requested! :rocket:

available in 1.1.7