Add Milestone endpoints

What changes does this PR introduce?

Moves the client logic out of __init__.py and into api.py
Adds internal helper methods for calling requests to the ClubhouseClient class in api.py
Adds a method for each Milestone endpoint offered by the Clubhouse API
Updates all dependency versions

Notes

The scope of this PR is larger than what would typically be acceptable. I set out to just add the Milestone endpoints, but made some structural changes as I discovered opportunities in the existing code. Now that I'm familiar with the code, I don't expect future PRs to be this large (or include out-of-scope changes).

Tests

I need to learn how to mock requests for unit tests. In an effort to maintain momentum on this project, I've decided to focus on adding as many endpoints as I can and creating a new issue for each group of endpoints that needs testing. (For example, I'll create an issue for adding all Milestone endpoint tests.)

Hey there, @j-martin 👋 Do you have any interest in reviewing this PR?


Add id and parent_id methods to PublicItem

This is a draft PR to facilitate discussion in #655.

I hope the "Eliminate Id references" commit is okay. I forked public-api before rustdoc-types made Id to copyable. So, with this commit, I removed several &Id that I introduced, and a few others.

The smaller PRs the better, so if it is possible to split this out into smaller PRs, that is a good thing.
I'm also curious about the performance impact of this PR. We currently don't have any CI check for performance. If we did I think it would be in the form of cachegrind which I think is independent of hardware it runs on since it counts instructions. That is partly what the Rustc performance checks use: https://github.com/rust-lang/rustc-perf/tree/master/collector
The best we have AFAIK in comparing performance before and after is manually running https://github.com/cargo-public-api/cargo-public-api-benchmarks/blob/main/benches/json_processing.rs with cargo bench. I don't care super much about performance since we are pretty fast regular sized crates, but this creates a slowdown of say 100% I think we need to discuss options.
I'll also unmark this as draft so we can see how CI is doing.

The smaller PRs the better, so if it is possible to split this out into smaller PRs, that is a good thing.

:+1: I submitted the "Eliminate Id references" as PR #659. I'll rebase this PR if that one is merged.
Would you like me to submit "allow underscore argument names" as its own PR as well?

Would you like me to submit "allow underscore argument names" as its own PR as well?

Yes please that would be great, with a 0.x.0 CHANGELOG entry in both CHANGELOG.md and public-api/CHANGELOG.md and the new regression test in functions.rs

Please let me know if you would like me to squash anything.

Ideally each commit should be self-contained and pass all CI tests. You can check locally with scripts/run-ci-locally.sh.
In this case I think I personally would have made the remaining parts of the PR a single commit.
Note that in GitHub you can press the "force-pushed"  link between the comments which allows easy review even with force push, as long as the base commit remains fixed. Although after a while those links gets pruned away.
I'm btw checking the performance of this new code now.


Collapse stat and save

This collapses the types for the stat rolls and the save rolls into one another. This makes it easier to modify the logic and centralize it. This is mentioned in #6.

The pull is rather nasty since I've had to corroborate several branches. I'd actually not accept this yet, since there's some extra changes in the middle there. Unfortunately, and this is my fault, I've hacked my code base to the point where it's hard to pull out the changes I need to. I'm sure there's a way to do it with git, or I could manually confect the changes I need, but right now this is what I can do.


wfreerdp initial fullscreen scaling via smart-sizing

Hello,
xfreerdp has initial fullscreen scaling via options: xfreerdp /v:servername /f /smart-sizing:320x200 - but this doesn't work with wfreerdp, is this unintended?
Information as per https://github.com/FreeRDP/FreeRDP/wiki/Quality-Assurance-(QA)#smart-sizing
Many thanks

xfreerdp is the most advanced of our clients. Smart sizing isn't just yet implemented in wfreerdp. If you have a look at the link you've posted it says
Clients
X11: xfreerdp

where the smart sizing tests are described.


Gold project sponsorship changes

new gold users can no longer sponsor projects
applies to gold users created after 2019-05-01

Shouldn't we use a time based feature flag for this?

Shouldn't we use a time based feature flag for this?

Feature flags apply to projects, correct? This applies to the user subscription.

New condition makes sense to me.


html-pdf npm library gives weird output on Linux Server?

I am generating PDF from HTML and that worked fine on my local machine, which has Windows as OS. But now I deploy my application on a Linux server where it gives weird output:
const htmlPdf = require('html-pdf')
try{
    let html = `<!DOCTYPE html><meta charset="UTF-8" />
Managed APs

AP Serial	AP Name	AP Model	Mac Address	IP	Connect Status	Cluster
1010212112	AP_Test	RJ147	<IP_ADDRESS>	<IP_ADDRESS>	Connected	Dummy Cluster

`

    htmlPdf.create(html).toBuffer(function(err, buffer){
        if(err){
            return res.json({
                success: false,
                message: dbErrorMessage
            });
        } else{
            const pdfData = buffer.toString('base64')
            return res.json({
                success: true,
                data: pdfData
            });
      }
    });
}
catch(e){
    return res.json({
        success: false,
        message: e
    });
}

I have also posted query on stackoverflow:
https://stackoverflow.com/questions/53866694/html-pdf-npm-library-gives-weird-output-on-linux-server

I am also facing the same issue, it is working fine in local but in linux server not working buffer output value gives as a  spawn /var/projects/dev/facommtrack/node_modules/phantomjs-prebuilt/lib/phantom\bin\phantomjs.exe ENOENT

@ganeshpaiya I was faced the same issue, If you update the phantomjs in your server then you may not get this issue.along with that in your server update the below packages too. It was works fine to me now.
sudo apt-get install libfreetype6
sudo apt-get install libfontconfig

For alpine it in Dockerfile was works fine
RUN apk add --no-cache curl &&
cd /tmp && curl -Ls https://github.com/dustinblackman/phantomized/releases/download/2.1.1/dockerized-phantomjs.tar.gz | tar xz &&
cp -R lib lib64 / &&
cp -R usr/lib/x86_64-linux-gnu /usr/lib &&
cp -R usr/share /usr/share &&
cp -R etc/fonts /etc &&
curl -k -Ls https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-2.1.1-linux-x86_64.tar.bz2 | tar -jxf - &&
cp phantomjs-2.1.1-linux-x86_64/bin/phantomjs /usr/local/bin/phantomjs &&
rm -fR phantomjs-2.1.1-linux-x86_64 &&
apk del curl
RUN npm rebuild phantomjs-prebuilt

And don't forgot libconfig


CMakeLists improvement, licence added, .info file configuration

This code extends from the colour-refactor branch of the base repository, and incorporates changes from commit https://github.com/sedeen-piip-plugins/StainAnalysis-plugin/commit/66bb6cc5b1a606c153f1cc99d56095c5276e346c.
Licence terms have been added to the repository and headers in all of the code files. The Apache License 2.0 was chosen.
Enhancements were made to the configuration steps in CMakeLists.txt. The ColorDeconvolutionKernel is dependent on boost::filesystem, and this dependency is now specified and configured in CMakeLists.
The .info file required in the Sedeen Viewer plugin folder is configured, created, and installed by CMakeLists, based on a new file, StainAnalysis-plugin.info.in.
Source files have been renamed to match the name of the repository.

I'm going to retract this pull request for now. I'll leave out the licensing text until the group decides which one to use, rebase the other commits, and submit a PR on a different branch.


Warning and errrors while building angular ssr app

Environment
CentOS Linux release 7.8.2003 (Core)
node.js v12.11.1
yarn v1.22.5
Dependencies:
"@angular/core": "~9.1.7",
"express": "^4.15.2",
"@nguniversal/express-engine": "^9.1.0",
"@instana/collector": "^1.129.0"
Problem:
After adding Instana, as shown below, build ends with warnings, errors. So build doesn't work.
// Instana
// tslint:disable-next-line
import instana from '@instana/collector';
// You need to call the exported function *immediately*, before importing anything else.
instana();

// tslint:disable-next-line
import { APP_BASE_HREF } from '@angular/common';
import { ngExpressEngine as engine } from '@nguniversal/express-engine';
import { REQUEST, RESPONSE } from '@nguniversal/express-engine/tokens';
import { NgExpressEngineDecorator } from '@spartacus/core';
import * as express from 'express';
import { existsSync, readFileSync } from 'fs';
import { createProxyMiddleware } from 'http-proxy-middleware';
import { createServer } from 'https';
import { join } from 'path';
import 'zone.js/dist/zone-node';

import { AppServerModule } from './src/main.server';

const ngExpressEngine = NgExpressEngineDecorator.get(engine);

