[new]: send_teams_message(message, webhook_url)

Check the idea has not already been suggested

[X] I could not find my idea in existing issues

Edit the title above with self-explanatory function name and argument names

[X] The function name and the argument names I entered in the title above seems self explanatory to me.

BigFunction Description as it would appear in the documentation
duplicate send_slack_message.yaml.
Change doc and assertion in code.
Teams incoming webhook doc:
https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=javascript
Examples of (arguments, expected output) as they would appear in the documentation

Deployed in bigfunctions.eu dataset. Can you check that it works correctly @batou9150 ?

@unytics it works 😉

Result:


🐛 [BUG] - Tables in docs formatting is broken.

Description
The first column is mis-formatted in all docs tables
Most likely a CSS issue.
Reproduction steps
e.g. here https://opentofu.org/docs/language/syntax/json
Screenshots
No response
Logs
No response
Browsers
Chrome, Safari
OS
Mac

Couldn't add the screenshot through the form, so here it is:

Could also be a formatting issue in the Markdown. This seems to work for me:
| Col | Col |
|:----|-----|
| ...   | ...    |

Thanks @vtrenton , I have the CSS-related issues on my todo list for the holidays if nobody picks it up until then.

Thanks for the debugging @vtrenton ! Keep it coming if you find anything, this will make writing a fix much easier.


Capabilities - App Group Issue

Hi.
Just referenced this issue https://github.com/yonaskolb/XcodeGen/issues/919 to add entitlements.
entitlements:
      path: App/App.entitlements
      properties:
        com.apple.security.application-groups: group.App.Sample

But for me it doesn't work since this creates .entitlements file with a String value for the key "com.apple.security.application-groups" instead of Array. This leads to a bug: app group is not present in the list and not "checked". And this capability doesn't work

At the same time, If I Use pre-generated Entitlements file and remove corresponding code in yaml, the groups list is just empty
Is there something like
`com.apple.security.application-groups:

group: "group.App.Sample`

?

Hi @yevgenPaykey. Does this work?
entitlements:
      path: App/App.entitlements
      properties:
        com.apple.security.application-groups: [group.App.Sample]

thanks, it did


Optimize feerate query for bad internet

There should not be any conflict, I created the branch from the latest master. What's going on?

Context: Before, when the user's internet was down, it waited 3 to 10 minutes randomly to update the feerates the wallet is using.
This is fine, but if it doesn't get the feerates the first time, then when the wallet needs it, it will not have it.
Modified so the feerate queries must happen every 3 seconds (instead of 3 to 10min) until the feerate is acquired the first time. This happened with Carlton when he was using unreliable internet 4 days ago and we fixed it in a similar way (inside the tb-alpha branch's Alpha folder), so it's tested.

There is a merge conflict as well, can you please check it out?


hide_if doesn't hide the entity after v1.2.5 if the value is a list

Describe the bug
After the upgrade from v1.2.2 to v1.2.5 hide_if doesn't hide the entity if the value is a list.
To Reproduce
Steps to reproduce the behaviour:
Use a list of values to compare against.
  - entity: sensor.d5448f4584034770844ddab4e6873e51_100_1_room_presence
    name: Mihai
    state_color: true
    show_state: true
    show_icon: true
    hide_if:
      conditions:
        - condition: equals
          value:
            - not_home
            - Lobby
            - Living Room
            - Master Bedroom
            - Sonia's Bedroom

Expected behaviour
Hide the entity if the value is matched against one of the values
Used to work fine in v1.2.2 with the previous implementation of hide_if.
  - entity: sensor.d5448f4584034770844ddab4e6873e51_100_1_room_presence
    name: Mihai
    state_color: true
    show_state: true
    show_icon: true
    hide_if:
      value:
        - not_home
        - Lobby
        - Living Room
        - Master Bedroom
        - Sonia's Bedroom

Screenshots
Desktop (please complete the following information):

OS: any
Browser: any
Version any

Smartphone (please complete the following information):

Device: any
OS: any
Browser: any
Version: any

Additional context

Hey @mihsu81. The config for hiding changed: https://github.com/marcokreeft87/room-card/wiki/Configuration#hiding.
So yours would be:
  - entity: sensor.d5448f4584034770844ddab4e6873e51_100_1_room_presence
    name: Mihai
    state_color: true
    show_state: true
    show_icon: true
    hide_if:
     conditions:
      - condition: equal
        value: not_home
      - condition: equal
        value: Lobby
      - condition: equal
        value: Living Room
      - condition: equal
        value: Master Bedroom
      - condition: equal
        value: Sonia's Bedroom

I changed this so all conditional entities would work the same in the card

Thanks a lot @marcokreeft87. I did notice that the config of hide_if changed but I didn't pay attention fully to the extent of the change. 😁


Update MD file on new branch 2017-39-14_05-12-42

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Minimum stability

Installing of this package requires setting minimum stability to "dev". This is not good idea if you package is stable enough. This setting is global. But I don't want any other packages to be installed with dev-stability level. It should be better if you require dev package as following:
    "require": {
        "devristo/phpws": "dev-master@dev",
        "react/http": "^0.4"
    },

This will not require global minimum stability set to "dev".

Hello,
Thank you for reporting this issue.
I set a stability flag as you suggested https://github.com/jclg/php-slack-bot/commit/a18d496bf099b57ab8c2b6fe7e37c5b78be6eebc
Unfortunately, it doesn't seem to work
composer require jclg/php-slack-bot
...
Using version ^0.0.5 for jclg/php-slack-bot
Your requirements could not be resolved to an installable set of packages.
...
jclg/php-slack-bot 0.0.5 requires devristo/phpws dev-master@dev -> no matching package found.

Maybe I am missing something ?

You're right. Something here is not as I expected. This solution helped me in other situations but not here.
I see fast solution in explicit defining stability for dependent dev package in root composer.json. Like this:
    ...
    "require": {
        "jclg/php-slack-bot": "*",
        "devristo/phpws": "@dev"
    },
    ....

Tomorrow I will investigate it deeper. Maybe I will find better solution of this problem.

The fast solution I proposed above is only solution to install your package without changing minimum-stability to dev. I was wrong when I offered you to add "@dev" to package version in require section. This trick works only for root packages, i.e. when you need to add in your app one dev-package with minimum-stability=stable. For 2nd level dependencies this doesn't work.
There's 2 variants of installation:

Explicitly specify "@dev" stability for dev-package in root composer.json (my fast solution above).
Set minimum-stability to "dev". And I recommend to add also "prefer-stable" : true. This will install dev version of packages only if stable version not exists.

You may add both examples to README to give user a choice.

Thank you for your help and your suggestions.
I ended up using a fork with a stable release of the same package https://github.com/semako/phpws
I updated the installation instructions in the README file.


Number of LLMs in Ollama Libary

What is the issue?
How can we calculate the number of LLMs in the Ollama library?
OS
No response
GPU
No response
CPU
No response
Ollama version
No response

Download them all, then run
 ollama list | grep -v "^NAME" | wc -l

jk.
for p in {1..133} ; do wget -qO - https://ollama.com/search?p=$p | sed -ne 's/^\s*\([0-9][0-9]*\)<.*Tags.*/\1/p' ; done | awk '{sum+=$1}END{print sum}'
8530

That's all variations of quantization.  If you just wanted the count of model families, there's 133 pages and 25 models per page, so 3325.  That includes model uploaded by ollama users.

thanks, it really helped, but what is 8530 from grep command?

8530 is the number of tagged models in the ollama library, eg gemma2:2b, gemma2:2b-instruct-fp16, gemma2:2b-instruct-q2_K, etc.  The grep command is just a joke, to make that work you would need to download terabytes of models, which is infeasible for most users.

okay thank you

@Gautamshahi, now that you have your answer, could you please close the issue? If you have questions like this, it's better to use Discord rather than the bug reports on GitHub, which are dedicated to solvable problems. When people see a high number of reported bugs, they might become concerned.

@Gautamshahi please close this issue.


Thanks for the suggestion!

Thanks for the suggestion!
How do you think CLI should warn about this: by printing a message to stderr and proceeding immediately, or by requiring you to confirm a potentially dangerous action?
Originally posted by @mislav in https://github.com/cli/cli/issues/6598#issuecomment-1313577402

It seems like you posted this issue here by accident. I'll close it


Add instructions on deploying MDA in kubernetes

Hi,
Can you please add instructions on creating the deployment yaml file, the command to be used to deploy it into kubernetes cluster and any settings of customization that might be needed?
Thanks,
Avi

Added to README.


Fixing mistakes in README

Related to issue

Closes #59

@Brosten Thanks. Do you have any other comments?

Shouldn't the method be more like?
public UIViewController GetTopViewController()
{
    var window = UIApplication.SharedApplication.KeyWindow.RootViewController;

    if (window is UINavigationController navController)
        return navController.ViewControllers.Last();

    return null;
}

And the iOS part is still confusing.
Why is it optional. If I don't have to initialize it, why do it? An explanation of pros and cons with iOS init would be nice!

I do not know how to explain that. It's quite difficult. I would have to talk about View Controllers in iOS.
I just thought that those who need it will understand it anyway. And others do not need to do anything

But for the ones who don't really understand it (like me). If I understand it correctly, everything will work perfect without the init code.
So, why should anyone else bather doing the init?
Perhap's provide a link to some place explaining the optional init thing...?

Perhap's provide a link to some place explaining the optional init thing...?
The link is in my previous message.

Perhaps this will be useful in native Xamarin.iOS  projects that do not use Xamarin.Forms or if you make custom View Controllers for Xamarin.Forms.


Protesting Removal of useProvider and HookWidget

In hooks_riverpod 1.0.0-dev.4 .. You are removing  useProvider . Most of us moved from provider to riverpod to reduce the boilerplate code. Can you please bring it back ?
It's removal will break more than 10 apps my team and I have put into production already.
You were selling riverpod as provider but different. I see no difference in deprecating some core functionalities. Bring back HookWidget
PLEASE @rrousselGit

It is not like you have to migrate until tomorrow or your apps stop working....

@smiLLe I know but what if there's a bug fix or a new feature on a new version that we need in our apps. Picturing those scenarios we can't upgrade because of the missing HookWidget

Flutter hooks... used by hooks_riverpod... was created to sort of emulate React Hooks which uses the use keyword. Why remove the useProvider hook ?

It is not that huge change
class Example extends HookConsumerWidget {
  @override
  Widget build(BuildContext context, WidgetRef ref) {
    useState(...);
    int count = ref.watch(counterProvider);
    ...
  }
}

What about FutureProvider and StreamProvider
class Example extends HookWidget {
  @override
  Widget build(BuildContext context) {
    // useState(...);
    final future = useProvider(myFutureProvider);
    return future.when(
        data: (data) {
          return Container();
        },
        loading: () => CircularProgressIndicator(),
        error: (e, s) => Text("error"));
  }
}

All hooks works within HookConsumerWidget. Including useFuture

class Example extends HookConsumerWidget  {
  @override
  Widget build(BuildContext context, WidgetRef ref) {
    // useState(...);
    final future = ref.watch(myFutureProvider);
    return future.when(
        data: (data) {
          return Container();
        },
        loading: () => CircularProgressIndicator(),
        error: (e, s) => Text("error"));
  }
}

@rrousselGit ... Is useProvider still there ?

Can't HookWidget and HookConsumerWidget coexist ?

You will use ref.watch in favor of useProvider.
You will use HookConsumerWidget in favor of HookWidget when you want to watch a provider.
So why do you still need useProvider in that case?

Can't HookWidget and HookConsumerWidget coexist ?

It would only add confusion and the migration is pretty easy.
Finally with Riverpod 1.0.0 we are getting e cleaner API surface without multiple ways to do the same thing.

@smiLLe The addition of WidgetRef

@rrousselGit  What is the prefered way of using a provider in a custom hook?

It's a matter of unifying the syntax for listening providers. See #335

What is the prefered way of using a provider in a custom hook?

Passing ref as parameter to the hook.

@rrousselGit ... Is useProvider still there ?

No.
But you can make it yourself
With the current dev release, a useProvider would be:
T useProvider<T>(ProviderBase<T> provider) {
  final context = useContext();
  final container = ProviderScope.containerOf(context);

  final result = useState<T?>(null);

  useEffect(() {
    final sub = container.listen<T>(provider, (value) => result.value = value);
    return sub.close;
  }, [container, provider]);

  return result.value as T;
}

I may or may not add it to hooks_riverpod again. We'll see.

@rrousselGit Why is there no final ref = useProviderRef()? Because of inconsitent API or is it just not possible?

The useRef route seems like it would give a more consistent API and make it so you can watch providers without the hook restrictions. If you were to add a hook back into hooks_riverpod I would vote for that option.

A useRef requires significant work

@wazini-john I just migrated our app to the latest hooks_riverpod and I believe the new version without useProvider is the superior to what was there before. Here are some reasons for it:

ref.watch is much clearer than useProvider. As someone reading the code and for new developers, when they see ref.watch in a provider OR a widget, they can assume the rebuild logic and return value is the same. The additional characters typed WidgetRef ref and ConsumerHookWidget do not justify a 2nd abstraction to read and understand. I have experienced this first hand when educating developers on how to use providers inside other providers vs. how to use providers inside a build method.
Separating business logic from UI logic becomes easier. If I want to clean up my build method, then you can see a number of ref.watch calls in the build method. These can easily get pulled into their own provider.
You can write your own useProvider if you really want to. (I would recommend against doing so unless you see a major benefit.)

And if we are talking about the migration process:

The actual migration process is very mechanical. We have a fairly large app and it took me about 90 minutes to do the whole migration.
We started using riverpod before it was 1.x. This means we have agreed to breaking changes for the advantage of allowing riverpod to converge on the best API possible before it hits 1.x. I and many members of the community are willing to invest some time in migrating our code for the benefit of a better api long term.

useProvider should be brought back in hooks_riverpod and ref.watch should be part of flutter_riverpod by convention

@venkatd We have 10 apps in production currently and working on 3. Migrating all of them would be such a hustle unless there is a hooks migrate command

Separating business logic from UI logic becomes easier. If I want to clean up my build method, then you can see a number of ref.watch calls in the build method. These can easily get pulled into their own provider.

Didn't think of that one!
Sounds like "extract as Provider" would be cool 😊

@venkatd We have 10 apps in production currently and working on 3. Migrating all of them would be such a hustle unless there is a hooks migrate command

The migration will take a second. There is a command line that does everything for you.

Will the functionality be brought back ?

The functionality never left. Only the syntax changed, but you can still do exactly the same thing

ref.watch sounds and looks like it belongs to flutter_riverpod.  The hook version should be useProvider

@wazini-john there is HookConsumerWidget which replaces the need for useProvider. Here's an example below...
BEFORE:
class AuthenticatedScreen extends HookWidget {
  AuthenticatedScreen({required this.child});

  final Widget child;

  @override
  Widget build(BuildContext context) {
    final authState = useProvider(authStateProvider);

    if (authState is AuthStateSignedIn) {
      return _AuthenticatedAppDependencies(child: child);
    }

    return authState is AuthStateUnknown
        ? LoadingOverlay(showSpinner: false)
        : SignInScreen();
  }
}

AFTER:

class AuthenticatedScreen extends HookConsumerWidget {
  AuthenticatedScreen({required this.child});

  final Widget child;

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    final authState = ref.watch(authStateProvider);

    if (authState is AuthStateSignedIn) {
      return _AuthenticatedAppDependencies(child: child);
    }

    return authState is AuthStateUnknown
        ? LoadingOverlay(showSpinner: false)
        : SignInScreen();
  }
}

