Enabling/disabling elevated button causes it to flash black

When you tap "ADD" the first time in the sector demo, the "REMOVE" button blinks black.

This is also experiencing some of #399. Also, tapping "add" then "remove" then "remove" again causes the entire engine to crash.

I can't reproduce the crash mentioned in the second comment. The issue in the first comment seems to be related to the animated container inside a MaterialButton. It slows down and becomes clear if you set a time dilation.

Ok, here's the problem. Disabled raised buttons use Colors.black12, aka const Color(0x1F000000). Enabled raised buttons use Colors.grey[300], aka const Color(0xFFE0E0E0).
When you switch from one to the other, we animate between them, which, when composited against the material background behind, means it cycles through these colours:

...and that's where the blackness comes from.

There's also something really weird going on with the shadow transitions.

I have an in-progress fix for this but it's blocked on making progress on https://github.com/flutter/flutter/issues/1701.

What I'm going to do for the color transition is instead of transitioning the color of the print, I'll transition a circle clip of the material laid on top.

Need to fix https://github.com/flutter/flutter/issues/3493 first though.

Is this still an issue?

Yep.

When _MaterialInteriorState rebuild, _MaterialInterior's color change from Color(0x1f000000) to Color(0xffe0e0e0).
But identical(oldColor, newColor) return true.

Add new Reproduce Code.
`class MyRenderPhysicalShapeDemo extends StatefulWidget {
@override
MyRenderPhysicalShapeState createState() {
return MyRenderPhysicalShapeState();
}
}
class MyRenderPhysicalShapeState extends State {
double _insets = 0.0;
double _opacity = 0.0;
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(title: Text('MyRenderPhysicalShapeDemo')),
body: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: [
Slider(
value: _insets,
onChanged: (value) => setState(() => _insets = value),
),
MyPhysicalShape(
insets: _insets,
child: Container(
width: 50,
height: 50,
),
)
]));
}
}
class MyPhysicalShape extends SingleChildRenderObjectWidget {
final _insets;
MyPhysicalShape({double insets, Widget child})
: this._insets = insets,
super(child: child);
@override
RenderPhysicalShape createRenderObject(BuildContext context) {
return RenderPhysicalShape(
clipBehavior: Clip.none,
color: Color(0x61000000),
clipper: ShapeBorderClipper(
shape: CircleBorder(),
textDirection: Directionality.of(context),
),
shadowColor: Colors.black,
elevation: _insets * 2,
);
}
@override
void updateRenderObject(BuildContext context, RenderPhysicalShape renderObject) {
renderObject
..elevation = _insets * 2;
}
}`

The solution is to split the animation into two phases, one where we turn the transparent elevation=0 raised button into an opaque elevation=0 raised button, and a second phase where we adjust the elevation.

I think fixing https://github.com/flutter/flutter/issues/48534 would fix this, right?
i.e. if Color.lerp handled lerping through transparent colors more gracefully we wouldn't see the darker grays.

Just verified it would not - there's a different issue going on here.

I was able to reproduce this on latest master channel.

 sample code
import 'package:flutter/material.dart';
import 'package:flutter/scheduler.dart';

void main() {
  timeDilation = 3.0;
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  bool _buttonEnabled = true;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Text(
              'foo text',
            ),
            RaisedButton(
                child: Text(_buttonEnabled ? 'Enabled' : 'Disabled'),
                onPressed: _buttonEnabled ? () {} : null),
            RaisedButton(
                child: Text('Toggle enabled'),
                onPressed: () =>
                    setState(() => _buttonEnabled = !_buttonEnabled)),
          ],
        ),
      ),
    );
  }
}

 flutter doctor -v
[✓] Flutter (Channel master, 1.22.0-2.0.pre.77, on Mac OS X 10.15.6 19G2021,
    locale en)
    • Flutter version 1.22.0-2.0.pre.77 at
      /Users/pedromassango/dev/SDKs/flutter_master
    • Framework revision c8f3df7ea5 (8 hours ago), 2020-08-25 21:26:05 -0400
    • Engine revision b1d9f863db
    • Dart version 2.10.0 (build 2.10.0-56.0.dev)

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor
      --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

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

[!] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] IntelliJ IDEA Community Edition (version 2020.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 48.1.4
    • Dart plugin version 202.6397.47

[!] VS Code (version 1.48.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • sdk gphone x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API
      30) (emulator)
    • macOS (desktop)         • macos         • darwin-x64     • Mac OS X
      10.15.6 19G2021
    • Web Server (web)        • web-server    • web-javascript • Flutter Tools
    • Chrome (web)            • chrome        • web-javascript • Google Chrome
      84.0.4147.135

! Doctor found issues in 3 categories.

@Hixie since the widget in question (RaisedButton) was deprecated in https://github.com/flutter/flutter/pull/59702 by @HansMuller I'm wondering if this issue is worth a fix and if it should remain opened.

Does the problem exist with ElevatedButton?

The problem does still occur with ElevatedButton. I will look into it.

The source of the problem is that Material with non-zero elevation is filled with the (default gray) shadowColor. In the screenshot below the top rectangle is defined with
Material(elevation: 0.0001, color: Colors.blue.withOpacity(0.12))

The bottom rectangle is:
Material(elevation: 0, color: Colors.blue.withOpacity(0.12))

The fill color for a disabled button has opacity 0.12. When the button's fill color animates from its opaque enabled color to the translucent disabled fill color, the elevation shadow continues to show through until the elevation finally reaches 0. To avoid this, we'll need to do the transition in two steps: first the elevation, then the color.

Just FTR, the original OutlineButton widget dealt with this problem, see https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/material/outline_button.dart#L396


Is it possible to edit \ update previously sent message to skype \ telegram \ slack?

Actually, telegram Bot API has this feature https://core.telegram.org/bots/api#updating-messages
Slack also has this feature https://api.slack.com/methods/chat.update
What about skype, I didn't find the answer.
I wonder whether it is possible or not to edit previously sent message by bot framework?

The botbuilder SDKs do not support this directly, but you can do it using the channelData field of the message activity. The channelData field allows your bot to send channel-native messages. Some documentation exists here (not specific to C#, even though it is in the URL):
https://docs.botframework.com/en-us/csharp/builder/sdkreference/channels.html

Great, thanks. But what about skype there is no any mention of it on that page, is it means that skype is not support this feature?

No, Skype does not support editing /updating previously sent messages.

@eanders-MS ok, got it

a old api version, i can send a message, pick your ID and edit it...

I understand that this is not supported but it appears that slack enables this behavior by exposing a editMessage endpoint on their API (as opposed to postMessage which just adds a message). Using channelData we cannot tell the connector which slack endpoint to use. How can the bot builder framework support the edit scenario on slack?


Show actual dataset name in swebench log directory

Previously, all evaluation results on SweBench were saved under the swe-bench-lite directory, regardless of the actual dataset name. This PR addresses this issue by using  args.dataset.replace("/", "__") + "-" + args.split.replace("/", "__")

Hi the linter issue is fixed now. It's a sample PR so I previously directly used github workspace and haven't set up the dev env.


preview only white screen

Describe the bug
preview only white screen
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-hxfen9
Steps to reproduce
preview only white screen
Expected behavior
preview only white screen
Screen Recording / Screenshot
preview only white screen
Platform
Browser name = Firefox
Full version = 133.0
Major version = 133
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:133.0) Gecko/20100101 Firefox/133.0
performance.memory = undefined
Username = hanshir
Chat ID = 1333cf890c19

Additional context
preview only white screen

Appreciate the feedback! We are aware of this issue and are tracking it here. Something to initially try is to make sure you are using Chrome or a Chromium browser as those are most compatible with Bolt.


Improve docs for runBefore() / runAfter()

@koskimas I should have noticed this when creating #796, but here a follow-up PR that improves docs further.
We could consider making these return result; statements optional with a simple change to this line:
https://github.com/Vincit/objection.js/blob/4db6fad8671c321e5317c57c8f6022ece964c02d/lib/queryBuilder/QueryBuilder.js#L1319
->
promise = promise.then(result => {
  const res = func.call(builder, result, builder);
  return res !== undefined ? res : result;
});

Wait, that's not the only place that would need changing. These two would need similar changes:
https://github.com/Vincit/objection.js/blob/74a0d6f5189eba9e00ec8f4709e7c7f772c234d1/lib/queryBuilder/operations/RunBeforeOperation.js#L10
https://github.com/Vincit/objection.js/blob/74a0d6f5189eba9e00ec8f4709e7c7f772c234d1/lib/queryBuilder/operations/RunAfterOperation.js#L10

Coverage remained the same at 95.052% when pulling db4dc278bca62a0f1c940205327136c84e7411c9 on lehni:fix/docs-run-before-after-2 into 21b09cae456d73aee4767bff9cd7148f9331835c on Vincit:master.

Coverage remained the same at 95.052% when pulling db4dc278bca62a0f1c940205327136c84e7411c9 on lehni:fix/docs-run-before-after-2 into 21b09cae456d73aee4767bff9cd7148f9331835c on Vincit:master.

@koskimas PS: If you think the above suggestion makes sense, I'm happy to create a PR and some tests for it.

Thanks! Let's not add the undefined handling you suggested. You would need to handle the case where undefined promise is returned too and that would complicate things:
runAfter(async () => {
  await something();
  // No return value --> a promise resolving to `undefined` gets returned.
})

That's a good point! I agree, let's keep it simple.


18318: Stop raising exception for missing columns

Don't know why some rows wouldn't have all data, but his makes the code robust for those ocassions


Fix redaction of conformance tests

Debugging the call to Debugf shows it's being called as Debugf("%s", "... logs that should be redacted ..."). Our previous redaction only ran on the format string, and not the rest of the args. This moves the redaction to run on the final logged output.
Fix #521. Replace #523.

cc @jdolitsky @shizhMSFT .

I did a check of the recent PRs to oci-conformance and everything is redacted there, so this would have broken sometime after November 2023.


Update link to Web authentication broker sample

The previous link: https://code.msdn.microsoft.com/windowsapps/Web-Authentication-d0485122 is dead. updating link to point to the Windows 10 universal sample page for web authentication broker.

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

Thanks for your contribution, I've merged your changes and they should be live soon.


Build failure with nan 2.0.0

Today nan 2.0.0 has been released, and ffi doesn't compile anymore:
$ npm install sleep
|
><EMAIL_ADDRESS>install /home/alexey/node_modules/sleep
> node-gyp rebuild

make: Entering directory `/home/alexey/node_modules/sleep/build'
  CXX(target) Release/obj.target/node_sleep/sleep.o
../sleep.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE Sleep(Nan::NAN_METHOD_ARGS_TYPE)’:
../sleep.cc:36:12: error: ‘NanScope’ was not declared in this scope
   NanScope();
            ^
../sleep.cc:38:7: error: ‘args’ was not declared in this scope
   if (args.Length() < 1 || !args[0]->IsUint32()) {
       ^
../sleep.cc:39:54: error: ‘NanThrowError’ was not declared in this scope
     return NanThrowError("Expected number of seconds");
                                                      ^
../sleep.cc:39:54: error: return-statement with a value, in function returning 'void' [-fpermissive]
../sleep.cc:42:9: error: ‘args’ was not declared in this scope
   sleep(args[0]->Uint32Value());
         ^
../sleep.cc:44:22: error: ‘NanReturnUndefined’ was not declared in this scope
   NanReturnUndefined();
                      ^
../sleep.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE USleep(Nan::NAN_METHOD_ARGS_TYPE)’:
../sleep.cc:48:12: error: ‘NanScope’ was not declared in this scope
   NanScope();
            ^
../sleep.cc:50:7: error: ‘args’ was not declared in this scope
   if (args.Length() < 1 || !args[0]->IsUint32()) {
       ^
../sleep.cc:51:59: error: ‘NanThrowError’ was not declared in this scope
     return NanThrowError("Expected number of microseconds");
                                                           ^
../sleep.cc:51:59: error: return-statement with a value, in function returning 'void' [-fpermissive]
../sleep.cc:54:10: error: ‘args’ was not declared in this scope
   usleep(args[0]->Uint32Value());
          ^
../sleep.cc:56:22: error: ‘NanReturnUndefined’ was not declared in this scope
   NanReturnUndefined();
                      ^
../sleep.cc: In function ‘void init(v8::Handle<v8::Object>)’:
../sleep.cc:61:16: error: ‘NanNew’ was not declared in this scope
   exports->Set(NanNew<String>("sleep"), NanNew<FunctionTemplate>(Sleep)->GetFunction());
                ^
../sleep.cc:61:29: error: expected primary-expression before ‘>’ token
   exports->Set(NanNew<String>("sleep"), NanNew<FunctionTemplate>(Sleep)->GetFunction());
                             ^
../sleep.cc:61:64: error: expected primary-expression before ‘>’ token
   exports->Set(NanNew<String>("sleep"), NanNew<FunctionTemplate>(Sleep)->GetFunction());
                                                                ^
../sleep.cc:61:74: error: request for member ‘GetFunction’ in ‘Sleep’, which is of non-class type ‘Nan::NAN_METHOD_RETURN_TYPE(Nan::NAN_METHOD_ARGS_TYPE) {aka void(const Nan::FunctionCallbackInfo<v8::Value>&)}’
   exports->Set(NanNew<String>("sleep"), NanNew<FunctionTemplate>(Sleep)->GetFunction());
                                                                          ^
../sleep.cc:62:29: error: expected primary-expression before ‘>’ token
   exports->Set(NanNew<String>("usleep"), NanNew<FunctionTemplate>(USleep)->GetFunction());
                             ^
../sleep.cc:62:65: error: expected primary-expression before ‘>’ token
   exports->Set(NanNew<String>("usleep"), NanNew<FunctionTemplate>(USleep)->GetFunction());
                                                                 ^
../sleep.cc:62:76: error: request for member ‘GetFunction’ in ‘USleep’, which is of non-class type ‘Nan::NAN_METHOD_RETURN_TYPE(Nan::NAN_METHOD_ARGS_TYPE) {aka void(const Nan::FunctionCallbackInfo<v8::Value>&)}’
   exports->Set(NanNew<String>("usleep"), NanNew<FunctionTemplate>(USleep)->GetFunction());
                                                                            ^
make: *** [Release/obj.target/node_sleep/sleep.o] Error 1
make: Leaving directory `/home/alexey/node_modules/sleep/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:820:12)
gyp ERR! System Linux 4.0.0-2-amd64
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/alexey/node_modules/sleep
gyp ERR! node -v v0.10.40
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the sleep package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls sleep
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 4.0.0-2-amd64
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "sleep"
npm ERR! cwd /home/alexey
npm ERR! node -v v0.10.40
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0

