Service Discovery on CF

On our platform, which will be based on PCF, we will introduce a new component that will work together with our buildpack to expose and secure APIs (you can think of it as a Micro Gateway). In order to configure those gateways a webbased UI will be introduced that should know about all our custom buildpack applications that are pushed to PCF and expose APIs. Ideally speaking every time an app gets pushed to PCF it should also notify the webbased UI that a new API is available (something like service discovery).
I know PCF has Etcd component which is used for Service Discovery but can we use it to push application cluster details to this custom webbased UI ?
The other part of the question is that the webbased UI will create a new app that will in turn expose an API as well. That new app will be exposed to the outside world and route traffic to the pushed  application (our buildpack apps) offcourse after applying some policies. Would that be possible to do with PCF?

Hi @roagarwal, if you're a PCF customer please visit http://support.pivotal.io.
Best,
@zaksoup, CF Release Integration

@roagarwal - Are you a PCF customer?  If so, Pivotal's support should be able to answer your questions.


feat: add new type Store in content

To complete more custom features of the content store. We need to wrap the content.store to call the function inner store.
Changes:

Add new type Store to wrap content.store.
Move UpdateTime call from fetch to Store.ReaderAt.

Reference: https://github.com/goharbor/acceleration-service/issues/141.

@imeoer PTAL.


Add CheckTaskCancellation

Following the discussion #221, this PR proposes to add a trivial CheckTaskCancellation parser/printer that can early-out parsing if the parent task is canceled. It is used as one would use try Task.checkCancellation(), that is before a potentially lengthy operation:
Many {
  CheckTaskCancellation()
  Parse {…}
}

