[Bug]: Checkout progress again and again, makes obsidian mobile cannot work well

Describe the bug
I just update the obsidian-git plugin to latest, and when I using on mobile, it will hint "Checkout progress: Analyzing workdir: xxxx". Seem like scanning something, but do this over and over again. I don't know why it happened. When scanning, I cannot search or open markdown file. It won't give the result until the checkout stopped.
Relevant errors (if available)
No response
Steps to reproduce

Start Obsidian APP

Expected Behavior
No response
Addition context
No response
Operating system
Android
Plugin version
2.4.1

Do you have auto backup turned on? It might try to commit everything. The interval might be very low.

Same issue in mobile. Checkout progress shows every time I try to pull. Taking roughly 30 secs which makes it impossible to use. Auto backups are disabled.

I don't think that's fixable. See the added warning in the documentation


CSS rules are accumulated when doing SSR with<EMAIL_ADDRESS>

Environment
System:

OS: macOS High Sierra 10.13.3
CPU: x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Free Memory: 409.59 MB
Total Memory: 16.00 GB
Shell: /bin/zsh - undefined

Binaries:

Node: 8.9.4
Yarn: 1.5.1
npm: 5.6.0
Watchman: Not Found

npmPackages:
styled-components:

wanted: ^3.2.1
installed: 3.2.1

Reproduction
Couldn't think of a nice way to reproduce this without creating a SSRed app with multiple entry points, which would have different styles.
Current relevant parts of the setup
async function renderHtmlDocument({ history, store, sagasDone, webpackStats }) {
  // 1st render phase - triggers the sagas
  renderToString(<Main history={history} store={store} />);
  // send signal to sagas that we're done
  store.dispatch(END);
  // wait for all tasks to finish
  await sagasDone();

  // capture the state after the first render
  const state = store.getState();

  // taken straight out of documentation
  const sheet = new ServerStyleSheet();
  // 2nd render phase - the sagas triggered in the first phase are resolved by now
  const appMarkup = renderToString(
    sheet.collectStyles(<Main history={history} store={store} />)
  );

  const css = sheet.getStyleTags();
  const { cssHash, js, styles } = flushChunks(webpackStats, {
    chunkNames: flushChunkNames(),
  });

  const head = Helmet.rewind();

  return `<!DOCTYPE html>
  <html lang="en" ${head.htmlAttributes.toString()}>
    <head>
    ...
    <!-- Inlined first render css -->
    ${css}
   ...
  </head>
  <body>
    ...
  </body>
</html>`;
}

Steps to reproduce

SSR a page.
Navigate to any other page. Do a refresh so that the page is SSR'ed.
Go back to the previous page and SSR it.

Expected Behavior
index.html file should not include CSS rules for other pages that were SSR'ed. Quick way to check this is if index.html file is of the same size.
Actual Behavior
index.html file includes CSS rules for other pages that were SSR'ed (it visibly increases in size).
I can reliably reproduce this on our site by installing<EMAIL_ADDRESS>or above<EMAIL_ADDRESS>works fine with the same setup. The issue described above leads to index.html becoming so big (140kb+) that it takes 20s+ for the browser to parse it, which often crashes a mobile browser.
I hope there's something immediately obvious that you guys changed from 3.1.6 to 3.2.0 that led to this behaviour, but if not, let me know if you need more info.

@kitten this sounds like a bug in your StyleSheet rewrite

Any news @kitten? Any hunches why this happens?

@mxstbr didn’t have any time yet to take a look :) also have to build a reproduction but since I’ll be more busy in the coming days, I’ll have to find a free evening to work on this

Had a quick look; I think I messed up ServerTag#clone; I’ll push a fix this eve

@DeividasK Hiya, pushed out a quick fix since this wasn't too complex to fix and just a messup 😅 Can you help me test the fix please? It's published as  v3.2.2-0 under styled-components@dev

FWIW, the v3.2.2-0 release resolves an issue with snapshot tests that I was just about to report :sweat_smile: (all styles were disappearing from nested components). So I assume jest-styled-components is also affected by this.

@kitten Hey Phil, I've checked it and it does not fix the issue.

@DeividasK sorry, I'm really under the weather today; I've messed up one of the clone functions again — let me push out another commit and prerelease;

@kitten sorry for taking a bit to respond, but I wanted to double check this - it seems that the styles rules are still being accumulated (based on the increasing index.html size). I will double check the actual output of styled-components tomorrow and will let you know.

@DeividasK that might just be our component comment markers. If so, I’m aware of that regression but it’s intended as long as we’re waiting for some ppl who’re relying on that (not for SSR)

@DeividasK v3.2.2 is now released with the fix in place :) https://github.com/styled-components/styled-components/releases/tag/v3.2.2

@kitten We are seeing this leak in our prod servers at Weedmaps. We just hotfixed to update to 3.2.2 and I think we are still seeing similar behavior. Here is a snippet from a heap dump -

Environment -
Alpine Linux 3.7.0
Styled Components - 3.2.2
Node - 9.7.0
Express - 4.16.3
NextJS - 5.0.0
We are using the following method to collect our styles (basically the example from the NextJS repo)

export class DeliveriesDocument extends Document {
  static async getInitialProps({ renderPage, req }) {
    const sheet = new ServerStyleSheet();
    const page = renderPage(App => props =>
      sheet.collectStyles(<App {...props} />),
    );
    const styleTags = sheet.getStyleElement();
    return {
      ...page,
      styleTags,
    };
  }

  render() {
    const { styleTags } = this.props;
    return (
      <html lang="en">
        <Head>
          {styleTags}
        </Head>
        <body>
          <Main />
          <NextScript />
        </body>
      </html>
    );
  }
}

@kitten we aren't seeing the accumulated styles being flushed into the DOM, but it seem they are still being retained

@kitten I see clones, deferred, tagMap grow

@kitten I have not dug into styled-components source too much, but debugging your tests, I see you assert that the generated style tags do not bleed over, however I am seeing the tagMap instance on the Stylesheets contains two values for each Sheet, when it should contain 1. If I comment out SheetB, then SheetA only contains 1 tag in the tagMap - Debugging done on the test here - https://github.com/styled-components/styled-components/pull/1605/files#diff-ff4f58ec4bfe127b48d620e3f45853e5R68

@bringking yep, that’s all still expected behaviour and as it worked before. At any point in time we need to preserve the order of components that were created.
If you’re seeing a growing tagMap that just means that you’re encountering new components over time. We can probably optimise this in the future, but for now please open a new issue if this really bothers you, as this was how it already worked pre-3.2 ;)

@kitten I can confirm that 3.2.2 works the same way as 3.1.6. As you've mentioned, some markers are being accumulated, but that is the same behaviour as in 3.1.6.

@kitten @DeividasK, thanks for the info we will keep digging. We are still seeing rapid memory growth with 3.2.2, but I want to get a solid repro case for you and I will open another issue if it is something in styled-components. Thank you guys!

@bringking @DeividasK I've got an easy modification here, which I was aware would help with this but left out during the refactor to keep everything the same.
https://github.com/styled-components/styled-components/pull/1612
It's published under the ssrmem tag. Can you two take a look at that PR, test the prerelease and report whether it improves the situation please? 👍🙌
I'll lock this issue for now, so that no one gets your discussion confused with the original issue :wink: Sorry about that, let's move the discussion to the PR


Failed to create file or rename to 'aux'

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

VS Code Version: 1.95.3
OS Version: Win11 24H2 26100.2314

Steps to Reproduce:

Create new file or just rename, and name as 'aux.h' or 'aux.cpp'
Show 'The name aux is not valid as a file or folder name. Please choose a different name.' Failed to save file

Honestly this sounds like the issue is by design...  Windows has reserved file name , without looking further you'll have this errors with:
prn
aux
con
Old age... I thought there are 5 i can only remember 3....   Searching...
Do not use the following reserved names for the name of a file:
CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9

Honestly this sounds like the issue is by design... Windows has reserved file name more a hold over from MS-DOS, and backward compatibility... Wiithout looking further you'll have this errors with:
prn aux con
Old age... I thought there are 5 i can only remember 3.... Searching, i found...
Do not use the following reserved names for the name of a file: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9

Thx. I try to manually rename to 'aux.h' in file explorer, and it success. But when I create a folder name 'aux', it shows an errror. I think 'aux.h' is legal as file name.

Either way i don't think even using the file name portion at all is wise exactly for the reason mentioned be it a file or dir,  I would think this will be closed by design...


party-robot: missing prerequisites

The party-robot exercise uses string, the int and float64 types, but its prerequisites don't ensure that the student has learnt these concepts.
The numbers and strings concepts should be added as the prerequisite of the party-robot exercise.

We can't do this yet:

strings depends on numbers, which depends on constants, which depends on strings forming a cycle:

Should be possible after #1625 is done.

This depends on issue #1613 to re-add the strings concept.
With that done the savings-account exercise needs to change to depend on strings rather than string-formatting - which is more correct, and also breaks a dependency cycle we get otherwise. We can then make this change to add these dependencies to the party-robot exercise.


Rewrite the interface of Target for encapsulation.

Limiting direct access to the members of Target lead to a lot of discoveries about the organisation of Downloader and zck data and functions, which is why this commit is quite bigger than initially expected. 😬
Some code have been moved from Downloader to Target member functions as they are mainly manipulating the state of Target without much changes to Downloader, which basically is a sign that it's code related to Target.
This is really just side effects of trying to make the Target interface more contained. Because a lot of other code was manipulating it's internals directly, it ended up touching a lot of code.
Where possible I tried to keep the order and meaning of the code when I had to move it around.
More info and discoveries (to help lead the related PRs that will come soon):