The API has been changed significantly, and ffi will probably need substantial changes. Meanwhile, please depend on nan "<2.0.0" so that ffi can be installed.

@TooTallNate Do you have time to do it? Just a package.json fix.
Meanwhile I started to work on nan2 support.

Pull request #216.


Fixed visibility of the filter clearing link

https://bugzilla.redhat.com/show_bug.cgi?id=1298369

@skateman test is broken

verified fix in UI.


Some small fixes. Closes #2459

Just a few basic fixes I did while trying to setup proper e-mail testing.

Something up with Travis?

Ah the joys of 5.3 ... no session_status()

What's up with php 7 going missing on the MySQL branch though?

Just Travis being a naughty boy ... I'll restart that run

If someone has reached this limit I start wondering if smallint is too low for mentions...

People generally won't be keeping mentions around.
People do keep their roleplays, though.


Stand up banner for 10/10-10/11

Get the banner to @jhibbets and @zachambrose

@jhibbets you're going to bring this to Innovators Program Demo Day, right?

yes
On Tue, Oct 3, 2017 at 9:52 AM, zachambrose<EMAIL_ADDRESS>wrote:

@jhibbets https://github.com/jhibbets you're going to bring this to
Innovators Program Demo Day, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-333848616,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoV6Z5rodtAa_G2OLLeeKBGVRIn3xRks5sojwQgaJpZM4PsGtT
.

Easiest to bring to 10/9 meetup and hand off there. Leaving open to remind myself to put it in the car.

+1
On Oct 4, 2017 6:51 AM, "Chris Mathews"<EMAIL_ADDRESS>wrote:

Easiest to bring to 10/9 meetup and hand off there. Leaving open to remind
myself to put it in the car.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-334119022,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoVwQyt7xYtSa9_63Ksuu7w9SEU9OQks5so2M1gaJpZM4PsGtT
.

I will send your easels then also.
On Oct 4, 2017 8:32 AM, "Jason Hibbets"<EMAIL_ADDRESS>wrote:

+1
On Oct 4, 2017 6:51 AM, "Chris Mathews"<EMAIL_ADDRESS>wrote:

Easiest to bring to 10/9 meetup and hand off there. Leaving open to
remind
myself to put it in the car.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-
334119022>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADgoVwQyt7xYtSa9_
63Ksuu7w9SEU9OQks5so2M1gaJpZM4PsGtT>
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-334140144,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMJnMwVXdyeSkDvDPCn0aaKmkUZDyWxfks5so3rRgaJpZM4PsGtT
.

Don't forget the orange lulu bag ;)
On Wed, Oct 4, 2017 at 9:04 AM, TaxLadyTracy<EMAIL_ADDRESS>wrote:

I will send your easels then also.
On Oct 4, 2017 8:32 AM, "Jason Hibbets"<EMAIL_ADDRESS>wrote:

+1
On Oct 4, 2017 6:51 AM, "Chris Mathews"<EMAIL_ADDRESS>wrote:

Easiest to bring to 10/9 meetup and hand off there. Leaving open to
remind
myself to put it in the car.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-
334119022>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADgoVwQyt7xYtSa9_
63Ksuu7w9SEU9OQks5so2M1gaJpZM4PsGtT>
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-
334140144>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AMJnMwVXdyeSkDvDPCn0aaKmkUZDyWxfks5so3rRgaJpZM4PsGtT>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-334148349,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoV9dACU4exOxv9L6nC2NE3FR36gsqks5so4J2gaJpZM4PsGtT
.

+1
Chris Mathews
On Wed, Oct 4, 2017 at 11:23 AM, Jason Hibbets<EMAIL_ADDRESS>wrote:

Don't forget the orange lulu bag ;)
On Wed, Oct 4, 2017 at 9:04 AM, TaxLadyTracy<EMAIL_ADDRESS>wrote:

I will send your easels then also.
On Oct 4, 2017 8:32 AM, "Jason Hibbets"<EMAIL_ADDRESS>wrote:

+1
On Oct 4, 2017 6:51 AM, "Chris Mathews"<EMAIL_ADDRESS>wrote:

Easiest to bring to 10/9 meetup and hand off there. Leaving open to
remind
myself to put it in the car.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/
issues/825#issuecomment-
334119022>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADgoVwQyt7xYtSa9_
63Ksuu7w9SEU9OQks5so2M1gaJpZM4PsGtT>
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-
334140144>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AMJnMwVXdyeSkDvDPCn0aaKmkUZDyWxfks5so3rRgaJpZM4PsGtT>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-
334148349>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ADgoV9dACU4exOxv9L6nC2NE3FR36gsqks5so4J2gaJpZM4PsGtT>

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-334192316,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtXVOD64ik8JBo0uo9o3yM1i-0F8uks5so6LegaJpZM4PsGtT
.

Nah, I thought I'd keep the bag lol
On Oct 4, 2017 11:25 AM, "Chris Mathews"<EMAIL_ADDRESS>wrote:

+1
Chris Mathews
On Wed, Oct 4, 2017 at 11:23 AM, Jason Hibbets<EMAIL_ADDRESS>wrote:

Don't forget the orange lulu bag ;)
On Wed, Oct 4, 2017 at 9:04 AM, TaxLadyTracy<EMAIL_ADDRESS>wrote:

I will send your easels then also.
On Oct 4, 2017 8:32 AM, "Jason Hibbets"<EMAIL_ADDRESS>wrote:

+1
On Oct 4, 2017 6:51 AM, "Chris Mathews"<EMAIL_ADDRESS>wrote:

Easiest to bring to 10/9 meetup and hand off there. Leaving open to
remind
myself to put it in the car.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/
issues/825#issuecomment-
334119022>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/ADgoVwQyt7xYtSa9_
63Ksuu7w9SEU9OQks5so2M1gaJpZM4PsGtT>
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/
issues/825#issuecomment-
334140144>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AMJnMwVXdyeSkDvDPCn0aaKmkUZDyWxfks5so3rRgaJpZM4PsGtT>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-
334148349>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ADgoV9dACU4exOxv9L6nC2NE3FR36gsqks5so4J2gaJpZM4PsGtT>

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-
334192316>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAOGtXVOD64ik8JBo0uo9o3yM1i-0F8uks5so6LegaJpZM4PsGtT>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/NCOpenPass/issues/825#issuecomment-334192962,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMJnM9BWPX2fIpGb1z7gx9mr7SMoB2P7ks5so6NNgaJpZM4PsGtT
.


