python3Packages.freebox-api: 0.0.9 -> 0.0.10

Motivation for this change
Update to latest upstream release 0.0.10
Change log: https://github.com/hacf-fr/freebox-api/releases/tag/v0.0.10
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

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

2 packages built:

python38Packages.freebox-api
python39Packages.freebox-api

Result of nixpkgs-review pr 118182 at d1fe52d4 run on aarch64-linux 1

2 packages built successfully:

python38Packages.freebox-api
python39Packages.freebox-api

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

3 packages built:

home-assistant
python38Packages.freebox-api
python39Packages.freebox-api

What's the downside of using poetry until the upstream pull request is merged?

Both approaches are probably fine. Sure, there is a chance that upstream rejects the patch, but I feel that it is slim to none in this case.

Test failure on x86_64 is unrelated (prometheus humidity sensor test).


Error while downloading AMD GPU drivers for NVv4 series VMs -  404 - File or directory not found.

[When I try to donwload the AMD GPU drivers for NVv4 series VMs for Windows 10 Enterprise multi-session - Build 1909 from your given link I am getting the error:  404 - File or directory not found. ]

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

ID: b614e743-5405-47cd-ee21-b442b4acb44d
Version Independent ID: 3aecf729-8f36-6e60-be76-b740df7aa7a6
Content: Azure N-series AMD GPU driver setup for Windows - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/n-series-amd-driver-setup.md
Service: virtual-machines-windows
GitHub Login: @vikancha-MSFT
Microsoft Alias: vikancha

@slp-tmm Thanks for reporting the issue. The download link had a typo with an extra 'e' in the .exe. We have fixed the link in the doc pages and the changes should go live by tomorrow.

@slp-tmm Thanks for the Feedback. The document is updated with correct link, changes will go live soon.


The way to 100% test coverage (part 1)

Q
A

Bug fix?
Yes

New feature?
No

BC breaks?
No

Deprecations?
No

Fixed tickets
N/A

I've started to fix tests to get 100% coverage. It's important image thing as for me.

I added each class refactoring as separate commit os it's convenient for cherry-pick.

First of all, thank you for your contribution to the project. I'm really appreciate that.
In open source there is a simple rule: no is temporary, yes is forever. If i say yes to this PR, we'll need to support those tests for every changes in recipes, and them are rapidly comes in. Those tests may bring 100% code coverage, but in coast of maintenance and slowing changes adoptions. In this project i nwhat ever aims to 100% code coverage. In fact i'm going to separate tests in two layers: one on unit tests for core (all what's in src and responds for task running and configuration) and integration tests for all recipes, tests what will be testing critical for recipes stuff, like success deploy, rollback, etc (i already start working on this, but code not in public for now). So, as maintainer of Deployer, i'm saying no to this PR for now.

@elfet Bad news for me.
Do you have a written list of main goals, principles and development trends of the project? Don't want to waste time for useless things.

@elfet

What're main features that you're planning in v5 and working right now?
What do you recommend to do for contributors?

Main feature it's deprecating other ssh clients and leaving only native ssh, so i want to fix as much as possible in v4 (while there is still way of using it if there is a bug).
For now, there is two labels: good for beginner and advanced+level. If you are planning something big it's good to open issue to discus it.


[Core] Implementing an openPosition dto

Hello, i had a big pause from the development of this library and i don't know if someone has implement this feature already. I would like to implement a getOpenPositions() method on the TradingService.class in order to get the openPositions on exchanges that we can use leverage. The default method output will be an ExchangeNotSupportedException. Can i do that? Thanks

I assume that z position you mean positions on future contracts?
There was some talk about this way back in https://github.com/knowm/XChange/issues/3171 but no one seams to have implemented it in core yet. This will require a lot of thought to do in a generic way.
There is only a hack for Bitmex there future contracts are added as  Currency and CurrencyPair: https://github.com/knowm/XChange/blob/develop/xchange-core/src/main/java/org/knowm/xchange/currency/Currency.java#L279
I think we would first have to ask our selfs how much of this type of trading will have in common with the current functionality of TradeService?
is a position a special type of order or should it be something totally different?
will closing of a position result in trades in the trade history?
If the answer to the above is false then I think we should consider adding a new interface: FuturesTradeService

Position is either in future contacts or using margin in spot trading( for example Kraken).
I am not sure if closing of a position will result in a trade history entry. I believe that this has to do with how the exchange has implement it.
In futures market as Bitmex, everything is a position and everything is been added to trade history.
The thing is that a position has different attributes than an ordinary order(limit,market,stop).
I believe that a FutureTradeService will not be needed because positions are not only in future markets. Also, the only method that will have is getOpenPositions(), because everything else can be done with the existing implementation(placingOrder,getTradeHistory etc).
I am thinking to create an OpenPosition DTO which extends Order and then add getOpenPosition method in TradeService. What do you think?

I am not sure if closing of a position will result in a trade history entry. I believe that this has to do with how the exchange has implement it.

we must try to unify this type of behaviour

Also, the only method that will have is getOpenPositions(), because everything else can be done with the existing implementation(placingOrder,getTradeHistory etc).

could you please provide an example code showing how one would post some positions and then retrieve them in a generic way (usable for many exchanges) according to your vision?

Here is my implementation so far.
In core dto/trade i have add:
public class OpenPosition extends Order {
public OpenPosition(OrderType type, BigDecimal originalAmount, CurrencyPair currencyPair, String id, Date timestamp, BigDecimal averagePrice, BigDecimal fee) {
    super(type, originalAmount, currencyPair, id, timestamp);
    setAveragePrice(averagePrice);
    setFee(fee);
}

}
and this:
public class OpenPositions implements Serializable {
private final List<OpenPosition> openPositions;

public OpenPositions(List<OpenPosition> openPositions) {
    this.openPositions = openPositions;
}

public List<OpenPosition> getOpenPositions() {
    return openPositions;
}

@Override
public String toString() {
    return "OpenPositions{" +
            "openPositions=" + openPositions +
            '}';
}

}
In TradeService interface i have add:
default OpenPositions getOpenPositions() throws IOException{
throw new NotYetImplementedForExchangeException();
}
In KrakenTradeService i have add:
@Override
public OpenPositions getOpenPositions() throws IOException {
return KrakenAdapters.adaptOpenPositions(super.getKrakenOpenPositions());
}
In KrakenAdapter i have add:
public static OpenPositions adaptOpenPositions(Map<String, KrakenOpenPosition> krakenOpenPositionMap){
List openPositionsList = new ArrayList<>();
krakenOpenPositionMap.values().forEach(krakenOpenPosition -> {
  openPositionsList.add(
          new OpenPosition(
                  KrakenAdapters.adaptOrderType(krakenOpenPosition.getType()),
                  krakenOpenPosition.getVolume().subtract(krakenOpenPosition.getVolumeClosed()),
                  KrakenAdapters.adaptCurrencyPair(krakenOpenPosition.getAssetPair()),
                  krakenOpenPosition.getOrderTxId(),
                  new Date(krakenOpenPosition.getTradeUnixTimestamp()*1000),
                  krakenOpenPosition.getCost().divide(krakenOpenPosition.getVolume().subtract(krakenOpenPosition.getVolumeClosed()), RoundingMode.HALF_EVEN),
                  krakenOpenPosition.getFee()
                  ));
});

return new OpenPositions(openPositionsList);

}

Of course the OpenPositionDto implementation can be changed

you showed me the features implementation but thats not what I asked for

could you please provide an example code showing how one would post some positions and then retrieve them in a generic way (usable for many exchanges) according to your vision?

I still don't understand how those positions got created.

The positions can only be retrieved from the exchange when you can the exchange endpoint. You do not send positions to the exchange, you only get the ones that are open, but you need to call a different endpoint than the getOpenOrders.

I am not sure if closing of a position will result in a trade history entry. I believe that this has to do with how the exchange has implement it.

Positions can close in one of two ways
a) Trading out of the position (long 1 then sell 1 give a 0 position)
b) The Future expires.  The position is settled in cash, we should see wallet payments their.
NB: Perpetual swaps will probably not expire, until the Exchange does.
I also see some hints in the insurance funds that deals with bankcrupt counterparties.


Raising no route matched log level to Warning

At the default log level(warning), if the default outbound is matched, there is no way to know whether a routing rule is matched or if the default route is taken.
Setting it to waring also reminds the user that a routing rule should be set for the special destination.
Knowing matched routing result clearly makes it easier to optimize the v2ray configuration.
If the log level in the configuration is simply set to info, there will be a lot of extra confusing info logs.

Codecov Report

Merging #1424 (013bb27) into master (7413246) will decrease coverage by 0.16%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1424      +/-   ##
==========================================
- Coverage   39.63%   39.46%   -0.17%
==========================================
  Files         598      590       -8
  Lines       35041    34945      -96
==========================================
- Hits        13887    13791      -96
+ Misses      19637    19630       -7
- Partials     1517     1524       +7

Impacted Files
Coverage Δ

app/dispatcher/default.go
29.41% <100.00%> (ø)

app/router/command/errors.generated.go
0.00% <0.00%> (-100.00%)
:arrow_down:

testing/servers/tcp/tcp.go
81.81% <0.00%> (-5.46%)
:arrow_down:

testing/scenarios/common.go
73.07% <0.00%> (-4.62%)
:arrow_down:

transport/internet/udp/hub.go
73.61% <0.00%> (-4.17%)
:arrow_down:

transport/internet/system_listener.go
50.00% <0.00%> (-4.00%)
:arrow_down:

transport/internet/kcp/dialer.go
80.39% <0.00%> (-3.93%)
:arrow_down:

app/router/command/command.go
36.92% <0.00%> (-3.08%)
:arrow_down:

transport/internet/kcp/connection.go
69.61% <0.00%> (-2.77%)
:arrow_down:

transport/internet/quic/hub.go
72.00% <0.00%> (-2.67%)
:arrow_down:

... and 13 more

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 7413246...013bb27. Read the comment docs.


Bluetooth: drivers: Sync bus types with BlueZ

The authoritative source of these values is BlueZ:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/lib/hci.h#n38
Update our values with the above. The IPM definiton doesn't exist in BlueZ, but should be added there to make sure we don't get out of sync again.

@Vudentz any chance you could help add the IPM definition to BlueZ? That way, if BlueZ extends this list, at least we don't use overlapping values. Likewise, if we ever need to extend it, we'll make sure to get the same addition to BlueZ as well.