// The Express app is exported so that it can be used by serverless Functions.
export function app() {
  const server = express();
  const distFolder = join(process.cwd(), 'dist/storefront/browser');
  const indexHtml = existsSync(join(distFolder, 'index.original.html'))
  ...

End of the build log:
Hash: 5272a7f256b5360005e8
Time: 112384ms
Built at: 2021-07-20 16:09:02
  Asset      Size  Chunks                    Chunk Names
main.js  11.5 MiB       0  [emitted]  [big]  main
Entrypoint main [big] = main.js
chunk    {0} main.js (main) 19.5 MiB [entry] [rendered]

WARNING in<EMAIL_ADDRESS>45:52-103
Critical dependency: the request of a dependency is an expression

WARNING in<EMAIL_ADDRESS>22:25-48
Critical dependency: the request of a dependency is an expression

WARNING in<EMAIL_ADDRESS>156:51-78
Critical dependency: the request of a dependency is an expression

WARNING in<EMAIL_ADDRESS>47:25-64
Critical dependency: the request of a dependency is an expression

WARNING in<EMAIL_ADDRESS>95:27-49
Critical dependency: the request of a dependency is an expression

WARNING in<EMAIL_ADDRESS>294:29-67
Critical dependency: the request of a dependency is an expression

WARNING in<EMAIL_ADDRESS>9:12-61
Critical dependency: the request of a dependency is an expression

WARNING in<EMAIL_ADDRESS>91:19-37
Critical dependency: the request of a dependency is an expression

WARNING in ./node_modules/dtrace-provider/dtrace-provider.js
Module not found: Error: Can't resolve './src/build' in '/home/aa.udalov/git/storefront/node_modules/dtrace-provider'

WARNING in ./node_modules/node-gyp/lib/Find-VisualStudio.cs 9:6
Module parse failed: Unexpected token (9:6)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| // This script needs to be compatible with PowerShell v2 to run on Windows 2008R2 and Windows 7.
|
> using System;
| using System.Text;
| using System.Runtime.InteropServices;
Done in 360.68s.

Hi @Stopy thanks for reporting this issue.
Based on my initial investigation, this seems to be related to the way the Webpack works.
It seems not to like dynamic imports, eg: this.addon = require(addonPath); extracted from WARNING in<EMAIL_ADDRESS>91:19-37.
I took a quick look at this post where they discuss about a similar issue: https://stackoverflow.com/questions/42908116/webpack-critical-dependency-the-request-of-a-dependency-is-an-expression
However I still didn't try it myself.
Could you maybe take a look at is as well? In the meantime, I will try to reproduce the issue with a small app that is bundled with Webpack.

Willian C.

Hi @Stopy ,
After some more investigation and some chat with one of the collaborators of Webpack, the recommendation would be to keep node_modules out of your bundle.
This will of course require you to add the production dependencies of your application in a package.json in the same directory as your - already bundled - project.
Basically, our API relies on native modules that are compiled through node-gyp, which causes some problems for Webpack, like the error you are facing.
I invite you to check the entire discussion here: https://github.com/webpack/webpack/discussions/13833
Please, note that this issue is not caused directly by our API, but it comes from another library that we depend on.
If you have further questions, feel free to reply to this thread. Otherwise I believe that the issue can be closed.
Cheers,

Willian C.

Hi @willianpc,
Thanks for your time.
I haven't got what you mean when you say "keep node_modules out of your bundle". We are using Angular, so we don't have a possibility to deeply change webpack config. Also our back and front code are connected to each other quite hard, cuz of SSR and so on.

Hi @Stopy ,
I understand.
Have you had a chance to check the discussion I had with the collaborator of Webpack? I think you can find all the details you are looking for in there.
But the important bit to clarify your question is this:

Bundle the application without node_modules dependencies by using node-externals. This prevents Webpack from bundling them and keep a proper require('module') in place
Ship the bundle with package.json / package-lock.json /etc
During deployment process, run npm i --production or one of the similar options in order to get all the external dependencies properly built and to be require by the bundle

This blog post can also be helpful for you: https://archive.jlongster.com/Backend-Apps-with-Webpack--Part-I
One idea that I would try is to keep all externals (node_modules) in the build except for the node-gyp one. Then you follow the 3 steps mentioned above, but only for the node-gyp dependency.
You can use https://www.npmjs.com/package/webpack-node-externals as recommended by Alexander (the Webpack collaborator) and use the options to filter what should or should not be in the bundle.
If this doesn't help, then I think that pinging the Webpack team is the best approach.
Hope this helps!

Willian

Hi @Stopy ,
I will close this issue as we explored all possible current solutions around bundling application with the Instana tracer.
Just as a last source of information, we have a documentation about this very same topic and directions on how to deal with the bundling, which is pretty much what we already discussed. But for a more formal explanation, please refer to : https://www.instana.com/docs/ecosystem/node-js/installation/#bundlers-webpack-and-similar
Best,

Willian

Please also see our documentation here: https://www.instana.com/docs/ecosystem/node-js/installation#bundlers-webpack-and-similar
Key points:

The preferred installation method when you pre-process your Node.js server application with a bundler like Webpack or Rollup is described in Installation Without Modifying the Source Code.

and

In case you are using Angular CLI, in particular with Angular Universal/SSR, you should add "externalDependencies": ["@instana/collector"] (and possibly other libraries that @instana/collector instruments) to your angular.json file to exclude it/them from bundling (see here).

Oof, Willian beat me by a few seconds :D

Thanks you guys so much, works great. I just needed to not edit my source code and follow these steps https://github.com/instana/nodejs/issues/365#issuecomment-891797356


[QUESTION] How can i create tag with ajax response

Hi, I want to create tag with ajax response.  Because when user delete this tag. I have to request to backend with tag id.
createTag: function (params) {
      var term = $.trim(params.term);
      if (term === "") {
        return null;
      }
      return {
        id: ?, //i want to set this with ajax response
        text: term,
        newTag: true,
        anotherId: ?, //i want to set with ajax response
      };
    },

Per project Issue Template guidance:

Make sure that your issue is a BUG or FEATURE REQUEST.  General usage and troubleshooting questions should be directed to the forums or Stack Overflow.  Issues asking for general support WILL BE CLOSED automatically.

https://forums.select2.org/t/create-new-tags/942 may help you.

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.


[context] Global Context

Should this be an RFC?

[X] This is not a substantial change

Which package is this a feature request for?
Context (@lit/context)
Description
It seems like it would be quite straightforward to extend the Context API so that a truly global context provider can be set up on document.
Something like this:
class AppComponent1 extends LitElement {
    // note use of 'document' instead of 'this'
    _userProvider = new ContextProvider(document, userContext);
    // or perhaps a new class:
    _userProvider = new GlobalContextProvider(document, userContext);
}

And then components can consume a global context value in exactly the same way as a normal one:
class AppComponent2 extends LitElement {
    static properties = {
        user: {}
    }
    _userConsumer = new ContextConsumer(this, userContext, value => {
        this._user = value;
    }, true);
}

My reasoning for this is that I have a largely static page, with different LitElement components in different areas. For example a navigation bar (which needs to know whether the user is logged in or not to show login/logout buttons), and a small section of interactive content further down the page, which depends on the login.
It doesn't really make sense to turn the whole largely static page into a LitElement, but it would be nice to have a standard way to share some context between all components on the page. Since context is identified by the identity of the context object, there doesn't seem to be any danger of breaking the isolation between separate components that do not know about the context, and this should be completely backwards compatible with the existing context API.
Alternatives and Workarounds
It's possible to do this outside of Lit, but would be much neater to re-use the internal ValueNotifier class, or just modify the existing ContextProvider class to accept the document, and it seems like something that would be generally useful.
If this is something which would be welcome, then I'm happy to have a stab at implementing it.
(I don't think this is a substantial change, but correct me if I'm wrong)

I can envision this being a possibility but I would discourage attaching the provider to the document from within another component like shown.
I think it could be more like the ContextRoot https://github.com/lit/lit/tree/main/packages/context#late-upgraded-context-providers that attaches a provider to a DOM node like document.body.
The only lifecycle that ContextProvider uses is hostConnected so perhaps it can be more generalized so that the provider can be added to any HTMLElement and the readiness can be manually signaled.

This does seem valuable and could perhaps piggyback on ContextRoot, but it is pretty simple to do with ContextProvider with one little hack to add addController to the host element (and this could easily just be optional):
// hack `addController` onto host
document.addController = () => {};
const provider = new ContextProvider(document, context, nextValue());
// doesn't need to be called in this case.
provider.hostConnected();

https://lit.dev/playground/#gist=049135c4376d76e12bc9ff28c8ccf628

Agree. I tried the same hack with no-op addController. 😁
Updating the host type on ContextProvider and optionally calling addController(), and documenting this use case seems like an easy way to support this. Manually calling hostConnected() would only be needed if this is imperatively being added to an element that's a child of another provider, or if there's concern that this will be added after a consumer's already registered and you need to tap into ContextRoot.


Add tests for mealsCount

In this PR, we added the following:

Refactored count function into functions for counting, creating a count element, and appending the count element to the DOM for cleaner tests
Add relevant tests for these functions

Hi @dfsalam , there is nothing else to say other than... it's time to merge it :shipit:


Pip install fails for 4.0.39 on Windows 10, Python 2.7

Environment

Python: 2.7.18 (v2.7.18:8d21aa21f2, Apr 20 2020, 13:25:05) [MSC v.1500 64 bit (AMD64)] on win32
pyodbc: 4.0.39
OS: Windows 10 Enterprise
DB:
driver:

Issue
Pip install fails repeatedly with red text shown below. Was able to install version 4.0.35 instead without issue

Can you copy and paste that text? Dark red on black is absolutely unreadable.

pyodbc 4.0.35 has Windows wheels for Python 2.7
pyodbc-4.0.35-cp27-cp27m-win_amd64.whl
pyodbc-4.0.35-cp27-cp27m-win32.whl

but pyodbc 4.0.39 only has wheels for Python 3. So if you want to install 4.0.39 for Python 2.7 you need to have the C++ compiler as indicated by the message

error: Microsoft Visual C++ 9.0 is required. Get it from http://aka.ms/vcpython27

(in the red-on-blue part).


Documentation not clear about multiple arguments in an exec request

Hi,
I found that the documentation is not clear about multiple arguments in an exec request as documented on https://jolokia.org/reference/html/protocol.html#exec.
The format says /arg1/arg2/... while Table 6.6 states <arg1>,<arg2>, ... and the example "true","true"
Which one is it?
Other than that, Jolokia is a great product! Keep up the good work 👍

Hi,
The format actually says /<arg1>/<arg2>/... and the table header states it's the Part, which means each <...> corresponds to each part of <...>,<...>, .... So I think it's clear enough.
Maybe we can make it a bit more clear at the example, which should be "true","true" or /true/true/....

Nice, thank you!


ParseError for Merge conflict marker (as detected by TypeScript)

Typescript has a great error message. When encountering lines generated by a merge conflict (and left in if unresolved or incorrectly resolved):
error TS1185: Merge conflict marker encountered.
/cc @bterlson

Should detect diff3 format as described here as well: https://github.com/Microsoft/TypeScript/issues/16129.

@bterlson Would detecting this potentially cause a spec violation? I'd assume the presence of such tokens would cause a SyntaxError anyway, so we'd just be giving a helpful message. Just want to make sure.

Note: This wouldn't be able to detect markers inside of multiline-strings.

@dilijev no spec violation, still a syntax error just with a nicer message.


🐛 Bug ➾ taqueria generated wrong error messages on last ligo syntax with no main function

🚥 Status (Internal Taqueria Team Use Only)

[ ] 🔬 Investigated and Verified
[ ] ⚗ Solution Identified and Designed
[ ] 🧫 Dev Implementation of Fix
[ ] 🧪 Fix Tested and Validated
[ ] 🏆 PR Merged

🆘 What happened?
On last ligo v0.61+, main function is no more mandatory, we can use @entry instead
Taq will still generated useless error messages , but compilation is successful
TAQ_LIGO_IMAGE=ligolang/ligo:next taq compile main.jsligo
=== Error messages for main.storageList.jsligo ===
Internal error: Entrypoint main does not exist

===

=== Error messages for main.storageList.jsligo ===
Internal error: Entrypoint main does not exist

===

=== Error messages for main.storageList.jsligo ===
Internal error: Entrypoint main does not exist

===

=== Error messages for main.storageList.jsligo ===
Internal error: Entrypoint main does not exist

===
┌───────────────────────────┬───────────────────┐
│ Contract                  │ Artifact          │
├───────────────────────────┼───────────────────┤
│ main.jsligo               │ artifacts/main.tz │
├───────────────────────────┼───────────────────┤
│ main.storageList.jsligo   │                   │
├───────────────────────────┼───────────────────┤
│ main.parameterList.jsligo │                   │
└───────────────────────────┴───────────────────┘

🆘 Steps to Reproduce?
run about command with any jsligo file having no main function but only @entry entrypoint functions
🪵 Relevant log output
see above

🐘 How impactful is this bug?
None
⏱ Prevalance
blocker
💻 Operating System
None
🕸 System Architecture
None
🌮 Taqueria Version
0.28.4
🌿 Node.js Version
No response
☎ Contact Details
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Finally is a blocker because the Michelson for  main.storageList.jsligo is not generated

ok, easy workaround is to create a fake main function on the storageList file ..

ok, I got it
If I have on the file :
const myvariableToReuse = ...

const default_storage = {
  my var : myvariableToReuse
}

Then I get into troubles because taqueria thinks I want to declare 2 initial storages   XD  @mweichert
I need to go all inline

Second problem :
I need to use   #include "./main.jsligo"    and not   #import "./main.jsligo" "CONTRACT"
This ... I don't know why ?  @mweichert


1539 | Kth Missing Positive Number | C++

Kth Missing Positive Number -
What will change -
Adding a new leetcode problem with optimized C++ solution
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Please assign this issue to me.

Please allow me to do it.

Please allow me to do it. Should I make a pull request just after solving the issue or wait for your reply ??

#1280 my solution PR


Tauri CLI wrapper (cli.js) does not work on Alpine Linux

Describe the bug
The JS wrapper for the Tauri CLI downloads a prebuilt binary which does not work on Alpine Linux.
To Reproduce
Steps to reproduce the behavior:

Set up an Alpine Linux Docker image with all build dependencies for Tauri (example)
Use @tauri-apps/cli via yarn tauri build
The command fails without any error message - just exit code 1 returned

Expected behavior
Any of the following would be fine:

error with message "Tauri JS CLI does not work on Alpine - please use the cargo tauri command"
build it from source on Alpine
provide binaries for Alpine

Screenshots

Platform and Versions (required):
(yarn tauri info also fails, so here the output of cargo tauri info)
Operating System - Alpine Linux, version 3.14.3 X64

Node.js environment
  Node.js - 14.18.1
  @tauri-apps/cli - 1.0.0-beta.10
  @tauri-apps/api - 1.0.0-beta.8

Global packages
  npm - 7.17.0
  yarn - 1.22.17

Rust environment
  rustc - 1.56.1
  cargo - 1.56.0

App directory structure
/public
/src
/src-tauri
/node_modules

App
  tauri.rs - 1.0.0-beta.8 (no lockfile)
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
  distDir - ../public
  devPath - http://localhost:41471
  framework - Svelte
  bundler - Rollup

related "feature" request: #2421

The issue is that AlpineLinux uses musl and not gnu so our cli.js won't work because it is not build for musl target. your only option right now, is to build our cli.rs yourself and use it as cargo tauri dev instead of yarn tauri dev.
I am gonna mark this as duplicate and further discussion should be at #2421


CORS error

We are working on comparing HTTP/2 and HTTP/3. As for HTTP/3 we are using aioquic implementation. We are generating metrics using other clients which require Access-Control-Allow-Origin in the header. We want to allow all origins. We tried adding this in the header in the example implementation but didn't get any success. Can someone help us with this issue?

Hello,
I am also facing a similar CORS issue when I try to access content from a server(built using aioquic) using a dash.js client also running over aioquic.
Any help would be greatly appreciated!


Revert tracing pom changes from Batch PR

Reverting tracing pom file changes updated by Blob Batch PR update.
Adding tracing to spotbugs-aggregate report.

@g2vinay The spotbugs-aggregate report is also missing Key Vault packages.
Do you want me to add them as a part of this PR?


Fixed insecure coding pattern

Fixed one suspicious comment and one default admin

Hello 👋  The existing code is intentional, so we will close this PR, but thank you for your contribution.


Release version 0.5.0

thx, this pre-release PR is a good idea, maybe we could try to use it more often.


switch to next file before maxBytesPerFile is reached

rather than switching after maxBytesPerFile is reached
fixes https://github.com/nsqio/go-diskqueue/issues/30

rebase, see if we get an Actions build?

rebased

Thanks for the review!


Update tag_and_release.yml to trigger on PR merge

Is this pull request associated with an issue(s)?
No.
Description
The tag_and_release.yml workflow is not triggering when a PR is merged into master. This PR should fix that.
TODOs

[ ] Should we also bump versions when a push to master is made?

I think the CI adding license headers has finally triggered, so there are a ton of changes on this PR that I did not expect to be here. The only changes relevant to this PR are in .github/workflows/tag_and_release.yml.

There we go! Version tagging is working now!


rxjs-run with TypeScript: property 'scan' does not exist on type 'Stream'.

The return value of DOMSource.events is typed as Stream<Event>, where Stream is an xstream stream. @cycle/rxjs-run adapts the xstream stream to an RxJs Observable. The return value of the adapt function is typed Observable<any> but I believe this value is assigned to a variable typed DevToolEnabledSource & Stream<Event>. TypeScript seems to resolve the value to type Stream<Event>. This causes compilation to fail when Rx.Observable methods are called on the value. Compilation fails with a similar error if I cast Stream<Event> to Observable<Event>. Oddly enough, compilation succeeds if I trigger it a second time without new changes. Here is a test case. Most of the code is generated by create-cycle-app.
I'm not sure what to make of this. It seems likely to be a user error on my part. Thanks for taking a look.
Code to reproduce the issue:
index.ts
import {run} from '@cycle/rxjs-run'
import {makeDOMDriver} from '@cycle/dom'

type Component = (s : Sources) => Sinks;

import {App} from './app'

const main : Component = App

const drivers = {
  DOM: makeDOMDriver('#root')
}

run(main, drivers)

app.tsx
import * as Rx from 'rxjs'

type Sources = {
  DOM : DOMSource;
}

type Sinks = {
  DOM : Observable<VNode>;
}

const add = (x1: number) => (x2: number): number => x1 + x2;

const addOne = add(1);

export function App(sources : Sources) : Sinks {
  const clickCount$ = sources.DOM
    .select('.button')
    .events('click')
    .scan(addOne, 0);

  const vtree$ = Rx.Observable.of(
    <button className="button">Button</button>
  );

  return {
    DOM: vtree$
  }
}

Expected behavior:
The code compiles.
Actual behavior:
Compilation fails with:
[at-loader] Checking finished with 1 errors
[at-loader] ./src/app.tsx:12:6
    TS2339: Property 'scan' does not exist on type 'Stream<Event>'.

Versions of packages used:
"dependencies": {
	"@cycle/dom": "18.3.0",
	"@cycle/rxjs-run": "7.1.0",
	"awesome-typescript-loader": "3.2.3",
	"rxjs": "5.4.3",
	"typescript": "2.5.3"
}

Hi! I believe in app.tsx you should do
import {DOMSource} from '@cycle/dom/rxjs-typings'

(Let's reopen this issue if that doesn't solve it)

Unfortunately not. The value still resolves to the xstream types.
import {DOMSource} from '@cycle/dom/rxjs-typings'

// ...

const button$: DOMSource = sources.DOM.select('.button');
const click$ = button$.events('click');
const clickCount$ = click$.scan(addOne, 0);

[at-loader] Checking finished with 1 errors
[at-loader] ./src/app.tsx:10:9
    TS90010: Type 'DOMSource' is not assignable to type 'DOMSource'. Two different types with this name exist, but they are unrelated.
  Types of property 'elements' are incompatible.
    Type '() => MemoryStream<string | Element | Document | Element[]>' is not assignable to type '() => Observable<Element | Element[]>'.
      Type 'MemoryStream<string | Element | Document | Element[]>' is not assignable to type 'Observable<Element | Element[]>'.
        Property '_isScalar' is missing in type 'MemoryStream<string | Element | Document | Element[]>'.

import {DOMSource} from '@cycle/dom/rxjs-typings'

// ...

const button$: DOMSource = sources.DOM.select('.button') as DOMSource;
const click$ = button$.events('click');
const clickCount$ = click$.scan(addOne, 0);

[at-loader] Checking finished with 1 errors
[at-loader] ./src/app.tsx:10:19
    TS2352: Type 'DOMSource' cannot be converted to type 'DOMSource'.
  Types of property 'elements' are incompatible.
    Type '() => MemoryStream<string | Element | Document | Element[]>' is not comparable to type '() => Observable<Element | Element[]>'.
      Type 'MemoryStream<string | Element | Document | Element[]>' is not comparable to type 'Observable<Element | Element[]>'.
        Property '_isScalar' is missing in type 'MemoryStream<string | Element | Document | Element[]>'.

Can you give more details? Like what is Sources in index.ts?

Oh good question. I simplified the examples a little from the create-cycle-app file structure but tested your suggestion with the original code. I understand now why you said the type needed to be imported. create-cycle-app creates a src/interfaces.ts file where those types are defined. That is where DOMSource should be imported from '@cycle/dom/rxjs-typings' but is imported from '@cycle/dom'.  So I think this is a bug in create-cycle-app. The steps to reproduce are:

create-cycle-app foo
Select TypeScript
Select RxJS
Open src/interfaces.ts.

Sorry for the run-around and thanks for the help!

Good! Open an issue with create-cycle-app then :)