model: transformers: ner: Change the links' formatting to rst

Fixes #559
I suppose this doesn't need a changelog

Perfect! Thank you!


Set correct AutoFocus value for FluentPopover

Fix #3597 The opened "Endpoints" window flashes but does not disappear when clicking anywhere on the dashboard page again
Microsoft Reviewers: Open in CodeFlow

The bulid break is known. Fixing with https://github.com/dotnet/aspire/pull/3662. When that gets merged we can rerun CI here.

/backport to release/8.0

/azd run

/azp run


remove redundant warning

Signed-off-by: Qiang Huang<EMAIL_ADDRESS>

LGTM

Updated.

Hmm, still failing. I'll fix it.

LGTM


nanotts: fix dependency on alsa-plugins

Description of changes
It was previously erroring out with the following error:
ALSA lib conf.c:4004:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so (/nix/store/l3m7axrj699nx4j024sb0dw0215alsd1-alsa-lib-<IP_ADDRESS>/lib/alsa-lib/libasound_module_conf_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib pcm.c:2735:(snd_pcm_open_noupdate) Unknown PCM default
error: opening pcm device failed No such file or directory

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

What is the next steps for this PR to be merged?
@Artturin , tagging you as you had reviewed the original PR.


Problem with datasets

I am wondering how to get the datasets like BA_shapes and BA_Houses
Cause in the function "load_syn_data",I can't find path "../../data/BA_Community/graph_ba_350_100_2comm.gpickel"

Hi, I did not upload the datasets to keep the repo size small. The graph classification datasets are part of the benchmark dataset for graph kernels released by TU Dortmund here.  The node classification datasets can be generated using the code provided for GNNExplainer here.
Let me know if you have any other questions. Thank you for your time and patience!


Problem accessing /j_spring_security_check

In the "setup-users" branch, when I try to login an existing user/pasword (ama/ama) via the custom form login I am getting the following HTTP ERROR 405:
Problem accessing /j_spring_security_check. Reason:
Request method 'POST' not supported

I am using "standard" Spring Security configuration via JDBC to user store, but it does not come to that point. I am suspecting a problem in the Spring Tiles configuration file...

The csrf values are not rendered in the login.jsp page:
  <form name='loginForm' action="${pageContext.request.contextPath}/j_spring_security_check" method='POST'>
    <input type="hidden" name="${_csrf.parameterName}" value="${_csrf.token}" />

When using http basic authentication to call protected resources (e.g. "http://localhost:8080/users/subscriptions") the automatic browser pop-up jumps asking for authentication and works after that.... This means the problem liest with custom login form configuration... (Tiles might have an impact...)

It was a configuration problem. The following in Spring Security 4 configuration file did the trick:
<form-login
  login-page="/login/custom_login"
  login-processing-url="/j_spring_security_check"
  username-parameter="username"
  password-parameter="password" />


add @graphiql/plugin-utils, docs to improve plugin development

as per conversations since 2019, and a conversation with users at GraphQL Berlin meetup, it's high time we start work on a simple set of utilities to enable graphiql plugin development!
this provides some conventions and abstracts away the details to make shipping plugins more readily poasible from this repo (or from any repo)
(also, as a platform engineer, seeing all the duplicate vite config and pain for users just made me sad, vite's plugin API was designed to eliminate such complexity!)

[x] vite plugin to abstract away config details
[x] shared tsconfig
[x] automatically rename output to match plugin name
[x] add docs for creating plugins

in later iterations

init script (npx create-graphiql-plugin myplugin)
validate package.json
extend vite plugin to show graphiql with plugin on vite command

Note: I've added a few commits to graphiql explorer plugin to this PR to fix an upstream issue, but I plan to backport them to happen independently as a bugfix, and restore copy-demo in a seperate PR

this PR will be re-created against main branch, and will continue using the index.umd.js pattern :)

recreated as #3346


Remove the requirement to hardcode the asset URL

Related to https://github.com/Shopify/oxygen-platform/issues/137
v3 action now takes

shop_id
storefront_id
build_command

deployment_id is no longer required.
See .github/workflows/ci.yml for new usage.

Amazing work 🎉


Fix KSCrash compilation against iOS 7.0 SDK

The definitions for CPU_TYPE_ARM64 and CPU_SUBTYPE_ARM_V8 are not present in the 7.0 SDK. This change guards against the CPU type check for these architectures.

Example compilation before the patch:

KSCrash/Source/KSCrash/Reporting/Sinks/KSCrashReportSinkQuincyHockey.m:239:14: use of undeclared identifier 'CPU_TYPE_ARM64'
        case CPU_TYPE_ARM64:
             ^

KSCrash/Source/KSCrash/Reporting/Sinks/KSCrashReportSinkQuincyHockey.m:246:22: use of undeclared identifier 'CPU_SUBTYPE_ARM_V8'
                case CPU_SUBTYPE_ARM_V8:
                     ^

Example compilation after patch is applied

Hang on with this. I'm probably going to restore support for earlier iOS versions.

Ah, cool. Thanks.

OK, latest release (1.0.1) supports ios 6, so we shouldn't need this anymore.

Thanks for taking a look, @kstenerud, though I can't confirm the fix. Even linking against 1.0.1, the issue persists for the iOS 7.0 SDK when linking against the KSCrashLib target in a workspace with KSCrash and Bugsnag. This particular project is not using CocoaPods.

Hmm ok. Well preprocessor checking won't hurt anything, but I think you need to add a check for arm v8 as well?

I think it passed because there was no case where arm v8 was defined but arm64 was not, but nesting both makes more sense. Patched!

Perfect! Thanks!

Thank you!


EITGenerator: enforce DVB 25 ms gap between consecutive sections

Related issue (if any):
DVB states that a 25 ms gap should be enforced between sections of the same PID, table ID and table ID extension.
Affected components:
EITGenerator
Brief description of the proposed changes:
This patch fixes plug-in eitinject.

Hi Thierry, and thanks for your work. DVB states that there should be a gap between the last byte of a section and the first byte of the next section with the same {PID, TID, TIDEXT}. The problem is that you have no way to know exactly when a section will be inserted, you only know the earliest date, and you certainly don't know the date of the last byte if the section is big and split into several TS packets (which can be the case for EIT).
It shouldn't be a problem if you have a high number of padding packets, but if the bandwidth is scarce, a section could be delayed signficantly. Besides you have no control over it. That is why I chose the current method that is 100% certain to enforce the section gap, but I leave it to you.

OK, I understand your concern about the gap after the last packet.

That is why I chose the current method that is 100% certain to enforce the section gap, but I leave it to you.

The timing issue of first vs. last packet of a section is the same with the two methods. The provideSection() method is called when the packetizer needs a section. You provide the section and then the packetizer will spead it over several TS packets in the next future. Therefore, when you reschedule sections in provideSection(), the rescheduled time is based on the time of the first packet of the current section, not the last one.

I think that the packetizer is the only object which is aware of the exact moment where the last packet of a section is injected.
Maybe I could enhance SectionProviderInterface to add an optional virtual method through which the packetizer will notify the section provider of the last packet of each section. In this method, you would ideally reschedule the sections of the same tid/tidext.
However, a corner case remains (also present in your PR). Let's assume that there is no enqueued section of the same tid/tidext and, consequently, nothing to reschedule. However, within the next 25 ms, a new section of the same tid/tidext is enqueued, and the queues are not much populated. Then, the section will likely be injected less than 25 ms after the previous one.
A general solution would be to keep a map of last injection time of last packet per tid/tidext. However, this would increase the burden even more. The EIT generator is very demanding in terms of resources, despite a few optimizations I implemented. An efficient and fully DVB compliant implementation would maybe require a complete rewrite. But I have no time for that.

If you look closely you'll notice that I only reschedule sections when the packetizer asks for a new section. That way I am sure that the previous section has been completely transmitted, so we have at least SECTION_GAP until the next section with identical TID,TIDEXT. In reality we have more than SECTION_GAP because the last section may have finished being transmitted earlier, but that's not a big deal in my opinion.
Of course having a callback in the packetizer to notify when a section has been fully transmitted would work to, and allow for a smaller gap.

If you look closely you'll notice that I only reschedule sections when the packetizer asks for a new section.

Sorry, my bad. I read it again more closely and realized that the rescheduling of sections concerned the previous section, the completed one, not the section which is returned by the provideSection() callback.

Hi Christophe,
I merged it in the master branch. Since I rebased before merging, the PR is not automatically detected as merged in GitHub and I will have to close the PR. If you look at the master branch, you will see your commit. I never understood this behavior and don't know how to fix it. Any idea?
There is another commit on top of it with a bunch of refactoring (I am in a background process of simplifying code since I dropped any pre-C++11 support).
I also modified one thing in your code: calling enqueueInjectSection() while working through the list was not appropriate since the call modifies that list, including the risk of invalidating the current iterator.

Merged


help: Regarding support issues for multi-agent environments

Hello, I am very interested in your work. I want to try using it in my experiment. But I don't know how to make it support multi-agent environments. I am a beginner, so my expression may not be accurate. Please forgive me.
In my environment, each step will return observations and rewards from multiple agents. The number of intelligent agents is fixed during the training process, but can be changed arbitrarily during testing. It seems that it can be seen as returning multiple batches within a step.
So how should I modify the code to perfectly integrate with your provided TransformerXL

Hi @liugehaizaixue
if the agents share the same policy, then it would be all bout adding this extra dimension about number of agents. I'd suggest to find a multi-agent PPO baseline to carefully check the differences to this single agent environment.
I also prepared an implementation of this repository as contribution to cleanrl. Maybe this is a helpful source towards your goals as well.
https://github.com/MarcoMeter/cleanrl-ppo-trxl/tree/master/cleanrl/ppo_trxl

Hi @liugehaizaixue
if the agents share the same policy, then it would be all bout adding this extra dimension about number of agents. I'd suggest to find a multi-agent PPO baseline to carefully check the differences to this single agent environment.
I also prepared an implementation of this repository as contribution to cleanrl. Maybe this is a helpful source towards your goals as well. https://github.com/MarcoMeter/cleanrl-ppo-trxl/tree/master/cleanrl/ppo_trxl

Thank you very much for your suggestion. I have started learning mappo according to your suggestion. However, I still really want to ask, are you interested in implementing an example of  mappo-trxl in the future? After all, you know ppo-trxl the best to write more perfect code.

Sorry, I don't have the capacity to implement multi-agent code.


JSON-LD 1.1 interest

I am curious if JSON-LD 1.1 is on the roadmap for this package.
https://json-ld.org/spec/latest/json-ld/
json-gold has been so wonderful to have and I'm just curious as I see 1.1 addressing some of the issues of multiple types and also being able to integrate things like GeoJSON elements into the JSON-LD object.
Thanks!
Doug

@fils the short answer is yes, absolutely. I've already put in some minor provisions to support it.
The long answer is: I haven't been following the latest development of this standard (since Dec 2017) and not 100% sure how stable it is. Also, the usefulness of this package (at least for us) depends on how up to date the other implementations are (JavaScript, Python and Java in particular).
Do you think it's a good time to start supporting 1.1?

Do you think it's a good time to start supporting 1.1?

Definitely! Full disclosure: I'm one of the Co-Chairs of the @w3c JSON-LD Working Group 😸
It would be great to have you join us as an implementer/tester as well as involved in the discussions around JSON-LD's future.
You can get involved via our various GitHub repos or join the W3C and then join the JSON-LD WG to get involved in our weekly phone discussions.
Regardless of what involvement you have time for, we'd appreciate the feedback you can contribute!
Thanks!
🎩

@BigBlueHat, I would be delighted help. We are actively using JSON-LD for the last 3 years and further development of the standard is of the utmost importance for us.
I'll take a look at the WG repos you mentioned. Any hints where my input would be most useful are welcome.

The syntax and api repos are likely of the greatest interest at this point. You can see more about what we plan to accomplish in our charter.
The other big area we could use help with is testing. We'll be continuing to use the current JSON-LD testing suite and at some point there will be an official W3C testing environment and process to get a "gold star" 🥇 as a conforming implementation--JSON-goLD is already listed there in fact! 😁
Lastly, there's a public mailing list where you can see some discussions and the posting of the call agenda and minutes each week. If you dig in deep enough, we'd also love to have you on the calls where final decisions are made by the group.
Thanks for all you're doing, and it's great to hear you've got so much experience with JSON-LD!

@BigBlueHat thanks for all the details.
It's our goal to always have 100% pass rate for the relevant test suite. By the way, providing this suite is a fantastic way to help JSON-LD developers with new implementations, it can't go any better!

@fils @BigBlueHat, we have implemented the initial support for JSON-LD 1.1 spec, see https://github.com/piprate/json-gold/pull/15. All 1.1 tests from the current official test suite pass, with an exception of 5 advanced framing tests. We don't support omitGraph option yet. I'll try to fix a couple of remaining tests, but this implementation is good enough to go live, in my opinion.
Having looked at the 1.1 spec in great detail I must say it's very good!

Added omitGraph support and fixed 2 framing tests. The only outstanding broken framing test is tg010, see https://github.com/piprate/json-gold/issues/13. I thought it's related to a different behaviour in 1.1, but it appears to have a different issue with document base. Will describe in #13.

@gkellogg many thanks for the pointer. I've taken the tests from the repos mentioned above and raised a new PR. There are a lot of additions, and the pass rate dropped to 87% (see the conformance report here). I implemented some of the smaller updates and marked the remaining unsupported/failing tests as to-be-skipped for now. The largest outstanding areas are HTML based tests (not sure when I'll look at these ones), list-of-lists, sealed contexts, stricter validation. The rest are various edge cases across all the operations. I'll turn it into issues and will deal with them when time permits.
There were several surprises. For instance, three toRdf tests which were passing before, started failing  after the test file update. It's related to the order of quads:
Old output (toRdf-0106-out.nq)
<http://example.com/people/dave> <http://xmlns.com/foaf/0.1/knows> <http://example.com/people/markus> .
<http://example.com/people/dave> <http://xmlns.com/foaf/0.1/name> "Dave Longley" .
<http://example.com/people/markus> <http://xmlns.com/foaf/0.1/name> "Markus Lanthaler" .
<https://json-ld.org/test-suite/tests/relative-node> <http://example.com/vocab/noTerm> <http://example.com/people/markus> .
<https://json-ld.org/test-suite/tests/relative-node> <http://xmlns.com/foaf/0.1/name> "Compact keys using @vocab" .

