[BUG] Managers Issue with Divisions

Describe the bug
To Reproduce
I think there may be some issues with leagues that use divisions. I'm seeing some strange behavior and not sure what is going on. I've only updated the managers page to be unique and added a few pictures. I've reverted back to the basic managers code and didn't update anything but adding 12 managers from 3 and still had the same issues.  I think they are all related to my league being broken out to divisions. Which is causing the trophies page not to load. In turn scrambling the data.
My trophies page is not properly loading. So, if I go to the trophy page, it will start loading and never finish. From there, any page you go to is inaccurate. It will show the names of managers that aren't right or standings or matchups for the wrong managers. However, one refresh of the page and that fixes it.  Any page you go to after the trophy page stalling. Will have a mix-up of the data. I showed two screenshots with description in title. I go to the before picture from the trophy page while it is loading. The data is wrong. I refresh, then the data is right.
If you go to the standings page after the trophy page is messed up and don't refresh before going to another page, the corresponding page will also be messed up. If you refresh the page to fix the data, then any page after that will be back on track until you go to the trophy page again. The trophy page loaded once for me, but that was it. Not sure why it isn't loading now. I haven't messed with any code outside of managers and pictures pages.
Your League ID
726145213692776448
Expected behavior
I would expect the manager(12) team to show the right picture.
I would expect all links to work the first time you click them versus needing a second screen refresh to pull accurately.
I would expect the standings to reflect the right team and right record.
I would expect the trophy page to load like the demo site.
Desktop (please complete the following information):

OS: windows 10
Browser chrome or safari
Version [e.g. 22] latest on both

Smartphone (please complete the following information):

Device: iphone 13 - OS: latest
Browser safari
Version latest

Additional context
I wasn't sure the best way to submit this issue and to explain it. So please feel free to look at my site directly. You can then see that the first time it loads versus when you refresh whatever page you are on is different.
https://league-page-woad-eta.vercel.app

/

Still been playing around with this trying to figure out what is going on. For reference. I created a whole new site. If I just put in league id. I get the same issue. Trophys(awards) never loads.

Sorry for the delay, looking into this shortly. Should be something minor

I fixed the trophy page bug in pr https://github.com/nmelhado/league-page/pull/102. I wasn't able to reproduce the managers bug locally though. Could you try updating and letting me know if you are still experiencing it?


Int search/filter resulting in no results.

Hello, I'm doing a search first by text and then a second search with same text by adding some number filters:
First search, results in a lot of results
{+(username:carlos address:carlos country:carlos description:carlos notes:carlos ) }
I then add a filter of userid = 1.
Tried first like a TextField:
 Query q = new TermQuery(new Term("userid", userid.Trim().ToLower()));
 booleanQuery.Add(q, Occur.MUST);
resulting in
{+(username:*carlos* address:*carlos* country:*carlos* description:*carlos* notes:*carlos* ) +usrid:1}

Then like a number range
int usrID = int.Parse(userid);
Query q = NumericRangeQuery.NewInt32Range("userid", usrID, usrID, true, true);
booleanQuery.Add(q, Occur.MUST);
resuing in
{+(username:*carlos* address:*carlos* country:*carlos* description:*carlos* notes:*carlos* ) +usrid:[1 TO 1]}

While indexing, these are the two approaches I took:
new Int32Field("userid", (int)(userID != null ? userID : 0), Field.Store.YES),
new TextField("userid",(userID != null ? userID.ToString() : ""), Field.Store.YES),

And for analyer, I'm using

IDictionary<string, Analyzer> customAnalyzerPerField = new Dictionary<string, Analyzer>();
customAnalyzerPerField ["userid"] = new StandardAnalyzer(LuceneVersion.LUCENE_48);
// also tried customAnalyzerPerField ["userid"] = new WhitespaceAnalyzer(LuceneVersion.LUCENE_48);

Any ideas on why its filtering to empty? (I checked DB and for that field there are a few rows that should match).

Checking while creating the index, and its saving for example this as a field of index document:
{stored,indexed,tokenized,omitNorms,indexOptions=DOCS_ONLY,numericType=INT32,numericPrecisionStep=4<userid:1>}

Are you seeing a difference in NumericRangeQuery behavior between 4.8.0-beta00016 and prior versions? We did make a few changes to it to avoid boxing. https://github.com/apache/lucenenet/pull/570/commits/2cae3c28001ff350a516635f33670581e8c58b85
I haven't spotted a problem with the query, but I noticed that there are different modes demonstrated in the NumericRangeQuery tests that you might want to experiment with.

Thanks both! I will check those links and test and use StackOverFlow in the future.
If that doesn't work I will provide a small sample code
Yes, the usrid was a typo here in the question.
Thanks!!

i've written a custom query parser for my cms
https://github.com/yohsii/puck-core/blob/master/core/PuckLucene/PuckQueryParser.cs
starting line 89 should handle your integer search

i've written a custom query parser for my cms https://github.com/yohsii/puck-core/blob/master/core/PuckLucene/PuckQueryParser.cs
starting line 89 should handle your integer search

worked like a charm

@diegolaz79 @yohsii
Do note that some cultures use alternate characters for the negative sign. So, for int. Parse() and long.Parse(), passing CultureInfo.InvariantCulture  may be required if the input may contain negative numbers that don't match the culture of the current thread.

@NightOwl888

Do note that some cultures use alternate characters for the negative sign. So, for int.Parse() and long.Parse(), passing CultureInfo.InvariantCulture may be required if the input may contain negative numbers that don't match the culture of the current thread.

Wouldn't you have to pass the CultureInfo for that culture in order for the Parse() method to correctly know how the negative number is represented?  Seems like CultureInfo.InvariantCulture wouldn't contain that info?


Could not find or load main class org.gradle.wrapper.GradleWrapperMain

I'm trying to run the example and I'm getting this error:
Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain

Nevermind, gladle folder was missing.


Button width and Icon Insets. Issues #17 and #18.

Fixing button width and added configurable Icon Insets.  Fixing minor changes for the new Swift version.

This would be useful! I have a suggestion though: Instead of a CGFloat property for the insets setting, why not use a UIEdgeInset, so you can customize all sides of the inset independently if you want?
Additionally, this isn't applying the insets to the hybrid types.

Sounds really good. Gives more control on how to display your segments. I'll have a look into it when I get my new MacBook charger back 🙈. The old one died 😭. Thanks for the suggestion by the way.
Sent from my iPhone

On Jun 29, 2016, at 2:11 PM, Daniel Burgess<EMAIL_ADDRESS>wrote:
This would be useful! I have a suggestion though: Instead of a CGFloat property for the insets setting, why not use a UIEdgeInset, so you can customize all sides of the inset independently if you want?
Additionally, this isn't applying the insets to the hybrid types.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Updated to Create 0.5.1

I decided to go through and update the dependencies and code for the mod to work with Create 0.5.1.b and above. I did a bit of testing and didn't find any immediately obvious issues or errors, which makes sense, as most changes were just semantic. I didn't do any major changes to any of the code, but major changes will be needed for future updates, as the addLayer function for Registrate is now deprecated

Thanks for the effort, unfortunately I already made an updated version, just for 1.18.2 branch
I should've done the same for 1.19.2 but I got too much other stuff to deal with 😭
If you want, you can make another PR, by merging/rebasing 1.18.2 updated branch on top of current 1.19.2 branch

Thanks for the effort @TonyGamer and @Lgmrszd ! I would love to see this on 1.19.2 soon. It's currently the only create addon mod to get compatibility with 5.1 in the pack I'm playing. (sorry for the pressure ;) )

Thanks for the effort, unfortunately I already made an updated version, just for 1.18.2 branch I should've done the same for 1.19.2 but I got too much other stuff to deal with 😭 If you want, you can make another PR, by merging/rebasing 1.18.2 updated branch on top of current 1.19.2 branch

I'll look into doing that. Shoulda checked a bit further before updating it all lol

Gotta close it as nee version is out already... But in any case, thanks for your effort, goes to show how important this mod is for some people 🙂


Setting index in PlayerContextProvider outside

In nextjs I have a page that displays the track list. Cassette is loaded in _app.tsx. How can I set the active index of the current playlist from  page/[playlist].tsx? I tried using the hooks npm but I receive a fatal error.

Could you please share the fatal error message you received and share the
relevant code you wrote in app.tsx and playlist.tsx ?
Le lun. 7 mars 2022 10 h 34 a.m., Steve @.***> a écrit :

In nextjs I have a page that displays the track list. Cassette is loaded
in _app.tsx. How can I set the active index of the current playlist from
page/[playlist].tsx? I tried using the hooks npm but I receive a fatal
error.
—
Reply to this email directly, view it on GitHub
https://github.com/benwiley4000/cassette/issues/480, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHOD3JHSNAVPBXVS6OLDQDU6YOWRANCNFSM5QDUPXNA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks for the help and quick reply!
This is without the hooks package.
_app.tsx
<PlayerContextProvider
            playlist={playlistTracks}
            onActiveTrackUpdate={(e) => console.log(e)}
            mediaElementRef={
              elem => {
                elem.addEventListener('timeupdate', (e) => console.log(e));
                elem.addEventListener('volumechange', (e) => console.log(e));
                elem.addEventListener('loadstart', (e) => console.log(e));
              }
            }
          >
            <MediaPlayerControls
              controls={[
                'backskip',
                'playpause',
                'forwardskip',
                'shuffle',
                'repeat',
                'volume',
                'progress'
              ]}
            />
          </PlayerContextProvider>

pages/playlist/[playlist].tsx
const handleListItemClick = (
    index: number,
    event: React.MouseEvent<HTMLDivElement, MouseEvent>,
    id: number,
    title: string,
    url: string
  ) => {
    setSelectedTrackIndex(index)
    setTrackIndex(index)
    //TODO: play song in cassette
  }