Should we add a code comment with a link to the authoritative source?

Should we add a code comment with a link to the authoritative source?

I'm just not sure how to make that reference so that it stays up to date, besides simply saying "These values come from Linux/BlueZ". What makes the situation more confusing is that BlueZ has multiple places defining them. There's e.g. the following which seems to be out of date with the latest VirtIO addition (@Vudenz you might want to fix this):
https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/src/shared/btsnoop.h#n51
The Linux kernel also has its own definitions, which could be seen as equally authoritative as the user space tree:
https://git.kernel.org/pub/scm/bluetooth/bluetooth-next.git/tree/include/net/bluetooth/hci.h#n60

@alwa-nordic @Thalley sorry, for the sake of completeness I realized "smd" and "virtio" need to be in the allowed DT property values as well, in case some future HCI driver/binding wants to use those. So you'll need to renew your approvals.

Should we add a code comment with a link to the authoritative source?

I'm just not sure how to make that reference so that it stays up to date, besides simply saying "These values come from Linux/BlueZ". What makes the situation more confusing is that BlueZ has multiple places defining them. There's e.g. the following which seems to be out of date with the latest VirtIO addition (@Vudenz you might want to fix this): https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/src/shared/btsnoop.h#n51
The Linux kernel also has its own definitions, which could be seen as equally authoritative as the user space tree: https://git.kernel.org/pub/scm/bluetooth/bluetooth-next.git/tree/include/net/bluetooth/hci.h#n60

I will update those value and add a reference to this issue so we crosscheck, Im also planning to add PCI(12) bus after IPC.


Fixes restoring group associated with site. Closes #3101

Fixes restoring group associated with site. Closes #3101

@waldekmastykarz: not sure why the merge was triggered like this. Verified the history and we are still in a straight line. I do not see additional actions here.

This happens when the branch from which the PR was issued is in-sync with upstream and there were no additional changes. Because the merged commit matches exactly what's in the PR, GitHub considers it merged. Nothing to worry about.


Add some keywords

typeof, pointerof, sizeof, instance_sizeof, with, previous_def are keywords in Crystal.

Thanks!
I didn't know with keyword.


Unable to resole typescript alias path

I have this eslint config:
module.exports = {
  parser: '@typescript-eslint/parser',
  extends: [
    'eslint:recommended',
    'airbnb',
    'plugin:@typescript-eslint/recommended',
    'plugin:@typescript-eslint/recommended-requiring-type-checking',
    'prettier',
  ],
  plugins: ['@typescript-eslint'],
  parserOptions: {
    project: ['./tsconfig.json'],
    tsconfigRootDir: __dirname,
  },
  env: {
    node: true,
  },
  settings: {
    'import/resolver': {
      "eslint-import-resolver-custom-alias": {
        alias: {
            "@features": "./src/features",
        },
        "extensions": [".ts"],
    },
      node: {
        moduleDirectory: ['node_modules', 'src'],
        extensions: ['.js', '.jsx', '.ts', '.tsx', '.d.ts'],
      },
    },
  },
  rules: {
    'import/extensions': [
      'error',
      'ignorePackages',
      {
        js: 'never',
        jsx: 'never',
        ts: 'never',
        tsx: 'never',
      },
    ],
    'import/order': [
      'error',
      {
        groups: ['builtin', 'external', 'internal', 'parent', 'sibling', 'index'],
        'newlines-between': 'always',
      },
    ],
    'no-void': 0,
  },
};

whenever I use an alias path I get an error like Unable to resolve the path to module<EMAIL_ADDRESS>I added the paths to tsconfig.json and I installed eslint-import-resolver-custom-alias or eslint-import-resolver-typescript but it does not fix the issue.
eslint-plugin-import: v2.26.0.

I tried eslint-import-resolver-custom-alias plugin and added the following to eslintrc and the error is gone
    "import/resolver": {
      "eslint-import-resolver-custom-alias": {
        "alias": {
          "@": "./src"
        },
        "extensions": [".ts", ".tsx"],
      }
    }

eslint-import-resolver-custom-alias

Unfortunately, this plugin does not fix the issue with my monorepo setup.

same issue and the plugin does not fix mine too

You'd better provide a runnable reproduction.

I don't know if this is the same issue, but eslint-plugin-import was complaining on my next.js project when I tried to import modules with the alias:

This is a monorepo with pnpm, but I guess it should be the same with any other tool, I have a package with the next app
So I added this setting to my eslintrc.js:

And that fixes the issue, since it is now correctly parsing my tsconfig.json for that monorepo package and it seems smart enough to recognise my defined path there:

Hope it works for you 👍

@ottodevs
I've been struggling with the same issue for over an hour with my Remix v2 app...
Your solution worked for me! Thank you! 🙏
For those who are in the same situation, I'm sharing my settings:
My dependencies version:
  "dependencies": {
    "@remix-run/node": "^2.9.2",
    "@remix-run/react": "^2.9.2",
    "@remix-run/server-runtime": "^2.9.2",
    "@vercel/remix": "2.9.2-patch.2",
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
  },
  "devDependencies": {
    "@remix-run/dev": "^2.9.2",
    "@remix-run/eslint-config": "^2.9.2",
    "@types/react": "^18.2.20",
    "@types/react-dom": "^18.2.7",
    "eslint": "^8.57.0",
    "eslint-import-resolver-typescript": "^3.6.1",
    "eslint-plugin-import": "^2.29.1",
    "typescript": "5.1.6",
    "vite": "^5.1.0",
    "vite-tsconfig-paths": "^4.2.1"
  },

.eslintrc.cjs
  settings: {
    "import/resolver": {
      typescript: {
        alwaysTryTypes: true, // always try to resolve types under `<root>@types` directory even it doesn't contain any source code, like `@types/unist`
        project: __dirname,
      },
      node: true,
    },
  },

tsconfig.json
    "baseUrl": ".",
    "paths": {
      "~/*": ["./app/*"],
      "@routes/*": ["./app/routes/*"]
    },

vite.config.ts
import { vitePlugin as remix } from "@remix-run/dev";
import { installGlobals } from "@remix-run/node";
import { defineConfig } from "vite";
import { vercelPreset } from "@vercel/remix/vite";
import tsconfigPaths from "vite-tsconfig-paths";

installGlobals();

export default defineConfig({
  plugins: [remix({ presets: [vercelPreset()] }), tsconfigPaths()],
});

Unfortunately not working in eslint v9 for me.


Update es-ES.coffee

Hi,
Several sentences translated to it's spanish version.
Regards!!!

Thanks for adding those translations, @GrecK0!


Duration of out.mp4 is messed up

Hi
The out.mp4 time duration results to be longer than original video becouse of this line in
imageio.mimwrite(os.path.join(folder_path, 'out.mp4'), frames, fps=18, output_params=['-vf', 'fps=25'])
18 must be changed to 25 to fix this issue

Hi,
Thank you for raising this issue, not sure how I missed it :sweat_smile:
I'll fix it soon


Add parser changes for regular expressions

Purpose

$title

Fixes #36834
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@lasinicl shall we check on the build failure

There are several changes that need to be added to this PR prior to reviewing. Hence closing temporarily. Will reopen once the changes are updated.


A wrong argument in trainSpeakerNet.py

Hi, I think the argument '--encoder' in trainSpeakerNet.py should be '--encoder_type'.

Thanks for letting us know! We will correct this in the next update.


 System Darwin 14.0.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/ricardoshigeoka/Jobs/Brastemp/Menu/node_modules/css-sprite/node_modules/gaze
gyp ERR! node -v v0.12.0
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok

npm ERR! Darwin 14.0.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "css-sprite"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the gaze package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls gaze
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:

I'm running on Mac OSX Yosemite.

+1

+1

+1

@CREEATION - Also have this issue with node 0.10.2
[INFO] ><EMAIL_ADDRESS>install C:\Workspace\code\main\node_modules\css-sprite\node_modules\lwip
[INFO] > node-gyp rebuild
[INFO]
[INFO]
[INFO] C:\Workspace\code\main\node_modules\css-sprite\node_modules\lwip>node "C:\Workspace\code\main\node\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild
[INFO] npm ERR! Windows_NT 6.1.7601
[INFO] npm ERR! argv "C:\Workspace\code\main\node
node" "C:\Workspace\code\main\node\npm\bin
npm-cli.js" "install" "--color=false"
[INFO] npm ERR! node v0.10.34
[INFO] npm ERR! npm v2.1.6
[INFO] npm ERR! code ELIFECYCLE
[INFO]
[INFO] npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
[INFO] npm ERR! Exit status 1
[INFO] npm ERR!
[INFO] npm ERR! Failed at the<EMAIL_ADDRESS>install script.
[INFO] npm ERR! This is most likely a problem with the gaze package,
[INFO] npm ERR! not with npm itself.
[INFO] npm ERR! Tell the author that this fails on your system:
[INFO] npm ERR! node-gyp rebuild

@aslansky
Is it possible to downgrade to<EMAIL_ADDRESS>until @shama fixes this.
https://github.com/shama/gaze/issues/110#issuecomment-61302737

@alexkaraman85
You can try using it with node v0.10.31, it worked for me, too.

Downgraded to v.0.10.31 and didn't  work

@ricardomasao - tried today as well and 0.10.31 did not change anything for me.  Still getting the same issue.

+1

+1

you may try an older release v0.10.29 works for me

+1

Tryed v0.10.29 and worked!
Thanks @cmnstmntmn

Downgrade is not resolves a problem. Current version of node.js is 0.12.0 and css-sprite should works on it.

I closed the issue as this solves the errors reported initially. I think the right thing would be to open a new issue reporting the error in node v0.12.0. Would be clearer for everyone. @denisborovikov

@ricardomasao The reason why you've got this error was node.js v. 0.12.0 and probably Mac OSX Yosemite (as in my case) , so issue you've opened is what we need. You may just rename it to make more clear description.

I'm with @denisborovikov, downgrading to an older version of Node.js is not a fix to this issue, but a work around.

should be resolved with 0.9.6

It's working, thanks :)

On 0.9.0 I was able to resolve this issue by rolling back Node to 0.10.29, per the comments above.

Mac + NodeJS v5.3.0
+1


Patch variation_citation table 99