Thanks again for the help. I moved the discussion here: create-cycle-app/issues/123


remove summit banner - from playground?

remove summit banner - from playground
Addresses: https://github.com/apache/beam/issues/22424

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Closing since already addressed elsewhere.


Chromie Time Dropdown Not Auto Selecting

The dropdown Chromie Time option is not auto-selecting any of the CT options (like Legion for example).

Fixed in 2cf8583.


Fix wrong callback call on server handshake ex recv

Just noticed that on rail_recv_handshake_ex_order that's called whenever the client receives a HanshakeEx message from the server, the client accidentally calls the ClientHandshakeEx callback instead of the ServerHandeshakeEx. This causes the client to send an unwanted HandshakeEx messsage, in addition to the handshake the actual client like xfreerdp will send again after that, probably causing a protocol error.
Regardless of this faulty behavior, according to the spec, the client should never send a HandshakeEx message anyway (it's documented that it should respond with a regular Handshake in response to both Handshake and HandshakeEx server messages). Wouldn't it be better to remove the ClientHandshakeEx callback entirely, reducing the API too? I could add a commit to the PR if found necessary.

@freerdp-bot can you test this PR please ?

Ok, looks like this is unused so far (the flag to support handshakeEx is not set)


chore(main): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2023-12-22)
Bug Fixes