New output (toRdf-0106-out.nq)
<http://example.com/people/markus> <http://xmlns.com/foaf/0.1/name> "Markus Lanthaler" .
<http://example.com/people/dave> <http://xmlns.com/foaf/0.1/name> "Dave Longley" .
<http://example.com/people/dave> <http://xmlns.com/foaf/0.1/knows> <http://example.com/people/markus> .
<https://w3c.github.io/json-ld-api/tests/toRdf/relative-node> <http://xmlns.com/foaf/0.1/name> "Compact keys using @vocab" .
<https://w3c.github.io/json-ld-api/tests/toRdf/relative-node> <http://example.com/vocab/noTerm> <http://example.com/people/markus> .

The only difference is the order of quads. My implementation (in line with Python and Java versions) sorts the quads as the last step. The spec doesn't mention ordering, and the test suite docs explicitly recommend comparing the outputs of ToRDF operation semantically, so no reliance on order. Sorting the quads was always a major performance hit and a limiting factor for streaming. I would love to get rid of it. What are you thoughts? Is it safe to stop sorting ToRDF output?

The spec has relaxed the requirements on blank node labeling to conform with RDF norms. You can no longer depend on the order of quads.  The test README says to use RDF isomorphism, but you could also use normalization to test the results.
Note, there is a broad change in test strategy to relax strict order and blank node naming.

@gkellogg thanks, I'll update the testing methodology and it will fix 3-4 older tests.

@fils @gkellogg @BigBlueHat,
I've created a new PR that implements a good chunk of the current JSON-LD 1.1 specification, see https://github.com/piprate/json-gold/pull/24.
Test suite conformance is at around 89%, ex. Framing. See the latest conformance report here. Please note that I'm not using RDF isomorphism yet for test checks, and there are around 10 tests for the ToRDF algorithm that pass but are marked as untested.
I'm planning to publish a new version of the library soon and document the outstanding issues with JSON-LD 1.1 compliance so that somebody can pick it up.

Hey @kazarena! Thanks for implementing the JSON-LD 1.1 API. It looks like things have gone really well!
Could you submit the conformance report as a pull request to the w3c/json-ld-api repo?? @gkellogg can work with you there on getting you added to the final report.
Thanks again!
🎩

@BigBlueHat, I was just about to ask about it, following the discussion in the JSON-LD Working Group mailing list. I'll submit the report asap.
Stan

@BigBlueHat I've pulled the latest official test suite in order to get a better alignment of test results (I used the version from early Jan 2020 previously). There's quite a bit of movement there, and I can see some easy targets to fix. I'll have to review and update them first before generating a new conformance report. It shouldn't take too long.

@BigBlueHat ok, I've updated the test suite and generated the latest conformance report.
@gkellogg, looking at your recent fixes, you expect "earl:test" to look like "https://w3c.github.io/json-ld-api/tests/testdata/expand-manifest#tc032", and not "https://w3c.github.io/json-ld-api/tests/testdata/expand-manifest.jsonld#tc032". Is that correct?
Is there anything else I should update in https://github.com/piprate/json-gold/blob/master/conformance_report.jsonld to reduce the amount of work required to incorporate the report?
Also, the framing implementation isn't updated to 1.1 yet, but is fully compatible with 1.0. What's the best way to report the test results? My report uses the test suite for JSON-LD Framing 1.0.

@gkellogg, looking at your recent fixes, you expect "earl:test" to look like "https://w3c.github.io/json-ld-api/tests/testdata/expand-manifest#tc032", and not "https://w3c.github.io/json-ld-api/tests/testdata/expand-manifest.jsonld#tc032". Is that correct?

Neither of those two (equivalent) URLs point to anything, as there is no "testdata" sub-directory. If they did, they would be to manifest entries. The suggested format is in the preliminary report. Best in Turtle format, but I can always convert the JSON-LD format to Turtle (you can use my distiller if you like).
 [ a earl:Assertion;
    earl:assertedBy <--your-developer-identifier-->;
    earl:subject <--your-software-identifier-->;
    earl:test <--uri-of-test-from-manifest>;
    earl:result [
      a earl:TestResult;
      earl:outcome earl:passed;
      dc:date "2016-12-26T10:18:04-08:00"^^xsd:dateTime];
    earl:mode earl:automatic ] .

 <> foaf:primaryTopic <--your-software-identifier--> ;
    dc:issued "2016-12-26T10:18:04-08:00"^^xsd:dateTime ;
    foaf:maker <--your-developer-identifier--> .

  <--your-software-identifier--> a doap:Project, earl:TestSubject, earl:Software ;
    doap:name          "My Cool JSON-LD Parser" ;
    doap:release [
      doap:name     "--short name wih version number--";
      doap:revision "--Software version number--" ;
      doap:created  "2020-02-19"^^xsd:date;
    ] ;
    doap:developer     <--your-developer-identifier--> ;
    doap:homepage      <--your-software-homepace--> ;
    doap:description   "--your-project-description--"@en ;
    doap:programming-language "--your-implementation-language--" .

Note that the manifest IRIs used for identifying individual tests do not include the ".jsonld" extension, and there is no "testdata"  subdirectory, so https://w3c.github.io/json-ld-api/tests/compact-manifest#t0001 and not https://w3c.github.io/json-ld-api/tests/testdata/compact-manifest.jsonld#t0001.
Also, note that the framing tests come from https://w3c.github.io/json-ld-framing/tests/frame-manifest not https://w3c.github.io/json-ld-api/tests/compact-manifest
You might also include a doap:release property referencing the doap:revision that you're reporting on.
With those changes I can generate a report, and I'll use this as the basis of doing an update, but for future reference please make sure the IRIs are right; if generating Turtle is a burden, it's easy enough to do on my end.
As it is, the summary information looks like the following:

A.1

JSON-goLD

Release
unknown
Programming Language
Go
Home Page

https://github.com/piprate/json-gold

Developer

Stan Nazarenko

https://github.com/kazarena

Test Suite Compliance

Compaction

232/238 (97.5%)

Expansion

356/366 (97.3%)

Flattening

55/55 (100.0%)

Remote document