<List>
            {playlistTracks.map((track:any, index:number) => (
              <ListItem key={track.id} disablePadding>
                <ListItemButton
                  selected={selectedTrackIndex === index}
                  onClick={(event) => handleListItemClick(index, event, track.id, track.title, track.url)}
                >
                  {track.title}
                </ListItemButton>
              </ListItem>
            ))}
</List>

This is when using hooks.
pages/playlist/[playlist].tsx
import { useState } from 'react';
import Box from '@mui/material/Box'
import Container from '@mui/material/Container'
import List from '@mui/material/List'
import ListItem from '@mui/material/ListItem'
import ListItemButton from '@mui/material/ListItemButton'
import { usePlayerContext } from '@cassette/hooks'

const Playlist = ({playlistName, playlistTracks, setTrackIndex} : {playlistName:any, playlistTracks:any, setTrackIndex:any}) => {
  const [selectedTrackIndex, setSelectedTrackIndex] = useState(0)

  const handleListItemClick = (
    index: number,
    event: React.MouseEvent<HTMLDivElement, MouseEvent>,
    id: number,
    title: string,
    url: string
  ) => {
    setSelectedTrackIndex(index)
    //TODO: play song in cassette
    setTrackIndex(index)
  }

  function PlayerContextUser() {
    const { currentTime, paused, onTogglePause } = usePlayerContext([
      'currentTime',
      'paused',
      'onTogglePause'
    ]);

    return (
      <>

          The track is {paused ? 'paused' : 'playing'}. The time is {currentTime}.

        <button onClick={onTogglePause}>Toggle pause!</button>
      </>
    );
  }

  return (
    <>
      <Box
        component="main"
        sx={{
          backgroundColor: (theme) =>
            theme.palette.mode === 'light'
            ? theme.palette.grey[100]
            : theme.palette.grey[900],
          flexGrow: 1,
          height: '100vh',
          overflow: 'auto',
        }}
      >
        <Container
          maxWidth={false}
          sx={{ mt: 10 }}
        >

{playlistName}

          <PlayerContextUser />
          <List>
            {playlistTracks.map((track:any, index:number) => (
              <ListItem key={track.id} disablePadding>
                <ListItemButton
                  selected={selectedTrackIndex === index}
                  onClick={(event) => handleListItemClick(index, event, track.id, track.title, track.url)}
                >
                  {track.title}
                </ListItemButton>
              </ListItem>
            ))}
          </List>
        </Container>
      </Box>
    </>
  )
}

export default Playlist

On the frontend I get this error.
Unhandled Runtime Error
TypeError: Cannot read properties of null (reading 'hasOwnProperty')

