When forcing null on attributes, hasChanges does not detect changes

Laravel Version: 5.7
PHP Version: 7.1

Description:
Forcing null on method isDirty
https://github.com/laravel/framework/blob/6ff9df42c8a6d9230bbaca5171a5d6253fa71890/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php#L1036
Makes that hasChanges
https://github.com/laravel/framework/blob/6ff9df42c8a6d9230bbaca5171a5d6253fa71890/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php#L1074
This happens because func_get_args() is returning
array:1 [▼
  0 => null
]

Steps To Reproduce:
Just force null on isDirty

Hmm, I see your point. Feel free to send in a PR for this.

Fix has been rejected in #23929.

@staudenmeir thanks for making me aware. As there are no plans to change this atm I'm gonna close this. Feel free to open up an issue in https://github.com/laravel/ideas to see if you can get support to change this behavior.


Customizing the TabBar with a sliding ScrollView

Current behaviour
The top tab bar works as expected but I am trying to turn it into a sliding top tab bar where the tabbar itself slides to display overflow of tab items. I wrapped the TabBar component in a horizontal scrollview in the renderTabBar. The current effect this gives is it slides as I want but anywhere on the screen i gesture to the right or left makes it slide. I think I somehow have to wrap the TabItem component that is being looped on in the scrollview instead.

Expected behaviour
The expected behavior is to have only the TabBar slide not the whole screen because right now the bottom content in the screen does not let me scroll down to it. The TabBar currently slides even if I gesture below it on other content to the right or left.

Code sample
<TabView         navigationState={this.state}         renderScene={SceneMap({           first: FirstRoute,           second: SecondRoute,           third: ThirdRoute,           fourth: FourthRoute,           fifth: FifthRoute,           sixth: SixthRoute,         })}         onIndexChange={index => this.setState({ index })}         swipeEnabled={false}         renderTabBar={props =>           <ScrollView       horizontal       style={{width: width, height: 55, paddingBottom: -400, marginRight: 0, marginBottom: -400, elevation: 4}}       showsHorizontalScrollIndicator={false}       contentContainerStyle={{ paddingBottom: 0, marginBottom: 0 }}       decelerationRate={6.5}         snapToInterval={width - 100}         snapToAlignment={"center"}     >           <TabBar             {...props}             indicatorStyle={{ backgroundColor: 'white', fontSize: 16, fontWeight: '500' }}             labelStyle={{ fontSize: 16, fontWeight: '400'}}             tabStyle={{marginRight: 25}}             style={{ backgroundColor: '#f4511e', height: 55, paddingBottom: 0, marginBottom: 0 }}           />           </ScrollView>         }         initialLayout={{ width: Dimensions.get('window').width, height: 0 }}       />

Screenshots (if applicable)

What have you tried
I tried wrapping the  <ScrollView       horizontal       style={{width: width, height: 55, paddingBottom: -400, marginRight: 0, marginBottom: -400, elevation: 4}}       showsHorizontalScrollIndicator={false}       contentContainerStyle={{ paddingBottom: 0, marginBottom: 0 }}       decelerationRate={6.5}         snapToInterval={width - 100}         snapToAlignment={"center"}     >             {routes.map((route: T) => (               <TabBarItem                 key={route.key}                 position={position}                 route={route}                 tabWidth={tabWidth}                 navigationState={navigationState}                 scrollEnabled={scrollEnabled}                 getAccessibilityLabel={getAccessibilityLabel}                 getAccessible={getAccessible}                 getLabelText={getLabelText}                 getTestID={getTestID}                 renderBadge={renderBadge}                 renderIcon={renderIcon}                 renderLabel={renderLabel}                 activeColor={activeColor}                 inactiveColor={inactiveColor}                 pressColor={pressColor}                 pressOpacity={pressOpacity}                 onPress={() => {                   onTabPress && onTabPress({ route });                   this.props.jumpTo(route.key);                 }}                 onLongPress={() => onTabLongPress && onTabLongPress({ route })}                 labelStyle={labelStyle}                 style={tabStyle}               />             ))} </ScrollView>
in the TabBar.tsx with the ScrollView but it does not help. There maybe a whole better way to achieve what I am trying to do and any help would be appreciated. Thank you!

Your Environment

software
version

ios or android
both

react-native
0.59.9

react-native-tab-view
2.7.1

react-native-gesture-handler
1.3.0

react-native-reanimated
1.1.0

node
v10.7.0

npm or yarn
6.1.0

I'm not sure what you're trying to achieve, but you can completely replace the tab bar with renderTabBar with your own implementation. You don't need to use the exported TabBar.
There are examples in the README and example folder on how to implement a custom tab bar.

@paingha I had a similar use-case and I was able to make it work like below, it might not be the best solution but I hope it helps you or anyone else searching for this.

    renderTabBar={(props) =>
         <ScrollView
             horizontal={true}
             style={{ height: 50, flexGrow: 0 }}
             showsHorizontalScrollIndicator={false}
             scrollEventThrottle={200}
             decelerationRate="fast"
        >
            <TabBar
                {...props}
                style={{ height: 50 }}
                indicatorStyle={{ backgroundColor: 'white' }}
            />
        </ScrollView>
    }