Add package metadata and configure automated releases (bcda0d2)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/pavophilip/react-shader-fiber/releases/tag/v1.0.0 :sunflower:


[.NET] Turkish Date support to skipped cases

Added boolean attribute to yaml files to determine if both before and after strings should be checked for match extension and modified methods in AgoLaterUtils to work according to this attribute.
With this modification, all Date test cases (and others in DatePeriod) pass.

@tellarin, this is ready for review and the following PRs depend on changes included in this one


New release?

Could be possible to have a new release, for the last changes added in PR #7 ?
Many thanks in advance.
PS: I have been using tbump for version bumping in some projects, and found it very useful to create the bump commits and make the changes to the version number, if you want to try :slightly_smiling_face:

@jose-lpa hello! Yes, I will release your changes next week. I have an idea, may be to add some weather provider to package? For example, use NASA POWER API to recieve weather for RothC model by coordinates

Hi, I'm not sure if it makes sense to embed connections to 3rd party APIs in this package. I believe this should be for the RothC calculations only, data provider agnostic. And let the users implement the data acquisition as they want or need.

Hi, I'm not sure if it makes sense to embed connections to 3rd party APIs in this package. I believe this should be for the RothC calculations only, data provider agnostic. And let the users implement the data acquisition as they want or need.

Shure, thank you! Added version 0.0.4 to pypi!)

new version added to pypi


Chapter about automation and reproducibility

Purpose/implementation Section
What changes are being implemented in this Pull Request?
This chapter is addressing how automation can help reproducibility. It closes #10

This is a good enough start for now. Gonna merge it.


valid group is needed for auto-renewable subscriptions

If I want to upload some inApp Purchases for recurring subscriptions I get an error that a valid group is needed...where is my mistake??
Errormessage:
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.139.0/spaceship/lib/spaceship/tunes/tunes_client.rb:230:in handle_itc_response': You must have a valid group for auto-renewable subscriptions. (Spaceship::Tunes::Error)
`
here is my ruby script:
require "spaceship" Spaceship::Tunes.login("yyyy", "xxxxx") Spaceship::Tunes.select_team # if you are more in than 1 team app = Spaceship::Application.find("zzzzz") tiers = Array[20,40,60,80] prices = Array[7.99, 6.99, 5.99, 4.99] for i in 0..tiers.size - 1   tier = tiers.at(i)   price = prices.at(i)   app.in_app_purchases.create!(     type: Spaceship::Tunes::IAPType::RECURRING,      versions: {       'de-DE': {         name: "Mitarbeiter",         description: "Freischaltung eines Mitarbeiters pro Monat"       }     },     reference_name: "Produkt zum Preis von %d" % [price],     product_id: "Mitarbeiter_%d" % [tier],     cleared_for_sale: true,     review_notes: "Product for tier %d" % [tier],     review_screenshot: nil,     pricing_intervals:        [         {           country: "WW",           begin_date: nil,           end_date: nil,           tier: tier         }       ],        family_id: nil,       subscription_duration: "1m",   ) end

..sorry, how can I get them?

✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.2

Ruby
2.6.3

Bundler?
false

Git
git version 2.21.0 (Apple Git-122.2)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.15.2 (19C57)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.3

System Locale

Variable
Value

LANG
de_DE.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  desc "Description of what the lane does"
  lane :custom_lane do
    # add actions here: https://docs.fastlane.tools/actions
  end
end

`./fastlane/Appfile`
# app_identifier("[[APP_IDENTIFIER]]") # The bundle identifier of your app
# apple_id("[[APPLE_ID]]") # Your Apple email address

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.139.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
2.3.6

claide
1.0.3

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.14.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.6.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.7.0

tty-cursor
0.7.0

tty-spinner
0.9.2

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.71.1

faraday
0.17.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.13.1

fastimage
2.1.7

gh_inspector
1.1.3

json
2.1.0

mini_magick
4.9.5

multi_xml
0.6.0

rubyzip
1.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.5

bundler
1.17.2

naturally
2.2.0

simctl
1.6.7

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.14.1

signet
0.12.0

memoist
0.16.2

os
1.0.1

googleauth
0.10.0

httpclient
2.8.3

google-api-client
0.36.4

google-cloud-env
1.3.0

google-cloud-core
1.4.1

digest-crc
0.4.1

google-cloud-storage
1.25.0

emoji_regex
1.0.1

forwardable
1.2.0

logger
1.3.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

date
2.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

zlib
1.0.0

libxml-ruby
3.1.0

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

generated on: 2020-01-07

@mhelgers Is this for a live subscription? (i.e. already approved)

no the subscriptions are not live....it is in the sandbox

Please check out the flow in App Store Connect. You are missing the family (=group). Each recurring subscription has to belong to one family/group. You might want to checkout the demo/sample code over at https://github.com/fastlane/fastlane/pull/7834

This was the hint I needed! Tanks a lot!


Fix Asset Config

Expand validation to check asset configs inside their creating accounts.
Fix accounting of changes to asset config.
Migration to repair asset configs from their original transaction data.

#169 is the better option now


arc: core: Fix possible overrun

dyn_reg_info has MPU_DYNAMIC_REGION_AREAS_NUM elements, just changing
the if check to be greater equal to this number to avoid access
MPU_DYNAMIC_REGION_AREAS_NUM element causing an out-of-bounds write.
CID: 205648
Signed-off-by: Flavio Ceolin<EMAIL_ADDRESS>

CID: 205648

You probably want to add
Fixes #
here.

Didn

CID: 205648

You probably want to add
Fixes #
here.

I thought Fixes was being used to reference github issue. I wanted to to put the coverity id for reference. Should I just reference the github issue id ?

I thought Fixes was being used to reference github issue. I wanted to to put the coverity id for reference. Should I just reference the github issue id ?

Yes, if you add the Github issue id, the issue gets automatically closed. Not sure btw if that is best in this case, as also the Coverity issue should be updated and that isn't done automatically (at least not until a next scan).

I thought Fixes was being used to reference github issue. I wanted to to put the coverity id for reference. Should I just reference the github issue id ?

we do have an issue here, so this PR should be marked as fixing the bug.
Fixed #20487


Train quantified object recognition

Hi there
thank you for such a great project.
I have looked into the documentation to see if there is a way to train quantified objects (i know that's still in experience mode) but can any one point me to where to start training grobid-quantities to recognize the quantified object? please

Dear @ahmed-elyoussefi, thank you for your interest in grobid-quantities.
The current implementation of the quantified object recognition uses a dependency parser and does some heuristic to find the quantified object in the sentence.
The plan was, at some point to migrate such implementation to a full machine learning based approach.
I had started to use the current implementation to pre-annotate training data and then I've started annotating some documents in order to set up annotation guidelines and find problems. I didn't get too far with that actually.
If you download the master branch you can pre-annotate data with all the available models using
-gH ../grobid-home/ -gP ../grobid-home/config/grobid.properties -dIn input_directory -dOut output_directory -r -exe createTrainingQuantities

and, for each PDF you will generate training data for each models. So to correct the quantified object data you will get a set of files *.quantifiedObject.xml from the output directory.
Give it a try and let me know if you have any issue.
Regarding the annotation, this part is very experimental because we didn't really think a lot about it.
The annotation are in the form of
```Nine cases are selected as true freak wave events````
with the <measure> tag just wrapping around the measurement with an id and the <quantifiedObject> linking it through a pointer using the attribute ptr. Have a look at what you got and I can anticipate that correcting such annotations it won't be so easy ;-).
The idea, at the begnning of this task, was to use CRF so is unlikely to cover distant links betweeen measurement and objects however I haven't spent enough time to figure out if some alternative exists.
I will probably need this model for a project I'm working on so I might get back to work on it, however I can support you if you need any further help.
I hope I haven't forgotten anything, in any case feel free to ask.
Regards
Luca

@ahmed-elyoussefi FYI I've added some partially corrected examples under https://github.com/kermitt2/grobid-quantities/tree/master/resources/dataset/quantifiedObject/corpus/staging

thank you for your replies
but if i have the annotated quantified objects how can i trigger the training ?
regards

good question... well right now you can't... cause that part haven't been written yet.
You need to wait that I finish that part 😅
Annotating data for this kind of task is very time consuming, so I haven't had time to work on it yet.

OK, @ahmed-elyoussefi I've managed to write the trainer for the quantifiedObject. 😅
It can process data, though the training data haven't been checked by anybody else... so everything is very alpha version. I'm planning to plug in the parser soon.
To run the trainer you need to type ./gradlw train_quantifiedObjects and cross your fingers :-)
This particular trainer is validating the consistency of the training data, so if there are missing links between measurement and objects it will raise an exception, like:
Caused by: org.grobid.core.exceptions.GrobidException: [GENERAL] The training data is inconsistent and should be corrected.
	measureId: null
	quantifiedObjectId: fbf9a8de-3763-4200-90eb-ae5e2fc33eff

Happy annotating!! 😆

awesome
thank you very much
i'll give it a try


[Bug] Game crashes at world creation when using BCLib

Issue description
The game crashes when creating a new world while using BCLib.
Tested with a minimal setup using:

Minecraft 1.21.1
Fabric 0.16.9
Fabric API 0.109.0+1.21.1
Architectury API 13.0.8
Athena 4.0.1
BCLib 21.0.13
Geckolib 4.7
Oritech 0.11.1
World Weaver 21.0.13
owo-lib 0.12.15+1.21

Steps to reproduce

Install the listed mods in the description
Create a new game

Minecraft version
1.21.1 (Latest)
Platform
Fabric
Loader version
0.16.9
Fabric API version
0.109.0+1.21.1
Oritech version
0.11.1
Other relevant versions
BCLib 21.0.13
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
https://pastebin.com/JY731CxP

Issue fixed with 0.11.2