Description
Patch variation_citation table
Use case
Describe the problem. Please provide an example representing the motivation behind the need for having these changes in place.
Benefits
If applicable, describe the advantages the changes will have.
Possible Drawbacks
None
Testing
Have you added/modified unit tests to test the changes?
If so, do the tests pass/fail?
Have you run the entire test suite and no regression was detected?
Yes, no regression detected.
Changelog
Are you changing the functionality of an endpoint? If so, please give a one line summary for the public facing changelog.
eg. [/xenobiology/orthologs] Added the ability to look up orthologs and paralogs from klingons and andorians

Coverage remained the same at 44.324% when pulling ded52427edff17bff09c1672dfeed18ef94ef99d on dglemos:patch/variation_attrib into 3926a20d4a15d86269eb2c07bd5ccf694b4c62c6 on Ensembl:release/99.


[http handler] add GET fallback if HEAD is not allowed or forbidden to get key size

Adding a fallback to get resource size if HEAD is not allowed.
Similar behavior to GDAL vsicurl.
Mainly used with URLs that are presigned for only one HTTP verb (AWS, GS).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

24 of 36 (66.67%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.8%) to 89.481%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

http.go
24
36
66.67%

Files with Coverage Reduction
New Missed Lines
%

http.go
1
64.29%

Totals

Change from base Build<PHONE_NUMBER>:
0.8%

Covered Lines:
689

Relevant Lines:
770

💛  - Coveralls

Couldn't the HEAD request be skipped completely and instead always do a GET request for the first block that populates the cache and sets the size in a single request ?

Do you mean parsing the Content-Range header instead of relying on the Content-Length one?
HTTP/1.1 206 Partial Content
Content-Range: bytes 0-1023/146515
Content-Length: 1024

Do you agree it requires modifying func (a *Adapter) Size(key string) (int64, error) ?
I can take a look ; it seems reasonable given we need the first block in most contexts (except in zips).


ESET Business KEY

Is it normal that ESET Business KEY cannot be used in the ESET Business Account I created?

I haven't checked this.  So no idea.  Can you describe in more detail?

This problem occurs when I add a business key to eset business


RUMM-1953 Lazy webview hosts

What does this PR do?
Allow setting the hosts for webview tracking upon creating of the DatadogEventBridge

Codecov Report

Merging #837 (7ac63f0) into release/1.12.0 (99932a2) will decrease coverage by 0.13%.
The diff coverage is 100.00%.

@@                Coverage Diff                 @@
##           release/1.12.0     #837      +/-   ##
==================================================
- Coverage           80.43%   80.30%   -0.13%
==================================================
  Files                 254      254
  Lines                8520     8530      +10
  Branches             1457     1457
==================================================
- Hits                 6853     6850       -3
- Misses               1322     1332      +10
- Partials              345      348       +3

Impacted Files
Coverage Δ

...atadog/android/core/configuration/Configuration.kt
95.74% <ø> (ø)

...id/webview/internal/rum/WebViewRumEventConsumer.kt
76.74% <ø> (-9.30%)
:arrow_down:

.../com/datadog/android/webview/DatadogEventBridge.kt
100.00% <100.00%> (ø)

...roid/webview/internal/MixedWebViewEventConsumer.kt
100.00% <100.00%> (ø)

...id/webview/internal/log/WebViewLogEventConsumer.kt
88.89% <100.00%> (ø)

...android/rum/internal/ndk/DatadogNdkCrashHandler.kt
83.73% <0.00%> (-4.82%)
:arrow_down:

...ain/java/com/datadog/opentracing/PendingTrace.java
58.97% <0.00%> (-0.85%)
:arrow_down:


is-slot-mode

I'm looking to only use one of columns with a v-slot to use a component,
But it seems that when you turn is-slot-mode to true that you have to make every column a v-slot
Is there a way I could add a v-slot without having to do them all?
I know display: exists but that doesn't fit my use case as I need to use vue components.
An optional slot mode would be ideal i.e default to not using a slot unless specified <3

Hi @Zersty

An optional slot mode would be ideal i.e default to not using a slot unless specified <3
Yes, this is a good idea. Thank you.
I am already changed v-slot to optional on version 1.0.9. Hope helpful you.

example: https://github.com/linmasahiro/vue3-table-lite/blob/master/src/examples/VSlotMode.vue

Thanks very much you rock!!!


⚠ Bofrost.at has degraded performance

In 57ae250, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1436 ms

Resolved: Bofrost.at performance has improved in 03339c6.


pull request for e2e test at 12/28/2016 00:45:07

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


Global issues

I'm curious how this interacts with global variables inside a function inside a cell, for example:
a = 1

def f():
    global a
    a = 5

f()
print(a)

This prints out 5 with the current ipykernel, which is what I would expect.

With akernel this prints out 1, unless:

the cell is divided in two:

# cell 1
a = 1

# cell 2
def f():
    global a
    a = 5

f()
print(a)

or we use nonlocal instead of global:

a = 1

def f():
    nonlocal a
    a = 5

f()
print(a)

I'm thinking we could parse the code and look for assignments at the top-level, and declare every assigned variable as global.
Thanks for raising this issue @jasongrout !


Does not work with the latest version of XO

Failed to load XO library. Make sure XO is installed in your workspace folder using 'npm install xo' and then press Retry.

This appears to be caused by XO v0.40 migrating the project to ESM, and with it breaking compatibility with this extension.

As far as I can tell, https://github.com/xojs/xo/pull/534 introduced some change to XO's config resolver, which in turn broke the logic that loads the XO library.

@lolPants is right, the version just before 0.39.1 is working well with this extension

Hi @Richienb, this issue is very much related to https://github.com/xojs/xo/issues/543.
<EMAIL_ADDRESS>is looking for eslint-config-xo within the vscode extension’s context, and not within the extension’s workspace root.
xo is loading using resolveModule(workspaceRoot, 'xo'), see https://github.com/SamVerschueren/vscode-linter-xo/blob/master/server/src/server.ts#L131.
Then it throws when trying to load eslint-config-xo – installing eslint-xo-config within the extension server’s root fixes the issue.

ESLint is only able to resolve plugins from the same node_modules folder that it is installed in or the node_modules of the project directory its cwd is set to. I think 0.40.0 just made it do the other thing but I can't be certain.
Could the cwd option in xo be of use for now?

It could but makes this plugin useless. Also makes linting so much harder.