`
Essentially, I had to wrap the TabBar into a <ScrollView> with horizontal={true} and set flexGrow: 0.
flexGrow: 0 actually made it to contain the tab in the size it required, otherwise it took more height but again that might just be for my specific case.

@Shiroe This worked great, thanks for the snippet! 👏

isScrollable : true  make my day

@Shiroe This worked great, thanks for the snippet! clap
UPDATE: scrollEnabled does the trick. Ditch the ScrollView solution it was only causing issues...

Not working in custom Tabbar.


BUG: can't get photo via #media when the return just contain #entities

when the return like below, #media can't get photo url. can you fix it????
created_at: "Sun Jun 25 07:21:01 +0000 2017",
id:<PHONE_NUMBER>80091400,
id_str: "878875663180091393",
text: "全関東学生ダー",
truncated: true,
entities: {
  hashtags: [ ],
  symbols: [ ],
  user_mentions: [ ],
  urls: [
    {
      url: "https://t.co/Md2ph7pktc",
      expanded_url: "https://twitter.com/i/web/status/878875663180091393",
      display_url: "twitter.com/i/web/status/8…",
      indices: [
       117,
       140
      ]
    }
   ]
},
source: "Twitter for Android",
in_reply_to_status_id: null,
in_reply_to_status_id_str: null,
in_reply_to_user_id: null,
in_reply_to_user_id_str: null,
in_reply_to_screen_name: null,

#media only can get #extended_entities, but sometimes, Twitter returns "entities" instead of "extended_entities".  @sferik

@sferik  @stve

Any ideas?

can you share some code? I can't find a tweet with id<PHONE_NUMBER>80091400 to troubleshoot with. Thanks.

I think I may have a similar issue. Using ruby 2.3.4p301 I instantiate a client and fetch a status with an image (https://twitter.com/i/web/status/887025375754166272) but media is empty.
client = Twitter::REST::Client.new do |config|
  config.consumer_key = ENV.fetch('TWITTER_CONSUMER_KEY')
  config.consumer_secret = ENV.fetch('TWITTER_CONSUMER_SECRET')
  config.access_token = ENV.fetch('TWITTER_ACCESS_TOKEN')
  config.access_token_secret = ENV.fetch('TWITTER_ACCESS_SECRET')
end

status = client.status(887025375754166272)

status.media?
=> false

I'm working with @ckundo on this. It looks like:
status = client.status(887025375754166272, tweet_mode: :extended)

Does the trick of loading media correct.

Based on changes documented here, it appears that only extended tweets will include media entities. https://dev.twitter.com/overview/api/upcoming-changes-to-tweets


Executing bang scripts fail on Linux

When executing bang on Linux, I get the following:
$ cat first_bang
#!/usr/bin/env bang run

[ -n "$1" ] && b.task.run "$@"

$ ./first_bang
/usr/bin/env: bang run: No such file or directory

I can quickly solve this by creating following script bang_run in my path:
#!/usr/bin/env bash

bang run "$@"

and changing the shebang in first_bang to:
#!/usr/bin/env bang_run

Hey!
Have you tried creating an symbolic link of bang in your /usr/local/bin path? maybe it solves the problem. You can check the Makefile in the install section. Btw, can you provide the name and version of your linux distribution?

Hello bellthoven,
I created a link in /usr/bin but no gain. The error remains.
I did find an ugly workaround by creating the wrapper script indicated above as "/usr/bin/bang run". Yes, a space in an application name !
My distro is Fedora 21 (workstation edition but with KDE).
Regards,
Eric

I think this issue was closed by #10, so I am closing it.


ci: add +nightly to commands

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 16.39%. Comparing base (77f5000) to head (c06d5df).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #149      +/-   ##
==========================================
- Coverage   16.39%   16.39%   -0.01%
==========================================
  Files        1467     1467
  Lines      129229   129228       -1
==========================================
- Hits        21187    21186       -1
  Misses     108042   108042

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


the  service url in deployment change

when i build always try to get routes etc from local host to my custom url for routes etc for production. The docs dont eleaborate for a beginner

more details pls, fail to catch up

when i place
yarn build and
serve my application i get 404 error. because tries get from localhost:5000
but i want not use mock api
rather my domain

just modify proxy in .umirc

just modify proxy in .umirc

same problems, i already change proxy in .umirc but nothing  change. application just run localhost:7000/api

just modify request.js, force axios use your domain

How to change the request.js so that it can use my own domain? After chaging that, in which way should I send the request? I used fetch to send request but the domain is still using 7000

just change let domain = '' to let domain = 'http://www.xx.com'


Improve documentation

Readme missing for:

Configuration
Side effect caching
Overall orbit behaviour

Hi, I'd like to request the Orbit docs include each new orbit method we've created (including legacy in its own section w/ deprecation and what to use instead) as well as API info on what to use the method for.
For example:
Current
.transform{ sends the code to the Appropriate Transformer . Should be used for API/backend/repository calls / business logic.
Legacy
.ignoreEvents() Does
-- (@Deprecated: As of 2.1.0 this is no longer necessary.)
Right now there's no documentation on what these methods do and looking at the javadocs / kotlin docs isn't helpful either (still doesn't indicate purpose, just mentions kotlin extensions)
https://babylonhealth.slack.com/archives/G1ZJNHMGR/p1573744275488700


H2 and H3 headings too similar visually

I believe the solution is to adopt a medium contrast type scale, which provides balanced contrast between heading sizes without overly large jumps. A type scale refers to the multiple by which font sizes increase. You can find more about typographic scales here: Typographic Scales.
For content-heavy websites like ours, a medium contrast scale is ideal, typically ranging from 1.2x - 1.33x. The larger the scale, the more contrast between heading sizes. However, I don’t want a drastic deviation from our current font sizes, as this could disrupt the look and feel of projects using our theme.
Constraints

Minimum size of 16px for accessibility.
Avoid major deviations from the current sizes.

Given these constraints, we're limited to a scale of approximately 1.2x. I’ve used the Minor Third scale (1.2x) and rounded the values to the nearest even whole number, with the Major Third scale (1.25x) added for reference:

Heading
Current Size (px)
Current Scale
Major Third (1.25x)
Minor Third (1.2x, rounded off)
Suggested Size (px)
Calculated Suggested Scale

H1
40
-
49
40
42
-

H2
32
1.25
39
33
34
1.23

H3
28
1.143
31
28
28
1.214

H4
24
1.167
25
23
24
1.167

H5
20
1.2
20
19
20
1.2

H6
18
1.111
16
16
16
1.25

Summary:

Except for the H4 to H3 transition, all headings have a minimum of a 1.2x increase, which is an improvement over the current scale.
I also suggest using a 600 weight for better legibility across headings. I added these details and some examples in Figma: Updated Heading Typography

Here’s a final comparison of current vs. suggested values:

Heading
Current Size (px)
Current Size (rem)
Suggested Size (px)
Suggested Size (rem)

H1
40
2.500
42
2.625

H2
32
2.000
34
2.125

H3
28
1.750
28
1.750

H4
24
1.500
24
1.500

H5
20
1.250
20
1.250

H6
18
1.125
16
1.000

This was discussed today and the final recommendations of new font size and increased font weight was accepted within the team. This is now ready for dev 💻
Final Recommendations:

Heading
Current Size (px)
Current Size (rem)
Suggested Size (px)
Suggested Size (rem)

H1
40
2.500
42
2.625

H2
32
2.000
34
2.125

H3
28
1.750
28
1.750

H4
24
1.500
24
1.500

H5
20
1.250
20
1.250

H6
18
1.125
16
1.000

Font Weight: 600
And also some designs and examples in Figma: Updated Typography (#97)


Include git in images

This is useful for projects which use the Cargo config:
git-fetch-with-cli = true
This can be necessary for working with some private repositories as
dependencies.

Sorry, this wasn't quite ready, will open a new PR later.

Diff looks plausible. Could you compare the Socker image sizes after adding git?

Without changes:  864MB (864364317KB)
With changes: 878MB (877657948KB)

@snoyberg @adityakalia thank you


Clarify which testnet is used

Hi, I think the source section should indicate which testnet is used. I searched for that address in Ropsten, Kovan and Rinkeby but neither of those has anything at that address.

Currently, the 0.9.3 is deployed both on Kovan and Ropsten. Check the main page https://github.com/ethereum-alarm-clock/ethereum-alarm-clock or https://github.com/ethereum-alarm-clock/ethereum-alarm-clock/commit/bb64d33730bbf29cedcb34418d162efdfbbefcf5


Cannot build with dynamicIO enabled.

Describe the Bug
When enabling the experimental dynamicIO feature, the following error occurs during build:
Error occurred prerendering page "/admin/[[...segments]]". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Route "/admin/[[...segments]]" has a `generateMetadata` that depends on Request data (`cookies()`, etc...) or external data (`fetch(...)`, etc...) but the rest of the route was static or only used cached data (`"use cache"`). If you expected this route to be prerenderable update your `generateMetadata` to not use Request data and only use cached external data. Otherwise, add `await connection()` somewhere within this route to indicate explicitly it should not be prerendered.
Export encountered an error on /(payload)/admin/[[...segments]]/page: /admin/[[...segments]], exiting the build.

While this is experimental, the documentation for the new 'use cache' directive states that it aims to replace the unstable_cache API.
Given that we will be using the payload client directly in Server Actions, we will need a way to cache those actions with tags (for revalidateTag). React's cache doesn't support tagging for manual revalidation, which leaves only Next's unstable_cache and 'use cache' with cacheTag as options.
Link to the code that reproduces this issue
blank
Reproduction Steps
Enable experimental dynamicIO feature.
Build.
Which area(s) are affected? (Select all that apply)
area: core
Environment Info
Payload: beta-119
Node: 20
Next.js: 15.0.2-canary.9

got the same error and the
await connection() doesn't help
import React, { FC } from 'react'
import { Metadata } from 'next'
import { connection } from 'next/server'

type DashboardProps = {
  searchParams: Promise<{ [key: string]: string | string[] | undefined }>
}

export const generateMetadata = async (
  props: DashboardProps
): Promise<Metadata> => {
  const searchParams = await props.searchParams
  const { page: currentPage } = searchParams

  return {
    description: `${currentPage}`,
  }
}

const Page: FC<DashboardProps> = async () => {
  await connection()

  return
Page

}

export default Page

and the log:
Next.js 15.0.2-canary.11
   - Environments: .env.local, .env
   - Experiments (use with caution):
     · turbo
     · dynamicIO

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ✓ Collecting page data

Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Route "/" has a `generateMetadata` that depends on Request data (`cookies()`, etc...) or external data (`fetch(...)`, etc...) but the rest of the route was static or only used cached data (`"use cache"`). If you expected this route to be prerenderable update your `generateMetadata` to not use Request data and only use cached external data. Otherwise, add `await connection()` somewhere within this route to indicate explicitly it should not be prerendered.
Export encountered an error on /(public)/page: /, exiting the build.
 ⨯ Static worker exited with code: 1 and signal: null

node -v
v22.11.0

I think this issue is related to this error too

Instead of using await connection() at the page level, wrapping the layout with <Suspense> solved the problem for me.
app/(payload)/layout.tsx
import configPromise from "@payload-config";
import "@payloadcms/next/css";
import { RootLayout } from "@payloadcms/next/layouts";
import React, { Suspense } from "react";

import "./custom.scss";
import { importMap } from "./admin/importMap";

type Args = {
  children: React.ReactNode;
};

const Layout = ({ children }: Args) => (
  <Suspense>
    <RootLayout importMap={importMap} config={configPromise}>
      {children}
    </RootLayout>
  </Suspense>
);

export default Layout;

See also the Next.js blog entry: Our Journey with Caching - Dynamic
I can't judge whether that's technically correct. My understanding of Next.js isn't deep enough for that.

I think wrapping the layout this high up would have a negative impact on the /api routes as well, but I'm not certain about that. I did also try wrapping the app/(payload)/admin/[[segments]]/page.tsx RootPage with Suspense, as well as creating a loading.tsx file (also generates a Suspense boundary), and finally creating a app/(payload)/admin/layout.tsx wrapping the children prop with Suspense. None of those worked.
It is interesting though that wrapping the root payload layout with Suspense works. This seems to indicate there's something in RootLayout causing the issue rather than RootPage as the error suggests.

This error said:
throw new CanaryOnlyError('experimental.dynamicIO');
^
CanaryOnlyError: The experimental feature "experimental.dynamicIO" can only be enabled when using the latest canary version of Next.js.
just upgrade npm i next@canary

@pedroaparecido As listed originally in my issue post, canary is being used. When you install canary, and enable dynamicIO, this issue occurs. While this is a canary-only option now, it has been stated by the Next.JS team to be the expected successor to the unstable_cache function. This would make the new use cache directive the only first-party way to cache server actions that use the local payload API with the ability to tag each cache and manually invalidate them.

Just bumped into this issue as well trying to deploy to Vercel.
@Figumari solution worked but I am getting the exact same error on my dynamic routes now too, outside of admin/.

Just bumped into this issue as well trying to deploy to Vercel. @Figumari solution worked but I am getting the exact same error on my dynamic routes now too, outside of admin/.

Ditto.


fix log spam

this makes the holo bridge warning print as debug instead of as warn, so it doesn't spam client logs.

imma need to fix some other stuff too so give me an hour


Test failure fix #14235

Test Failure Fix linked with https://github.com/apache/pinot/pull/14235

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (feb67de).
Report is 1203 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (feb67de). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (feb67de)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
0

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14260       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
?

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Dev tooling2

Added support for fragment styling via regexp for makeTabs and makeExample
Added gulp help support
Added gulp task to determine which examples and associated jade files are affected as a result of a given git commit.
... and associated refactoring and cleanup.

Wow! @jtraband and @wardbell, you two have been going to town!
It'd be great if we could split these kinds of PRs up into a couple smaller ones, and maybe do some squashing next time.
Taking a look now.

Files changed 382

I'm kinda overwhelmed. Even ignoring the generated fragments, I'm having a hard time following this. @jtraband: are there a couple key files/modifications that you could point me towards?

I'm going to get rid of 272 unwanted file changes and squash this thing today.
We've wanted to do smaller PRs but its been hard to get the cycle going fast enough. We'll work on this for the next round.
Meanwhile, hang tight on this PR. We're likely to withdraw it and submit something less ominous.
Please note that, post squash, the commit message will likely be crisp such as: " updated dev guide sample code management infrastructure and getting started samples"

:+1: Thanks, Ward

Close and discard this PR in favor of #203


Opening saved link should autoload ABI

Seems that's broken rn
e.g. https://callthis.link/?to=callthis.eth&value=0.1

Loads on preview, but it should load on edit too. Example: https://callthis.link/?to=uniswap.eth


Minetest Edu/Minecraft Education Thoughts

Once of this original goals of McThings is Education. And this goal has been already covered in Minecraft and Minetest.
There is Minecraft Education, which is the reference. It has specific behaviours in this version (like Strucure Blocks which are more powerful and easy too use), and it is now (June 2020) in 1.12.60 (it has not passed the flattening change!) and based on the Bedrock Edition.  Probably we must analyze if it is interesting to join this effort, but it is only for Bedrock (in the app market I can not find an Android version). It seems Linux could run the Bedrock edition: https://github.com/minecraft-linux/mcpelauncher-manifest/wiki (https://github.com/ChristopherHX/linux-packaging-scripts) but probably it is a hack that could break easily.
In Minetest there are also Edu initiatives: https://wiki.minetest.net/MinetestEDU But it needs a lot of work so it is ready to be deployed in schools easily for example. https://github.com/minetest-edu has potential but it is in its infancy. The most promising project is: https://framinetest.org/en/  The mods they ysed are at: https://framagit.org/Framinetest-mods. One of the issues is that it seems to be a French language based project.  https://framacolibri.org/t/some-questions-about-framinetest/5556/9 is interesting to know more details.
So, what to do? Contributing to Minetest Edu seems to be he natural approach for a project like McThings.

Our approach is to support all platforms (Minecraft Edu probably can import Schematics using some tool, or use worlds generated with McThings scenes). Let's see if we can accomplish our goals and this overall strategy.


Descriptor support

Hello, are you planning/working on descriptor API support?
Thank you!

Hello,
What are you missing from that documentation ?
There is some support available already in the schema module and Schema class.

DESCRIPTOR_TYPES is an attribute that gives you the different type available directly in aepp
getDescriptors, createDescriptor , putDescriptor and deleteDescriptor exist

In the SchemaManager class, a createDescriptorOperation also exist to simplify the task.

Apologies, I didn't look carefully enough. All needed functions are available.


Number format

It is not really an issue but it would make the stats more readable when a thousand separator would be used!
When a memcache server is running for weeks then the hits/miss, ... numbers are very high.
what is more readable?
a)<PHONE_NUMBER>49
b) 465'983'216'549
and it would be even more general when the single quote would be used like in the above example.

Would a comma not be the more common thousand separator?

:-) What ever :-)
I suggested ' because comma is used in Europe as the decimal point. As long the long numbers are more readable...


feat(auth): force terms on social sign up FR-2869

https://user-images.githubusercontent.com/49310486/118881769-19db3d80-b8fc-11eb-8c81-2cace2d6c0bc.mov


provide request context for oscp session creation

Previously platform dependent on NSS_CERT_STORE couldnt follow up on incomplete certificate chain, this fixes it.
Tested with https://incomplete-chain.badssl.com/

Thanks!


[Fix] Adjoint Ode bug fixes

Summary
This has a few fixups for the reverse mode ode adjoint method. There are quite a few places where I was worried we could be indexing incorrectly or shallow copying objects when we should be doing a hard copy. Changes include:
count_vars.hpp

Changing order of functions for count_vars_impl so that the forward declares are not needed

cvodes_integrator_adjoint.hpp

Moving y_return_ out of solver_ and into the top class wrapped with arena_t<std::vector<Matrix>>.

Fix list initializer order of object instantiation in cvodes_solver (this usually throws an error in gcc so I'm surprised it did not.)

Moves all the checks into the initializers for each of the top class's members. This looks a bit odd, but I had a really hard time parsing out what we were checking when these were all laid out in the body of the class's constructor since there's so many. So I made an immediately invoked lambda within each of the initializers that does the checks for each input directly in the initializer.

        ts_([](const char* function_name, auto&& ts) {
          check_nonzero_size(function_name, "times", ts);
          check_finite(function_name, "times", ts);
          check_sorted(function_name, "times", ts);
          return arena_t<std::vector<T_ts>>(ts.begin(), ts.end());
        }(function_name, ts)),

I'm fine with moving this back to in the body but imo this cleans up everything nicely and allows for solver_ to also be constructed in the initializer list.

Removes the store_state() member function. Instead all we need to do is make a deep copy of state_forward_. The reason for this is because state_forward_ is an arena_matrix<Eigen::VectorXd>. arena_matrix<> types are the equivalent of a map around memory allocated by the stack allocator

Eigen::Map<Eigen::Matrix<Scalar, Rows, Cols>>(ChainableStack::alloc_array<Scalar>(rows * cols), rows, cols)

One important point is that they do shallow copies of each other (essentially assigning an arena matrix to another arena matrix is the same as just giving the lhs the pointer of the rhs. What this all means is that since state_forward_ is an arena matrix and we don't want it's memory going into the y_return_ or y_ matrices we need to make a hard copy of it to a Eigen::VectorXd before we do assignment.

Makes a hard copy of y_return_ when calling solution()

Gives a nicer error message when a particular parameter or data comes in as non-finite during the forward pass.

In chain whenever two eigen matrices of the same size are being assigned to each other I removed some of the explicit loops and used eigen matrix assignments directly. This should help us ensure we don't have indexing errors.

arena_type.hpp
This was just a small change to the std::vector<> overload to make sure we also caught const std::vector<T>& etc. template parameters.
Tests
Right now I'm just testing this locally by running the example from discourse available in the comment here. Once we think this looks good and @wds15 tests locally I can take the ODE part of that model and put it into the testing framework.
@wds15 when running it locally the first few iterations throw errors, but then after that the model seems to sample fine. Is this okay/what we would expect? Or would we not know until all the sampling is complete?
$ ./Test_Adjoint_v2 data file="adjoint_data.json" init="init.json" sample output refresh=2
method = sample (Default)
  sample
    num_samples = 1000 (Default)
    num_warmup = 1000 (Default)
    save_warmup = 0 (Default)
    thin = 1 (Default)
    adapt
      engaged = 1 (Default)
      gamma = 0.050000000000000003 (Default)
      delta = 0.80000000000000004 (Default)
      kappa = 0.75 (Default)
      t0 = 10 (Default)
      init_buffer = 75 (Default)
      term_buffer = 50 (Default)
      window = 25 (Default)
    algorithm = hmc (Default)
      hmc
        engine = nuts (Default)
          nuts
            max_depth = 10 (Default)
        metric = diag_e (Default)
        metric_file =  (Default)
        stepsize = 1 (Default)
        stepsize_jitter = 0 (Default)
    num_chains = 1 (Default)
id = 1 (Default)
data
  file = adjoint_data.json
init = init.json
random
  seed =<PHONE_NUMBER> (Default)
output
  file = output.csv (Default)
  diagnostic_file =  (Default)
  refresh = 2
  sig_figs = -1 (Default)
  profile_file = profile.csv (Default)
num_threads = 1 (Default)

Gradient evaluation took 0.463662 seconds
1000 transitions using 10 leapfrog steps per transition would take 4636.62 seconds.
Adjust your expectations accordingly!

Informational Message: The current Metropolis proposal is about to be rejected because of the following issue:
Exception: ode_adjoint_tol_ctl: ode parameters and data[397] is inf, but must be finite! (in '/tmp/Rtmp5le0nw/model-1b38f07d4012f8.stan', line 141, column 2 to line 156, column 74)
If this warning occurs sporadically, such as for highly constrained variable types like covariance matrices, then the sampler is fine,
but if this warning occurs often then your model may be either severely ill-conditioned or misspecified.

Informational Message: The current Metropolis proposal is about to be rejected because of the following issue:
Exception: ode_adjoint_tol_ctl: ode parameters and data[397] is inf, but must be finite! (in '/tmp/Rtmp5le0nw/model-1b38f07d4012f8.stan', line 141, column 2 to line 156, column 74)
If this warning occurs sporadically, such as for highly constrained variable types like covariance matrices, then the sampler is fine,
but if this warning occurs often then your model may be either severely ill-conditioned or misspecified.

Informational Message: The current Metropolis proposal is about to be rejected because of the following issue:
Exception: CVODES: CVode At t = 0 and h = 5.75889e-102, the corrector convergence test failed repeatedly or with |h| = hmin. Error code: -4 (in '/tmp/Rtmp5le0nw/model-1b38f07d4012f8.stan', line 141, column 2 to line 156, column 74)
If this warning occurs sporadically, such as for highly constrained variable types like covariance matrices, then the sampler is fine,
but if this warning occurs often then your model may be either severely ill-conditioned or misspecified.

Informational Message: The current Metropolis proposal is about to be rejected because of the following issue:
CVODES: CVode At t = 394 and h = -2.81685e-26, the error test failed repeatedly or with |h| = hmin. Error code: -3
If this warning occurs sporadically, such as for highly constrained variable types like covariance matrices, then the sampler is fine,
but if this warning occurs often then your model may be either severely ill-conditioned or misspecified.

Iteration:    1 / 2000 [  0%]  (Warmup)
Iteration:    2 / 2000 [  0%]  (Warmup)
Informational Message: The current Metropolis proposal is about to be rejected because of the following issue:
Exception: normal_lpdf: Scale parameter is 0, but must be positive! (in '/tmp/Rtmp5le0nw/model-1b38f07d4012f8.stan', line 188, column 23 to column 59)
If this warning occurs sporadically, such as for highly constrained variable types like covariance matrices, then the sampler is fine,
but if this warning occurs often then your model may be either severely ill-conditioned or misspecified.

Iteration:    4 / 2000 [  0%]  (Warmup)
Iteration:    6 / 2000 [  0%]  (Warmup)
Iteration:    8 / 2000 [  0%]  (Warmup)
Iteration:   10 / 2000 [  0%]  (Warmup)
Iteration:   12 / 2000 [  0%]  (Warmup)

Side Effects
Release notes
Bug fix for ODE adjoint method
Checklist

[ ] Math issue #(issue number)

[x] Copyright holder: Steve Bronder
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

This version does not work at all for me. CVODES complains not being able initialise... and the reason is that you de-allocated the forward data-structures of CVODES after solving the forward problem. That's not OK, since CVODES really expects all things to be still in place when doing the backward solve.
Moreover, I switched the model posted in the other PR over to use the bdf solver. Once I do that, then I get a very slow running program, but the program seems to sample just fine - I do not get any of those Inf rejections. I was too impatient to wait for all 10 iterations (will let that program run on the side and report later).
So as it stands this version in this PR seems to still suffer from the problems we have originally and "my" PR seems to avoid these issues with Inf - and the bdf integrator is also working fine and does not trigger throwing "Inf" issues. How about we go ahead with the other PR? Either as is or we clean that up if you think that is needed?


Create  component

Description
Badges are non-clickable labels that communicate the status of any particular instance (e.g. booking).
Visual style

Zeplin: https://zpl.io/2j4YyOA
Interactions
As badge is non-clickable, there are not many interactions. Only interaction here is triggering something after hovering the badge, for example showing a tooltip.
Additional information

We have only one size
It should have the possibility to show icon on the left side.
It should be possible to force circular shape - for notification badges (if it's not different component)

Storybook chapters
Default

Type: Neutral, with icon

Badge types (not sure if one chapter or more)

List of all types of badges
Possibility to change: icon, text

Notification badge

Circle badge with a number inside
Possibility to change the type
No possibility to change/choose icon

#243


.NET Core / .NET Stard support

It looks like the versions that support .NET Core have been in alpha for more than a year.
Is there any plan to release them as stable versions?

We'll promote the release as stable once we're confident in the stability. Since the release includes lots of changes, we want to be careful with this one. I'd recommend trying out the alpha and reporting bugs/feedback with it.


Amplify App Missing, Tried redeploying but domain setup says domain already associated with different app

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
No response
Region
us-east-2
Amplify Hosting feature
No response
Describe the bug
We had a an amplify app up and running for many months, but the app is now missing from our list of amplify apps on console ('m sure I'm looking at the right regions,tried switching regions too). The site was live and working but no new changes were being pushed. Tried fetching using the aws cli too, but this app is missing.
I tired making a new amplify app from the same github repo and delete the old s3 records and set up new ones. I made the new app without any issues, but while I configure the domain I get this error
Create domain association failed One or more domains requested are already associated with another Amplify app: (domain names...)
Is there any way to hard reset this or free up this some other way? Can I get a list of all my amplify apps globaly(I checked different regions and can't find it anywhere but still I'd like to check)? I am fine with redeploying the app again, how can I get my domain freed up from amplify again?
Expected behavior
Amply app correctly displayed in app list in amplify consose
Reproduction steps
Nil
Build Settings
No response
Additional information
No response

Hi @incepthink can you please share your account ID or current app ID so we can further investigate this behavior?

Closing due to no response. Please re-open if you are running into this issue still.


room_temp_api_timeout not working

I’m using an external temperature sensor to set the current room temperature using the service ‘set_api_room_temperature’. This works, but after one minute, the temperature is set back to the internal temperature sensor, despite the timeout has not passed.

Tested with AC off and in heating mode with:
globals:

id: room_temp_api_timeout
type: int
restore_value: no
initial_value: "1800"

MhiAcCtrl:
  id: ${mhi_device_id}
  frame_size: ${frame_size}
  room_temp_timeout: 1800

add room_temp_timeout in MhiAcCtrl section in your yaml:
MhiAcCtrl:
  id: ${mhi_device_id}
  frame_size: ${frame_size}
  room_temp_timeout: 1800

Thanks!
This resolved the issue for me.

Added to the example.yaml: https://github.com/ginkage/MHI-AC-Ctrl-ESPHome/commit/309cd34828d0e55a7cfbcb62c637b5569f2ff8a3


Get-DbaBackupHistory is whack again - Cannot convert object to decimal

Is this:
Just place "x" to indicate selection (e.g. "[x]")

[ ] feature
[x] bug:

Details
Current dev branch
PS C:\github\dbatools> Test-DbaLastBackup -SqlInstance $instance | Out-GridView
Could not compare "39000000018400001" to "40000000002400001<PHONE_NUMBER>2400001<PHONE_NUMBER>2400001". Error: "Cannot convert the "System.Object[]" value of type
"System.Object[]" to type "System.Decimal"."
At line:248 char:10
+ ...         if ($DiffDb.LastLsn -gt $Fulldb.LastLsn -and  $DiffDb.Databas ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : ComparisonFailure

Get-DbaBackupHistory : Cannot process argument transformation on parameter 'LastLsn'. Cannot convert null to type "System.Numerics.BigInteger".
At line:261 char:130
+ ...  $db -raw:$raw -DeviceType $DeviceType -LastLsn $TLogstartLSN | Where ...

Unsure if this is Test-DbaLastbackup's fault but I think it hasn't been modified much

null lastlsn ?!?!?!?

can't replicate. is that sql2016 on your lab ?

This was on my lil laptop which is configured the same as the appveyor. Let me create a test real quick.

Excellent news - was a totally isolated incident!


Filter Failed - Dell P713 Printer

I am attempting to use a Dell P713 Printer on Ubuntu. I receive an error - "Filter failed".
The diagnostic output is attached.
troubleshoot.txt
Partial output from the error_log file is as follows:
D [22/Jul/2017:21:19:27 -0500] cupsdMarkDirty(----S)
D [22/Jul/2017:21:19:27 -0500] cupsdSetBusyState: newbusy="Active clients and dirty files", busy="Active clients and dirty files"
D [22/Jul/2017:21:19:27 -0500] [Client 1697] Returning IPP successful-ok for Cancel-Subscription (/) from localhost
D [22/Jul/2017:21:19:27 -0500] [Client 1697] Content-Length: 75
D [22/Jul/2017:21:19:27 -0500] [Client 1697] cupsdSendHeader: code=200, type="application/ipp", auth_type=0
D [22/Jul/2017:21:19:27 -0500] [Client 1697] con->http=0x5574f223f7a0
D [22/Jul/2017:21:19:27 -0500] [Client 1697] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=75, response=0x5574f2157790(IPP_STATE_DATA), pipe_pid=0, file=-1
D [22/Jul/2017:21:19:27 -0500] [Client 1697] Writing IPP response, ipp_state=IPP_STATE_DATA, old wused=0, new wused=0
D [22/Jul/2017:21:19:27 -0500] [Client 1697] bytes=0, http_state=0, data_remaining=75
D [22/Jul/2017:21:19:27 -0500] [Client 1697] Flushing write buffer.
D [22/Jul/2017:21:19:27 -0500] [Client 1697] New state is HTTP_STATE_WAITING
D [22/Jul/2017:21:19:27 -0500] [Client 1697] Waiting for request.
D [22/Jul/2017:21:19:27 -0500] cupsdSetBusyState: newbusy="Dirty files", busy="Active clients and dirty files"
I [22/Jul/2017:21:19:28 -0500] Expiring subscriptions...
I [22/Jul/2017:21:19:52 -0500] Saving subscriptions.conf...
D [22/Jul/2017:21:19:52 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Dirty files"
I [22/Jul/2017:21:19:52 -0500] Expiring subscriptions...
D [22/Jul/2017:21:19:52 -0500] Report: clients=15
D [22/Jul/2017:21:19:52 -0500] Report: jobs=1
D [22/Jul/2017:21:19:52 -0500] Report: jobs-active=1
D [22/Jul/2017:21:19:52 -0500] Report: printers=1
D [22/Jul/2017:21:19:52 -0500] Report: stringpool-string-count=32649
D [22/Jul/2017:21:19:52 -0500] Report: stringpool-alloc-bytes=17504
D [22/Jul/2017:21:19:52 -0500] Report: stringpool-total-bytes=546800
D [22/Jul/2017:21:20:05 -0500] [Client 1704] Accepted from localhost (Domain)
D [22/Jul/2017:21:20:05 -0500] [Client 1704] Waiting for request.
I [22/Jul/2017:21:20:05 -0500] Expiring subscriptions...
D [22/Jul/2017:21:20:05 -0500] [Job 22] Unloading...
D [22/Jul/2017:21:20:05 -0500] [Client 1704] POST / HTTP/1.1
D [22/Jul/2017:21:20:05 -0500] cupsdSetBusyState: newbusy="Active clients", busy="Not busy"
D [22/Jul/2017:21:20:05 -0500] [Client 1704] Read: status=200
D [22/Jul/2017:21:20:05 -0500] [Client 1704] No authentication data provided.
D [22/Jul/2017:21:20:05 -0500] [Client 1704] 2.0 Get-Printer-Attributes 1452
D [22/Jul/2017:21:20:05 -0500] Get-Printer-Attributes ipp://localhost/printers/Dell%5FP713w
D [22/Jul/2017:21:20:05 -0500] [Client 1704] Returning IPP successful-ok for Get-Printer-Attributes (ipp://localhost/printers/Dell%5FP713w) from localhost
D [22/Jul/2017:21:20:05 -0500] [Client 1704] Content-Length: 12920
D [22/Jul/2017:21:20:05 -0500] [Client 1704] cupsdSendHeader: code=200, type="application/ipp", auth_type=0
D [22/Jul/2017:21:20:05 -0500] [Client 1704] con->http=0x5574f2247f40
D [22/Jul/2017:21:20:05 -0500] [Client 1704] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=12920, response=0x5574f20b7770(IPP_STATE_DATA), pipe_pid=0, file=-1
D [22/Jul/2017:21:20:05 -0500] [Client 1704] Writing IPP response, ipp_state=IPP_STATE_DATA, old wused=0, new wused=0
D [22/Jul/2017:21:20:05 -0500] [Client 1704] bytes=0, http_state=0, data_remaining=12920
D [22/Jul/2017:21:20:05 -0500] [Client 1704] Flushing write buffer.
D [22/Jul/2017:21:20:05 -0500] [Client 1704] New state is HTTP_STATE_WAITING
D [22/Jul/2017:21:20:05 -0500] [Client 1704] Waiting for request.
D [22/Jul/2017:21:20:05 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
I [22/Jul/2017:21:20:06 -0500] Expiring subscriptions...
I [22/Jul/2017:21:20:09 -0500] Expiring subscriptions...
D [22/Jul/2017:21:20:09 -0500] Closing client 1010 after 300 seconds of inactivity.
D [22/Jul/2017:21:20:09 -0500] [Client 1010] Closing connection.
D [22/Jul/2017:21:20:09 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:20:16 -0500] [Client 1705] Accepted from localhost:44196 (IPv4)
D [22/Jul/2017:21:20:16 -0500] [Client 1705] Waiting for request.
I [22/Jul/2017:21:20:16 -0500] Expiring subscriptions...
D [22/Jul/2017:21:20:16 -0500] cupsdAddCert: Adding certificate for PID 0
I [22/Jul/2017:21:20:17 -0500] Expiring subscriptions...
I [22/Jul/2017:21:20:20 -0500] Expiring subscriptions...
D [22/Jul/2017:21:20:20 -0500] Closing client 1577 after 300 seconds of inactivity.
D [22/Jul/2017:21:20:20 -0500] [Client 1577] Closing connection.
D [22/Jul/2017:21:20:20 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:20:21 -0500] [Client 1705] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [22/Jul/2017:21:20:21 -0500] [Client 1705] Closing connection.
D [22/Jul/2017:21:20:21 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
I [22/Jul/2017:21:20:21 -0500] Expiring subscriptions...
I [22/Jul/2017:21:20:22 -0500] Expiring subscriptions...
I [22/Jul/2017:21:20:43 -0500] Expiring subscriptions...
D [22/Jul/2017:21:20:43 -0500] Closing client 1603 after 300 seconds of inactivity.
D [22/Jul/2017:21:20:43 -0500] [Client 1603] Closing connection.
D [22/Jul/2017:21:20:43 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:23:17 -0500] [Client 1704] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [22/Jul/2017:21:23:17 -0500] [Client 1704] Closing connection.
D [22/Jul/2017:21:23:17 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
I [22/Jul/2017:21:23:17 -0500] Expiring subscriptions...
D [22/Jul/2017:21:23:17 -0500] Report: clients=12
D [22/Jul/2017:21:23:17 -0500] Report: jobs=1
D [22/Jul/2017:21:23:17 -0500] Report: jobs-active=1
D [22/Jul/2017:21:23:17 -0500] Report: printers=1
D [22/Jul/2017:21:23:17 -0500] Report: stringpool-string-count=32600
D [22/Jul/2017:21:23:17 -0500] Report: stringpool-alloc-bytes=16584
D [22/Jul/2017:21:23:17 -0500] Report: stringpool-total-bytes=545704
D [22/Jul/2017:21:23:17 -0500] [Client 1699] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [22/Jul/2017:21:23:17 -0500] [Client 1699] Closing connection.
D [22/Jul/2017:21:23:17 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:23:17 -0500] [Client 1693] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [22/Jul/2017:21:23:17 -0500] [Client 1693] Closing connection.
D [22/Jul/2017:21:23:17 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:23:17 -0500] [Client 1691] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [22/Jul/2017:21:23:17 -0500] [Client 1691] Closing connection.
D [22/Jul/2017:21:23:17 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:23:17 -0500] [Client 1688] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [22/Jul/2017:21:23:17 -0500] [Client 1688] Closing connection.
D [22/Jul/2017:21:23:17 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:23:17 -0500] [Client 1687] HTTP_STATE_WAITING Closing for error 32 (Broken pipe)
D [22/Jul/2017:21:23:17 -0500] [Client 1687] Closing connection.
D [22/Jul/2017:21:23:17 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
I [22/Jul/2017:21:23:18 -0500] Expiring subscriptions...
I [22/Jul/2017:21:23:43 -0500] Expiring subscriptions...
D [22/Jul/2017:21:23:43 -0500] Closing client 700 after 300 seconds of inactivity.
D [22/Jul/2017:21:23:43 -0500] [Client 700] Closing connection.
D [22/Jul/2017:21:23:43 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:23:43 -0500] Closing client 701 after 300 seconds of inactivity.
D [22/Jul/2017:21:23:43 -0500] [Client 701] Closing connection.
D [22/Jul/2017:21:23:43 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:23:43 -0500] Closing client 737 after 300 seconds of inactivity.
D [22/Jul/2017:21:23:43 -0500] [Client 737] Closing connection.
D [22/Jul/2017:21:23:43 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
I [22/Jul/2017:21:23:50 -0500] Expiring subscriptions...
D [22/Jul/2017:21:23:50 -0500] Closing client 1684 after 300 seconds of inactivity.
D [22/Jul/2017:21:23:50 -0500] [Client 1684] Closing connection.
D [22/Jul/2017:21:23:50 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
I [22/Jul/2017:21:23:51 -0500] Expiring subscriptions...
D [22/Jul/2017:21:23:51 -0500] Closing client 658 after 300 seconds of inactivity.
D [22/Jul/2017:21:23:51 -0500] [Client 658] Closing connection.
D [22/Jul/2017:21:23:51 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:23:51 -0500] Closing client 686 after 300 seconds of inactivity.
D [22/Jul/2017:21:23:51 -0500] [Client 686] Closing connection.
D [22/Jul/2017:21:23:51 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
I [22/Jul/2017:21:24:28 -0500] Expiring subscriptions...
D [22/Jul/2017:21:24:28 -0500] Closing client 1697 after 300 seconds of inactivity.
D [22/Jul/2017:21:24:28 -0500] [Client 1697] Closing connection.
D [22/Jul/2017:21:24:28 -0500] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [22/Jul/2017:21:24:28 -0500] Report: clients=0
D [22/Jul/2017:21:24:28 -0500] Report: jobs=1
D [22/Jul/2017:21:24:28 -0500] Report: jobs-active=1
D [22/Jul/2017:21:24:28 -0500] Report: printers=1
D [22/Jul/2017:21:24:28 -0500] Report: stringpool-string-count=32578
D [22/Jul/2017:21:24:28 -0500] Report: stringpool-alloc-bytes=16520
D [22/Jul/2017:21:24:28 -0500] Report: stringpool-total-bytes=545176````

Any help would be appreciated. I am using CUPS 2.1.3. Thanks.

The troubleshoot.txt file points to a third-party driver issue; I'd check with the OpenPrinting folks to see if this is one of their drivers...


Set configured resource attributes during export

The OpenTelemetry SDK can have resource attributes configured during setup, these should be exported as tags too. This includes setting a consistent process / application name.
Fixes #5.

I've set the repo to always squash and merge when accepting any PR so it happen automatically 👍


[rancher-abs][HA] Fail to switch the volume from one host to another host.

Rancher versions:
rancher/server:1.6.7
catalog: https://github.com/thxCode/rancher-catalog.git
branch: aliyun-bs
network: VPC
Steps to Reproduce:

Launch rancher-abs service.
Add two hosts agent1 and agent2.
Launch wordpress catalog.
Three services of wordpress deploy on this two host randomly.
Upgrade agent2 and add a volume in mariadb service.
Disk create, attach and mount successfully.
Delete agent2.

Results:

Mariadb launch fail because it cannot find its volume.

Expectation

All the services of wordpress switch to agent1 and launch normally.
Volume switch from agent2 to agent1.

@yasker  @thxCode
#9194

Only abs shows this problem, ebs is normal.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Installing dev dependencies takes forever. [APE-814]

As per the contributing.md file, running the following takes forever:
pip install -e .'[dev]'

Here is the tail of the output before hanging (> 1hour):
INFO: pip is looking at multiple versions of coverage[toml] to determine which version is compatible with other requirements. This could take a while.
  Using cached coverage-7.0.2-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (224 kB)
  Using cached coverage-7.0.1-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (216 kB)
  Using cached coverage-7.0.0-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (215 kB)
  Using cached coverage-6.5.0-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (213 kB)
  Using cached coverage-6.4.4-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (212 kB)
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. See https://pip.pypa.io/warnings/backtracking for guidance. If you want to abort this run, press Ctrl + C.
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. See https://pip.pypa.io/warnings/backtracking for guidance. If you want to abort this run, press Ctrl + C.
  Using cached coverage-6.4.3-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (212 kB)
  Using cached coverage-6.4.2-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (212 kB)
  Using cached coverage-6.4.1-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (212 kB)
  Using cached coverage-6.4-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (211 kB)
  Using cached coverage-6.3.3-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (211 kB)
  Using cached coverage-6.3.2-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (211 kB)
  Using cached coverage-6.3.1-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (210 kB)
  Using cached coverage-6.3-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (210 kB)
  Using cached coverage-6.2-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (215 kB)
  Using cached coverage-6.1.2-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (215 kB)
  Using cached coverage-6.1.1-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (215 kB)
  Using cached coverage-6.1-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (214 kB)
  Using cached coverage-6.0.2-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (255 kB)
  Using cached coverage-6.0.1-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (254 kB)
  Using cached coverage-6.0-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (254 kB)
  Using cached coverage-5.5-cp310-cp310-manylinux1_x86_64.whl (238 kB)
Collecting toml
  Using cached toml-0.10.2-py2.py3-none-any.whl (16 kB)
Collecting coverage[toml]>=5.2.1
  Using cached coverage-5.4.tar.gz (687 kB)
  Preparing metadata (setup.py) ... done
  Using cached coverage-5.3.1.tar.gz (684 kB)
  Preparing metadata (setup.py) ... done
  Using cached coverage-5.3.tar.gz (693 kB)
  Preparing metadata (setup.py) ... done
  Using cached coverage-5.2.1.tar.gz (694 kB)
  Preparing metadata (setup.py) ... done
INFO: pip is looking at multiple versions of colorama to determine which version is compatible with other requirements. This could take a while.
Collecting colorama<0.5.0,>=0.4.1
  Using cached colorama-0.4.6-py2.py3-none-any.whl (25 kB)
  Using cached colorama-0.4.5-py2.py3-none-any.whl (16 kB)
  Using cached colorama-0.4.4-py2.py3-none-any.whl (16 kB)
  Using cached colorama-0.4.3-py2.py3-none-any.whl (15 kB)
  Using cached colorama-0.4.1-py2.py3-none-any.whl (15 kB)
INFO: pip is looking at multiple versions of click to determine which version is compatible with other requirements. This could take a while.
Collecting click>=8.0.0
  Using cached click-8.1.3-py3-none-any.whl (96 kB)
INFO: pip is looking at multiple versions of colorama to determine which version is compatible with other requirements. This could take a while.
INFO: pip is looking at multiple versions of charset-normalizer to determine which version is compatible with other requirements. This could take a while.
Collecting charset-normalizer<3.0.0,>=2.1.0
  Using cached charset_normalizer-2.1.1-py3-none-any.whl (39 kB)
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. See https://pip.pypa.io/warnings/backtracking for guidance. If you want to abort this run, press Ctrl + C.
  Using cached charset_normalizer-2.1.0-py3-none-any.whl (39 kB)

This is where it fails:
INFO: pip is looking at multiple versions of click to determine which version is compatible with other requirements. This could take a while.
  Using cached cfgv-3.3.0-py2.py3-none-any.whl (7.3 kB)
ERROR: Exception:
Traceback (most recent call last):
  File "/home/ygg/.local/lib/python3.10/site-packages/pip/_internal/cli/base_command.py", line 160, in exc_logging_wrapper
    status = run_func(*args)
  File "/home/ygg/.local/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", line 247, in wrapper
    return func(self, options, args)
  File "/home/ygg/.local/lib/python3.10/site-packages/pip/_internal/commands/install.py", line 400, in run
    requirement_set = resolver.resolve(
  File "/home/ygg/.local/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 92, in resolve
    result = self._result = resolver.resolve(
  File "/home/ygg/.local/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 481, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
  File "/home/ygg/.local/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 392, in resolve
    raise ResolutionTooDeep(max_rounds)
pip._vendor.resolvelib.resolvers.ResolutionTooDeep: 2000000

definitely make sure you update your version of pip when you encounter this error


lxing-oai/add-google-drive

added Google Drive cookbook
Summary
Briefly describe the changes and the goal of this PR. Make sure the PR title summarizes the changes effectively.
Motivation
Why are these changes necessary? How do they improve the cookbook?

For new content
When contributing new content, read through our contribution guidelines, and mark the following action items as completed:

[ ] I have added a new entry in registry.yaml (and, optionally, in authors.yaml) so that my content renders on the cookbook website.
[ ] I have conducted a self-review of my content based on the contribution guidelines:

[ ] Relevance: This content is related to building with OpenAI technologies and is useful to others.
[ ] Uniqueness: I have searched for related examples in the OpenAI Cookbook, and verified that my content offers new insights or unique information compared to existing documentation.
[ ] Spelling and Grammar: I have checked for spelling or grammatical mistakes.
[ ] Clarity: I have done a final read-through and verified that my submission is well-organized and easy to understand.
[ ] Correctness: The information I include is correct and all of my code executes successfully.
[ ] Completeness: I have explained everything fully, including all necessary references and citations.

We will rate each of these areas on a scale from 1 to 4, and will only accept contributions that score 3 or higher on all areas. Refer to our contribution guidelines for more details.

I've merged main in your branch to keep it up to date, make sure examples/chatgpt/gpt_actions_library/gpt_action_google_drive.ipynb is in the format you expected before merging, lgtm if you confirm, approving and I'll let you merge @lxing-oai


over fueled?

for some reason my fuel is way over the full mark. How would I go about fixing this?? at 65% it is on fuel.

what fuel system are you using? most likely the system doesnt respect your vehicles maximum fuel amount.

LegacyFuel

still having this issue and some cars the speedo just spins making it look like your doing 220+ when your doing 100

"in some cars", gonna need something to reproduce the issue with.

well its a constant with those vehicles is doing it on so not really sure how to reproduce it

well its a constant with those vehicles is doing it on so not really sure how to reproduce it

I literally made an account to comment on this lmao.
Maybe provide a link to the cars that happen to be doing it could possibly help? saying "those vehicles" still doesn't help

They are custom vehicles that I have created so id rather not
On Tue, Jul 28, 2020, 13:02 therealknight<EMAIL_ADDRESS>wrote:

well its a constant with those vehicles is doing it on so not really sure
how to reproduce it
I literally made an account to comment on this lmao.
Maybe provide a link to the cars that happen to be doing it could possibly
help? saying "those vehicles" still doesn't help
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Bluethefurry/SexySpeedometer-FiveM/issues/3#issuecomment-665189288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AILTDMSTFWD6TWCYH4GHI2DR54HBZANCNFSM4MZPZI7A
.

if you cannot provide something i can reproduce it then its a "wont fix", it works fine for everyone i've seen use it, reopen this issue if you can provide ZIP of resources/cars this issue occurs with.

well im not going to give you a model that i made... plus from what it seems on your closed tickets there is an issue with the fuel gauge

i can send you a video of it but i cannot send you the vehicle itself

if there is an issue with the fuel gauge, send a zip of an environment i can reproduce it with, a video is useless in such a case, if you cant provide something i can actually test it with, you might aswell not send anything.

Let see if any cars of gta5-mods does it
On Tue, Jul 28, 2020, 19:09 Blue<EMAIL_ADDRESS>wrote:

if there is an issue with the fuel gauge, send a zip of an environment i
can reproduce it with, a video is useless in such a case, if you cant
provide something i can actually test it with, you might aswell not send
anything.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Bluethefurry/SexySpeedometer-FiveM/issues/3#issuecomment-665356631,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AILTDMXJLXWOJ44OJ3QPG3LR55SD5ANCNFSM4MZPZI7A
.


TPI not updating Y at each iteration

This bug results in a failure of the model to satisfy the resource constraint.
There needs to be a statement Y=Ynew inside the TPI loop.

Fixed in PR #278


Compilation failure on AArch64 with DYNAMIC_ARCH=1

I've been testing compiling OpenBLAS on multiple architectures using the new GCC 7.1.0 release, and it looks like something has changed on AArch64.  Compilation of this line now fails with the following error message:
gcc -march=armv8-a -O2 -DMAX_STACK_ALLOC=2048 -Wall -DF_INTERFACE_GFORT -fPIC -DDYNAMIC_ARCH -DSMP_SERVER -DNO_WARMUP -DMAX_CPU_NUMBER=8 -march=armv8-a+crc+crypto+fp+simd -mtune=cortex-a57 -DASMNAME=dynamic -DASMFNAME=dynamic_ -DNAME=dynamic_ -DCNAME=dynamic -DCHAR_NAME=\"dynamic_\" -DCHAR_CNAME=\"dynamic\" -DNO_AFFINITY -I../.. -c dynamic.c -o dynamic.o
dynamic.c: In function 'support_avx':
dynamic.c:110:3: warning: implicit declaration of function 'cpuid' [-Wimplicit-function-declaration]
   cpuid(1, &eax, &ebx, &ecx, &edx);
   ^~~~~
dynamic.c:100:3: error: impossible constraint in 'asm'
   __asm__ __volatile__
   ^~~~~~~
Makefile:83: recipe for target 'dynamic.o' failed

Probably a silly question from me (again), but does this target support AVX ? Both the inline assembly and the call to cpuid() are in #ifndef NO_AVX blocks - perhaps something in the cpu detection code changed (or shows changed behaviour when compiled with gcc7) ?

@staticfloat Please let me know the command that you used to build.

dynamic.c is not compiled on aarch64. Maybe you are using x86 compiler on x86 platform?

Please let me know the command that you used to build.

I am building this within the julia source tree, but the eventual make invocation to OpenBLAS is:
make CC="gcc -march=armv8-a" FC="gfortran -march=armv8-a" RANLIB=ranlib FFLAGS="-O2 -fPIC" TARGET= BINARY= USE_THREAD=1 GEMM_MULTITHREADING_THRESHOLD=50 NUM_THREADS=8 NO_AFFINITY=1 DYNAMIC_ARCH=1 MAKE_NB_JOBS=0

dynamic.c is not compiled on aarch64. Maybe you are using x86 compiler on x86 platform?

Definitely not.  This is running on an AArch64 box, with a GCC 7.1.0 freshly compiled.  Running gcc -dumpmachine gives aarch64-unknown-linux-gnu.
It actually looks like this is due to us setting DYNAMIC_ARCH=1 on an AArch64 system.  Is that not allowed?

I just confirmed that compiling with GCC 6.3.0 has the same error, so this isn't anything new with GCC 7.

It should have no effect ideally, dynamic.c has only x86 codes so far.

Not sure if this is actually documented anywhere, but looking in Makefile.system the list of supported cpu cores for DYNAMIC_ARCH=1 is definitely x86-only. (Actually DYNAMIC_ARCH is supposed to be unset
there automatically if the list of DYNAMIC_CORES is empty, perhaps this does not work as expected ?)

Thanks for the tip @martin-frbg, I've opened a PR that works on my machine: https://github.com/xianyi/OpenBLAS/pull/1176

Thanks for the PR - neat trick to print the settings, but did you check that setting DYNAMIC_ARCH to zero is safe (i.e. that there is no place that has ifndef DYNAMIC_ARCH) ?

No, all I did was compile it to make sure it gets all the way through.
$ grep -E 'ifn?def' -R . | grep DYNAMIC_ARCH
./common_q.h:#ifndef DYNAMIC_ARCH
./common_param.h:#ifdef DYNAMIC_ARCH
./Makefile:#ifdef DYNAMIC_ARCH
./common_c.h:#ifndef DYNAMIC_ARCH
./common_d.h:#ifndef DYNAMIC_ARCH
./kernel/Makefile:#ifdef DYNAMIC_ARCH
./driver/others/openblas_get_config.c:#ifdef DYNAMIC_ARCH
./driver/others/openblas_get_config.c:#ifndef DYNAMIC_ARCH
./driver/others/openblas_get_config.c:#ifdef DYNAMIC_ARCH
./driver/others/openblas_get_config.c:#ifndef DYNAMIC_ARCH
./driver/others/openblas_get_config.c:#ifndef DYNAMIC_ARCH
./driver/others/memory.c:#ifdef DYNAMIC_ARCH
./driver/others/memory.c:#ifdef DYNAMIC_ARCH
./driver/others/memory.c:#ifndef DYNAMIC_ARCH
./driver/others/memory.c:#ifdef DYNAMIC_ARCH
./driver/others/memory.c:#ifdef DYNAMIC_ARCH
./driver/others/memory.c:#ifdef DYNAMIC_ARCH
./common_x.h:#ifndef DYNAMIC_ARCH
./common_z.h:#ifndef DYNAMIC_ARCH
./common_s.h:#ifndef DYNAMIC_ARCH

Looks like there's quite a few instances of that within C code, but within the Makefiles they're all commented out.  (I had to do a few double-takes to realize that #ifdef DYNAMIC_ARCH in a Makefile doesn't actually do anything)

I verified that using override DYNAMIC_ARCH= works as well, so I changed it to do that instead.


Extract all codesandbox component examples on an unique repository.

Describe the bug
Due to the large number of codesanbox component examples, it is necessary to extract all these examples of component states into a single repository.
This way, it will be easier to maintain for future versions of the cdk.

All examples extracted here: https://github.com/mawelCaballero/halstack-angular-boiler-plate


added fixtures for various cars collected on github/discord

Citigo iV, Octavia iV and Superb
my_favorite_car.yaml renamed to kodiaq_2024_ps7d6z_exclusive.yaml

Yes I was asked to commit those as vehicle owners are not experienced with GIT


Chore(FDS-355) ViewConfigWarning: React does not recognize the isEditable prop on a DOM element.

To get this warning in cosmos, I copied the values we get from CC and pass it as param in Cosmos.
New Component Checklist

[-] Includes unit tests for ALL required FDS use cases
[-] Does not mute any top level API props in React
[-] Includes an explanation for any changes to Jest snapshots (should be a PR tag automatically added if this happens)
[-] Component uses React.forwardRef() when a single DOM node is returned, AND it makes React-sense to access that DOM node

Warnings

:warning:
Please assign someone to merge this PR, and optionally include people who should review.

  Generated by :no_entry_sign: dangerJS against a2ea24efb81f9deb3898dc02581f8af3d4cd5dfd


[tracking] Developer/debugging workflows

Accessible options to:

[ ] Disable verifier
[ ] Enable IR printing
[ ] #136
[ ] Add asserts for weird types like i1
[ ] Add a project wide NDEBUG setting that gates possibly expensive and exhaustive Python asserts
[ ] Add options to enable debug logging of import phases (i.e. to jittable.py)
[ ] Preserve Python level stack traces in jittable.py (currently is getting proxy_tensor.py and needs to use some PyTorch utility to wrap properly)

Hi @dan-garvey, I'm working on clearing up the stale issues in Turbine and Torch-MLIR. Just wanted to confirm, if this issue is still relevant or not.


ctc decode problem

Hi @yenmeng ,
Many thanks for finding and addressing this issue.
The fix LGTM, thanks!


[Bug]: Taunt not work with MythicMobs

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

Here is my current skill, i also enable ThreatTable in every Mythicmobs's mobs but not working, please check
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- Server Software:
- ProSkillAPI Version:
- ProMCCore Version:
- Plugins:

latest.log
No response
Anything else?
No response

I'm a little confused at how this should work. When a MythicMobs mob gets damaged, it will target the player anyway, so why are you trying to taunt the entity when it gets damaged? It should be targeting the player either way.

You didn't set the skill up correctly. I tested taunt and vanilla mobs and mythicmobs, it works perfect. Here's an example skill you can test. https://pastebin.com/mNkQQ5Tv


[Bug Report] OSError: Unable to open file (file signature not found)

Looking forward to your replay, When i tried to download the data medium-replay, I got the error: File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "h5py/h5f.pyx", line 78, in h5py.h5f.open
OSError: Unable to open file (file signature not found)
I can't solve this error.Thanks for your help!

i got the same error.  Have you solved it ?

我也遇到差不多的问题了

how to slove it?


Update documentation with user-agent override

Changing the user-agent string was added in PR #63. This should be added to the README.

Note: It is not a user-agent override, but the option to add a user agent. So instead of sending "profitbricks-sdk-python/4.1.0", you can send "client-app/1.2 profitbricks-sdk-python/4.1.0" instead.


Dynamic color resets after opening different playlist

Hello,
when I use the Dynamic theme with Atmosphere (Best) mode and click into another playlist it resets to a grey color.

 I have to start another song so the dynamic theme reacts.
If I use any other mode like Average of Colors or Dark/Light Vibrant, this behaviour doesn't occur.
Is this normal for the Atmosphere mode?
Thanks

PS: My config:

I tried installing it via Marketplace and the Powershell script.

Nord Spotify Changes color when the cover art changes. Song change, page change such as switching to a diff playlist page can cause the cover art to change. If the cover art chagnes dynamic color changes.
This bug occurs in Made for You playlists, as the cover art for made for you playlist's are in diff format, Atmosphere mode is not supported its not fixable as thats how spotify intended to format those cover arts. So all modes except Atmosphere can work with Made for You playlists
https://user-images.githubusercontent.com/75513645/211516886-4db9da7d-ccac-4985-8ee7-64a5fa1350bd.mp4

JulienMaille's dribbblish-dynamic-theme and spicetify-dynamic-theme dont have those bugs as they just use spotify's default color extraction method. but Nord Spotify's Atmosphere mode gets accurate colors from a API request where only user, playlist, song cover art are supported (no support for made for you, radio).
Use this option to disable cover art while page change


Master detail relations details doesnt show all columns

I embedded master detail relation in my ServiceRow as below
 [DisplayName("Details"), MasterDetailRelation(foreignKey: "ServiceId", MasterKeyField = "Id"), NotMapped]
        public List<ServiceItemsRow> SerServiceItems
        {
            get { return Fields.SerServiceItems[this]; }
            set { Fields.SerServiceItems[this] = value; }
        }

In a details  section of ServiceRow form it shows all direct column of ServiceItems row, but not a derived columns (View field / columns from other tables linked with foreign key)
Based on belwo three columns in ServiceRow
  [DisplayName("Seq No"), NotNull]
        public Int32? SeqNo
        {
            get { return Fields.SeqNo[this]; }
            set { Fields.SeqNo[this] = value; }
        }

        [DisplayName("Service"), NotNull, ForeignKey("[dbo].[Service]", "Id"), LeftJoin("jService"), TextualField("ServiceName")]
        public Int32? ServiceId
        {
            get { return Fields.ServiceId[this]; }
            set { Fields.ServiceId[this] = value; }
        }

        [DisplayName("Service Name"), Expression("jService.[ServiceName]")]
        public String ServiceName
        {
            get { return Fields.ServiceName[this]; }
            set { Fields.ServiceName[this] = value; }
        }

It Shows SeqNo, ServiceId, But it shows blank in Service Name
Its not a column present in ServiceItems Table, rather Its View Field based on foreign key linking (i.e based on service ID)

put [MinSelectLevel(SelectLevel.List)] on ServiceName field in Row.cs

Read the guide

Also helpful: https://serenity.is/docs/tutorials/movies/the_cast_and_characters_they_played (Resolving Empty Actor/Actress Column Problem).


updated joi to version 12

Closes #38
A test is not passing, but since it was not passing before I guess this is normal
That's a small pull request, but well, I saw an issue...
It's an occasion for me to thank you for your work, celebrate is great :smile:

Thanks for the PR!
This issue tells you what changed and why the test failed. The escaping of HTML characters. What do you want to do here @cjihrig? We could fix this and just pass in escapeHtml to make the tests pass or some other option I'm not thinking of...

If possible, I think we should maintain the previous behavior in celebrate.

So @giltho use the escapeHtml option when we call Joi.validate and then the tests should pass. It should also be possible for users to set that value to false if they really want it disabled.

Indeed, this should be better, I also added this in the docs, since it is a divergence with Joi

I created a default object to which one can easily add properties if it is decided to add more default values that diverge from Joi in the future

Now that I'm looking at this... we are already escaping html with the EscapeHtml library... curious if we need both that lib and the Joi escape HTML?

No, we probably don't need both.

How come the test would not pass when I did not use Joi's option ?

Celebrate only uses EscapeHtml to escape paths, which is why the error message that appears in the test was not escaped. However, Joi's escapeHtml option seems to escape some error messages but not paths. It looks like both are not doing the same Job.
I think you can chose to either keep it that way, or escape the whole error with EscapeHtml module.

Thanks for the PR!


More frequent releases for core astropy

Blocked by:

[ ] Stakeholder surveys (see comments)
[ ] #97

Suggested by: @eteq
Expanded by: @pllim (feel free to edit if I got things wrong)
Motivations:

Lower the stakes if a high-priority PR or a killer feature did not make the current release deadline; i.e., users do not have to wait as long as 6 months to get them in the next release.
More frequent deadlines for contributors and maintainers who are primarily motivated by deadlines; i.e., instead of a big spike on feature freeze week, we turn it into smaller but more frequent spikes.

Possible new cadence (currently every 6 months):

Every month.
Every 2 months.
Every 3 months.

Requires:

Changes to APE 2.
Changes to core astropy release calendar.
Partial automation of the release process (see Risks).

Risks:

Increased burden for release manager. -- Can be partially solved by automation of the process.
Increased cadence lowering the importance of a feature freeze, encouraging inaction; e.g., "Oh, I can just wait till the next one."
The perception that we are "turning into pytest" with frequent releases and scaring pipeline people, who value stable packages.
Added effort on downstream packages and/or OS packagers to test the release candidate. (See https://github.com/astropy/project/issues/95#issuecomment-628775375)

See Also
#96

I would be in favor of this but only if we are willing to embrace a significant level of automation in releases.

Big :+1: from my own perspective, and I definitely feel the 6-month wait is a real driver for the "I really want to push this last PR in" mentality. I don't think that risk 2 is very serious, especially if the new cadence is release per 3 months.
About pipeline people, they do have the option of LTS, or else just skipping intermediate releases. I know in my work we basically pin all packages until such time as we are ready to upgrade and do the appropriate testing.
Maybe adding to risks is added effort on downstream packages and/or OS packagers to test the release candidate.

Maybe adding to risks

@taldcroft , done!

3 months seems a good idea to reduce the peak of activity before a release, but I'm not sure about the impact on users. That means more versions to test and "validate" to make sure there is no regressions, and there can be a fear to upgrade because a the breaking changes. So this could cause more users to stay on the LTS version to avoid too frequent upgrades ?
One option could be to have LTS versions every year instead of two years, and see intermediate releases as "unstable" ones, or more developer oriented. But that would mean more backporting work as well.
It could useful to make a survey on the mailing list ?

I think an LTS has to be available for more than a year. Unless we want to have multiple LTS versions around at he same time, we should not increase the LTS frequency.
I'm not sure how users upgrade astropy currently. For my non-development work, I typically make either (a) a new conda environment with current released versions of all packages that I anticipate using (i.e. I don't pin versions, so I just get the most recent ones) or (b) I reuse a some existing environment (i.e. an environment that I used for a previous project with similar requirements).
I think case (b) might be the most common. In that case, I only update astropy if I need a feature that I see in docs.astropy.org, but I don't have in my version or if I install some other package and conda or pip upgrade astropy for me.
Looking (in a non statistically representative way) at the co-workers in my group who are not developing code, workflow (b) is typical: Two examples: (1) CIAO (the Chandra analysis code) is released annually. People install CIAO and then put astropy into that environment and don't touch it again until the next CIAO is released. (2) I was recently asked why a certain example in the astropy docs did not work from them. It turned out that they were running astropy 1.0, which had all they needed (io.fits - I know users who don't use anything else from astropy and io.fits has not changed much in years).
I think the careful curation of versions and "users upgrading when a new version is available" is mostly limited to developers (who can deal with frequent releases) and curated institutional environments like instrument pipelines (that's what LTS is for).
So, this is to say: The astropy release schedule does not matter to most users and in fact more frequent releases might be slightly better, because users just get the "most recent" when they install.
I'm describing this in this much detail here because I think a survey on the mailing will get answers very biased towards developers/software interested people who behave different from the bulk of our users. Anecdotal evidence from more "typical" users around is is probably the best source for how "normal" users install and upgrade.
(Before you cry to educate me: My workflow is different to environments where I do development for astropy or some other package.)

Just to what I said before about automation - I think I would like to first see how we can make the current releases more automated, so that we get to the level of 'oh that was easy, why don't we do it more often', then consider changing the cadence :)

Yes, perhaps the automation part should be discussed separately in #97. I will update my post above to indicate that this is now blocked by #97.

About a survey, if it is posted to facebook / twitter we should get a more representative sample that includes typical astronomer users who are not devs.  Agreed that astropy-dev / astropy are skewed. Also agreed to make sure more frequent releases are feasible from the dev perspective before making any noise.

I'm -100 on having more frequent releases as it creates more problems than it solves while don't really provide much for the users either:

the same rush of half baked PRs will be pushed through on release day, no matter whether the cycle is 6month or 3 month long. PRs will be merged with the caveat last comment that the outstanding 2-3 review comments, and docs additions can be fixed in a follow-up PR, but given the impending feature freeze the PR has to be merged "right now". Call me sceptical, but this was always the case even though we have talked about it a lot on telecons and on meetings.

we supposed to move forward in the direction of having a coordinated package framework. This coordination currently is not automated, and while many parts of it could be automate up, the 3 month release cycle is a very short one in this regard.

RC testing is a significant endeavour. We cannot realistically expect our downstream and packagers to get it done in a few days, having multiple RC means a minimum of a month or more from FF to actual release. This can be cut back significantly, but only if the dev branch is well tested. That branch is only well tested if there isn't a huge rush of features prior the FF deadline. (One especially cannot expect a short RC cycle if PRs merged in the last minute are not even compatible with each other, as was the case in the 4.1 feature freeze).

building the release and pushing to pypi is the most minor part of making a release. following up threads (those "docs/fix to know bug in this shiny new feautre is coming in a follow-up PR") and getting decisions from maintainers is more significant, and cannot be automated.

Most users don't care about new releases, but very happily use year old versions. I don't see that providing a 3 month cycle would improve anything for them expect broadcasting the message that astropy is not stable. We could certainly do more bug fix releases, but that would require to focus on fixing bugs rather than adding new features.

Any surveys on twitter/facebook feels an extremely bad approach as the status of the cutting edge, backwards compatibility, etc are mostly relevant for developers, mostly developers of downstream libraries and packages and pipelines, and maybe admins of departmental servers, science platforms etc, and not the random but very vocal grad students and postdocs  are overwhelming the social media sample and who most probably have no insight or appreciation of a dev cycle of a large and complex library.

=========
Solutions:

Have regular work together days. These can imitate the team work feeling of the feature freeze days, while avoid any of the pitfalls of an actual feature freeze.
Have regular triage days. 5 maintainers sweeping through the issues and regularly close obsolete ones, and open bug fixes and most importantly do make decisions rather than postponing stating unsaid arguments would make wonders.
Have regular telecons. We are supposed to have them, but in practice we don't even have them doodled. We did have regular work together hours but it was very very poorly attended. Have a very concrete agenda, for an extremely well working example see the regular numpy calls.

==========
As for the release/FF I have a controversial approach in mind, but maybe some of you would like it. The real issue with the FF is not even the last minute rush. It's a problem, too see the conflicting merges and need for constant rebase on the last day. So the real issue is that hardly anything being merged at FF day had any chance to be tested downstream before branching out and making an RC. And that's a huge issue, as it's contradiction in our communication towards downstream packages where we ask them to test against master with the false promise that this is good practice to discover compatibility issues early and avoid the need for firefighting when the new astropy release is out.
So my suggestion is to have the branching day ~1month before FF. New features have the chance to be ported to the new branch if they are merged and tested before FF day. If they are not in that category, it means they'll be in the next release.
With this approach developers can deliver features for their own timelines and deadlines (see the spectralcoord case in 4.1) while ensuring that the release is not hold up due to the need of downstream testing and coordination. This approach would also remove the blanket policy that never really worked and was a source of large amount of frustration. I always felt very confident of merging a few very last minute PRs when I already saw that they are well tested, and also integrated downstream at the time the PR was opened, even if they've been a day late, while had no way to not include the rushed through ones that was knowingly causing troubles at the minute they are merged but nevertheless was merged to meet the deadline.
==
And to reiterate of how an ideal world of dev cycle would work, let's remember the case of last summer when both the big overhaul of modeling and large amount of improvements to units/table have been merged in the middle of the dev cycle in the summer, meaning that we neither cause any issues at release time but provided well tested new/reworked functionality. Let's aim to find a framework where this approach is valued by all maintainers to the level they are willing to follow it themselves.

I think if nothing else more frequent bug fix releases could be made feasible with at a minimum:

Better automation of releases--it should be possible to automatically cut a bug fix release directly from a CI pipeline when run on tags.  A successful CI build of a bugfix tag should result automatically in a release.

The above should include testing against affiliated packages--bugfix releases obviously should not break affiliated packages.

With such improvements in place it might be possible to extend this to other types of releases, but I would focus only on more frequent bugfix releases first.
Still making the above work reliably, while possible, will require a few non-trivial changes to the development process (some of which are good to do anyways, such as improving management of the changelog).  I am skeptical as to who exactly more frequent releases (without some specific institutional need) benefits.

Did you say change log? Please see astropy/astropy#10334 😉

I think what would definitely be beneficial is more frequent/automated bug fix releases - probably an easier place to start and clearer benefits.

Just in case you want to revisit the idea of GitHub Action, I stumbled upon https://github.com/pytest-dev/pytest/blob/master/scripts/release-on-comment.py 😉

Since this was opened, @astrofrog and @Cadair implemented automated release using Azure Pipeline. Not sure how relevant is this still.

Since this was opened, @astrofrog and @Cadair implemented automated release using Azure Pipeline. Not sure how relevant is this still.

Packaging up is still not the biggest burden for a release, but all the testing and downstream integration.

Packaging up is still not the biggest burden for a release, but all the testing and downstream integration.

Superseded by:

https://github.com/astropy/astropy-APEs/pull/82

I wouldn't say this is superseded, as even with APE 21 we could still have more frequent releases - in fact APE 2 already says that we can have more frequent releases if we agree to it.


chore(examples): remove redundant world spec

Feature or Problem

Remove the redundant world specification for wit-bindgen invocations. It's not necessary when there's only one world in the package
Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

Are we sure we want to do this? This is going to be worse for anyone looking at these to learn.
The fact that the world is auto-selected is not immediately obvious, but world: "..." makes it more explicit. We shouldn't depend on implicit functionality when someone completely new to the ecosystem might be showing up.

People completely new to the ecosystem are very unlikely to have more than one world defined in their WIT packages - it's an advanced feature and if anything, we should be steering developers away from it to avoid confusion.
In any case, these examples should not be using wit-bindgen at all - https://github.com/bytecodealliance/cargo-component is the official tool to build Rust components, especially for newcomers

In the interest of not holding up 1.0, we'll get this in and hopefully no one is confused by it


Enable type inference for ops with regions in Python bindings

This is currently explicitly disabled upstream. We could try enabling this and see what happens:
/// Returns true if the InferTypeOpInterface can be used to infer result types
/// of the given operation.
static bool hasInferTypeInterface(const Operator &op) {
  return op.getTrait("::mlir::InferTypeOpInterface::Trait") &&
         op.getNumRegions() == 0;
}

This is also part of the public API track, likely blocked on #32.


Properly playtest (G)ZDoom compatibility

See title. Wait until multiplayer exists, but for now test LAN.

Done


Fix multisite conditional in wordpress-site.conf

Essential fix. The conditional item.value.multisite always evaluates true, so this changes it to item.value.multisite.enabled.
Important fix. logs_root: /var/log/nginx/ plus error_log  {{ logs_root }}/error.log warn; yields double slash /var/log/nginx//error.log so I removed trailing slash from the logs_root variable, like how there is no trailing slash in www_root: /srv/www.
Aesthetic fix. (EDIT: this one removed; see comment below) With one combination of variable values, the wordpress-site.conf.j2 template produces this irregular indentation:
server {
    listen 443 ssl spdy;

  server_name  staging.example.com;
  access_log   /srv/www/example.com/logs/access.log;
  error_log    /srv/www/example.com/logs/error.log;

  root  /srv/www/example.com/current/web;
  index index.php;

  charset utf-8;

  rewrite ^/(wp-.*.php)$ /wp/$1 last;
      rewrite ^/(wp-(content|admin|includes)/.*) /wp/$1 last;
    include ssl.conf;
  include ssl-stapling.conf;
...

We can achieve perfect indentation by adding #jinja2: lstrip_blocks: True at the top of the template (discovered it after seeing trim_blocks setting here and here) and exchanging the various {%- stuff -%} with simply {% stuff %} (see whitespace control, ). It seems simpler but maybe there are arguments against this change.

I've revised the PR to omit the whitespace formatting changes (with the #jinja2: lstrip_blocks: True, etc.). The reason was that by removing indentation in the template, I made the templates less friendly to the developer, and templates are where the developer works. So, now I'm thinking of it like this: "Templates are to the conf files they create, as other source files are to uglified dist files they create."

:+1:


Stateless LSTM link

I need a stateless-LSTM link like GRU. Stateful-LSTM link makes a code simple, but it is difficult to generate a sequence with beam search because we need to store top-k states to a priority queue.
We also need to design consistency of names.

Stateful LSTM: links.LSTM
Stateless LSTM: new!
Stateful GRU: links.StatefulGRU
Stateless GRU: links.GRU

Adding the beam-search code too would also be nice! I'm not aware of any libraries that have it available.


[WIP] Fix issues with inline fragments

[x] Test case for #354
[x] Test case for #365
[ ] Find other failing situations
[ ] Fix those bugs

These would be much simpler to test here: https://github.com/apollostack/apollo-client/blob/master/test/roundtrip.ts
These tests basically just check that a query can travel through the store unchanged, which is what I think we are trying to do here.

@stubailo I'll try that, thanks!

Ok, now going into debug mode 🔴 ➡

I think this shouldn't be too hard to fix. Right now, src/writeSelectionSetToStore is called recursively on the entire document AST. The solution should consist of not running it recursively on stuff that's been skipped (e.g. skipped inline fragments).

Looks cool to me! I think the same issue (i.e. #355) will also apply to fragment spreads (i.e. anything we have to recurse on) because it will try to look for those fields as well even if they've been skipped.  Basically, we should only recurse in any capacity if the skip evaluates to false.

@Poincare & @stubailo : I'm not sure fragment spreads works in roundtrip.js. Is this normal ? Should I move the fragment spread tests elsewhere ?

@rricard You're right - it seems that named fragments don't currently work in roundtrip.ts. I've filed an issue about that at #361. In the meantime, we can just move those tests to test/QueryManager.ts, I think.

Or I could just try to fix #361 as well. I didn't get into any details but that doesn't seem to hard...

@Poincare, all done!

Maybe wait for #350 to be merged first. Rebasing this one will be "cheaper" than rebasing the other.

Looks great to me + ready to merge! I think holding off on merging until we have #350 sorted out makes sense.

WARNING: Rebased

Woohoo finally got this in!


Added basic chat pattern matching

Added example for adding chat patterns
Added fix for empty lines on signs crashing bots (bukkit servers)
Signed-off-by: Corgano<EMAIL_ADDRESS>

So only things missing :

adding chatAddPattern in the table of content of the doc (best way : doctoc doc/api.md in the console)
discription -> description


PXP-577: [CLI] Implement the command

Summary

Ticket: PXP-577
What's Changed

Added

[x] Add a new tui command to render TUI

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

I think we should remove the Header text from the layout. It should just be an empty pane at the beginning.
For other panes, I think the pane title should be like this

So that it will save some space in the pane

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan, onimsha
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


ProjectX Template Added

ProjectX Template Added
Pull Request
Contribution type

[ x] New template contribution
[ ] Existing template update
[ ] Issue fix
[ ] README.md update

Contribution Description

For consideration as part of EthDenver bounty. Template name: ProjectX.

[x ] I would like my template to be added to the Unstoppable Domains' website builder
Unstoppable Domain Name:
userzero.crypto

Hey,
Matias from Unstoppable Domains here.
Thanks for submitting a template!
We will be reviewing all pull requests this week.
Best,

I'd reccomend checking out 3Box for updating your form

I am closing this PR due to inactivity


auto check for dependencies

determine all dependencies for compiling and installation
update the install script to test for dependencies
if failure, output to user which dependencies are needed
only proceed on success

fedora
apt-get install build-essential npm git -y
centos
yum install git -y
yum groupinstall "Development Tools" -y
curl --silent --location https://rpm.nodesource.com/setup_7.x | bash -
yum install -y nodejs


PARQUET-1072: Build with ARROW_NO_DEPRECATED_API in Travis CI

Also fixes a number of Clang warnings and uses of deprecated API calls as of Arrow 0.6.0

Looks like I accidentally force pushed the wrong branch. I will restore the original patch for PARQUET-1072 when I can

@majetideepak does this look OK?

+1 LGTM apart from a minor suggestion.