This gives the user the possibility to perform these checks where and when it is relevant.
I find the enclosing or fluent alternative discussed in #221 more difficult to understand because of the parser they should be applied to. Users using Tasks should likely be familiar with this PR's construct.
This doesn't fix the issue of parsing 100 millions integers. In this case, we would only want to perform the checks every 10000 integers for example, but the CheckTaskCancellation style doesn't allow this. It is probable that we can build something that does this with existing combinators. I had a potential implementation that made CheckTaskCancellation a class with a counter, and some API like CheckTaskCancellation(every: 10000), but I was worried about the added complexity for the user (this situation only occurs in a Many, but the argument is there all the time and can be used where it doesn't make sense). And there was an issue with making it Sendable, locks & performance. So for now, I have no solution to propose for this configuration.
In order to test it, we generate a very long string of "1,1,1,…" and ask a Many parser to process it in a Task. Quickly after the beginning of the execution, we cancel the Task and check how much it processed. Since the parsing was aborted, the expected count should be lower than the input's size. If we remove the check, parsing continues for a few seconds and all the input is processed. On my machine, it passes in ~0.1s, parsing ~1/10th of the input, and fails in ~4s. ~This gives some room ahead and shouldn't be too flaky~ [Downloading Xcode from CI to check what's going on]. There is maybe a better way to test it.
This makes me wonder if we should backtrack when we exit processing, because we have a parser that threw and consumed the input.

It seems there is a bug they fixed since Xcode 13.2.1 and OS of this time. With the current code and this version of Xcode testing on iOS of this time, the task execution is blocking and .cancel() is called only once it's finished. If I switch to Mac, it uses my up to date Monterey runtime, the task is not blocking, cancel is called fairly quickly and the test passes. If this is a known bug, it's maybe worth adding a note in the documentation that this parser has no effect on such systems. Or we can limit the availability to these versions.

@tgrapperon My main first thought at this point is to generalize. It seems like it would be useful to insert arbitrary Void effects into parsers in general. Spitballing syntax:
Do { try Task.checkCancellation() }

While the overhead of the escaping closure may not be ideal, it also may be minimal in the body style of parser we've been exploring.
I'm not sure we're ready to dive into the design space here before having the time to think about it and explore it more, though! Just some thoughts in the meantime :smile:

@stephencelis Thanks for the feedback. I guess it also opens the way to some kind of pre/post actions for parsers, but right now, and without some kind of Environment/Context to pass the information along, uses seem fairly limited to global stuff like Task cancellation or logging. We can capture something of course, but it would be nice if built-in parsers could pass relevant information along, like the current count in a Many, etc. If user-defined properties are allowed, the usual issue with environmental stuff is the cost induced by handling dictionaries, but we can maybe take some inspiration from the way AttributedString are composing attributes.
I'm closing the PR for now then. The failing test remains a mystery. I don't understand why it passes on my Mac but fails on an iPhone with similar OS/Swift versions, and on older macOS/Swift versions.

@stephencelis BTW, a similar pattern forms in TCA with protocolized reducers, where something that was before a wrapper of a Reducer can become an independent, elemental reducer that can be chained/zipped with a "base" reducer. For example, if the Binding() reducer is a reducer that only reduces binding actions and does nothing otherwise, the .binding() reducer can be rewritten as[^1]:
Reduce {
  Binding()
  Upstream()
}

[^1]: In the proto-2 experiments at https://github.com/tgrapperon/swift-composable-architecture/commits/reducer-modifier, I compare both approaches.
This is very nice, because it offers the possibility to compose/break down reducers functionalities:
Reduce {
  Animation()
  Binding()
  Upstream()
  Debug()
}

I wonder if some existing combinators can also be broken into elemental ones.
It can be interesting to draw parallels between swift-parsing and TCA during your reflections around Do {}.


Can use uber-go/zap to replace log15? if it is yes, I can provide a pull request

log15 is  inactive for a long time.
Can use uber-go/zap to replace log15? if it is yes, I can provide a pull request.

I wouldn't be opposed to improving performance as long as it can be done
without changing the current logger interface definition, and can provide a
similar non breaking configuration options.
Let me know if that is possible before starting any work. One of the issues
we had with log15 was being able to set the debit frame properly so it
would report the correct long numbers, this may be an issue in zap as well.
On Dec 15, 2017 5:13 AM, "runner"<EMAIL_ADDRESS>wrote:

log15 is inactive for a long time.
Can use uber-go/zap to replace log15? if it is yes, I can provide a pull
request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/revel/revel/issues/1282, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUsBgCxDYDKAlUJKqp_3CzoD69dcG03ks5tAnBpgaJpZM4RDdmS
.

zap has a  https://godoc.org/go.uber.org/zap#AddCallerSkip Option, it is increases the number of callers skipped.

Are you working on this @runner-mei ?

No, I waiting for your confirm

I will working it at this weekend

Sounds good - like I said earlier all that I am concerned about is that the Multilogger interface remains unchanged and that the configuration settings for it remains the same.

@runner-mei any luck with this?

I'm closing this issue for now, I want to make the current logger interface less reliant on log15 for the interfaces but for now zap logger is a heavier implementation - I created a start of a gist but if you want to remain perfectly agnostic use the logger.HandlerFunc to perform your own logging.


New version: Nextcloud.NextcloudDesktop version 3.12.2

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

2024-03-21T00:21:44.7222958Z ##[error] Manifest Error: DisplayVersion declared in the manifest has overlap with existing DisplayVersion range in the index. Existing DisplayVersion range in index:  [ [<IP_ADDRESS>40306, <IP_ADDRESS>40306]]

(Automated response - build 870.)


add constant lines

Enable adding of constant lines on both axes
Added parameter 'constantLines' on both yAxes and xAxes
Sample :
options:{
	scales:{
		xAxes:[{
			constantLines:[0.1]
		}],
		yAxes:[{
			constantLines:[0.25,0.50,0.75]
		}]
	}
}

Nice! I am looking for this function, but could that be a constant number instead of %?

Please rebase this PR so that we can merge without conflicts.

Closed because out of date


flutter run --release stuck when building for iOS: "library not found for -lPods-Runner"

My flutter run --release for my iPhone is stuck at:
~/Code/hello_cupertino[master*] $ flutter run --release
Launching lib/main.dart on flutter 6s in release mode...
Traceback (most recent call last):
  File "/tmp/fruitstrap_d83d5bc53967baa0ee18626ba87b6254b2ab5418.py", line 35, in run_command
    lldb.target.Launch(lldb.SBLaunchInfo(shlex.split(args[1] and args[1] or '--enable-dart-profiling')), error)
IndexError: list index out of range

Any ideas?
~/Code/hello_cupertino[master*] $ flutter --version
Flutter • channel master • git@github.com:flutter/flutter.git
Framework • revision a0f0c42fe3 (64 minutes ago) • 2017-01-31 14:48:48
Engine • revision 2d54edf0f9
Tools • Dart 1.22.0-dev.9.1

and
~/Code/hello_cupertino[master*] $ flutter doctor
[✓] Flutter (on Mac OS, channel master)
    • Flutter at /Users/sethladd/Code/flutter
    • Framework revision a0f0c42fe3 (64 minutes ago), 2017-01-31 14:48:48
    • Engine revision 2d54edf0f9
    • Tools Dart version 1.22.0-dev.9.1

[✓] Android toolchain - develop for Android devices (Android SDK 25.0.0)
    • Android SDK at /Users/sethladd/Library/Android/sdk
    • Platform android-25, build-tools 25.0.0
    • Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

[✓] iOS toolchain - develop for iOS devices (Xcode 8.2.1)
    • XCode at /Applications/Xcode.app/Contents/Developer
    • Xcode 8.2.1, Build version 8C1002

[✓] IntelliJ IDEA Community Edition (version 2016.3.1)
    • Dart plugin version 163.9166.22
    • Flutter plugin version 0.1.4

[✓] Connected devices
    • flutter 6s • d83d5bc53967baa0ee18626ba87b6254b2ab5418 • ios • iOS 10.1.1 (14B100)

Hm, apparently when you don't have all the necessary signing mumbo jumbo under the General tab of the Project build settings, you can hang flutter run like this.
For those folks also running into this:

I somehow opened up the project settings for my app.
Then I selected "Runner" under "TARGETS".
Then I selected "General" from the horizontal list of options (general, capabilities, etc)
Then I found "Signing" and ensured I unchecked "automatically manage signing"
Then I found "signing (debug)" and ensured my "provisioning profile" was correct.
I did the same for "Signing (Release)"

Now I get this error:
Ld /Users/sethladd/Code/hello_cupertino/build/ios/Debug-iphoneos/Runner.app/Runner normal arm64
    cd /Users/sethladd/Code/hello_cupertino/ios
    export IPHONEOS_DEPLOYMENT_TARGET=8.0
    export PATH=""
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch arm64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS10.2.sdk -L/Users/sethladd/Code/hello_cupertino/build/ios/Debug-iphoneos -L/Users/sethladd/Code/hello_cupertino/ios/Flutter -F/Users/sethladd/Code/hello_cupertino/build/ios/Debug-iphoneos -F/Users/sethladd/Code/hello_cupertino/ios/Flutter -filelist /Users/sethladd/Code/hello_cupertino/build/ios/Runner.build/Debug-iphoneos/Runner.build/Objects-normal/arm64/Runner.LinkFileList -Xlinker -rpath -Xlinker @executable_path/Frameworks -miphoneos-version-min=8.0 -dead_strip -Xlinker -object_path_lto -Xlinker /Users/sethladd/Code/hello_cupertino/build/ios/Runner.build/Debug-iphoneos/Runner.build/Objects-normal/arm64/Runner_lto.o -Xlinker -export_dynamic -Xlinker -no_deduplicate -fobjc-arc -fobjc-link-runtime -ObjC -ObjC -framework Flutter -lPods-Runner -Xlinker -dependency_info -Xlinker /Users/sethladd/Code/hello_cupertino/build/ios/Runner.build/Debug-iphoneos/Runner.build/Objects-normal/arm64/Runner_dependency_info.dat -o /Users/sethladd/Code/hello_cupertino/build/ios/Debug-iphoneos/Runner.app/Runner

ld: library not found for -lPods-Runner
clang: error: linker command failed with exit code 1 (use -v to see invocation)

cc @cbracken have you heard of this issue?

Update:
I create a new Flutter project (via flutter create), and when I try to run that on my iPhone, I see this error:
~/tmp/foobar $ flutter run
Launching lib/main.dart on flutter 6s in debug mode...
Traceback (most recent call last):
  File "/tmp/fruitstrap_d83d5bc53967baa0ee18626ba87b6254b2ab5418.py", line 35, in run_command
    lldb.target.Launch(lldb.SBLaunchInfo(shlex.split(args[1] and args[1] or '--enable-dart-profiling --enable-checked-mode')), error)
IndexError: list index out of range
Exception from flutter run: Exception: Timeout while attempting to retrieve Uri for Observatory
package:flutter_tools/src/base/common.dart 30         throwToolExit
package:flutter_tools/src/protocol_discovery.dart 55  ProtocolDiscovery.nextUri.<async>.<fn>
===== asynchronous gap ===========================
dart:async                                            _Future.timeout
package:flutter_tools/src/protocol_discovery.dart 53  ProtocolDiscovery.nextUri.<async>
===== asynchronous gap ===========================
dart:async                                            Future.Future.microtask
package:flutter_tools/src/protocol_discovery.dart     ProtocolDiscovery.nextUri
package:flutter_tools/src/ios/devices.dart 271        IOSDevice.startApp.<async>
dart:async                                            _SyncCompleter.complete
package:flutter_tools/src/ios/mac.dart 180            buildXcodeProject.<async>
dart:async                                            _SyncCompleter.complete
package:flutter_tools/src/base/process.dart 145       runAsync.<async>
===== asynchronous gap ===========================
dart:async                                            _asyncThenWrapperHelper
package:flutter_tools/src/ios/devices.dart            IOSDevice.startApp
package:flutter_tools/src/run_hot.dart 161            HotRunner._run.<async>
dart:async                                            _SyncCompleter.complete
package:flutter_tools/src/resident_runner.dart 156    ResidentRunner.startEchoingDeviceLog.<async>
===== asynchronous gap ===========================
dart:async                                            _asyncThenWrapperHelper
package:flutter_tools/src/run_hot.dart                HotRunner._run
package:flutter_tools/src/run_hot.dart 78             HotRunner.run.<fn>
package:stack_trace                                   Chain.capture
package:flutter_tools/src/run_hot.dart 77             HotRunner.run
package:flutter_tools/src/commands/run.dart 278       RunCommand.runCommand.<async>

Exception from flutter run: Exception: Timeout while attempting to retrieve Uri for Diagnostic server
package:flutter_tools/src/base/common.dart 30         throwToolExit
package:flutter_tools/src/protocol_discovery.dart 55  ProtocolDiscovery.nextUri.<async>.<fn>
===== asynchronous gap ===========================
dart:async                                            _Future.timeout
package:flutter_tools/src/protocol_discovery.dart 53  ProtocolDiscovery.nextUri.<async>
===== asynchronous gap ===========================
dart:async                                            Future.Future.microtask
package:flutter_tools/src/protocol_discovery.dart     ProtocolDiscovery.nextUri
package:flutter_tools/src/ios/devices.dart 274        IOSDevice.startApp.<async>
dart:async                                            _SyncCompleter.complete
package:flutter_tools/src/ios/mac.dart 180            buildXcodeProject.<async>
dart:async                                            _SyncCompleter.complete
package:flutter_tools/src/base/process.dart 145       runAsync.<async>
===== asynchronous gap ===========================
dart:async                                            _asyncThenWrapperHelper
package:flutter_tools/src/ios/devices.dart            IOSDevice.startApp
package:flutter_tools/src/run_hot.dart 161            HotRunner._run.<async>
dart:async                                            _SyncCompleter.complete
package:flutter_tools/src/resident_runner.dart 156    ResidentRunner.startEchoingDeviceLog.<async>
===== asynchronous gap ===========================
dart:async                                            _asyncThenWrapperHelper
package:flutter_tools/src/run_hot.dart                HotRunner._run
package:flutter_tools/src/run_hot.dart 78             HotRunner.run.<fn>
package:stack_trace                                   Chain.capture
package:flutter_tools/src/run_hot.dart 77             HotRunner.run
package:flutter_tools/src/commands/run.dart 278       RunCommand.runCommand.<async>

I haven't seen it but neither of those are helpful error messages and the first one should be relatively straightforward to catch.
Some ref material in case someone gets to it before me:
For signing, the settings Xcode (8.1) cares about in the .pbxproj are DEVELOPMENT_TEAM and PROVISIONING_PROFILE. There's some checking on PRODUCT_BUNDLE_IDENTIFIER as well though I'll have to look up the details.
The second error appears to be a separate issue. A quick search of our issues looks turns up #6576 and #5398, which suggests that opening the .xcworkspace and building from there seems to help, though obviously that shouldn't be a required part of our workflow.

Closing this, because even a brand-new Flutter app doesn't run. I might reopen this, but for now: one thing at a time.
Closing as "not fixed, but there may be a bigger issue"
See https://github.com/flutter/flutter/issues/7767 for the "a brand-new flutter app doesn't run on my ios device"

Doh... sorry guys. Restarted Xcode and reopened my project by .workspace (not .project) file. Everything started to archive again. :-/


Crash on Startup in latest build.

Log:
latest.log

The issue is that it's compiled for Java 21. 1.20.1 mods should not be compiled for Java 21 as it uses Java 17.

bump

https://modrinth.com/mod/nears/version/POkHQ3qP fixed


Exporting Weights from Tensorflow Keras to C produces a different set of outputs, reduced accuracy in the model.

For some reason when I export my weights from a Tensorflow Keras model, be it a simple Sequential FNN, and then load them into C to perform forward passes I get different output results, sometimes similar and often just not the same at all. It's like the accuracy has taken a substantial loss over the original predict() in Keras.
This is how I export my weights:
    for layer in model.layers:
        if layer.get_weights() != []:
            numpy.savetxt(layer.name + ".csv", layer.get_weights()[0].flatten(), delimiter=",")
            numpy.savetxt(layer.name + "_bias.csv", layer.get_weights()[1].flatten(), delimiter=",")

and
f.write(", /* weight */ " + str(layer.get_weights()[0].flatten()[i]))
f.write(", /* bias */ " + str(layer.get_weights()[1].flatten()[i]))

The first method writes a long E value and the second writes a smaller float value to the most significant decimal place. Although that should not cause a loss in precision over the first method? right?
I'm not sure why the saved weights would give different outputs, even with a 1 layer FNN that has 1 output,  a very simple network, all the weights are saved to float32 in C and then processed with float math functions such as tanhf() etc depending on the layer output.
I must be missing some understanding of what Tensorflow or Keras is doing behind the scenes? Something it's default configuration is doing to my network/weights that I need to disable or reproduce? Are the arrays of weights in reverse or something? Do I need to iterate them from left to right and not right to left on the inputs? What am I missing?
Here is a project that demonstrates this issue:
https://github.com/jcwml/neural_unitvector
In this project a dataset is exported from main.c to ensure the C program and Tensorflow Keras program both use data generated by the same random function, then Keras trains a set of weights for a simple FNN network to some number of hidden units and layers, and then those weights are exported and loaded into the C program where the forward pass is reconstructed in C code. There are 3 types of networks in this example that have had their forward passes reconstructed, each more complicated than the last, and yet, none of them produce the same outputs as Keras predict() had, it's not even a minor accuracy loss, it is substantially different, you can tell that the weights still represent what they where trained to but with just much worse prediction accuracy.
Another important fact to note is that when I train a network with multiple layers it would seem in many cases when I export the weights to C for a forward pass that the input data passed into the network eventually becomes 0's before it gets to the deeper layers, like vanishing gradients, this would imply that Tensorflow is using a different precision float format but the documentation says it uses float32 by default and the console printouts also claim to be using float32 in my application. My only thought is that maybe numpy is not saving them in the full float32 precision but when I looked into that apparently it does export full precision, and that exporting weights this way should be fine.
I am very confused.

@BeverlyCode,
I was facing the issue/error while executing the given code. Kindly find the gist of it here.

@BeverlyCode, I was facing the issue/error while executing the given code. Kindly find the gist of it here.

You can just not supply any command line parameters to the python file and it will execute fine.

Just a small update, from my research exporting the weights using both numpy.savetxt(layer.name + ".csv", layer.get_weights()[0].flatten(), delimiter=",") and f.write("," + str(layer.get_weights()[0].flatten()[bc])) on the latest Python versions and packages exports the weights to the exact decimal precision they are in.
But encase they didn't I also exported all the weight floats as bytes and then converted them back to floats in C to be extra-sure using this function on the export:
def float_to_hex(f): return hex(struct.unpack('<I', struct.pack('<f', f))[0])
It would seem that in even very basic FNN's in Tensorflow, there is something that Tensorflow is doing in the forward-pass that is not obvious, and I'm not sure how I would find-out what it is doing. I would assume that in Tensorflow the state of all things are disabled, such as layer regularisation, etc, unless explicitly turned on? Is it possible that Tensorflow actually turns some of this stuff on by default to improve default trained networks and that I just haven't realised this?
I'm clutching at straws here but Tensorflow is a large complicated SOTA framework and I'm not really sure where to start or how to go about debugging this.

Trying to figure this out independently still, I downloaded the Keras source code to try and find discrepancies, pdb was useless for this task for example, stepping though execution for a discrepancy is a lot less efficient when I can just check the code.
So I'm still in this process, Keras is a large system, it may take me a while. I am also going to look at tensorflow-onnx to see how they convert Keras models to ONNX for inference.
A comparison of the tanh function activations.py#L379 shows very little difference between that and other implementations in terms of accuracy, a small C program enclosed demonstrates this:
#include <stdio.h>
#include <math.h>

const float e = 2.718281746F;
const float e2 = 7.389056206F;

static inline float mysinh(float f)
{
    return 0.5f * (powf(e, f) - powf(e, -f));
}

static inline float mycosh(float f)
{
    return (powf(e, f)/2.f) + (powf(e, -f)/2.f);
}

static inline float mytanh1(float f)
{
    return mysinh(f) / mycosh(f);
}

static inline float mytanh2(float f)
{
    const float pe = powf(e2, f);
    return (pe-1.f) / (pe+1.f);
}

static inline float kerasth(const float x) // keras tanh
{
    return ((expf(x) - expf(-x))/(expf(x) + expf(-x)));
}

int main()
{
    printf("mycosh():  %g\ncoshf():   %g\n", mycosh(45.f), coshf(45.f));
    printf("mytanh1(): %g\nmytanh2(): %g\ntanhf():   %g\ntanh():    %g\nkerasth(): %g\n", mytanh1(0.2f), mytanh2(0.2f), tanhf(0.2f), tanh(0.2f), kerasth(0.2f));
    printf("---\n");
    printf("mycosh():  %f\ncoshf():   %f\n", mycosh(45.f), coshf(45.f));
    printf("mytanh1(): %.9f\nmytanh2(): %.9f\ntanhf():   %.9f\ntanh():    %.9f\nkerasth(): %.9f\n", mytanh1(0.2f), mytanh2(0.2f), tanhf(0.2f), tanh(0.2f), kerasth(0.2f));
    return 0;
}

But I can get better results by dumping my sigmoid() for a simple scaled output, even though in Keras I define a sigmoid output on the final dense layer, when I import the weight in C I get better scaled outputs by replacing the sigmoid with an output*0.03 for example. But that doesn't explain anything really, the outputs are still different, just detect the intended inputs more how it should, and it still doesn't explain why when I export the weights from an FNN with multiple layers that these weights quickly cause inputs to vanish past the first or second layer causing 0 ouputs.
It feels like either Keras is scaling the inputs or using some kind of regularisation between layers. Something is odd, but I am having a hard time workout out what.

Hi @BeverlyCode ,
It is really difficult to assess whether the code in main.c is equivalent to the Keras/Tensorflow code. Just the matrix multiplication, for instance, is difficult to analyze.
I do see a possible culprit though. In the example output of the exported keras model you added above, I see "activation": "sigmoid" on the last Dense layer. However, your C code only implements tanh. And in fit.py, the last layer has no activation right now. So there is a discrepancy here. Can you verify if that is the issue?

Hi @BeverlyCode ,
It is really difficult to assess whether the code in main.c is equivalent to the Keras/Tensorflow code. Just the matrix multiplication, for instance, is difficult to analyze.
I do see a possible culprit though. In the example output of the exported keras model you added above, I see "activation": "sigmoid" on the last Dense layer. However, your C code only implements tanh. And in fit.py, the last layer has no activation right now. So there is a discrepancy here. Can you verify if that is the issue?

Nah that's just a model I dumped from a different network which I also output to C, some I use sigmoid some I use linear outputs. I have basically replicated many Dense FNN networks in C from Keras, and they all 'kind of work' but not really because the accuracy is lacking.
Nice try though, if only it was that simple. ;)

@BeverlyCode ,
I changed line 208 to this:
for weight in layer.get_weights()[0].transpose().flatten():

and tested in a roundabout way and got the same results.
So it's either a bug in the norm_neural code or the Python export code. It could just come from a misunderstanding of how flatten works.
Anyway, transposing before exporting fixes it.
Thanks.

You are completely right, you have solved it! Thank you so much!
I had to transpose the weight matrix before export, out of interest how did you discover this, I know that Tensorflow uses channels_last but the row/column major of the matrix was not a factor I had considered, partly I think because I did not even think of the weights as a matrix with columns or rows rather as a flat array.
I am wondering what you thought process was to have solved this so that I can improve my though processes.
But thank you so much. I hope that other people as confused as me find this thread and your answer. I should in future dump the array shape in future and if it is a matrix consider transposing I suppose.

Hi @BeverlyCode ,
My thought process was mostly a hunch that:

it had nothing to do with Keras (an issue in something as simple as 2 Dense layers would have been found by now)
it wasn't a precision issue, it was something more fundamental (numbers were way off)

Glancing at the C code, it looked correct. But one thing wasn't clear to me, which was whether the loops and index calculations were done correctly in the matrix multiplication to multiply rows with columns. Rather than trying to prove the code right or wrong, I thought I would transpose and give it a shot. And transposing the export was easier than modifying the code.
As far as the order of columns vs. rows is concerned, in this particular case, it's Numpy that's used (get_weights returns Numpy arrays and flatten() is a Numpy API, not Tensorflow). But as it turns out, Tensorflow uses the same order.
import numpy as np
y = np.array([[1, 2], [3, 4]])
y.flatten()

array([1, 2, 3, 4])

import tensorflow as tf
x = tf.constant([[1, 2], [3, 4]])
tf.reshape(x, (4,))

<tf.Tensor: shape=(4,), dtype=int32, numpy=array([1, 2, 3, 4], dtype=int32)>


fix shell after unifying flakes

hey, #211 broke the shell.nix pointer to development shell.
also, nix-direnv throws an error
error: '' needs to evaluate to a single derivation, but it evaluated to 3 derivations

so it's required to specify the exact shell now (echo "use-flake .#scala" > .envrc).

so it's required to specify the exact shell now (echo "use-flake .#scala" > .envrc).

That's odd. There's a default shell, so that shouldn't be needed. I have use flake in my .envrc and it's working (direnv v2.32.2).

ah, that's right. I had use nix and it was throwing an error. use flake works like a charm.

np :) I have some questions to your FEDA book. Is there any place we can text/talk for a moment?