As you can see, it's the same number of lines of code. And it's clearer because it uses the same ref.watch we are used to in provider declarations.

What if the code contains useState?

@wazini-john Using HookConsumerWidget you can use hooks like useState and still use ref.watch for providers

Closing since this discussion should be inside the RFC instead #335


Object.whateverId label is inferred incorrectly as "Whatever" instead of "Whatever id"

Before I send a PR to fix this, just want to make sure if this is side-effect of this code:
humanize: function() { //modified from underscore.string
      if (this.s === null || this.s === undefined)
        return new S('')
      var s = this.underscore().replace(/_id$/,'').replace(/_/g, ' ').trim().capitalize()
      return new S(s)
    }

Is there any reason to explicily remove "_id"?

In a lot of cases this is what you want because if you're storing an ID reference to another collection, then you're probably labeling it as User rather than User ID in the interface. But I agree this may not be the best place for that decision to be made, so a PR to remove that is fine.

"Humanize" can cause ambiguous error messages in validation if two keys humanize into the same string. An example is: {externalSource: 'google', externalSourceId: '123googleid456'}. If the schema requires both these keys and you insert a doc with externalSource but not externalSourceId the error message would be: "External source is required".
@lovetostrike were you going to propose a change?

@mhwheeler I added a PR as you can see above, but it failed the CI and I haven't got a chance to get back to it.

@marcodejongh, does your new humanize stuff fix this? Can you add a test for this? Otherwise I will when I have time.

@aldeed It does fix it but only because the package author made a mistake https://github.com/jxson/string-humanize. The package should be stringjs humanize behaviour but in a isolated package, I guess the author forgot to add the removing of id postfixes.
I've added tests for this in #499 the only case that will still cause confusion now is if you have:
externalSourceId: 123
externalSource_id: 456

Which will both translate to External source id but in that case it's the schema design that needs to be fixed not the simple schema code.


Is there a vscode version?

Thank you for this useful package. Do you have the plan to make a vscode version.

Thank you for this useful package. Do you have the plan to make a vscode version.

Very good suggestions. I'll consider them in the near future.

Hi, @GeneralLi95 , The hexo-front-matter for vscode version published.
plugin-name: hexo-fromt-matter
plugin-url: https://marketplace.visualstudio.com/items?itemName=humbinal.hexo-fromt-matter
github-repo:  https://github.com/humbinal/hexo-front-matter-vscode


useNativeDriver animation redraws inside animating Modal

Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: x64 Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz
Memory: 2.55 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.9.4 - ~/.nvm/versions/node/v8.9.4/bin/node
Yarn: 1.5.1 - ~/.yarn/bin/yarn
npm: 6.0.1 - ~/.nvm/versions/node/v8.9.4/bin/npm
Watchman: 3.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
Android SDK:
Build Tools: 23.0.1, 23.0.2, 23.0.3, 24.0.0, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 26.0.3, 27.0.1, 27.0.2, 27.0.3
API Levels: 23, 24, 25, 26, 27
IDEs:
Android Studio: 3.1 AI-173.4819257
Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
npmPackages:
react: 16.5.0 => 16.5.0
react-native: 0.57.2 => 0.57.2
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
Description
Clone the below repository to notice the bug with native driver animations inside an animating Modal. Simply turn the switch to on and notice it reset to off when modal closes. Removing the animationType on the Modal component or disabling native driver fixes the problem.
Reproducible Demo
git clone<EMAIL_ADDRESS>

Yes, this is indeed still a problem on the latest version of the library.

I guess this might be causing this react-native-modal issue

Been an issue for over a year now. Is it going to be fixed? Is there any other solution than not using the native driver?

I've been using react-native for over 3 years. And although I love this framework, the underlying functionality is quite challenging to achieve given it supports multiple platforms. You either have to bite the bullet and write native code for corner cases or wait a long time for these issues to be addressed, simply because they aren't simple to fix.
Having said that, I'm hoping this gets some attention soon :)