15/18 (83.3%)

Transform JSON-LD to RDF

420/442 (95.0%)

Transform RDF to JSON-LD

36/51 (70.6%)

Is there anything else I should update in https://github.com/piprate/json-gold/blob/master/conformance_report.jsonld to reduce the amount of work required to incorporate the report?

Thanks for thinking of this, just what I mentioned above.

Also, the framing implementation isn't updated to 1.1 yet, but is fully compatible with 1.0. What's the best way to report the test results? My report uses the test suite for JSON-LD Framing 1.0.

Test with what you have, and it will show some level of compliance. You probably want to filter on specVersion and/or processingMode.

See https://github.com/w3c/json-ld-api/pull/447.

@gkellogg thank you, I will address your feedback and update the conformance report.
Regarding the test suite for framing, I will try to update [the test suite] to 1.1 and see the level of conformance. Regardless of what the results are like, I will incorporate them into the conformance report to be consistent.

@gkellogg please review the updated report here. I refreshed the Framing tests too.

@kazarena Looks good, I'll update our report and push out shortly. Of course, you can always submit and update to your test results.


not it install in the pcl

How to install in the PCL? Need splat 2.0.0, but splat 2.0.0 Only supported netstandard.

It will install just fine in pcl profile 111 or you a version lower (6.4 and under).  Please google your issue as this has absolutely nothing to do with this library


Generated text not respecting pattern

I'm trying to generate some text using a modified version of the main example and am running into an issue where the model is picking a token containing a non-numerical character for the 'chapter' variable despite that not matching the pattern. Here's my code:
prompt = '''
Tweak this proverb to apply to machine learning model instructions instead.

{{proverb}}
- {{book}} {{chapter}}:{{verse}}

UPDATED
Where there is no guidance{{gen 'rewrite' stop='- '}}
- GPT {{gen 'chapter' pattern='[0-9]' max_tokens=1}}:{{gen 'verse' pattern='[0-9]+' stop='\\n'}}
'''[1:-1]

model = guidance.llms.Transformers('stabilityai/stablelm-base-alpha-3b', device=0)
program = guidance(prompt, llm = model)
executed_program = program(
    proverb="Where there is no guidance, a people falls,\nbut in an abundance of counselors there is safety.",
    book="Proverbs",
    chapter=11,
    verse=14,
)

print(executed_program)
print(executed_program["chapter"])

and the generated output:
Tweak this proverb to apply to machine learning model instructions instead.

Where there is no guidance, a people falls,
but in an abundance of counselors there is safety.
- Proverbs 11:14

UPDATED
Where there is no guidance, a people falls, but in an abundance of counselors there is safety.

- GPT 2::2
2:

I should also add that I saw a similar issue earlier today with pattern not working as intended so I made sure I was on the latest version just before running this just now.

Thanks! This turned out to be a case where the max tokens stopping criteria fired before the ":" end criteria. Reversing this order proved to be a pain, but I think I have a patch now. Will push soon. Note also that max_tokens=1 might look like it would prevent the ":" from firing, but the "2" is actually joined to the prior space into " 2" (because of token healing) and hence does not count towards the max_tokens limit.

@slundberg I grabbed the latest version just now and am still getting the same issue when I use "OpenAssistant/oasst-sft-4-pythia-12b-epoch-3.5" as my model instead. Interestingly, I can get the desired behavior by setting max_tokens=2, max_tokens=0, or omitting max_tokens entirely but it's still generating a ":" when max_tokens=1.


How is the "!" preview function of ragflow implemented? I can't find the corresponding code.

Discussed in https://github.com/orgs/infiniflow/discussions/2741

Originally posted by DAAworld October  8, 2024

When answering questions, an “!” will be displayed on the message, and a preview of the source of the quote will appear above it. How is this function implemented?

thinkyou,I thought it was directly searching for matching, and in the end I found that it was not.


Host a notebook example

Notebook Example
What does this add?
This PR adds a notebook example into the main accelerate codebase, rather than just in the transformers documentation.
Also a small bugfix to the base cv example

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


vRA 7.1 Support

vRA 7.1 compatibility

Allow for new catalog requests
Put logic in to pull from vRA to get IP address
Added some jsons for future use

Signed-off-by: JJ Asghar<EMAIL_ADDRESS>

Notes for later:
https://{{vra-url}}/iaas-proxy-provider/api/services/{{providerRef-id}}/resources/types/{{resource-type}}/{{provider-binding-id}}?includeAllProperties=true

c = @client.http_get("/iaas-proxy-provider/api/services/8100ba32-8f87-4516-9eb5-470660f362db/resources/types/Infrastructure.Virtual/71c49252-ae3a-4fa5-aac6-d588c3738971?includeAllProperties=true")

This is to get the ip from the vra instance ^^^^^

[54] pry(#<Chef::Knife::Cloud::VraService>)> JSON.parse(c.body)['resourceData']['entries'][22]
=> {"key"=>"__datacollected_ipaddress", "value"=>{"type"=>"string", "value"=>"<IP_ADDRESS>"}}

out = JSON.parse(c.body)['resourceData']['entries']
out.fetch('ConnectViaVmrc')

@cstewart87 ping.


metagpt should be able to get terminal output and screenshot to review code

you can refer these projects to design it.
refer projects:
open-interpreter: https://github.com/OpenInterpreter/open-interpreter
aider: https://github.com/Aider-AI/aider
screenshot-to-code: https://github.com/abi/screenshot-to-code
Agent-E: https://github.com/EmergenceAI/Agent-E
gptme: https://github.com/ErikBjare/gptme

https://jmanhype.github.io/HotpotQA-Alternate-History-Generator/

You could try the Data Interpreter, which has some of the functionality mentioned, like getting textual terminal output. It will become the backbone of all agents in version 1.0.


ERROR WITH SpatialAnchorConfig

Саn you tell me how to create a SpatialAnchorConfig file??
I have 9 errors due to BuildDemo2019 compilation.

any information is useful!

In the Unity Editor select the assembly
Microsoft.MixedRealiy.SpatialAlignment.ASA.asmdef
In the Inspector under "Assembly Definition References" click the "+" sign and drag in the assembly called
AzureSpatialAnchors.SDK.Core.Runtime.asmdef
This assembly is either located in the packages folder if you imported the Azure Spatial Anchors SDK through the Package Manager. Or it's located in your Assets folder if you imported it as old-fashioned '.unitypackage'.
Then hit "Apply" at the bottom of the Inspector window. Does that fix the problem?
If it doesn't, try to adding three more assembly definition references for the specific ASA SDK platforms right after the Core Runtime assembly:
AzureSpatialAnchors.SDK.iOS.Runtime.asmdef
AzureSpatialAnchors.SDK.Android.Runtime.asmdef
AzureSpatialAnchors.SDK.Windows.Runtime.asmdef
Let me know if it worked :)

Where i can find or download AzureSpatialAnchors.SDK? in spectator view i downloaded only Azure-Spatial-Anchors-Samples.

I think that's the problem

and there is no .asmdef file in Azure-Spatial-Samples

Ошибки исчезли, когда я поставил путь репозитория C:\SpectatorView

Однако при билде происходит ошибка с пакетами

C:\SpectatorView\src\SpectatorView.Unity\Assets\SpectatorView\Scripts\SpatialAlignment\MarkerVisual\QRCodeMarkerVisualDetectorSpatialLocalizer.cs(20,25): error CS0234: The type or namespace name 'Package' does not exist in the namespace 'Microsoft.Windows.ApplicationModel' (are you missing an assembly reference?)

C:\SpectatorView\src\SpectatorView.Unity\Assets\SpectatorView\Scripts\SpatialAlignment\MarkerVisual\QRCodeMarkerVisualDetectorSpatialLocalizer.cs(20,85): error CS0234: The type or namespace name 'ProcessorArchitecture' does not exist in the namespace 'Microsoft.Windows.System' (are you missing an assembly reference?)

Go into all files which trigger the error and search for statements like this:
#if UNITY_WSA && !UNITY_EDITOR
                return (Windows.ApplicationModel.Package.Current.Id.Architecture != Windows.System.ProcessorArchitecture.X86); // HoloLens 1 is not supported.
#elif UNITY_EDITOR

Now prefix the Windows.xxx. statements with the global:: namespace like so:
#if UNITY_WSA && !UNITY_EDITOR
                return (global::Windows.ApplicationModel.Package.Current.Id.Architecture != global::Windows.System.ProcessorArchitecture.X86); // HoloLens 1 is not supported.
#elif UNITY_EDITOR

Thank you so much))) compilation of the build was successful)

Tomorrow I will test on hololins, I hope everything will be fine)

so...

I have some errors with build Appx file:
Microsoft.MixedReality.Toolkit.Build.Editor.d__5:MoveNext() (at Assets/Pcjs/MixedRealityToolkit/Utilities/BuildAndDeploy/UwpAppxBuildTools.cs:144)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder1:SetResult(ProcessResult) Microsoft.MixedReality.Toolkit.<StartProcessAsync>d__0:MoveNext() (at Assets/Pcjs/MixedRealityToolkit/Extensions/ProcessExtensions.cs:38) System.Runtime.CompilerServices.AsyncTaskMethodBuilder1:SetResult(ProcessResult)
Microsoft.MixedReality.Toolkit.d__1:MoveNext() (at Assets/Pcjs/MixedRealityToolkit/Extensions/ProcessExtensions.cs:150)
UnityEngine.UnitySynchronizationContext:ExecuteTasks() (at C:/buildslave/unity/build/Runtime/Export/Scripting/UnitySynchronizationContext.cs:104)

maybe I need to install a different version of MixedReality.Toolkit?

I don't understand, why not just throw off UnityPackaje, in which everything is already configured? What is the point of spending time on something that can be done in 5 minutes


Fix emmet error decoding DataURI without workspace

Source: #8316
If the user wants to decoding the image without open workspace, then just show a warning.

Hi @mrmlnc, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Maybe info is better than warning?

@mrmlnc LGTM, thanks. I agree this should be an info not a warning

Hi @mrmlnc, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@mrmlnc LGTM, I need to update to the noExpansionOccurred refactoring and some message tweaks.


Use a queue

@queue.push([id, task.wait, content])

is a blocking operation and the behaviour is kind of inverted.
What you need is like this:
queue = Queue.new

Async do
  result = query_db
  queue.push(result)
end

while update = queue.pop
  write(update)
end

I'd probably wrap this for the user, e.g.
h1.content do
  query_db