Added rounding functionality on the end time

Added the rounding and the rounding down threshfold on the settings page created a new combo componant.
Added the logic and button to the entry page.

There still needs to be some finishing touches. When the rounding is done on a new entry it isn't always saved to the state.
There could also be a better way of using the rounding, maybe without the button.

before round button

round button pressed.

@Gaya  Also the netlify build didn't work. All I see is a blank white screen when I view the preview.

@Scoombe Thank you for adding the screenshots. Makes it clear what you made. Looks like you got pretty far, that's great.
I think rounding can happen when starting and stopping the timer automatically. So when you start a task it will for instance round down to every 5 / 10 / 15 minutes etc. You could also set it to go up  or automatically round up or down.
The same could be possible for end times as well.
I need to look into the Netlify preview because of some changes I made to the deployment earlier for Thyme to work on usethyme.com/thyme. Will create an issue for it.

I've changed it so the rounding happens on the start of the timer, it does the start and the end date. I think I'm pretty close to be being finished. can you have a look at this change for me when you get a chance.
Thanks.

Nice! I think you're very close. If you want I can pick it up from here and finish the PR, or I can also do a code review if you'd like to do that yourself.

@Gaya if you could do a code review that would be nice, I'm not to confident on the flow stuff and I've done pretty much the minimum to get it working. I've also had a go at the merging your lint fixing stuff as there was a conflict on the entry.js.

@Gaya fair enough. I have made some changes. Just having some problems with the flow stuff on the properties of the object. If we could go through that when you're back that would be good.

I am going to start looking into this as it is also something I really want to have myself. Will come up with the best way forward from the work you've done. I might pick up where you left off and finish it.

You can see my solution over at #101 , will close this PR in favour of that one. Thank you for helping out!


Conditional types don't seem to reject supertypes where they should

Bug Report
🔎 Search Terms
conditional types, supertype
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about conditional types

⏯ Playground Link
Playground link with relevant code
💻 Code
type Test<T>
    = T extends undefined ? "contains-undefined"
    // This condition should be false for number | undefined
    // as number is NOT a supertype of number | undefined
    : number extends T ? "number"
    : never;

// Kind should just be "contains-undefined", however it is also
// | "number" which is wrong
type Kind = Test<number | undefined>

🙁 Actual behavior
The branch number extends T is incorrectly included as number not being a supertype of number | undefined. (NOTE: This would not be the same as T extends number, because T = number | undefined is indeed a supertype of number).
You can observe the same behaviour with just:
// number is clearly not a supertype of (number | undefined)
type ShouldBeNever = number extends (number | undefined) ? "not-never" : never;