There is multiple accidental data structures hidden in Target, most related to different aspects of a download process.
This makes difficult to follow which states Target can take and when (there is also a lot of redundancy in how Target's state is changed).
Target, Downloader and zck data/functions are intertwined in a way that suggests there is a several separation necessary (but I didn't proceed where I didn't need to, for now) - basically this lacks "separation of concerns" and should be improved.
Both Target and zck seems to be internal details of Downloader's mechanisms, which is fine, but it also means we should not expose them as public interfaces (I think, or at least not completely).
Downloader::check_msg seems to have at least 3 transfer error flags that might be contradictory; this makes difficult to understand which flag means what kind of error.

All this will probably participate to complications in evolving libpowerloader, but we are in a good position and time to improve the situation. :)

Looks like the python tests are "blocking" somewhere test/test_other.py. I'm reviewing to check which code changed order or meaning compared to main branch.


C# and Visual Studio Code: Connecting Signals from the GUI doesn't add a method.

Godot version: v3.2.2stable.mono.official
OS/device including version:Windows 10  (Build 18363)
Issue description:
When connecting a signal via the GUI, the new signal method is not being added to the script.
Steps to reproduce:
Under Editor Settings -> Mono I have the External Editor set as "Visual Studio Code". Tried this on multiple projects (going through the tutorial series)
Minimal reproduction project:
N/A
Apologies if this isn't a bug or has been reported. I couldn't find it but the tutorials are implying it should append the method template. I am wondering if it's because it's C# and/or an external editor? I've tried completely closing the file in VSC and connecting signal but it just never appears in the file regardless of text editor I open it in.

Duplicate of https://github.com/godotengine/godot/issues/23208.


Make the Document Store More Robust

Currently, the document store is built on top of the key-value store UnQLite. It responds to error results from UnQLite without checking to see what the specific error is. This means that there are situations that the document store will not handle well. For example,

If the error code indicates that the operation could not proceed because another thread's transaction had a lock, the document store will treat the operation as a failure rather than waiting and retrying.
UnQLite is written in C and manages its memory independently of RUST. If a return code indicates that UnQLite is out of memory, rather than attempting to somehow restart UnQLite the document store will treat it as a normal failure and continue to call UnQLite expecting additional operations to succeed when they won't.
If UnQLite returns a failure indicating that it cannot open a file due to permission errors, the document store will be unaware of the situation and not report it.

To improve this, one of the following three things should be done:

Modify the document store to respond to specific error statuses in an appropriate way. Currently the only way for the document store to tell what the specific UnQLite error is, is to look at the error string associated with the error by the Rust wrapper. A complete list of these is in UnQLite's error.rs:

    pub fn error(&self) -> &str {
        match self.kind {
            ErrorKind::NOMEM => "Out of memory",
            ErrorKind::ABORT => "Another thread have released this instance",
            ErrorKind::IOERR => "IO error",
            ErrorKind::CORRUPT => "Corrupt pointer",
            ErrorKind::LOCKED => "Forbidden Operation",
            ErrorKind::BUSY => "The database file is locked",
            ErrorKind::DONE => "Operation done",
            ErrorKind::PERM => "Permission error",
            ErrorKind::NOTIMPLEMENTED => "Method not implemented by the underlying Key/Value storage engine",
            ErrorKind::NOTFOUND => "No such record",
            ErrorKind::NOOP => "No such method",
            ErrorKind::INVALID => "Invalid parameter",
            ErrorKind::EOF => "End Of Input",
            ErrorKind::UNKNOWN => "Unknown configuration option",
            ErrorKind::LIMIT => "Database limit reached",
            ErrorKind::EXISTS => "Record exists",
            ErrorKind::EMPTY => "Empty record",
            ErrorKind::COMPILE_ERR => "Compilation error",
            ErrorKind::VM_ERR => " Virtual machine error",
            ErrorKind::FULL => "Full database (unlikely)",
            ErrorKind::CANTOPEN => "Unable to open the database file",
            ErrorKind::READ_ONLY => "Read only Key/Value storage engine",
            ErrorKind::LOCKERR => "Locking protocol error",
            ErrorKind::OK => unreachable!(),
            ErrorKind::__Nonexhaustive => unreachable!(),
        }
    }

A drawback of this approach is that if any of the wrapper's error messages ever change, they will not be recognized by the document store.

Modify the document store to respond to the numeric error status produced by UnQLite.
The error that is returned by the UnQLite wrapper is a struct named Custom. It contains the numeric error status returned by UnQLite and the ErrorKind enum variant that the wrapper associates with the numeric error status. Unfortunately, the wrapper has these fields declared private and no methods are provided to access the fields.
I have created an issue for UnQLite to fix this. Since the most recent commit to UnQLite at the time of this writing is 15 months ago, we many find that the maintainers of UnQLite will not respond to this issue in a timely manner. If this is the case, we may consider making the fix in our own fork of the UnQLite wrapper.

Replace UnQLite with Sled. Sled is actively maintained and is 100% Rust.  I suggest this because we may eventually have to replace UnQLite anyhow. The reason for that is that UnQLite is thread safe only on Windows and Unix-like operating systems. To make it thread safe on other operating systems, we would have to add another operating-system-specific mutex mechanism to UnQLite.
Since Sled is all Rust, it goes anywhere Rust goes. The reason that I suggest switching before MVP is that it allows us to avoid the headache of having to write a utility to convert UnQLite files to Sled.

UnQLite is no longer being used for the underlying database.


Add a rule to enforce TypeORM's Relation<...>-wrapper

When migrating to ESM this wrapper is required to avoid dependency conflicts. The new rule enforce-relation-wrapper avoids to forget this wrapper and makes migration to ESM on an existing codebase pretty easy (since are not updated by hand)
See: https://typeorm.io/#relations-in-esm-projects
Additionally I added support for this wrapper also to the existing rules, that they do not raise issues if references are wrapped as e.g. Relation<Other>
Happy to discuss this!

Thank you for your contribution!
My question is, could this rule be part of enforce-relation-types? One could define "enforce-relation-types": ["error", {"relationWrapper": true}] and it would handle both the correct inner types, and require the wrapper to be around it. I didn't have time to look at the code extensively, can you tell me why you opted for the separate rule?

TBH I did not think about this. I wrote the rule a while ago and now decided to publish it, found your repository and here ist the PR...
I think it could be part of the enforce-relation-types rule. However I made some more advanced attempts to respect existing imports and aliases if applicable and would still proceed to maintain. If I merge the rules I would also apply these to existing rules.: E.g. when import { OneToMany as OTM } from 'typeorm', this alias is maintained and considered (although this kind of "type-checking" is not actually part of eslint, but gave a bit more stability in my particular case). This would also affect the existing rules.
However, if you are fine with that I would merge these rules and update the PR as soon as I find the time

I looked at your code, and decided to combine the rule with the already existing enforce-relation-types. Actually it was much simpler than expected, since I already had another wrapper type for lazy relations (Promise<T>), so I just needed to change that a little. I also added support for forcing every relation to Relation<T>, I put together these in #18. Feel free to take a look at it, and I will put out a new version in the following days.
As far as the import aliases go, I eventually decided against it. I don't really know any ESLint rule that looks at or changes imports and even though it could be a cool feature, it would be very niche usage. I hope you don't mind it, I just didn't want to add the extra maintenance overhead. Thanks for your contribution anyways.

I merged this in #18, thank you for raising this issue.


fix issue #22

fix "ValueError: Shapes are not compatible when training transition model after autoencoder trained" and make the code compatible with recent versions of Keras.

@geohot this is an update required by recent tensorflow

thanks


AWS SES

Hello,
The AWS SES app is missing the possibility to use the "reply to" field of an email

Hey @shalin24999, could you have a look at this?

Hey @tristandostaler could you please check 257. Is this what you suggested?