end

and have:
def content(&block)
  Async do
    @queue.push(yield)
  end
end

etc

That makes sense, but the developer experience isn‘t great. It would mean forcing the user to use proprietary APIs to create their asynchronous tasks and it would also mean having to establish a context object in the controller since database queries, etc. will usually be kicked off before beginning rendering.
The API we had so far has been
Controller
def index
  render Views::Dashboard::Index.new(
    posts: Async { Post.all.load }
  )
end

View
class Views::Dashboard::Index < Views::Base
  def initialize(posts:)
    @posts = posts
  end

  def view_template
    Layout do
      Slot(@posts) do |slot|
        slot.placeholder { div { "Loading..." } }
        slot.content do |posts|
          posts.each do |post|
            h1 { post.title }
          end
        end
      end
    end
  end
end

I know Rails controller actions do have context which we could use, but this would mean making Flecks dependent on Rails, which hasn’t been necessary so far.
So far, Flecks has just been a way to hold off rendering certain blocks until the tasks they depend on are ready. Busy waiting works really well for this. 🤔

Wait, why doesn’t this crash? :confusing
Sync do
  users_task = Async { sleep 10; }
  Async { users_task.wait }
  puts "This isn’t blocked"
end

This also works, which is literally what I’m trying to do by wrapping a user’s own task in my task that waits for it and pushes the result of their task into the queue.
Sync do
  queue = Queue.new
  b = Async { sleep 3; "!" }
  a = Async { sleep 2; " World" }
  Async { queue.push(a.wait) }
  Async { queue.push(b.wait) }
  print "Hello"
  print queue.pop
  print queue.pop
end

Okay, I found the issue. The issue is the fibres are being created in the controller and then puma is creating a thread before the views are rendered. There’s an issue with new fibres created in the new thread waiting on the fixers created in a different thread.
Minimal reproduction of the error I’m running into
Sync do
  queue = Queue.new
  b = Async { sleep 3; "!" }
  a = Async { sleep 2; " World" }
  Thread.new do
    Async { queue.push(a.wait) }
    Async { queue.push(b.wait) }
    print "Hello"
    print queue.pop
    print queue.pop
  end
end

If I have time tomorrow, I'll try to take a closer look at the final implementation. Well done.


Installation steps are not clear

Installation steps mentioned here are not working. Following the steps I don't see the theme applied on 'my-site' app and doesn't work.
mkdir my-site
cd my-site
yarn init -y
yarn add gatsby react react-dom @wkocjan/gatsby-theme-intro

Do I need to create a new gatsby project first before this theme can be applied?

I had some trouble with this too. What you need to do after the following steps is to create the gatsby-config.js file and copy/paste the sample config from the README. Afterwards run gatsby develop and I was able to get the test setup to show.

What would these steps look like when using NPM? Particularly the last line is not very clear to me.

Agree @gouravsood . I do think the steps need to be updated for beginners. Such as installing gatsby, checking gatsby version, and then how to create the gatsby-config-.js file.


memif2vxlan2memif: errors in nsmgr, no response for nsc

Hi,
I'm trying to deploy the memif2vxlan2memif example but getting strange errors in the local nsmgr of the nsc. On one machine the connection is fine, on the other the NSC is not getting a response, but the error is there in both try.
I post the logs from the NSC and the NSMGR in both cases (bad, working). Could you please take a look at them?
bad-memif2vxlan2memif-nsc.txt
bad-memif2vxlan2memif-nsmgr.txt
working-memif2vxlan2memif-nsc.txt
working-memif2vxlan2memif-nsmgr.txt
The difference between the machines is the k8s version:
Working machine:
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:18:45Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.4", GitCommit:"ec2760d6d916781de466541a6babb4309766c995", GitTreeState:"clean", BuildDate:"2021-02-27T17:18:03Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

NOT working machine:
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5", GitCommit:"6b1d87acf3c8253c123756b9e61dac642678305f", GitTreeState:"clean", BuildDate:"2021-03-18T01:10:43Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-28T05:33:22Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Thanks!

Hello @richardstone,
Could you also share versions of your images?

I'm using latest from the repo.

@richardstone NSM works with k8s v1.17.11 or higher.

So closing this.
@richardstone Be free to reopen the issue if I missed someting!


first release of new DP0.2 NBs

@DukeofSuffolk should this PR just be closed?

Rebranched instead of PR.


Can not do cache or prefetch on asyncData?

This question is available on Nuxt.js community (#c105)

Closed thanks to the work of @joostdecock currently on the development branch.


Save and restore winminheight in addition to winheight

Save and restore winminheight in addition to winheight when opening and closing the floating window

Thank you!


update for julia 0.5

There should be no pressure to merge this, as it breaks 0.4 support.  However it may save someone the trouble of making the changes themselves.

Replaced by https://github.com/JuliaLang/Formatting.jl/pull/20 without breaking 0.3 and 0.4 (according to local testing at least.)


Performance Improvements (1)

Description

increase sharding to avoid lock contention
fix availablity info typo
add size hints to avoid multiple allocations
improve AutoMap/Set thresholds
uses non-zero usize to leverage Option<> optimization

Testing Instructions

Closes WEB-1679

Does anything actually use size_hint?

I guess collect will use it for the initial capacity. Without it it starts with an empty buffer and grows it on every element by factor 2. So a correct size_hint will only cause one allocation instead of log N ones.


Emulate all color options exposed by Plotly Express

This is a meta-issue to track and discuss the implementation of all color options exposed by Plotly Express.
This discussion started in #215 but I decided to open a new issue to discuss and track the more general goal of implementing of all color options exposed by Plotly Express, and make sure ridgeplot follows the same conventions laid out by the Plotly Express interface.
Here are some relevant references:

https://plotly.com/python/colorscales/
https://plotly.com/python/discrete-color/
https://plotly.com/python/builtin-colorscales/
https://plotly.com/python/reference/

Notes
Plotly uses color_continuous_scale in Plotly Express functions and colorscale for its object API (e.g. marker.colorscale in go.Scatter)
From the Plotly docs:

legends are visible representations of the mapping between colors and data values. Legend markers also change shape when used with various kinds of traces, such as symbols or lines for scatter-like traces. Legends are configurable under the layout.legend attribute. Legends are the discrete equivalent of continuous color bars

Currently our built-in support for legends is also quite basic. Maybe this is something we could expand on in the future?
Also from the docs:

Most Plotly Express functions accept a color argument which automatically assigns data values to discrete colors if the data is non-numeric. If the data is numeric, the color will automatically be considered continuous.

Is there something we can do to emulate this color behaviour? There seems to be some conceptual overlap between Plotly's color and our colormode...
Tasks:
General

[ ] #279
[x] #236
[x] Stop using the term "midpoint" in our docs. The technical term would be "interpolant"
[x] Take a look at _plotly_utils.basevalidators.ColorscaleValidator to see if we can use it to replace some of our own custom logic.

Continuous color scales

[x] Allow continuous color scale values to be integers too (for 0 and 1). This should be a simple fix to the type annotations.
[x] https://github.com/tpvasconcelos/ridgeplot/pull/229
[x] #230
[x] Plotly Express allows passing a continuous color scale by name just like ridgeplot already does. However, Plotly treats the input as case-insensitive strings, while I don't think we do... (e.g., they allow both 'Inferno' and 'inferno'). (REF1) (REF2)
[x] ~Rename colorscale to color_continuous_scale. Maybe we could deprivate colorscale and support both for a long while?~
[x] What is the difference between ridgeplot.list_all_colorscale_names() and px.colors.named_colorscales() (and ColorscaleValidator().named_colorscales)? Why did we use a different name? Document this?
[ ] #276
[ ] #277
[x] Do we need to do anything special to support cyclical color scales? Maybe they are already supported? Are they included in our ridgeplot.list_all_colorscale_names()? Etc...
[x] Same as above but for diverging color scales... See next point too 👇
[ ] See: https://github.com/tpvasconcelos/ridgeplot/discussions/278

Discrete color scales

[ ] #275
[ ] #274

All tasks have either been completed or turned into issues/discussions... 🚀


Add collision policy

When ranked models are set in the same first or last position, the 24th
element will have the RankedModel::MIN_RANK_VALUE or RankedModel::MAX_RANK_VALUE.
Apply rearrange will force to shift for the all the next elements in the first/last position, when the list is really large performs an sql like:
UPDATE `table` SET position_column = position_column + 1 where
`table`.`position_column` >= -8388606

and its lock rows that can cause performance issues.
Setting the collision_policy: :rebalance for ranked models that usually inserts in the same first/last position will reduce the performance issues in very large ranked lists.

+1 here!
Is the gem still maintained?

Hola :-) this looks like a great addition, happy to merge and release. Current status is wrestling with travis: https://github.com/mixonic/ranked-model/pull/79

Great to know :+1:

great @mixonic ! Ping me if you need something to move this PR to move forward

@csaura, did you still want to progress this? If so, can you rebase? :)

Hi everyone. This has been fixed in master. The list automatically rebalances as soon as it can't insert an item between two ranks.


Wake device from sleep

Hi, the device enters sleep mode after period amount of inactivity .. is there a way to wake up programmatically ?
Thanks!

Are there any updates to this issue?


output_javascript no longer emits .d.ts files

Starting with v2.9.4 it appears that output_javascript no longer emits typescript definitions. Conversely, output_typescript won't emit any JS files and unfortunately won't play nicely with bundlers (when consumed through Buf via node_modules) either.
Here's the difference, v2.9.4; please note how the parser_pb.d.ts is absent:
internal/gen/proto/ts/runme/parser
└── v1
    ├── parser_pb.client.d.ts
    ├── parser_pb.client.js
    └── parser_pb.js

2 directories, 3 files

And here's v2.9.3:
internal/gen/proto/ts/runme/parser
└── v1
    ├── parser_pb.client.d.ts
    ├── parser_pb.client.js
    ├── parser_pb.d.ts
    └── parser_pb.js

2 directories, 4 files

Sebastian, are you sure this is related to https://github.com/timostamm/protobuf-ts/releases/tag/v2.9.4 ? The changes were minimal.
The version of TypeScript used by plugin-framework was not changed either (it would be the most likely cuprit).

@timostamm looking at the diff I'm a bit puzzled myself but A/B testing the two versions side-by-side with nothing else changing, I can reliably reproduce the results from above.
I can try to do more digging. Would you have any pointers where to look @timostamm? The only other place I can think of is https://github.com/bufbuild/protobuf-es but I'm somewhat unfamiliar with both projects.