🙂 Expected behavior
Only "contains-undefined" should be included in the final type, similarly for the smaller example ShouldBeNever should, well, be never.

type ShouldBeNever = number extends (number | undefined) ? "not-never" : never;

This is correctly evaluated to "not-never".  extends means “is a subtype of”, or more accurately in the case of conditional types, “is assignable to”.  number is assignable to number | undefined, so it takes the true branch.
As for Test, its behavior is also correct due to distributivity of generic conditional types:
https://www.typescriptlang.org/docs/handbook/2/conditional-types.html#distributive-conditional-types

This is correctly evaluated to "not-never". extends means “is a subtype of”, or more accurately in the case of conditional types, “is assignable to”. number is assignable to number | undefined, so it takes the true branch.

Admittedly I got it mixed up as I was trying T extends number and number extends T, and the fact T extends undefined worked made me assume T extends undefined refered to is T a supertype of undefined.

As for Test, its behavior is also correct due to distributivity of generic conditional types:

Okay this works as expected, I'm not sure that I agree with the docs that:

Typically, distributivity is the desired behavior.

It seems more confusing to me that in this one specific instance unions are distributed like nowhere else in TS, it actually makes me now concerned that pretty much all of my conditional types don't work with union types now.

if it helps, the rule is that conditional types distribute whenever the type being checked (T extends…) is a naked generic type parameter.  You can easily suppress it by writing the check as [T] extends [U] ? …


Prepare for 0.9.9 release

@murgatroid99 @jayantkolhe I think this is what we need to be ready to roll as soon as we have push access to npmjs.

Coverage remained the same at 92.422% when pulling ac25605965c7808b0d746825a5748cb03c16dab1 on bjwatson:prepare-0.9.9 into 02f587472ecdc2582f8d5fc754996aa6ef9388a0 on google:master.

@murgatroid99 FYI, I think this contains the release notes you need, although there might be more since I did this.

Can you update this to account for #98.

@murgatroid99 Done.

Coverage remained the same at 92.673% when pulling b9583178cbe87b53e9a390b3e4c8abb6595a0bad on bjwatson:prepare-0.9.9 into 1c2d853c5a6e3ad0081b6e0a54dd2ac8b9033003 on google:master.


aarch64 support

I used conda to create a python 3.8 environment but I cannot pip install jpype1 on the linux aarch64 machine. Please help. Thanks!!!
Error:
# pip install jpype1
Looking in indexes: http://mirrors.cloud.aliyuncs.com/pypi/simple/
Collecting jpype1
  Using cached http://mirrors.cloud.aliyuncs.com/pypi/packages/25/42/8ca50a0e27e3053829545829e7bcba071cbfa4d5d8fd7fc5d1d988f325b1/JPype1-1.5.0.tar.gz (819 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting packaging (from jpype1)
  Using cached http://mirrors.cloud.aliyuncs.com/pypi/packages/08/aa/cc0199a5f0ad350994d660967a8efb233fe0416e4639146c089643407ce6/packaging-24.1-py3-none-any.whl (53 kB)