Yeah, that is definitly the issue, eslint-config-xo is being searched within the CWD.
The issue is not when linting files, but when loading the package.
The cwd option is actually already set when linting (https://github.com/SamVerschueren/vscode-linter-xo/blob/master/server/src/server.ts#L198)

For those seeking a workaround until this is otherwise resolved, use xo v0.39.1, the most recent working version:
npm install<EMAIL_ADDRESS>--save-dev

or the shorter version:
npm i<EMAIL_ADDRESS>-D

If you want to see xo's description of what's in the last few releases: https://github.com/xojs/xo/releases/

added this issue here for visibility: https://github.com/xojs/xo/issues/563
@SamVerschueren can we get any confirmation on if this extension is dead or alive? It doesn't look like its had any real activity in 2 years. Should we look for a new solution for vscode integration?

Is there anyone here that would like to fix this for money? I am willing to pay.

Willing to monetarily support an update to this, as well.

@yakov116 has funded $20.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

An anonymous user has funded $20.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

An anonymous user has funded $20.00 to this issue.
* Submit pull request via [IssueHunt](https://issuehunt.io/repos/44163560/issues/91) to receive this reward.

* Want to contribute? Chip in to this issue via [IssueHunt](https://issuehunt.io/repos/44163560/issues/91).

* Checkout the [IssueHunt Issue Explorer](https://issuehunt.io/issues) to see more funded issues.

* Need help from developers? [Add your repository](https://issuehunt.io/r/new) on IssueHunt to raise funds.

@yakov116
Er, that wasn't supposed to be anonymous. But in any event, I've matched funding.

@tusbar has funded $20.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

I forked and published this package as a new extension - since it seems this is no longer being maintained or accepting PRs. Please try this via the link below, and feel free to file issues in my fork. My extension should work now for all versions of XO. @tusbar @yakov116 @savearray2  -- if you have any problems definitely let me know and I will try to fix right away.
https://marketplace.visualstudio.com/items?itemName=spence-s.linter-xo

@Spence-S
Thank you for the update! It is much appreciated. I'm in the middle of switching laptops. I'll check it out in the next day or so :)

I forked and published this package as a new extension - since it seems this is no longer being maintained or accepting PRs. Please try this via the link below, and feel free to file issues in my fork. My extension should work now for all versions of XO. @tusbar @yakov116 @savearray2  -- if you have any problems definitely let me know and I will try to fix right away.
https://marketplace.visualstudio.com/items?itemName=spence-s.linter-xo

@Spence-S your extension works perfect ly! @SamVerschueren can you merge the PR?
If it does not get merged in the next week I will credit you the bounty.

closed by https://github.com/SamVerschueren/vscode-linter-xo/pull/94

Can you try to link the pull request? If this does not work I will email them

@SamVerschueren I think you may have to reward it since your the repository owner. @Spence-S I will send them an email now. If they don't get back to me in a prompt matter, I will send it to u via PayPal etc.

@yakov116 feel free to email me<EMAIL_ADDRESS>if you need anything else from my end. Will try to stop spamming these threads here 😄 - but thanks for your support on this.

Not entirely sure how this works. I'll check tomorrow on my computer. I tried linking the PR, not sure if that did it...

I think you have to go onto issue hunt and award it there

@samverschueren has rewarded $54.00 to @spence-s. See it on IssueHunt

:moneybag: Total deposit: $60.00
:tada: Repository reward(0%): $0.00
:wrench: Service fee(10%): $6.00

Yes. I found it :). Great work everyone!


Error.captureStackTrace is not a function

The "Network error. Check your connection and reload the page?" dialog pops up, with detail message "Error.captureStackTrace is not a function."

It looks like this happens a lot in other people's projects, and there's a pattern of it working on Chrome and failing in other browsers.

This Error API appears to be in V8 so is only available in Node and Chrome. Other browsers don't have the function. Some library we're using makes a call to that API without checking whether the function exists. https://www.npmjs.com/package/error-polyfill should solve the problem.

Closing this as our error capture and reporting has changed drastically since this has been reported. If there is a reproducible way to get this error please let me know how and we will re-open this issue!


Unable to update boolean attribute through Console

Describe the issue:
Unable to update boolean attribute through Console
How to reproduce:

Create a custom attribute
Add additional property ("dataType" : "boolean")
Make it avail in user profile
Try updating the attribute. It will not be updated

Expected behavior:
Should be able to update.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

As per the discussion had with @VivekVinushanth , this feature is only available through API and therefore the chance of end users encountering this bug through UI is slim. Therefore reducing the severity.

And IMO data type should be a first class property. This has been a concern when user tries to signup with a boolean value (though we changed the attribute type to boolean through API) , the signup still prompts with a text box.

When registering an attribute type should be considered and signup/ profile pages should reflect this
For all the text value, we still provide a text box but there can be a necessity to get input from a dropdown which we dont support.

This has been a concern for few prospects and customers to be frank

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Callback comes back in the background - never called in the foreground

Hi,
I noticed that if I launch my app (from the background), and then put it very quickly in the background again, the branch callback (initSessionWithLaunchOptions) is being called in the background.
That's OK, but the problem is that when the app comes back the next time to the foreground - the callback is never called.
Sounds like a bug to me
(The current workaround is that I manage logic for the callback when it's called in the background)

@arrows To confirm, waiting a little bit longer before you put it in the background the first time will correctly call init upon return?

Correct.
This only occurs if I go to the background very quick after launch.
On 21 Mar 2016, 18:04 +0200, Alex<EMAIL_ADDRESS>wrote:

@arrows(https://github.com/arrows)To confirm, waiting a little bit longer before you put it in the background the first time will correctly call init upon return?
—
You are receiving this because you were mentioned.
Reply to this email directly orview it on GitHub(https://github.com/BranchMetrics/iOS-Deferred-Deep-Linking-SDK/issues/316#issuecomment-199357358)

Hi All,
Any update for this issues.
+1

@arrows @Alkalouti unfortunately this an extreme edge case that would require a substantial redesign of the SDK that we can't support. Sorry about that. I am closing here but feel free to reopen if you have any updates. Cheers!


clashleaders.clash.api.TooManyRequests in GET /search.json

Error in ClashLeaders
clashleaders.clash.api.TooManyRequests in GET /search.json
Too many requests when fetching clan [#82V028YU].
View on Bugsnag
Stacktrace
clashleaders/clash/api.py:58 - find_clan_by_tag
clashleaders/views/clan.py:27 - search

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
clashleaders.clash.api.TooManyRequests in GET /search.json

An error linked to this issue has been reopened in Bugsnag
clashleaders.clash.api.TooManyRequests in GET /search.json

An error linked to this issue has been reopened in Bugsnag
clashleaders.clash.api.TooManyRequests in GET /clan/92GPQQU0/short.json

An error linked to this issue has been marked as fixed in Bugsnag
clashleaders.clash.api.TooManyRequests in GET /search.json

An error linked to this issue has been reopened in Bugsnag
clashleaders.clash.api.TooManyRequests in GET /search.json


ENH: Support for rendered target as an output

Proposed new feature or change:
First, thank you so much for this! It's been working great.
One enhancement that would be really helpful is to have a step output for the rendered target. In my current workflow I'm adding a step that does a cat target.file for every rendered template for debugging purposes. With an output it would be trivial to expand that output and do away with the need for the extra steps (and very long log messages) which we only need while debugging.
Another use-case would be using the content as a variable in other parts of the workflow, like writing comments, pull request descriptions and the like.

Thank you for your kind feedback.
I will take a look at this next week so please bear with me. Prima facia, looks straight forward.


feature: support smol_str

Goal
Add support for the widely used string crate smol_str (15m downloads from crates.io).
The main and only type in the crate is SmolStr which is essentially a string with some optimisations.
Checklist

[x] I have followed the steps listed in the Contributing guide.
[x] If necessary, I have added documentation related to the changes made.
[x] I have added or updated the tests related to the changes made.

Hi @corvusrabus, thanks for the PR! Can you add a quick test for it please? That'll help avoid regressions in the future

Thanks @gustavo-shigueo. Sure I can do that but I don't see tests for any of the other similar fundamental datatypes like uuid-impl, bigdecimal-impl,  ... either. Is it necessary?

I wouldn't say it's necessary, but I do think it's a good idea. Also, thanks for pointing out those missing tests! I'll try to find some time to add them in the weekend

@gustavo-shigueo. I'll add them if you haven't done it yet

Added tests @gustavo-shigueo

Awesome! Thank you so much @corvusrabus

@gustavo-shigueo there seems to be some CI failures on master

Oops, I missed on smolstr-impl


Add support for @Pattern bean validation annotation

🆕🐥:dog: First Timers Only
This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
:space_invader: Description of the issue
Currently the dolphin-platform-bean-validation module do not provide support for all default bean validation annotations. One that is missing is the @Pattern annotation. For solving this issue the support for the @Pattern annotation must be added like it is done for several other bean validation annotations in the dolphin-platform-bean-validation module and at least one unit test must check that the annotation is supported.
📋 Step by Step

🙋 Claim this issue: Comment below.
🔄 replace the up for grabs label with in progress.
:fork_and_knife: fork the repository in github by simply clicking the 'fork' button.
:arrow_heading_down: check out the forked repository
:twisted_rightwards_arrows: create a feature branch for the issue. We do not have any naming definition for branches.
💾 Commit your changes.
🔀 Start a Pull Request.
🏁 Done 👍 Ask in comments for a review :)
🔬 If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
:boom: you did it! We will merge the fix in the master of the Dolphin Platform project.
:bouquet: Thanks, thanks, thanks for being part as an open source contributor for Dolphin Platform

🤔❓ Questions
You can join our community chat at Slack

Hey @hendrikebbers, I would like to work on this issue.

@bezmax 👍

@hendrikebbers All done. Please review :)
I've also done some refactoring by separating tests for different validators. I was also thinking about separating those into separate files, but did not want to go too far away from the scope of this issue. Maybe a separate ticket is needed for that.


Bugfix and new option in double date dialog

Fixed dialog initialization and added option secondDateAfterFirst to double dialog

thanks 😀


Add Reason(err error) to logger

Very often the only reason why string formatting is needed, is to embed
an error. New Instead of
logging.DefaultLogger().Error().Msgf("Something failed with %s." err)
do
logging.DefaultLogger().Error().Reason(err).Msgf("Something failed.")

This change is

@stu-gott yeah agree on the possible confusion, but using Err() looked strange too, and Error() was already used, so Reason() in contrast to Msg() sounded somehow plausible to me.
Msg: Doing X failed .
Reason: This is why X failed.


Improved ofolder creation

Just a small change when the out_folder is created, to allow also the recursive creation of subfolders.

Hi @JonasKemmer --- thanks for this PR! I've added manually, as your PR had some spacing changes that I was not sure if they were tabs or spaces. The commit that adds your PR is here: https://github.com/nespinoza/juliet/commit/936c0dcb177e4d230c3b2d3d2b25763afa97207e. I'm however, closing this PR request without merging because I've already commited it myself out of fear (hehe).
Once again, thanks a bunch!


Using sync storage for Recently Watched List

Select your issue type: (check at least one)

[ ] Bug
[ ] Question
[x] Suggestion
[ ] Other (please describe):

Describe your issue:

please extend the amount of anime in the recently watched list, make it so the person can add a cap themselves, so that if they watching 15 anime at the time but just in case they don't want everything to be crowded they add a cap of 25.

make it so that the recently watched can be synced to the account.

can u make it so people can hide the things on the companion, like the icon that links you to my anime list, link to the 9anime website.

could you also make it that in the recently watched, if a new episode comes out next to the anime it says the words [NEW] next to it,

this is more to see how it would look like but could you post a screenshot of how the extension would like like in the colours of the 9anime website and ask people to vote weather or not it should be changed.

@kr3d hey thanks for the suggestions 😄 . Just one small thing. Can you please put your suggestions to a single comment? You can edit comments by pressing the :pen: icon on top right. So something like
1. ...
2. ...
3. ...

would be perfect. Or if you want I can edit it for you. Lemme know.

@lap00zza This is what we have initially planned, a dedicated page for recently watched list
Should we implement it?

@densityx yeah eventually.  For now what do you think will be better? I was thinking of simply increasing the cap to 20-25.


Investigate creating Windows binaries again using PyInstaller

Seems to be working gracefully on my machine, just need to figure out:

how can it be automated via Travis for each release/tag?
how to include all relevant licensing documentation?
should I include a copy of ffmpeg/mkvmerge with the distribution, or force users to download it themselves?

If so, same should be done for #DVR-Scan.  The team at Advanced Installer has graciously provided a license for both projects.  All assets related to the installer will be placed in this repository when available.

Managed to get it working again - trick is having to analyze __main__.py instead of scenedetect.py.  The v0.5.5 release has been updated with both a Windows installer and portable binaries.


Release 0.8.0-rc

Release 0.8.0-rc

[x] Review closed issues have appropriate tags.
[x] Review closed issues have been applied to the current milestone.
[x] Review closed PRs have appropriate tags.
[x] Review closed PRs have been applied to the current milestone.
[x] Ensure the next version milestone is created.
[x] Any issues in the current milestone that are not closed, move to next milestone.
[x] Run make gen-changelog to generate the CHANGELOG.md (if release candidate make gen-changelog RELEASE_VERSION=0.8.0-rc)
[x] Ensure the helm tag value is correct (should be the 0.8.0 if a full release, 0.8.0-rc if release candidate)
[x] Ensure the helm Chart version values are correct (should be the 0.8.0 if a full release, 0.8.0-rc if release candidate)
[x] Run make gen-install
[x] Ensure all example images exist on gcr.io/agones-images-
[x] Create a draft release with the release template

[x] Make a tag with the release version.

[x] Site updated

[x] If full release, review and remove all instances of the feature shortcode
[x] If full release, update to the new release branch 0.8.0+0.1.
[x] If full release, update site with the new release version (release-version in config.toml) to 0.8.0+0.1
[x] If full release, update documentation with updated example images tags
[x] Copy the draft release content into a new /site/content/en/blog/releases content (this will be what you send via email).

[x] Create PR with these changes, and merge them with approval
[x] Confirm local git remote upstream points at git@github.com:GoogleCloudPlatform/agones.git
[x] Run git remote update && git checkout master && git reset --hard upstream/master to ensure your code is in line with upstream  (unless this is a hotfix, then do the same, but for the the release branch)
[x] Run make do-release. (if release candidate: make do-release RELEASE_VERSION=0.8.0-rc) to create and push the docker images and helm chart.
[x] Do a helm repo add agones https://agones.dev/chart/stable and verify that the new version is available via the command helm search agones/
[x] Do a helm install and a smoke test to confirm everything is working.
[x] Attach all assets found in the release folder to the release.
[x] Submit the Release.
[x] Send an email to the mailing list with the release details (copy-paste the release blog post)
[x] If full release, then increment the base_version in build/Makefile
[x] Ensure the helm tag value is set to the next version (should be the 0.8.0+0.1 if a full release, 0.8.0+0.1-rc if release candidate)
[x] Ensure the helm Chart version values is set to the next version (should be the 0.8.0+0.1 if a full release, 0.8.0 if release candidate)
[x] Run make gen-install
[x] Create PR with these changes, and merge them with approval
[x] Close this issue.
[x] If full release, close the current milestone. Congratulations! - the release is now complete! :tada: :clap: :smile: :+1:

Done!


Use ES5 .bind() and ES6 arrow functions

With ES5 native Function.bind() you can bind this context without using lodash
With ES6 arrow functions, the context this pass through the call chain, so there is no need to specify a reference to this.
Note:
Regarding lines https://github.com/wistityhq/strapi/blob/master/lib/Strapi.js#L41-L49 I don't think you even have to bind those functions, since they are already part of the Strapi.prototype when Strapi is called with new, all those functions will use this as the instance of Strapi by default.
Note 2:
Is this funciton used somewhere? https://github.com/wistityhq/strapi/blob/master/lib/start.js#L38

Hey @dciccale, thanks a lot for your lovely pull request! I'll try your changes today as soon as I have some free time.
Regarding your notes:

You're right I'm not sure we need to do that either... we need to try.
Again you're right, it appears we never use it.

Do you want to improve it?

You've been really fast on answering!
Tests passes however it should be thoroughly tested to be sure.
Tests were run under node v4.2.2 (latest)

Note 3: here: https://github.com/wistityhq/strapi/blob/master/lib/server.js#L25
There is no need for a function that returns a new instance of Strapi. You can do that directly (as is being done in other parts of the code)
Note 4: in that same file, isLocalStrapiValid and isStrapiAppSync methods are being binded again to the instance of Strapi however those methods are already included in Strapi prototype here https://github.com/wistityhq/strapi/blob/master/lib/Strapi.js#L112-L113 so it has the correct context.

Oh my bad I misunderstood your question about the second note: we never use it except as this very moment. So yes, we definitely use it every time the Strapi server starts.
Regarding your fourth note, we can try without binding it yes.
Thank you very much for your help @dciccale.

So I can revert and put back the strapiReady function? (I made a search in all the repository and is not being used anywhere) Also is not being exported so as long as iit is not exported won't be available anywhere either.

You can put it back yes please but maybe we can write it another way right?

@dciccale: do you still want to improve some things?

Not more for now. Maybe sometime but in other PRs.

Awesome, thanks a lot for your great contribution @dciccale.


Web archive link for ie.microsoft.com

There might be more pages from ie.microsoft.com that need to be switched.

Oh wow, didn't know this exists, noice!

There might be more pages from ie.microsoft.com that need to be switched.

I found three (two, counting your current change): https://github.com/Fyrd/caniuse/search?q=ie.microsoft.com

Went ahead and did all three manually, thanks!


Persistence of rolling codes

Describe you new feature you'd like
How are the sensitive rolling codes protected from a sudden power interruption?
I have delved a little deeper into the code, but so far I have only discovered the backup/restore function, which, as far as I understand, is explicitly called on demand by the user in the GUI.
If there is already another, invisible automated functionality for securing the persitence of the rolling codes, I am happy, if not, I see an opportunity resp. need for improvement here.
I have some implementation ideas for this (including protection against flash killing), which I would be very happy to contribute to.

Ah I see, sry, I must have misunderstood the correspondent passage in the backup&restore section
Honestly I had already guessed that, as you really seem to have thought of everything in your masterpiece 👍
Still - may I ask in which way and what cycles the rolling codes are written to the NVM? (I'm a bit worried if the controller will really last 10 or 20 years without the flash wearing out - I've made some bad experiences with deceased SD cards in Raspberry PI's and my Loxone Server...)

They are transactional.  The NVS uses wear leveling so you have nothing to worry about here.  If a failure occurs it will not be because it wore out the NVS.  It will wear out your motors before it commands enough times to even get close to the block marking.   The LittleFS persistence is only written when on cycle and only when it is dirty.  So it only persists when a movement has completed or any of the configuration is saved.   This is part of the reason I do not write logs to Littlefs.

Sure. I think you should be able to count on the wear leveling of the littleFS (I assume it will be utilising Espresso's wear levelling API?). And you're right: I once extrapolated (under the pessimistic assumption of only 10000 write cycles until flash wear out) that a life span of 20 years allows more than 600 movements per day! That should be far more than enough for my 22 shutters, which now let me sleep peacefully 😅
Anyway - just in case it becomes a topic (e.g., if Espressif's wear levelling doesn't turn out to be quite as perfect...) - My idea would have been a relatively simple mechanism that utilises the rolling code tolerance (of ~+100?), of course minus adequate security, and triggers the write operation to the NVS only after "enough" movements have accumulated (still to be determined, e.g., when the first of all blinds has performed more than a tolerable number of movements since its last backup), and then the rolling codes of all shades are written to the NVS in one transaction... - I believe this could reduce the number of write operations by more than a factor of 100. Just something to consider, in case it becomes necessary someday...
Something else - regarding the impending memory shortage issue:
You noted that increasing SOMFY_MAX_SHADES can cause you to run out of memory. Conversely, does this mean that decreasing this value (I only have 22 shades and will never have more) would save memory and thus increase the stability of the system (probably not much, but still)?

(Of course, after power on and restoring the last backup, the rolling codes would need to be increased by an offset of that tolerance value + x, since it must be assumed that additional unsaved movements may have occurred since the last backup, thus ensuring that the next transmitted rolling code is sufficiently high (for this, the "+ x" will be meaningful for additional safety) but not too high.
The tolerance value still to be defined must be small enough to ensure sufficient distance from the assumed RTS tolerance of "approx. 100". On the other hand, it should be large enough to yield a worthwhile effect -> I believe a good value will likely be between 10 and 20...)
Oops, it just occurred to me a potential overflow of the 2-byte rolling code! Admittedly, 64k movements may sound like a lot for a single shade, but projected over 20 years, it suddenly becomes a realistic consideration... but I'm sure you've already cared about that :)

While the ESP32 wear leveling is not perfect in that it does not trim() the other components on the board are more likely to fail over time.  Eventually the motor will reject the rolling code if it is not correct and blacklist the address so incrementing the rolling code will cause the commands to start failing.
If you did 600 movements per day, you will be replacing the motors long before the ESP gives up the ghost.
The rollover of the rolling code is handled.  These are actually 15 bits not 16 although they are unsigned and roll over to 0.  Decreasing the number of shades will not change anything as far as stability since there is ample memory at 32 shades 16 groups and 16 rooms to allow for the call stack.

No no I meant 600 NVS writes per day = 600 total movements of all blinds if written after each movement —- anyway still very many per blind 😎
(One 4K block wear leveled on assumed 2M memory * 10,000 / 20 / 365; without counting addt’l config backups)

Yep you should be fine.  Having written a few bits of software for the pi I can tell you the killer of SD card isn't so much the number of writes it is the frequency of them.   The heat generated from hammering the card repeatedly for an extended period of time is a card death sentence.
The piOS does enough of that on its own but when folks try to log outside of a batch write it is inviting failure.   The pi5 however, has an nvme interface that will negate all of that.  For my HA instance, I use a mini-PC with an M.2 nvme.

Good discussion.  There are a lot more discussions about how one comes up with the duty cycle but know that every 4k block is not written on each transaction.

Hi @nbarrientos,
This is what I understood so far:

the last rolling code (of a drive, which of course is the same for all configured drives) is written to LittleFS after each operation, so the controller is insensitive to power failures etc.

During backup, the last rolling code is also written to the backup file.

As long as you do not change the hardware, restoring (any) backup will work, because the application compares the rolling code of the backup with that of LittleFS and takes the higher one.

As long as you have a planned hardware change in mind, this is not a problem, as you can make a backup with the current rolling code just before the change.

Yes, I agree with you: If you have to completely rebuild the controller after a total failure, the up-to-dateness of the backup is crucial, because the LittleFS of the new controller is initially empty and only the rolling code of the backup can be used. So if the backup is very old, the rolling code stored there will most likely be too small and therefore out of sync. Apart from the regular backup, I can't think of anything really intelligent to do here - except perhaps to carefully patch the rolling code in the backup file (which is an editable text file) to a value increased by a maximum of 99 (if the rumor is true that the rolling code tolerance is +100). But this is by no means a sure thing, and would only work approximately if the backup file is not too old...
Another alternative would be to reset the rolling code on the drive itself. However, this does not work on all drives and has not been sufficiently tested or verified (see #293).

Actually the last rolling code is also stored in the NVS partition.  The problem is that if you do a total rebuild the NVS is erased prior to recreating the partitions.  There is no way around that on the ESP32.
However, there is a way to get a periodic backup.  This can be done with the backup entity in HA or by sending it GET http://<ip address>/backup
If you want it in a response that is just a text output of the values GET http://<ip address>/shades.cfg

Thanks! I'll schedule daily backups, then. Maybe it's worth adding a simple recipe to the documentation, something like:
wget --content-disposition http://espsomfyrts.lan/backup -P /backups/config/espsomfy --quiet

For info, even though my instance of ESPSomfyRTS is protected by username/password, the /backup endpoint dumps a full backup without any authentication needed. Not expected, I'd say :)


Run Algolia Crawler on Refresh

It is necessary to run the Algolia crawler when new documents are added to the site, so that they are available in search results immediately.
Part of this issue is adding reporting if there are errors.

[ ] Re-index the site in Algolia when content changes using the Algolia REST API: https://www.algolia.com/doc/rest-api/crawler/

Suggested approach for error reporting:

[ ] Report any links that are crawled that result in 500 or 404 HTTP error. Errors generated by the repository submission that triggered the refresh webhook should be reported to that same repository in the for of an issue using the GitHub API.
[ ] The "bad links" report should include information about what page contains the links.

switched to typesense and static builds https://github.com/onflow/docs


SRG Request analyses for lack of biological data collection in 2021

2022 Assessment
SRG Request # 12

If biological data cannot be collected by any fleet in 2021, the SRG encourages the JTC to explore model sensitivity to that absence. We commend the JTC for their foresight in investigating the impact of the lack of 2020 Canadian freezer-trawler age data in this year’s assessment.

@cgrandin I don't think was a problem for Canada was it? It was NOT a problem for the US.

[ ] Add response to the Assessment

@cgrandin can you give a summary of the data that was NOT available for 2021? Didn't you say that there were no observers? I am not sure exactly what fleet / samples that translates to though.

Potential runs

remove all Canadian fishery ages to get an idea of an overall value
just Canadian age data from 2020 and 2021 b/c that is realistic of where we are at today (even though there were a few ages in 2021 and some from shoreside in 2020)
remove Canadian ages from Freezer Trawler sector (none to remove in 2021 or 2022)

In 2021 assessment we just did (3).
@cgrandin what are they proposing for the future, would shoreside ages be collected or nothing from either sector?

@kellijohnson-NOAA apologies for late response here -
I have not heard anything concrete about plans to sample the freezer trawler catch. The rumor I have heard is that there will be some sampling done on shore when the FT's come in from their week-long trips. But then I'm guessing the data would be aggregated to trip (nobody is going to separate them all into haul samples while at sea).
Shoreside should proceed as normal.


add indicator to lab-card

This PR will resolve #811

Preview of how I made it.

Great, I think this is okay for now. I personally would probably put the icon back in the bottom right corner (with spacing) and maybe even add a matToolTip that says something like "this execution has outputs" or maybe even make the icon link to the execution's output view.
But this can be done in a following PR.
 :)
Thank you man!

Great, I think this is okay for now. I personally would probably put the icon back in the bottom right corner (with spacing) and maybe even add a matToolTip that says something like "this execution has outputs" or maybe even make the icon link to the execution's output view.

Agree!
This is better for the UX so I will add it.  💪

Result:

Really don't wanna be picky here, but I think the commit message should be feat(...): ....
Not sure if the changelog generator will pick it up otherwise..

Oh, and don't forget to put the
Closes: #811

back in there :)

Oops..

Oops..😃

Sweet! Waiting for travis

Thanks for the quick response!


Debugger stopped working after MacOS X Catalina update

Hello all,
I'm using vscode 1.45.1 with vscode-cmake-tools 1.4.0 with MacOSX Catalina 10.15.5. I always had some trouble to use it, when I launch the debugger without any further configuration the debugger get stuck. After some searching I found a solution, adding this to settings.json
"cmake.debugConfig": {
    "stopAtEntry": false,
    "MIMode": "lldb",
    "miDebuggerPath": "/Users/macdev/.vscode/extensions/ms-vscode.cpptools-0.28.1/debugAdapters/lldb-mi/bin/lldb-mi"
}

and it started to work perfectly for months. Some day ago I received the Catalina update and now when I launch the debugger it stops with the following error: (it's translated from italian)
"Unable to find GDB in the predefined search path and in "/Users/macdev/.vscode/extensions/ms-vscode.cpptools-0.28.1/debugAdapters/lldb-mi/bin/lldb-mi".
I tried to remove the above configuration from the settings.json but everything go back to the initial situation, when the debugger get stuck after launch.
I don't know if it's a bug, but it's strange that everything worked perfectly for months and now stopped working.
Thank you in advance.
EDIT: Sorry, I had to update the miDebuggerPath to 0.28.2. Closing...

Sorry, I had to update the miDebuggerPath to 0.28.2. Closing...

Just wanted to note that 0.28.3 was released this morning so you'll need one more update until we update this extension to find it for you.


Unable to start App

Im getting below error in cmd
Failed at the<EMAIL_ADDRESS>start script 'webpack-dev-server --hot'.
Make sure you have the latest version of node.js and npm installed.
If you do, this is most likely a problem with the reactapp package,not with npm itself.

Closing because the latest version was completely refactored.


ImportError: No module named 'youtube_dl.extractor.alphaporno'

Hey
Trying to youtube-dl -l -x "http://www.youtube.com/watch?v=A9ew7glBHy0", fails with:
Traceback (most recent call last):
  File "/usr/lib64/python3.4/site-packages/youtube_dl/extractor/__init__.py", line 4, in <module>
    from .lazy_extractors import *
ImportError: No module named 'youtube_dl.extractor.lazy_extractors'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/youtube-dl", line 3, in <module>
    import youtube_dl
  File "/usr/lib64/python3.4/site-packages/youtube_dl/__init__.py", line 43, in <module>
    from .extractor import gen_extractors, list_extractors
  File "/usr/lib64/python3.4/site-packages/youtube_dl/extractor/__init__.py", line 9, in <module>
    from .extractors import *
  File "/usr/lib64/python3.4/site-packages/youtube_dl/extractor/extractors.py", line 23, in <module>
    from .alphaporno import AlphaPornoIE
ImportError: No module named 'youtube_dl.extractor.alphaporno'

In fact just running youtube-dl without any arguments, or with --help, produces that fail.
Version 2016.04.13

Actually looks like a Gentoo Portage package issue.

Reported https://bugs.gentoo.org/show_bug.cgi?id=580070

Actually looks like a Gentoo Portage package issue.

I'm closing it here. Please leave comments if it's not a Gentoo issue but a youtube-dl one.


[1pt] All data should be preserved - Team member #3

All data should be preserved by saving collections in .json files.

All was ok


Convert the downtime_id to be a string for the perform worker action

According to http://stackoverflow.com/a/17277093, this is the fix for
the Errbit errors we've been seeing (https://errbit.publishing.service.gov.uk/apps/5304e0520da11511b0000011/problems/58d536ee65786370a1900000).
I'm doing this .to_s directly here, because I think this is the only
place in the file where the downtime_id parameter isn't previously
stringified. The other downtime_id parameters are used from other
methods (self.schedule_publish_and_expiry, for example) which have
already had the downtime.id.to_s treatment, but perform isn't
called from any of these. I did try to trace this through the
workers/controllers/models to see where perform was being called
directly, but I couldn't - I presume it's a purely Sidekiq thing.

"When green" might be a while given how red CI is still looking after many rebuilds.

It's green! 🎉


Expand All is not activated in the References bar.

Does this issue occur when all extensions are disabled?: Maybe Yes? (It is impossible to reproduce without using a C# extension.)

VS Code Version: 1.85.1
OS Version: Mac OS Sonoma 14.1

Steps to Reproduce:

Check the list in the References bar using Find All Reference for anything in the C# file.
Then press the Collapse All button in the References bar.
Expand All is not possible even though all lists have collapsed.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

@jrieken
Why is this issue a feature-request and should it be voted on?
A feature that worked well in versions before vscode 1.85 has a problem after version 1.85.
This is a bug. Please review again. thank you

The tree view only offers a "Collapse All" actions. Individual tree views could add their own "Expand All" action if they want to.
There are two possible feature requests here:

Allow all trees to opt in to an "Expand All" action
Add an "Expand All" actions to just the references view.

Add an "Expand All" actions to just the references view.

This one is actually not great to implement, so I think this is better as a feature request to add an "Expand All" that all trees can opt in to.

@alexr00
Thank you for answer.
I guess I was mistaken. I thought I had used that feature before, but I guess not.
Currently, this function is in the Search Bar, so I hope you find it useful.
thank you

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


image size 100%

Id like to have a responsive component and want to set width="100%" but since the croppa component is not accepting % values and the width is hard coded into the elements style tag its kinda hard to overwrite it with CSS rules .. what is the preferred way to set 100% width?

#76 This issue was addressed here and has been solved : )

Oh thx - that option wasnt inside the Template Example and since its pretty long i thought it has everything in there.
BUT
i just tested this: with version 1.3.0-1.3.3 it works, but in 1.3.4 the content is broken/not visible when set to auto-resize :(

I will look into that. Thanks!

Same problem here... I have been using in the past the jquery plugin called guillotine and it works really well but now Im using vue and croppa would fits my needs if it was responsive keeping aspect ratio
Thank you :)

@kakulukia @mcordoba auto-sizing issue in 1.3.4 is fixed in 1.3.5.

@kakulukia @mcordoba The problem with auto-sizing in v1.3.4 is fixed in v1.3.6.

Thank you for the update but it is not keeping the aspect ratio. If I show it in desktop at 300x200 and then in mobile I have 200px width, the height must be 133px. It is adapting to the available width but the height is fixed to the initial value.
Would be possible to have this feature?

Well, this is not a croppa thin in my opinion. When setup correctly this works like it should.
Here is how you could do it:
.headerImage <- this is the croppa wrapper
  width: 100%
  padding-bottom: 30%
  position: relative
  canvas
    position: absolute
    top: 0
    left: 0
    bottom: 0
    right: 0

@mcordoba do you found a solution?


for macOS

macOS users can use "fswatch" command instead of UnityCompileInBackground-Watcher.
I wrote a patch for watch filesystem events with "fswatch" while Unity Editor is running macOS.

Thank you!


Could you keep your comments constructive; there's no need to use offensive language here
We welcome feedback, and contributions, but please keep it constructive.
I see you opened another issue regarding docker run -v; https://github.com/docker/docker.github.io/issues/2598, so I'll close this one.


Fix: Adapt usage of typed Arrays for RC1

Description
Godot 4 RC1 is stricter with its usage of typed arrays. This PR will adapt the usage of typed arrays so it won't throw errors anymore.

Thanks a ton!


onChange: do not check class name

Checking class name existence before removing it is a little bit over-engineered :)
Simply call the remove function, and let it handle the case when the class doesn't exists.

Rebased onto master and tagged in v1.6.2.


fixed some things

fixed order of navigation
added github and wiki link
commented out reading time
changed icon of the doorsensor in
deleted example page

mein erster pull request 😊

accepted


Does it allow downloading of the pdf?

It looks like you just ignored my lovely handmade issue template. Please help me solving your issue by answering the questions asked in this template. Please open a new issue with filled issue template.


[Nacos] Support ServerIntrospector

[Nacos] Support ServerIntrospector
Fixes #650
I add the code to support the ServerIntrospector.
And I add the test in spring-cloud-alibaba-dubbo-examples.
Please check it

Thanks for your contribution, we will review it soon.

It seems we should implement isSecure(Server server) method.
The secure info stored in Metadata. Look at NacosDiscoveryProperties#init:
if (secure) {
	metadata.put("secure", "true");
}

@flystar32 how do you think about it?

Hi @fanyy .
We should override public boolean isSecure(Server server) method of DefaultServerIntrospector.
The secure info can be getted by the secure key of NacosServer#metadata.


which optimizer is used in pointpillars

in the config file
hv_pointpillars_secfpn_6x8_160e_kitti-3d-3class.py
doesn't define which type of optimizer( like adam or else) is used in contrast to other methods which is defined
it defines just the learning rate
lr = 0.001
optimizer = dict(lr=lr)

We use inheritance in the configuration system. The type of optimizer is defined in the file _base_/schedules/cyclic_40e.py, where AdamW optimizer is utilized.


Drop previously fetched data possible?

Hello, I am looking for an infinite scrolling solution. In your code it seems like all loaded elements are concated to your existing state data array. Did you think about dropping the previous data? (recycler view) Is this possible using your code?
Kind regards.

i second this. i have rendered thousands of DOM elements and its becoming slower and slower. is it possible to only show the dom elements into view

This is not the point of this library. If you wanna combo it with some other tools that do this you can do it freely; I'd recommend https://www.npmjs.com/package/react-recycled-list


App crash when /create-intent request fails during apple pay

Describe the bug
When you pay with applepay and any kind of error is returned from /create-intent the app is being crashed.
Docs with the flow we follow: https://docs.stripe.com/payments/accept-a-payment-deferred?platform=react-native
To Reproduce
Steps to reproduce the behavior:
return error from the backend /create-intent request during applepay from @stripe/stripe-react-native presentPaymentSheet method
Expected behavior
Nn error is displayed instead of the app crashing
Screenshots
✅  /create-intent returns client_secret
https://github.com/user-attachments/assets/62b423dd-53d6-4b8d-a11e-0a1027e92954
🔴  /create-intent throws an error - card is working well, apple pay - app crashes
https://github.com/user-attachments/assets/1ab84c80-8950-43d3-bcf2-5ea41d08264b
Demo repository with app & server code
just provide your sandbox keys in server, run the server and build the app locally
https://github.com/bartoszboruta/stripern
Smartphone (please complete the following information):

Device: iPhone 15 - any kind of iphones
OS: 17

Additional context
Thread 9 Crashed:
0   libsystem_kernel.dylib        	       0x1113353b0 0x11132c000 + 37808
1   libsystem_c.dylib             	       0x10fac75c0 0x10fa54000 + 472512
2   libswiftCore.dylib            	       0x10f12f0cc 0x10ee5c000 + 2961612
3   libswiftCore.dylib            	       0x10f12f0e8 0x10ee5c000 + 2961640
4   libswiftCore.dylib            	       0x10f179c50 0x10ee5c000 + 3267664
5   CoreFoundation                	       0x10d5b9288 0x10d488000 + 1249928
6   CoreFoundation                	       0x10d5bb5ac 0x10d488000 + 1258924
7   PassKitCore                   	       0x1328586dc 0x1323cc000 + 4769500
8   PassKitCore                   	       0x132858344 0x1323cc000 + 4768580
9   stripern                      	       0x10549c56c @nonobjc PKPaymentAuthorizationResult.init(status:errors:) + 152
10  stripern                      	       0x105494bf0 PKPaymentAuthorizationResult.__allocating_init(status:errors:) + 52
11  stripern                      	       0x105494894 closure #1 in STPApplePayContext.paymentAuthorizationController(_:didAuthorizePayment:handler:) + 536 (STPApplePayContext.swift:380)
12  stripern                      	       0x105496618 closure #1 in STPApplePayContext._completePayment(with:completion:) + 508 (STPApplePayContext.swift:517)
13  stripern                      	       0x105497d40 closure #1 in closure #2 in STPApplePayContext._completePayment(with:completion:) + 1680 (STPApplePayContext.swift:559)
14  stripern                      	       0x1054a04a0 partial apply for closure #1 in closure #2 in STPApplePayContext._completePayment(with:completion:) + 132
15  stripern                      	       0x105a5e740 closure #1 in ApplePayContextClosureDelegate.applePayContext(_:didCreatePaymentMethod:paymentInformation:completion:) + 476 (STPApplePayContext+PaymentSheet.swift:67)
16  stripern                      	       0x105f14344 StripeSdk.intentCreationCallback(result:resolver:rejecter:) + 2128 (StripeSdk.swift:152)
17  stripern                      	       0x105f14660 @objc StripeSdk.intentCreationCallback(result:resolver:rejecter:) + 204
18  CoreFoundation                	       0x10d5bb760 0x10d488000 + 1259360
19  CoreFoundation                	       0x10d5b8ac4 0x10d488000 + 1247940
20  CoreFoundation                	       0x10d5b8d5c 0x10d488000 + 1248604
21  stripern                      	       0x104c2a758 -[RCTModuleMethod invokeWithBridge:module:arguments:] + 1796 (RCTModuleMethod.mm:584)
22  stripern                      	       0x104c2e7e4 facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&, int, (anonymous namespace)::SchedulingContext) + 1688 (RCTNativeModule.mm:196)
23  stripern                      	       0x104c2df80 facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int)::$_0::operator()() const + 128 (RCTNativeModule.mm:113)
24  stripern                      	       0x104c2def4 invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int) + 28 (RCTNativeModule.mm:104)
25  libdispatch.dylib             	       0x10e7be104 0x10e7bc000 + 8452
26  libdispatch.dylib             	       0x10e7bf978 0x10e7bc000 + 14712
27  libdispatch.dylib             	       0x10e7c7b10 0x10e7bc000 + 47888
28  libdispatch.dylib             	       0x10e7c8688 0x10e7bc000 + 50824
29  libdispatch.dylib             	       0x10e7d3a84 0x10e7bc000 + 96900
30  libdispatch.dylib             	       0x10e7d30d0 0x10e7bc000 + 94416
31  libsystem_pthread.dylib       	       0x11ab1b814 0x11ab18000 + 14356
32  libsystem_pthread.dylib       	       0x11ab1a5d4 0x11ab18000 + 9684

We are experiencing the same issue.
Passing any error to the intentCreationCallback in the deferred payment case when using Apple Pay will lead to a crash of the app. Using a credit card will work as expected.
To replicate this is a minimal confirmHandler for initPaymentSheet:
const confirmHandler = async (
  paymentMethod: Result,
  shouldSavePaymentMethod: boolean,
  intentCreationCallback: (result: PaymentSheet.IntentCreationCallbackParams) => void,
) => {
  const error = {
    code: PaymentSheetError.Failed,
    message: "There was an unexpected error -- try again in a few seconds",
    localizedMessage: "There was an unexpected error -- try again in a few seconds",
  } as StripeError<PaymentSheetError.Failed>;

  callback({ error });
};

https://github.com/user-attachments/assets/916c1cdb-2cde-4552-92be-0a2f5baa2970


HOTSTAR DRM SUPPORT!!

C:\ffmpeg\bin>youtube-dl --verbose https://www.hotstar.com/in/tv/game-of-thrones/8184/the-iron-throne/1770005178
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.hotstar.com/in/tv/game-of-thrones/8184/the-iron-throne/1770005178']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2021.01.03
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.19041
[debug] exe versions: ffmpeg 2021-01-05-git-66deab3a26-full_build-www.gyan.dev, ffprobe 2021-01-05-git-66deab3a26-full_build-www.gyan.dev
[debug] Proxy map: {}
[hotstar]<PHONE_NUMBER>: Downloading webpage
ERROR: This video is DRM protected.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp7n_m4vnl\build\youtube_dl\YoutubeDL.py", line 803, in wrapper
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp7n_m4vnl\build\youtube_dl\YoutubeDL.py", line 824, in __extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp7n_m4vnl\build\youtube_dl\extractor\common.py", line 532, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp7n_m4vnl\build\youtube_dl\extractor\hotstar.py", line 132, in _real_extract
youtube_dl.utils.ExtractorError: This video is DRM protected.

Why it has been closed?

Why it has been closed?


EntityAssigner not using proper EntityManager

I am using ApolloServer and passing a forked em into the ctx: Context. I am watching sql queries with debug mode on and notice that for a very simple case when fetching relationships there are fewer queries than expected, meaning that somehow my forked em is being polluted with global context from previous requests.
I am still familiarizing myself with the code, but I believe the error might stem from EntityAssigner L15
  static assign<T extends AnyEntity<T>>(entity: T, data: EntityData<T>, onlyProperties: AssignOptions | boolean = false): T {
    const em = wrap(entity).__em;
    ...

which is called by EntityManager L222
    // add to IM immediately - needed for self-references that can be part of `data` (and do not trigger cascade merge)
    this.getUnitOfWork().merge(entity, [entity]);
    EntityAssigner.assign(entity, data as EntityData<T>, true);
    this.getUnitOfWork().merge(entity); // add to IM again so we have correct payload saved to change set computation

EntityAssigner.assign is accessing a different instance of em that has more objects defined in its unitOfWork.identityMap than the forked instance of em that we had been using in EntityManager.merge previously in the call stack.
Here is the relevant portion of my index.ts just to show you that I am following all of your suggestions and still having this issue:
  app.use((req, res, next) => {
    RequestContext.create(orm.em, next);
  });

  const apolloServer = new ApolloServer({
    schema: await buildSchema({
      resolvers: [UserResolver]
    }),
    context: ({ req, res }) => {
      const em = orm.em.fork()
      em.clear()
      // confirming that each request starts with a clean map
      console.log(em.getUnitOfWork().getIdentityMap())

      return {
        req,
        res,
        em,
      }
    }
  });

If you are creating the request context manually (via the em.fork(), you do not need to use the RequestContext helper (on the app level bootstrap, you should use only one of those). The only downside is that you will need to use the forked em all the time in your requests manually (aka this breaks DI on controller level, you can't inject EM or repositories and use those as they would be associated with wrong EM - and that is what the RequestContext is for). Or on the other hand you could use it and drop the manual forking.
Also note that em.getUnitOfWork() will return UoW stored in current request context (the one started from RequestContext helper). So in your snippet, you are creating the fork, but console.log(em.getUnitOfWork().getIdentityMap()) will return the UoW (and its IM) from the one created from RequestContext helper.
Same problem applies to em.clear(), under the hood it will also prefer the UoW from RequestContext. So in your snippet, you create the fork, but you clear different EM than you think. But the em.fork() itself will clear the IM by default, so you can just omit the line.
If you use latest v3, there is second parameter in em.fork() that allows you to specify whether the new (forked) EM will use its own UoW/IM, or it will fallback to the one created RequestContext. By default em.fork() will give you clean IM and the new EM will not fallback to the RequestContext.
Btw as part of em.merge(), the entity is also reassigned with internal EM reference. That is the one you get via wrap(entity).__em`.

EntityAssigner.assign is accessing a different instance of em that has more objects defined in its unitOfWork.identityMap than the forked instance of em that we had been using in EntityManager.merge previously in the call stack.

If this is really true then it sounds like you are loading the particular entity from some global context, and not from the request handler. Could you share more information about that? What code, and what entity (created/loaded where) causes this?
But as I said, em.merge will reassign the internal em reference so it sounds really weird that you would get a wrong one in the following line.

Here's a minimal repo to reproduce. I appreciate you taking a look.
In this repro I only use em.fork(). You can see I commented out the RequestContext middleware. In my testing, the domain.run calls next() but returns before my ApolloServer request is run, which ends the domain lifecycle, making it useless.

Thanks for the repro, that will help a lot! Will try to look into this soon.

Much appreciated. This library looks super promising, I really appreciate your hard work.

I did a bit more digging and here is what I believe is happening:
The getter for wrap(entity).__em is created by EntityHelper.decorate, which is called by metadata.decorate, which only happens in the bootstrap phase of MikroORM.init.
Therefore, in future requests, even though a forked em is passed, the wrap(entity).__em returns the "global" one created in the bootstrap phase by MikroORM.init.
I've also found that I have the desired outcome if every request I fork the em and clear the global em like so:
  const apolloServer = new ApolloServer({
    schema: await buildSchema({
      resolvers: [UserResolver]
    }),
    context: ({ req, res }) => {
      const em = orm.em.fork()
      orm.em.clear()

      return {
        req,
        res,
        em,
      }
    }
  });

This also supports my conclusion that the global em is being used. Hope that's helpful. In case you already pulled my repo, I added a few more comments to make it super easy to trace.

Therefore, in future requests, even though a forked em is passed, the wrap(entity).__em returns the "global" one created in the bootstrap phase by MikroORM.init.

As I said, em.merge() does replace this reference with the current one, so this should not be the problem.

In this repro I only use em.fork(). You can see I commented out the RequestContext middleware. In my testing, the domain.run calls next() but returns before my ApolloServer request is run, which ends the domain lifecycle, making it useless.

If you do not use RequestContext helper, then there is no magic involved (no domain api used).

I'm sorry, I think I was unclear and made this thread confusing. I am not using RequestContext at all, although I had previously (and unsuccessfully) tried it. I am only using em.fork().
Please do check out my repo when you have a chance, I really believe there is unexpected behavior. Here is why I believe merge is not working as you say.
In my example I am fetching two linked objects: a User and a Tag. Here is what happens on the second request.

The user is fetched and merge is called. The forked em's IdentityMap is empty. entity === undefined, and so __em is not redefined. Therefore, user.__em still points to the global reference, not the forked one.

The EntityAssigner will merge all properties from user.__em (the global reference) into the newly fetched object. This includes the details of the tag from the previous request, even though it hasn't been fetched yet in this request.

  merge<T extends AnyEntity<T>>(entityName: EntityName<T> | T, data?: EntityData<T> | boolean, refresh?: boolean): T {
    ...
    // See Point 1
    let entity = this.getUnitOfWork().tryGetById<T>(entityName, data as FilterQuery<T>);
    if (entity) {
      Object.defineProperty(entity, '__em', { value: this, writable: true });
    }
    ...
    // See Point 2
    this.getUnitOfWork().merge(entity, [entity]);
    EntityAssigner.assign(entity, data as EntityData<T>, true);
    this.getUnitOfWork().merge(entity); // add to IM again so we have correct payload saved to change set computation

    return entity;
  }

Ok so the problem is that the em.merge() is actually not correcting the internal __em value as it should be (not for the user entity because it was not looked up by primary key).
Will try to publish new version soon.

Makes sense. Thanks!

Btw as a workaround, you can do this correction yourself. I think it should be enough to merge it again:
const user = await ctx.em.findOne(User, {
  firstName: 'user-1',
});

if (user) {
  ctx.em.merge(user);
}

return user;

If not, you can reassign it directly:
if (user) {
  wrap(user).__em = ctx.em;
}

Fixed in 3.0.0-rc.1.


Runtime error

$ ./test_ordered_map
libc++abi.dylib: terminating with uncaught exception of type boost::unit_test::framework::setup_error: test unit with name 'test_insert<tsl__ordered_map<long long, long long, std____1__hash<long long>, std____1__equal_to<long long>, std____1__allocator<std____1__pair<long long, long long> >, std____1__deque<std____1__pair<long long, long long>, std____1__allocator<std____1__pair<long long, long long> > > >>' registered multiple times
[1]    48387 abort      ./test_ordered_map

Hello,
Thank you for the report. Which compiler do you use as I can't reproduce the problem on my side (neither with GCC, Clang or MSVC)?
Nonetheless, I removed some duplicate types in test_types of tests/ordered_map_tests.cpp which could be the reason of the registered multiple times error. Could you try it with the last commit?

With which version of Boost?
Does the last commit resolves the problem?

It resolved it! I'm using Boost version: 1.67.0. Thank you!


[PE-D][Tester E] App - [cd] [done mod]

Steps to reproduce

Launch the app
Type in the command cd cs2109s
Type in the command done mod cs2109s

Expected
Mark CS2109S module as done
Actual
Error message of "Please exit the current module using 'cd ..' command!"
Notes
Not sure whether it is compulsory to exit a module before marking a module as done ( done module command), but if it is, it would be good to include it in the UG (put a "Note" box or a "Warning" box)
Screenshot

Labels: severity.Low type.FunctionalityBug
original: yuxuanleong/ped#4

I think this can also be resolved by adding to the UG


Failed to download the PDB of clrjit.dll

Failed to download the PDB of clrjit.dll  04E0A0B260EE4C95B1E8374FC2AE68C810 cant' get it.

PLS. Everybody can upload this PDB of clrjit.dll 04E0A0B260EE4C95B1E8374FC2AE68C810 .THX.THX...


In recipes - add option to create non-ephemeral or ephemeral nodes

Hello! Could We add option to create non-ephemeral or ephemeral nodes into Recipes(Lock, SharedLock)? Like in kazoo https://github.com/python-zk/kazoo/blob/master/kazoo/recipe/lock.py#LC129
I can do it

@nonspher I'm not against, but personally, I don't see too much sense in having non-ephemeral locks for most cases.
For example, if some process just dies, you will have basically deadlock. From my point of view, it is better not to push bad design decisions. If someone needs it is really easy to subclass lock and make it explicit.
If you want to implement it, feel free to make PR + tests.


mgmt: mcumgr: accept "offset reverted" packets to improve robustness

reverted offset could be caused by ble connection is unstable or mcu high load. Overwrite fs_mgmt_ctxt.off to off to continue upload process, this improves upload success rate

@nordicjm Thank you for your prompt response.
i am not sure how ble retry behaves, but i indeed test under ble link.
reverted offset also happens even if mcumgr client send the same packet at application layer.
As I mentioned in the PR, reverted offset happens only at high mcu load (possible) or unstable BLE connection (may not)
my test log is like this:
                     off      fs_mgmt_ctxt.off
...
fs_mgmt_file_upload 285552 <-> 285552
fs_mgmt_file_upload 287972 <-> 287972
fs_mgmt_file_upload 290392 <-> 290392
# reverted offset
fs_mgmt_file_upload 285552 <-> 292812
fs_mgmt_file_upload 285552 <-> 292812
fs_mgmt_file_upload 285552 <-> 292812

# seesion aborted

my test environment:

zephyr v3.2-branch
nrf52840
nRF Connect Device Manager v1.6.0

You'd need to get a trace with e.g an nRF52840 loaded with the sniffer firmware showing where this "revert" is coming from, zephyr should not be sending a lower offset.

The reverted offset is sent by app, this is related to client upload api.
OK. Let me try to sniff rf packets, and provide more details.

@dinesharjani this sounds like an app bug?

@nordicjm this is Android? I think? The version number looks like Android. But I would not discount that this issue could be on the side of iOS as well, I can have a look at the code. Anyway, pinging @philips77

Yes. I tested through android nRF Connect Device Manager v1.6.0.

i will provide more information. Please allow me some time.
In my point of view, the transport layer can't always guarantee each pkt will be received only once, from my experience it is not easy, and costive. (For example mqtt QoS 2: exactly once.)
For current implementation, even a retry packet would stop the process (of course you can say it is on transport, but it is not always the way).
I do agree my case is not a general case. This patch just improve robustness, and doesn't break anything. It is some sort none common sense, but it do good.

In my point of view, the transport layer can't always guarantee each pkt will be received only once, from my experience it is not easy, and costive. (For example mqtt QoS 2: exactly once.)

Well in bluetooth it does actually, MQTT does too. In fact they both work similarly, for TCP/IP the host sends the data, the receiving device then sends an ACK packet - if the ACK packet is not received then the message will be sent again - it will be marked as a retransmission and have the same IP header details as the previous packet, so if the receiving device gets it again, it knows that the ACK packet was lost and will retransmit it, it will not give that data to the application again. Likewise in BLE, all transmissions are acknowledged, the difference is in where they are acknowledged, indications and write with response packets are acknowledged at the application level, notifications and write without response packets are acknowledged at the stack level - the difference being that if the applications buffers or configuration is such that it cannot accept the data, notifications/write without response data will be dropped whereas indication/write with response will not and will need to be resent until it is accepted. If that is the issue you are seeing, then chances are your devices buffer configuration is inadequate for the amount of data the phone is sending, but that would not explain why the file write position counter would be going backwards.


Missing exact block blockchain state tag

We need to add exact block tag. It should be the number of the block that is converted to hex. It is an alternative for latest, pending state.

@biboran/z please, pay attention to this issue

#47 needs a fix before this one


color names

Color names should be user intuitive, i.e. "deeppink" should be "deep pink"

Pr #53 solves this issue.


Generative AI

created AI chatbot for users to use
both users will share the same conversation history, allowing for a better collaboration and ease of discussion :)

minor aesthetic fixes (i think the input text box size is different from the chatbox) and can consider changing the names "AI ASSISTANT" and "Chatbot"


Run locally

"How do I run this project locally? I see that you're using next-auth, but there doesn't seem to be any handling for local execution."

rename the env.example.txt to .env.local

It worked! Thank you very much.

It worked! Thank you very much.