Update: I just ran protobuf-ts locally instead of as Buf plugin and the ts compiler in v2.9.4 appears to produce the desired result.
@timostamm any chance you could point me at where I can file an issue for Buf? Thank you! And thanks for maintaining this project!
internal/gen/proto/direct/runme/parser
└── v1
    ├── parser_pb.client.d.ts
    ├── parser_pb.client.js
    ├── parser_pb.d.ts
    └── parser_pb.js

2 directories, 4 files

That's right, both projects are completely independent of each other right now. The plan is to gradually change that to keep maintenance manageable, with the first step switching to @bufbuild/protoplugin as the plugin framework. But that has not happened yet.
Thanks for the investigation! I think this is due to a recent optimization for the remote plugins. They use exactly the same code, but the Docker image build recently changed.
Can you file an issue on https://github.com/bufbuild/plugins and reference https://github.com/bufbuild/plugins/tree/main/plugins/community/timostamm-protobuf-ts?
It will be extremely helpful to include a proto file that demonstrates the issue. The problem most likely does not show for every proto input, and may only show under rare circumstances. So you'll save the folks a lot of trial an error if you include an example.

Filed https://github.com/bufbuild/plugins/issues/1162 in this issues place.


Updates to use lowest/locked/latest strategy for continuous integration

Adds composer.lock to the repository
Updates .travis.yml to run, for each supported PHP version:

against the lowest supported versions (composer update --prefer-lowest)
against the versions in the lockfile (composer install)
against the latest versions (composer update)

In order for the latest target to work, PHPUnit must be a minimum 4.5 version.

Ping @stefanotorresi - you don't need to do this one. :)
(Did this in an attempt to verify a reported issue.)


RuntimeError: invalid low watermark ratio 1.4

Hi,
I'm on M1 Mac Studio with 32GB RAM
While starting training, the programme exits at the following steps:
...
loading u-net:
loading vae:
loading text encoder:
import network module: networks.lora
...
RuntimeError: invalid low watermark ratio 1.4
...
Any idea what this error message is and how I can fix it?

Solved: removed PYTORCH_MPS_HIGH_WATERMARK_RATIO=0.7 from environment variables.

Could you tell us where PYTORCH_MPS_HIGH_WATERMARK_RATIO is located?


Add unit tests for adoption_reconciler.go

Issue #, if available: https://github.com/aws-controllers-k8s/community/issues/939
Description of changes:

Add an interface to test Sync method of adoption_reconciler similar to resource_reconciler
Write unit tests for Sync method of AdoptionReconciler
Add a new factory method to allow dependency injection of k8sClient and Reader.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/retest

/test unit-test

/test unit-test

Great!
/approve
/lgtm


Refactoring thoughts

This issue is for talking about a refactor across the IDAES, WaterTAP and Prommis organization repositories for the purposes of re-using major parts of the WaterTAP UI in other projects.
The main challenge being addressed is how to have separate style.branding, lists of flowsheets, and output pages for WaterTAP, Prommis, and future related projects -- while sharing the main UI elements and methods for "wrapping and exporting" flowsheet inputs and outputs.

Diagram of current thoughts


Added gzipTileset script to tools

[x] Write tests
[x] Promisify the module

Also:

[ ] Update README.md with instructions.

This is updated.

Ok this is actually ready now.

@lilleyse is this ready now?

Not yet, I still need to build out the command line tool/json input.

Ok this is updated now. Let me know what you think about the pipeline JSON format.

gunzip

ungzip?

node ./bin/3d-tiles-tools.js gzip -i ./specs/data/TilesetOfTilesets/ -o ./output/TilesetOfTilesets-gzipped/

Can -i be implicit or explicit?
Can -o be optional?

Basically can I run this?
node ./bin/3d-tiles-tools.js gzip ./specs/data/TilesetOfTilesets/

Can you setup travis to run jsHint and the unit tests and coveralls for test coverage?  See gltf-pipeline for a simple example, but probably only 90% right with best practices.  Let me know if you need me to login to enable things.

Add instructions for running the tests and other npm scripts to the README.md.  You can somewhat copy from our other repos.
Basically, I want to get this repo fully setup for development while the code itself is so small and simple so we can easily onramp CIS 399 students in a few weeks.

The README.md is current written for advanced users.  Change the order of the presentation so the individual tools - and their options - are introduced first (e.g., so if I come to the repo asking "how do I gzip this tileset?" I can quickly find the easy way to do it), and then the pipeline is introduced for advanced users.
Also, in the next PR when the pipeline gets a second stage, please add a pipeline diagram so it is super clear how things work.

This is minor, but I wonder if there is any way to add a package.json to the root directory so that if someone runs npm install on the root directory like I did, we can display a message that says to run it on one of the sub-directories.  In general, you might want to look a bit at how repos with multiple node modules are designed.  I know it is common, but I don't know the best practices.

Add instructions for running the tests and other npm scripts to the README.md. You can somewhat copy from our other repos.

For repoing coverage, I think you can exclude the bin directory.  See if we did so in gltf-pipeline.

There's a JSHint warning:
bin\3d-tiles-tools.js
  line 90  col 48  ['tilesOnly'] is better written in dot notation.

  ‼  1 warning

Change the order of the presentation so the individual tools - and their options - are introduced first

Likewise, the pipeline JSON section should show all of each stages options perhaps using formatting similar to the glTF spec.  The glTF spec is actually generated from the JSON schema, but at this point, this does not need one.

node ./bin/3d-tiles-tools.js pipeline -i ./specs/data/pipeline.json

Can we make this as simple as
node ./bin/3d-tiles-tools.js ./specs/data/pipeline.json

If this were ran on a server, are there any security concerns we need to address now, e.g., reading random directories, etc.

Just those comments, this project is off to a nice start!

Can you setup travis to run jsHint and the unit tests and coveralls for test coverage? See gltf-pipeline for a simple example, but probably only 90% right with best practices. Let me know if you need me to login to enable things.

You'll need to do this, I don't have admin access.

This is minor, but I wonder if there is any way to add a package.json to the root directory so that if someone runs npm install on the root directory like I did, we can display a message that says to run it on one of the sub-directories. In general, you might want to look a bit at how repos with multiple node modules are designed. I know it is common, but I don't know the best practices.

I'm not sure if it's possible to override npm install.

If this were ran on a server, are there any security concerns we need to address now, e.g., reading random directories, etc.

Yeah we would need to handle the input and output directories given in pipeline.json. I'll look into this some more.

Output directory optional

Just replying to a lot of related comments here, the output directory is always optional.

Made some changes, still have a few more things to round out.

If this were ran on a server, are there any security concerns we need to address now, e.g., reading random directories, etc.

I believe it should be safe as long as the server that wraps this project writes the input files and output files to temp directories before processing, as well as changes the relative paths in the pipeline JSON to absolute paths (like in 3d-tiles-tools.js). I'm not sure if there's much we can do here.

Can you setup travis to run jsHint and the unit tests and coveralls for test coverage? See gltf-pipeline for a simple example, but probably only 90% right with best practices. Let me know if you need me to login to enable things.
You'll need to do this, I don't have admin access.

I'll submit an issue; it will be a bit before I have time for this.
Anything else left for this PR?

Anything else left for this PR?

This should be ready now. -f, --force is now added to overwrite existing folders.

The only unresolved comment is https://github.com/AnalyticalGraphicsInc/3d-tiles-tools/pull/3#discussion_r75106486.

The only unresolved comment is #3 (comment).

Just to clarify, I don't think you necessarily needy to make any of those changes.  I was just trying to illustrate how writing server-side tools is very different than writing cli tools.  Of course if our goal is to provide a library of tools that will be used either on the client or the server, then we need to lay out some architecture ground rules up front.

The only unresolved comment is #3 (comment).
Just to clarify, I don't think you necessarily needy to make any of those changes. I was just trying to illustrate how writing server-side tools is very different than writing cli tools. Of course if our goal is to provide a library of tools that will be used either on the client or the server, then we need to lay out some architecture ground rules up front.

If this is easy enough to address now, I would like to do it soon.
@mramato please keep a backlog of updates for the Node Guide.

I addressed https://github.com/AnalyticalGraphicsInc/3d-tiles-tools/pull/3#r77263777.
Now the tiles are gzipped during the directory walk rather than all at once. To check that all the files are processed, I keep track of the current count and compare that with the total number of files in the directory.
I also added writing and logging callbacks. However I'm not completely sure what to do with the write callbacks when there are multiple stages. Currently intermediary stages ping-pong between two temp directories. Should the write callback have control over those too? I have a TODO in the code for this.
@mramato I would appreciate your thoughts on the current approaches.

@mramato if you have any more feedback, please submit an issue.


Fade effect disables slidesPerView and slidesPerColumn

This is a (multiple allowed):

[x] bug
Swiper Version: 3.3.1
Platform/Target and Browser Versions: chrome osx

What you did
set slidesPerView: 3, slidesPerColumn: 2, effect: 'fade'
Expected Behavior
group of 6 slides should fade out and display next group
Actual Behavior
grouping is disabled and only one slide is showing at a time, with fade transition

I'm having the same issue. Hope it will be fixed soon!

Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity.
If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


Change Twig global "container" to "crmp_crm.container"

As crmp_crm registeres the global it should be moved to its namespace.

Remember the class RegisterGlobals.

Wait for UnitTests here.


Refactor data gathering into Role model

Coverage increased (+2.4%) to 65.524% when pulling da3ee4457f79c23ef169fa8ee7bc561fbc5378a5 on data-gathering-refactor into 2efd944c8a380a673e4baa048a9bb7ae103cb9a6 on master.


son-profile: Made son-profile package gen. compatible with latest packaging/descriptor version

test this please


Bug Fix: Handling pandas ExtensionDtypes

Pandas ExtensionDtypes are not handled correctly in SQL Lab.

If a SQL column is of type TIMESTAMP and supports timezones, pandas returns an object of type DatetimeTZDtype https://github.com/pandas-dev/pandas/blob/v0.20.2/pandas/io/sql.py#L911
DatetimeTZDtype is a np.dtype duck-typed class but not a real numpy dtype.

Will this one be merged or should we do a custom patch? It's causing some issues for us.

Coverage increased (+0.004%) to 69.121% when pulling 14ff3dd030937b32538329b9129330828656caed on tc-dc:ExtensionDtypes into 147c12dddf0da742f1c33c6fee3b2a4b9dbd12c8 on apache:master.