pages\playlist[playlist].tsx (25:68) @ PlayerContextUser
function PlayerContextUser() {
> 25 |     const { currentTime, paused, onTogglePause } = usePlayerContext([
     |                                                                    ^
  26 |       'currentTime',
  27 |       'paused',
  28 |       'onTogglePause'

At a glance, it seems like you might not be rendering the
PlayerContextProvider high enough in your app. It doesn't need to be the
immediate parent of the MediaPlayerControls but it definitely does need to
be an ancestor of any part of the app that uses the playercontext. Is it
possible your list component does not have the PlayerContextProvider
ancestor? Otherwise we don't know what player context you're referring to.
Not sure if you're used to redux but it's kind of like the redux provider.
Usually you'd put it at the very top of your app, but if you have multiple
media players on the same page, then you would put it lower.
Does this help?
Le lun. 7 mars 2022 11 h 07 a.m., Steve @.***> a écrit :

Thanks for the help and quick reply!
This is without the hooks package.
_app.tsx
<PlayerContextProvider
playlist={playlistTracks}
onActiveTrackUpdate={(e) => console.log(e)}
mediaElementRef={
elem => {
elem.addEventListener('timeupdate', (e) => console.log(e));
elem.addEventListener('volumechange', (e) => console.log(e));
elem.addEventListener('loadstart', (e) => console.log(e));
}
}
>
<MediaPlayerControls
controls={[
'backskip',
'playpause',
'forwardskip',
'shuffle',
'repeat',
'volume',
'progress'
]}
/>

pages/playlist/[playlist].tsx
const handleListItemClick = (
index: number,
event: React.MouseEvent<HTMLDivElement, MouseEvent>,
id: number,
title: string,
url: string
) => {
setSelectedTrackIndex(index)
setTrackIndex(index)
//TODO: play song in cassette
}

            {playlistTracks.map((track:any, index:number) => (

 handleListItemClick(index, event, track.id, track.title, track.url)}
                >
                  {track.title}

            ))}

This is when using hooks.
pages/playlist/[playlist].tsx
import { useState } from 'react';
import Box from @./material/Box'
import Container from @./material/Container'
import List from @./material/List'
import ListItem from @./material/ListItem'
import ListItemButton from @./material/ListItemButton'
import { usePlayerContext } from @./hooks'
const Playlist = ({playlistName, playlistTracks, setTrackIndex} : {playlistName:any, playlistTracks:any, setTrackIndex:any}) => {
const [selectedTrackIndex, setSelectedTrackIndex] = useState(0)
const handleListItemClick = (
index: number,
event: React.MouseEvent<HTMLDivElement, MouseEvent>,
id: number,
title: string,
url: string
) => {
setSelectedTrackIndex(index)
//TODO: play song in cassette
setTrackIndex(index)
}
function PlayerContextUser() {
const { currentTime, paused, onTogglePause } = usePlayerContext([
'currentTime',
'paused',
'onTogglePause'
]);
return (
  <>

      The track is {paused ? 'paused' : 'playing'}. The time is {currentTime}.

    <button onClick={onTogglePause}>Toggle pause!</button>
  </>
);

}
return (
<>
<Box
component="main"
sx={{
backgroundColor: (theme) =>
theme.palette.mode === 'light'
? theme.palette.grey[100]
: theme.palette.grey[900],
flexGrow: 1,
height: '100vh',
overflow: 'auto',
}}
>
<Container
maxWidth={false}
sx={{ mt: 10 }}
>
{playlistName}

{playlistTracks.map((track:any, index:number) => (

<ListItemButton
selected={selectedTrackIndex === index}
onClick={(event) => handleListItemClick(index, event, track.id, track.title, track.url)}
>
{track.title}

))}

</>
)
}
export default Playlist
On the frontend I get this error.
Unhandled Runtime Error
TypeError: Cannot read properties of null (reading 'hasOwnProperty')
pages\playlist[playlist].tsx (25:68) @ PlayerContextUser
function PlayerContextUser() {

25 |     const { currentTime, paused, onTogglePause } = usePlayerContext([
|                                                                    ^
26 |       'currentTime',
27 |       'paused',
28 |       'onTogglePause'

—
Reply to this email directly, view it on GitHub
https://github.com/benwiley4000/cassette/issues/480#issuecomment-1060856911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHOD3LWMKJ6AAWPSX72ZXLU6YSVJANCNFSM5QDUPXNA
.
You are receiving this because you commented.Message ID:
@.***>

In case you're still stuck, it might help if you can share the full code of
your app.tsx component. Let me know.
Le lun. 7 mars 2022 11 h 14 a.m., Ben Wiley @.***> a
écrit :

At a glance, it seems like you might not be rendering the
PlayerContextProvider high enough in your app. It doesn't need to be the
immediate parent of the MediaPlayerControls but it definitely does need to
be an ancestor of any part of the app that uses the playercontext. Is it
possible your list component does not have the PlayerContextProvider
ancestor? Otherwise we don't know what player context you're referring to.
Not sure if you're used to redux but it's kind of like the redux provider.
Usually you'd put it at the very top of your app, but if you have multiple
media players on the same page, then you would put it lower.
Does this help?
Le lun. 7 mars 2022 11 h 07 a.m., Steve @.***> a
écrit :

Thanks for the help and quick reply!
This is without the hooks package.
_app.tsx
<PlayerContextProvider
playlist={playlistTracks}
onActiveTrackUpdate={(e) => console.log(e)}
mediaElementRef={
elem => {
elem.addEventListener('timeupdate', (e) => console.log(e));
elem.addEventListener('volumechange', (e) => console.log(e));
elem.addEventListener('loadstart', (e) => console.log(e));
}
}
>
<MediaPlayerControls
controls={[
'backskip',
'playpause',
'forwardskip',
'shuffle',
'repeat',
'volume',
'progress'
]}
/>

pages/playlist/[playlist].tsx
const handleListItemClick = (
index: number,
event: React.MouseEvent<HTMLDivElement, MouseEvent>,
id: number,
title: string,
url: string
) => {
setSelectedTrackIndex(index)
setTrackIndex(index)
//TODO: play song in cassette
}

            {playlistTracks.map((track:any, index:number) => (

 handleListItemClick(index, event, track.id, track.title, track.url)}
                >
                  {track.title}

            ))}

This is when using hooks.
pages/playlist/[playlist].tsx
import { useState } from 'react';
import Box from @./material/Box'
import Container from @./material/Container'
import List from @./material/List'
import ListItem from @./material/ListItem'
import ListItemButton from @./material/ListItemButton'
import { usePlayerContext } from @./hooks'
const Playlist = ({playlistName, playlistTracks, setTrackIndex} : {playlistName:any, playlistTracks:any, setTrackIndex:any}) => {
const [selectedTrackIndex, setSelectedTrackIndex] = useState(0)
const handleListItemClick = (
index: number,
event: React.MouseEvent<HTMLDivElement, MouseEvent>,
id: number,
title: string,
url: string
) => {
setSelectedTrackIndex(index)
//TODO: play song in cassette
setTrackIndex(index)
}
function PlayerContextUser() {
const { currentTime, paused, onTogglePause } = usePlayerContext([
'currentTime',
'paused',
'onTogglePause'
]);
return (
  <>

      The track is {paused ? 'paused' : 'playing'}. The time is {currentTime}.

    <button onClick={onTogglePause}>Toggle pause!</button>
  </>
);

}
return (
<>
<Box
component="main"
sx={{
backgroundColor: (theme) =>
theme.palette.mode === 'light'
? theme.palette.grey[100]
: theme.palette.grey[900],
flexGrow: 1,
height: '100vh',
overflow: 'auto',
}}
>
<Container
maxWidth={false}
sx={{ mt: 10 }}
>
{playlistName}

{playlistTracks.map((track:any, index:number) => (

<ListItemButton
selected={selectedTrackIndex === index}
onClick={(event) => handleListItemClick(index, event, track.id, track.title, track.url)}
>
{track.title}

))}

</>
)
}
export default Playlist
On the frontend I get this error.
Unhandled Runtime Error
TypeError: Cannot read properties of null (reading 'hasOwnProperty')
pages\playlist[playlist].tsx (25:68) @ PlayerContextUser
function PlayerContextUser() {

25 |     const { currentTime, paused, onTogglePause } = usePlayerContext([
|                                                                    ^
26 |       'currentTime',
27 |       'paused',
28 |       'onTogglePause'

—
Reply to this email directly, view it on GitHub
https://github.com/benwiley4000/cassette/issues/480#issuecomment-1060856911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHOD3LWMKJ6AAWPSX72ZXLU6YSVJANCNFSM5QDUPXNA
.
You are receiving this because you commented.Message ID:
@.***>

Well, that worked! I just moved it up higher in _app.tsx. Thanks for much!

Awesome, glad that worked.
It's important to understand that Cassette doesn't use a global
communication channel, it uses React Context. This means that the player
context is inherited implicitly via the React hierarchy. If the component
that wants to use the player context doesn't live underneath a
PlayerContextProvider, it won't work.
Don't hesitate to ask more questions!
Le lun. 7 mars 2022 11 h 57 a.m., Steve @.***> a écrit :

Well, that worked! I just moved it up higher in _app.tsx. Thanks for much!
—
Reply to this email directly, view it on GitHub
https://github.com/benwiley4000/cassette/issues/480#issuecomment-1060907408,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHOD3J7CFVWFAWDF5Y5DC3U6YYO7ANCNFSM5QDUPXNA
.
You are receiving this because you commented.Message ID:
@.***>


Also include NEQ in filters

This fixes != for field value comparisons.

@pauldix @dgnorton

LGTM, :ship:. Since you were adding test cases for queries against tags, it wouldn't hurt to add some that test against multiple tags using AND and OR operators.

Let me get back to that -- I'm working on tags in https://github.com/influxdb/influxdb/pull/2105, and will add more tests there.


Fix Monitoring server port missing

It should be 9000 according to README(https://github.com/sqshq/piggymetrics#important-endpoints), and it's missing from the config files

Codecov Report

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

@@            Coverage Diff            @@
##             master      #48   +/-   ##
=========================================
  Coverage     79.42%   79.42%
  Complexity      230      230
=========================================
  Files            51       51
  Lines           588      588
  Branches         12       12
=========================================
  Hits            467      467
  Misses          119      119
  Partials          2        2

Continue to review full report at Codecov.

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

Thank you for the contribution


create subnets in different availability zones

this can be done by by passing the az's properly in the subnets list


Update live

Maybe?

Docs Build status updates of commit f1d12bb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-autogen/com.microsoft.signalr.DefaultHttpClient.yml
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.signalr.HttpClient.yml
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.signalr.HttpHubConnectionBuilder.yml
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.signalr.HubConnection.yml
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.signalr.InvocationMessage.yml
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.signalr.LongPollingTransport.yml
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.signalr.NegotiateResponse.yml
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.signalr.StreamInvocationMessage.yml
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.signalr.TransportEnum.yml
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.signalr.yml
:white_check_mark:Succeeded

docs-ref-autogen/toc.yml
:white_check_mark:Succeeded

package.json
:white_check_mark:Succeeded

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

To be clear this does not include removing non-public APIs, correct? I think that's fine, I just want to be clear.

Correct, since I just learned how a few minutes ago :P

Well it kind of worked, still says 2.2 preview 3 at the bottom of all the pages, but at least new stuff is there now.


[LUIS] Access denied error when clicking on a trace in emulator

What project is affected?
VA
What language is this in?
C#
What happens?
[LUIS] Access denied error shown when clicking on a trace in emulator
What are the steps to reproduce this issue?

Deploy the bot using proveded script
./Deployment/Scripts/deploy.ps1 -name "MyAssistant1" -location "southcentralus" -appPassword "XXX" -luisAuthoringKey "XXX" -luisAuthoringRegion "westus" -luisEndpoint "https://westus.api.cognitive.microsoft.com/" -parametersFile "./Deployment/Resources/parameters.template.json" -languages "en-us,es-es"
Run emulator using the link from the script output and enter your name
Click on "trace" (see screenshot)

What were you expecting to happen?
Not sure what should I expect but definitely not the error
Can you share any logs, error output, etc.?
[LUIS] Access denied due to invalid subscription key or wrong API endpoint. Make sure to provide a valid key for an active subscription and use a correct regional API endpoint for your resource.
Any screenshots or additional context?

Would be great if the Emulator could provide some initial guidance on this error and how to resolve within the Emulator?

@turbozapekanka did that resolve the issue for you?

Sort of.
I had to manually provide the keys though
I signed in and then clicked + to add luis services but it didn't automatically find the luis models for some reason:

After I added one luis model manually it worked (for all models, which is strange.)

I'd just remove that red error from the emulator and instead show a hint in the top right part (where intent is shown) saying "sign in for reassigning the intent" (I guess this all it does, right?)
That red thing just scares people.

@turbozapekanka what version of the Emulator are you using?

4.9.0

Thanks. The heuristic used that is causing this behavior is that you are using a .bot file to connect to the bot. Can you confirm?
In the above scenario, the assumption is that the appropriate LUIS credentials are also serialized into that .bot file.

Yes I do use a .bot file

@cwhitten As a part of this PR we https://github.com/microsoft/BotFramework-Emulator/pull/2074 we had addressed this scary message from not showing up when connecting to a bot through a URL whereas when connected through a bot file we do show the missing credentials error message. We might need a a design update to make sure a visual friendly message.

The design update we will be making is showing the error message with the amber font color to make it less blaring for now.


Clothes do not carry

The clothes of my hotel are not charging, already changed my SWF several times and have checked several times if the wrong configuration. I do not know what else to do.
I will post some of my prints SWF I was using with Azure 2.0 and everything was working 100%, I've changed the Habbo.swf.
http://imgur.com/a/gEggN
All commands work, mobs, etc ... LESS visual, they do not carry.
I am eager to use the emulator of you, and I'm desperate because I can not put these visuals to work. PLEASE HELP ME.

You know that this new release, has two extra .xml, the PRODUCTION has more xml's on gordon. Check for some 404 not found in the client.

Is there any own swf for this emulator?


Proposal: All Offers Expire

One of the long-term challenges for the XRP Ledger is managing the unbounded growth of ledger data size. History is one thing—it's inevitable that full historical data will grow indefinitely—but the size of the current state also has a tendency to get larger under normal usage as it accumulates ledger objects that no one wants or needs anymore—in a word, cruft.
One way we can get rid of some cruft is to make it so that all Offers in the decentralized exchange eventually expire, after which point they can be removed. Right now Offers only expire if their creator explicitly sets an Expiration time on them. A simple change that would improve the situation is to change the OfferCreate transactor so that if you omit the Expiration time, it gets set to a sensible default value such as 90 days. This alone could dramatically reduce the "incidental" introduction of cruft in the ledger.
There are lots of issued currencies in the XRP Ledger that are no longer used and as long as the XRP Ledger continues to exist it's likely that more issued currencies may pop up and die off. It's pointless to keep offers for these currencies around when they're no longer in use. There are also lots of dormant accounts that may never be used again; and even though it may be too hard to know which accounts can be reasonably deleted, there should be no problem with deleting those accounts' offers even in active markets. To my understanding, it's pretty normal for an exchange to have a maximum lifetime for any single offer. Most of the time the market is expected to move often enough that you don't want an offer to hang around that long.
We could also look at setting explicit upper bounds for Expiration so you can't, say, set it to expire at MAXINT to make an effectively immortal offer. I think 1 year seems like a reasonable "longest offer term" value. If you can't be bothered to update your offers annually I don't know what you're doing. I guess a possible use case for immortal offers would be if you issued a currency and then intentionally blackholed your account?

I would be fine with setting the upper bound for Expiration to 90 days. For example, Robinhood has only two options for "Time in Force". Orders expire either "Today" (at after-hours close) or in 90 days ("Good till canceled" is the term used -- even though they actually expire in 90 days unless cancelled before that).
One concern is that "old" offers are difficult to find (so that they can be removed). One approach for this could be to have a new transaction type that can only delete expired offers from the books. Similar to finishing an escrow that has passed its FinishAfter time, anyone (a "good samaritan"?) could help reduce ledger cruft by clearing out expired offers in this way.

This proposal spams the transaction database vs. the ledger state. I'm not sure that this is a good trade-off, but it might be worth it after all - RAM is more expensive than disk at the moment.
I share Elliot's concern about the actual cancelling mechanism, though I find the "good samaritan" approach of Escrows already rather kludgy - and with offers there's nearly no incentive for anyone other than server operators to actually remove outdated offers.
I also have concerns about "magic values". What makes 90 days, a year or a decade (or 10 minutes) special or worthy enough to write into the core of the protocol, force cancelling an offer after that time?
If you are concerned about ledger state growth, a "swap" mechanism that moves rarely used portions of the state trie on slower storage might be a more general solution that doesn't need such invasive measures.

That's a good point that this hits the transaction database harder, since it means there will probably be more metadata for Offers that have been canceled. You mentioned that disk is cheaper than RAM "at the moment"—but realistically, disk will always be cheaper than RAM; if it weren't, people wouldn't use disk. But more importantly, the transaction database doesn't suffer from the same scaling problem as the ledger state. Full history is not necessary to process any future transactions; full state is. So it's absolutely achievable (even today!) to archive transactions beyond a certain age, whereas the tech to find and archive portions of the state trie that aren't in use is quite a bit more complicated and may not work at all for some possible ledger states.
I'm sympathetic to the issue of magic numbers, but at some point when designing a system you just have to make choices so you aren't paralyzed by indecision. I could see the maximum offer expiration being set on a votable parameter like the fee and reserve settings, but I honestly don't think it's important enough. If people later decide they want more flexibility in max offer expiration, a follow-up amendment can change it.
As for how the expired offers get deleted from the books: worst case scenario, no one does anything and they sit around untouched, which is exactly the current status quo. So while we can debate possible improvements, I don't think that should be a showstopper for implementing global offer expiration, because it's still an improvement in terms of keeping the ledger size in check.
On that subject, though, here's roughly how I would make the cleanup transaction work.

Transaction Type (tentative name): CleanUpBook (normal transaction¹)
Fields: Common fields, plus TakerGets and TakerPays.

The value amounts in these fields would be ignored. Otherwise these fields match the equivalent fields in OfferCreate.

Effect: Finds the order books that would be matched by a theoretical "OfferCreate" with the same TakerGets and TakerPays currencies, except that it treats TakerGets (the amount being offered) as infinite and TakerPays (the amount being asked in return) as infinitesimal. Thus it walks through the matching books starting at the best possible rate of return. Whenever the transaction finds an unfunded² or expired offer, it deletes that offer and moves on. It stops after it has accumulated a maximum amount of metadata (so probably something like 1000 or 2000 offers like tecOVERSIZE), or if it has finished walking through all the books for this currency pair.

To prevent excessive work, it adds a LastCleaned timestamp to each offer directory it crawls. If the offer directory already has a LastCleaned timestamp that is more recent than some predefined interval (24 hours? 7 days?) then the transaction skips over that book entirely.

I have a feeling this transaction should have a higher than normal cost or have some other restrictions. It's likely a very intensive transaction to process in both RAM and CPU. Worse, running the transaction multiple times on the same book in quick succession provides little to no benefit but costs as much or more work as doing it on a very "cluttered" book where it removes a lot of expired offers.
¹ I considered making a pseudotransaction that servers could automatically propose, but I couldn't figure out an elegant mechanism for how they'd know which markets to submit cleanup transactions for. The nice thing of making these kinds of cleanup functions "normal transactions" is that someone can step up and handle the chore of doing it without burdening "ordinary" servers in the network with keeping track of when and how to do it, so it could be done entirely by one entity who's very good at it. The downside, of course, is the Tragedy of the Commons. Theoretically the community could donate to someone who does this sort of work to compensate them for the costs of inspecting the ledger for things that need cleanup, or something like that. Basically at some point the ledger may need a formal waste management utility or something but its structure and management don't need to be written into the XRPL protocol.
² There are likely some weird edge cases around declaring offers unfunded when the same person has placed offers at different depths of the same book. For example, a trader might have a small "front" offer at a cheap rate and a larger "backstop" offer at a more profitable rate. I'd like them to have the flexibility to keep the backstop offer on the books in case they cancel or replace their cheaper front offer. To achieve that, I think I'd like the CleanUpBook transaction to consider an offer unfunded only if the owner has none of the offered currency, which should be evaluated independently for each offer.

I would prefer an approach using familiar concepts:

Change the OfferCreate transactor so that if you omit the Expiration time, it gets set to a sensible default value (90 days), as proposed by @mDuo13
Change the OfferCancel transactor to include a mandatory Owner field. Offers and Escrows already share the OfferSequence field. Allow expired offers to be cancelled by anyone, just like escrows.

On another note, why are Offers worthy of a dedicated cleanup transaction, but not PaymentChannels, Checks and Escrows?

I like the idea of OfferCancel having an Owner field so you can cancel other people's (expired/unfunded) Offers¹. It could be optional, and if omitted the transaction sender is the owner (just how the transaction works today).
¹ I also like the idea of having a transaction I can use to cancel other people's (non-expired, funded) offers. But that's only for me, not the rest of y'all. 😜

Another idea: Add a flag to the OfferCreate and/or OfferCancel transactions that tells the transactor to do the proposed CleanUpBook action. If the flag was set, the base fee would be increased to pay for the extra work. The users working with that book would probably be the most incentivized to keep that book clean and usable. In combination with the other OfferCreate flags and non-crossing values, we wouldn't need a new transaction type.

If you want to save RAM, how about use AMM Liquidity Pool to instead of order book.

I saw this discussion and got curious about how many offers actually hang around for over 90 days.  So I took a sample.  I grabbed ledger 64177830 which is pretty recent.  And I grabbed ledger 62119762, which is just a hair over 90 days old.  Then I extracted the indexes of the offers in both ledgers and compared them to see how many offers over 90 days old were in the recent ledger.  Here were the results:
Ledger        Offers          Offers over 90 days old        Percentage of old offers
62119762       37176
64177830       30969                            23765                             77%

So, assuming I did all the steps right, it turns out that 77% of the offers in ledger 64177830 are over 90 days old.  That's substantial.  Those offers may have changed in the last 90 days, but at a minimum the offers have been present in the ledger that long.
I also have to agree with @RareData that if we're going to take on the problem of stale ledger data we should make sure we prioritize the data types to get the most space savings.  Offers may not be the biggest offenders.

Thanks to work by NixerFFM, we can now actually get the counts of objects in the ledger and their space: https://xrpldata.com/api/v1/ledgerdata
Based on this, a single recent ledger by data size consists of accounts (47%), trust lines  (31%), owner directories (16%), and everything else is margin. Offers are 1% with another 0.7% in order book DirectoryNodes.
So, while we probably could save a few megabytes by doing this, it's clearly not the place to get the most savings. In the long term, I still think setting limits on Offers will be necessary, and it might be easier to put into practice than some of the other places because there is precedent in the exchange industry and it's easy enough to re-create them, whereas it would certainly be more controversial to purge unused accounts or even trust lines.

Given the relatively small amount of open offers, and the fact that an offer already ties up an owner reserve (this serves as an incentive for offer creators to cancel unwanted offers), I think there is minimal benefit to having all offers expire. There's also a good argument to be made that it's harmful since it reduces liquidity on the DEX (and more liquidity is more important than reducing ledger size, at least for now).
I vote for closing this issue. "not a bug / won't fix"
Of course, we can re-open or revisit if the size of open offers becomes a problem in the future.

One of the most used XRPL DEX interfaces, XRP Toolkit, enforces a max
expiration time of 1 year. This is an issue that can be solved off chain.
On Thu, 15 Jul 2021, 21:29 Elliot Lee, @.***> wrote:

Given the relatively small amount of open offers, and the fact that an
offer already ties up an owner reserve (this serves as an incentive for
offer creators to cancel unwanted offers), I think there is minimal benefit
to having all offers expire. There's also a good argument to be made that
it's harmful since it reduces liquidity on the DEX (and more liquidity is
more important than reducing ledger size, at least for now).
I vote for closing this issue. "not a bug / won't fix"
Of course, we can re-open or revisit if the size of open offers becomes a
problem in the future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ripple/rippled/issues/3219#issuecomment-880956476,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKSEFCT2DQ4YXSBN2P4GTVTTX4ZJZANCNFSM4KE62L6A
.


Ensure elfeed-search-browse-url stays in elfeed buffer (fixes #425)

If some emacs internal browser such as eww is invoked by browse-url, the
remainder of the function ran in the eww buffer which didn't make sense and
didn't visually mark the entry as read.

Thanks! I made a tweak to use with-current-buffer instead of set-buffer,
then merged as 243add9.


Setup query regarding Png++ install (unrelated to this repository)

I'm trying to install Png++ with no sucess. I followed the instructions and tried to 'make' the installation.
This is my output from the first make command:

shreyas@shreyas:~/png++-0.2.9$ make
make -C example
make[1]: Entering directory /home/shreyas/png++-0.2.9/example' Makefile:45: pixel_generator.dep: No such file or directory g++ -M  -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g pixel_generator.cpp -o- | \ 	  sed 's/\(pixel_generator\)\.o[ :]*/\1.o pixel_generator.dep : /g' > pixel_generator.dep make[1]: Leaving directory /home/shreyas/png++-0.2.9/example'
make[1]: Entering directory /home/shreyas/png++-0.2.9/example' g++ -c -o pixel_generator.o pixel_generator.cpp -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g g++ -o pixel_generator pixel_generator.o -L/usr/local/lib -L/home/shreyas/anaconda2/lib -lpng16  -g make[1]: Leaving directory /home/shreyas/png++-0.2.9/example'

And when I try to run make test, this is my ouput:

shreyas@shreyas:~/png++-0.2.9$ make test
make test -C test
make[1]: Entering directory /home/shreyas/png++-0.2.9/test' Makefile:64: convert_color_space.dep: No such file or directory Makefile:64: generate_gray_packed.dep: No such file or directory Makefile:64: read_write_gray_packed.dep: No such file or directory Makefile:64: generate_palette.dep: No such file or directory Makefile:64: write_gray_16.dep: No such file or directory Makefile:64: read_write_param.dep: No such file or directory Makefile:64: dump.dep: No such file or directory g++ -M  -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g dump.cpp -o- | \ 	  sed 's/\(dump\)\.o[ :]*/\1.o dump.dep : /g' > dump.dep g++ -M  -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g read_write_param.cpp -o- | \ 	  sed 's/\(read_write_param\)\.o[ :]*/\1.o read_write_param.dep : /g' > read_write_param.dep g++ -M  -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g write_gray_16.cpp -o- | \ 	  sed 's/\(write_gray_16\)\.o[ :]*/\1.o write_gray_16.dep : /g' > write_gray_16.dep g++ -M  -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g generate_palette.cpp -o- | \ 	  sed 's/\(generate_palette\)\.o[ :]*/\1.o generate_palette.dep : /g' > generate_palette.dep g++ -M  -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g read_write_gray_packed.cpp -o- | \ 	  sed 's/\(read_write_gray_packed\)\.o[ :]*/\1.o read_write_gray_packed.dep : /g' > read_write_gray_packed.dep g++ -M  -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g generate_gray_packed.cpp -o- | \ 	  sed 's/\(generate_gray_packed\)\.o[ :]*/\1.o generate_gray_packed.dep : /g' > generate_gray_packed.dep g++ -M  -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g convert_color_space.cpp -o- | \ 	  sed 's/\(convert_color_space\)\.o[ :]*/\1.o convert_color_space.dep : /g' > convert_color_space.dep make[1]: Leaving directory /home/shreyas/png++-0.2.9/test'
make[1]: Entering directory `/home/shreyas/png++-0.2.9/test'
g++ -c -o convert_color_space.o convert_color_space.cpp -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g
g++ -o convert_color_space convert_color_space.o -L/usr/local/lib -L/home/shreyas/anaconda2/lib -lpng16  -g
g++ -c -o generate_gray_packed.o generate_gray_packed.cpp -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g
g++ -o generate_gray_packed generate_gray_packed.o -L/usr/local/lib -L/home/shreyas/anaconda2/lib -lpng16  -g
g++ -c -o read_write_gray_packed.o read_write_gray_packed.cpp -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g
g++ -o read_write_gray_packed read_write_gray_packed.o -L/usr/local/lib -L/home/shreyas/anaconda2/lib -lpng16  -g
g++ -c -o generate_palette.o generate_palette.cpp -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g
g++ -o generate_palette generate_palette.o -L/usr/local/lib -L/home/shreyas/anaconda2/lib -lpng16  -g
g++ -c -o write_gray_16.o write_gray_16.cpp -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g
g++ -o write_gray_16 write_gray_16.o -L/usr/local/lib -L/home/shreyas/anaconda2/lib -lpng16  -g
g++ -c -o read_write_param.o read_write_param.cpp -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g
g++ -o read_write_param read_write_param.o -L/usr/local/lib -L/home/shreyas/anaconda2/lib -lpng16  -g
g++ -c -o dump.o dump.cpp -Wall -I.. -I/usr/local/include -I/home/shreyas/anaconda2/include/libpng16  -g
g++ -o dump dump.o -L/usr/local/lib -L/home/shreyas/anaconda2/lib -lpng16  -g
./test.sh
PNG++ FAILS TESTS (154 OF 1566 FAILED)
review test.log for clues
make[1]: *** [test] Error 1
make[1]: Leaving directory `/home/shreyas/png++-0.2.9/test'
make: *** [test] Error 2

I'm hoping someone here knows how to fix this issue. I'm a bit lost. Any help is greatly appreciated.
FYI, this is what my test.log file looks like (154 errors)

convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/basi2c16.png.GRAY.16.out cmp/pngsuite/basi2c16.png.GRAY.16.out differ: byte 60, line 3
out/pngsuite/basi2c16.png.GRAY.16.out cmp/pngsuite/basi2c16.png.GRAY.16.out differ: byte 60, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/basi2c16.png.GA.16.out cmp/pngsuite/basi2c16.png.GA.16.out differ: byte 53, line 3
out/pngsuite/basi2c16.png.GA.16.out cmp/pngsuite/basi2c16.png.GA.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/basi6a16.png.GRAY.16.out cmp/pngsuite/basi6a16.png.GRAY.16.out differ: byte 53, line 3
out/pngsuite/basi6a16.png.GRAY.16.out cmp/pngsuite/basi6a16.png.GRAY.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/basi6a16.png.GA.16.out cmp/pngsuite/basi6a16.png.GA.16.out differ: byte 53, line 3
out/pngsuite/basi6a16.png.GA.16.out cmp/pngsuite/basi6a16.png.GA.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/basn2c16.png.GRAY.16.out cmp/pngsuite/basn2c16.png.GRAY.16.out differ: byte 53, line 3
out/pngsuite/basn2c16.png.GRAY.16.out cmp/pngsuite/basn2c16.png.GRAY.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/basn2c16.png.GA.16.out cmp/pngsuite/basn2c16.png.GA.16.out differ: byte 52, line 3
out/pngsuite/basn2c16.png.GA.16.out cmp/pngsuite/basn2c16.png.GA.16.out differ: byte 52, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/basn6a16.png.GRAY.16.out cmp/pngsuite/basn6a16.png.GRAY.16.out differ: byte 53, line 3
out/pngsuite/basn6a16.png.GRAY.16.out cmp/pngsuite/basn6a16.png.GRAY.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/basn6a16.png.GA.16.out cmp/pngsuite/basn6a16.png.GA.16.out differ: byte 53, line 3
out/pngsuite/basn6a16.png.GA.16.out cmp/pngsuite/basn6a16.png.GA.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/bgan6a16.png.GRAY.16.out cmp/pngsuite/bgan6a16.png.GRAY.16.out differ: byte 53, line 3
out/pngsuite/bgan6a16.png.GRAY.16.out cmp/pngsuite/bgan6a16.png.GRAY.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/bgan6a16.png.GA.16.out cmp/pngsuite/bgan6a16.png.GA.16.out differ: byte 53, line 3
out/pngsuite/bgan6a16.png.GA.16.out cmp/pngsuite/bgan6a16.png.GA.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/bgyn6a16.png.GRAY.16.out cmp/pngsuite/bgyn6a16.png.GRAY.16.out differ: byte 53, line 3
out/pngsuite/bgyn6a16.png.GRAY.16.out cmp/pngsuite/bgyn6a16.png.GRAY.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/bgyn6a16.png.GA.16.out cmp/pngsuite/bgyn6a16.png.GA.16.out differ: byte 53, line 3
out/pngsuite/bgyn6a16.png.GA.16.out cmp/pngsuite/bgyn6a16.png.GA.16.out differ: byte 53, line 3
out/pngsuite/s09i3p02.png.RGB.8.out cmp/pngsuite/s09i3p02.png.RGB.8.out differ: byte 58, line 3
out/pngsuite/s09i3p02.png.RGB.8.out cmp/pngsuite/s09i3p02.png.RGB.8.out differ: byte 58, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/tbbn2c16.png.GRAY.16.out cmp/pngsuite/tbbn2c16.png.GRAY.16.out differ: byte 53, line 3
out/pngsuite/tbbn2c16.png.GRAY.16.out cmp/pngsuite/tbbn2c16.png.GRAY.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/tbbn2c16.png.GA.16.out cmp/pngsuite/tbbn2c16.png.GA.16.out differ: byte 52, line 3
out/pngsuite/tbbn2c16.png.GA.16.out cmp/pngsuite/tbbn2c16.png.GA.16.out differ: byte 52, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/tbgn2c16.png.GRAY.16.out cmp/pngsuite/tbgn2c16.png.GRAY.16.out differ: byte 53, line 3
out/pngsuite/tbgn2c16.png.GRAY.16.out cmp/pngsuite/tbgn2c16.png.GRAY.16.out differ: byte 53, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
out/pngsuite/tbgn2c16.png.GA.16.out cmp/pngsuite/tbgn2c16.png.GA.16.out differ: byte 52, line 3
out/pngsuite/tbgn2c16.png.GA.16.out cmp/pngsuite/tbgn2c16.png.GA.16.out differ: byte 52, line 3
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED
convert_color_space: expected 8-bit data but found 16-bit; recompile with PNG_READ_16_TO_8_SUPPORTED

Thank you very much in advance!
Regards,
Shreyas

Figured this one out!
Apparently libpng1.6 doesn't work well with Png++ version 0.2.9. I downgraded my libpng to version 1.2.50 and switched to the png++ 0.2.7 version and it works now.

Hi，how to downgraded libpng to version 1.2.50 ？

Hi，how to downgraded libpng to version 1.2.50 ？

https://github.com/jzbontar/mc-cnn/issues/17#issuecomment-377492959

Hi，how to downgraded libpng to version 1.2.50 ？

https://sourceforge.net/projects/libpng/files/


Promote TentativeOrAccuSnap

@bbastings The MeasurePerpendicularTool from measure-tools-react uses the TentativeOrAccuSnap API, which is marked internal.
Promote this or should the tool use something else?

@bbastings The MeasurePerpendicularTool from measure-tools-react uses the TentativeOrAccuSnap API, which is marked internal.
Promote this or should the tool use something else?

You can promote this to public, it's just a convenient wrapper for public AccuSnap and TentativePoint methods.


Adding final to field inconsistant

There are times where it seems that I don't get the final keyword added on my fields.  I'm using idea15 pro edition

Do you have an example of a non working file so I can reproduce? It seems to work for me.

cannot reproduce


tag new release

Is it possible to tag a new release for features like lambda: check if error type is InvokeResponse_Error (#312)?

done! https://github.com/aws/aws-lambda-go/releases/tag/v1.20.0


clone redundant?

Running clippy warns that this clone is redundant:
https://github.com/async-rs/async-task/blob/b7a249680490991f92cc2144d4eff65e4effb3b7/src/waker_fn.rs#L26
True or false?
Thanks

No, this clone and forget is necessary to bump the reference counter. This won't be necessary anymore when this feature gets stabilized: https://github.com/rust-lang/rust/pull/70733

Thanks!


Deal with fields not having a designation

Some records in my 1Password setup don't have a "designation" value in every field.  For example:
{'id': 'signup-submit;opid=__5', 'name': '', 'type': 'I', 'value': 'Sign up'}

This change skips any fields without a designation, rather than crashing out with a KeyError.

Thank you! <3 <3


Please modify the tensorflow/workspace.bzl's eigen version to make Nvidia TX2 compilation successful

Hi,all
I just managed to compile Tensorflow 1.2 successfully in Nvidia TX2. Despite the patches made by this article: http://www.jetsonhacks.com/2017/04/02/tensorflow-on-nvidia-jetson-tx2-development-kit/ , the workspace.bzl file needs to be modified to use the latest eigen version.
Specifically, you need to change the following lines:

native.new_http_archive(
name = "eigen_archive",
urls = [
"http://mirror.bazel.build/bitbucket.org/eigen/eigen/get/f3a22f35b044.tar.gz",
"https://bitbucket.org/eigen/eigen/get/f3a22f35b044.tar.gz",
],
sha256 = "ca7beac153d4059c02c8fc59816c82d54ea47fe58365e8aded4082ded0b820c4",
strip_prefix = "eigen-eigen-f3a22f35b044",
build_file = str(Label("//third_party:eigen.BUILD")),
)

to:

native.new_http_archive(
name = "eigen_archive",
urls = [
#"http://mirror.bazel.build/bitbucket.org/eigen/eigen/get/f3a22f35b044.tar.gz",
#"https://bitbucket.org/eigen/eigen/get/f3a22f35b044.tar.gz",
"https://bitbucket.org/eigen/eigen/get/3.3.4.tar.gz",
],
sha256 = "the sha256 value you used to verify",
strip_prefix = "eigen-eigen-5a0156e40feb",
build_file = str(Label("//third_party:eigen.BUILD")),
)

Since I'm not sure if the newest eigen works well in other platform, I don't have confidence to ask for a PR.
I just post this issue in case some of you guys can't compile tensor flow 1.2 in nvidia TX2.

I think the best course forward here would be to propose this as a PR. We can then review it and see whether it makes sense to make this change. Thanks!


Treat list custom json facebook with test

updates send_custom_json function and adds tests for facebook
Status (please check what you already did):

[x] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

Pull Request Test Coverage Report for Build 600526778

0 of 5 (0.0%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 87.282%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

rasa/core/channels/facebook.py
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

rasa/core/channels/facebook.py
1
40.43%

rasa/core/test.py
1
94.82%

rasa/test.py
2
84.78%

Totals

Change from base Build 585609801:
-0.02%

Covered Lines:
22071

Relevant Lines:
25287

💛  - Coveralls


Hardware performance issues cause items to be lost

Tested versions
the newest, v4.3
System information
Godot v4.3.stable - Windows 10.0.19045 - GLES3 (Compatibility) - GeForce GT 240 - AMD Athlon(tm) II X2 250 Processor (2 Threads)
Issue description
My computer is so bad that I can't use the forward+ mode of Godot 4.3, and now the engine crashes when I open the editor for this rendering mode, but I accidentally set a project that was originally rendered in compatibility mode to forward+ rendering, and now I can't open the editor and I can't fix the rendering mode.
Steps to reproduce

getting your computer old and making sure it performs can't be rendered using the forward+ mode
open a project that is rendered in compatibility mode
convert it to forward+ rendering mode
follow the pop-up window to restart the editor
editor crashed

Minimal reproduction project (MRP)
Any project (including empty projects with nothing) can trigger this bug, this is my full project

To fix this you can edit the project file, starting with 4.4 this is solved by switching the rendered automatically if not supported, see:

https://github.com/godotengine/godot/pull/97142

You can also open it directly from the command line with godot --rendering-driver opengl3 project.godot

it works,thanks so much!


maven-publish gradle bug workaround.

Fix generated POMs to mark dependencies scope as gradle defined 'compile', not 'runtime'.

You shouldn't switch every library into the maven compile scope in the pom. Only libraries in the public api that people would then have to search for. The compileApi configuration added by a nebula plugin is a little less boilerplate.
Personal opinion is that the way maven leaks compile scope dependencies everywhere is a detriment.

We can re-open this PR, depending on how #141 works for Maven users.


Undesirable change to JDBC Sampler behaviour in 5.6.3

Expected behavior
The following commit has introduced an undesirable change to the JDBC sampler.
https://github.com/apache/jmeter/commit/945281cfaa6cca782f0e11f151eb22497d545713
Prior to this change, the "Limit Resultset" value would only apply when reading the result set, reading would stop after 'n' rows.
Now, by this change, the sampler calls SetMaxRows() to the limit value. This can then be used by the JDBC client and server to optimise the query, such as by pushing a LIMIT clause into the query plan which can terminate server processing before all results have been generated.
I believe this behaviour should be rolled back, as it invalidates a common requirement of database performance testing.
Actual behavior
No response
Steps to reproduce the problem
https://github.com/apache/jmeter/commit/945281cfaa6cca782f0e11f151eb22497d545713
JMeter Version
5.6.3
Java Version
No response
OS Version
No response

It might indeed make sense to split the property in two: "max rows" limit at JDBC level and "number of fetched rows" at the client level.

That is an excellent suggestion.


Update active-directory-accessmanagement-manage-groups.md

Update to clarify that users who no longer satisfy a rule on a group are removed from that group

Hi @RobdeJong, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (rodejo). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@RobdeJong : Thanks for your contribution to the Azure documentation! The author, @curtand, has been notified to review your proposed change.


Round robin should also update triage owner on Bugzilla

This way the triage owner rotation is reflected in Bugzilla too

I think this is blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=1773137

Waiting for https://github.com/mozilla-bteam/bmo/pull/1866 to be merged and deployed


Added the stub of a method to update the python_anywhere server when …

…we push to the github repo (webhook)

Ok


[BUG] Time Out message doesn't send

Describe the bug
When putting a limited amount of tries, if RandomTP runs out of tries for the command, the server doesn't send the timed out message to the player.
To Reproduce
Steps to reproduce the behavior:

set max tries to a limited number (ex: 5)
save config and restart server to reload the config
run /rtp

Expected behavior
"Timed out trying to find a safe location to warp to."
Desktop (please complete the following information):

RandomTP version: 7.1.0
Minecraft Version: 1.19.2

Additional context
If you do get teleported, try again until you won't be teleported.

This should be fixed in the latest release. If not make sure to re-open the issue or create a new one.


Update API README.md

Remove broken route and fixed 8000 route to current version

Can you look into the failing tests?

I expect those a Chris's fault. Check the 0.38 branch. If they are the same failing tests, then it's him.
.:Brian J. Geiger
Sent from the phone.

On Jun 3, 2015, at 3:47 PM, Saman Ehsan<EMAIL_ADDRESS>wrote:
Can you look into the failing tests?
—
Reply to this email directly or view it on GitHub.

Since 0.38 has been released, please re-submit to 0.39 or develop. Thanks!

@brianjgeiger Is this change still relevant or have the general osf.io develop docs been updated to include this information? In other words, should I send a PR to develop with this minor change?

Let's skip this. We'll probably want to do a more comprehensive docs change in a week or so.


Send Monthly Statistic report

On the administrative dashboard allow the user to slect a date range (already implemented) and then click on a button to download a Upload report or a usage report
The download report would have the same format as the weekly report sent via email: https://github.com/psu-stewardship/scholarsphere/blob/develop/lib/tasks/scholarsphere.rake#L207-L209
The Usage report (downloads and views) would have the following format:
File URL, work URL, downloads, views
Not needed:
https://github.com/psu-stewardship/scholarsphere/blob/develop/config/cronjobs/send_weekly_stats.bash
https://github.com/psu-stewardship/scholarsphere/blob/develop/config/schedule.rb#L45

From the spreadsheet, folks would like the ability to create:
Total number of uploads by resource type
Downloads:
Number of total downloads
Top 10 downloads (urls)

https://github.com/psu-stewardship/scholarsphere/wiki/Yearly-Download-and-Upload-Report - Keep empty downloads in the report.

Getting weekly stats and aggregating that data.


Improve handling of chunks in ember-core

We convert between three different representations, mostly for convenience: Chunk, Array, and ByteVector. I think we could avoid a lot of copying by either choosing one representation or being more diligent about when we copy.

The biggest performance leap Blaze ever made was getting smarter about viewing ByteBuffers vs. copying.  Don't overlook that, if you've got any that you know you won't be modifying.

@RaasAhsan @rossabaker are we talking about consistency between lines 1, 2 and 3 all being Array[Byte] instead of being Array[Byte], Chunk[Byte] and ByteVector respectively?

@ashwinbhaskar I think the goal is less around consistency and more being mindful around where we're copying where it isn't necessary. FS2 gives us a Chunk[Byte] which we convert to Array[Byte] and ByteVector for various reasons, which definitely copies. The underlying representation of the Chunk we get from FS2 is a ByteBuffer, and in the ideal world, that's sufficient for us to parse a response without doing any funky conversions.


BREAKING CHANGE: Upgraded to support babel v6.

.babelrc added to project.
Peer dependencies for 'babel' and 'babel-plugin-syntax-flow' packages have
been added.
Plugin updated accordingly to match the required format of babel v6.

Solves issue #7
Supersedes PR #8 - Thanks @mlegenhausen for the inspiration! x
All tests passing, would appreciate someone having a scan.
@gcanti @mlegenhausen

@ctrlplusb this is awesome! Thanks a lot. Going to merge

No problem!  Thank you for the quick merge and for your amazing work on tcomb.
I went full circle through so many type systems (including flow and typescript) and honestly believe tcomb is the best candidate.  I'm babel 6 guy, so had to make this happen! :)

Thanks for helping me out :)


ESP32C3: BLE Peripheral advertisement fails to start when Central already scanning [zephyr-v3.5.0]

Describe the bug
It seems that on Espressif esp32c3 with Zephyr v3.5.0, starting BLE peripheral advertisement via bt_le_adv_start() fails with error code -EIO, if the BLE central is already scanning. This was working fine with Zephyr v3.4.0 for my BLE application.
To Reproduce
The bug can be reproduced by slightly modifying the Scan & Advertise sample as follows:

Add advertisement params

static struct bt_le_adv_param adv_param = BT_LE_ADV_PARAM_INIT(BT_LE_ADV_OPT_CONNECTABLE,
                                                               BT_GAP_ADV_FAST_INT_MIN_2,
                                                               BT_GAP_ADV_FAST_INT_MAX_2,
                                                               NULL);

Use adv_param to start advertisement

err = bt_le_adv_start(&adv_param, ad, ARRAY_SIZE(ad), NULL, 0);

Build the application for esp32c3_devkitm and flash it to the board.
Observe the debug logs.

Expected behavior
No error on starting advertisement while the client is scanning.
Impact
Showstopper, since I'm unable to run my application properly.
Logs and console output
*** Booting Zephyr OS build zephyr-v3.5.0 ***
Starting Scanner/Advertiser Demo
[00:00:00.000,000] <inf> esp32_bt_adapter: BT controller compile version [d913766]
[00:00:00.162,000] <inf> bt_hci_core: Identity: FF:2C:50:7E:A3:98 (random)
[00:00:00.162,000] <inf> bt_hci_core: HCI: version 5.0 (0x09) revision 0x0016, manufacturer 0x0060
[00:00:00.162,000] <inf> bt_hci_core: LMP: version 5.0 (0x09) subver 0x0016
Bluetooth initialized
[00:00:00.566,000] <wrn> bt_hci_core: opcode 0x2005 status 0x0c
Advertising failed to start (err -5)

Environment:

Devcontainer based on image: zephyrprojectrtos/zephyr-build:v0.26.6
Toolchain: Zephyr SDK 0.16.4
Zephyr branch: zephyr-v3.5.0 / main
Target: esp32c3 (DevkitM-1)

Additional context
For reference, the modified main.c from the sample is attached as main.txt

@abdulayubzoi Can you reproduce this on current main?

@abdulayubzoi this may be a limitation of the controller, but if it used to work in 3.4.0 there may be something else there. Would you be able to git bisect the issue and find what specific commit broke it?

@abdulayubzoi Can you reproduce this on current main?
Yes, I've been able to reproduce it on main.

We shall submit the new hal_v5.1 base PR in a couple of weeks.

@sylvioalves this was done, right? Can you close the issue then?

We shall submit the new hal_v5.1 base PR in a couple of weeks.

@sylvioalves this was done, right? Can you close the issue then?

Yes.


Consider new rules from eslint-plugin-react@3

eslint-plugin-react v3 was released. I wanted to make sure you react folks (@dcousens, @cesarandreu, @jprichardson, @dcposch) knew about it.
If there are any rule changes you want to make, please go ahead. standard v5 will be upgrading the eslint-plugin-react dependency from v2 to v3.
This is their changelog:
3.1.0 / 2015-07-28

update dependencies
add event handlers to no-unknown-property (#164 @mkenyon)
add customValidators option to prop-types (#145 @CalebMorris)
fix comment handling in jsx-curly-spacing (#165)
documentation improvements (#167 @ngbrown)

3.0.0 / 2015-07-21

add jsx-no-duplicate-props rule (#161 @hummlas)
add allowMultiline option to the jsx-curly-spacing rule (#156 @mathieumg)
breaking in jsx-curly-spacing braces spanning multiple lines are now allowed with never option (#156 @mathieumg)
fix multiple var and destructuring handling in props-types (#159)
fix crash when retrieving propType name (#163)

no-unknown-property looks good,  provided it only occurs for DOM elements (library authors may not be so consistent).
jsx-no-duplicate-props LGTM.

@dcousens Author of the upgrade to no-unknown-property here. I'm not a fan of the name, but it does only occur on DOM elements, not React components. It reminds you that JSX prefers onClick to onclick and acceptCharset to accept-charset. There are specs to help verify that.

Please test it on some of your code. If you think it looks good, please send a PR and (if you're feeling bold) publish a new version to npm!

Closing this stale issue.


missing icon for ipad pro

ipad pro icon 83.5pt is missing in the generation

Are you sure? It seems there in latest version (0.6.0):
{ name<EMAIL_ADDRESS>size : 167 }

you are right looks like that xcode don't pick it up automatically don't know why.
but adding it by hand from the folder works!

i have the same issue.  the icon for the ipad pro is created but it doesn't automatically get added to the build.  have to modify the Contents.json file to make it work.
Using<EMAIL_ADDRESS>&<EMAIL_ADDRESS>

Closing since talking about possibly outdated problems.
Fell free to open a new issue if needed.


Fix: README.md grammar

Hi!
     I have fixed a few grammatical mistakes and missing article the in the README.md file. Please review this contribution.
Thanks!

@mjbvz :confused:  about what:question:

Hey! @gjsjohnmurray, I haven't concocted these rules for mere contribution. These grammar rules exist and the references are taken from grammarly and one can also refer to the grammar textbook.
This contribution IF approved want make any breaking changes rather it makes the VS Code documentation more robust.
My bit is done with contribution and clarification, feel free to make your case for REJECTION or APPROVAL.

@gjsjohnmurray is spot on here
The changes themselves are questionable and there's already been far too much time spent arguing over grammar rules

flowchart TD
    A(Contribution)
    A--> B[Confused Emoji]
    B-->C(Confused About What ??)
    C--> D[From somewhere IMO jumps in to give IMO]
    D-->E(IMO rebutted with facts & standard rules)
    E-->F{REJECTED}
    F-->G((Why??))
    G-->H[IMO matter]
    G-->I[Standard rules don't matter]
    H-->J((END OF STORY))
    I-->J((END OF STORY))


fix Chinese text of public policy

edit the chinese description of public policy

Coverage increased (+0.02%) to 56.231% when pulling 6b6cff017452a941ab948955eb8ddea31e8ade00 on ninjadq:fix_public_policy_text into 53dbe7408f9a08c272f00e36cce98d122dcdfe57 on vmware:master.


Mineotaur is not temporarily removed

I doubt it's going to be returning....

No veto from my side.


Some sort of bug with NavigationToolbar2QT

When I try to perform the example call I receive this error:
Traceback (most recent call last):   File "C:\Users\Jonathan\Miniconda3\envs\ThermalAspen\lib\site-packages\cpselect\cpselect.py", line 162, in updateGUI     if self.wp.canvas.toolbar._active not in ['', None]: AttributeError: 'NavigationToolbar2QT' object has no attribute '_active'
Any ideas?

I dont know, but I also have the same issue

Hi! I have also encountered the same issue. I could fix it by commenting all of the code-blocks in which "self.wp.canvas.toolbar._active" is used in "cpselect.py."
I am not 100% sure what it does, but I think it is meant to make sure that none of the toolbar items is activated before selecting the points. I am sure there is a more elegant fix for it, though.
Line 128 - 142:
`
    #if self.wp.canvas.toolbar._active in ['', None]:
    if self.wp.canvas.pickmode == True:
        self.wp.canvas.pickMode_changed = True
        self.wp.canvas.pickmode = False
        self.statusBar().showMessage('Pick Mode deactivate.')
        self.wp.canvas.cursorGUI = 'arrow'
        self.wp.canvas.cursorChanged = True
    else:
        self.wp.canvas.pickMode_changed = True
        self.wp.canvas.pickmode = True
        self.wp.canvas.toolbar._active = ''
        self.statusBar().showMessage('Pick Mode activate. Select Control Points.')
    #else:
    #    self.statusBar().showMessage(
    #        f'Please, first deactivate the selected navigation tool {self.wp.canvas.toolbar._active}', 3000)`

Line 162 - 164:
#     if self.wp.canvas.toolbar._active not in ['', None]:
       #    self.wp.canvas.pickmode = False
        #       self.wp.canvas.pickMode_changed = True


Added Moe Counter Widget

78 . Moe Counter
Another Cute View Counter.

📍 For example :

It's kinda childish, but what's over.

78 . Moe Counter
Another Cute View Counter.
📍 For example :

It's kinda childish, but what's over.

Thanks for adding 🙏🙏


tentatively finish 2020-resources.md

I finished (tentatively) compiling and organizing all the resources (from the STAT545A part of the course, not STAT545B) - let me know what you think, but it should be ready to put up in the website after I implement any comments that you have! 👍

This is really comprehensive. Thank you for putting this together!


Wonder The package include in the main class from where

Hi, thks for this wonderful machine learning algrithm. I want to know where I can get the package included in main class,
import no.uib.cipr.matrix.DenseMatrix; import no.uib.cipr.matrix.DenseVector; import no.uib.cipr.matrix.Matrices; import no.uib.cipr.matrix.NotConvergedException;
I imported the code but these lines got wrong. How can I fix it, many thks if you can help me.

Include this dependency in your project's pom.xml
   <dependency>         <groupId>com.googlecode.matrix-toolkits-java</groupId>         <artifactId>mtj</artifactId>         <version>1.0.4</version>     </dependency>


Avoid passing too few parameters into function calls

With this commit we reenable the pylint check E1120 which checks
whether function calls contain the correct number of arguments.
Relates #838

@elasticmachine update branch


Create updated spreadsheet for mass obsoletion review (4 branches)

This issue is for the technical team, and should be done AFTER ALL THE MASS OBSOLETION FOR BRANCHES WERE DONE AND MERGED. (Sabrina or Trish or Nicole will let you know when it is ready)
Context:
We have been reviewing the effects of term obsoletion on their children. We are using the spreadsheet created by Harshad (issue number something), choosing parents for children to become orphan/leaves the branch after the obsoletion.
After reviewing the spreadsheet, we added these new parents and obsoleted terms going ontology branch by branch.
There are 4 ontology branches for which we could get this review "for free" because most (or all?) of the terms to be obsoleted in these branches have already been obsoleted in other branches (the obsoleted terms were in multiple branches of the ontology).
To do:
For the following 4 ontology branches, recreate the spreadsheets by using an updated list of "terms to be obsoleted" that includes only terms that have not been obsoleted yet. (note: please create NEW spreadsheet, and do not remove the previous/existing spreadsheets)
Ontology branches:

branch ID
branch name

MONDO:0021147
disorder of development or morphogenesis

MONDO:0003847
hereditary disease

MONDO:0002254
syndromic disease

MONDO:0024458
disorder of visual system

Terms to be obsoleted:
Please use the original term to be obsoleted list (list can also be found here, in the tab called "terms to obsolete (230913)), and filter out all the terms that are currently obsoleted in the ontology, and keep the one with the "obsoletion candidate" tag (some terms have been removed from the original obsoletion list).
Note: there is a possibility that this list of terms left to be obsoleted might be very small.
Spreadsheets:
run the same code as previously (Harshad's code) for the 4 branches above, using the list of terms to be obsoleted above.
The spreadsheet includes: all children of terms to be obsoleted + their parents in and outside the branch + their ancestors in and outside the branch.

The results can be found here

Thank you @hrshdhgd
Could you please re-run them again, but remove the following from the list of terms to be obsoleted (they have been removed from the obsoletion candidate list):
MONDO:0019054
MONDO:0015338
MONDO:0019713
MONDO:0015337
THANK YOU!

@sabrinatoro can this be closed?

Yes, this has been done. Closing.


Guide users to not install R versions of PowerCLI

I had an issue at a customer where we installed the latest R version of PowerCLI on our processing server which caused a significant amount of troubleshooting for a week.  We lost a lot of time.  We couldn't uninstall the R3 version and just install "RTM" as when R3 is installed, the code is stuck in there even when installed 6.0.  We had to rebuild our processing server from scratch.  When you look at the download page, I believe you are compelled to want to get the latest version, which is the issue we got stuck on.  The edit is to try and avoid other pros from making this mistake.

Hi @RudiGroenewald, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@RudiGroenewald : Thanks for your contribution to the Azure documentation! The author, @rayne-wiselman, has been notified to review your proposed change.

correct but language needs changes
Please change from : "Ensure to install Version 6.0 and not the R versions"
To: "Currently other versions of PowerCLI aren't supported, including R releases of version 6.0."
@azurecla

Changes done!  Thanks @rayne-wiselman

Thank you for  your contribution Rudi. Great to see folks participating in our documentation!
From: Rudi Groenewald<EMAIL_ADDRESS>Sent: Friday, June 17, 2016 4:42 PM
To: Azure/azure-content<EMAIL_ADDRESS>Cc: Rayne Wiselman<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-content] Guide users to not install R versions of PowerCLI (#6842)
Changes done! Thanks @rayne-wiselmanhttps://github.com/rayne-wiselman
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-content/pull/6842#issuecomment-226771566, or mute the threadhttps://github.com/notifications/unsubscribe/AD2-iD7rIIMovaDbYvPnXvMwVSHFGH2Aks5qMqQcgaJpZM4I32ox.


Could add a classname to addon-info proptype table

Is your feature request related to a problem? Please describe.
I need add style to the prop-types table whithout influencing the showing "Table" component by addon-info，I use the less，but it's diffcult to use css selector only selecting the proptypes table element without influencing the  coomponent I display.
Describe the solution you'd like
Adding a className for the proptypes table element is a nice choice
Describe alternatives you've considered
providing a api to set the className is also great.
Are you able to assist bring the feature to reality?
If needed, yes

You can override options.TableComponent so you can literally put whatever you want in there?

yes，I know that way. But the options.TableComponent seems  to override table render，what I want is just adding a className to make the div wapper or table more semantic.Tanks for your reply~


Enyo-1171 Add webkit keycode of backspace for keyboard

Issue
HistorySample does not work when we use USB keyboard
Cause
keymap.js did not have keycode for back space key in keyboard
Fix
Add keycode into keymap.js
Note
'0x8' is webkit keycode of backspace key. It is not reserved from any other keys of remote controller yet. However we'd better get confirm from Architect.
Enyo-DCO-1.1-Signed-off-by: David Um<EMAIL_ADDRESS>

Closing out as Jira linked to this has been closed.


Add empty parens to var-to-function renames

What's in this pull request?
This adds empty parens when a var is renamed to a function of no arguments.

Resolved bug number: (SR-1649)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

LGTM.
@swift-ci please smoke test and merge.

@swift-ci please smoke test and merge.

It looks like the smoke test skipped building Swift entirely?

I saw this flutter earlier too. Let's just do it again.
@swift-ci Please smoke test Linux platform

@swift-ci please smoke test Linux platform.

@swift-ci please smoke test Linux platform.


[core] Output ES code in /es

Hey!
There was some discussion over in #5952 with the result that material-ui should publish a non-transpiled / minimally transpiled version of the source code as well. This offers better build sizes to people that know their target browsers well and do the transpilation / polyfilling themselves.
I've changed the build process so that it outputs a true ES6 version (instead of just a module file) along the ES5 one. module / esnext:main-definitions have been updated accordingly.
Discussion: Is babeling to ES6 already "too much" compilation, does publishing a stage-x-free release make more sense?

The final version
We push #5952 further with a /es folder alternative of the modules using all the latest ES features.

I had to inline the global babel presets / plugins because babel would normally merge those which would put us back where we started generating plain old ES5.

@NeoLegends Babel is about to add a js version of the configuration file. Maybe we can take advantage of it. I'm not sure if it's in babel@6 or babel@7

Discussion: Is babeling to ES6 already "too much" compilation, does publishing a stage-x-free release make more sense?

I think that we should be releasing a pure ESnext version of the modules. Something that matches the latest official supported features of the language. Nothing more (stage-x), nothing less (require, etc).

I think that we should be releasing a pure ESnext version of the modules. Something that matches the latest official supported features of the language. Nothing more (stage-x), nothing less (require, etc).

I like this idea. Seems like we need to output that do a different folder tho. Can webpack be made to automatically reference /src when importing from material-ui?

@oliviertassinari I updated the PR.

@NeoLegends Babel is about to add a js version of the configuration file. Maybe we can take advantage of it. I'm not sure if it's in babel@6 or babel@7

.babelrc.js seems to be a feature of Babel@7, which is not finished yet.

I think that we should be releasing a pure ESnext version of the modules. Something that matches the latest official supported features of the language. Nothing more (stage-x), nothing less (require, etc).

The build process now generates ESNext code. 🎉

@NeoLegends Thanks

@oliviertassinari A question: as the v1-beta branch isn't stable yet, wouldn't it be possible to do a breaking change here and use this as an opportunity to clean up the old way of handling the module-field in package.json? Seems like something is off when one uses a bundler that understands module but depends on ES5 code.

@NeoLegends We introduce breaking changes from time to time. I don't think that it's the old way of doing it. As far as I know, it's still the standard way of handling the module key.


Ticket 4539. Fix/Adjustment to exception handling in request-management api

Python 3 exceptions do not have a message attributes. See PEP 352 for more details.
Please see corresponding docreviewer PR here: https://github.com/bcgov/foi-docreviewer/pull/560

This branch/PR is reverted. New PR is found here https://github.com/bcgov/foi-flow/pull/4619/files


cmd/compile: impossible type assertion reports wrong signature for methods that don't match in case

What version of Go are you using (go version)?

$ go version
go version devel go1.18-6eb58cdffa Tue Jan 25 22:56:45 2022 +0000 linux/amd64

Does this issue reproduce with the latest release?
No.
What did you do?
https://go.dev/play/p/M_0U_6fSpFp
What did you expect to see?
./foo.go:17:7: impossible type assertion:
	T1 does not implement I (missing Foo method)
		have foo()
		want Foo()
./foo.go:18:7: impossible type assertion:
	T2 does not implement I (missing Foo method)
		have foo() string
		want Foo()

What did you see instead?
./foo.go:17:7: impossible type assertion: i.(T1)
	T1 does not implement I (missing Foo method)
		have foo() at ./foo.go:9:11
		want Foo()
./foo.go:18:7: impossible type assertion: i.(T2)
	T2 does not implement I (wrong type for Foo method)
		have foo() string at ./foo.go:13:11
		want Foo()

The compiler complains about the wrong signature even though the method names don't match, which I think is the more important error to report. Bisects to 429d1e01557f95bba29837f2190441696484fd41.
/cc @danscales

Thanks for the example.    The error message should be fixed in this case, which will be like what it is in Go 1.17.  I have a simple fix, but it may wait until after beta-2.