This still requires community attention!

Yes, this is still an issue.


[Pick 2.0](inverted index) fix inverted index read data opt not work on MOW

Proposed changes
Issue Number: close #xxx
Pick from #31075
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Add -DiagnosticInfo values

The values for -DiagnosticInfo were published by the Exchange Team here: https://techcommunity.microsoft.com/t5/exchange-team-blog/digging-into-hybrid-migration-move-report-data/ba-p/1675064

Docs Build status updates of commit 3d382b7:
:clock10: Full build: the average full build time is 17 min(s) 32 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 3d382b7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md
:white_check_mark:Succeeded
View (exchserver-ps-2010) View (exchserver-ps-2013) View (exchserver-ps-2016) View (exchserver-ps-2019) View (exchonline-ps) View (o365scc-ps) View (eop-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2b52960:
:clock10: Full build: the average full build time is 17 min(s) 32 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 2b52960:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-MoveRequestStatistics.md
:white_check_mark:Succeeded
View (exchserver-ps-2010) View (exchserver-ps-2013) View (exchserver-ps-2016) View (exchserver-ps-2019) View (exchonline-ps) View (o365scc-ps) View (eop-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


improve performance of join by make it internal

Avoids exponential string append
Before:
BenchmarkJoinShort
BenchmarkJoinShort-4   	   28102	     42257 ns/op
BenchmarkJoinLong
BenchmarkJoinLong-4    	   40666	     28405 ns/op
After:
BenchmarkJoinShort
BenchmarkJoinShort-4   	  163660	      7162 ns/op
BenchmarkJoinLong
BenchmarkJoinLong-4    	  387810	      3023 ns/op

Good question, yes should work, internal functions does not know about generators, will only get values. But i'm not sure how it get compiled to make it work in these cases, now i got curious. So i guess a call to a function that has any argument that results in no outputs will itself result in no output? seems resonable.
Tried your examples with the change:
$ go run cmd/gojq/main.go -nr '["a","b"] | join(",", "\n")'
a,b
a
b
$ go run cmd/gojq/main.go -nr '["a","b"] | join(empty)'

Maybe it's possible to have a more generic internal help function for improving performance of reduce + binop functions?  like keep map over array in jq and then pass result to a internal function with argument for how it should aggregate?

You don't need to worry about stream as argument of internal functions because they are processed before called.
Don't break {x:1,y:2} | join(",").

This growing complexity is the reason I stopped making it internal. I don't like the duplicates with the executor and pathValue to be used by internal functions. So how about def join($x): [.[]] | _join($x); and making _join internal? Or if type != "array" then [.[]] end | _join($x) if we avoid cloning arrays.

Updated to use own string builder, long when from 57242 to 48389

By avoid cloning the array do you mean implement our own version of strings.Join so that we don't have to copy it?

No, use strings.Join. I just mean [.[]] | _join($x) clones the input array.

Ok switching back to strings.Join

👍  appreciate your comments and suggestions


The Twilight Grove quest description dose not fit Objectives (Gilneas)

@SebastianTanoni Any thoughts on this? It's not going to be possible to just rewrite the flavour text, because Goldrinn has no connection to Wyrmrest Temple. Is there a more lore-appropriate objective that will work? What was the issue with the Shrine of Goldrinn objective?

I wanted gilneas objective to stay in the north alliance duel. Because of 8v8. If it happened that your ally is the night elves, you get goldrinn requirement literally turn 2

So I need an objective that is linked to the fight with Legion and scourge in some way


Assertion `it->impl != __null' failed in virtual void Legion::Internal::IndividualTask::trigger_dependence_analysis()

I got the following assertion failure with the most recent master branch when I am running candle_uno (https://github.com/flexflow/FlexFlow/blob/master/examples/candle_uno.cc). The backtrace is as follows.
#0  0x00007fffd7c7e207 in raise () from /lib64/libc.so.6
#1  0x00007fffd7c7f8f8 in abort () from /lib64/libc.so.6
#2  0x00007fffd7c77026 in __assert_fail_base () from /lib64/libc.so.6
#3  0x00007fffd7c770d2 in __assert_fail () from /lib64/libc.so.6
#4  0x000000000233202b in Legion::Internal::IndividualTask::trigger_dependence_analysis (this=0x7ffa00438d60) at /home/users/zhihao/legion/runtime/legion/legion_tasks.cc:4985
#5  0x00000000022820f6 in Legion::Internal::Operation::execute_dependence_analysis (this=0x7ffa00438f10) at /home/users/zhihao/legion/runtime/legion/legion_ops.cc:366
#6  0x00000000022883c8 in Legion::Internal::SpeculativeOp::execute_dependence_analysis (this=0x7ffa00438f10) at /home/users/zhihao/legion/runtime/legion/legion_ops.cc:2288
#7  0x00000000022d9ce0 in Legion::Internal::MemoizableOp<Legion::Internal::SpeculativeOp>::execute_dependence_analysis (this=0x7ffa00438f10) at /home/users/zhihao/legion/runtime/legion/legion_ops.inl:124
#8  0x0000000002386a7f in Legion::Internal::InnerContext::process_dependence_stage (this=0x7ffa082017d0) at /home/users/zhihao/legion/runtime/legion/legion_context.cc:5770
#9  0x000000000238f6d0 in Legion::Internal::InnerContext::handle_dependence_stage (args=0x7ffa08199188) at /home/users/zhihao/legion/runtime/legion/legion_context.cc:7812
#10 0x00000000029be41c in Legion::Internal::Runtime::legion_runtime_task (args=0x7ffa08199188, arglen=12, userdata=0x45a9dd0, userlen=8, p=...) at /home/users/zhihao/legion/runtime/legion/runtime.cc:21669
#11 0x00000000035eaffa in Realm::LocalTaskProcessor::execute_task (this=0x4df69d0, func_id=4, task_args=...) at /home/users/zhihao/legion/runtime/realm/proc_impl.cc:967
#12 0x0000000002b747bd in Realm::Task::execute_on_processor (this=0x7ffa08198ff0, p=...) at /home/users/zhihao/legion/runtime/realm/tasks.cc:200
#13 0x0000000002b7886a in Realm::UserThreadTaskScheduler::execute_task (this=0x4df6ca0, task=0x7ffa08198ff0) at /home/users/zhihao/legion/runtime/realm/tasks.cc:1394
#14 0x0000000002b76c16 in Realm::ThreadedTaskScheduler::scheduler_loop (this=0x4df6ca0) at /home/users/zhihao/legion/runtime/realm/tasks.cc:903
#15 0x0000000002b7d2d6 in Realm::Thread::thread_entry_wrapper<Realm::ThreadedTaskScheduler, &Realm::ThreadedTaskScheduler::scheduler_loop> (obj=0x4df6ca0) at /home/users/zhihao/legion/runtime/realm/threads.inl:97
#16 0x0000000002b54194 in Realm::UserThread::uthread_entry () at /home/users/zhihao/legion/runtime/realm/threads.cc:1032
#17 0x00007fffd7c90010 in ?? () from /lib64/libc.so.6
#18 0x0000000000000000 in ?? ()

This would happen if you passed in an "empty" future into the runtime, e.g. a future that you constructed yourself and didn't have a value associated with it. The runtime should probably handle this better, but did you intend to pass in an empty future?

If you think this is still a runtime bug then please make me a frozen process on sapling to look at.

There should not be any empty future if the app runs correctly. Do you know how to track the life time of this feature? Such as which task created the future

Turn out to be an application bug.

I've update the runtime to prune out uninitialized futures now whenever they are passed in so we don't get the internal assertion that we did here.


package "absa_parser"

thanks for sharing the sourcecode of your page. it's a great job.
May i know if you would like to share the package "absa_parser", which is missing in line 194, 207, and 323 in file 'data_utils.py'?  thanks.

find the package in LAL-Parser/src_joint/absa_parser.py. thanks.


python310Packages.cloudflare: 2.14.2 -> 2.15.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.cloudflare is: Python wrapper for the Cloudflare v4 API
meta.homepage for python310Packages.cloudflare is: https://github.com/cloudflare/python-cloudflare
meta.changelog for python310Packages.cloudflare is: https://github.com/cloudflare/python-cloudflare/blob/2.14.3/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.14.3 with grep in /nix/store/ykh39rzm9sxvjnwkl0ffb204w85lp8xr-python3.10-cloudflare-2.14.3
found 2.14.3 in filename of file in /nix/store/ykh39rzm9sxvjnwkl0ffb204w85lp8xr-python3.10-cloudflare-2.14.3

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python311Packages.certbot-dns-cloudflare
python311Packages.cloudflare

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ykh39rzm9sxvjnwkl0ffb204w85lp8xr-python3.10-cloudflare-2.14.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.cloudflare https://github.com/r-ryantm/nixpkgs/archive/8e5f2d6859d0392721cd48c4632e274a9d34cfbf.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8e5f2d6859d0392721cd48c4632e274a9d34cfbf#python310Packages.cloudflare

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ykh39rzm9sxvjnwkl0ffb204w85lp8xr-python3.10-cloudflare-2.14.3
ls -la /nix/store/ykh39rzm9sxvjnwkl0ffb204w85lp8xr-python3.10-cloudflare-2.14.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python311Packages.certbot-dns-cloudflare
python311Packages.cloudflare

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.cloudflare is: Python wrapper for the Cloudflare v4 API
meta.homepage for python310Packages.cloudflare is: https://github.com/cloudflare/python-cloudflare
meta.changelog for python310Packages.cloudflare is: https://github.com/cloudflare/python-cloudflare/blob/2.15.1/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.15.1 with grep in /nix/store/chfdcm4w13xq79w4na53l079cmbpdxsw-python3.10-cloudflare-2.15.1
found 2.15.1 in filename of file in /nix/store/chfdcm4w13xq79w4na53l079cmbpdxsw-python3.10-cloudflare-2.15.1

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python311Packages.certbot-dns-cloudflare
python311Packages.cloudflare

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/chfdcm4w13xq79w4na53l079cmbpdxsw-python3.10-cloudflare-2.15.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.cloudflare https://github.com/r-ryantm/nixpkgs/archive/27699e3db28463b4d4a2d9c4e90b9b46c4169760.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/27699e3db28463b4d4a2d9c4e90b9b46c4169760#python310Packages.cloudflare

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/chfdcm4w13xq79w4na53l079cmbpdxsw-python3.10-cloudflare-2.15.1
ls -la /nix/store/chfdcm4w13xq79w4na53l079cmbpdxsw-python3.10-cloudflare-2.15.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python311Packages.certbot-dns-cloudflare
python311Packages.cloudflare

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.cloudflare is: Python wrapper for the Cloudflare v4 API
meta.homepage for python310Packages.cloudflare is: https://github.com/cloudflare/python-cloudflare
meta.changelog for python310Packages.cloudflare is: https://github.com/cloudflare/python-cloudflare/blob/2.16.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.16.0 with grep in /nix/store/mf5m7gb2kfwjbbn7lz4hgd8lcmq21sz3-python3.10-cloudflare-2.16.0
found 2.16.0 in filename of file in /nix/store/mf5m7gb2kfwjbbn7lz4hgd8lcmq21sz3-python3.10-cloudflare-2.16.0

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python311Packages.certbot-dns-cloudflare
python311Packages.cloudflare

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mf5m7gb2kfwjbbn7lz4hgd8lcmq21sz3-python3.10-cloudflare-2.16.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.cloudflare https://github.com/r-ryantm/nixpkgs/archive/52a6110faec5d418b02ccd6b4c15a383b7b820d2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/52a6110faec5d418b02ccd6b4c15a383b7b820d2#python310Packages.cloudflare

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mf5m7gb2kfwjbbn7lz4hgd8lcmq21sz3-python3.10-cloudflare-2.16.0
ls -la /nix/store/mf5m7gb2kfwjbbn7lz4hgd8lcmq21sz3-python3.10-cloudflare-2.16.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

certbot-full
cloudflare-dyndns
python310Packages.certbot-dns-cloudflare
python310Packages.cloudflare
python311Packages.certbot-dns-cloudflare
python311Packages.cloudflare

Maintainer pings

Superseded by #284295.


Add "rotate" parameter to setup(), extend rotation in write()

Basic rotation, reflecting the design of the display (modules combined this or that way), should be set during setup(). An extra rotation during write() would make a nice addition, in particular if angles of 90, 180 and 270 degrees would be supported :)
(BTW, what about mirroring?)

That's partially an issue due to lack of proper documentation. While writing you can transform:

rotate left/right
invert, is that your mirroring?


Fix Pagination plugin #1258

Fix #1258

Model shouldn't be reinitialized. It may contain IDs that are needed for relational queries. Model/Collection/RelationCollection shall be cloned instead.
groupBy is needed when queries with joins are used. DB engine started to shout if it was missing for collections.

Two tests added for collection and relational collection result verification.
:exclamation: Contains PR #1271
:exclamation: Makes PR #1261 redundant

Strangely tests fail if not only Pagination Plugin tests are run. Here with only Pagination Plugin tests it works.

Seems that virtuals plugin somehow ruins up bookshelf.Model... Investigating further.

It wasn't a problem with virtuals but the base class of the Model I was cheching it is a instance of.
@rhys-vdw I think this PR is ready to be merged.
I needed to improve CollectionBase.clone as well implement RelationBase.clone. Actually there was an issue currently that Relation object didn't get cloned on collection cloning but got copied. So original and cloned collecion would have a reference to the same Relation object.

@vellotis any chance this gets merged soon?

Sorry to be a pest, but is it possible to have one of the maintainers merge this fix soon?

+1

@vellotis Can you rebase please?

@kirrg001 I could rebase if you are ok to review it. I didn't accept my own PRs (not my practise) while I was more active on bookshelf project.

@vellotis I will review it 👍

Good. I will rebase it on the weekend.
https://mailtrack.io/ Sent with Mailtrack
<EMAIL_ADDRESS>2017-04-21 12:59 GMT+03:00 Katharina Irrgang<EMAIL_ADDRESS>
@vellotis https://github.com/vellotis I will review it 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tgriesser/bookshelf/pull/1272#issuecomment-296149365,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASzavVPH81EkOJypu95vfPYnSztjAmCks5ryH4TgaJpZM4IsozQ
.

Any news on this ? The issue is still here

Sadly, this is the downside of open source. People around the world putting
their own free time to the projects. And some times they value their free
time with real physical people more than the time in open source community
with virtual people.
But, really. I am going to rebase the PR in upcoming weekend.
My apologies!
2017-04-28 17:02 GMT+03:00 Patrick Mettraux<EMAIL_ADDRESS>
Any news on this ? The issue is still here
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tgriesser/bookshelf/pull/1272#issuecomment-298006094,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASzav0otfYKuX30cIsiLe4anpfz4C0fks5r0fFvgaJpZM4IsozQ
.

@vellotis what is this "real" physical world/people that you speak of? 😆

https://github.com/tgriesser/bookshelf/pull/1561

Check #1561 Discussion


Update readme and license information

Codecov Report

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

@@           Coverage Diff           @@
##           master      #46   +/-   ##
=======================================
  Coverage   74.69%   74.69%
=======================================
  Files          19       19
  Lines         972      972
  Branches      146      146
=======================================
  Hits          726      726
  Misses        246      246

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 e20efb9...762530f. Read the comment docs.


evaluator: comprehension that creates constraint violation silently allowed

What version of CUE are you using (cue version)?

$ cue version
cue version v0.0.0-20230511092117-a670427406af

go version go1.20.2
      -buildmode exe
       -compiler gc
     CGO_ENABLED 1
          GOARCH arm64
            GOOS linux
             vcs git
    vcs.revision a670427406af7451da77cf477c0786d6f1b129c8
        vcs.time 2023-05-11T09:21:17Z
    vcs.modified false

Does this issue reproduce with the latest release?
Yes
What did you do?
! exec cue vet -c x.cue
stderr 'x.age: conflicting values int and "age" (mismatched types int and string)'

-- x.cue --
x: {
	name: string
	age:  int
}

x: {
	for k, _ in x {
		(k): k
	}
}

What did you expect to see?
A passing test.
What did you see instead?
> ! exec cue vet -c x.cue
[stderr]
x.age: incomplete value int:
    ./x.cue:3:8
[exit status 1]
> stderr 'x.age: conflicting values int and "age" (mismatched types int and string)'
FAIL: /tmp/testscript1176224950/repro.txtar/script.txtar:2: no match for `x.age: conflicting values int and "age" (mismatched types int and string)` found in stderr

i.e. the mismatch between int and "age" appears to have been lost, and the error has instead proceeded to a complaint about the age field being incomplete (one of the last checks).
Indeed this is somewhat confirmed by the result of cue eval:
$ cue eval x.cue
x: {
    name: "name"
    age:  int
}

Marking this as v0.6.0 because at least v0.4.3 reported an error that this was a cycle. It feels strictly worse that we are reporting this an incomplete error.

Perhaps a better test (more befitting the issue title) might be to run cue vet -c=false, which succeeds inappropriately.


Implement mktemp

I'll try to implement mktemp.
BTW I have some questions:

Is the recommended reference is coreutils/coreutils?
Can I use external library (such as tempfile?

Yes to both. My only caveat for the first question is to make a clean-room implementation (copy behavior, not code), since GNU coreutils is GPL and this implementation isn't.
Good luck! Feel free to ask for help if needed.


Question minimal number of values to initiate animation?

Hello folks, I'm trying to implement the real time bar chart, but I do not have any initial data properly, I'm getting the data through ajax call to json each second, but when I use the .push method to update my chart, nothing happens.
That is my chart:
$('#mem-chart').epoch({     type: 'time.bar',     axes: ['top', 'right', 'bottom', 'left'],     data:[{         label: "Memory",         values: [{time: parseInt(new Date().getTime()/1000), y: 78}}]}] });
And here is where a call push method:
$('#mem-chart').push([{time: parseInt(new Date().getTime()/1000), y: data.freeMemory}]);

The error was beacause I was not using push on the chart variable.


Allow relative path to duckdb

Currently the duckdb file needs to be in the same path as evidence.
Can we make it possible to point at a relative path?

@ReneTC where would you like to keep yours specifically?
(Good workarounds in the meantime include for example, a CI step that copies it from the current location to the root)

Thanks @archiewood - I use evidence with meltano, so the project is running inside a meltano project. My data is outside of the meltano proejct.
It's a good suggestion with a CI copy for now. However the database might grow really big

Just adding to this - in the mdsinabox.com project, I am using duckdb with "external materializations" which are parquet files. When I run npm run dev etc, the path does not resolve correctly and the files cannot be found. The current workaround is building the entire env in meltano, which resolves the pathing issues.

Can you elbaorate matsonj?  how Meltano solves the pathing issues :D? I am asking becease the Meltano utility https://hub.meltano.com/utilities/evidence/ says:
 EVIDENCE_SETTINGS_DUCKDB_FILENAME: Name of the DuckDB database file stored in the same directory as your Evidence project.

Sure! I’m sharing my config from https://github.com/matsonj/nba-monte-carlo
  - name: evidence
    variant: meltanolabs
    pip_url: evidence-ext>=0.5
    config:
      home_dir: $MELTANO_PROJECT_ROOT/evidence
      settings:
        database: duckdb
        duckdb:
          filename: ../data/data_catalog/mdsbox.db

Since it remaps everything to the root and build its own environments, it handles the relative pathing by keeping everything its own instance for evidence (installed via meltano)

@ReneTC oh I’m realizing that the documentation is wrong in meltano util! Good news, I’m one of the maintainers 😆

Thank you very much, I appreciate your help.
It's up to the evidence developers if this ticket should be closed or not.
The meltano tip solved my issue.
On Mon, 23 Oct 2023, 20.30 Jacob Matson, @.***> wrote:

@ReneTC https://github.com/ReneTC oh I’m realizing that the
documentation is wrong in meltano util! Good news, I’m one of the
maintainers 😆
—
Reply to this email directly, view it on GitHub
https://github.com/evidence-dev/evidence/issues/1220#issuecomment-1775778229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJSZI4NJDHOJXQRT44HUOODYA2ZSZAVCNFSM6AAAAAA5MDF6NOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZVG43TQMRSHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

We'll keep this open, I think it's not full solved.
However, I want to add another workaround that can work here that I tested today.
If you edit the credentials file inside .evidence/template/evidence.settings.json, rather than the UI, you can use a relative path.
However, you need to map the path relative to this subfolder (rather than the root of the evidence project), as this subfolder is where the process actually runs.
For example, if you stored your duckdb inside ./data/database.duckdb then you would need to use the path ../../data/database.duckdb
Similarly, this is the path that will be copied when you set the environment variables also.

This can now be configured in the connection.yaml for your DuckDB file.
The filepath is relative to the directory where the connection.yaml file is stored.
For example you can use something like this:
connection.yaml
# This file was automatically generated
name: needful_things
type: duckdb
options:
  filename: ../../../../../../Users/archie/Downloads/needful_things.duckdb


Minor typos in DA1469x MCU syscfg

Fixed minor typos as a way to try out the contribution workflow.

thanks ian!


[vcpkg baseline][graphqlparser] needs python2

Failed on https://dev.azure.com/vcpkg/public/_build/results?buildId=105330&view=logs&j=7b75bd19-17d3-53d4-00fd-23f1a49a8ba4
Test that FIND_PACKAGE(PythonInterp 2 REQUIRED), and based on it's result :

Failed for CI x64-osx and arm64-osx machine
Found python3 for CI x64-linux machine

The port graphqlparser requires python2, so mark x64-osx and x64-linux as failed in ci.baseline.txt (arm64-osx has bee added before #27414).

[x] Changes comply with the maintainer guide.
[ ] ~SHA512s are updated for each updated download.~
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version.~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[ ] ~The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.~
[ ] ~Only one version is added to each modified port's versions file.~

Given that this won't build on any modern systems (depends on out of support Python 2), upstream appears missing, the last release was 7 years ago, and that this is a leaf, I think we should deindex this outright.

@ras0219-msft @AugP @JavierMatosD @vicroms and I agree that it should be deindexed entirely. Thanks!

@BillyONeal Please let me confirm that should this port be set to empty with set(VCPKG_POLICY_EMPTY_PACKAGE enabled)? Or deleted in ports and versions/baseline.json

deleted in ports and versions/baseline.json

This.

All the failures are existing other baseline regressions likely resulting from the build lab being broken before so I'm merging around it.


Change the default storage class of a cluster

What happened:
I provisioned a new storage class to a cluster, removed the storageclass.kubernetes.io/is-default-class from the default-class and added it to my new storage class. After some time, gardener automatically re-adds storageclass.kubernetes.io/is-default-class to default-class.
As a result, there are two storage classes marked as default and provisioning new PVCs without specifying a storage class fail with persistentvolumeclaims "sample-pvc" is forbidden: Internal error occurred: 2 default StorageClasses were found
What you expected to happen:
If a storage class marked as default exists, gardener should not mark the default-classas default.
How to reproduce it (as minimally and precisely as possible):
provision a new storage class, e.g. https://github.com/rancher/local-path-provisioner
kubectl patch storageclass default-class -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"false"}}}'`
kubectl patch storageclass other-storage-class -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'

wait...

I don't think we can implement this easily. The extension controllers will create the storage classes and will pick one that is the default class. After that, these manifests are given to the resource-manager who will apply them every minute or so. The resource-manager itself is not aware of what it applies, i.e., it doesn't know about the context. However, it would need to know to fix "this issue", but that contradicts its design.
The extensions themselves could check whether there is another storage class that is marked as default, and if so, then don't mark their own as default. However, this does not work when we switch to reconciliation only in the maintenance time window (every 24h, basically).
--> I don't think we can easily solve this soon and we probably won't find time to work on it. I'll close the PR and mark it as "won't fix" for now. Also, I guess it's no too hard restriction that the default class cannot be changed.


⚠ Samsung has degraded performance

In 7d8a348, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2554 ms

Resolved: Samsung performance has improved in b7d4c3f.


Region should support MPI_Alltoallv()

In the distributed ptscotch unstructured partition such an operation is coded for regions. gentryx mentioned that there should be a native operation in Region to allow this.

I believe the communication operation should exist in MPILayer, not Region.

Oops, sorry, mistyped. Fixed.


WIP: Ensure related document shows in Console

What does this PR do?
Add the currently related documents to the documents list to ensure it's rendered as an option.
Test Plan
None
Related PRs and Issues

https://github.com/appwrite/appwrite/issues/5541

Have you read the Contributing Guidelines on issues?
Yes

@stnguyen90 what is pending on this PR?

@TGlide, this was a hacky PR to show @ArmanNik what the root cause was. My approach here was super messy, and it would be good to get a cleaner approach in place.


vmTools: Make msize larger to silence warning

Motivation for this change
See https://issues.guix.gnu.org/47225
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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

[x] Fits CONTRIBUTING.md.

good thing i searched before making a pr myself, could you set it to 512000 and then lets merge?

Can rebase, did rebase, it's out of my hands now :)

This broke nixosTests.hibernate and blocks nixos-unstable channel; example on Hydra: https://hydra.nixos.org/build/158899310
Any ideas?  It seems very well reproducible, Hydra retried and I locally bisected it to ecf388e90 with retries.

Feels like a OOM, but I'm currently afk. If nobody else is able to track the issue down until evening, I will be back and take a look

Yeah, a bigger msize consumes more memory, so if it was contraindicated before, that's probably the cause. Increasing memorySize should solve that.

The install step (IS) (sometimes) succeeds with a larger nodes.machine.virtualisation.memorySize, but, contrary to our expectations, the hibernate test duration is significantly increased compared to using the old msize setting.
Here are the results of multiple runs of tests/hibernate.nix:

This PR, memorySize = 1024;

Failure: While running nixos-install, the test hangs with 100% CPU in the python test runner, while the machine idles
IS finishes after 611.15 s
with suspicious output machine # [  189.432660] hrtimer: interrupt took 3697118 ns while running nixos-install.

This PR, memorySize = 2048

IS finishes after 1056.41 s
Note that this is run takes longer while using more memory.

nixpkgs-unstable (which doesn't include this PR):

IS finishes after 302.41 s
IS finishes after 332.51 s

I'd suggest to revert this PR.

https://github.com/NixOS/nixpkgs/pull/146783

I'm not seeing those results at all. On master, when setting memorySize to 1024, I got the following run times:

374.78s
368.70s

With msize changed back to 16384, I get these times instead:

359.16s
360.17s

I'm not seeing any hangs or other issues. However, the results with a lower msize are still slightly better. I'm not sure if any other tests perform better with a high msize, so reverting might still be a good idea.

i found this commit https://github.com/NixOS/nixpkgs/commit/a5bc11f9eb70482daf559019f9b775c285defb63

reverted in https://github.com/NixOS/nixpkgs/pull/147180


[Q] eitinject already changes the SDT table ?

Do I need to change SDT eit flags to 1 manually, when I use -P eitinject ?
EIT_present_following_flag = 1 and EIT_schedule_flag = 1
I didn't find it in the manual.
Thanks

Hi @Litrona
This must be done separately. TSDuck is a low-level toolkit. All tasks which can be performed separately are handled in independent plugins. The plugin eitinject injects EIT's and that's all. To set the EIT indicators in the SDT, use the plugin -P sdt --service-id XXX --eit-pf 1 --eit-schedule 1. Add one such plugin for each service you want to update.

OK, understood then.
Thanks


Update sbt-updates to 0.6.1

Updates com.timushev.sbt:sbt-updates from 0.6.0 to 0.6.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.6.0).
You might want to review and update them manually.
docs/website/package-lock.json

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.timushev.sbt", artifactId = "sbt-updates" } ]

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, old-version-remains, commit-count:1

Codecov Report

Merging #675 (bb1f719) into main (ce9afac) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #675   +/-   ##
=======================================
  Coverage   61.31%   61.31%
=======================================
  Files          59       59
  Lines        1383     1383
  Branches       49       49
=======================================
  Hits          848      848
  Misses        535      535

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 ce9afac...bb1f719. Read the comment docs.


TypeScript definitions

Hello, I am interested in contributing a PR to add typescript definitions.
This should be a small configuration change.
Would the maintainer(s) approve this? Thanks!

@petermikitsh I'd love for you to add TypeScript definitions! Thanks! 🙏

Closed in #8


devise_for :admin_users makes current_user always nil in SwitchUser config

Hello. I think I may have found a bug.
Simplified version of my routes config looks like this:
1:  devise_for :admin_users, {class_name: 'User'}.merge(ActiveAdmin::Devise.config)
2:  ActiveAdmin.routes(self)
3:  devise_for :users

Luckily I can use switch_user in development environment because view_guard & controller_guard conditions look like:
Rails.env.development? || current_user&.email ==<EMAIL_ADDRESS>
Unfortunately It doesn't work in production environment because current_user is always nil.
Steps to reproduce:
comment out the 1st line with devise_for :admin_users and current_user is working again and not nil(for signed in users).
Does anyone have an idea on how to make it work with ActiveAdmin?

same here:
config.controller_guard = ->(__current_user, request, original_user) { #users always nil here }


fix:back-btn

Description
I have added a back button to go back to the main page instead of clicking reload from hamburger icon [i.e menu display]...I have added this button on both customization of color spectrum display and as well as on the page displaying the spectrum with music.
Fixes:  #181

Type of change

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

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[x ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@PallaviGudupallavi isnt there a reload button which is already reloading the entire page the back button should take the user back to main page without starting the preloader and also improve the design it should be in the navbar with the others or below the timer as an icon

@PallaviGudupallavi hi i noticed that the issue is not assigned to you
You cannot work on someone elses issue
You can create another issue and create a pr when it is assigned to you


conditionals

Translate GPflow/GPflow/conditionals.py to gpflowr/R/conditionals.R
When closed, remember to tick the box in the roadmap issue

nullified by #27


Automate updating of homebrew casks

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable not needed

Description
This PR aims to automate the updating of the chatterino homebrew casks.
Currently only support for the stable channel of chatterino is included but will manually create both beta and nightly casks in the 'versions' cask repo.
Not at all familiar with actions but they're sorta like Azure DevOps pipelines - hope that means I didn't make too much of a mess.

Will test this when 2.3.3 is released and if I'm happy with it I'll publish this PR.

2.3.3 has come and gone, were you happy with the results?

2.3.3 has come and gone, were you happy with the results?

I missed two releases with this PR, whoops. I'll give it a test tonight and open it for review.


Systemd Stage 1 includes unnecessary fsPackages

As mentioned in #201396, if you have boot.initrd.systemd.enable = true;, then initrd will contain the bin directories of all system.fsPackages, which is undesirable. For instance, this by default includes dosfstools in initrd, which is obviously not necessary for almost anyone.

which is obviously not necessary for almost anyone.

Is that accurate? I remember my system failing to run fsck.fat on boot a few times because it's trying to check /boot. FAT32 /boot is very common for UEFI systems.


Added more intro material in MS MARCO passage replication guide

Recent students who have done this replication, I'd appreciate your comments: what isn't clear?
cc @ArthurChen189 @printfCalvin @saileshnankani @andrewyguo

Looks clear to me!

Looks clear to me as well. The details are really helpful!

I think newly added details really help when recreating this experiment.


azure-cli: 2.26.0 -> 2.26.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Azure/azure-cli/releases.
meta.description for azure-cli is: "Next generation multi-platform command line experience for Azure"
meta.homepage for azure-cli is: "https://github.com/Azure/azure-cli"
meta.changelog for azure-cli is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/2zn8ghaizh52f5cd9v89klkz0ix6nblk-python3.8-azure-cli-2.26.1/bin/az passed the binary check.

Warning: no invocation of /nix/store/2zn8ghaizh52f5cd9v89klkz0ix6nblk-python3.8-azure-cli-2.26.1/bin/.az-wrapped had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/2zn8ghaizh52f5cd9v89klkz0ix6nblk-python3.8-azure-cli-2.26.1/bin/.az-wrapped_ had a zero exit code or showed the expected version

0 of 3 passed binary check by having a zero exit code.

1 of 3 passed binary check by having the new version present in output.

found 2.26.1 with grep in /nix/store/2zn8ghaizh52f5cd9v89klkz0ix6nblk-python3.8-azure-cli-2.26.1

found 2.26.1 in filename of file in /nix/store/2zn8ghaizh52f5cd9v89klkz0ix6nblk-python3.8-azure-cli-2.26.1

directory tree listing: https://gist.github.com/96888d0f1690eee43439d8cba1859524

du listing: https://gist.github.com/f3df159c489dc483938b9e3fbf311a22

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
azure-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2zn8ghaizh52f5cd9v89klkz0ix6nblk-python3.8-azure-cli-2.26.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A azure-cli https://github.com/r-ryantm/nixpkgs/archive/73e2b2f0e0667c7baec01833021cd38107095325.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2zn8ghaizh52f5cd9v89klkz0ix6nblk-python3.8-azure-cli-2.26.1
ls -la /nix/store/2zn8ghaizh52f5cd9v89klkz0ix6nblk-python3.8-azure-cli-2.26.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

azure-cli

Maintainer pings
cc @jonringer for testing.

I would be highly supprised if this worked...


corrected docs around custom CA support beta v. stable

Proposed changes
Updated description of support for custom CA certificates in FAQ's
Related issue
per this user-reported issue: https://github.com/docker/for-mac/issues/343#issuecomment-253806642.
Please take a look
@samoht @justincormack @mstanleyjones @thaJeztah
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

Okay I think this is good. Merging!


Couldn't import fesapi after installation on Windows for Python

I believe I followed all the instructions except "Please first install the wheel located in fesapi/python/dist". There is no dist folder. Below are the files in the fesapi/python/ folder. Is the installation incomplete?

I tried to add in python path: "sys.path.append("...\fesapi\python")", then "import fesapi", but got the error: cannot import name 'fesapi' from partially initialized module 'fesapi' (most likely due to a circular import) (...\python\fesapi_init.py)

Hi,
Did you build FESAPI with visual studio and install it (by building the VIsual Studio INSTALL project)  ?
Could you paste last lines of the build log please?
This is the responsability of the (Visual studio) build to produce the fesapi/python/dist.

FYI if you understand cmake this  is where the final python generation should be processed.

And here is the CI where python is tested. However, it is done on ubuntu (not on windows).
I jsut highlighted the line of the install

Thank you for the quick reply and you are right. I previously built the entire Fesapi solution, and it turned out that the 3 other projects were built successfully, but the INSTALL project was skipped. I just re-built the INSTALL project and got the error below:

Try to rebuild in release (withdebinfo if you want and even without optimisation if you want) mode please.
It looks you build in debug mode which is much less tested.

If you really want to build a debug version, please try first to set this SWIG_LINKED_TO_RELEASE cmake variable  to false.

I rebuilt with release mode and still got the same error:

The complete line before the error is below. And I can find the file "FesapiCppd.<IP_ADDRESS>.lib" under \fesapiEnv\build\install\lib\ and \fesapiEnv\build\src\Release\

C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\HostX86\x64\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:C:/Users/fuyl/tools/fesapiEnv/build/install/lib /LIBPATH:C:\ProgramData\Miniconda3\libs /LIBPATH:C:\ProgramData\Miniconda3\PCbuild\amd64 /LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\ATLMFC\lib\x64 /LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\lib\x64 /LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\lib\um\x64 /LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.19041.0\ucrt\x64 /LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.19041.0\um\x64 /LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\lib\x64 /LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\atlmfc\lib\x64 /LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\VS\lib\x64 /LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.19041.0\ucrt\x64 /LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\VS\UnitTest\lib /LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.19041.0\um\x64 /LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\lib\um\x64 FesapiCppd.<IP_ADDRESS>.lib /EXPORT:PyInit__fesapi build\temp.win-amd64-3.9\Release\swigGeneratedPythonWrapper.obj /OUT:build\lib.win-amd64-3.9\fesapi_fesapi.cp39-win_amd64.pyd /IMPLIB:build\temp.win-amd64-3.9\Release_fesapi.cp39-win_amd64.lib
LINK : fatal error LNK1181: cannot open input file 'FesapiCppd.<IP_ADDRESS>.lib'

Hi @fuyuli123456
I don't understand how you can have this error message if you have not played with the SWIG_LINKED_TO_RELEASE cmake variable.
The last line of your pasted log reference 'FesapiCppd.<IP_ADDRESS>.lib' which is the debug version (cause of the suffix 'd'). However, in your screenshot above, we can see at the first line that you copy the correct release library....
I tried myself on my own computer and cannot reproduce your error using v<IP_ADDRESS>. However, I have another error about an unresolved external symbol witsml2_1::Channel::setPropertyKind which is a regression starting from v<IP_ADDRESS>. I am just trying to fix it in my dev branch (i.e. for v<IP_ADDRESS>).
Either you can fix it yourself in your local v<IP_ADDRESS> by adding a dllexport prefix as in this commit file Channel.h
Or you can build v<IP_ADDRESS> (Release mode)
Or you can build the branch dev (Release mode)
Or you can use the wheel I just produced for v<IP_ADDRESS> and which I have put in the v<IP_ADDRESS> release assets.

Thank you so much! I tried the wheel file. I couldn't get it work because I was not able to install python 3.10 on my computer. I have python 3.9.5 and 3.11.5 instead. Do you happen to have the wheel files for either of these two versions? If wheel can't work out, I will start over to build v<IP_ADDRESS>.

OK, I just upgraded my python to v3.11.5 and relaunch the VS INSTALL project built.
Here is the result in the assets of v<IP_ADDRESS> : https://github.com/F2I-Consulting/fesapi/releases/download/v<IP_ADDRESS>/fesapi-<IP_ADDRESS>-cp311-cp311-win_amd64.whl

this worked! Thank you so so much!!!


Change cell language fires change event

Version: 1.46.0-insider

Commit: cd41dd1f6065db76c77c6e2f659bb50e6f558dec
Date: 2020-05-29T05:45:24.735Z
Electron: 7.3.0
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.5.0

Steps to Reproduce:
1.Open a notebook
2.Create a markdown cell and change the language to markdown.
A notebook event if fires for change of cell language even though the current language is already the same.
I would not expect the event to get fired if the cell language is the same.
Also as a side effect the cell output change event also gets fired (feels this is a noop change, hence events shouldn't get fired)

Does this issue occur when all extensions are disabled?: Yes/No
@rebornix

I'm trying to use a vscode.notebook.onDidChangeCellLanguage listener, but this seems to never be called now, even if I do change a cell to a different language.
vscode.notebook.onDidChangeNotebookCells does get fired when the language is changed.

@RMacfarlane did you switch only between Markdown and GitHub Issue Notebook, if so it's expected as switching between markdown and code cells is a cellsChange event but not a language change event.

Ah, yes, that is what I did. How do I change to a language outside of those?

@RMacfarlane you can try

Firstly clone  https://github.com/microsoft/vscode-notebook-renderer-starter
Add multiple language support to sample provider https://github.com/microsoft/vscode-notebook-renderer-starter/blob/master/src/extension/sampleProvider.ts#L49 . Change languages to ['json', 'css']
Register a cell language listener in https://github.com/microsoft/vscode-notebook-renderer-starter/blob/master/src/extension/extension.ts#L24
F5
Create a *.sample file and open
Switch language from json to css

Thanks, that worked!


Updated railroad.py to correct OptionalSequence error

tabatkins/railroad-diagrams#87
OPtionalSequence.writeSVG() was adding an extra 10 pixels to the width for each item and leaving a gap in the path before the next container.

I'm not sure what your edit's trying to do here - it's modifying the code for Stack, which is a vertically-stacking Sequence, rather than OptionalSequence.

Hi Tab,
Apologies if my pull request is wrong in some way.  It’s the first one I’ve ever done and I’m not entirely familiar with how it works.  I’d intended to change the value in line 470 and it looks like I made an editing error.  I’ll change my code properly and recommit - I think that’s the proper procedure, right?
Ian

On 13 Jul 2021, at 00:51, Tab Atkins Jr. @.***> wrote:

I'm not sure what your edit's trying to do here - it's modifying the code for Stack, which is a vertically-stacking Sequence, rather than OptionalSequence.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

The change is actually line 471 anyway - the copy of railroad.py in my venv site-packages folder, which I only installed a few days ago using pip, seems to be missing the new name space url in line 260.  Anyway, I hope I've got this one right.  I don't get why this is a problem on my installation but it clearly works when you test it.  Can you reproduce the issue I'm seeing - images attached?
Ian

Yup, confirmed the problem, and the solution looks good. I'll deploy to pip momentarily. Thanks!


invalid_grant on request when obtaining access_token from somewhere else

Hello,
I have an iOS App where I use SSO to authenticate the user and then save the accessToken & refreshToken locally to keychain on my device. Then I'm calling my server who uses a javascript background function to call your library to make a request to Uber.
So far, I'm trying to set up your library with my 2 local tokens like this:
 var uber = new uberClient({
    client_id: '...',
    client_secret: '...',
    server_token: '...',
    name: 'My App',
    sandbox: true, //optional
    access_token: accessToken,
    refresh_token: refreshToken
  });

afterwards I want to call the uber.requests.getEstimatesAsync endpoint like this:
uber.requests.getEstimatesAsync({
      "start_latitude": pickupLocation["lat"],
      "start_longitude": pickupLocation["lng"],
      "end_latitude": dropoffLocation["lat"],
      "end_longitude": dropoffLocation["lng"]
      })
      .then(function(res) {
        console.log(JSON.stringify(res));
      })
      .error(function(err) {
        console.error(err);
      });
})

Though every time I get an "invalid_grant" error while doing this. Did I make a mistake authenticating myself or setting up the Uber client wrong? Is it even possible to add my local accessToken & refreshToken manually to your uber client?
I'm using a Developer account for doing this, therefore I should actually have all the required permissions for the request endpoint, but I also obtained them previously in the App.
Best regards,
Matt

Hello, currently i have the same issue.

I also have same issue. Tried setting access_token with
uber.access_token = 'xxx'
and in init options and all the same, i always get "invalid_grant" error.
I'm using latest version of module.

So I think it's a problem with the library itself. Because once I made the request with http with the "request" library (https://github.com/request/request) it worked. Include for that at the top of your code:
var request = require('request');
Both OAuth2 and SSO accessToken worked. You should give the method a pickupLocation with latitude and longitude and your obtained accessToken from Uber like this:
function getAllAvailableUberProducts(pickupLocation, accessToken){
    var lat = pickupLocation["lat"].toString();
    var lng = pickupLocation["lng"].toString();

    var options = {
        uri: "https://api.uber.com/v1.2/products?latitude="+lat+"&longitude="+lng,
        method: 'GET',
        headers: {
            "Authorization": "Bearer " + accessToken,
            "Accept-Language": "en_US",
            "Content-Type": "application/json"
        }
    };

    request(options, function (error, response, body) {
        if (!error && response.statusCode == 200) {
            console.log(JSON.parse(body).products);
        } else {
            console.log(error);
        }
    });
}

I hope this helps someone.


Tests failing with seed 49750

Reproducible with bundle exec rspec spec --seed 49750.
See errors in Travis.
Discovered in #686 but fails with any DB.

Commenting this line or skipping the enclosing test passes the other tests.
spec/generators/install_generator_spec.rb#62
Object.send :remove_const, :User

bundle exec rspec --seed 49750 spec/generators/install_generator_spec.rb spec/models/topic_spec.rb fails at spec/models/topic_spec.rb#95
# fails
expect(topic.subscriptions.last.subscriber).to eq(subscription_user)
# passes
expect(topic.subscriptions.last.subscriber.attributes).to eq(subscription_user.attributes)
# fails
expect(topic.subscriptions.last.subscriber.class).to eq(subscription_user.class)

Good find. Thanks for doing this work, @zakak!


Several PostgreSQL operators are incorrectly split in two

Some examples I've encountered:

Before
After

<->
< ->

<=>
<= >

&&
& &

@>
@ >

There are probably many more. I think the formatter should avoid splitting adjacent symbols like this entirely.

Some other examples that are wrongly split:
SELECT
  left <@ right,
  left << right,
  left >> right,
  left &< right,
  left &> right,
  left -|- right,
  @@ left,
  @-@ left,
  left <-> right,
  left <<| right,
  left |>> right,
  left &<| right,
  left |>& right,
  box1 <^ box2,
  box1 >^ box2,
  ?- line,
  left ?-| right,
  left ?|| right,
  left ~= right

Notice that this is only a tiny subset of postgres supported operators. You can get the full list by running
select * from pg_operator;

Additionally you are allowed to create your own operator through CREATE OPERATOR.  The allowed operator characters are `+ - * / < > = ~ ! @ # % ^ & | ` ?`.
I agree with @Diggsey that the tokenizer should avoid splitting sequences of the above symbols in order to be safe. Currently it breaks queries using such operators.

With https://github.com/shssoichiro/sqlformat-rs/pull/57 merged in I think this issue is solved. Any chance we could get a release so I can update my library that depends on sqlformat-rs? Really appreciate the effort you put into this library!

Pushed a new release, please let me know if this is still an issue. Thanks.


(docs) Store navigation sidebar alongside Puppet Server docs content

In the docs.puppetlabs.com website, we use a central config file to assign an
HTML fragment as the navigation sidebar for a group of pages.
It used to be that we had to store these fragments in one specific directory,
but we recently revised our tools so we could load an HTML fragment from any
content directory.
This makes it possible to maintain the navigation TOC right alongside the
content that it governs. The PuppetDB team have been doing this for a few months
now, and it makes it much easier to add or delete a page.
Once this PR is merged, there will be two new tasks for maintaining these docs:

If you add a page, add it to the TOC. Its URL should be an absolute path from
the root of the docs site, and should use a {{server_version}} placeholder
to represent the version number.
When it's time to start preparing for a new X.Y release, change the
server_version value at the top of the nav fragment.

:+1:

:+1: LGTM


np.random doesn't work

np.random doesn't work after upgrading to v0.6.

@Oceania2018 when have time you can check again - if your TF.NET code still work after merge #176 we can close this issue here.


Update README.md

for the training demo, we do not need set .cuda() manually, casue it would load model and diffusion into the master GPU node which is unnecessay. Relate issue: https://github.com/lucidrains/denoising-diffusion-pytorch/issues/146

oh yes you are right, forgot to remove those after migrating to accelerate
thank you!

you are welcome, happy to do a minor contribution ;)


SOGNO

SOGNO Project Proposal
General information
Name of project
SOGNO
Project description (what it does, why it is valuable, origin and history)
The energy decarbonisation increases the share of renewables based distributed generation that is connected to the distribution level of grids. Similarly, the electrification of mobility and heating as well as the flexibility offered by customers result in new power profiles and have a large impact on the operation of distribution grids. Network reinforcements are not sufficient any longer to deal with the increasing complexity of distribution systems. The deployment of advanced distribution management systems down to the low voltage network is required.
SOGNO aims at facilitating the transition to a modular microservices based control center software solution for distribution system operators. This allows operators to adapt faster because components can be updated more independently from each other. It provides system operators and automation software developers with an open source framework that exposes open APIs to plug in new automation functions and supports industry standards such as CIM IEC61970 and IEC61850. The vision is to integrate today’s SCADA systems with SOGNO and gradually move functionalities into microservices.
A preliminary set of automation functionalities will be provided together with the framework and should be further developed as part of the SOGNO project:

state-estimation
load prediction
voltage control

The functionalities developed as part of the project will not be treated differently from any other SOGNO compatible automation functions developed externally and use the same interfaces.
Due to modules for real-time simulation, the SOGNO project supports a seamless integration of development, testing and deployment. New automation functionalities can be developed and thoroughly tested against a virtual real-time representation of the power system.
Project lead
To be decided by the project’s Technical Steering Committee
Project financial sponsor organization(s)
RWTH Aachen University
Names of other key contributing individuals and organizations

Fraunhofer - Digitale Energie
Ricerca sul Sistema Energetico - RSE S.p.A.
RWTH Aachen University
TSSG, Waterford Institute of Technology
EU projects: PlatOne, EdgeFlex

Proposed Technical Steering Meeting (TSC) members
Initial TSC members:
Antonello Monti - RWTH/Fraunhofer<EMAIL_ADDRESS>Markus Mirz - RWTH/Fraunhofer<EMAIL_ADDRESS>Existing community links

repository hosting - initially https://git.rwth-aachen.de/acs/public, later GitHub

project website and docs - https://git.rwth-aachen.de/acs/public/catalogue/-/blob/doc/doc/README.md

mailing lists, slack, irc - none yet
social media accounts - none yet
Link to code base
SOGNO documentation and kubernetes files to set up services: https://git.rwth-aachen.de/acs/public/catalogue
Preliminary set of automation functions:

State Estimation
https://git.rwth-aachen.de/acs/public/automation/se

Load Forecasting
https://git.rwth-aachen.de/acs/public/automation/plf

Coordinated Voltage Control
https://git.rwth-aachen.de/acs/public/automation/covee

Open source status
Please describe the project's license
Apache 2.0
Is this project's code publicly posted?
Yes
Does this project have ongoing public (or private) technical meetings?
So far, regular private meetings
Do this project's community venues have a code of conduct? If so, what is it?
Plan to adopt LF Energy code of conduct
(https://www.lfenergy.org/community/code-of-conduct/)
Describe the project's leadership team and decision-making process.
None yet
Does this project have public governance (more than just one organization)?
None yet
Does this project have a development schedule and/or release schedule?
None yet
Does this project have dependencies on other open source projects? Which ones?

Automation functions listed above (state-estimation, load forecasting, voltage control)
Real-time simulation projects of RWTH (VILLASframework, DPsim)
FiWare generic enablers
docker (containerd), kubernetes, helm, RabbitMQ, Grafana

to be completed

Describe the project's documentation
The documentation will include:

an overview that describes the architecture, what specific solutions were selected and why: virtualization and orchestration, messaging, API gateway, etc.

a catalogue of automation functions / services that are developed as part of the SOGNO project or that are compatible

guides and templates to integrate new automation functions / services

Describe any trademarks associated with the project.
None to our knowledge
Project status
Do you have a project roadmap? please attach [Are this project's roadmap and meeting minutes public posted?]
Not yet
Does this project have a legal entity and/or registered trademarks?
No
Has this project been announced or promoted in any press?
The SOGNO software project is one of the results of the SOGNO EU H2020 project. The H2020 project has been promoted in press (https://www.sogno-energy.eu/).
Does this project compete with other open source projects or commercial products?
Concerns that SOGNO might overlap with the LF Energy SEAPATH project have been discussed and it was concluded that the two projects have different goals. SEAPATH is focusing on substation automation at the edge, whereas the focus of SOGNO is on the control center. Besides the testing of automation functions based on real-time simulation does not seem to be part of SEAPATH.
No competing commercial products known. The aim of SOGNO is to integrate with existing SCADA solutions.
Project value
Why would this project be a good candidate for inclusion in LF Energy? Provide a statement on alignment with the mission in the LF Energy charter.
To cope with the drastic changes in power systems explained in the beginning, it is important to develop next generation distribution management systems that can be adapted rapidly. The key factors to enable this rapid adaptation are modularization and open source components that allow stakeholders to focus on the functionalities that they require the most and share development efforts.
What specific need does this project address? Describe how this project impacts the energy industry.
Today, automation software is built in a monolithic way and cannot be extended easily mixing products of different vendors. With more and more new types of equipment, e.g. electric vehicles, being connected to grids, it becomes increasingly difficult to keep up with the resulting requirements on grid automation.
The modular microservices based approach of SOGNO enables a multi-vendor/supplier control center solution and even to develop functionalities together with other stakeholders.
The built-in support for real-time simulation based testing further supports the fast integration of new automation systems since the same environment can be used in testing and operation.
Describe how this project intersects with other LF Energy projects.
See comments on LFE SEAPATH project above.
Who are the potential benefactors of this project? What other organizations in the world should be interested in this project?
The project could be interesting for power system utilities as well as automation system developers and researchers as an open platform to integrate their solutions.
Project needs
How would this project benefit from inclusion in LF Energy
Becoming part of LF Energy, a vendor neutral entity, would make the project more attractive as a platform integrating solutions of multiple vendors and developers contributing directly to the project or compliant modules.
Please describe any infrastructure needs or requests (e.g., web hosting).
None at the moment
Plan for achieving next maturity level (Incubation -> Early Adoption -> Graduated).
The project was tested in several field trials with DSOs. The idea is to provide an MVP that can be used in production within the next 2 years.

Moving out 1 meeting to accommodate an agenda item

Annual review approved on 4/23/2024 - moving out next review one year.


DetectX Module

Will pull a json file from DetectX granted the admin deploying this module places it in the cache dir.

Thanks. Could you please fix the indenting? I have a hard time reading the code.. ;-D

Atom must be messing with it since I turned off softwraps. I'll get it all prettified and a touch statement to add an empty json file in install.sh then commit again.

@bochoven Is that any better?

@bochoven should be fixed now.

@bochoven @tuxudo Thanks for pointing those out, should be fixed now.


grid-column, grid-row shorthands do math

Similar to: https://github.com/leafo/scssphp/issues/542
When using the line-based placement shorthand (e.g. grid-column: 1 / 3), the compiler does the division math and the CSS output is grid-column: 0.333333...
Two easy workarounds:
grid-column: #{"1 / 3"};

or
grid-column-start: 1;
grid-column-end: 3;

Filed with the note that Node-Sass handles this properly.

in Compiler.php change the line 1646 to
if ($compiledName === 'font' || $compiledName === 'grid-row' || $compiledName === 'grid-column') ...
This will not match expressions inside the grid-row or grid-column


Bump identity.apps.core version to 2.4.9

$Subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/9850899388

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/9850899388
Status: success


Inference with FasterTransformer with GLB-130B

Hi!
I am trying to configure the GLM-130B models with FasterTransformer and I need to convert glm ckpt files, so where i can get model_optim_rng.pt file?
And I'm facing this
CMake Error at cmake/Modules/FindNCCL.cmake:153 (message):   Found NCCL header version and library version do not match! (include:   /home/ubuntu/anaconda3/envs/glm/include, library:   /home/ubuntu/anaconda3/envs/glm/lib/libnccl.so) Please set NCCL_INCLUDE_DIR   and NCCL_LIB_DIR manually. Call Stack (most recent call first):   CMakeLists.txt:41 (find_package)
while i'm trying to make build using this command cmake -DSM=70 -DCMAKE_BUILD_TYPE=Release -DBUILD_PYT=ON -DBUILD_MULTI_GPU=ON ..
My basic task is to minimize the inference time I also configured THUDM/GLM-130B main branch and I set MAX_OUTPUT_LENGTH=64 it takes about 55s to generate a response.
Machine Specs: (V100) 8 * 32GB
Thanks

Thank you!
Do you know any other method which helps me to reduce response time for GLM-130B?

We have just released the quantized version of GLM-130B. The V100 servers can efficiently run the GLM-130B in INT8 precision, see Quantization of GLM-130B for details.

We have just released the quantized version of GLM-130B. The V100 servers can efficiently run the GLM-130B in INT8 precision, see Quantization of GLM-130B for details.
Hello,the Quantization  method referred in the link can also apply to GLM-10B model?

We haven't tried it, but I think a smaller model might be easier to do quantization.

We have just released the quantized version of GLM-130B. The V100 servers can efficiently run the GLM-130B in INT8 precision, see Quantization of GLM-130B for details.
Hello,the Quantization  method referred in the link can also apply to GLM-10B model?

We haven't tried it, but I think a smaller model might be easier to do quantization.

i juset convert to 4-way for the GLM-10B,but i run the generate_block.sh,but failed to load the model

We have just released the quantized version of GLM-130B. The V100 servers can efficiently run the GLM-130B in INT8 precision, see Quantization of GLM-130B for details.
Hello,the Quantization  method referred in the link can also apply to GLM-10B model?

We haven't tried it, but I think a smaller model might be easier to do quantization.

i juset convert to 4-way for the GLM-10B,but i run the generate_block.sh,but failed to load the model

i change the MPSIZE to4 in the script

用FasterTransformer加速推理中指定某个pt,还是整个pt的文件夹？

Hello @jiangliqin! This repo is only for GLM-130B model, we have not yet do quantization for GLM-10B.


Update README to reflect eventual Windows support

Moved 'Windows support' from the 'Non Goals' section of the feature list to the 'Eventually' section. In light of recent developments, I think this change might more accurately reflect the roadmap for the project.

Merged. Thanks: f8dc21fa644526ae234db3b224c7a9570bd724d2


Able to trigger the QM Detail Window

I thought it is the Raycast problem. But actually, it is because of the Collider.
Problem solved with oneline for each Block: lowerBlock.AddComponent<MeshCollider>().convex = true;
😆😂
In this Pull Request:

Click QM -> Show QM Detail Window
Change content type for API Key Field (hide the API)
Add unit test example
Add a Help Window

Update: Change to Right Mouse Click

I'm afraid the QM click does not work as intended -> when I'm navigating (i.e. having mouse clicked down and then pressing WASD to navigate) as soon as my mouse points to a block, it interprets it as if I clicked on it and sidebar pops up. So we want to differentiate behaviour when navigating vs. clicking on a block.
Otherwise password, help button and test look great 👍

Do you think it would be more appropriate to change it to double-click?

I'm afraid the QM click does not work as intended -> when I'm navigating (i.e. having mouse clicked down and then pressing WASD to navigate) as soon as my mouse points to a block, it interprets it as if I clicked on it and sidebar pops up. So we want to differentiate behaviour when navigating vs. clicking on a block.
Otherwise password, help button and test look great 👍

Do you think it would be more appropriate to change it to double-click?

Change to Right Mouse Click