Coverage increased (+0.004%) to 69.121% when pulling 14ff3dd030937b32538329b9129330828656caed on tc-dc:ExtensionDtypes into 147c12dddf0da742f1c33c6fee3b2a4b9dbd12c8 on apache:master.

Coverage increased (+0.004%) to 69.121% when pulling 14ff3dd030937b32538329b9129330828656caed on tc-dc:ExtensionDtypes into 147c12dddf0da742f1c33c6fee3b2a4b9dbd12c8 on apache:master.


Fix unwrap tuple for exclude_opts

Thanks! Not sure why this went unnoticed as this was supposed to be a straight port from v1's contrib.

Thank you for creating such awesome projects! I have been a Fabric user for many many years. Just switch all my projects to Fabric/Invoke.

Hm, that'll teach me to try using github's fancy schmancy conflict resolution. Managed to delete a line by mistake.
Gonna just do my usual and cherry pick your original commit and manually close.

Commit's been cherry-picked (to the 1.0 branch so far). Found a second yak herd hiding over the next ridge...hopefully mostly done with it now. Travis seems to be having a bad evening too. We'll see what tomorrow brings.
I'd say this is the most incidental work I've done in order to merge a one-character change, but I suspect it's only 2nd or 3rd place 😂

Guess Github straight up ignores closes #XXX for PRs? 1.0 is finally green on Travis and I added a changelog entry so we're good - thanks again!


[ML] fix(next-pylint): Resolve consider-using-with for _Local_job_invoker

Description
This pull request is part of a effort to ready the Azure ML Python SDK for an impending bump to the versions of pylint and azure-pylint-guidelines-checker that is used in our CI.
This pull request specifically resolves R1732 (consider-using-with) for sdk/ml/azure-ai-ml/azure/ai/ml/operations/_local_job_invoker.py, which was skipped in the previous PR for R1732
Validated with:
pylint==2.15.8
azure-pylint-guidelines-checker=0.0.8
pylint --rcfile=../../../eng/pylintc --disable=all --enable=R1732 azure/
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

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


Insufficient requirements to run notebooks

The requirements.txt file does not specify all necessary packages that are required to run the package.
P.ex. projection_util requires scipy and tensorflow, which are not defined in the requirements.txt.
Installing scipy through conda yields version 1.10.1 and indicates a clash between the specified numpy version(1.19.3) and numpy versions for scipy, which are 1.19.5 and 1.27.0

kind of fixed in this commit
still requires tf-gpu setup according to this tutorial feel free to pull.


Memory leak in Syntax Highlight Service

There has been 2-3 reports on Discord with people having memory leaks that seem to be coming from the syntax highlight process specifically.
To my knowledge, this has been reported on Linux only so far, and can happen both when the editor is running, and also on close (this one may have changed since #1488, the last report of this was before then).
The process basically uses all available memory on the machine:
I'll link this issue in Discord and hopefully we can get some logs from someone, as I've been unable to repro on my machine (source build, tar.gz, appimage).

So I just compiled 8ba63de2 to ensure my repro still works. Running Arch Linux on 5.6.3-arch1-1.
It's quite simple and 100% reproducible for me. Sending a SIGTERM to Oni2 in order to close it causes the highlight service to go beserk until the oom killer finally gets rid of it. 2-3 minutes after closing Oni2 that way, it looks something like this:

This issue doesn't occur when using :q to quit.

With the changes that were made (#1619, #1621) above and the fact there has been no other reporting of this recently, I'll close this out.
If someone is still experiencing this, we can re-open.


Added SECURITY.md File #660

I had added the SECURITY.md file

closes #660

Your Welcome @NathanTarbert


Profile_card - Pyoush Madan

Hey @pyoushmadan10!
You have added your repository link instead of your hosted website link. Please add code files to the "Code" folder only and add your hosted website link to the README.md file inside the "Profile Card Collection folder.

Hey @pyoushmadan10! You have added your repository link instead of your hosted website link. Please add code files to the "Code" folder only and add your hosted website link to the README.md file inside the "Profile Card Collection folder.

I have created new pull request and resolved all the raised queries please review it
Thanks


APEX 22.2 - CLOB Session state

Hi,
thanks fpr the plugin - is this or will this be compatible with the new 22.2 CLOB Session state ?
regards

never mind, just found the "Session State Supports CLOB" checkbox in the plugins standard attributes :D

If only that was all ;)
In the PL/SQL Code, you'd also have to change:
apex_plugin_util.print_display_only
    ( p_item             => p_item
-   , p_display_value    => p_param.value
+   , p_display_value    => p_param.session_state_value
    , p_show_line_breaks => true
    , p_escape           => false
    , p_show_icon        => false
);

and
-apex_plugin_util.print_escaped_value(p_param.value);
+apex_plugin_util.print_escaped_value(p_param);

Goes without saying, updating the plug-in on your own is unsupported. Hope the FOS team will update soon.


Discussion: validator table relationships

Just opening up a discussion:
Currently there are no relationships between validator_status and validator_config.
This will require me to query for things twice (which is fine if performance will be an issue) in the future but i'm not 100% about the performance.
It's also a bit weird that we don't have a validator table.
Is there a reasoning for this design?

@ryuash
It is the naming issue. since solana calls validator account as vote account. Actually they can be the same, I think we should call it validator table instead of vote_account


feat: implement use the '-' mark to ignore writing values for field

What's changed and what's your intention?
Similar to the following struct, The CPU field is marked with -,  will write the zero value of the type:
type Monitor struct {
	ID          int64     `greptime:"tag;column:id;type:int64"`
	Host        string    `greptime:"tag;column:host;type:string"`
	Memory      uint64    `greptime:"field;column:memory;type:uint64"`
	Cpu         float64   `greptime:"-"`
	Temperature int64     `greptime:"field;column:temperature;type:int64"`
	Running     bool      `greptime:"field;column:running;type:boolean"`
	Ts          time.Time `greptime:"timestamp;column:ts;type:timestamp;precision:millisecond"`
}

Result:
+------+-----------+--------+------+-------------+---------+----------------------------+
| id   | host      | memory | cpu  | temperature | running | ts                         |
+------+-----------+--------+------+-------------+---------+----------------------------+
|    0 | <IP_ADDRESS> |      1 |    0 |          -1 |       0 | 2024-12-02 07:31:46.403000 |
|    0 | <IP_ADDRESS> |      1 |    0 |          -1 |       0 | 2024-12-02 07:31:46.587000 |
|    1 | <IP_ADDRESS> |      1 |    0 |          -1 |       1 | 2024-12-02 07:31:46.403000 |
|    1 | <IP_ADDRESS> |      1 |    0 |          -1 |       1 | 2024-12-02 07:31:46.587000 |
|    2 | <IP_ADDRESS> |      2 |    0 |          -2 |       1 | 2024-12-02 07:31:46.403000 |
|    2 | <IP_ADDRESS> |      2 |    0 |          -2 |       1 | 2024-12-02 07:31:46.587000 |
+------+-----------+--------+------+-------------+---------+----------------------------+
6 rows in set (0.03 sec)

Checklist

[x]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)
https://github.com/GreptimeTeam/greptimedb-ingester-go/issues/54

IMO, the meaning of greptime:"-" should be: ignore this field when writing and read with struct.
For this PR, it just writes the zero value, it's not a field ignore.

IMO, the meaning of greptime:"-" should be: ignore this field when writing and read with struct.
For this PR, it just writes the zero value, it's not a field ignore.

Wait for me to modify it soon.

Make some changes, please review again. @zyy17
Usage Examples: README
There is also a unit test TestParseSchemaWithIgnoreFields that has passed.


Conditional Relationship throws UnexpectedValueException('Unexpected resource relationship value.') when encoding

Example in Resource file's relationships method:
return [
    $this->when($this->showAddress, $this->relation('address')),
];

Thrown in file laravel-json-api/encoder-neomerx/src/Schema/Relationships.php Line 103 as of v1.0.0-alpha.3 because the ConditionalList iterator returns it as a ConditionalField instead of JsonApiRelation.

Ah yes, good point! Will get that fixed now.

@Wizofgoz this should be sorted now. To give it a go:
composer config minimum-stability dev
composer require laravel-json-api/laravel:^1.0.0-alpha.4 --no-update
composer up laravel-json-api/*

Looks to be fixed to me! Thank you! 👍


Admin Power Pack Not Loading for Admin User

When navigating to Admin Power Pack (fresh install after removing both original install and dummy connector), all admins get the following error page:

Console errors don't show much, attaching log here.
looker.com-1656086949878.log
This has been an issue for Looker versions 22.8 and 22.10.
Things worked correctly with 22.6.

same here
My console says

looker_admin_power_pack.js:35 TypeError: Cannot read properties of undefined (reading 'includes')
at looker_admin_power_pack.js:35:310337
at Array.filter ()
at looker_admin_power_pack.js:35:310316

how can I fix it?

Apologies for the delay, this has been fixed in the latest release v1.0.3
If you've followed the marketplace install, you can reinstall APP (navigate to Marketplace => Manage, and remove and re-add the tool)
If you're using the url parameter to point to the GitHub Pages hosted version of this extension then no action is required, this should now work as expected


Preview Tables don't update post normalization

Preview table values do not update after normalization. not sure if this is needed, but for the unbelieving user this could raise a flag the normalization is not being applied. Maybe something showing pre and post normalization data.
User can always apply and check plots, but may want raw data post-normalization

This should reflect changes, including after log transformation. Will investigate, thank you.


Add code of conduct

Actually, we've removed all code on caffe2/caffe2 so people go to pytorch/pytorch and don't accidentally install this. We really only have it here as historical info since we can't do a real redirect.

Ugh - I must have been working on an outdated branch. Sorry about that. Thanks for catching that.


Install flake8 dependencies in virtualenv

Otherwise any locally installed plugins also emit errors,
and required plugins are not installed.

I have lots of other plugins installed, which emit lots of errors, often conflicting errors ;-)

Codecov Report

Merging #31 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #31   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           3      3
  Lines          50     50
=====================================
  Hits           50     50

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 18771de...bd6f468. Read the comment docs.

Ha! Good call.
I always create project-specific virtualenvs, so tox always just picks up the project's dev environment. Much better to dep them into the toxenv!

(Oh--and here I was, all worried that you were going to be displeased with how many plugins I had installed... :stuck_out_tongue_closed_eyes:)