Yes that seems right!
If it's worth anything, the lines 59 to 104 could be simplified without the if, hence reducing the code duplication. The only difference is "text" vs "html".
There could be a if before, or a function call with the type.
Ex if you want to default to Html:
email_type = "Html"
if data_option != 'Html':
email_type = "Text"
response = client.send_email(
(...)
'Body': {
email_type: {


Fixes to the documentation

This PR fixes some issues in the documentation. Recommend going through each commit to see what each change is. In summary:

Fixed missing quotes in odm-how-to qmd fikle
Updated all parts sheet to have a firstRelease and lastUpdated columns
Updated the invalid_category rule specification to allow missing values in a categorical column
Made the file names consistent for the invalid_type rule assets

@zargot I may need your help with some of your commits appearing in this PR. They're not in the dev branch so I assume they were deleted in a rebase. Should I just rebase dev?

This PR fixes some issues in the documentation. Recommend going through each commit to see what each change is. In summary:

Fixed missing quotes in odm-how-to qmd fikle
Updated all parts sheet to have a firstRelease and lastUpdated columns
Updated the invalid_category rule specification to allow missing values in a categorical column
Made the file names consistent for the invalid_type rule assets

@zargot I may need your help with some of your commits appearing in this PR. They're not in the dev branch so I assume they were deleted in a rebase. Should I just rebase dev?

@yulric, yes, you can simply rebase your 4 commits onto dev, discarding the others.
This can be done in a few ways:

git rebase --onto dev HEAD~4
git rebase -i dev, then delete the lines for the other commits.

This PR fixes some issues in the documentation. Recommend going through each commit to see what each change is. In summary:

Fixed missing quotes in odm-how-to qmd fikle
Updated all parts sheet to have a firstRelease and lastUpdated columns
Updated the invalid_category rule specification to allow missing values in a categorical column
Made the file names consistent for the invalid_type rule assets

@zargot I may need your help with some of your commits appearing in this PR. They're not in the dev branch so I assume they were deleted in a rebase. Should I just rebase dev?

@yulric, yes, you can simply rebase your 4 commits onto dev, discarding the others. This can be done in a few ways:

git rebase --onto dev HEAD~4
git rebase -i dev, then delete the lines for the other commits.

Thanks! Should be good for you to review now.


Style options to remove street names, underlying tile bitmap

So is there a way with the MapZen API to get tiles with no street names on them and no bitmap image for the tile? It seems like these tiles have buildings and roads as vector objects built on top of a tile bitmap that has the street names etc. on them. Can we have options to choose tile styles? I really just want to show the 3D roads / water / land / buildings, but not the tile bitmap.

Oh wait this is already there, with the load images bool--duh!


Dashboard fails when project in subdirectory 404s

Installing laravel-websockets in a project that resides in the subdirectory of a fqn, the dashboard xhr request paths are incorrectly formed.  It can be hacked to work by overriding dashboard.blade.php with static path values... less than ideal.
So when we have an installation like this...
www.example.com/mysite/laravel-websockets
line 121 dashboard.blade.php
authEndpoint: '{{ request()->path() }}/auth',
Produces xhr requests 404
I can overcome this by changing line 121 ans 165 of dashboard.blade.php to a static path prefix
line 121 - authEndpoint: '/mysite/{{ request()->path() }}/auth',
line 165 - $.getJSON('/mysite/{{ request()->path() }}/api/'+this.app.id+'/statistics', (data) => {
A dynamic solution is required, passing an install path from websockets.php or changing {{ request()->path() }} to the correct complete path...
I found a post on stack which provides more background...
https://stackoverflow.com/questions/60018500/laravel-websockets-dashboard-base-path-with-sub-folder-not-working

In dashboard.blade.php I replaced request()->path() with Request::getRequestUri() on line 121 and 165, that provides a dynamic solution in Laravel 6.

https://github.com/beyondcode/laravel-websockets/pull/434


Not compatible with elasticsearch>=1.8.0

Changes in elasticsearch 1.8.0 are not compatible with the current version of elasticutils. bulk_index has been depricated.

ElasticUtils is a dead project and hasn't had any activity since March. You should switch to a different Elasticsearch library or, if you must, use an older version of elasticsearch-py.

Thanks for the headsup


HOT Reloading shows the previous change

Description
I have this issue where HOT reloading works perfectly, but in the Simulator it shows the previous change instead of the current one.
Reproduction Steps and Sample Code
Lets say I have a <Text>12</Text>
If I change it to <Text>123</Text> the Simulator shows on screen : 12
If I change it to <Text>1234</Text> the Simulator shows on screen : 123
If I change it to <Text>12345</Text> the Simulator shows on screen : 1234
....
.... and so on
Works fine but just with 1 step behind.
Additional Information

React Native version: 0.44.0
Platform: iOS
Development Operating System: macOS
Dev tools: Visual Code

Any chance you can get the exact list of steps that got your project into this state?

Closing this issue as we haven't heard back from the author.


added Equality Comparison topic for

for #12 issue
added this
/equality_comparison/
│
├── README.md
├── loose_vs_strict.md
├── object_comparison.md
└── deep_comparison.md
also please add hacktoberfest , hacktoberfest-accepted label

@mohitahlawat2001 having merge conflicts.
can you take latest pull from main branch.

@neerajrathore i make change please merge this before anyone else , other wise may be new conflict comes


added vercel.json

Configured vercel.json to avoid navigating issues like this:

Added a vercel.json file to the project.
`{ "rewrites": [{ "source": "/(.*)", "destination": "/" }] }

Fails up the Production Deployment


To make it work with DS 6.2

Maybe this should be comment rather than an issue?
(Sorry for 1 more issue, but I hope it's useful)
To make the Dockefile work with DS 6.2, there are 3 important changes that are needed
Obviously, the first line should change from:
FROM nvcr.io/nvidia/deepstream:6.1-devel
to
FROM nvcr.io/nvidia/deepstream:6.2-devel
But there are 2 more things:

Add this line after line 7:
ENV CUDA_MODULE_LOADING=LAZY
That's new in 6.2 and I presume it will be ignored in 6.1 and before

Add this line between current line 15 and 16:
RUN bash /opt/nvidia/deepstream/deepstream/user_additional_install.sh
As that will install the extra libraries taht are no longer part of the default package since 6.2

Do you have a repo fork somewhere with code to get started? If so, I could take a look

Hi Joxis,
I'm afraid not. I was just doing some edits locally to make it work and understand how it works. But all the changes to 6.2 are mentioned in the first post. Just the additional libraries are the issue.
(Feel free to close the tickets if it's not worth it. I'll take no offense)

How to use this repository with the yolov5 model as well as the custom yolov5 model?


chore(deps): replace deprecated Google protobuf module

Motivation: When importing a new dependency e.g. go get k8s.io/kubernetes/pkg/controller/deployment/util (probably others), the command would fail due to the deprecated package.

Verified this works with our WIP Prometheus 2.45 build. Merging!


Enable Report Card.

Generates a Report Card of how well your repo meets Clever's best practices.
Its result is visible via GH Status hook, and you can see all details by looking in Drone's output.
For context, see https://clever.atlassian.net/browse/INFRA-1577.

This PR was autogenerated. You were assigned this PR as the most active committer to this repo (or because @nathanleiby chose you). Congrats!

LGTM


bump 21w38a

add support for 21w38a fapi 0.40.4

I will only support release versions of Minecraft.


Support custom fonts

Description
Will Marimo support custom font configuration for cell display? It's a bit regrettable that such a beautiful notebook cannot have custom fonts.
Suggested solution
Can choosing code fonts and ligatures, such as Fira Code, selection different languages fonts (mainly non-English text).
Alternative
No response
Additional context
No response

While the css variables we use are not quite a supported API - you can override this if you'd like.
After this PR is released, you can do something like:
import marimo as mo

# Load the font and override the css vars
mo.Html(
    """
<link href="https://fonts.googleapis.com/css?family=Happy+Monkey" rel="stylesheet">

<style>
    :root {
        --text-font: "Happy Monkey", cursive, sans-serif;
        --heading-font: "Happy Monkey", cursive, sans-serif;
    }
</style>
"""
)

If this fits your needs, happy to support this. Otherwise open to discuss further font customization

@GrahLnn , we just released 0.1.81, which lets you do what Myles suggested in the previous post. Let us know if that works for you.


Querying for multiple tags generates the wrong query

Welcome to Ghost's GitHub repo! 👋🎉
We use GitHub only for bug reports 🐛
Anything else should be posted to https://forum.ghost.org 👫
🚨For support, help & questions use https://forum.ghost.org/c/help
💡For feature requests & ideas you can post and vote on https://forum.ghost.org/c/Ideas
If your issue is with Ghost CLI, please report it on the CLI repo ➡ https://github.com/TryGhost/Ghost-CLI/issues/new.
Issue Summary
When doing a filter like "tags:one+tags:two" it will not returns posts which have both one and two as tags.
The generated sql is:
select `posts`.id from `posts`
    left outer join `posts_tags` on `posts_tags`.`post_id` = `posts`.`id`
    left outer join `tags` on `posts_tags`.`tag_id` = `tags`.`id`
    where (`posts`.`status` = 'published' and `posts`.`page` = false)
        and (`tags`.`slug` = 'one' and `tags`.`slug` = 'two')
group by
    `posts`.id, `tags`.slug
order by
    CASE WHEN posts.status = 'scheduled' THEN 1 WHEN posts.status = 'draft' THEN 2 ELSE 3 END ASC,
    CASE WHEN posts.status != 'draft' THEN posts.published_at END DESC,posts.updated_at DESC,posts.id DESC
limit 15

When doing multiple queries for a field it should generate a new outer join with an alias and the condition or use a subquery on the join.
To Reproduce
Try to filter multiple tags using {{#get}} for example.
Technical details:

Ghost Version: 2.1.4
Node Version: 8.12
Browser/OS: chrome
Database: JawsDb mysql

This is a duplicate of https://github.com/TryGhost/GQL/issues/16, it only affects the old GQL (used when using the API directly, or with the get helper).
It does not affect NQL+JSON (used in dynamic routing).
We are slowly moving over to NQL (but still need to implement joins for NQL+SQL, correctly this time).

@ErisDS How do I use NQL. My filter is part of dynamic routing.

@ErisDS I don't think this is working. I just added this route.
  /:
    permalink: /{slug}/
    filter: tags:-[article,unit,activity]
    template:
      - index

And the SQL it produces is:
select `posts`.*
from `posts`
	left outer join `posts_tags` on `posts_tags`.`post_id` = `posts`.`id`
	left outer join `tags` on `posts_tags`.`tag_id` = `tags`.`id`
where (`posts`.`status` = 'published'
	and `posts`.`page` = false)
	and (`tags`.`slug` not in ('article', 'unit', 'activity'))
group by `posts`.`id`
order by CASE WHEN posts.status = 'scheduled' THEN 1 WHEN posts.status = 'draft' THEN 2 ELSE 3 END ASC,
	CASE WHEN posts.status != 'draft' THEN posts.published_at END DESC,posts.updated_at DESC,
	posts.id DESC

This does not remove items with those tags from the listing.

This bug was fixed in Ghost 2.8.0.


scroll position not reset on SRP -> PDP

When scrolled down on the search results page and clicking on an item, scroll position is not reset.

Hello @jeffrey-slentz-algolia can you just maybe record what's wrong? I'm not sure than I have the same issue:
https://share.getcloudapp.com/jkuW7Enq

Looks like it's because your PDP fits inside your vertical screen height. If it had a scroll-bar, it might present the issue. You can arbitrarily increase the height of the PDP to test?


Add email and random number authentication

Hi,
I'm creating a project at work using Serverpod, and I don't want users to have to remember yet another password. I plan to have them enter their email, then the server will email them a random 6-digit passcode which they can put into the server. Rather like the current implementation, but without the password, and with the added benefit of logging them out if they've not made a request in a certain amount of time.
Firstly, I ain't a security expert. I just know how fragile passwords are. Is this a terrible idea? My bank do it, so I'm thinking not, but I'd rather get a second opinion from you lovely people.
Secondly, if I make this, is it a feature that the team would consider adding back into Serverpod?
Thanks for a wonderful package. I look forward to any replies.

Hey @ChrisCRCB!
This sounds very much like Slacks magic link and is basically just a multi factor authentication where possession of the email is the means of authenticating the user.
I'm not a security expert either, so the advice given below only reflects my personal thoughts and are not best practices.
There are a couple of things I would take into consideration:

Email service security - The schema would rely on the security of the email service, this should be the same as if a user request a password reset but is good to keep in mind (which is basically what your 6-digit passcode would represent).
Brute force concerns - Make sure there are mechanisms to protect from brute force attacks. This could be limiting the number of tries agains a validation code before it is removed together with a short time window for when the code works.

This sounds like a neat feature to provide and would be cool to include. But for it to be included in the auth modules in Serverpod it would need to be a good implementation that is well tested and documented.


refactor: cleanup

This PR features basic refactoring and cleaning up.
Users may receive some errors if they were using SernEmitter directly. This class has been removed

Removed the localization feature of this branch. this has turned into a refactor branch.
Localization is moved to sern/tools

By at least tomorrow, this might be a patch I gotta review it again
Vào Th 5, 8 thg 2, 2024 lúc 12:31 CH SrIzan10 @.***> đã
viết:

ready to merge?
—
Reply to this email directly, view it on GitHub
https://github.com/sern-handler/handler/pull/348#issuecomment-1934711859,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASJS6O6IWX4VF3JBTGH2TTTYSUKYTAVCNFSM6AAAAABBNN3JGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZUG4YTCOBVHE
.
You are receiving this because your review was requested.Message ID:
@.***>

@SrIzan10 rereview, I think everything will be alright


Compile grpcio fail in rust:latest Docker container.

Describe the bug
Compile grpcio fail in rust:latest Docker container
To Reproduce
I have a project which depended on grpcio. In Cargo.toml: grpcio = "0.4"
I made a Dockerflie like:
FROM rust:latest

WORKDIR /temp_project

COPY . .

RUN apt-get update\
    && yes yes | apt-get install cmake \
    && cargo install --path .

then I try to build image docker build.
After all, I received error messages:
-- Configuring incomplete, errors occurred!
See also "/temp_project/target/release/build/grpcio-sys-037849703dbc0a9e/out/build/CMakeFiles/CMakeOutput.log".
See also "/temp_project/target/release/build/grpcio-sys-037849703dbc0a9e/out/build/CMakeFiles/CMakeError.log".

--- stderr
CMake Warning at cmake/protobuf.cmake:48 (message):
  gRPC_PROTOBUF_PROVIDER is "module" but PROTOBUF_ROOT_DIR is wrong
Call Stack (most recent call first):
  CMakeLists.txt:140 (include)

CMake Error at third_party/boringssl/CMakeLists.txt:38 (message):
  Could not find Go

thread 'main' panicked at '
command did not execute successfully, got: exit code: 1

build script failed, must exit now', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.42/src/lib.rs:861:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Expected behavior
Build success.
System information

CPU architecture: x86_64
Distribution and kernel version: Linux 4.9.184-linuxkit x86_64
SELinux on?: No?
Any other system details we should know?:

Additional context
Found this issue has same error message return:
https://github.com/pingcap/grpc-rs/issues/274#issuecomment-527506074
cmake version: 3.13.4
binutils version: 2.31.1-16
gcc version: gcc (Debian 8.3.0-6) 8.3.0

As README says:

By default, the secure feature is provided by boringssl, which requires Go (>=1.7) to build. You can also use openssl instead by enabling openssl feature.

You can either install go in the docker image, use openssl or just disable the secure feature.

Thanks, let me try it tomorrow. I will let you guys update.

I'm assuming this is resolved so I'm closing this. :)


Check for autoStartLoad option, call startLoad when required.

somehow i don't understand though how the video can trigger a play event if we haven't started loading it. it should only trigger waiting, then data should be aggregated (there it needs to load) and then it would trigger play? how can it trigger play before we started loading?
and then, couldn't we just call startLoad by default? it wouldn't harm if autoStartLoad is enabled?

Thanks for the feedback @tchakabam
The reason for disabling autoStartLoad is to stop hls.js from buffering the video when the player is loaded, since this might cause a lot of unused traffic on a heavily visited website. So always calling hls.startLoad() on load would defeat the whole purpose for disabling it.
The patch will trigger hls.startLoad() only when the user triggers play (or when autoplay is enabled, in which case the play will be triggered before the manifest is parsed, and there need to be a call to hls.startLoad() when hls.js finishes parsing the manifest).

hey @woutd, i suddenly understand the whole reason for our misunderstanding from the start.
not loading when just the player loads (and then starting loading when play is pressed, what you seem to be wanting to achieve) is a feature that is already implemented in the sister repo of this one, which the P2P-tech wrapper for Streamroot, its in this repo: https://github.com/streamroot/videojs5-hlsjs-p2p-source-handler
apparently it hasn't been done in the plain wrapper flavor here, although the source code is extremly similar. you could just take it from there and patch it over here.
then you would just only start to play when video is actually loaded, not when page is loaded. so you wouldn't ever have to pass the autoStartLoad option to false. does that make sense to you now?
hence i was really confused about the purpose of this patch, and why you needed to pass the option in the first place from the start, as you could see in our conversation on the issue thread..

@woutd you would just need to modify the initialize function in this version to do the same as here: https://github.com/streamroot/videojs5-hlsjs-p2p-source-handler/blame/master/lib/videojs5-hlsjs-source-handler.js#L50

Hi @tchakabam, thanks for the information, I did not know of this sister project.
It is not entirely what I want to achieve: to be able to choose whether the video (buffer) is loaded on page load.
In normal situations, we do want to have the video preloaded on page load. But sometimes we need to embed a video player on a heavily-visited (front) page, in which case we want to be able to disable this buffering since most users will not play the video.

@woutd to achieve that i d rather call the load function of the Videojs API selectively on videos i d want to preload or not (see http://docs.videojs.com/docs/api/player.html#Methodsload)
that should call the appropriate methods on the native tech and thus will trigger events that will take care of preloading (with the sister project). by default it wont load, if you call this function it will. something similar might be done with some videojs config attribute but i dont know it from the top of my head. it would be the cleaner approach imho.

It was my first idea to dynamically load Video.js, but this is not so easy to explain to people who use the player, as they just want to be able to set an option for this.
I also tried using HTML5 preload, this does seem to work on Firefox, but has not effect on Chrome, IE and Edge.
As hls.js has the ability to prevent loading HLS segment until really requested using autoStartLoad, I thought it would be nice to have the source wrapper support this option.

@woutd
as a first step i d move the functionality which i indicated before from the "p2p" side of this project into this codebase here (splitting up initializing Hls.js and calling load-source upon waiting event, see link to code i posted).
that will have as a result that loading actually only happens upon pressing play. so by default you will have the behavior that you are now trying to get by passing autoStartLoad = false. and that should actually be the normal expected behavior. usually it is not expected that media is starting to load just on setting the source, it should happen only on calling play or preload.
after that you have actually fixed the behavior in this project as it is already done in the p2p project, you may be then able to use the preload function of a given videojs instance to preload selectively videos before user's indicated playback intent.
if that doesn't work, or only partly works, solutions may need to be found then.
that's how i d approach it i think. can't say much more about it to be helpful i guess.

Any ETA for this PR as a release?

@woutd thanks, I merged this PR into https://github.com/Go-Promo/videojs5-hlsjs-source-handler/tree/hls6 and it works fine.

You can also check my branch/pull request: #32. I've synced with "p2p" repository, which includes fixes of auto behavior. I've also bumped hls.js version.

Hi all, we are using my patch in production for some time now, and it works well. I do agree that using preload is a cleaner way to accomplish this, but did not had the time to implement this.


Find total number of dad laughs you have played

DaddyLaugh
Problem:
I want people to notice how much time they are wasting on this "useless website"
Solution:
Display total number of dad laughs you have played on the website.

Assign it to me


changelog?

I want to update it on my projects, but not sure what changed since the 2014 version nor if it is a breaking change.
I can investigate the commits (and I will), but a small changelog would be nice. 👍

Would be a good idea going forward.
The latest change don't have any semver breakage. Most were to the dev dependencies or test setup (Travis config). The only code change was falling back to crypto.randomBytes if crypto.pseudoRandomBytes is not available as it disappeared for a bit in node v7 but now it's back so in theory the change wasn't even needed anyway.


track master for both Scala.js and Slick

FYI @sjrd, FYI @szeiger

green build at https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/171/console


How to keep comments in the CST?

Normally comments are ignored(skipped) at the lexer level
which means they are invisible to the parser and thus do not appear in the cst.
You could handle comment as other tokens and do not ignore them.
But because comments can normally appear anywhere in the grammar that would mean
the grammar would become quite verbose and bloated.
Alternatively you could collect all the comments instead of skipping them
using a separate token group and reconnect them to the AST you are building from the CST. As long as your AST supports location information it should not be hard to find the closest
AST node to match a comment with.

Thanks for the answer. I guess collecting comments and then connecting them in the CST visitor is the only viable way right now. But I had a thought would it be a good idea to handle comments in chevrotain? For example introduce a group Lexer.COMMENT, and leadingComments and trailingComments properties to theToken class, each is an array of nodes. Then during tokenization (before parsing) add comments to these arrays.
If you think it's possible I can investigate the problem.

It does not make much semantic sense so I'm less in favor of adding such support in Chevrotain.
because a comment is on a CST/AST node not on a Token.
But I see why you would like to do so as it would make it easy to extract during CST analysis...
You can implement this easily by post-processing the Token output of the lexer.
Without any built-in support by Chevrotain.

[A, Comment, B, C, Comment, D] --> [A , B , C, D]
With the matching comments attached to B and D

// This lexer does not skip comments!
let lexResult = myLexer.tokenize(input)
let tokens = lexResult.tokens

let newTokens = []
let precedingComments = []
tokens.forEach((currTok) => {
    // collect preceding comments
    if (chevrotain.tokenMatcher(currTok, Comment) {
       precedingComments.push(currTok)
    }
     // new token array will not include comments.
    else {
        // augment original tokens with precedingComments property.
        currToken.precedingComments = precedingComments
        newTokens.push(currTok)
    }
})

Thanks for the idea! I'll try it later this week.

Thanks for the idea! I'll try it later this week.

Great.
I will close the issue for now.
The issue of comment handling still exists, but I'm uncertain if there is a good solution at the
parsing library level.


Agencies Dashboard Title

As per the design at https://mongodb.invisionapp.com/share/MYXRXC2T2H3#/422348690_Global_Admin-Home-Dashboard - When the global administrator clicks on Dashboards in the top nav and then Agencies; the resulting page at /global_agencies should show a title of 'Agencies Dashboard'. Currently it says 'Agencies'.

@o-fish-wildaid can I work on this?

@fgiuliani Yes please go ahead!

I was able to complete this issue on my local machine. I noticed that there hasn't been any updates in a week. Would it be alright if I put in my PR for review regarding this?

Absolutely, please do!

@fgiuliani According to the contribution guidelines at https://wildaid.github.io/contribute/index.html - we consider an issue that hasn't been commented on in 72 hours to be abandoned. As such, we have re-assigned it.
If you have time to code, we still have plenty of other issues to work on!

@Sheeri sorry not answering before. I was planning to work on this as part of Hacktoberfest. And as I asked about this issue before October, I was planning to wait.
My bad. Sorry again @Sheeri @k-charette


Indicate that abs() of the minimum integer value for signed dtypes is undefined

Should we add the same note for negative?
I noticed that NumPy uses -(min value) = min value (e.g., np.negative(-128, dtype=np.int8) == -128) and abs(min value) = min value. This has the properties that -x + x always equals 0, and abs(x) = -x for x < 0.

Should we add the same note for negative?

Seems reasonable to me.

I'll make a separate PR for negative.


Update website and docs to remove reference to windows .exe installer

Update website and docs to remove reference to windows .exe installer.
We stopped producing this starting with 3.0.1

#3249 should address the docs part of this.

Install docs should now no longer mention, after PR #3249. There may still be website/wiki mentions.

This should now be resolved.


master

Fix of issue: https://github.com/orhanobut/tracklytics/issues/47

updated to gradle:3.3.0:

Changed buildToolsVersion to "28.0.3"
Replaced variant.javaCompile to if (variant.hasProperty('javaCompileProvider')) {// Android 3.3.0+ javaCompile = variant.javaCompileProvider.get() } else { javaCompile = variant.javaCompile }
Moved String[] args to doLast task (because args can't be init before assembleTask)
replaced compile to implementation
removed .idea files
Updated ReadMe file

@Kolyall your fork is working fine?

@furflez Yes

@furflez seems owner doesn't work with github any more

Thanks for updating the lib dependencies. 👍  Looks great. Let me see why Travis is failed.

I'll merge it and publish the artifacts, that'll fix Travis as well. Thanks for the contribution 🎉

We checked out the PR, included the gradle plugin jar and aar locally.
Build seems working fine but we can't get the aar working when referencing locally. Events are not tracked on our test setup

I just published the artifacts of 2.1.0 version. Can you try with that version? It should be available now.


improvementNot allowed to operate internal_schema database

Proposed changes
Issue Number: close #xxx

Only root user can operate __internal_schema database
The scope of impact includes：
create database
drop database
alter database
create table
drop table
alter table
truncate table
insert overwrite
insert
delete
update
load(root also not allowed)

delete support auth check

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Custom GUI (3D Bounding Box)

Hi, I'm focusing on the customed gui, what I want to do is put some 3D bounding boxes into the scene, and maybe we provide some initial boxes sample in the side bar, and users could directly drag them into the scene.
I noticed that the viewer and viewer_beta folder in source code, it's a little bit complicated. So could you give some points which I can dive into?
BTW, is there any way to debug custom gui on windows? Or the viewer cannot be launched without training process?
cc @tancik

I developed one: https://github.com/OrangeSodahub.github.io/nerfstudio, someone also need this could try


Load GeoJSON as TileLayer

I would like to be able to load a regular GeoJSON as a TileLayer, and not to have it in a GeoJSON layer.
Or to be able to transformn between one and the other kind.
So we could be able to load some  layers like countries borders for example.
There's an old plugin which does something similar*:
https://github.com/brandonxiang/leaflet-geojson-vt
*Even though this plugin does not gives us a tile layer, is kind of a custom tile layer.

https://github.com/Leaflet/Leaflet.VectorGrid/


rook monitoring: add to uptime-robot: https://uptimerobot.com/inc/files/ips/IPv4.txt

Full list of IPs is here:
https://uptimerobot.com/inc/files/ips/IPv4.txt
Small list is:
<IP_ADDRESS>
<IP_ADDRESS>/25
<IP_ADDRESS>/28
<IP_ADDRESS>/28
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

This has been set up. Just need to test that it has been added to the uptime-robot config...and that it is working.

This has been set up. Just need to test that it has been added to the uptime-robot config...and that it is working.

Monitoring is now in place. Closing.

Monitoring is now in place. Closing.


To add page for detailed APY calculation explanation

How Yearn calculates its yVaults Returns
It is a standard on Defi Space to estimate returns through APY and APR, and Yearn also does so. However, different calculations depend on the yVault underlying asset. One for Curve.Finance LP Tokens and another way for non-curve assets. For a simpler version, check the TL;DR version or the infographic at the end of the page. The following sections will show how each one is calculated:
Non-curve assets
The estimated returns are displayed on Yearn.finance this way:

Where the definition of each one is:
•	Gross APR: Vault total APR before deducted fees
•	Net APY: Vault considered APY. If the network is ETH mainnet, this will show the Monthly APY, as the harvests are not that frequent. On the other hand, if the network is Fantom, then the Weekly API is chosen, as the harvests are more frequent.
•	Weekly APY: Calculated considering the yVault price share difference in the last seven days
•	Monthly APY: Calculated considering the yVault price share difference in the last 30 days
•	Inception APY: Calculated considering the yVault price share difference since inception
The actual code can be found on this repo

Where the file that contains the calculation for the most recent version of the yVaults is this one
Curve assets
The estimated returns are displayed on Yearn.finance this way:

Where the definition of each one is:
•	Pool APY: APY is calculated considering the change in the “virtual price” of the curve.finance LP token in the last seven days.
•	Bonus Rewards APR: Rewards are usually given by the token owner. IE frax curve pools also offer frax as a reward. The APY if the token were sold at the current price.
•	Base CRV APR: The APR from the CRV emissions this curve pool gets.
•	Boost: Multiplier from staked veCRV, ranging from 1x to 2.5x
•	Convex APR: APR when the yVault strategy is depositing the curve.finance LP tokens into Convex Finance
•	Gross APR: Vault total APR before deducted fees
•	Net APY: Vault current APY, after deducting the fees
The actual code can be found on this repo

Where the file that contains the calculation for the most recent version of the yVaults is this one
Notes:
•	When the active strategy of a yVault uses Convex Finance, and the streaming of the rewards is frozen at Convex, Yearn.finance Net APY will show 0% until the streaming is resumed.

More details about rewards streaming on Convex Finance
•	When there is a spike of transactions in a pool, the “Pool APY” will reflect it for a week, as the fees will be added to the “virtual price” of this pool, and the calculation takes the last seven days into account.
Infographic

Nice description! Would you mind sending a PR as a docs page so we include it in the documentation?

Sure! https://docs.google.com/document/d/17fNl5N1UTTE8O7VA2iZQLaO1t54z4cZ_aTUqDTyxM_c/edit?usp=sharing


don't allow to record on history list if I press '=' button before I …

…press the operator button #1748
Fixes #.
Description of the changes:

If you press equal(=) button without pressing any operator buttons, it would be not update on history item list.
Parenthesis, 'e', 'π' that are numbers themselves also can't be recorded.
For example, if you input any numbers and press equal(=) button right away, then nothing is recorded.

How changes were validated:

ad-hoc testing

Thanks for this PR! I'm not sure this is the best way to fix #1748, because I think there might be cases where we do want to add to history even if the first token is not an operator. Also, ot looks like this might be breaking some unit tests, and we should add new unit tests which verify the new behavior.
I'm going to close this PR for now. Let's continue the discussion about the desired behavior in #1748. Once that issue is approved, we can open a PR again. Thanks!


closurecompiler: 20180319 -> 20180402

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/closure-compiler/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/gvch7ph5qinav24mdlb48b3lk833aiaf-closure-compiler-20180402/bin/closure-compiler --help’ got 0 exit code
found 20180402 with grep in /nix/store/gvch7ph5qinav24mdlb48b3lk833aiaf-closure-compiler-20180402
directory tree listing: https://gist.github.com/2858ac6d2346b885778eb695553956a0

Success on x86_64-darwin (full log)
Attempted: closurecompiler
Partial log (click to expand)
configuring
no configure script, doing nothing
building
no Makefile, doing nothing
installing
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/db297wxkcsnxlcnpwxh7qrfnk22xj00v-closure-compiler-20180402/bin
patching script interpreter paths in /nix/store/db297wxkcsnxlcnpwxh7qrfnk22xj00v-closure-compiler-20180402
/nix/store/db297wxkcsnxlcnpwxh7qrfnk22xj00v-closure-compiler-20180402

Success on x86_64-linux (full log)
Attempted: closurecompiler
Partial log (click to expand)
building
no Makefile, doing nothing
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/3wc4mrdda5w4ia8glvd6499jzqxli5d3-closure-compiler-20180402
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/3wc4mrdda5w4ia8glvd6499jzqxli5d3-closure-compiler-20180402/bin
patching script interpreter paths in /nix/store/3wc4mrdda5w4ia8glvd6499jzqxli5d3-closure-compiler-20180402
checking for references to /build in /nix/store/3wc4mrdda5w4ia8glvd6499jzqxli5d3-closure-compiler-20180402...
/nix/store/3wc4mrdda5w4ia8glvd6499jzqxli5d3-closure-compiler-20180402

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: closurecompiler
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.


I'm having trouble with javascript thiry-party

I'm learning a lot with react but I'm having a difficulty with javascript third-party.
I need to embed a javascript Snap.svg to my homepage npm install snapsvg (detail: https://github.com/adobe-webplatform/Snap.svg)
The way to import snapsvg is by using this code:
const Snap = require(`imports-loader?this=>window,fix=>module.exports=0!snapsvg/dist/snap.svg.js`);

But this occurs a following error:
Module not found: 'imports-loader' in ...
I installed imports-loader and it does not work.
What is another alternative without using eject?

npm ls react-scripts<EMAIL_ADDRESS>node -v: v7.7.3
npm -v: 4.4.1
Operating system: macOS Sierra

Hi! We don't support Webpack-specific syntax like this.
Since they don't provide a CommonJS entry point, your best bet is to:

Copy snap.svg-min.js into your public folder (preferably with a version, e.g. snap.svg@0.5.1-min.js).
Open public/index.html and add <script<EMAIL_ADDRESS>to its <head>.
Add const Snap = window.Snap; in any file where you want to use it, and you’re good to go.

You can also ask them to provide a CommonJS entry point that doesn’t require fiddling with Webpack.
Hope it helps!

I'm having a hell of a time getting solc module working in create-react-app.
I have this in my html header:
<script src="https://cdn.rawgit.com/ericxtang/browser-solc/master/browser-solc.min.js" type="text/javascript"></script>

and I have this in my code:
console.debug(window.BrowserSolc);

it shows as undefined. Oddly, if I just do:
console.debug(window);

I DO see the BrowserSol object in the window object. It just seems not available in the space of the react app itself.
I'm trying to use the solc nodejs module, which has no commonJS entry point, unfortunately.
Can anyone explain how I can get this working? I don't really know how to use webpack with create-react-app yet...

@Tectract One thing to make sure of is that you've given time for the third party library to be load and run before your code looks for it. You're code may be running before that value has been put on the window object.
Might want to have a retry loop every 50ms to check if the value has been set before you try and use it?

Thanks!
That's interesting. If I do a setTimeout for 1 second before loading window.BrowserSolc, then it appears!
You just saved me so much work-around :)

This sounds pretty weird. I haven't checked this specific library but just want to make it clear that scripts tags are blocking and normally there's no need to wait for them to "execute". Now, of course, it may be that the library sets the global asynchronously, but this is very unusual.

Hi @gaearon,
I saw the same problem with @Tectract . Below is the code of broserSolc https://github.com/ericxtang/browser-solc
I have to sleep 1 second and everything is ok. So weird :(
I downloaded and added to header of html file
    <script src="%PUBLIC_URL%/browser-solc.min.js"></script>


New UI: Logo not displaying on login page

Describe the bug
It seems like something that clients would want displayed on the login screen, since that will be most user's first interaction with the system.
To Reproduce
Steps to reproduce the behavior:

Enable the new ui
Logout
Notice that the logo isn't there
See error

Expected behavior
Logo should be displayed on login page
Screenshots

Platform:

OpenEquella Version: 2018.2, 2019.1
OS: windows 10
Browser: chrome

Fix different for 2018.2 - created new Jira ticket for Jolse to fix.

Fixed in 2019.1 and 2018.2


Allow the user to control job splitting

This issue is related to #897.
Suppose that the user knows that she wants to split her circuits to 10 jobs. Currently she can inherit from the experiment and override _run_jobs. Do you think we can add this option, in a nice way, to the experiment interface? Maybe as an experiment option named num_jobs? Then users will not have to write their own code for _run_jobs.

Haggai suggests that qiskit-experiments will provide a class, let's name it MultiJobExperiment. MultiJobExperiment will inherit from BatchExperiment. It will be similar to BatchExperiment, with the difference that different sub-experiments will be routed to different jobs.
Specifically for our use case of RB on all device qubits, both solutions will work: a num_job parameter, as suggested above, or a MultiJobExperiment. These two suggestions however are not equivalent, and for each there may be use cases that it covers while the other one does not. Haggai says that he has an additional concrete use case where MultiJobExperiment will help him, I'll ask him to detail it here.
I tried to route experiments to different jobs without writing a new expeiment class, in this spirit:
from qiskit import IBMQ

from qiskit_experiments.framework import ParallelExperiment, ExperimentData, CompositeAnalysis
from qiskit_experiments.library.randomized_benchmarking import StandardRB

IBMQ.load_account()
provider = IBMQ.get_provider(hub="ibm-q-internal", group="dev-qiskit", project="ignis")
backend = provider.backend.ibm_bangkok

basis_gates = ["rz", "sx", "cx"]

transpiler_options = {
    "basis_gates": basis_gates,
    "optimization_level": 1,
}

#qubit_groups = [[0, 1, 2, 3, 4, 5, 6, 7], [8, 9, 10, 11, 12, 13, 14], [15, 16, 17, 18, 19, 20, 21]]
qubit_groups = [[0], [1]]

lengths=list(range(20, 201, 20))

pardatalist = []
set_of_qubits = []
for group in qubit_groups:
    set_of_qubits.extend(group)
    exps = []
    for qubit in group:
        exp = StandardRB(
            qubits=[qubit],
            lengths=lengths,
            seed=123,
            backend=backend,
            num_samples=3)

        exp.analysis.set_options(gate_error_ratio=None, plot_raw_data=False)
        exps.append(exp)

    parexp = ParallelExperiment(exps, flatten_results=True)
    parexp.set_transpile_options(**transpiler_options)
    pardata = parexp.run(backend=backend)
    pardatalist.append(pardata)

expdata = ExperimentData(backend=backend)
expdata.experiment_type = "Hi Haggai"
expdata.share_level = "project"
expdata.metadata["physical_qubits"] = set_of_qubits

for pardata in pardatalist:
    pardata.block_for_results()
    expdata.add_jobs(pardata.jobs())
    expdata.add_analysis_results(pardata.analysis_results())

    figs = []
    for fig_id in range(len(pardata.figure_names)):
        figs.append(pardata.figure(fig_id))

    expdata.add_figures(figs, figure_names=pardata.figure_names)

expdata.save()

This code snippet is not working, because we're trying to save results whose experiments are not recognized:
Unable to save the experiment data: Traceback (most recent call last):
  File "/home/yaelbh/.local/lib/python3.8/site-packages/qiskit_experiments/framework/analysis_result.py", line 225, in save
    self.service.create_or_update_analysis_result(
  File "/home/yaelbh/.local/lib/python3.8/site-packages/qiskit_ibm_experiment/service/ibm_experiment_service.py", line 787, in create_or_update_analysis_result
    return self.create_or_update(
  File "/home/yaelbh/.local/lib/python3.8/site-packages/qiskit_ibm_experiment/service/ibm_experiment_service.py", line 1348, in create_or_update
    result = create_func(**params)
  File "/home/yaelbh/.local/lib/python3.8/site-packages/qiskit_ibm_experiment/service/ibm_experiment_service.py", line 746, in create_analysis_result
    response = self._api_client.analysis_result_create(
  File "/usr/lib/python3.8/contextlib.py", line 131, in __exit__
    self.gen.throw(type, value, traceback)
  File "/home/yaelbh/.local/lib/python3.8/site-packages/qiskit_ibm_experiment/service/utils.py", line 44, in map_api_error
    raise IBMApiError(
qiskit_ibm_experiment.exceptions.IBMApiError: 'Failed to process the request: The server responded with \'400 Client Error: Bad Request for url: https://resultsdb.quantum-computing.ibm.com/analysis_results. {"errors":["Experiment 2e650001-6e12-4b4c-8613-c486eeef3e76 does not exist"]}\''

The way to overcome it is to use CompositeAnalysis, which in turn expects metadata to contain information coming from the sub-experiments. Providing all this metadata to the composite analysis is de-facto a re-implementation of CompsiteExperiment, hence we fall back to writing a new experiment class like MultiJobExperiment.

Thanks @yaelbh - the use case I have besides RB are some characterization experiments that contain many circuits (such as whole device Ramsey's on disconnected qubits + ZZ on disconnected edges), amounting to more than the limitation of 300 circuits per job. It then makes sense to divide the circuits into sub-jobs manually according to have control over their simultaneous execution.

In a meeting we agreed that I'll open two separate PRs:

A run option max_circuits (name is consistent with a similar VQE option) for BaseExperiment - maximum number of circuits in a job.
A Boolean run option different_jobs (can you think of a better name?) for BatchExperiment - whether to run circuits of different sub-circuits in different jobs.

Thank you. Perhaps separate_jobs is slightly better a name.

The run options are actually pretty much dedicated to options that pass to backend.run. Therefore max_circuits and separate_jobs will be experiment options.


PNAS corrections

This addresses the comments on the PNAS submission draft made by @drvinceknight.

This is now ready for review. Note that I have added the cover letter and the supplementary material.

Thank you for your comments!


ResNet strides

resnet_strides: add strides as a parameter to the ResNet like in the PyTorch. Sometimes it's necessary to change it. For example in this paper https://arxiv.org/abs/2103.17263 on the evaluation state strides have to be (1, 2, 1, 1).

@googlebot I signed it!


Aztec Code improvements

[x] FNC1 FLG(0)
[x] ECI FLG(1) to FLG(6)

Closed with ab43f5b4576a1859a0d22841194c45d6d79a5ae2.


no README in examples/todo-list

Problem statement
the todo-list example should have its own instructions.  there is a README.md in the stream-server example, but it is not clear that it is supposed to apply to this example as well.  (and i could not get that example to work either.)
really it'd be nice to have a simple makefile that has targets for build, test, and clean.
this would be useful for doing CI on the examples as well, if you're doing that.

I actually had the same thoughts regarding a Makefile. I had started on one based on one I use across projects that supports running locally as well as performing all the tasks within a Docker container.
@casualjim Would you be interested in having such a Makefile?

I will never stand in the way of improvements, bear in mind that I want to migrate to circle ci 2.0 manifests this weekend but that should be easy enough to support


Feature Request

I'm not exactly sure how ":allow_playback_repeats => true" works. If it accomplishes this somehow, then disregard this request and perhaps consider clarifying the description in the relish docs.
Feature: It would be incredible handy to have a feature that can automatically detect if the same sequence of requests with the same parameters were performed by multiple examples and only create 1 file. That way you don't end up with 30 identical duplicate files. A default naming scheme based on the uri and parameters would be nice too!
Credit: I got this idea from the ephemeral_response gem, however, I don't believe it recognizes request sequences. I think it only recognizes individual duplicate requests, which can sometimes be problematic if the response changes after the execution of another request.

I'm not exactly sure how ":allow_playback_repeats => true" works. If it accomplishes this somehow, then disregard this request and perhaps consider clarifying the description in the relish docs.

Hmmm...I definitely want to make the relish docs clear, so maybe you can help suggest how to clarify them :).  Here's a fuller explanation of that option.
FakeWeb and WebMock both let you stub a request once, and it'll reuse the stubbed response if the request is made multiple times.  Or you can stub a request with an array of responses, and the last response will keep being used if there are more requests matching your stub than the number of responses.  See the "Rotating Responses" section of the FakeWeb readme or the "Multiple responses for repeated requests" section of the WebMock readme for examples.
VCR 1.x used these FakeWeb/WebMock APIs and thus had the same behavior.  If a cassette had two interactions for GET http://foo.com/bar, and a test made three such requests while using that cassette, the last request would get the response from the 2nd interaction (even though the interaction had already been "used" once).
I got a feature request (#54) to change this, since it's not really in the "spirit" or design philosophy of VCR.  It's not a given that every HTTP server will return the same thing when a request is made again, so I think it's best if VCR doesn't continue to return the same response again.  Instead, it's better if you re-record the entire sequence of HTTP interactions so that the sequence of interactions is accurate.
So, in VCR 2, I was able to make this change.  When a new request is made that matches an already "used" interaction, VCR will now either:

allow the request and record it (if you're using the :new_episodes record mode)
or raise an "unhandled request" error (if you're using the :once record mode), to alert you to this so you know to re-record the whole sequence.

The :allow_playback_repeats option is simply there to restore the old VCR 1.x behavior if you need it, but I don't recommend using it unless you are upgrading from VCR 1.x and your tests rely on this behavior.
Does that make sense?  How would you recommend I improve the relish docs?
(more response to come later for the rest....)

That does a lot to clarify the behavior of ":allow_playback_requests" and I think that simply adding "Restores VCR 1.x behavior of recording responses" to the docs would suffice for now. I only just started using VCR 2 so I'm not familiar with it's functionality yet. Perhaps a useful section of the docs would be a general list of new or different features in version 2 in addition to the Changelog.
I'm still a bit confused on the scope of the request matching. Are you referring to an example, a test file, or the entire test suite?: 'When a new request is made that matches an already "used" interaction.'
I didn't observe the behavior that you described in the first version as being similar to FakeWeb or WebMock. How did VCR catch and handle requests with stubs? It was my understanding that you had to explicitly associate an example or group of examples with a cassette in order to return the same response. It didn't happen automatically based on the uri and parameters requested.
I ran into two major problems while using VCR which required hours of extra work to circumvent. They may no longer be issues in VCR 2.x, but I couldn't figure out how to avoid them. The proposed feature would help eliminate the following issues:

Expensive API's. I use several API's that have a per-request cost associated with them. Some of these requests are identical and are performed in nearly a hundred examples. The was VCR is functions, I have to perform the request once per example, unless I explicitly reference the same cassette for each example or group of examples. Note that this will not work if another request is performed in an example, even if the other request is completely unrelated. Pe
Example:
Consecutive Requests.

Feature: It would be incredible handy to have a feature that can automatically detect if the same sequence of requests with the same parameters were performed by multiple examples and only create 1 file. That way you don't end up with 30 identical duplicate files. A default naming scheme based on the uri and parameters would be nice too!

There are a couple techniques that can accomplish this: one that has always been possible with VCR, and one that is now possible due to some new VCR 2.0 APIs.
It's convenient to use one cassette per casette using VCR's RSpec integration, but as you point out, this can lead to an explosion of duplicate cassettes.  Often times, I instead create some helper methods in my tests that encapsulate performing an HTTP operation, and using an appropriate VCR cassette based on the request parameters.  Here's an example of what I mean:
module GeocodingHelpers
  def geocode(address)
    VCR.use_cassette("geocoding/#{address}") do
      Geocoder.geocode(address)
    end
  end

  RSpec.configure do |c|
    c.include self
  end
end

This works well for deterministic APIs like a geocoder.  VCR will take care of sanitizing the cassette name into a valid file name.
VCR 2.0 provides request hooks that can be used to handle particular request types globally.  Here's how you can use an around_http_request hook:
VCR.configure do |c|
  c.around_http_request do |request|
    uri = URI(request.uri)
    if uri.host == 'api.geocoder.com'
      # extract an address like "1700 E Pine St, Seattle, WA"
      # from a query like "address=1700+E+Pine+St%2C+Seattle%2C+WA"
      address = CGI.unescape(uri.query.split('=').last)
      VCR.use_cassette("geocoding/#{address}", &request)
    else
      request.proceed
    end
  end
end

Credit: I got this idea from the ephemeral_response gem, however, I don't believe it recognizes request sequences. I think it only recognizes individual duplicate requests, which can sometimes be problematic if the response changes after the execution of another request.

Yeah, I've looked into ephemeral response a bit and it's nifty.  However, as you point out, due to the global way it handles requests (i.e. identical requests always get the same response) it can be problematic.  I think you don't have sufficient knowledge in a global hook to always handle a request a particular way; you often need the context of a particular test, and the sequence of requests made around it.  So I opted for the VCR approach instead, but I think it would probably be possible to re-implement ephemeral response on top of VCR API's (particularly the new request hooks).
Anyhow...let me know if this stuff doesn't meet your needs; I'm always open to further ways to improve VCR.

That does a lot to clarify the behavior of ":allow_playback_requests" and I think that simply adding "Restores VCR 1.x behavior of recording responses" to the docs would suffice for now.

Want to take a stab at adding that to the docs?  I'd be happy to merge a pull request for this :).

I only just started using VCR 2 so I'm not familiar with it's functionality yet. Perhaps a useful section of the docs would be a general list of new or different features in version 2 in addition to the Changelog.

Good idea...I may distill it into the Upgrade doc.  In the meantime, I've been blogging about the new features in VCR 2.0:

http://myronmars.to/n/dev-blog/2011/10/custom-request-matchers-in-vcr-2-0
http://myronmars.to/n/dev-blog/2011/11/cassettes-in-vcr-2-0
http://myronmars.to/n/dev-blog/2011/12/vcr-2-0-0-rc-released

I'm still a bit confused on the scope of the request matching. Are you referring to an example, a test file, or the entire test suite?: 'When a new request is made that matches an already "used" interaction.'

I think the blog post on request matchers (the first one) should help clear this up (both how it worked in 1.x and now in 2.0).  As to your specific question: the scope is always the current cassette (or a "parent one" if cassette usage is nested--but that's rarely used).

I didn't observe the behavior that you described in the first version as being similar to FakeWeb or WebMock. How did VCR catch and handle requests with stubs? It was my understanding that you had to explicitly associate an example or group of examples with a cassette in order to return the same response. It didn't happen automatically based on the uri and parameters requested.

That's correct; cassettes operate a bit like a "sandbox".  In any particular test, the only interactions that can apply are the ones in the current cassette (or a "parent" cassette in a nested context).  But within the context of a single cassette, there can be many HTTP interactions, and VCR uses the :match_requests_on option to configure how it matches to find the correct HTTP interaction to replay.

Expensive API's. I use several API's that have a per-request cost associated with them. Some of these requests are identical and are performed in nearly a hundred examples. The was VCR is functions, I have to perform the request once per example, unless I explicitly reference the same cassette for each example or group of examples.

I recommend using the "helper method" approach I outlined above, or the new request hooks.  This is how I usually use VCR, anyway.

@Retistic -- did any of my suggestions above help sufficiently?

I only just started using VCR 2 so I'm not familiar with it's functionality yet. Perhaps a useful section of the docs would be a general list of new or different features in version 2 in addition to the Changelog.

@Retistic -- does https://github.com/myronmarston/vcr/blob/master/Upgrade.md meet your needs?

Sorry, I've been away on business. The changes look great. I ended up making a cassette for each request like you recommended and it works really well. I haven't taken a shot at automating the creation of duplicate requests in different tests as I don't have enough duplicates to make it worthwhile yet. When I have a bit more time, I'll look at your implementation suggestion.
Thanks again for all the help! VCR is an awesome indispensable gem.

Cool, glad to hear that things are working well for you.  I'm going to close this, but feel free to re-open or create a new ticket if you have other feedback.


Broken Cypress test eventRegistration.js

Where to find the issue
eventRegistration.js
Describe the issue
The Cypress test eventRegistration.js fails due to text changes made in PR https://github.com/corona-warn-app/cwa-website/pull/3093
Suggested change
The Cypress test checks for the exact text match from:
https://github.com/corona-warn-app/cwa-website/blob/218de1eb4c2d4437a8da001182126ee529b57a27/cypress/fixtures/copy/stringEn.json#L4
and from:
https://github.com/corona-warn-app/cwa-website/blob/218de1eb4c2d4437a8da001182126ee529b57a27/cypress/fixtures/copy/stringDe.json#L4
These texts need to be changed.

Internal Tracking ID: EXPOSUREAPP-14072

I want to update this but before then, perhaps we could

replace string assertions with DOM element assertion OR
reduce the length of assertions to something stable (if we know which part of that statement would be stable)

Any suggestions?

I will provide a PR simply fixing this issue by aligning the statements in about an hour or so. Any further discussion about how to improve the test should be made on e it's fixed, I think.

I will provide a PR simply fixing this issue by aligning the statements in about an hour or so. Any further discussion about how to improve the test should be made on e it's fixed, I think.

PR https://github.com/corona-warn-app/cwa-website/pull/3116 provided.

Hi @MikeMcC399, @chrisenitan,
we have merged @Ein-Tim 's PR for the moment, we might think of a better solution at some point!
Thanks everybody!


[portaudio] Fix library cannot be found

Related issue #8834, #8869.

cc @GiulioRomualdi

Dear @NancyLi1013 thanks for fixing the problem. Now portaudio is found by the cmake project. However as I wrote in https://github.com/microsoft/vcpkg/issues/8834#issuecomment-551848072, the compilation phase failed when #include<portaudio.h> is added to the project.

/azp run


As a user, I can view all my contacts in an alphabetical order

... so I find a contact if I cannot remember who I am searching for

Duplicate Issue


Make rule order deterministic

👍

Codecov Report

Merging #26 into master will increase coverage by 0.34%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
+ Coverage   84.67%   85.01%   +0.34%
==========================================
  Files          13       13
  Lines         261      267       +6
  Branches       13       18       +5
==========================================
+ Hits          221      227       +6
  Misses         40       40

Impacted Files
Coverage Δ

core/src/main/scala/com/stripe/dagon/Dag.scala
91.33% <100%> (+0.36%)
:arrow_up:

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 dbbe7fc...c7ada51. Read the comment docs.


Wrong characters displayed in runtime with translations and Montserrat font

Godot version
4.1.1
System information
Linux
Issue description

In runtime, the characters are different than in the editor.
I could only reproduce with Montserrat font, and when Settings/Locale/test is set to sr
Steps to reproduce
Can be reproduced in the small project I uploaded.
Minimal reproduction project
font_issue.zip

Serbian locale can typically be either Latin or Cyrillic. I think with our OS.get_locale() formatting this would be sr_Latn or sr_Cyrl (following https://en.wikipedia.org/wiki/ISO_15924). Not sure which one is used by default if you specify on sr, but your test seems to show that it would be sr_Latn, while your OS/editor locale might be sr_Cyrl?
CC @bruvzg

When printing out OS.get_locale() I get en_US which makes sense because my OS is in english

These substitutes for Serbian are set in the font file itself, so Godot (it's done by HarfBuzz library in particular) is doing what font designer intended to be done:
Substitution list:

Target glyphs:

As a workaround, you can change language value (force it to en) in the Labels BiDi properties, it will affect rendering only and should not interfere with localization.

Also, I take a quick look at the Wikipedia, and this glyph style might be actually correct:


launch OPN RFP 5 March

I provided a few suggestions on the RFP language, and one initial comment up top that is not timely but would be nice to include.

@peterspdx thanks


safecloset: 1.3.1 -> 1.3.2

Diff: https://github.com/Canop/safecloset/compare/v1.3.1...v1.3.2
Changelog: https://github.com/Canop/safecloset/blob/v1.3.2/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg eval

Result of nixpkgs-review pr 267804 run on x86_64-linux 1

1 package built:

safecloset


[dogstatsd] dogstatsd daemon embedded into a lambda

This is a potential solution to a problem we are likely going to face soonish, and looking at idea how we could potentially have a scaable solution for pushing metrics to statsd.
We want the ability to have lambdas push metrics using the statsd protocol to lambda. (We know there is a way with logging it to CloudWatch). We really enjoy the interface that a dogstatsd client exposes client.increament.. we don't want to rebuild the functionality, and and instead of send to daemon, but to just send to log.
We have a potential solution to create an EC2 instance, attach an LB, and allow our lambdas to send metrics to this directly. While this approach seems ok, I don't want to provision a new instance for something that as basic as just running a simple daemon to ship metrics to DataDog.
Another potential solution, I'm eyeing up. Is the fact that I could write a serverless function.. (AWS Lambda), that wraps the daemon, that is hooked to an ALB. The ALB is known endpoint that metrics can be forwarded to. Would this potentially work?
Some problems I probably need to think about is how the event is handled in the lambda, perhaps? Is it something thats been explored? Failed?

The other potential idea, is using the new layering feature within AWS, and wrap the lambda with a special statsd runtime...


setup.sh flag to recreate config

In order to clear the configuration, you need to delete the config.txt in the .shared-folder.
"Could have" a flag for the setup.sh that would clear the config.

Should probably just reference where the config.txt file is located so people are aware of its presence.


refactor: refactor unexported pack methods

I'm splitting PR #572 into 2 parts, this is the first part.

Codecov Report

Merging #573 (4747c97) into main (e6d40b6) will increase coverage by 0.08%.
The diff coverage is 92.68%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #573      +/-   ##
==========================================
+ Coverage   74.15%   74.24%   +0.08%
==========================================
  Files          51       51
  Lines        4787     4814      +27
==========================================
+ Hits         3550     3574      +24
- Misses        908      910       +2
- Partials      329      330       +1

Files Changed
Coverage Δ

pack.go
83.68% <92.68%> (+0.86%)
:arrow_up:


Refactor tests

Branched from #13 which should be merged first
This PR does away with the e2e tests, and moves them into a locally run tests using controller-runtime envtest.
This makes running tests for policy-approver, and future plugins, much quicker as we don't have to wait for a kind cluster etc.
This does away with the e2e tests. Later on, we will replace it with a smoke test which will install policy-approver against a kind cluster. Proper testing should always be done against /test/env.
/test/env is designed to be reusable by other projects.
/test/env will setup a API server, installs the CRDs, and starts the cert-manager webhook.
/assign @charlieegan3

/retest

/lgtm
/hold
Hold added to allow response to above comment, please feel free to merge after that.

/hold cancel


Fixing a bug in the RangeSlider and adding some flexibility to the Annotator

Some simple stuff. I took care to make sure I don't break any current behavior, and added the ability to display the annotation lines by default, set a custom click handler, and turn off the click handler w/ an option.

Hey @ryana,
Are you interested in adding tests to this PR? We know it's been awhile but better late than never. Thanks for your initial contribution!


Problem with loading GL functions

Hello nice job with WASM!
But I tried with simple white triangle and it can't see in my code like this your code with I use white Triangle
		uint vaoID = 0;
		GL.glGenVertexArrays(1,&vaoID);

		uint vboID = 0;
		GL.glGenBuffers(1, &vboID);

		GL.glBindVertexArray(vaoID);
		GL.glBindBuffer(BufferTargetARB.ArrayBuffer, vboID);

		float[] vertices = {
			 0.0f,  0.5f, 0.0f,
		     0.5f, -0.5f, 0.0f,
			-0.5f, -0.5f, 0.0f
		};

		fixed (float* vertices_ptr = &vertices[0])
		{
			GL.glBufferData(BufferTargetARB.ArrayBuffer, vertices.Length * sizeof(float), vertices_ptr, BufferUsageARB.StaticDraw);
		}

		int stride = 3 * sizeof(float);
		GL.glVertexAttribPointer(0, 3, VertexAttribPointerType.Float, false, stride, (void*)0);
		GL.glEnableVertexAttribArray(0);

		GL.glDrawArrays(PrimitiveType.Triangles, 0, 3);

Add lines asssssssssfter GL.LoadAllFunctions(EGL.GetProcAddress);
Than I type dotnet build -c Release and dotnet run -c Release and I open chrome and it doesn't see triangle :(

How do I fix? I thought WASM has not problem with OpenGLES.

Just to check, have you set a shader to render your verts? It would be helpful if you upload the solution in full so I can take a look.

Hello @AshleighAdams  sorry I am busy for trying to resolve with WASM-Test like you made but It is really hard to find. I thought MyRuntime() should with GL function, correct or wrong?
Check my repository under Github DeafMan1983/Wasm-Test
Thanks!

I took a quick  look, and it looks like you're doing the rendering once on load, which is then cleared in Frame() here: https://github.com/DeafMan1983/Wasm-Test/blob/f49e8bd439842ac1c2ad705ca5c55d2a2d0c0cda/Program.cs#L130-L135
Frame is where your rendering code should ideally be run, as it's currently set up to be invoked from requestAnimationFrame(). Just as a quick test, I commented out the clear invocation, and it resulted in the following:


Make setRawValue work with redux-form and react-day-picker

Addresses #251
I didn't find a place to add tests specific to the React implementation, so I didn't add any. If you tell me how/where to add a test, I'm happy to.

Hey. Sorry, was away for a few weeks, will merge and publish a release soon.

No worries. I have a workaround in place in the meantime.


Add support for internationalization with TranslateErrors middleware

Add support for internationalization with TranslateErrors middleware:

Rename  HandleChangesetErrors middleware to TranslateErrors
Implement internationalization using Gettext and default Crudry.Translator module
Allow overriding default translator Crudry.Translator by adding a custom translator in Absinthe's context
Allow overriding default language en by passing a custom locale in Absinthe's context
Translate Ecto error messages using domain defined in Translator.errors_domain/0, which defaults to errors
Translate Ecto schema fields using domain defined in Translator.schema_fields_domain/0, which defaults to schema_fields
Add tests
Improve modules docs

This is a breaking change, so it should go to https://github.com/gabrielpra1/crudry/tree/v2.0, please rebase with that branch and change the PR to it

Closed in favor of #33


Issue 58: Updated UV1 alignment shift position

I am ready to merge the UV1 alignment.

Looks good :)

looks good


Add aarch64 builds

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

I don't know if this is going to work or not, but if it does it would be great to add Linux Arm support.

Looks like this builds & tests! Would love to have a maintainer look at it & merge :). Didn't require any changes, just enabling the AArch64 builds and re-rendering with Conda Smithy.

This looks good to me but since I'm still a conda-forge toddler, I'll follow up with the real experts over here and get back to you.

Thanks @mdekstrand ! Would you like to be a maintainer on this recipe? I'll go ahead and merge this now. If you do want to be a maintainer, you can open an issue as described in https://conda-forge.org/docs/maintainer/infrastructure.html#conda-forge-admin-please-add-user-username