Building wheels for collected packages: jpype1
  Building wheel for jpype1 (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for jpype1 (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [77 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/dbapi2.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/nio.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jarray.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jinit.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jcollection.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jclass.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/config.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_classpath.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/protocol.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jvmfinder.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jproxy.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_pykeywords.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/__init__.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/beans.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jcustomizer.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jthread.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jmethod.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_core.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/pickle.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jio.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/imports.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_gui.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jexception.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jpackage.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jstring.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/types.py -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jobject.py -> build/lib.linux-aarch64-cpython-38/jpype
      creating build/lib.linux-aarch64-cpython-38/jpype/_pyinstaller
      copying jpype/_pyinstaller/example.py -> build/lib.linux-aarch64-cpython-38/jpype/_pyinstaller
      copying jpype/_pyinstaller/entry_points.py -> build/lib.linux-aarch64-cpython-38/jpype/_pyinstaller
      copying jpype/_pyinstaller/hook-jpype.py -> build/lib.linux-aarch64-cpython-38/jpype/_pyinstaller
      copying jpype/_pyinstaller/test_jpype_pyinstaller.py -> build/lib.linux-aarch64-cpython-38/jpype/_pyinstaller
      copying jpype/_jcollection.pyi -> build/lib.linux-aarch64-cpython-38/jpype
      copying jpype/_jio.pyi -> build/lib.linux-aarch64-cpython-38/jpype
      running build_ext
      Call build extensions
      Using Jar cache
      copying native/jars/org.jpype.jar -> build/lib.linux-aarch64-cpython-38
      Call build ext
      building '_jpype' extension
      creating build/temp.linux-aarch64-cpython-38/native/common
      creating build/temp.linux-aarch64-cpython-38/native/python
      g++ -Wno-unused-result -Wsign-compare -DNDEBUG -fwrapv -Wall -fPIC -isystem /root/miniforge/envs/panama_env_py38/include -fPIC -isystem /root/miniforge/envs/panama_env_py38/include -fPIC -Inative/common/include -Inative/python/include -Inative/embedded/include -Inative/jni_include -I/root/miniforge/envs/panama_env_py38/include/python3.8 -c native/common/jp_array.cpp -o build/temp.linux-aarch64-cpython-38/native/common/jp_array.o -g0 -std=c++11 -O2
      /tmp/pip-install-slfymkmi/jpype1_5eff3cf79b41465db0338f7ba04175b0/setupext/pytester.py:20: SetuptoolsDeprecationWarning: The test command is disabled and references to it are deprecated.
      !!

              ********************************************************************************
              Please remove any references to `setuptools.command.test` in all supported versions of the affected package.

              By 2024-Nov-15, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.
              ********************************************************************************

      !!
        from setuptools.command.test import test as TestCommand
      /tmp/pip-build-env-v_i4w5xp/overlay/lib/python3.8/site-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'tests_require'
        warnings.warn(msg)
      /tmp/pip-build-env-v_i4w5xp/overlay/lib/python3.8/site-packages/setuptools/dist.py:495: SetuptoolsDeprecationWarning: Invalid dash-separated options
      !!

              ********************************************************************************
              Usage of dash-separated 'index-url' will not be supported in future
              versions. Please use the underscore name 'index_url' instead.

              By 2025-Mar-03, you need to update your project and remove deprecated calls
              or your builds will no longer be supported.

              See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
              ********************************************************************************

      !!
        opt = self.warn_dash_deprecation(opt, section)
      error: command 'g++' failed: No such file or directory
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for jpype1
Failed to build jpype1
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (jpype1)

According to this post here https://github.com/jpype-project/jpype/pull/910, I tried and found that version 1.2.1 supports aarch64 however the later versions don't. Could you please support aarch64 for versions after 1.2.1 as well.

I too went to install JPype1 on Ubuntu 24.10 for ARM the other day and came to the same realization.  Would love to see a wheel for it!

The log says error: command 'g++' failed: No such file or directory. Have you tried installing a c++ compiler and trying again?

I just tried again, and it was able to build the source.  Not sure why it failed for me before.
(venv) ryan@ubuntu2410:~$ pip3 install JPype1
Collecting JPype1
  Downloading JPype1-1.5.0.tar.gz (819 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 819.1/819.1 kB 26.0 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting packaging (from JPype1)
  Downloading packaging-24.1-py3-none-any.whl.metadata (3.2 kB)
Downloading packaging-24.1-py3-none-any.whl (53 kB)
Building wheels for collected packages: JPype1
  Building wheel for JPype1 (pyproject.toml) ... done
  Created wheel for JPype1: filename=JPype1-1.5.0-cp312-cp312-linux_aarch64.whl size=447131 sha256=b556d5f950b36f344888cee0c0c9454084fcd42241155381169257a29d6c357f
  Stored in directory: /home/ryan/.cache/pip/wheels/62/a4/75/36e26edddd69fa4006421979f7782fa8758f43797474fc7ef6
Successfully built JPype1
Installing collected packages: packaging, JPype1
Successfully installed JPype1-1.5.0 packaging-24.1

The log says error: command 'g++' failed: No such file or directory. Have you tried installing a c++ compiler and trying again?

This error occurs because it cannot find the desired package and starts to build from source. I would prefer to install the pre-built package. The doc said it supports arm from 1.2.1 and future releases but it seems it is not true.

@marscher why is it closed?

I didn't even know we provide arm64 binaries out of the box. I think conda-forge does provide it (external build pipeline). The package there is called jpype1.
If you volunteer to look into it - fine give it a shot. I do not have the time to dig into it and I believe nobody of the volunteers working here for no cash have it at the moment. Watch your tone mate.

I didn't even know we provide arm64 binaries out of the box. I think conda-forge does provide it (external build pipeline). The package there is called jpype1.
If you volunteer to look into it - fine give it a shot. I do not have the time to dig into it and I believe nobody of the volunteers working here for no cash have it at the moment. Watch your tone mate.

I already posted the screen shot of the release note saying that aarch64 has been added to the built patterns for publication in this and future releases. If you didn't know, look at it, read it and realize there was something wrong instead of closing my issue.
Just because I asked you why you closed the issue, you ask me to watch my tone, LOL. Pathetic, mate.

I didn't even know we provide arm64 binaries out of the box. I think conda-forge does provide it (external build pipeline). The package there is called jpype1.
If you volunteer to look into it - fine give it a shot. I do not have the time to dig into it and I believe nobody of the volunteers working here for no cash have it at the moment. Watch your tone mate.

Don't speak on behalf of the other volunteers. They are more helpful and better than you.

I didn't even know we provide arm64 binaries out of the box. I think conda-forge does provide it (external build pipeline). The package there is called jpype1.
If you volunteer to look into it - fine give it a shot. I do not have the time to dig into it and I believe nobody of the volunteers working here for no cash have it at the moment. Watch your tone mate.

Don't speak on behalf of the other volunteers. They are more helpful and better than you.

It takes all of two seconds to install g++ on linux. Having a c/c++ compiler available is expected when installing python packages. Minimal troubleshooting on your end would fix the problem. It is not feasible to provide pre-built wheels for every possible architecture/os combinations.
It also appears that you are using http://mirrors.cloud.aliyuncs.com so if it doesn't have the packages you need that is entirely on you.
I understand that the confusion may cause an emotional reaction but your response to this being closed was not appropriate.

I didn't even know we provide arm64 binaries out of the box. I think conda-forge does provide it (external build pipeline). The package there is called jpype1.
If you volunteer to look into it - fine give it a shot. I do not have the time to dig into it and I believe nobody of the volunteers working here for no cash have it at the moment. Watch your tone mate.

Don't speak on behalf of the other volunteers. They are more helpful and better than you.

It takes all of two seconds to install g++ on linux. Having a c/c++ compiler available is expected when installing python packages. Minimal troubleshooting on your end would fix the problem. It is not feasible to provide pre-built wheels for every possible architecture/os combinations.
It also appears that you are using http://mirrors.cloud.aliyuncs.com so if it doesn't have the packages you need that is entirely on you.
I understand that the confusion may cause an emotional reaction but your response to this being closed was not appropriate.

Asking why it is closed was "not appropriate". I don't understand what you are talking about.


Trigger BREAKING CHANGE from PR #278

The recent changes to Disk resource in #278 should trigger a major version number bump. Need to add a BREAKING CHANGE: commit

This was fixed in PR #283


CDN-related error while loading the web parts.

**Hello
I have followed the setup but unfortunately I get an error message when trying to load the web parts in a page of the project on my SharePoint. The message is as following:**
[SPLoaderError.loadComponentError]:
***Failed to load component "d67d6088-e294-4a23-af02-c4ea8783c23f" (GdprInsertEventWebPart).
Original error: ***Failed to load URL 'https://publiccdn.sharepointonline.com/contosogdprswe.sharepoint.com/sites/clientsideassets/ActivityHub/gdprstarterkit-gdprinsertrequeststrings_en-us_3a374bd4fecd98b5af22dc9a8072d8b6.js' for resource 'gdprInsertRequestStrings' in component 'd67d6088-e294-4a23-af02-c4ea8783c23f' (GdprInsertEventWebPart). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.
***INNERERROR:
***Failed to load URL 'https://publiccdn.sharepointonline.com/contosogdprswe.sharepoint.com/sites/clientsideassets/ActivityHub/gdprstarterkit-gdprinsertrequeststrings_en-us_3a374bd4fecd98b5af22dc9a8072d8b6.js' for resource 'gdprInsertRequestStrings' in component 'd67d6088-e294-4a23-af02-c4ea8783c23f' (GdprInsertEventWebPart). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.
***CALLSTACK:
Error
at t (https://spoprod-a.akamaihd.net/files/sp-client-prod_2017-12-29.004/sp-pages-assembly_en-us_f84b940bd26c347833961851c56e827f.js:307:15840)
at t (https://spoprod-a.akamaihd.net/files/sp-client-prod_2017-12-29.004/sp-pages-assembly_en-us_f84b940bd26c347833961851c56e827f.js:724:38028)
at e.buildErrorWithVerboseLog (https://spoprod-a.akamaihd.net/files/sp-client-prod_2017-12-29.004/sp-pages-assembly_en-us_f84b940bd26c347833961851c56e827f.js:724:43517)
at e.buildLoadComponentError (https://spoprod-a.akamaihd.net/files/sp-client-prod_2017-12-29.004/sp-pages-assembly_en-us_f84b940bd26c347833961851c56e827f.js:724:40238)
at Anonymous function (https://spoprod-a.akamaihd.net/files/sp-client-prod_2017-12-29.004/sp-pages-assembly_en-us_f84b940bd26c347833961851c56e827f.js:724:12336)

**I figured it might be the CDN-path of the URL on the write-manifests.json file (sites/CDNname/CDNLibrary). Because when I enable the public CDN in the tenant (through this guide: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn) the "*/CLIENTSIDEASSETS" does not change to "Sites/CDN/CDNFiles". I have tried to write both clientsideassets and sites/CDN/CDNFiles on the write-manifests file.
Any suggestions on how I can move further?**

@Mathilda-P @alidgren I had the same problem.....error'd on Chrome PC. Tried in IE on PC and works fine.
I used IE to put the web part on the page, publish the page and then load in Chrome and still fails. Any ideas on why this is? I'm gonna keep digging as it could be some localized issue on my machine, but this is sorta weird huh?
Thoughts?

@Mathilda-P @PopWarner Hi all, I've got exactly the same issue... did you resolved this problem ?
Thanks

you can try gulp trust-dev-cert before bundle and package-solution ?

Did this work for anyone? I am having the same issue

Any fix for this issue? i am getting the same..

Any update on how to fix it. I am getting the same error.

try gulp trust-dev-cert before bundle and package-solution.
helped me in resolving the issue.

I have the same error with the "react-todo-basic" demo
It is working fine in the workbench.aspx when gulp serve --nobrowser is running but when deploying to a CDN location, there is no "react-todo-basic-todostrings_en-us_d4fe2bb623d36825d3cfdfeb1cfde318.js" file in the \react-todo-basic\dist folder.
Is there a way to create this file from the "\react-todo-basic\src\webparts\todo\loc\en-us.js" file?

Hello,
Today I was manage to solve problem @Ofer-Gal @Mathilda-P please check your react-todo-basic-todostrings_en-us file on deploy if there is any weird character in my case it was ` instead ". I change mark in my en-us file under \loc and its work :)

From your post, I can't understand which file needs to be fixed

Sorry for that @Ofer-Gal.
I had similar problem like you with file strings_en-us_.js and in my case I opened and close string with ` instead " in one line in /lib/webparts//loc/en-us.js file where I had my strings.
Chrome didn't have problem with that but IE throw error about HTTPS certificate problem and point to *string_en-us.*js file.

My file is the same as in the src as was made from the yo.
not the same problem

having same error, deployment was successful but while loading it starts giving the same error. Was a solution found for this problem.?

yes i am also facing the same error. its working in chrome, but not in IE. please give the solution as soon as possible

Same here on IE11. Pretty urgent, broken in PROD, have uploaded to app catalog, not CDN.

I am also getting same error after following above steps:
Something went wrong
If the problem persists, contact the site administrator and give them the information in Technical Details.
TECHNICAL DETAILS
[SPLoaderError.loadComponentError]:
***Failed to load component "b8e54bd2-454c-4b1d-90b1-852355cc44eb" (ReactSpFxPnPWebPart). Original error: ***Failed to load URL 'https://publiccdn.sharepointonline.com/Esssity/sites/Esssity/Shared Documents/CDN/reactspfxpnp-controlstrings_en-us_9d5c960645bbbbf6af0dced2dc36c079.js' for resource 'ControlStrings' in component 'b8e54bd2-454c-4b1d-90b1-852355cc44eb' (ReactSpFxPnPWebPart). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.
***INNERERROR:
***Failed to load URL 'https://publiccdn.sharepointonline.com/Esssity/sites/Esssity/Shared Documents/CDN/reactspfxpnp-controlstrings_en-us_9d5c960645bbbbf6af0dced2dc36c079.js' for resource 'ControlStrings' in component 'b8e54bd2-454c-4b1d-90b1-852355cc44eb' (ReactSpFxPnPWebPart). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.
***CALLSTACK:
Error
at t [as constructor] (https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_dcfe147211950575af0e17d26b0ced7b.js:4:53271)
at new t (https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_dcfe147211950575af0e17d26b0ced7b.js:20:10505)
at Function.e.buildErrorWithVerboseLog (https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_dcfe147211950575af0e17d26b0ced7b.js:20:53017)
at Function.e.buildLoadComponentError (https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_dcfe147211950575af0e17d26b0ced7b.js:20:49048)
at https://spoprod-a.akamaihd.net/files/sp-client/sp-pages-assembly_en-us_dcfe147211950575af0e17d26b0ced7b.js:20:44589


Fix OutOfMemoryError: Java heap space Issue

Purpose
The test suite is keeping CompileResult objects live during the run using a large portion of the memory.

eg:
@AfterClass
public void tearDown() {
    compileResult = null;
    negativeResult = null;
}

Fixes #
Before

After

Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

We can probably improve at least the negative tests by switching to local variables for their CompileResults. Shall we create an issue for this?

We can probably improve at least the negative tests by switching to local variables for their CompileResults. Shall we create an issue for this?

Created an issue https://github.com/ballerina-platform/ballerina-lang/issues/27856

Created an issue https://github.com/ballerina-platform/ballerina-lang/issues/27856


Allow for permalink:false, add test for this

This makes the plugin accept files with front-matter where permalink is set to false.
Setting permalink to false is useful when you create a single-page website where sections of content are put into files of their own (something like "our mission", "career" etc.) and are included in index.html (via looping in the layout for index.html), but should not be written to disks as separate files. This can be achieved with permalink:false.
Here's a reference to the 11ty docs that describe this setting: https://www.11ty.dev/docs/permalinks/.
Without the change, the permalink:false makes the plugin crash, with output like this:
[11ty] Original error stack trace: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type boolean (false)

Published a new release v4.0.2.

Thanks for accepting my suggestion. I really use your plugin a lot :-)


website

This change reorganizes the docs/ directory in order to create a rudimentary website for Sockeye (addressing #540). Among other things, this PR:

builds a website on the Github Jekyll framework.
removes tutorials as a top level directory, folding all that content into the website itself
moves some of the information in the top-level README into docs/
(perhaps controversially) removes the sphinx files, on the idea that these can be generated locally or browsed through github

You can see a live demo here. The website is quite simple and basic. The idea is to get something in place so that people can contribute, and improve it iteratively down the line.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This is a great first step and something users have been asking about for awhile!  I support merging this version and iterating, including accepting pull requests from others who have expressed interest in adding to our documentation.
It looks like check-manifest couldn't find some files.  Otherwise the demo looks good.

what about the readthedocs build now?
Does python setup.py docs still run sphinx and is able to create the documentation hosted at https://sockeye.readthedocs.io/en/latest/ ?

No, I killed that. I thought we had discussed this being okay privately a while back, since people can always just browse through Github.
If you want Sphinx, too, that could work. The problem is they both require use of the docs/ directory, but I think the only file overlap is index.md.

I haven't tried Sphinx at all since I don't think I have permissions to generate that and it was too time-consuming to worry about getting them both to work (I've already probably spent more time on this than I should have). My hope here is that we fold this in (I think the website is more important, actually), and then try to rebuild Sphinx on top of that, afterward. It shouldn't be too difficult, I wouldn't think.

Sounds good, thanks! Consider also, though, that there is nothing new here at all: this PR just pulls together documentation that was already there but in many different places. I think the only thing I added was the docs for source factors (an existing feature).

I think it be useful to have some kind of link on the website that points to the code/github.

Thanks for putting together the website change! Regarding sphinx: we did indeed discuss to have just a single place for documentation, namely the website. In general it definitely makes total sense to avoid having the same information available redundantly in multiple locations. As the github page will no longer contain the docs generated from modules we could consider hosting module docs on readthedocs and everything else on the github page. This way we wouldn't have redundant information. That said, it's unclear how useful the module docs are. So maybe we just go ahead with the page change as is and revisit the sphinx documentation later.
It's definitely great that we will finally have a website :)

Looks great. I think a couple of links wouldn't work anymore. Let's fix those and enable the website :)

Excellent! Now we just need one of you to flip the docs switch, right? Then the website will be live and we can start advertising.

perfect. I'll merge now and then pull the switch :)

I am page-reloading with bated breath.

I enabled github pages. Somehow it doesn't show up at https://awslabs.github.io/sockeye/ yet. Let's see if its just delayed.

Looks like it's live now!

great, thanks for putting this together, Matt!


The PR "Fixes/win32 can resize" is not included in the release

Describe the bug
If you have ExtendToClientDecorations = true, and CanResize = false, you can't drag with titlebar on win32.
Expected behavior
Being able to drag a window's titlebar when ExtendToClientDecorations = true and CanResize = false
Desktop (please complete the following information):

OS: Windows
Version 10 21H2

Additional context
This bug was fixed in #7755 (which was merged into master in March), but isn't included in the release build as of version 0.10.17.

Will be available in 11.0 I think. Currently many changes are done for next major release.

Thanks for the precision. Though, shouldn't it also be included in 0.10, since it's only a bugfix?

@fr-Pursuit thanks!
It was backported. Will be available with 0.10.18 soon.

Thanks!


Created OPSDeclarator class

This is a generic class for OPS declarations.
Example:
Pass name and type args.
stencil = OPSDeclarator('stencil_n', 'ops_stencil')
block = OPSDeclarator('block', 'ops_block')

LGTM. @vincepandolfo ?

Codecov Report

Merging #885 into master will decrease coverage by 0.01%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##           master     #885      +/-   ##
==========================================
- Coverage   89.19%   89.18%   -0.02%
==========================================
  Files         105      105
  Lines       11935    11942       +7
  Branches     2370     2370
==========================================
+ Hits        10646    10650       +4
- Misses        994      997       +3
  Partials      295      295

Impacted Files
Coverage Δ

devito/ops/types.py
84.31% <57.14%> (-4.33%)
:arrow_down:

Continue to review full report at Codecov.

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

@FabioLuporini as mentioned in #884 I would prefer separate objects (OpsStencil, OpsDat, etc.) instead of this but this would work too

I just thought that the dtype of these objects is statically known and it is known in advance, hence dtype should actually be a class attribute, just like here
So I not only prefer separate objects, but also class-level dtypes


Documentation for extension authors to make compatible with VS Live Share

Are there any documentation or resources for extension developers on how to make their extensions work/support VS LiveShare?
I can not see anything in documentation anywhere but it would be nice to know how to do this please.

@sandy081 does this mean that this will not be documented or advised now that you have unassigned yourself.
Will someone else pick this up?


Rename CODEOWNERS to CODEOWNERS Roshan Sharma Hacker Of Nepal

Roshan Sharma Hacker Of Nepal topper Hacker Of Dark web Virtual virus and Google platform is giving chance server of YouTube Nepal
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕

Will ban this account if attempted again.


undefined is not a function.    import_react.useSyncExternalStore

Current Behavior
I followed the docs and got setup the tamagui for react native but when i run the android app it gives me following error
ERROR  TypeError: undefined is not a function (near '...(0, import_react.useSyncExternalStore)...')
This error is located at:
in Unknown (at App.tsx:13)
in PortalProvider
in _Theme (created by _ThemeProvider)
in _ThemeProvider (created by _TamaguiProvider)
in _TamaguiProvider
in Unknown (at App.tsx:12)
in App (at renderApplication.js:50)
in RCTView (at View.js:32)
in View (at AppContainer.js:92)
in RCTView (at View.js:32)
in View (at AppContainer.js:119)
in AppContainer (at renderApplication.js:43)
in main(RootComponent) (at renderApplication.js:60)
Expected Behavior
I expect it to work properly
Tamagui Version
"react-native": "0.66.4",
"tamagui": "^1.36.6",
"react": "17.0.2",

Reproduction
Try to use tamagui with following configurations

//babel.config.js

process.env.TAMAGUI_TARGET = 'native'

module.exports = {
  plugins: [
    ['transform-inline-environment-variables', {
      include: ['TAMAGUI_TARGET']
    }]
  ]
}

//tamagui.config.ts

import { shorthands } from '@tamagui/shorthands'
import { themes, tokens } from '@tamagui/themes'
import {createMedia} from '@tamagui/react-native-media-driver'
import { createFont, createTamagui } from 'tamagui'
export default createTamagui({
  media: createMedia({
        xs: { maxWidth: 660 },
        // ...
  }),
  themes,
  tokens,
  shorthands,
  fonts: {
    body: createFont({
      family: 'Arial',
      size: {
        4: 14,
      },
      lineHeight: {
        4: 16,
      },
    }),
  },
})

// App.tsx

/* eslint-disable jsx-a11y/accessible-emoji */
import React from 'react';
import { TamaguiProvider, View } from 'tamagui'
import config from '../../tamagui.config'

const App = () => {

  return (
    <TamaguiProvider config={config}>
      <View></View>
  </TamaguiProvider>

  );
};

export default App;

System Info
No response

Try to add this to your bable file:
[
      '@tamagui/babel-plugin',
      {
        components: ['tamagui'],
        config: './tamagui.config.ts',
        importsWhitelist: ['constants.js', 'colors.js'],
        logTimings: true,
        disableExtraction: process.env.NODE_ENV === 'development',
      }
    ],

Based on https://tamagui.dev/docs/intro/compiler-install#babel--metro
Looks like your mobile app thinks its a website.

You need at least React 18, or to import '@tamagui/react-17-patch' which isn't guaranteed to work


Disable checkbox option

I want to disable the checkbox option in the in the table

Expected Behavior

Disable the checkbox option. I there an option to disable the checkbox option?
In a specific table I don't want the option to select & delete.
Current Behavior

Your Environment

Tech
Version

Material-UI
4.10.0

MUI-datatables
3.3.0

React
16.13.1

browser
Chrome

etc

See the documentation of the selectableRows option. Ex:
let options = {
    selectableRows:"none"
};

I can't believe I missed that.
Thanks!


Help

Someone just stole my phone.. I have their hardware and software
information and need to locate my phone and them asap
On Sat, Mar 26, 2022, 4:07 PM Sahat Yalkabov @.***>
wrote:

Closed #1187 https://github.com/sahat/hackathon-starter/issues/1187.
—
Reply to this email directly, view it on GitHub
https://github.com/sahat/hackathon-starter/issues/1187#event-6312545475,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYARU6WN3LLKCR2OARE7RLDVB5373ANCNFSM5P7PZ5GA
.
You are receiving this because you authored the thread.Message ID:
@.***>

What do I do step by step or can I pay u to track them?
On Sat, Mar 26, 2022, 4:49 PM Tristin Lindamood @.***>
wrote:

Someone just stole my phone.. I have their hardware and software
information and need to locate my phone and them asap
On Sat, Mar 26, 2022, 4:07 PM Sahat Yalkabov @.***>
wrote:

Closed #1187 https://github.com/sahat/hackathon-starter/issues/1187.
—
Reply to this email directly, view it on GitHub
https://github.com/sahat/hackathon-starter/issues/1187#event-6312545475,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYARU6WN3LLKCR2OARE7RLDVB5373ANCNFSM5P7PZ5GA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Incorporate "upstream" changes / rebase from sapper-postcss-template

Many things from the new trimmed-down template have been cleaned up, so this is a note to self to start "fresh" from that as a base.

Done with a4ff3c276ff02ccfcd83bc022733d762145fe56f! 🚀


API: Loaders for XML format

classpath & URL-based loaders for XML
They should support:

Properties XML-format
OWNER XML-format

done.


mgie inference error

Traceback (most recent call last):
File "/content/ml-mgie/extract_ckpt.ipynb", line 5, in
"execution_count": null,
NameError: name 'null' is not defined

How can I solve the problem? I want to test the model on Colab

I change 'null' of code to 'None'. Then no error but it seems doesn't work.

@Zerycii I think you are trying to run code from this repository: https://github.com/apple/ml-mgie
In that case I think its best if you raise this issue in that repository
Also you are trying to run an .ipynb file using the !python command
That only works for .py files, you can copy-paste the cells of a python notebook (.ipynb) inside a colab and get them to work.
All the best :)


Code resurrect.

I have resurrected the old GLFW 2 code to a newer, FreeGLUT and GLEW based code, and adapted Makefiles and lib files accordingly.

I had abandoned these demos ages ago. Nice to see that someone cares. GLUT is not my thing, but it's just a personal preference.


Why does opleader create mapping in both normal and visual mode?

Why does opleader create a mapping in both normal and visual mode? I noticed that the mapping I set for operator-pending mode appears as an xmap as well. Is there a specific reason for why it is set in visual mode as well? Is it even possible to perform an operator-pending command from visual mode?
From the README:
---LHS of operator-pending mappings in NORMAL + VISUAL mode
---@type table
opleader = {
    ---Line-comment keymap
    line = 'gc',
    ---Block-comment keymap
    block = 'gb',
},

Is there a specific reason for why it is set in visual mode as well?

Because then in visual mode you will be able to do something like V10jgc to comment 10 lines in visual mode.

Ok I think see your point.
It sorta clashed with my setup because I wanted try using as cm as a trigger in normal mode and <leader>c in visual mode, but this caused cm to become an operator in visual mode as well which I didn't want.
I'll just use #98 to set up my mappings instead as you suggested in #104.


ideas

this is not an issue, just my idea about this plugin. I think to be truly interesting, it should handle file creation and naming too, appearing on the menu after a right click on a specific folder.
Because right now, i don't really file any advantage to use this, rather than hit ctrl+N and launch a snippet.
Best regards

Hi,

I have added a new version 1.1.6.
Thanks


[HOTFIX] Fixed all examples

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2803/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4049/

retest this please

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2805/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4051/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/4052/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2806/

LGTM


Updated dependabot to check dependencies in the main webapp.

Changes proposed in this pull request:

Updated dependabot to check dependencies in the main webapp.

I suspect we also need to add a package-lock.json file to the repository, no?

I don't think the package-lock.json is required.  The other package.json that Dependabot is checking in docs/ and main/tests/cypress do not have package-lock.json checked in either.

At least that is what I am seeing in the GitHub UI:

I added the package-lock.json.


Update set-policy to remove list

fixes #44

Hi @ritazh - why does the list policy need to be removed?


fixed interval loop

primary simulation loop runs too quickly or too slowly, need to give it a fixed interval.

https://stackoverflow.com/questions/56253623/how-can-i-run-a-set-of-functions-on-a-recurring-interval-without-running-the-sam
std solution

literally just used sleep in the loop
closing this issue with a tear


show stops on map

I just made the initial commit for this issue on a new branch.
Can you have a quick check on my work?
PS: Currently stops return null from api. I added if/else statement inside stop marker function.

Open a PR for this issue #21

closing due to #23


Add ReferencedAttribute for Check and Quota result.

This change is

@qiwzhang: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
8746fa8254b811b3deb506898ad5f2bd78a1c75e
link
/test mixer-e2e-smoketest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/lgtm

/approve

NONE


⚠ Bofrost.fr has degraded performance

In 4299f65, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1199 ms

Resolved: Bofrost.fr performance has improved in 41b8f2b after 6 minutes.


I have added java7&java8 by jenv, but only 'system' available

refer to http://www.jenv.be/
I installed jenv by brew, set the configure

echo 'export PATH="$HOME/.jenv/bin:$PATH"' >> ~/.bash_profile
echo 'eval "$(jenv init -)"' >> ~/.bash_profile

And, added java7 & java8 which hava been installed before.

jenv add /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home
jenv add /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home

also, I restart my terminal before I use jenv.
but when I tap 'jenv version' and enter, only 'system' appear.
I tried add java8 one more time, then it warn that
There is already a oracle64-<IP_ADDRESS> JDK managed by jenv
I'm puzzled about it, can you give me some advice to solve it?
thanks a lot~
[ by the way, how can I paste a img in issue?

Oh....I'm sorry It shoule be jenv versions


fix: 修复useMessage文件type类型报错

General

✏ Mark the necessary items without changing the structure of the PR template.

[ ] Pull request template structure not broken

Type

ℹ What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉 Put an x in the boxes that apply.

[ ] My code follows the style guidelines of this project
[ ] Is the code format correct
[ ] Is the git submission information standard?
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@a63149300  新版本的antdv引发的类型问题 我锁死vue版本 回滚了下antdv的版本 现在类型问题正常了


[submodule-sync] bot-submodule-sync-branch-23.04 to branch-23.04 [skip ci] [bot]

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
 If failed, it will remain open until test pass or manually fix.


Move PointF/SizeF calculations to it's own namespace

Something like LemonUI.Math, like GTA.Math.

They will be removed in #145, instead pointing to the LemonUI.Tools.Extensions class.


Do not rely on Leader/Follower to position DropdownMenu menu

Description
This PR removes DropdownMenu usage of Leader/Follower.
Leader/Follower positioning was introduced in https://github.com/flutter/flutter/pull/154667 which uses Leader/Follower approach to fix some weird positioning issues (such as https://github.com/flutter/flutter/issues/149037).
Unfortunately, it also introduces some regressions, see:

https://github.com/flutter/flutter/issues/157916
https://github.com/flutter/flutter/issues/158924

Because https://github.com/flutter/flutter/pull/154667 is already included in the beta channel, cherry-picking this PR should be considered.
Context
This PR is not a full revert and keeps Leader/Follower usage in MenuAnchor because this usage is optional and doesn't cause any regression.
There are some ongoing work which might fix or mitigate this problem:

https://github.com/flutter/flutter/pull/157921
https://github.com/flutter/flutter/pull/158255

Related Issue
Fixes https://github.com/flutter/flutter/issues/157916
Fixes https://github.com/flutter/flutter/issues/158924
Reopens https://github.com/flutter/flutter/issues/123395
Reopens https://github.com/flutter/flutter/issues/149037
Reopens https://github.com/flutter/flutter/issues/151856

Seems like there is a tradeoff here, and we need to decide which set of bugs is more detrimental to the user.
The regressions look like they are annoying, but the issues that this reopens are also pretty bad: they hide the dropdown on a mobile device because the keyboard covers up the menu, and the menu gets disconnected from the anchor when scrolling.
Are you expecting that the two other PRs referenced will fix the reopened issues, or are they just related?
Also, the "Fixes" section in this PR description seem to refer to the PRs, not the bugs, so you might want to update the numbers there.

Thanks for the feedback :pray:
(I have edited the description to fix the two links in the "fixes" section, thank for noticing this).

Seems like there is a tradeoff here, and we need to decide which set of bugs is more detrimental to the user.

Yes, there is a tradeoff. The main reason I filed this PR is that we are probably close to a stable release and I think this has an impact on the decision.

Are you expecting that the two other PRs referenced will fix the reopened issues, or are they just related?

One of the PR,, is a direct attempt to fix the first regression. But it is still a draft and It might take time to discuss and review this solution and it probably needs more work because being able to move the menu above the field is a good first step but not as smart as the current positioning logic that MenuAnchor offers when not using Leader/Follower.
The second PR introduces RawMenuAnchor in the widget library, I don't think it will fix the reopened issues. But it might help. It is a promising and huge PR so it might takes time to review it.
In summary, there are pending work that will help to fix the referenced regressions, but the corresponding PRs might not be ready for the next stable release.

Option 1: Close this PR
Downside: We'll be stuck with the following two issues. What would be the long term plan for addressing these if we go with this option?
https://github.com/flutter/flutter/issues/157916: DropdownMenu menu always appears below the TextField
A bad one because Dropdowns at or near the bottom of the screen are unusable on all platforms. The workaround would be to move the Dropdown.
https://github.com/flutter/flutter/issues/158924: Cannot scroll to the bottom of DropdownMenu
Also a bad one because latter menu items are not clickable. It seems to affect all platforms. Affects only longer lists,  but that's probably common (in the issue, a Dropdown in the center of the screen with 8 items repros the bug). Workaround would just be to keep the list shorter.
Option 2: Merge this PR
The above two issues will be fixed, but the following ones will be reopened. They might be fixed with work in progress in https://github.com/flutter/flutter/pull/157921 and https://github.com/flutter/flutter/issues/158924, but those probably won't be done by the next release.
https://github.com/flutter/flutter/issues/123395: Menu appears behind the keyboard
Android only, doesn't happen all the time. The user can work around the problem by closing the keyboard. Admittedly though, it looks very bad.
https://github.com/flutter/flutter/issues/149037: DropdownMenu Entries Not Positioned Correctly on Keyboard Appearance
Looks to me like a duplicate of the previous issue.
https://github.com/flutter/flutter/issues/151856: DropdownMenu doesn't follow in scrollable
All platforms. Affects any Dropdown in a Scrollable, which is probably a good amount. The user can work around the problem by closing and reopening the menu and not scrolling. Looks bad.
So what should we do?
It looks to me like option 2 gets us in a better state. The issues we'd have are ugly but not app-breaking. Also, we seem to have a potential path forward to fixing them with https://github.com/flutter/flutter/pull/157921 and https://github.com/flutter/flutter/issues/158924. I say we merge this PR and then follow up on making sure those issues get fixed.

@itsjustkevin The two PRs that this reverts (https://github.com/flutter/flutter/issues/157916 and https://github.com/flutter/flutter/issues/158924) have already rolled into beta, so this PR should be cherry picked into beta if possible.


May I ask how does the author establish the matrix A

The matrix "A" in the code is the normalized graph adjacency matrix (generally written as \hat{A} in the literature on GCN).


HTML not decrypted after reload

Hi,
I have detected that when I execute this in Javascript:
window.location.reload()
After reloading the raw html file (encrypted) gets displayed instead of the decrypted version. I managed to work around the problem by doing this instead:
window.location = window.location.href.replace(/#.*/, '');
I believe the problem might be isCryptFiles. It doesn't take into account that the URI might have a fragment identifier and it doesn't look like this situation is handled anywhere else.

Is the environment Android?
Please try the latest version.

The environment was indeed Android. I am sorry but I can't try the latest version: the project on which the problem was detected is already closed and I'm too busy right now to take it back.

OK. Close this issue.

I have this issue with the latest version. And blaskurain  workaround didn't work for me.
What I am trying to do is to reload the app when the user logs out. and it loads the index.html file but encrypted !


Add new EasyRPG strings (terms and skill/item usage messages)

This pull requests add some EasyRPG-customizable terms. They will only work in EasyRPG, and will be overriden if someone attemps to edit the project in RPG Maker 2000/2003.
Some allow to replace hardcoded things (like terms in the Status scene), while others allow to customise messages per item or per skill.

Introduced in liblcf#419

@easyrpg_using_message in RPG::Item: per-item custom message about using the item,
@easyrpg_battle_message_2k3 in RPG::Skill: per-skill custom message about using the skill,
easyrpgAnnBattleItem2k3 term: generic message before using a skill (allows %S, %O placeholders)
easyrpgAnnBattleSkill2k3 term: generic message before using an item (allows %S, %O, %U placeholders)

Introduced in liblcf#414:

easyrpgItemNumberSeparator term: Item number separator
easyrpgSkillCostSeparator term: Skill cost separator
easyrpgEquipmentArrow term: Equipment window arrow
easyrpgStatusSceneName term: Status scene Name
easyrpgStatusSceneClass term: Status scene Class
easyrpgStatusSceneTitle term: Status scene Title
easyrpgStatusSceneCondition term: Status scene Condition
easyrpgStatusSceneFront term: Status scene Front
easyrpgStatusSceneBack term: Status scene Back
easyrpgOrderSceneConfirm term: Order scene Confirm
easyrpgOrderSceneRedo term: Order scene Redo
easyrpgAnnBattleDoubleAttack2k3 term: RPG Maker 2003 battle monster Double Attack notification
easyrpgAnnBattleDefend2k3 term: RPG Maker 2003 battle monster Defend notification
easyrpgAnnBattleObserve2k3 term: RPG Maker 2003 battle monster Observe notification
easyrpgAnnBattleCharge2k3 term: RPG Maker 2003 battle monster Charge notification
easyrpgAnnBattleSelfdestruct2k3 term: RPG Maker 2003 battle monster Self-Destruct notification
easyrpgAnnBattleEscape2k3 term: RPG Maker 2003 battle monster Escape notification
easyrpgAnnBattleSpecialCombatBack2k3 term: Message for back and pincer attack

I'd say RPG::Terms should be moved to SchemaLDBTerms.txt and the original code there removed... it was moved into a separate file because there are a lot of terms

All seems well, merging, thank you


Template doesn't have contributor agreement

When updating the docs for the MongoDB Charm, @grobbie pointed out that the CONTRIBUTING file should have the Canonical Contributor Agreement. Additionally, should the README have license and security sections?

My opinion is yes, these are important pieces of information and guidance that help to inform users, and should be included in every README.


chore(main): release 4.1.3

:robot: I have created a release beep boop
4.1.3 (2024-08-03)
Bug Fixes

pressing <esc> has a 1 second delay (#311) (c38ca8f)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v4.1.3
:sunflower:


Debugging SPFx Solutions in Github Codespaces

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

SPFx 1.13.1
Node.js 14

Issue description
Would it be possible to debug SPFx solutions using Github workspaces?
When I just try to run the solution as is, I get an error in the hosted workbench:
https://steria.sharepoint.com/_layouts/15/workbench.aspx?debug=true&noredir=true&debugManifestsFile=https://shurick81-alexsapozhkov-codespaces-demo-00-77p5r5x73xrpw-4321.githubpreview.dev/temp/manifests.js

I try to dig deeper and checking https://shurick81-alexsapozhkov-codespaces-demo-00-77p5r5x73xrpw-4321.githubpreview.dev/temp/manifests.js in the browser, I'm getting a Bad Gateway error:

Then I try to fix the latter one and do the following changes (that helps for running SPFx gulp serve in containers: https://github.com/pnp/docker-spfx#known-issues):

Modify node_modules\@microsoft\spfx-heft-plugins\lib\plugins\webpackConfigurationPlugin\WebpackConfigurationGenerator.js:393

const debugBaseUrl = `${serveConfig.https ? 'https' : 'http'}://${serveConfig.hostname || 'localhost'}:${serveConfig.port || 4321}/${distFolderName}/`;

to:
const debugBaseUrl = `${serveConfig.https ? 'https' : 'http'}://localhost:${serveConfig.port || 4321}/${distFolderName}/`;

map the workbench to <IP_ADDRESS>, by modifying the ./config/serve.json file in your SharePoint Framework project to:

{
  "$schema": "https://developer.microsoft.com/json-schemas/core-build/serve.schema.json",
  "port": 4321,
  "hostname": "<IP_ADDRESS>",
  "https": true,
  "initialPage": "https://enter-your-SharePoint-site/_layouts/workbench.aspx"
}

I get the response when I request js file then:

However, when I try to run the hosted workbench, I get new issues:

When I look into developer tools in the browser, I can see that the browser is getting proper response from https://shurick81-alexsapozhkov-codespaces-demo-00-77p5r5x73xrpw-4321.githubpreview.dev/temp/manifests.js but then it is trying to access resources from https://localhost:4321/temp/manifests.js and of course fails:

I might guess that the reason is that the file https://shurick81-alexsapozhkov-codespaces-demo-00-77p5r5x73xrpw-4321.githubpreview.dev/temp/manifests.js actually contains a lot of references on the localhost:

Hi @shurick81 - in 1.14 beta (that should be released soon) we introduced new configuration called ipAddress. This property is used explicitly wind up the server and doesn't impact the debugging urls.
Although, it was done for Docker scenarios, it might be helpful here as well. You can specify both ipAddress and hostname to achieve your needs.
Please, share the results with us, too!

When you open an SPFx project in Codespaces, you are getting a new VM based on the default Linux container (unless you have configured .devcontainers). Regardless, because this is a new "machine," you have to generate the developer certificate, download it to your local machine and install it in the Certificate store.  If not, localhost will not deliver the manifest.js file to your browser and you get the initial errors you are seeing. (Error loading manifest.js)

@DonKirkham, thanks, but as I noted above, getting manifest.js was not prevented by certificate, but only by the host name configuration. I'm not sure how it was in earlier times of Codespaces, but right now its proxy is exposing SSL with it's own certificate, so adding the certificate from container to the client device should not be necessary.

@shurick81 - Can you please try to

Open the code in VS code using the Remote explorer extension

In the VS code terminal run gulp serve
You should see a message that port 4321 is forwarded
In case you see Error loading debug manifests message - check if the manifest.js is being served from localhost first and then you can solve that error using this post
Or you can run the below commands in VS code terminal and install the certificate on your local machine

gulp trust-dev-cert
cp ~/.gcb-serve-data/gcb-serve.cer ./spfx-dev-cert.cer
cp ~/.gcb-serve-data/gcb-serve.cer ./spfx-dev-cert.pem

Ok, I run "View: Show Remote Explorer"

in VS code terminal I run gulp serve

Where should I see that message that port 4321 is forwarded?
I can see this if I switch tab to "PORTS":

I can see that the manifests file is served:

What certificates on what local machine? On my local machine when I access manifests, they are served behind the application proxy that is using a publicly valid certificate:

Interesting. I think I have seen this in the past when I used the spfx docker image to create the codespace. Can you try without the spfx docker image?

Create an empty repo in GitHub with just a README file
Create a codespace for that repo in github.com
Open that codespace in VS code
In the terminal, run the command npm install gulp-cli yo @microsoft/generator-sharepoint --global to install the SPFx pre-reqs
After that create a new SPFx project with yo @microsoft/sharepoint
Once complete run gulp serve
You should the below message in VS code at the bottom right

In the Ports tab you should see ports 4321 and 35729 being forwarded to <IP_ADDRESS>

The picture you are showing with ports @anoopt, it is not from Codespaces, it is from remote containers, right? In this case yes it will be <IP_ADDRESS> on your machine and it will be exposed via the same SSL certificate that you set up in browser. Github Codes Codespaces is different in this sense: it is exposed on the remote host. That is why it is important that manifests refer to the remote host name too. You can see in my previous comments that probably the issue is that even though all assets are hosted on the shurick81-alexsapozhkov-codespaces-demo-01-96j5q5x6h7xgq-4321.githubpreview.dev host name, manifests are referring to localhost. As a result, the browser can reach manifests file without issues but then browser executes it and trying to reach resources on localhost, which will never work for Github Codespaces.

Thanks @shurick81 - the ports are from codespaces as you can see it under Origin column in the screenshot.
What I have noticed is when I have the .devcontainer folder with the files that you have in your repo and create a codespace for that repo, then the codespace gets created with the ``m365pnp/spfx:1.14.0` image. With that image the ports get forwarded to the codespace host and not to <IP_ADDRESS>.
So, if you create new repo without the .devcontainer folder, create a codespace for that and then do the initial SPFx setup on that codespace, open the codespace on VS code on your machine, you should see the ports forwarded correctly.
Not sure if the image m365pnp/spfx:1.14.0 in devcontainer.json is not being liked by codespaces. Need to check.

Thanks @anoopt, you were totally right, now it is working in codespaces in VS and everything exposed on <IP_ADDRESS>:

And this is considering that I don't even have Docker running on this machine, just VS and browser. The container is completely remote but somehow it is exposed on the <IP_ADDRESS>...
How will I sleep now without understanding how this exposure is controlled...

I digged a bit deeper now and the only change I needed to do in order to make the port available on the localhost is this: https://github.com/alexsapozhkov/codespaces-test-04/commit/7e637207703f7098b8bd5f12e67ec7f189742c47
The image m365pnp/spfx:1.14.0 is just fine. The only problem was the configuration of ports that dictated Codespaces to forward them to https://*.githubpreview.dev. See more: https://code.visualstudio.com/docs/remote/devcontainerjson-reference

I think we could close this issue since debugging is now working with Codespaces. However, then we need to open a new issue regarding debugging without Visual Studio installed, with just browser. When I use just browser, without Visual Studio, it is of course not possible to expose the container port on the localhost, so the port is forwarded to https://*.githubpreview.dev.
In such scenario, gulp serve should generate assets that refer to the remote host name in *.githubpreview.dev space. But that should be probably registered as a separate issue?