Transactions in RedisOM?

I am looking to perform transactional operations using redis om spring. Does the JPA @Transcational annotation work with redis om spring? If not, is it possible to opt-in to the lower level transactions provided by redistemplate?
Thanks for any advice

+1
@Transactional annotation should send all write commands in the surrounded method in one Redis transaction

Planned for 1.0.0


Enable CreateSubnetwork option for Gke Cluster

Pass configuration of clusterVersion from resourceClass to GKE Cluster spec
Pass configuration of CreateSubnetwork from resourceClass into the GKE Cluster Spec

Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #453
Checklist:

[ ] Documentation has been updated, if necessary.
[ ] Pending release notes updated with breaking and/or notable changes, if necessary.
[ ] Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
[ ] Code generation (make generate) has been run to update object specifications, if necessary.
[ ] CRD manifests generation (make manifests) has been run to update CRD manifests yaml file specifications, if necessary.
[ ] Update dependencies (make vendor) has been run to update Gopkg.lock file, if necessary
[ ] RBAC permissions in clusterrole.yaml have been updated to include new types, if necessary
[ ] All related commits have been squashed to improve readability.
[ ] Comments have been added or updated based on the standards set in CONTRIBUTING.md

@lukeweber were you able to verify that this update fixes the issue?

I verified that it does get around the issue we were having creating all clusters in the default subnet and the related bug. Testing pending on gitlab once we get the new gitlab controller.

@lukeweber sounds good.
Could you lease lint this change so we have a good build?


Added Modern chair E-commerce project #318

Modern Chair E-Commerce Project: Designed a stylish, responsive platform for selling modern chairs, built using HTML, CSS, and JavaScript. The site features detailed product descriptions, including chair dimensions, materials, and pricing. Users can browse, view product details, and add items to the cart for a streamlined shopping experience. The design prioritizes user engagement with a clean layout and intuitive interface.
https://github.com/user-attachments/assets/9b948540-ab12-402f-b641-f292d7ac9936
Features:
Browse modern chair collections.
Add to cart and checkout functionality.
Product details and description for each item.
Save user data and cart items locally.

mention the issue no

Hi @iamrahulmahato it is already mentioned in title #318


Prevent ossification of ambient

In ambient, we have made a lot of design decisions, from behaviors, APIs, headers, etc. All of this is "alpha". Given the size and scope of these changes, and that we probably only have one opportunity to "get it right", it's critical that we can make the right decisions.
IMO, this can only reasonably done through iteration. Theoretically the feature progression between alpha beta stable provides this. In practice, things have been historically locked in after the first alpha release (1.18 for ambient).
To avoid this, we should make explicit measures to avoid ossification in ambient so that we have flexibility to make required changes.
Ideas:

prefix APIs with experimental-
Very very clear, alarms blaring, warning documentation
Following above, make uses explicitly acknowledge the alpha style in ambient??
Vague idea - intentionally make breaking changes. This is likely only useful if we remain in alpha for  a long time without any natural changes. This is a bit like the Google SRE trick or intentional downtime when exceeding SLOs.

cc @costinm

I think most impact will be to have alpha/experimental off by default, with narrow opt-in ( workload ) and clear experimental- prefix.
We can also have an install mode that clearly indicates it's experimental and unsupported and allows broader use for testing.

It may ne better to identify first what we do want to treat as stable:

api - K8S Gateway seems clear, a subset of Istio beta APIs ( authz, etc ) - when applied to a gateway
an narrow subset of api that apply to ztunnel
default protocol based on h2 and a subset of headers
MCS API if we can finish enabing it
???

I think most install options, labels, annotations are to be treated as experimental - for a long time we had the goal to either promote to CRD and  beta or deprecate. That probably won't work for sidecar/original Istio, but may work for ambient if we start right.

not stale

not stale


enforce min python version

PR Checklist
Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change

PR Type
What kind of change does this PR introduce?
when running lbrynet command, it checks the min python version and errors if python is not compatible
Why is this change necessary?
version before python 3.7 do not check that the version is too low when you pip install

[x] Bugfix
[ ] Feature
[ ] Breaking changes (bugfix or feature that introduces breaking changes)
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number: N/A
What is the current behavior?
What is the new behavior?
Other information

According to this: https://stackoverflow.com/a/48777286/376675
As long as you have a recent version of pip tools (which works in python2.7) you should get automatic python checks.
Do we really need to add this custom version check code into lbry?

Here's what I'm seeing (in a fresh venv):
$ pip --version
pip 19.1.1 from /home/grin/.virtualenvs/lbry/lib/python3.6/site-packages/pip (python 3.6)
$ python --version
Python 3.6.7
$ pip install -e .
Obtaining file:///home/grin/code/lbry/lbry
Collecting torba (from lbrynet==0.38.0rc2)
...
Successfully built torba
Installing collected packages: multidict, idna, yarl, attrs, typing-extensions, idna-ssl, async-timeout, chardet, aiohttp, pycparser, cffi, asn1crypto, coincurve, pbkdf2, six, cryptography, pylru, plyvel, torba, netifaces, aioupnp, appdirs, certifi, colorama, distro, base58, protobuf, msgpack, ecdsa, pyyaml, docopt, hachoir, lbrynet
  Running setup.py develop for lbrynet
Successfully installed aiohttp-3.5.4 aioupnp-0.0.12 appdirs-1.4.3 asn1crypto-0.24.0 async-timeout-3.0.1 attrs-18.2.0 base58-1.0.0 certifi-2019.3.9 cffi-1.12.1 chardet-3.0.4 coincurve-11.0.0 colorama-0.3.7 cryptography-2.5 distro-1.4.0 docopt-0.6.2 ecdsa-0.13 hachoir-3.0a5 idna-2.8 idna-ssl-1.1.0 lbrynet msgpack-0.6.1 multidict-4.5.2 netifaces-0.10.9 pbkdf2-1.3 plyvel-1.0.5 protobuf-3.6.1 pycparser-2.19 pylru-1.1.0 pyyaml-4.2b1 six-1.12.0 torba-0.5.4 typing-extensions-3.7.2 yarl-1.3.0
$ lbrynet start
Traceback (most recent call last):
  File "/home/grin/.virtualenvs/lbry/bin/lbrynet", line 11, in <module>
    load_entry_point('lbrynet', 'console_scripts', 'lbrynet')()
  File "/home/grin/.virtualenvs/lbry/lib/python3.6/site-packages/pkg_resources/__init__.py", line 489, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/home/grin/.virtualenvs/lbry/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2843, in load_entry_point
    return ep.load()
  File "/home/grin/.virtualenvs/lbry/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2434, in load
    return self.resolve()
  File "/home/grin/.virtualenvs/lbry/lib/python3.6/site-packages/pkg_resources/__init__.py", line 2440, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/home/grin/code/lbry/lbry/lbrynet/extras/cli.py", line 16, in <module>
    from lbrynet.extras.daemon.loggly_handler import get_loggly_handler
  File "/home/grin/code/lbry/lbry/lbrynet/extras/daemon/__init__.py", line 1, in <module>
    from lbrynet.extras.daemon import Components  # register Component classes
  File "/home/grin/code/lbry/lbry/lbrynet/extras/daemon/Components.py", line 15, in <module>
    from lbrynet import utils
  File "/home/grin/code/lbry/lbry/lbrynet/utils.py", line 264, in <module>
    @contextlib.asynccontextmanager
AttributeError: module 'contextlib' has no attribute 'asynccontextmanager'

wait nvm, didn't update setup.py

ok here's all we really need


Apex minecraft hosting server "failed to mark promise as success because it has succeeded"

Renting a server from apex and installed few mods was running great but then the console started filling with the error above and everytime it appeared it lagged the whole server. Just looking for a fix so i can play on the server with friends tried updating netty on the server by replacing the one in both the com and io folders with the latest jar on the netty site and i still get the errors that lag everything. I saw another post said solved but im not sure how to use the solutions cause they involve installing a differnt netty or something and i dont know how to do that on the server. Heres the error that repeatedly apears. Dont even need to move or do anything in game just start it join server and then this starts. Thanks for the help id give a crash report but the game never crashes just lags or rather freezes and then continues seconds later before repeating
io.netty.channel.ChannelOutboundBuffer safeSuccess
WARNING: Failed to mark a promise as success because it is done already: DefaultChannelPromise@118e41(success)

@Divx001 this sounds like a bug in the system that is using netty. Which basically means they complete a ChannelPromise but also forward it through the pipeline. Please report the issue to the software creator itself


added my own features in my PPP (v1.2)

Codecov Report

Merging #55 (4d40e4b) into master (526df79) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #55   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


New feature: Change app language to other than system default

I am very advanced with this and I have it fully working in all windows and dialogs
Code is preview and a bit dirty mainly because Settings activity doesn't support rotation (added it in draft using recreate() which is ok in gui settings window). Also some checks about the APIs and Manifest finer adjustments
It is really great for multilingual people (like I prefer device system lang in Fr but I prefer your app in English)
Let me know if you have time and you want to look at it right away

it is nearly done, I will commit it asap
Will be my last work on the GUI.
After that, I will continue with translating the Help french doc


added decorator type in index.d.ts

I have added the type definitions for the decorator as well as the wrapper function.

@zalmoxisus Im sorry, but i recently upgraded your package to webpack 4 and babel 7. it doesnt fix TS class issues but upgrading the source code might get us closer. i have tested this with all 3 examples provided.

That's great to have those updated. Thanks! I published it as 0.3.3.


[bug] Invalid argument: Instance of 'QPurchaseUpdatePolicy'

My code from Qonversion Docs example:
var purchaseOptions = QPurchaseOptionsBuilder()
    .setOldProduct(oldProduct)
    .setUpdatePolicy(QPurchaseUpdatePolicy.chargeFullPrice)
    .build();
var entitlements = await Qonversion.getSharedInstance().purchaseProduct(
    product,
    purchaseOptions: purchaseOptions
);

only when i call setUpdatePolicy with any QPurchaseUpdatePolicy, i receive error:

Invalid argument: Instance of 'QPurchaseUpdatePolicy'

It think, the problem is in qonversion_internal.dart on 121 line, you are providing enum value instead of basic String value
Constants.kUpdatePolicyKey: purchaseOptions.updatePolicy

fix should be smth like:
final updatePolicy = purchaseOptions.updatePolicy;
...
Constants.kUpdatePolicyKey: updatePolicy != null
            ? StringUtils.capitalize(describeEnum(updatePolicy))
            : null,
...

Hi @AErmek ,
Thank you for bringing this to our attention! That's really our fault. The fix will be released very soon.

The new version 9.2.1 with the fix has just been released. Thank you again for reporting this bug!
I'll go ahead and close this issue, but feel free to reopen it or create new ones if you have any further questions.


doc: add managed datahub & self-hosting section

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

updated sidebar to have "managed-datahub" & "self-hosting" section
updated managed datahub overview page to generated-index page

note : let's go with "Acryl Cloud"


Add links to branches on pull request

Modifies branch names on the pull request summary page are now links to the branch that is being merged into/from.
The CONTRIBUTING.md says that only English translations are maintained in this repo, but I still modified the markdown that was embedded in other translations. Please let me know if this was the wrong move.
Screenshots:
Merging from one repo's branch to another's:

Merging into the same repo:

Merging from a deleted repo:

Closes #5672

Codecov Report

Merging #6424 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6424      +/-   ##
==========================================
- Coverage   38.87%   38.87%   -0.01%
==========================================
  Files         365      365
  Lines       51393    51393
==========================================
- Hits        19980    19978       -2
- Misses      28544    28546       +2
  Partials     2869     2869

Impacted Files
Coverage Δ

models/repo_list.go
66.84% <0%> (-1.06%)
:arrow_down:

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 fb2ea06...80a40eb. Read the comment docs.

@lafriks Hopefully these addressed everything. Sorry for the delay.

Please resolve conflicts

can you please resolve conflicts?

just tell us if you need help

ok looks like this already got implemented by another pull already ...


Requirement for custom baud rate setting function

I hope to add a custom baud rate feature so that users can use a baud rate of 2000000 or higher on their own. Currently, I can use a maximum baud rate of 6000000, but "vscode serial monitor" does not support this configuration

@SeaHi-Mo Have you tried using the vscode-serial-monitor.customBaudRates setting?

Thank you, this is very useful


can't run app due to 'NoSucnMethodError'

see the screenshort

logcat:
07-25 15:35:16.207 24781-24803/com.example.flutterhelloworld I/flutter: When the exception was thrown, this was the stack: 07-25 15:35:16.220 24781-24803/com.example.flutterhelloworld I/flutter: #0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:46:5)     #1      MPListView.build (package:flutter_hello_world/widgets/mp_lisview.dart:15:33) 07-25 15:35:16.221 24781-24803/com.example.flutterhelloworld I/flutter: #2      StatelessElement.build (package:flutter/src/widgets/framework.dart:3695:28)     #3      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3642:15)     #4      Element.rebuild (package:flutter/src/widgets/framework.dart:3495:5)     #5      ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:3622:5)     #6      ComponentElement.mount (package:flutter/src/widgets/framework.dart:3617:5)     #7      Element.inflateWidget (package:flutter/src/widgets/framework.dart:2907:14)     #8      Element.updateChild (package:flutter/src/widgets/framework.dart:2710:12)     #9      SingleChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:4654:14)     #10     Element.inflateWidget (package:flutter/src/widgets/framework.dart:2907:14)     #11     Element.updateChild (package:flutter/src/widgets/framework.dart:2710:12)     #12     SingleChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:4654:14)     #13     Element.inflateWidget (package:flutter/src/widgets/framework.dart:2907:14)     #14     Element.updateChild (package:flutter/src/widgets/framework.dart:2710:12)     #15     SingleChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:4654:14)     #16     Element.inflateWidget (package:flutter/src/widgets/framework.dart:2907:14)     #17     Element.updateChild (package:flutter/src/widgets/framework.dart:2710:12)     #18     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3653:16)     #19     Element.rebuild (package:flutter/src/widgets/framework.dart:3495:5)     #20     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:3622:5)

Sorted it out. It has to do with permission.
Goto your mobile settings -> Apps & Notification -> Select the app -> Permission -> Enable disabled permission.


Images need to be updated

Hi - the images need to be updated. The computed entities now show a yellow lightening symbol instead of black. A colleague was looking for info but said couldn't find it because he didn't see the updated images.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 016cc5b0-e90e-c87e-874f-d71cc5d740b8
Version Independent ID: 486eeb0a-d69d-3a9a-f17d-10482de0dcf2
Content: Computed entity scenarios and use cases - Power Query
Content Source: powerquery-docs/dataflows/computed-entities-scenarios.md
Service: powerquery
GitHub Login: @radacad
Microsoft Alias: bezhan

Please ignore (I'm using bot automation to add tags). #please-open

Hi @pawarbi
All of the images you specified needing updates have been updated along with all mentions of computed entities being updated to computed tables throughout the Power Query documentation.


Relax rails dependency to enable compatibility with >= 3.2.13

Relax rails dependency further, so the gemspec should not interfere with future rails updates.

Thanks for the patch.


fix(global-left-nav): refactor for a11y in v6

Overview
Resolves
https://github.ibm.com/Bluemix/core-dev/issues/3881
Best keyboard accessible navigation ever, for the global left nav.
Added
Some javascript to handle more keypresses.
Removed
...nothing?
Changed
Menu trigger is now a <button> element.
Nav items are closer together, icons are smaller. (these design tweaks are already in staging, will be cleaned up in Common after this PR is merged)
Testing / Reviewing
Tab to hamburger, use space/enter to open, use tab OR arrows to navigate! Home and end keys select first and last item. Menu closes automatically when you tab out of menu.

Our refator commit type doesn't trigger semantic-release, so I renamed it. Also changed the scope.


Test: ensure dep-infos do not collide when cdylib and bin coexist

What does this PR try to resolve?
A new test build::no_dep_info_collision_when_cdylib_and_bin_coexist
is added to prevent regression.
Note that on Windows MSVC cargo does not use metadata, so a collision
still happens when cdylib and bin targets coexist. This is tracked in
the other issue already.
Closes #9325
r? @ehuss

Thanks!
@bors r+

:pushpin: Commit e2142487d4916e68b80d50edbadda78b61925b21 has been approved by ehuss

:hourglass: Testing commit e2142487d4916e68b80d50edbadda78b61925b21 with merge c9a8199e927192d4f03f73a14f97faa29c9df956...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing c9a8199e927192d4f03f73a14f97faa29c9df956 to master...


Please add our CVPR 2023 paper to face reconstruction

Hi, @DWCTOD,
Could you please add our CVPR 2023 paper to the list:
Title: A Hierarchical Representation Network for Accurate and Detailed Face Reconstruction from In-The-Wild Images
Topic: Face reconstruction
Paper link: https://arxiv.org/pdf/2302.14434.pdf
Project Link: https://younglbw.github.io/HRN-homepage/
Thanks a lot!

Received,thanks


Build from source throws an error

When I git clone and then gradle build, I get the following output.
`> Configure project :
Fabric Loom: 0.10.66
FAILURE: Build failed with an exception.

Where:
Build file '/home/ahpt/Documents/Git/Quadz-development/build.gradle' line: 72

What went wrong:
A problem occurred evaluating root project 'quadz'.

Could not get unknown property 'publish.lazurite.alias' for root project 'quadz' of type org.gradle.api.Project.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 676ms`
I am still quite new to building from source, so please educate me if there is something that I am doing incorrectly. Thank you!

Fixed in d32e4882e4242ace48cba20828a4f57164dbc285


fixed background of email in footer and functioning of back to top button in free e books webpage

Related Issue
Fixes:  #1817
Description
fixed background of email in footer and functioning of back to top button in free e books webpage
Type of PR

[X] Bug fix

Screenshots / videos (if applicable)

https://github.com/anuragverma108/SwapReads/assets/159682348/2906c082-d263-4e10-8d39-ac8949c3d1a6
Checklist:

[X] I have made this change from my own.
[X] My code follows the style guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers and screenshots after making the changes.

@RitiChandak @anuragverma108 i have creates the new pull request and updated the issue please merge my pull request under appropriate gssoc level .


Create Counter on Journals, Referrals and E-books.

Feature description
In this counter, for ex:- Journals counter will begin from 0 to 518+ which will give an animated effect.
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

hey @Mahak008 are you working on this issue ?

I would like to work on this issue ,please assign me this issue under GSSOC-23.


helm-service: Helm upgrade fails

When trying to onboard the adservice of the hipstershop using the master version of Keptn, the helm-upgrade fails with the following error:

Error when installing/upgrading chart hipstershop-dev-adservice-generated in namespace hipstershop-dev: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "DesitinationRule" in version "networking.istio.io/v1alpha3", unable to recognize "": no matches for kind "virtualservice" in version"networking.istio.io/v1alpha3"]

Not necessarily a Keptn error, but sounds like the manifests contain something that's not allowed in there? Can you show us the manifests?

The content for adservice.yaml:
Copyright 2018 Google LLC

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
apiVersion: apps/v1
kind: Deployment
metadata:
name: adservice
spec:
selector:
matchLabels:
app: adservice
template:
metadata:
labels:
app: adservice
spec:
terminationGracePeriodSeconds: 5
imagePullSecrets:
- name: regcred
containers:
- name: server
image: adservice
ports:
- containerPort: 9555
env:
- name: PORT
value: "9555"
#- name: JAEGER_SERVICE_ADDR
#  value: "jaeger-collector:14268"
resources:
requests:
cpu: 200m
memory: 180Mi
limits:
cpu: 300m
memory: 300Mi
readinessProbe:
initialDelaySeconds: 20
periodSeconds: 15
exec:
command: ["/bin/grpc_health_probe", "-addr=:9555"]
livenessProbe:
initialDelaySeconds: 20
periodSeconds: 15
exec:
command: ["/bin/grpc_health_probe", "-addr=:9555"]
apiVersion: v1
kind: Service
metadata:
name: adservice
spec:
type: ClusterIP
selector:
app: adservice
ports:

name: grpc
port: 9555
targetPort: 9555

`# Copyright 2018 Google LLC

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
apiVersion: apps/v1
kind: Deployment
metadata:
name: adservice
spec:
selector:
matchLabels:
app: adservice
template:
metadata:
labels:
app: adservice
spec:
terminationGracePeriodSeconds: 5
imagePullSecrets:
- name: regcred
containers:
- name: server
image: adservice
ports:
- containerPort: 9555
env:
- name: PORT
value: "9555"
#- name: JAEGER_SERVICE_ADDR
#  value: "jaeger-collector:14268"
resources:
requests:
cpu: 200m
memory: 180Mi
limits:
cpu: 300m
memory: 300Mi
readinessProbe:
initialDelaySeconds: 20
periodSeconds: 15
exec:
command: ["/bin/grpc_health_probe", "-addr=:9555"]
livenessProbe:
initialDelaySeconds: 20
periodSeconds: 15
exec:
command: ["/bin/grpc_health_probe", "-addr=:9555"]
apiVersion: v1
kind: Service
metadata:
name: adservice
spec:
type: ClusterIP
selector:
app: adservice
ports:

name: grpc
port: 9555
targetPort: 9555
`

I tested installing the adservice using the current master version and I cannot reproduce the error.
My assumption for this error is that Istio was not properly installed.


ADR008 - Page ordering defined by pointers to the next page in form objects

Thanks for sharing these three options in the ADR. Would it be worth adding a short description of the impact on migration to and from GOV.UK Forms by us going with "Option 3: Treat pages as a linked list, with a pointer to the next page"?
I'm thinking about potential scenarios where colleagues may want to import one or a bunch of forms to GOV.UK Forms from other GOV.UK form building platforms (and vice versa) without having to create them from scratch. I couldn't find the specific schemas, but as two examples:
https://github.com/XGovFormBuilder/digital-form-builder/blob/main/model/src/schema/schema.ts
https://ministryofjustice.github.io/form-builder-metadata-api-docs/#tag/Services/operation/latest-service-metadata
Alignment with existing schemas might help to converge in the future?

@danielburnley Good question. Thanks for breaking the challenge down a bit more.
We've had a few emails from people looking to migrate to GOV.UK Forms, mostly from COTS platforms, and two from government platforms, though they've not specifically asked for "import existing forms" as a feature.
I was more thinking about generally trying to converge and avoid lock-in within UK central government platforms (COTS vendors generally aren't incentivised to do this). I think this ADR would benefit from documenting where we think using an existing approach would cause problems for us, both in the schemas and the other aspects you mentioned? I'd hope that would be useful for future developers on the team to understand why we are taking our own approach.

👋 I know that this is long closed.. but opt 2 (point to next page vs position) would be better. Opt 1 won't work when you have significant branching. I haven't yet implemented this for our runner, but the graph view in our designer is based on computational graphs. you can use algorithms to go forwards and backwards. and typically very well documented.. since it's just maths.
singly linked should be ok. I'd love to work a solution for this that works for all of us!


Lifecycle Mixin (transitions example)

I thing when i click ok on Confirm Box or click on the dashboard link without input (empty string) it will transition to 'Dashboard' but nothing happen.

confirmed ... wonder what's wrong ...

Looks like this line of code is bailing out of the transition for some reason:
https://github.com/rackt/history/blob/master/modules/createHashHistory.js#L92-L93

I tried with BrowserHistory but still do not work.

same bail out there too: https://github.com/rackt/history/blob/master/modules/createBrowserHistory.js#L64-L65

Looks like this line of code is bailing out of the transition for some reason:

That line is fine. It returns early for POP, because POP transitions change the URL immediately. For PUSH&REPLACE we need to change the URL manually once the transition finishes.
As far as I can tell the problem is here: https://github.com/rackt/react-router/blob/master/modules/useRoutes.js#L214 . state reflects the old location in contrast to what the comment suggests. With transition hooks, match doesn't get to the point where it updates state since it uses partialNextState (https://github.com/rackt/react-router/blob/master/modules/useRoutes.js#L42).
My guess is that that branch should update state as well:
  function match(location, callback) {
      if (partialNextState && partialNextState.location === location) {
        // Continue from where we left off.
        finishMatch(partialNextState, function (err, nextLocation, nextState) {
              if (nextState)
                state = nextState
              callback(err, nextLocation, nextState)
            });
      } else { ... }

The goal was for useRoutes.match to be a pure function, but useRoutes.listen would be the one to mutate state.

Is there any workaround to this?  I'm unable to get history.pushState, history.replaceState, nor history.transitionTo` to actually load the component at the new url.

I had to downgrade to beta4.

This is happening for me too. :(

I've found that wrapping the pushState call in a timeout seems to fix the problem. I'm not sure why, but so far so good.
window.setTimeout(function() {
    this.props.history.pushState(null, '/protected');
}.bind(this), 500);

hit this as well. any work around, or idea where the issue is to PR?

As far as I can tell... the issue comes in when you attempt to do a transition in the middle of a state change loop. I've wrapped my transitions in a setTimeout when I need to transition in lifecycle methods and it seems to work for now. It's definitely a hacky work-around though.

I didgged in as much as I could and @taurose seems to be right on the money, partialNextState is never actually processed into state

Is there going to be an rc2 soon that includes this fix?

@mjackson your fix looks good, but there might an unintended side effect.
Server rendering currently utilizes useQueries.match, and since that no longer mutates state, calls to history.isActive on the server will no longer return the correct value (hence server rendering - renders active Links as active failing in current build). One potential fix for this might be to transition the memory history to the correct location in match, as I've done here https://github.com/schnerd/react-router/commit/01bd815e893950c3be6345686ffadd648ecd525f. If that looks good, or if you have other ideas on how this might be solved, let me know and I can submit a PR.
As a quick aside, the removal of null arguments in be37196 also breaks the test server rendering - sends null values when no routes match.
thanks for all your work on the router

Was this fixed? I think I'm running into this issue (R-R 1.0.3, using createBrowserHistory) where I attempt to transition state using this.history.replaceState(null, '/myPage') and the URL updates but the app state doesn't...

I guess I'm running after the same issue described by @rubencodes :(


Enable sync stack for Form Recognizer

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

/azp run java - formrecognizer - tests

/azp run java - formrecognizer - tests


planetscale-serverless: allow Client as a valid type

I have no actually knowledge of TypeScript, but this should mitigate the issues in https://github.com/drizzle-team/drizzle-orm/issues/1743
Passing a Client instance to the drizzle constructor properly handles connection pooling and safely creating new connections when needed.
Client itself supports execute() and transaction() just like an individual Connection, just done in a more correct way.
Related: https://github.com/drizzle-team/drizzle-orm-docs/pull/210
As for documentation, currently for mysql2, it's documented both how to use a single connection and a connection pool, so this change is our version of a connection pool. So it might make sense to document both ways? But really, I'd personally believe should always use a Client rather than an explicit single Connection in all cases. Unlike a traditional MySQL connection, our Connection is essentially free and doesn't translate to a new TCP connection. It's just an object to store shared state.
Given my very limited knowledge of TypeScript, I'm not really sure how to verify this change works and passes the type checker, but I read through the code in this driver and it seems like this type union would satisfy all of the uses.
Example script I used to validate behavior:
https://gist.github.com/mattrobenolt/b33e965d285caa6ade5c2484c28d9194

Session logs
|INFO| ok method="Execute" query="select 2"              session_id="4Bbn0YabRmQ54TpY4PH2r" client_session=false
|INFO| ok method="Execute" query="select 1"              session_id="LM0chCw2uLqRaVvBH9mjI" client_session=false
|INFO| ok method="Execute" query="BEGIN"                 session_id="XK2sRh5KXx_kMXTMAKoZS" client_session=false
|INFO| ok method="Execute" query="select 1"              session_id="XK2sRh5KXx_kMXTMAKoZS" client_session=true
|INFO| ok method="Execute" query="savepoint sp1"         session_id="XK2sRh5KXx_kMXTMAKoZS" client_session=true
|INFO| ok method="Execute" query="select 2"              session_id="XK2sRh5KXx_kMXTMAKoZS" client_session=true
|INFO| ok method="Execute" query="release savepoint sp1" session_id="XK2sRh5KXx_kMXTMAKoZS" client_session=true
|INFO| ok method="Execute" query="COMMIT"                session_id="XK2sRh5KXx_kMXTMAKoZS" client_session=true

From these logs, each session_id represents a unique Connection. So we can see that the first two queries each used a new session with no client_session, meaning, the driver didn't send along an existing session. It was a new session entirely.
Then the subsequent BEGIN until COMMIT block shares the same session_id correctly, and after the first BEGIN, we can see client_session=true meaning, we are indeed sending along the existing client session for each query.

please see https://github.com/drizzle-team/drizzle-orm/issues/1743#issuecomment-1892860001
you can currently pass in a Client but the same issue is still present

Can you provide evidence otherwise? I cannot reproduce. If you share code along with ps-http-sim logs (or I can run it myself) I can see what's wrong.

lemme give this a go
didnt have time to set up full replication for the issue
but I can quickly test this fix

confirmed working 100%
used this repo for testing https://github.com/McPizza0/drizzle-ps-concurrency-test

@AndriiSherman this fixes all the linked issues
I'll open a pr to docs to update the new method

@McPizza0 Hi, I appreciate it, but we already have this taken care of.

ah yeah, I see the docs pr now: https://github.com/drizzle-team/drizzle-orm-docs/pull/210
🫡

@mattrobenolt thanks a lot for you PR! We will include those changes in the next release


Maid 1466

Launcher IPC integration. Switched to the Launcher compatible API instead of the older FFI approach

r? @ustulation
(maidsafe_highfive has picked a reviewer for you, use r? to override)

r? @Viv-Rajkumar

merging this to allow the github issues with the example get raised.


Document multiline string cmd

Introduced in 2.0. Related: https://github.com/iterative/dvc/pull/5194
There was a docs patch for repro (https://github.com/iterative/dvc.org/pull/2071) which is missing (most likely got lost during merge in v1 -> v2 docs transition). I'll try adding that as well.

We still don't support multiline string in dvc.lock properly. Need to see what we can do, without causing compatibility issues.
Keeping it in draft till then.


video-audio-caption download correlation

Have you read the FAQ and checked for duplicate issues:yes
What version of Shaka Player are you using:v2.1.6
Can you reproduce the issue with our latest release version:yes
Can you reproduce the issue with the latest code from master:
Are you using the demo app or your own custom app:demo
If custom app, can you reproduce the issue using our demo app:
What browser and OS are you using:chrome/ff
What are the manifest and license server URIs:
(you can send the URIs to<EMAIL_ADDRESS>instead, but please use GitHub and the template for the rest)
**What did you do?**opened stream and waited
What did you expect to happen? stream must play as fast as possible
What actually happened? several seconds to wait additionally
I throttled chrome to low network speed and saw that palyer downloaded segments in this way:
video-fragment-1(downloaded)
audio-fragment-1(downloaded)
caption-fragment-1(downloaded)
audio-fragment-2(downloaded)
caption-fragment-2(downloaded)
audio-fragment-3(downloaded)
caption-fragment-3(downloaded)
audio-fragment-4(downloaded)
video-fragment-2(still downloading)
caption-fragment-4(downloaded)
audio-fragment-5(downloaded)
caption-fragment-5(downloaded)
So video/audio/caption downloading is not correllated. If player have no video, why downlaod audio and caption? The same problem i described at https://github.com/Dash-Industry-Forum/dash.js/issues/1319
Can you make same fix here? It will be very helpful for low speed users.

From the dash.js code you referenced, it would seem that you want us to avoid buffering more audio than we have already buffered for video.  Is that correct?
Can you explain the problem a bit more?  Why is it wrong to buffer video and audio independently?
Do you expect us to wait until a video segment is buffered before fetching the corresponding audio segment?  Or fetch them simultaneously?

"you want us to avoid buffering more audio than we have already buffered for video. Is that correct?" - correct
"Do you expect us to wait until a video segment is buffered before fetching the corresponding audio segment? Or fetch them simultaneously?" - both methods wiil be ok, because at the moment available bandwith is used for downloading future audio-captions, but this bandwith could be used to download necessary video segment:

So, is it possible?

I think this is feasible.  Tentatively scheduled for v2.3.

We hadn't planned to work on this right now, but it came up while working on another issue.  It seems to help that other issue, and it is fairly simple, so we will clean it up and try to get it out soon.

Fix cherry-picked to v2.3.5.

@joeyparrish Thanks!


Option for UUIDs to be lowercase

Our UUIDs fail to validate against your spec because the letters a-f in their hex representations are lowercase rather than uppercase. Suggest adding an argument to isUUID that allows us to specify that lowercase uuids are allowed. This is particularly frustrating when used in conjunction with express-validator, since their syntax for checking headers makes preprocessing the uuids to all uppercase rather cumbersome.

oops just noticed that this is not our bug, sorry

The regular expressions have an i suffix so the match is case-insensitive:
> validator.isUUID('3ea9c08d-824c-4bdf-995f-5456ed103a7a')
true
> validator.isUUID('3EA9C08D-824C-4BDF-995F-5456ED103A7A')
true

Are you sure your UUIDs are valid? If so, are you sure you're matching against the correct UUID version?
> validator.isUUID('3ea9c08d-824c-4bdf-995f-5456ed103a7a', 4)
true
> validator.isUUID('3ea9c08d-824c-4bdf-995f-5456ed103a7a', 3)
false

Ah :smile:


Is django-axes latest version supports django 1.11?

Is the latest version of django-axes supports Django 1.11?

Yes it does.


No HNSNetwork of type L2Bridge can be created when Wi-Fi is enabled

Issue: Calling hcsshim.HNSNetworkRequest to create a L2Bridge hnsnetwork returns an error when Wi-Fi is on.
Windows speficiations
Edition: Windows 10 Enterprise
Version: 20H2
OS build: 19042.1826
In order to reproduce do the following:
Preconditions:

Unplug the LAN cable of your Windows machine where you will try to reproduce the issue.
Turn on the Wi-Fi of your Windows machine and connect to your WLAN network.
Check by calling ipconfig -all that your Windows machine has an IPv4 address assigned to the Wi-Fi adapter (see attached file
output_of_ipconfig_all_when_wifi_on.txt).
Call on an admin PowerShell get-hnsnetwork | ? Name -Like "cbr0" | remove-hnsnetwork to delete a possible already existing HNSNetwork named "cbr0".

Test steps:

Copy the content of the file "hnsnetwork_test.pdf" to \src\github.com\microsoft\hcsshim\hnsnetwork_test.go
Navigate to the directory \src\github.com\microsoft\hcsshim
Call on an admin CMD go test -v  --> the output that I become is the following:

=== RUN   Test_CreateHnsNetwork
    hnsnetwork_test.go:20: Network 'cbr0' does not exist
    hnsnetwork_test.go:38: Attempting to create HNSNetwork {"Name":"cbr0","Type":"L2Bridge","Subnets":[{"AddressPrefix":"<IP_ADDRESS>/24","GatewayAddress":"<IP_ADDRESS>"}]}
    hnsnetwork_test.go:41: failed to create HNSNetwork cbr0. Reason: failed during hnsCallRawResponse: hnsCall failed in Win32: The parameter is incorrect. (0x57)
--- FAIL: Test_CreateHnsNetwork (1.62s)
FAIL
exit status 1
FAIL    github.com/Microsoft/hcsshim    1.945s

Call on an admin PowerShell get-hnsnetwork --> The HNSNetwork named "cbr0" is not in the output.

Now do the following:

Turn off the Wi-Fi on your Windows machine.
Plug in the LAN cable
Check by calling ipconfig -all that your Windows machine has an IPv4 address assigned to the Ethernet adapter (see attached file
output_of_ipconfig_all_when_wifi_off.txt)
Navigate to the directory \src\github.com\microsoft\hcsshim
Call on an admin CMD go test -v  --> the output that I become is the following:

=== RUN   Test_CreateHnsNetwork
    hnsnetwork_test.go:20: Network 'cbr0' does not exist
    hnsnetwork_test.go:38: Attempting to create HNSNetwork {"Name":"cbr0","Type":"L2Bridge","Subnets":[{"AddressPrefix":"<IP_ADDRESS>/24","GatewayAddress":"<IP_ADDRESS>"}]}
--- PASS: Test_CreateHnsNetwork (10.80s)
PASS
ok      github.com/Microsoft/hcsshim    11.116s

Call on an admin PowerShell get-hnsnetwork --> The HNSNetwork named "cbr0" is in the output (see attached file
output_of_get-hnsnetwork_wifi_off.txt)

hnsnetwork_test.pdf

This problem is lasting since a long time: see https://github.com/docker/for-win/issues/2237


[Style] Nav Bar for Small devices

What's the style idea?
We need to improve the nav bar that pops up in case of smaller screens.
The transparent background can be made better.
When the cursor is on any of the other pages like home,about,components etc there is no indication or a proper CSS styling done for it.

I can contribute in that. This is my first open source contribution :)
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[X] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Proceed @Gauranshgoel123


Add utility function to enforce hash prefix uniqueness

@mdboom @pv Resolves #299 by adding a utility function to resolve a hash prefix to the "full" hash.

Was this closed accidentally?

@pv Yeah, I was trying to retrigger the Travis run as a bunch of web tests randomly failed.

Yes, there's something strange with phantomjs on travis, and the conda environment creation also seem to fail quite often due to web connectivity issues...

@pv Looks like it's all passing now. It looks like Travis has some caching infrastructure that might help cut down on the network failures, which I'll try to look into this evening.

LGTM.


Blob Storage reference docs - request SAS 1:1 with .NET

Is it possible with the existing Blob Storage SDK v12 for JS to have an equivalent of this .NET code? I can't see it in the ref docs or the samples in this SDK repo.
.NET SDK code
sasBuilder.ExpiresOn = DateTimeOffset.UtcNow.AddHours(1);
sasBuilder.SetPermissions(DataLakeSasPermissions.Read | DataLakeSasPermissions.Write |DataLakeSasPermissions.List);

This is the code I have with permissions as a string in JS but I would like to use something from the SDK without a string.
JS SDK code
async function createAccountSas() {

    const sasOptions = {

        services: AccountSASServices.parse("btqf").toString(),                     // REMOVE this string to enum or something else
        resourceTypes: AccountSASResourceTypes.parse("sco").toString(), // REMOVE this string to enum or something else
        permissions: AccountSASPermissions.parse("rwdlacupi"),               // REMOVE this string to enum or something else
        protocol: SASProtocol.Https,
        startsOn: new Date(),
        expiresOn: new Date(new Date().valueOf() + (10 * 60 * 1000)),   // 10 minutes
    };

    const sasToken = generateAccountSASQueryParameters(
        sasOptions,
        sharedKeyCredential
    ).toString();

    console.log(`sasToken = '${sasToken}'\n`);

    // prepend sasToken with `?`
    return (sasToken[0] === '?') ? sasToken : `?${sasToken}`;
}

I'm not a storage expert, but it looks like the generateAccountSasUrl method on BlobServiceClient could make this a little simpler?
Also you should be able to do something like AccountSASPermissions.from({read: true, list: true}) to make the permissions a bit more legible.

@xirzec Can you tag an engineer that might be closer to SAS token generation on JS?

I think @EmmaZhu is the best point of contact for this.

Hi @diberry ,
The permission in JS is defined as a class instead of an enum type, parsing from a string to create a permission object is recommended.
Thanks
Emma

@EmmaZhu Are you saying my sample code at the top of this issus is the recommended? If not, can you please provide an example of "a string".

@diberry Yes, we'd recommend to input the permission with code like: permissions: AccountSASPermissions.parse("rwdlacupi")

@diberry , anymore questions, please feel free to active the issue.


Remove "Rancher" from helper text and misc areas Phase 1

David will work on this issue, no need to assign to someone
It's best to avoid the company's name in helper text and miscellaneous areas in the UI where possible.
I should review en-us.yaml translations and see if we can remove such areas and make tweaks in some areas to improve the language used (should be formal and simple).

[ ] Add cluster, authorized endpoint text needs improvement and removal of word "Rancher"

There are mentions of "Rancher" in template.hbs (misc HTML) as well -- not just in en-us translations. As such, I changed the name of this issue to "Phase 1" which just covers basic checks in en-us.yaml translations.
Phase 2 is here: https://github.com/rancher/rancher/issues/21971 and this is more in-depth checking inside of hbs files, etc.

Version: master-head (8/9/19)
I can confirm the term "Rancher" has been removed in the correct areas as per the PR. I didn't identify any issues with this.


M1 mac

Issue #, if available:
https://github.com/aws/aws-mwaa-local-runner/issues/131
https://github.com/aws/aws-mwaa-local-runner/issues/136
*Description of changes:
modifies scripts and compose files to docker on amd64 emulation  mode
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Any timelines on when this will be merged?

@subashcanapathy any thoughts on this, - can we help in any way?

what python version are you installing onto M1? from homebrew?

@jgc93 what is the error you are getting?
I think this uses the default python on amazon linux, which is 3.9? https://docs.aws.amazon.com/linux/al2022/release-notes/all-packages-al2022-20220824.html

Please update to modify the default 2.2.2 branch

great