No such file or directory for GPU arch : gfx1035

Hello,
I don't know if it should be the best place for this issue (maybe it belongs to the ollama official repository).
My laptop has an iGPU AMD Radeon™ 680M.
I am using the flake to build ollama with rocm support.
{
  description = "learning";

  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/master";
    ollama.url = "github:abysssol/ollama-flake";
    flake-utils.url = "github:numtide/flake-utils";
  };

  outputs = { self, nixpkgs, ollama, flake-utils }:

  flake-utils.lib.eachDefaultSystem (system:
    let
      pkgs = import nixpkgs {
        inherit system;
        config.allowUnfree = true;
      };
      ollama-rocm = ollama.packages.${system}.rocm;
    in {

      devShell = pkgs.mkShell {
        buildInputs = with pkgs; [

          valgrind
          poetry
          ruff
          stdenv.cc.cc.lib
          ollama-rocm
        ];
        LD_LIBRARY_PATH = "${pkgs.stdenv.cc.cc.lib}/lib";
      };
  });
}

When I try to generate some tokens via the API (I tried with mistral and phi) I have the following trace:
> ollama serve                                                                                nix-shell-env
time=2024-02-25T20:58:47.533+01:00 level=INFO source=images.go:710 msg="total blobs: 19"
time=2024-02-25T20:58:47.533+01:00 level=INFO source=images.go:717 msg="total unused blobs removed: 0"
time=2024-02-25T20:58:47.534+01:00 level=INFO source=routes.go:1019 msg="Listening on <IP_ADDRESS>:11434 (version 0.1.26)"
time=2024-02-25T20:58:47.534+01:00 level=INFO source=payload_common.go:107 msg="Extracting dynamic libraries..."
time=2024-02-25T20:58:47.799+01:00 level=INFO source=payload_common.go:146 msg="Dynamic LLM libraries [cpu cpu_avx2 rocm cpu_avx]"
time=2024-02-25T20:58:47.799+01:00 level=INFO source=gpu.go:94 msg="Detecting GPU type"
time=2024-02-25T20:58:47.799+01:00 level=INFO source=gpu.go:265 msg="Searching for GPU management library libnvidia-ml.so"
time=2024-02-25T20:58:47.799+01:00 level=INFO source=gpu.go:311 msg="Discovered GPU libraries: []"
time=2024-02-25T20:58:47.799+01:00 level=INFO source=gpu.go:265 msg="Searching for GPU management library librocm_smi64.so"
time=2024-02-25T20:58:47.799+01:00 level=INFO source=gpu.go:311 msg="Discovered GPU libraries: [/nix/store/0x1y6by0mjcm1gn91rdn0bq5bh0f6l1i-rocm-smi-5.7.1/lib/librocm_smi64.so.5.0]"
time=2024-02-25T20:58:47.803+01:00 level=INFO source=gpu.go:109 msg="Radeon GPU detected"
time=2024-02-25T20:58:47.803+01:00 level=INFO source=cpu_common.go:11 msg="CPU has AVX2"
time=2024-02-25T20:58:58.038+01:00 level=INFO source=cpu_common.go:11 msg="CPU has AVX2"
time=2024-02-25T20:58:58.039+01:00 level=INFO source=cpu_common.go:11 msg="CPU has AVX2"
time=2024-02-25T20:58:58.039+01:00 level=INFO source=cpu_common.go:11 msg="CPU has AVX2"
loading library /tmp/nix-shell.YHbFgT/ollama2810121158/rocm/libext_server.so
time=2024-02-25T20:58:58.109+01:00 level=INFO source=dyn_ext_server.go:90 msg="Loading Dynamic llm server: /tmp/nix-shell.YHbFgT/ollama2810121158/rocm/libext_server.so"
time=2024-02-25T20:58:58.109+01:00 level=INFO source=dyn_ext_server.go:150 msg="Initializing llama server"

rocBLAS error: Cannot read /nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary.dat: No such file or directory for GPU arch : gfx1035
 List of available TensileLibrary Files :
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx940.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx1100.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx908.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx1030.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx90a.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx942.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx906.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx900.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx1102.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx941.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx1101.dat"
"/nix/store/ialcylww20hrrzy91agi6ncqrk528fzs-rocblas-5.7.1/lib/rocblas/library/TensileLibrary_lazy_gfx803.dat"
[1]    409190 IOT instruction (core dumped)  ollama serve

Do you see any obvious issue ?
Thank you very much.

It seems to me that the version of rocblas in nixpkgs (5.7.1) doesn't support your gpu. As far as I can tell, this is purely a nixpkgs problem, not an upstream ollama nor llama.cpp problem.
There's already an issue in upstream nixos/nixpkgs#280927 about updating to version 6,  and a related pull request nixos/nixpkgs#289187, but I'm not sure if it's making progress. If that stalls for too long, I may try to update rocmPackages myself when I have enough free time, but for now your gpu will be unusable, unfortunately.

Thank you very much for your insight, as I had trouble identifying the root of the issue alone.
I will try to upgrade the package myself, as I have some spare time to spend these days. :)

Hi, I've taken a closer look at this issue.
Currently, it seems sensible to wait for Vulkan support to be implemented in Ollama. In the meantime, I've modified the flake.nix and the build-ollama.nix in my fork that includes Vulkan support, assuming we can somehow pass this option to Ollama.  --> https://github.com/adfaure/ollama-flake/commit/2edd38fabd013ae86e1eec6acb632c09265aab42
For local testing, I had to add the option "LLAMA_VULKAN=on" at this line.

Have you tried enabling rocm on a recent version of ollama from nixpkgs? The version in nixpkgs-unstable has been using version 6 of rocm libraries, which may be worth trying to see if your gpu works with them. Just update your unstable channel/flake input, and check ollama --version to make sure it's 0.1.31.
With nixos-unstable:
services.ollama = {
  enable = true;
  acceleration = "rocm";
};

With nixos-23.11 and nixpkgs-unstable:
services.ollama = {
  enable = true;
  acceleration = "rocm";
  package = unstable.ollama;
};

Also, maybe setting LLAMA_VULKAN in nix could work?
 goBuild ((lib.optionalAttrs enableRocm {
   ROCM_PATH = rocmPath;
   CLBlast_DIR = "${clblast}/lib/cmake/CLBlast";
 }) // (lib.optionalAttrs enableCuda {
   CUDA_LIB_DIR = "${cudaToolkit}/lib";
   CUDACXX = "${cudaToolkit}/bin/nvcc";
   CUDAToolkit_ROOT = cudaToolkit;
+}) // (lib.optionalAttrs enableVulkan {
+  LLAMA_VULKAN = "on";
 }) // {
   inherit pname version src vendorHash;

Oh, looks like now my iGPU is now supported (680M) (https://github.com/ROCm/ROCm/discussions/2932).
I will try it thank you.
I tried the variable LLAMA_VULKAN, but the cmake still doesn't build llama with vulkan. I believe that gen_linux.sh needs to be updated to handle vulkan build. But maybe I am missing something.

I will try soon, and I guess if it works I can close the issue that is specific to rocm.
It might be worth opening a dedicated issue for vulkan ?

According to the linked issue, you should set HSA_OVERRIDE_GFX_VERSION:
services.ollama = {
  enable = true;
  acceleration = "rocm";
  environmentVariables = {
    HSA_OVERRIDE_GFX_VERSION = "10.3.0";
  };
};

You might consider opening such an issue about vulkan on the nixpkgs repo. If you do then ping me in it.


CI: docker-test target is broken on CircleCI due to arm64 no longer being available

Since few days ago, the publish_main job started to fail, in particular compare last successful and first failed run:

https://app.circleci.com/pipelines/github/thanos-io/thanos/8601/workflows/4c16d4a7-f94c-406f-853b-6133f701db93/jobs/17922
https://app.circleci.com/pipelines/github/thanos-io/thanos/8638/workflows/d9b63971-3ac2-4309-98eb-0e74ee25d3cd/jobs/17965

According to logs from the docker run --privileged tonistiigi/binfmt:qemu-v6.1.0 --install all step of the process, we are no longer able to install emulator for arm (or other architectures for that matter):
installing: riscv64 cannot register "/usr/bin/qemu-riscv64" to /proc/sys/fs/binfmt_misc/register: write /proc/sys/fs/binfmt_misc/register: invalid argument
installing: mips64le cannot register "/usr/bin/qemu-mips64el" to /proc/sys/fs/binfmt_misc/register: write /proc/sys/fs/binfmt_misc/register: invalid argument
installing: mips64 cannot register "/usr/bin/qemu-mips64" to /proc/sys/fs/binfmt_misc/register: write /proc/sys/fs/binfmt_misc/register: invalid argument
installing: arm64 cannot register "/usr/bin/qemu-aarch64" to /proc/sys/fs/binfmt_misc/register: write /proc/sys/fs/binfmt_misc/register: invalid argument
installing: ppc64le cannot register "/usr/bin/qemu-ppc64le" to /proc/sys/fs/binfmt_misc/register: write /proc/sys/fs/binfmt_misc/register: invalid argument
installing: arm cannot register "/usr/bin/qemu-arm" to /proc/sys/fs/binfmt_misc/register: write /proc/sys/fs/binfmt_misc/register: invalid argument
installing: s390x cannot register "/usr/bin/qemu-s390x" to /proc/sys/fs/binfmt_misc/register: write /proc/sys/fs/binfmt_misc/register: invalid argument
{
  "supported": [
    "linux/amd64",
    "linux/386"
  ],
  "emulators": null
}

Although my first suspicion was this is related to container privileges, I found some hints it might be related to kernel version - see issue - https://github.com/tonistiigi/binfmt/issues/53 - although according to the run outputs, I could not detect a difference in environments between successful and failed runs.

Resolved by https://github.com/thanos-io/thanos/pull/5083


Topic embeds

Relevant Issues

Closes #434
Description

Embeds are now used for providing the topic and the hyperlink to where you can suggest more. The form here has been updated to include the offtopic section.
Reasoning

By using itertools.cycle, all channels in the TOPICS dictionary have an infinite generator. This was created by shuffling the topics in their current state and then putting them into their own section of a dictionary. They were shuffled so on restart of the bot, reoccurring topics are less likely to occur.
Screenshots

Did you:

[x] Join the Python Discord Community?
[x] If dependencies have been added or updated, run pipenv lock?
[x] Lint your code (pipenv run lint)?
[x] Set the PR to allow edits from contributors?

Both previous commits that updated the py_topics.yaml file changed the IDs from the test server channel IDs to the actual Python Discord channel IDs.

The force pushes were both meant to show a different commit for the previous commits that only said that a file was updated.


Include object literals and arrays in javascript + typescript + jsx + tsx queries

It's easy to get lost in a big nested object literal.
What if we added a new query that records the current key of the object the user is focused inside of? It would be best if the query worked at any level of nesting so an object like
const foo = {
  bar: {
    baz: {
      bip: 'bop' // cursor on this line
    }
  }
}

would return {} foo > {} bar > {} baz > {} bip
I have a version that works for a single level of nesting but wanted to get a sense of whether this is a feature others would use before I dove in to figure out how to make this work at any level of nesting.

Hey! I am not that well versed with ts and js, but yeah, this seems like a good idea.

I have a version that works for a single level of nesting but wanted to get a sense of whether this is a feature others would use before I dove in to figure out how to make this work at any level of nesting.

We need a query to work only for one level, the plugin is able to recursively walk up the tree and extract the same pattern again and again. Could you share your treesitter queries?

I Would totally use this feature


Change license

I believe this program should be in the public domain. Please accept my pull request

I agree with @moncefmechri. In this day and age, a project such as this should definitely be in the public domain. Without such, how could @cpiotr feature this project on http://ciruk.pl?

the board games are for the people!


[Bug]: 2.3.21 Boot Problem

What happened?
After the update to V 2.3.21 I rann into a Boot Loop of the plugins Child bridge.
Device Type
Doorbell (Supported)
Plugin Version
v2.3.x (Best Effort)
HomeBridge Version
v1.7.x (Supported)
NodeJS Version
v20 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
Error: listen EADDRINUSE: address already in use :::49921
    at Server.setupListenHandle [as _listen2] (node:net:1897:16)
    at listenInCluster (node:net:1945:12)
    at Server.listen (node:net:2037:7)
    at EventedHTTPServer.listen (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:164:20)
    at HAPServer.listen (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:377:21)
    at Bridge.<anonymous> (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1365:18)
    at step (/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:195:27)
    at Object.next (/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:176:57)
    at /homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:169:75
    at new Promise (<anonymous>)

config
{
    "enableDetailedLogging": false,
    "CameraMaxLivestreamDuration": 30,
    "pollingIntervalMinutes": 10,
    "hkHome": 1,
    "hkAway": 0,
    "hkNight": 3,
    "hkOff": 63,
    "ignoreStations": [
        "T8030P2322510ACF",
        "T8410P4122298480"
    ],
    "ignoreDevices": [],
    "country": "DE",
    "cameras": [
        {
            "serialNumber": "T8114P0121091166",
            "rtsp": false,
            "snapshotHandlingMethod": 2,
            "videoConfig": {}
        },
        {
            "serialNumber": "T8410P4122298480",
            "rtsp": false,
            "videoConfig": {},
            "snapshotHandlingMethod": 2
        },
        {
            "serialNumber": "T8134P202326321C",
            "rtsp": false,
            "snapshotHandlingMethod": 2
        },
        {
            "serialNumber": "T8210P00202218E1",
            "rtsp": false,
            "enableCamera": true,
            "snapshotHandlingMethod": 2
        }
    ],
    "cleanCache": true,
    "unbridge": false,
    "ignoreMultipleDevicesWarning": true,
    "syncStationModes": false,
    "autoSyncStation": false,
    "username": ,
    "password": ,
    "deviceName": "",
    "platform": "EufySecurity",
    "_bridge": {
        "username": ,
        "port": 49921
    },
    "hsv": true
}

disable the plugin for 30min and try again. Sometimes homebase aren't closing their port.

disable the plugin for 30min and try again. Sometimes homebase aren't closing their port.

THX
I just solved it by changing the Port.


Sometimes fail to install geckodriver on windows platform

Describe the bug
On windows platform there is a report of unable to pnpm install on the main branch.
Expected behaviour
pnpm installation should succeed  under the main branch
Environment

Version: main branch
Platform: both Web App / Desktop App
OS:  Windows
Browser: any

To Reproduce
This does not seem to be for all installations, and is not reproduced for MacOS and Linux.
Any additional context, screenshots, etc

Successful on MacOS and Linux, eg:
threat-dragon % pnpm install geckodriver
Packages: +44
++++++++++++++++++++++++++++++++++++++++++++
<EMAIL_ADDRESS>Running<EMAIL_ADDRESS>Running postinstall script, done in 640msreused 125, downloaded 2, added 44, done

dependencies:
+ geckodriver 3.0.2

I removed it from package.json, will this work? @jgadsden

Hello @taoyiyang1 , we would prefer to keep geckodriver in the packages used for TD front-end. I have updated the main branch to use geckodriver version 3.0.2, could you pull this change and try installing again?
With a bit of luck this may cure the problem

All problems are solved, many package installations have to use a VPN, China has too many restrictions @jgadsden

Thanks for finding out what the problem is @taoyiyang1
I will update the documentation to suggest using a VPN if there are problems installing

I have added a FAQ in the Threat Dragon wiki : https://github.com/OWASP/threat-dragon/wiki/FAQs#failures-when-installing-from-source-code


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.5 to before v5.15.22",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=670638477aede0d7a355ced04b569214aa3feacd",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e83d941fd3445f660d2f43647c580a320cc384f6"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "670638477aede0d7a355ced04b569214aa3feacd",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "e83d941fd3445f660d2f43647c580a320cc384f6",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "perf/x86/intel/pt: Fix crash with stop filters in single-range mode\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.22 by commit e83d941fd3445f660d2f43647c580a320cc384f6, it was introduced in version v5.5 by commit 670638477aede0d7a355ced04b569214aa3feacd. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000594


Add converting auth util functions

What is a quick description of the change?
Adds util functions to the frontend that accesses the backend servlets from #99 to convert between user UID and email.
Is this fixing an issue?
Closes #63.
Are there more details that are relevant?
Two async functions were added to the index.js file of the AuthUtils directory: `getUserEmailArrFromUserUidArr' and 'getUserUidArrFromUserEmailArr'. Both access the corresponding servlet and returns its response. On servlet error, returns an empty array instead.
Check lists (check x in [ ] of list items)

[  ] Test written/updating
[  ] Tests passing
[x] Coding style (indentation, etc)

Testing is addressed in #99.
Any additional comments?

What happens if, on this site, I manually craft a post request to these servlet functions with a list of emails or uids? Will I get the list back, or is there some form of security preventing arbitrary post requests from being responded to? This would be interesting to test using something like postman: https://learning.postman.com/docs/sending-requests/requests/

Unfortunately I think you can just craft a POST request from anywhere like this, though it might be possible to set rules in the Google Cloud console to have the backend component only accept requests from the frontend component. It's something that I'll try to look into.


Getting an error when running against my template

I see the following with my template - my suspicion is that it is the not handling the trigger section properly.

Serverless: Excluding development dependencies...
Serverless: Export:
Serverless: Exporting resources
Serverless: Exporting resource: LogExpiryLambdaFunction
Serverless: Exporting resource: LogExpiry
Serverless: Exporting resource: AWSLambdaVPCAccessExecutionRole
Serverless: Exporting resource: TAPRole
Serverless: Exporting resource: TAPCustomersTable
Serverless: Exporting resource: TAPAlarmTopic
Serverless: Exporting resource: EventSourceMappingCreate
Serverless: Exporting resource: EventSourceMappingEmail
Serverless: Exporting resource: EventSourceMappingAlert
Serverless: Exporting resource: LambdaExecSecurityGroup
Serverless: Exporting outputs
Serverless: Exporting parameters
Serverless: Exporting conditions
Serverless: Exporting functions
Serverless: Exporting function: create as Create
Serverless: Exporting function: list as List
Serverless: Exporting function: get as Get
Serverless: Exporting function: getLoginURL as GetLoginURL
Serverless: Exporting function: getRandomLogin as GetRandomLogin
Serverless: Exporting function: update as Update
Serverless: Exporting function: delete as Delete
Serverless: Exporting function: triggerCreate as TriggerCreate

  Type Error ---------------------------------------------

  Cannot read property 'enabled' of null

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Stack Trace --------------------------------------------

TypeError: Cannot read property 'enabled' of null
    at FunctionConverter.isEventEnabled (/Users/robweaver/Sites/master/SharedDeployScripts/AWS/serverless/TrialAccountProvisionService/node_modules/serverless-sam/lib/FunctionConverter.js:120:18)
    at Object.keys.forEach (/Users/robweaver/Sites/master/SharedDeployScripts/AWS/serverless/TrialAccountProvisionService/node_modules/serverless-sam/lib/FunctionConverter.js:93:21)
    at Array.forEach (<anonymous>)
    at serverlessFunction.events.forEach (/Users/robweaver/Sites/master/SharedDeployScripts/AWS/serverless/TrialAccountProvisionService/node_modules/serverless-sam/lib/FunctionConverter.js:91:33)
    at Array.forEach (<anonymous>)
    at FunctionConverter.serverlessFunctionToSam (/Users/robweaver/Sites/master/SharedDeployScripts/AWS/serverless/TrialAccountProvisionService/node_modules/serverless-sam/lib/FunctionConverter.js:85:33)
    at allFunctions.forEach (/Users/robweaver/Sites/master/SharedDeployScripts/AWS/serverless/TrialAccountProvisionService/node_modules/serverless-sam/lib/SamGenerator.js:119:32)
    at Array.forEach (<anonymous>)
    at SamGenerator.readFunctions (/Users/robweaver/Sites/master/SharedDeployScripts/AWS/serverless/TrialAccountProvisionService/node_modules/serverless-sam/lib/SamGenerator.js:109:20)
    at SamGenerator.generate (/Users/robweaver/Sites/master/SharedDeployScripts/AWS/serverless/TrialAccountProvisionService/node_modules/serverless-sam/lib/SamGenerator.js:58:10)
    at BbPromise (/Users/robweaver/Sites/master/SharedDeployScripts/AWS/serverless/TrialAccountProvisionService/node_modules/serverless-sam/index.js:206:46)
    at SamPlugin.exportSam (/Users/robweaver/Sites/master/SharedDeployScripts/AWS/serverless/TrialAccountProvisionService/node_modules/serverless-sam/index.js:203:12)
From previous event:
    at PluginManager.invoke (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:372:22)
    at PluginManager.run (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:403:17)
    at variables.populateService.then (/usr/local/lib/node_modules/serverless/lib/Serverless.js:102:33)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)
From previous event:
    at Serverless.run (/usr/local/lib/node_modules/serverless/lib/Serverless.js:89:74)
    at serverless.init.then (/usr/local/lib/node_modules/serverless/bin/serverless:42:50)
    at <anonymous>

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Forums:        forum.serverless.com
     Chat:          gitter.im/serverless/serverless

  Your Environment Information -----------------------------
     OS:                     darwin
     Node Version:           8.9.1
     Serverless Version:     1.26.0

This is the first place I see 'enabled' in my serverless.yml:
 # Event that is triggered by the table log stream
  # Looks for events that are creating an account and starts that process
  triggerCreate:
    handler: users/triggerCreate.triggerCreate
    events:
          - stream:
            # Get the stream to trigger on ...
            Fn::Join:
              - ""
              - - "arn:aws:dynamodb:${self:custom.region}::table/"
                - "Ref" : "TAPCustomersTable"
                - "/stream/"

#  # Event that is triggered by the table log stream
#  # Looks for events that are creating an account and starts that process
#  triggerCloningComplete:
#    handler: users/triggerCloningComplete.triggerCloningComplete
#    events:
#          - stream:
#            # Get the stream to trigger on ...
#            Fn::Join:
#              - ""
#              - - "arn:aws:dynamodb:${self:custom.region}::table/"
#                - "Ref" : "TAPCustomersTable"
#                - "/stream/"

  # The function to check created items
  # This is a cron that looks at all records and tries to finish the cloning
  # process that was started by triggerCreate (in case that times out)
  cronCreateCheck:
    handler: users/cronCreateCheck.cronCreateCheck
    events:
      # Schedule to run every 5 minutes
      - schedule: rate(1 minute)
        name: check-creation
        description: 'Check for creations every minute to update when cloning is complete'
        enabled: true

I had this same issue, I fixed it by indenting the attributes for the schedule event. From your example, it would look like this.
cronCreateCheck:
    handler: users/cronCreateCheck.cronCreateCheck
    events:
      # Schedule to run every 5 minutes
      - schedule: rate(1 minute)
          name: check-creation
          description: 'Check for creations every minute to update when cloning is complete'
          enabled: true


Disconnecting after 1 minute

I'm having the same issue as:
https://stackoverflow.com/questions/48744861/php-nats-client-disconnects-after-some-idle-time

After connecting, receiving few messages and having some 30 secs idle time, it gets disconnect itself without any interruption. However my Node.js client is working good with the same NATS server.

Not sure what I'm missing.

@timsmid could you create a fork with all your PR merged and added to composer registry? Since there is no active maintaining of the library

@timsmid could you create a fork with all your PR merged and added to composer registry? Since there is no active maintaining of the library

You will probably be better of setting up a repository / package yourself. Unfortunately, I have currently no intent to actively maintain or support this library. My fork with the applied timeout changes is publicly available at https://github.com/timsmid/phpnats/tree/develop.
If you have any further questions though, feel free to ask.

@timsmid how to pull your repository with composer?

@timsmid how to pull your repository with composer?

You might be able to reference it directly in your composer.json file, although I am not entirely sure about the syntax. You can probably use the repositories key as described in the Composer documentation (https://getcomposer.org/doc/05-repositories.md).
Another alternative is forking my repository and creating a Packagist package yourself. Then you can use your own package in your composer.json file. That would probably be the sanest route, as you would be in full control of the code.

use like this:
$client->connect(-1);

use like this: $client->connect(-1);

thanks!
seems, it works, but it is slightly ambiguous to permanently write this in queue consumers, right?


NexCollector/pom.xml does not have org.eclipse.paho dependency

I believe the library are imported to developer eclipse so missed to put it to pom.xml
The module failed without the library.

We merged your PR. Thank you!


TypeError: $cordovaSocialSharing.shareViaInstagram is not a function

Hi, I'm using ionic + cordova and the plugin is working perfectly except for shareViaInstagram which gives me the error in the title.
https://github.com/EddyVerbruggen/SocialSharing-PhoneGap-Plugin/blob/573e409/README.md makes no mention of this function... but this does:
https://github.com/EddyVerbruggen/SocialSharing-PhoneGap-Plugin
I have version cordova-plugin-x-socialsharing 5.0.7 "SocialSharing" installed.
Thanks

which platform are you having issue with?

@jazzwhistle is this actually supported according to ngCordova?

Hi Eddy, I assumed it was because I found it here initially: http://ngcordova.com/docs/plugins/socialSharing/
The shareViaInstagram function is not mentioned there though...
Thanks

That's no big deal really... more importantly I keep getting random SIGBART crashes on iOS in
[[self getTopMostViewController] presentViewController:activityVC animated:YES completion:nil];


[WiP] PR: Greatly simplify and clarify Github PR template

Pull Request Checklist

[x] Read and followed this repo's Contributing Guidelines
[x] Based this PR on the latest version of the correct branch (master or 3.x)
[x] Followed PEP 8 code style
[x] Ensured this pull request hasn't eliminated unrelated blank lines/spaces,
modified the spyder/defaults directory, or added new icons/assets
[x] Described the changes and the motivation for them below
[x] Noted what issue(s) this pull request resolves, creating one if needed
[x] Included a screenshot, if this PR makes any visible changes to the UI

Developer Certificate of Origin Affirmation
By submitting this Pull Request or typing my name below, I affirm the
Developer Certificate of Origin
with respect to both the content of the contribution itself and this post,
and understand I am releasing it under Spyder's MIT (Expat) license.

Description of Changes

Per the suggestions of @jnsebgosselin , I've greatly simplified the PR template, reducing its total size by ~40% (by character count).

Split the PR checklist into two parts:

One with a condensed version of the basics that apply to every PR on submission (Contrib Guide, correct branch, PEP8/PEP 257, no-nos) and make that all just one checkbox,
One with the other three (Docstrings, Unit tests, screenshot) as individual bullets that can be removed as necessary

Cut down excess text throughout the rest of the template

Issue(s) Resolved

Fixes #8270

I think the checkboxes in the  "Description of changes" section should be written as a series of commands, like:
- [ ] Write at least one-line docstrings (for any new functions).
- [ ] Add unit test(s) covering the changes (if testable)
- [ ] Include a screenshot (if affecting the UI)

But I'm not sure the "Write at least one-line docstings (for any new functions)" has its place there. I think this is included as part of the "we need to follow the PEP 257 Guidelines" specification. It is in the same league as the 4-space indent specification IMO.

By submitting this Pull Request or typing my name below, I affirm the
[Developer Certificate of Origin](https://developercertificate.org/)
with respect to both the content of the contribution itself and this post,
and understand I am releasing it under Spyder's MIT (Expat) license.

<!--- TYPE YOUR GITHUB USERNAME AFTER THE FOLLOWING STATEMENT ---!>
I certify the above statement is true and correct:

This confusing to me. It says By submitting this Pull Request **or** typing my name below. So, why are we requested to write our name below, if this can be done simply by submitting the PR? Would it be possible to replace that by :
By submitting this Pull Request, I affirm the
[Developer Certificate of Origin](https://developercertificate.org/)
with respect to both the content of the contribution itself and this post,
and understand I am releasing it under Spyder's MIT (Expat) license.

Or, regarding the https://github.com/spyder-ide/spyder/pull/8272#issuecomment-440106090 I made above, instead of writing down our names, would it be possible to add this in a checkbox instead? I think in that case, that would be very meaningful.

Also, @CAM-Gerlach, you are free to disagree and argue with my propositions. I do not mean to impose my vision here.

So, I would replace that by a simple sentence written as a MD comment.

Okay, done.

I think the checkboxes in the "Description of changes" section should be written as a series of commands

Okay, but is there a particular reason/justification for that, other than just the habit of writing commit messages that way? Neither are all that decisive, but I see two conceptual reasons why past tense makes sense here:

Given they are directly under the heading "description of changes", in the past tense they are in same form as one would conventionally describe other things accomplished in the PR, like "I've greatly simplified the PR template" whereas they would sound out of place there as imperative
In the past tense, they represent things that have been done, which is what they are supposed to mean if checked and what people are checking to assert, while in the imperative they represent commands—they also are in this case, but it comes across softer and less demanding to avoid the imperative tense where not necessary.

I think this is included as part of the "we need to follow the PEP 257 Guidelines" specification.

That was my initial thinking too, but the reason I put it there was that it fell under the "optional things that might not be included in the initial submission", and the fact that PEP 257 only says that public functions and methods "should" have docstrings, as well as it being more specific about the nature of docstrings to include. I can remove it since that's not a very strong justification, but that leaves us with only two list items which looks a little silly.

Okay, but is there a particular reason/justification for that, other than just the habit of writing commit messages that way? Neither are all that decisive, but I see two conceptual reasons why past tense makes sense here:
* Given they are directly under the heading "description of changes", in the past tense they are in same form as one would conventionally describe other things accomplished in the PR, like "I've greatly simplified the PR template" whereas they would sound out of place there as imperative

Ok I understand. I was seeing this more like a "TODO" list. Like this PR for example https://github.com/spyder-ide/spyder/pull/8192.

* In the past tense, they represent things that have been done, which is what they are supposed to mean if checked and what people are checking to assert, while in the imperative they represent commands—they also are in this case, but it comes across softer and less demanding to avoid the imperative tense where not necessary.

This makes sense too. I was not seeing this as a list of things we are asking contributors to do, but more as a tool for the contributors to use to structure and document the progress in their PR.
So basically, I think both options as correct. It depends if you see the PR template as a tool for the developers or as a tool for guiding first time contributors.

Also, @CAM-Gerlach, you are free to disagree and argue with my propositions. I do not mean to impose my vision here.

You do know whom you're asking that of, right? :P If there is one thing I am infamous on this repo for, it is writing long and rambling replies disagreeing and arguing with even the most trivial of propositions.

So, why are we requested to write our name below, if this can be done simply by submitting the PR?

That's a good point, and one I've considered at length multiple times. Singing it positively affirms people have actually seen, read and agree to the DCO, both making sure they understand what they agreeing to and they it is clear that they are actually agreeing to it in an enforceable way. Its the reason almost all websitse or installer with a license/ToS that you have to agree to at some point makes you actually click "Agree" or check a box rather than just saying "by creating an account" and leaving it at that, or even pre-checking the box/selecting "Agree" by default, at least whenever they can. However, including the "or submitting the PR" covers us in case they don't, and we forget to ask them to, or they try to sneakily remove it and claim that means they don't agree anymore. By including both, we're covered in all reasonable scenarios.

would it be possible to add this in a checkbox instead? I think in that case, that would be very meaningful.

I considered that, but a checkbox is much more easily "mutable" and less ambiguous than a written name, which unlike a checkbox requires a specific and deliberate sequence of actions that cannot be construed to be an accident. Furthermore, typing one's name is considered to be legally equivalent to "signing" something, in this case the DCO, while there is no such strong legal precedant behind checking a Github checkbox. If we're going to include this, its worth spending an extra second or two and doing it right (of course, the best way would be having all contributors sign their commits with git commit -s, but if they forgot to or didn't know to even one time, they would have to rebase their entire PR and resign every commit that they didn't, which is a comparatively huge burden especially for newer and less experienced contributors).

So basically, I think both options as correct. It depends if you see the PR template as a tool for the developers or as a tool for guiding first time contributors.

Indeed, two ways of looking at the same thing. It certainly can be seen as a todo list. Ultimately both reasons were pretty weak, the first based on the context of the heading they were under, and the second optimizing to be a little more gentle on new contributors while not taking anything really away from current ones.

Hey @jnsebgosselin , are there more changes you'd like to make, or do you still need time to look over it?

@jnsebgosselin Thanks for all the catches; my brain was clearly turned off last time missing all that, since even I saw it right away opening up the file today.


contabo-client: Test and Fix the reinstall method

I wrote the reinstall method but I couldn't test it.
Most probably it is not working.

And then when you reinstall an instance and then try to access it, are you encountering the following issue:

If you encounter this issue, you can run the following command.
sudo ssh-keygen -f "/root/.ssh/known_hosts" -R <IP_ADDRESS>

This is because the SSH key gets regenerated whenever we reinstall an instance.


Separate language strings. Fixes #111.

I've separated the language strings to defaults.js, so that they are exposed as yasqe.options.language and can be thus overwritten by different locale in the YASQE constructor. I've also fixed a couple of typos, such as "Fetchting autocompletions" in autocompletes.utils.js.
This is just a proposal of how localization can be introduced in YASQE. Please advise if there is another preferred way to do so.

I got the feeling this might be a bigger issue than expected if done right.

a locale setting (default 'en', or null/undefined for using the browser's locale)
A way to add the translated string to the options (e.g. options.language.en) object (either via ajax request, or as part of the settings)
Adding a function for getting all ui-related strings. Something like yasqe._('This line is invalid. Expected:'), where the english translation is the key we'd use for other translations (probably wont cover all use cases/languages, but it'll probably suffice)
Applying the locale setting to the YASR output plugins. I see most plugins have a localization system in place. The implementation is not consistent between these plugins though, so this requires some tweaking as well
(optional): check whether a locale is supported by a plugin, and show in english if it's not.

This isnt on my priority list atm as there are a few other YASGUI issues I need to take a stab at. But, if you'd like to take this up, that'd be much appreciated.

Closing due to inactivity. Still open to the idea though, but just not at the top of the todo list atm


Fix JoinEventStream behaviour and add tests

Depends on #17

Changes Unknown when pulling e58fac4e02e6ed87402f03b5e6767dda13c6e982 on join-eventstream-tests into ** on master**.

Changes Unknown when pulling 9c1f916c884cc66302023f01b01a9999b2a2ae2a on join-eventstream-tests into ** on master**.

Changes Unknown when pulling 4bac8d73c38accc7e6d7c016c557644a511d36da on join-eventstream-tests into ** on master**.

Changes Unknown when pulling f8fdcd20dfda742e68f41010ab16ccc6de8379c7 on join-eventstream-tests into ** on master**.


[Bug] Appsmith can never delete a datasource

There is an endless loop of users not being able to delete datasources that are referenced by APIs, and data sources not being visible when they have no references. This means that once a datasource is created, it stays in our system forever. Users will unknowingly bloat the size of our database for no reason because of it.

@nidhi-nair thanks for pointing this out. This is certainly an issue. We've deprioritized this for now because we'll have a holistic solution once we implement global actions

@Nikhil-Nandagopal How will global actions solve this?
In this case, don't we just need to display all the datasources in an organization and allow users to manage them?

@mohanarpit sorry you're right, we need an org level display

Will be closed along with https://app.zenhub.com/workspaces/appsmith-actions-pod-603dd87bd4dff90011242dc9/issues/appsmithorg/appsmith/4567

@arunvjn How are these 2 issues related?

@Nikhil-Nandagopal We provide a list of datasources in API Editor from where the users can navigate to the datasource form. This flow allows a user to finally delete a datasource. Here is the deploy preview for you reference. https://deploy-preview-4587--appsmith-editor-ce.netlify.app/

We now have a way to delete a data source. So closing this action.

Correction: we have fixed this only for API data sources and not for DB query data sources. Open a new issue - https://github.com/appsmithorg/appsmith/issues/5027


Upgrading is messy, confusing, and a bit scary

RC2 Darwin
I imported the consensus and wallet files before starting the RC2.
It hung for a few minutes before managing to boot into the main screen. Now it's been stuck on "Loading Sia". I guess I'll just wait a bit longer? Peeking inside the Sia folder, I can tell thing are happening as some files' last modified timestamps match the current time. I'm assuming things are going in the right direction and the program is not just stuck in a loop... Or is it? No way to tell for sure.
There needs to be more feedback for the user. I can't determine whether Sia has crashed or what is happening. In-app upgrading is also needed, messing with wallets and other files is not nice and potentially a bit dangerous if you're careless or easily distracted.

It's slowly calculating the usual folders and files. transactionpool, miner, gateway, host, renter etc... Not sure why so long since I'm not doing any renting/mining/farming. Right now it looks like it's going through the whole blockchain and refreshing the hostdb as it reads the contracts. Perhaps I should have moved the rest of the folders/files as well?
I'm even wondering if this might have an impact on uptime calculations as the whole process probably took 30/40 minutes. If this is going to be the case for every upgrade, doesn't that leave significantly less time for other kinds of planned and unplanned downtime?

Yeah, siad can take a long time to rescan an incomplete data-set.  The UI shows "Loading..." when siad has been started but is not finished loading modules, "Welcome Back" when it finishes, and an error if it fails.  There's a planned upgrade to load the API module first, which means the UI can provide more granular feedback on this process.
As for upgrading, the plan is to use a common, OS-specific, data directory so users can just replace their binary and not have to worry about meddling with Sia data.  That issue is here: https://github.com/NebulousLabs/Sia-UI/issues/243 .  It should be implemented for 1.0.  In-app upgrades are much harder, but also planned https://github.com/NebulousLabs/Sia-UI/issues/255.
Thanks again for your feedback.

Thank you for listening!
I remember the days when Sia used the OS specific directory. Some people did lose their wallets that way, you have to be very careful, especially about multiple clients launching in parallel. Mist (Ethereum) seems to handle this properly, so I'm sure there's a good/safe way to do it.
Perhaps you could even have Sia check for and pull the update from a signed/verified address on the Sia network, so you don't have to deal with a "centralised" (boo!) process of querying github and whatnot.

What is the status on this issue? Is the upgrade complete?
Should we consider rescan progress / loading progress to be a part of this issue, or should we open up a separate issue?

Users upgrading from 1.0.0 do not have to manually move their sia data.  The new version of Sia will load their data from the OS-specific data directory, meaning the upgrade process is as simple as launching the new binary.  Rescanning should not be an issue for users upgrading from 1.0.0+.
Closing this issue.


Create a unified environment with build matrices for different compilers

Is your feature request related to a problem? Please describe.
We want a unified environment that covers all application and that can be installed easily for multiple compilers.
Describe the solution you'd like
Scan the various virtual environment packages and combine those that are needed. Remove the others. Use build matrices for compilers to install the unified environment for multiple compilers in a single directory tree.
We put together a list of packages and versions in https://docs.google.com/spreadsheets/d/1j31C2WrG3hNAQAKdey8CbOx9eek_kGMsUVuHeBUhamg/edit?usp=sharing, based on the four applications global-workflow, ufs-weather-model, ufs-srw-app, skylab.
Additional context
The spack stack setup-meta-modules script does handle multiple compiler+MPI combinations in one environment, at least for lmod modules. Not sure about tcl modules, but the sites using those (Gaea, Narwhal, Ubuntu 20, Red Hat 8) typically use only one compiler.

Completed!


Add support to pause a Flow Execution by API

We have to follow the https://azkaban.github.io/azkaban/docs/latest/#api-pause-a-flow-execution

Can I have this one?

Yeah!

I just finished it and made a pull request. #60


Fix the just commands and update the README

just test is fast and works perfectly 😎
just load-dat is mentioned in the README, but doesn't seem to exist
just docs isn't working

@MrPowers mind if i grab this?


user name/password not work

Hi!
I tried this library in my Lwip stm32f4 webserver project, it works fine but if add user name/password, then not work, I think need modification for making it work with example mentioned below
"http://admin:admin@<IP_ADDRESS>:8989/path/to/test?query=yes&param1=no#frag=1"

Hello, the library does not support credentials in the URL for now, but let me fix it and it will probably be done by the weekend :-D Please, let me know if there any more problems or improvements :+1:

Thanks for your quick response, I needed it today, modified it myself and it works well now,
have added comment where I added my code.
`int
yuarel_parse(struct yuarel *url, char *u)
{
char *start = u;
/added by farrukh*/
char myPtr;
/*********************/
if (NULL == url || NULL == u)
	return -1;

memset(url, 0, sizeof (struct yuarel));

/* relative URL, parse scheme and hostname */
if (*u != '/') {
	/* Scheme */
	url->scheme = u;
	u = strchr(u, ':');
	if (u == NULL || url->scheme == u)
		return -1;
	*(u++) = '\0'; // Replace ':' with NULL

	/* Forward to after // */
	while (*u == '/') u++;

	/* Host */
	if (*u == '\0')
		return -1;

/edited by farrukh*/
myPtr=strchr(u, '@');
if(myPtr==0x00)
{
url->host = u;
start = u;
}
else
{
*myPtr=0x00;
url->namePassword=u;
              url->host = myPtr+1;
              start = myPtr+1;
            }

/**********************/
}`

Great :-) I can fix the code so that it conforms to the existing code style and :) Thank you :+1:

Any chance to have this merged & resolved? I'd prefer to use this library as git submodule without doing my own fork.

Sorry, I have been busy and forgot about it :-( I will look at it tonight
:-)
Best regards
Jack
On Tue, 18 Apr 2017 11:57 Jarek Zgoda<EMAIL_ADDRESS>wrote:

Any chance to have this merged & resolved? I'd prefer to use this library
as git submodule without doing my own fork.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/jacketizer/libyuarel/issues/3#issuecomment-294757298,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGL2t9IexzgXXLSDSIw5WRIr-p1E1w_Qks5rxIkBgaJpZM4LS0yx
.

Sorry for the delay, it is now fixed on master :-)


GNAudio.Jabradirect version 5.4.33519

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Package already added. manifests/j/Jabra/Direct
#14621


password character escape

If you have a password with "!" or other character this is not working. How about you escape the $DBPASSWORD inside the backtick?

Hey @Morpheus-ro ,
Can you please try this?
Open the .sh file
Find this:
-p$DBPASSWORD

Change as:
-p "$DBPASSWORD"

And try again.
Also please let me know whether this works.

hei, thank you for the reply, the issue is not doing anything. I posted around so solve this issue -> http://unix.stackexchange.com/questions/349521/bash-escape-exclamation-character-inside-variable-with-backtick?noredirect=1#comment618641_349521 and here http://stackoverflow.com/questions/42628841/bash-escape-exclamation-character-inside-variable-with-backtick

this is the modified line
databases=mysql -h$DBHOST -u$DBUSER -p "$DBPASSWORD" -e "SHOW DATABASES;" | tr -d "| " | grep -v Database``

Hello again,
So can you confirm, changing -p$DBPASSWORD to -p "$DBPASSWORD" solves it for the time being ? I'll double quote the variables in mysql string on that case.
I checked those stackexchange links, I'll try to implement those feature soon, however, while the query is running even with those mktemp trick I can see the location of temp file, cat it and get the password through it. So no difference between ps trick and that. Please correct me if I'm wrong.

Hey,
No, it is not solving the issue. I also tied -p '$DBPASSWORD' and is the tame result. Inside the backticks is the issue, I don't know hot to escape inside them. I tried also:

-p "'$DBPASSWORD'"
-p \\"'$DBPASSWORD\\"
-p \\"'$DBPASSWORD'\\"

and nothing. is the same result, not working.
Regarding the security of the script, for me is not mandatory because I am using private networks and limited access to instances so that is not my primary concern now. The objective is to be able to export the tables from the DB with any kind of passwords and this is failing now.

@Ardakilic Your documentation is slightly incorrect which is probably causing the issue for @Morpheus-ro and @Morpheus-ro you are not describing exactly what you are doing and have assumed there is a problem with the script. Let me explain.
You have given 2 examples under the section On The Fly Configuration the first example is incorrect because the password is not quoted.
@Morpheus-ro You do not show your command line (neither here nor at stackexchange)
Bug in the script : lines 170 and 174 should use double quotes around any variable that might contain characters which interfere with bash.
Just a comment, @Ardakilic instead of using the back-tick syntax for setting a variable to output of command, I would use $( ) syntax, it's easier to read - although it doesn't make any difference.
I have created a pull request, which fixes this issue.

@techsailor thank you for the PR!
Also, backtick is only used to define the backup name, anywhere else you're suggesting ?

Closing this issue as a result of last PR. Yet, it's still open for discussion.


Report from a user: Onboarding screen skips and then is unusable

It appears to do it on the 4th screen of onboarding
https://www.dropbox.com/s/jeoiq5n7oc8x5sc/Textile.mp4?dl=0

That's an old version of the app that contained that bug. It is fixed in current versions of the app.


[Themes] Only a subset of components apply fontFamily

https://github.com/callemall/material-ui/search?utf8=✓&q=fontFamily
Button:

Checkbox:

A checkbox wouldn't need a font-family since there's no text in that type of html element, where a button will have text inside of it.

 Deal? :wink:

Fixed by now.


null values in http headers are allowed.

Hi Tom,
We are using wiremock extensively.  Our tests were working fine till 1.58. After upgrading to 2.1.7 many tests failed.
I am able to narrow down the root cause.
If I try following URL on 1.58 it works fine. But with 2.1.7 it throws 500 internal server error.
curl -vv -H"Hello;" http://localhost:8080/__admin/
It breaks when http header has a key with null value.
As per following document null values are allowed in http headers. Key cannot be null, but values can be null.
https://docs.oracle.com/javase/8/docs/jre/api/net/httpserver/spec/com/sun/net/httpserver/Headers.html
"However, null keys will never will be present in HTTP request headers, and will not be output/sent in response headers. Null values can be represented as either a null entry for the key (i.e. the list is null) or where the key has a list, but one (or more) of the list's values is null. Null values are output as a header line containing the key but no associated value."
Here is my pull request with relevant changes.
I've removed null value check and corresponding unit test case.
Thanks,
-Shailesh

Fixed in 3ba037ce9b8af310e62176ee38cb4c2e8957072b

Thanks a lot.


i18n out of the box

If we could have content like this,
content/
    |- my-cool-blog/
        |- index.md
        |- index_zh-Hans.md
        |- index_hi.md

so if a user prefers Mandarin, he will get content from index_zh-Hans.md (zh-CN is the code of Chinese Simplified)

Guess this is a great solution, but we will many files with that

yeah fair point, Have you seen any project handling i18n? I am a little clueless about this right now. Are there suppose to be two different websites for two different languages? or just the same website where you switch content with JavaScript?

No, no, same website but separating translations into multiple files and load them on demand

oh yes makes sense

oh yeah! like what you show on the top,
but need to add the code for each language in the documentation

There are two possibilities we can think of.

The site can have subdomains based on the language. For instance, the React Documentation's Hindi variant has hi.reactjs.org or Spanish variant has es.reactjs.org.
When user requests for a translated page, it can routed to respective language sub pages as can be seen at overreacted.io. For example, a post has URL of https://overreacted.io/goodbye-clean-code & Spanish version of the post has URL of https://overreacted.io/es/goodbye-clean-code. This logic is probably handled by a Gatsby plugin named gatsby-plugin-i18n.

References

Repository of overreacted.io
Repository of gatsby-plugin-i18n

Yes 2nd method seems like a better option. Thank you for the help @kasipavankumar :D


Add additional pre-commit hooks

Codecov Report

Merging #181 (91f8e34) into main (82d4b0e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #181   +/-   ##
=======================================
  Coverage   91.82%   91.82%
=======================================
  Files          10       10
  Lines         832      832
=======================================
  Hits          764      764
  Misses         68       68

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 82d4b0e...91f8e34. Read the comment docs.


As a user I'd like to explore resources that are linked to the Open Beelden collection

When the search API is ready for it (see issue 59), the user must be able to explore resources as described in the acceptance criteria:
Acceptance criteria
After searching for something on the media suite search page and subsequently selecting a result to be shown in the resource viewer:

[ ] User should select one of the detected LD resources (from the resource viewer) and jump to DIVE
[ ] User should be able to visualise the same resource in the DIVE UI, and be able to navigate to other resources which are related to it.
[ ] User should be able to select another resource on DIVE UI and jump back to the resource viewer.

Note: currently the grlc plugin is not working for Python 3, so that has to be fixed first in the search API...


Fix postgresql addon for Xenial

Adds convenience methods to data top determine what type of system this is running on
Use systemd on Xenial, Upstart on previous Ubuntus
Do not run addon on non-linux

Problem it tries to resolve: Get the postgres you specify, rather than always 9.6: https://travis-ci.org/joepvd/travis-experiment/jobs/388177347#L443
This is how it looks like on staging: https://staging.travis-ci.org/joepvd/travis-staging-test/builds/722684


Corruption on some UI elements

Bevy version
v0.10.0 (289fd1d0f2353353f565989a2296ed1b442e00bc)
Relevant system information
Rust Stable
cargo 1.67.1 (8ecd4f20a 2023-01-10)
SystemInfo { os: "Windows 11 Pro", kernel: "22621", cpu: "AMD Ryzen 5 5600X 6-Core Processor", core_count: "6", memory: "15.9 GiB" }
AdapterInfo { name: "AMD Radeon RX 6750 XT", vendor: 4098, device: 29663, device_type: DiscreteGpu, driver: "AMD proprietary driver", driver_info: "23.2.2 (AMD proprietary shader compiler)", backend: Vulkan }

What you did
Ran some examples like: contributors, blend_modes or game_menu
What went wrong
Some UI elements have some sort of texture corruption?
Additional information

In the contributors example it's happening all the time and the corruption is flickering/changing every frame.
In the blend_modes example I have to rotate the camera around to start seeing some corruption and its flickering but without changing the camera angle it does not change.
But could not reproduce it in some examples like in tonemapping

Still an issue in 0.10.1 (1c5c94715cb17cda5ae209eef12a938501de90b5) (also ran cargo update)

I re-ran the examples with DX12 and the issue did not appear. It seems like the issue is related to Vulkan.

I'm having the same issue using 0.10.1.
AdapterInfo { name: "AMD Radeon RX 5600 XT", vendor: 4098, device: 29471, device_type: DiscreteGpu, driver: "AMD proprietary driver", driver_info: "23.4.2 (AMD proprietary shader compiler)", backend: Vulkan }

I re-ran the examples with DX12 and the issue did not appear. It seems like the issue is related to Vulkan.

How do you hardcode the engine to use DX12? I'm running into the same issue in the mentioned issue.

I re-ran the examples with DX12 and the issue did not appear. It seems like the issue is related to Vulkan.

How do you hardcode the engine to use DX12? I'm running into the same issue in the mentioned issue.

When you're adding the default plugins, do this
.add_plugins(
    DefaultPlugins
        .set(RenderPlugin {
            wgpu_settings: bevy::render::settings::WgpuSettings {
                backends: Some(Backends::DX12),
                    ..default()
                }
            })
)

I can't reproduce this on AMD+Windows 11 on either bevy 0.10.1 or bevy main (10f5c9206847ae01b8dc833c2680562e7bd46664).
 SystemInfo { os: "Windows 11 Pro", kernel: "22621", cpu: "AMD Ryzen 9 5900X 12-Core Processor", core_count: "12", memory: "31.9 GiB" }
AdapterInfo { name: "AMD Radeon RX 6800 XT", vendor: 4098, device: 29631, device_type: DiscreteGpu, driver: "AMD proprietary driver", driver_info: "23.5.2 (AMD proprietary shader compiler)", backend: Vulkan }

With the help of @Elabajaba I installed a bunch of thinks that eventually made it better. But I can't say I understand what the exact fix was.
https://github.com/GPUOpen-Drivers/AMDVLK/releases
https://github.com/lutris/docs/blob/master/InstallingDrivers.md
What actually did the trrick in the end was setting the environment variable AMD_VULKAN_ICD=RADV

reopening as #9169 was reverted in #9237

The same issue is happening to me with Bevy 0.11.2 on Windows 11 22H2 with an RX 6700 (non XT), using DX12 fixes it.
AdapterInfo { name: "AMD Radeon RX 6700", vendor: 4098, device: 29663, device_type: DiscreteGpu, driver: "", driver_info: "", backend: Vulkan}

Also experiencing this with my lovely font:

OS: Windows 10 IoT Enterprise LTSC, 21H2 (19044.5131)
Bevy version: 0.11.2
rustc version: rustc 1.84.0-nightly (705cfe0e9 2024-11-01)
GPU: RX 6750 XT
Rendering backend: Vulkan

I misread Bevy's version number, sorry! I'm currently on 0.14.2 and have updated my comment accordingly.

I misread Bevy's version number, sorry! I'm currently on 0.14.2 and have updated my comment accordingly.

I see, thank you! Does your issue persist if you force DX12 as a backend?

I have same issue here I supposed.
uname -a
Linux Gentoo 6.12.1-gentoo #3 SMP PREEMPT_RT Sun Nov 24 11:14:43 CST 2024 x86_64 AMD Ryzen 9 5900HX with Radeon Graphics AuthenticAMD GNU/Linux

bevy version: git log -1
commit 8e284984aa9b6c556b9fcdfec0d7f7df690ad9ac

 rustc --version
rustc 1.82.0 (f6e511eec 2024-10-15)

INFO bevy_render::renderer: AdapterInfo { name: "AMD Radeon RX 6800M", vendor: 4098, device: 29663, device_type: DiscreteGpu, driver: "AMD proprietary driver", driver_info: "(AMD proprietary shader compiler)", backend: Vulkan }

And the crash only happen at the bottom part of the window, unless the window is too small, at when will it spread to all window.

Tried game_menu from examples, the corruption only happens when the window is too small.


Make noise when a build machine's job is taking longer than 1 hour

We can learn about current build jobs on our machines by fetching  http://build.servo.org/json/slaves?as_text=1. One example shows that sevo-linux-cross3 has been running for more than 2 hours: https://gist.github.com/jdm/ae1be5ef10ef308f9fdc93856a0515e0 . We should query this information every 30 minutes and squawk loudly if any build machine is stuck.

Hello, @jdm ! Can I take over this issue?

Please do! Ask questions if anything is unclear!

@carlosmcgregor Have you made any progress with this?

Thank you for your patience! I have my test IRC server running and I have been playing around with crowbot commands. I am also reviewing its code so that I do not add unnecessary lines. I hope to be done by the end of the weekend, if that's alright.

@jdm Just making sure: the alert needs to go off for builds that have past their ETA.

@carlosmcgregor I would say if a build is >30 minutes past the ETA, it would be worth alerting about the fact.

@jdm I am pretty much done, but I am missing the squawking part. Could you please hint me in the direction of how to send sounds via IRC? I read about the /sound command, but I could not find a resource talking about how to enact this via node-irc.

Sorry, by squawk I just meant send a message to the channel that gets attention.

Oh okay! Sorry, I'm new to crowbot so I'm still getting used to the terms used here. Would this channel be #servo? Also, is it necessary for me to add test cases?
Sorry if I'm asking too many questions!

You can follow the example of this code which uses the first channel from the configuration file as the target. And a test case would be nice to have, if it doesn't require too many awkward internal changes to support. This project uses mocha, and you can find the tests in tests/server.test.js, and run them with npm test.

Thank you! That's the code I was using. I will be making a pull request right now.

This was fixed by #76 and #79.


optimize:add SQL exception prompt not supported by AT mode

[x] I have registered the PR changes.

Ⅰ. Describe what this PR did
添加AT模式不支持的SQL语句异常提示
Ⅱ. Does this pull request fix one issue?

fixes #4324
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #4336 (45466ad) into develop (d87e8c9) will increase coverage by 0.07%.
The diff coverage is 62.68%.

:exclamation: Current head 45466ad differs from pull request most recent head df5e13d. Consider uploading reports for the commit df5e13d to get more accurate results

@@              Coverage Diff              @@
##             develop    #4336      +/-   ##
=============================================
+ Coverage      48.52%   48.59%   +0.07%
- Complexity      3830     3855      +25
=============================================
  Files            728      728
  Lines          24472    24526      +54
  Branches        3027     3009      -18
=============================================
+ Hits           11875    11919      +44
+ Misses         11330    11299      -31
- Partials        1267     1308      +41

Impacted Files
Coverage Δ

...rser/druid/mysql/MySQLOperateRecognizerHolder.java
50.00% <53.33%> (+7.14%)
:arrow_up:

...er/druid/oracle/OracleOperateRecognizerHolder.java
50.00% <53.33%> (+50.00%)
:arrow_up:

.../postgresql/PostgresqlOperateRecognizerHolder.java
52.63% <53.33%> (+52.63%)
:arrow_up:

.../java/io/seata/sqlparser/druid/BaseRecognizer.java
89.18% <81.81%> (-3.12%)
:arrow_down:

...a/sqlparser/druid/oracle/BaseOracleRecognizer.java
26.19% <81.81%> (+26.19%)
:arrow_up:

...obuf/convertor/BranchRegisterRequestConvertor.java
90.47% <0.00%> (-9.53%)
:arrow_down:

...otobuf/convertor/GlobalBeginResponseConvertor.java
92.59% <0.00%> (-7.41%)
:arrow_down:

...n/src/main/java/io/seata/common/util/IdWorker.java
77.08% <0.00%> (-6.25%)
:arrow_down:

...otobuf/convertor/GlobalCommitRequestConvertor.java
93.75% <0.00%> (-6.25%)
:arrow_down:

...otobuf/convertor/GlobalStatusRequestConvertor.java
93.75% <0.00%> (-6.25%)
:arrow_down:

... and 33 more

https://seata.io/zh-cn/docs/user/sqlreference/sql-restrictions.html文档里，大佬要不麻烦也给个样例sql。😄

LGTM


[docs] Describe using traditional calling syntax for specifying fixture names and pages

Some people have problems understanding our tagged template literal syntax:
fixture`123`.page`example.com`;

At least, we should mention that the function calls can be used here as well:
fixture('123').page('example.com');

Or even rewrite our examples to use simpler syntax, and mention tagged templates as an alternative.

Code examples in basic guides now feature the latter syntax, making them easier to understand for newcomers.


Consider non-joined fields when merging preloaded assocs only at root

Otherwise, using more than one join with preload will result in
duplicating assocs.
[Fixes #2815]

Take a look at https://github.com/elixir-ecto/ecto/issues/2815 for details.

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


About Us page

Can I work on this issue? I'm a participant of LGM Soc21.

Can I work on this issue? I'm a participant of LGM Soc21.

Can I work on this issue? I'm a participant of LGM Soc21.

After making changes host the page from your github then send the link here first.

Sure!

https://jagannath8.github.io/HelpingHand/

https://jagannath8.github.io/HelpingHand/

Don't make separate page. Like every other area make about us in same the page.
and follow this serial.
home--> mission --> about us->contact
Delete the contact symbols from "About us" page;
Do this changes and then share the link.

https://jagannath8.github.io/HelpingHand/

I would like to work on it

https://jagannath8.github.io/HelpingHand/

This about us section s not complementing the website.

I would like to work on it

Make changes and share me the link here

I would like to work on this issue, please assign me this issue

hey can try once if you want

I also want  to work on this issue, please assign me this issue

Look at it

its looking awesome and simple view with the colors and fonts

its looking awesome and simple view with the colors and fonts, please let me know for changes
https://jatinjain001.github.io/HelpingHand/

@jatinjain001 make the background color similar to the website theme

its looking awesome and simple view with the colors and fonts, please let me know for changes
https://jatinjain001.github.io/HelpingHand/

@jatinjain001 make the background color similar to the website theme

okay

I would like to do this. Can you please assign me this issue....

I would like to do this. Can you please assign me this issue....

I am still working on it

I would like to do this. Can you please assign me this issue....

I am still working on it

You can check it on last link i shared you iis it fine ? if any changes please let me know


Added station metadata end point

Closes #17
Added endpoints for station metadata
station/
station/{country}
station/{country}/{station_id}
In each case, the station metadata and definitions are returned.
Simplified code structure by bringing in epicsa-python into the project. Test will still need to be transferred see #25

@chrismclarke I have put the definitions to come back with the station metadata. Let me know if this is ok.
I have also removed open cdms as this should not be used any more and moved the epicsa python into this project as it is only one file and I felt like it created more complications.

Thanks @ChrisMarsh82 - all sounds good to me, I'll start testing dashboard integration next week and share any feedback then.
Bringing in the e-picsa python lib makes a lot of sense to me (never fully understood why it needed its own repo as seemed to only really call r functions). I've updated the Architecture Diagram accordingly
Also really nice that means no more python dependencies at all, should make workflows a lot smoother. Thanks for updating the documentation and dockerfile also.
Also nice to hear you were able to finish the migration from OpenCDMS - I know that triggered a number of issues for python version compatibility so good to be a little more streamlined.


DrawState: crash on vkUpdateDescriptorSets

Hi,
we encounter a crash while calling vkUpdateDescriptorSets when the draw_state layer is active.
In draw_state.cpp:validateSampler:
line:2588: auto sampIt = my_data->sampleMap.find(*pSampler);
Reason:
pSampler is an invalid pointer.
pSampler is inavlid because in line 2968:
if ((skipCall = validateUpdateContents(my_data, &pWDS[i], &pLayout->createInfo.pBindings[binding])) == VK_FALSE) using binding as index for pBindings is invalid for sparsely defined descriptor sets.
This is also a regression to previous versions of the sdk.

This is already fixed in master. Below is the latest version of the call referenced above:
skipCall = validateUpdateContents(
                         my_data, &pWDS[i],
                         &pLayout->createInfo.pBindings[bindingToIndex->second])

Note that binding is now correctly mapped to a valid index, handling sparsely defined descriptor sets.


transparency in name-preview window make names sometimes unreadable

The set transparency in the "name-preview window" (for lack of better words), makes it often unreadable, espeicially if the POI is in a crowded area with many POIs.
Full white would be the easiest, I guess, and does the job.

set to 80% white instead of 50% - better now?

Let´s mark that as done. It is not crucial anymore, and if we get user-feedback, we can open a new one.


Blank Page after login

Blank page after login

Fatal error: Uncaught ErrorException: Connection timed out after 30000 milliseconds in /var/www/html/skins/includes/openid.php:284 Stack trace: #0 /var/www/html/skins/includes/openid.php(480): LightOpenID->request_curl() #1 /var/www/html/skins/includes/openid.php(638): LightOpenID->request() #2 /var/www/html/skins/includes/openid.php(857): LightOpenID->discover() #3 /var/www/html/skins/includes/authorize.php(31): LightOpenID->authUrl() #4 {main} thrown in /var/www/html/skins/includes/openid.php on line 284

try refresh the page with CTRL + F5 to clear the cache and tell me if its the same.

Same even after doing that, it doesn't go to steam.
On Fri, Mar 1, 2024, 7:18 PM LielXD @.***> wrote:

try refresh the page with CTRL + F5 to clear the cache and tell me if its
the same.
—
Reply to this email directly, view it on GitHub
https://github.com/LielXD/CS2-WeaponPaints-Website/issues/29#issuecomment-1973236953,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM6GKLC5LEZSVGO6SQ53WDTYWCBKRAVCNFSM6AAAAABEBHBCB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTGIZTMOJVGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

https://cdn.discordapp.com/attachments/912715770193117274/1213148187641122846/Screenshot_2024-03-01_183740.png?ex=65f46b4b&is=65e1f64b&hm=921addb1e372f5aa553e31adff18f8280b2001b4368fa9bd2d5f0f3d14353cd4&
This is what I'm getting now

I've sign in to your website and worked fine maybe some issue with steam try again tomorrow and tell me if its still throwing error.

I found a fix


Dw 132

Fixes dw-132

@Yembot31013 I'm re-writing public git history as part of dw-153. As a result, your fork will likely become out of sync and you will need to create a new fork (or otherwise sync with the upstream repo). I suspect this will force you to start over on this task. I apologize for this inconvenience.


isort doesn't work if non-import statement before imports?

(Using isort 4.3.21; Python 3.7.3; Mac OS 10.14.6)
Running isort has no effect on this file (-d option gives me the same text; --diff gives me no output):
# isort_test.py
print("foo")
import os

However, add an import before the print statement:
# isort_test2.py
import sys
print("foo")
import os

And it works as expected:
$ isort -d isort_test2.py
# isort_test2.py
import os
import sys

print("foo")

Is there a config somewhere that I'm missing? I would have expected the default behavior to be that isort would be able to move all imports to the top even if there are statements before the first import.

Hi @dwhswenson,
Thanks for reporting this issue! isort is meant to be safe to run on large code bases. Occasionally, those large code bases do crazy things in code before imports, to change the behaviour of imports themselves. As a result isort tries to not have an opinion about these kind of things by default focusing only on what it is best at. However, I could definitely see value in making an optional flag that will collect all imports at the top of the file, before any code. For those with code bases that will allow it. As such, I'll leave this issue here to represent that work.
Thanks!
~Timothy

I'm going to close this as isort has switched to a purely streaming approach to enable it to do such things as sort imports within functions. This means it will never move import blocks, just sort them where they are.


literal types

(This may be a dupe of #31 but types are not literals, i.e. not usable in constant expressions. It's also brought up in #10 but it's a separate concern from signedness so I thought it might be good to organise the threads into two.)
I took a quick look and things like std::fill and std::array may pose a problem in earlier language revisions, or even C++20. Would you be OK with abandoning C++11. Not necessary but very helpful because then you can keep variables and loops.
And would you consider abandoning C++14 and C++17? Even less necessary but still would reduce the amount of change necessary to achieve constexpr.

Long answer to a short question. I would like to leave uintwide_t alone for the moment, other than a few potential tweaks and providing a safe area to benchmark performance stretching up with higher-order multiplication Toom-Cook and FFT.
We have (or are in the process of) hammering out the details of intwide_t, for which I actually recommend another new project. A lot of this is descrive in #10. Key reasons are C++20, clean new type more adherent to LEWG drafts, etc.
If (or when) intwide_t materializes, consider to (within that newer work) also support the unsigned type with similar top-level attributes.
This sketches out a rather long-term plan. If there are, however, some simplifications that we could make to the present uintwide_t, however, I can consider these. For the moment, I do actually like the support of C++11 or higher, although C++14, with is somewhat relaxed constraints on the depth of the bodies of constexpr functions makes it a lot easier to strive for compile-time constant. This can be negotiated.

Just to see if it was possible, I gave wide-integer C++20 constexpr support in #42. This was mostly the tedious task of adding the constexpr keyword to many functions and requiring C++20 in the build configuration. Things that (unsurprisingly) didn't get constexprified:

IO (the streaming operators)
RNGs
fixed_dynamic_array

I had to make a few little tweaks like value-initialising variables and replacing memset with fill. It didn't take much. (It's a pleasant codebase to work in.)
If you're concerned about constexpr interfering with benchmarks, you might want to play around with the branch. I'm confident that so long as you dynamically randomise your input properly, you should be seeing run-time results, not compiler-baked results. But you should probably check that none of the algorithms didn't mysteriously drop to 0s!
Would you be interested in further pursuing this branch, i.e. chasing C++17 and C++14 support? It gets more challenging -- mostly because fewer of the standard library algorithms are supported. So, for example, we might need to provide our own fill and all_of. If we can get to C++14, there's little reason not to move over. Being able to use these types as literals is an incredibly useful feature to provide -- aside from use in CNL.

Just to see if it was possible, I gave wide-integer C++20 constexpr support in #42.

Many thanks @johnmcfarlane for this ground-breaking stride forward. That is awesome! I left a few initial thoughts in the PR.

Would you be interested in further pursuing this branch, i.e. chasing C++17 and C++14 support? It gets more challenging -- mostly because fewer of the standard library algorithms are supported.

Yes. Either here directly, or, better yet in something like a version 2 reload of uintwide_t, intwide_t, etc. with proper storage, C++20 support and also (among other standardization migrations) improved constexpr correctness.
I'm thinking new project instead of branch.

Given I can see a route to C++20 constexpr support using the macros, I don't think the C++17,14,11 is so important now. CNL 2.x targets C++20 only currently, and it looks like it starts to quickly get difficult to support C++17 constexpr.

Given I can see a route to C++20 constexpr support using the macros, I don't think the C++17,14,11 is so important now.

Indeed, I've toned the revolution ideas down for the moment. In particular, it was cool how things actually worked out (or are in the process of working out) quite well with the C++20 constexpr support, as the method you've (we*ve) found does still retains compatibility with 11, 14, 17.

CNL 2.x targets C++20 only currently, and it looks like it starts to quickly get difficult to support C++17 constexpr.

The final question I have is if we should stick with this repo, make a version 2, or migrate a derived work into the org you mention in another post

@ckormanyos I think any of those works. I'm 75% convinced I should create a cnl-org, which I think would make a good home for a library like this.
One option I neglected to mention was straight-out replacing cnl::dupliex_integer with a cnl::multiword_integer which derives from fixed_static_array(*). I assumed you'd prefer to continue wide-integer along its own track but combining our efforts would be a big win for CNL. I already aim to support all the functionality of a wide integer type as well as using it to create an exceedingly powerful fixed-point type which users seem to be very keen to see.
(*) I've not mentioned fixed_dynamic_array so far -- mostly because it is impossible to constexprify in C++20 -- and I'm still unfamiliar with the architecture of these types. But I have some thoughts about it also:

I think you could consolidate fixed_static_array and fixed_dynamic_array into a single adapter (a little like std::stack) in which storage is parameterised. Then that parameter would determine whether storage was dynamic or static:
template<long NumWords, std::integral TopWord, multiword_storage Storage = static_array>
class multiword_integer;

(That last parameter might need to be a template template parameter.)
I'm guessing the algorithms for both types are the same; they just operate on words in different areas of memory.

Regardless of missing constexpr support, I think a dynamic memory type needs better support in CNL, i.e. I need to use forwarding everywhere so that these things are not copied more than is necessary. So I'm interested in using fixed_dynamic_array as a measure of interface and implementation quality.

A further separation of concerns (I mentioned previously) is to separate the type from the operators. CNL does this with custom_operator, tags and _impl::wrapper. Basically, you only have to provide functors which contain the algorithms for each operator. You then create a tag which describes the type, e.g. multiword_tag<12, int64_t> for a 768-bit type and the type is created for you with: using int768_t = cnl::_impl::wrapper<static_array<int64_t>, multiword_tag<12, int64_t>>;.
The benefit of this approach is that you don't need to write a full set of operators, or all of the boilerplate related to construction, conversion etc..

Sorry for the overwhelming brain dump there, but regardless of where this project goes, I'd be keen to contribute to its design where you think it would help.
Anyway, closing this now because literal types are in. Thanks!

Hi @johnmcfarlane without going into detail on all your points, i generally agree with all those thoughts.
I would like to retain the identity of the wide-integer Repo and will be trying to move forward on:

the signed integer type,
a clean and terse epxression of Toom-Cook 3,4,
improved sub-quadratic division,
low-limb count high-speed division.

So these goals are not entirely consistent with another set of goals which is to generally move big integers, floats and fixed-points into a standardized form. My work here, in Boost and together with you is all hopefully generally moving in that direction.
Along these lines, I think we should, at some point in time (maybe after signed integer), pull out some of the stuff in this Repo, get it where you need it to be for CNL and contribute there.
Along the way, I would greatly appreciate and enjoy your help, advice and expert contributions in this little wide-integer project here. I really learned a lot from you in these contributions that you led us on.
Thanks @johnmcfarlane and let's keep gling on numbers.
I will officially close this issue.


Wok 529 refactoring ds image analysis

I see that i failed to create a new branch for the speed optimization. All commits before 8ad943e have been reviewed as part of  WOK-529, while this is actually related to WOK-507


getPrintableDeviceMode function prints data from class and not from device

This is bad as a bad configuration can slip away to someone not aware of this behavior.
Data should instead be read from device using readBytes

@an4cr0n  what do you think about this refactor?


Remove inlined webpack loader declaration

Ensure that the webpack loader declarations are in the plugin and configurations so that custom resolution isn't affected when consuming the plugin.

Thanks for the PR!
As this does not currently compile, I'm going to close this - please re-open when it is ready for review


Need fast-mode model

Current model architecture is complex (especially CNN model for turn or river).
Computation time could be bottle-neck for experiment.

Computation time measured on 2 machine (with/without GPU machine)

without GPU

XXX-no-MacBook-Air-2:HoleCardHandicapper kota$ python sample/measure_calc_time.py
Using Theano backend.
[preflop] Average calculation time : 0.033076
[flop] Average calculation time : 0.063380
[turn] Average calculation time : 0.078801
[river] Average calculation time : 0.088379

with GPU

XXX-Mac-Pro:HoleCardHandicapper enoshima$ python sample/measure_calc_time.py
Using Theano backend.
Using gpu device 0: GeForce GTX 980 (CNMeM is enabled with initial size: 1 MB, cuDNN 5005)
[preflop] Average calculation time : 0.028391
[flop] Average calculation time : 0.150273
[turn] Average calculation time : 0.135556
[river] Average calculation time : 0.136874

Re-measured computation time on GPU machine
>>> def ff(a,b,c,n=100):
...   def f(a,b,c):
...     st = time.time()
...     a(b,c)
...     return time.time()-st
...   return sum([f(a,b,c) for _ in range(n)])*1.0/n
>>> ff(flop_model.predict, 3, 1000)
0.005469787120819092
>>> ff(turn_model.predict, 4, 1000)
0.005874849081039428
>>> ff(river_model.predict, 5, 1000)
0.005476136922836303

Tuned performance for reinforcement learning use.
What changed

remember all win rate in preflop and just return it without neuralnet
cache last (hoke, community, win_rate) pair and just return the win rate if cache hits


Add meet

Link
https://github.com/ryanprior/meet
Checklist

[x] - Shard is at least 30 days old.

@jgarte Could use a rebase on master. Pretty sure CI would fail due to it not being in ABC order.

@jgarte Could use a rebase on master. Pretty sure CI would fail due to it not being in ABC order.

@Blacksmoke16 Thanks for catching that! I re-pushed with the fix.

@Blacksmoke16 done.


Implements  Timeout Feature For Operations

Hi @saitakturk,
Thanks for implementing that. This changset looks pretty good for me. Could you have any idea of the failure on CI and could you please further fixes that?

Hi @saitakturk,
Thanks for implementing that. This changset looks pretty good for me. Could you have any idea of the failure on CI and could you please further fixes that?

The timeout feature has been implemented in #131.


Refactor car actions: doors and direction signal

The current action (direction + target) is not too expressive
We need to:

Add a door and open/close door actions (people can get in and out only when door is open)
A signal arrow of where the next direction of the elevator is (down, up).

People should enter car IFF door open  and direction matches direction of person

@andresjarami , this is the critical issue that we need to address next. If we solve this, then we can close PR #9 with lots of issues associated.
The issue is this: in line 36 we ask the controller what the actions are for each car (red arrow):

So what the simulator needs to do is realize the actions in ONE place, not in two. The previous simulator changed the direction and target of the car, but only the current_floor later, having then two places to "execute" the actions on the car.
The actions should be executed ONCE in the car, and then realize all the effects of that happening. This means that the display or reporting should be linked to each action or effect, not all in one shot as we would have lost the temporal relationship.
For example, suppose the elevator has a door. Then the steps are as follows:

Elevator moves to floor 10 say in step 1 (drawing of movement done)
Elevator shows arrow of next direction in step 2, indicating where the elevator will move next (drawing of arrow, or report)
Elevator opens the door in step 3 (drawing/report of door opening done here)
People enter the elevator in step 4  (drawing of people done)
Elevator closes the door in step 5 (drawing done)
....


[WIP] Containers old refresh: create/resolve mapped tags in separate pass

Overview issue: https://github.com/ManageIQ/manageiq-providers-kubernetes/issues/126

[ ] Depends on https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/117
which makes parser emit :tags_to_resolve, each hash there potentially used
in multiple entities' :tags.

This does not yet do batch Tag queries.  Still O(tags).
I expect will give a small performance boost from parser reusing same tag for multiple entities, which will allow saving to query the tag id only once.
(That's why it now sets tag_hash[:tag_id] as side effect.)
And retag_entity remains an O(entities) bottleneck.
My main goal here is exposing ability to resolve tag hashes to tag ids in one pass and reassign them later, which I'll leverage later to implement tag mapping for containers graph refresh.
@miq-bot add-label enhancement
@Ladas @agrare @zgalor @moolitayer Please review.

@miq-bot add-label wip
Exploring using InventoryCollection instead of hashes for both old and graph refresh...

Closing in favor of #16098


fix error service name in Cleanup

fix bug in https://github.com/istio/istio/pull/27002
issue：[release-1.6] cleanup services when removing cluster secret #26930
[X] Does not have any changes that may affect Istio users.

Hi @ImmortanJoe. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@googlebot I signed it!

LGTM
/ok-to-test

@ImmortanJoe: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
d967071f39f7a934a647a4b26363164273a99e43
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio

@ImmortanJoe: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
d967071f39f7a934a647a4b26363164273a99e43
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio

@ImmortanJoe: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
d967071f39f7a934a647a4b26363164273a99e43
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio

Why the bot not cherry-pick


[SMALLFIX] Use static imports for standard test utilities in class FileWorkerMasterSyncExecutorTest

…terSyncExecutorTest

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17822/
Test PASSed.

Merged build finished. Test PASSed.

@aaudiber  are we supposed to static-import Mockito?


Severity value & icons

For now it is not possible to use different icons at different value-ranges / severities (e.g. mdi: battery-10 and so on).
Can you allow icon-changes on severities?

Added in 1.6.0.


Move goals and stakeholders to root readme

looking for 👀 to move the goals up to the root readme, in the streamlined format.
We'll have separate PRs to amend the goals.


no_std support

Thank you for creating this! I'm in the process of porting some no_std blocking code to async and needed to make some small modifications to this crate to do so.

Add support for no_std when the std feature is not enabled
Enable std by default
Add an alloc feature to pull in the alloc crate for Vec impls when using no_std + alloc

@yoshuawuyts Sorry for the ping, did you get a chance to take a peek at these changes?


[MGDOBR-1250] - Fetch Bridge details to deploy from Control Plane and Create ManagedBridge CR instances

…reate ManagedBridge CR instances
Jira : https://issues.redhat.com/browse/MGDOBR-1250
Insert JIRA Issue number and update link
PR owner checklist
Please make sure that your PR meets the following requirements:

[ ] Your code is properly formatted according to this configuration.
Run mvn clean verify -DskipTests so that imports are correctly set.
[ ] Your commit messages are clear and reference the JIRA issue e.g: "[MGDOBR-1] - $clear_explanation_of_what_you_did"
[ ] The layers in the kustomize folder have been updated accordingly.
[ ] All new functionality is tested
[ ] Pull Request title is properly formatted: MGDOBR-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

PR reviewer(s) checklist

[ ] Check if code and Github action workflows have been modified and if the modification is safe
[ ] If the modification is safe, add the safe to test label

How to trigger pipelines and use the bots:

Run the end to end pipeline
Annotate the pull request with the label: safe to test. If you want to run the pipeline again, remove and add it again.

Rebase the pull request
Comment with: /rebase.

Deploy BOT
Comment with `/deploy <dev,stable> when the PR has been merged to deploy to a target environment.

@robpblake


Download fixes

I made some fixes in download.py to make it work on both Python 2 and 3, as listed in supported platforms list

@everm1nd Thanks!


Update libraries and remove deprecations #818

Prepare for Symfony 6 by removing deprecations.

I prefer the latest phpunit, as Symfony no longer appears to mention
simple-phpunit in it's documentation:
https://symfony.com/doc/current/testing.html#the-phpunit-testing-framework
But honestly I don't know, both work, I think simple-phpunit is now at 8.5,
while phpunit is at 9.5.
I can remove it, though, until there's a better reason to switch.
On Mon, Nov 15, 2021 at 4:01 AM Jérémy Benoist @.***>
wrote:

@.**** commented on this pull request.
In composer.json
https://github.com/j0k3r/f43.me/pull/819#discussion_r749117905:

@@ -65,13 +65,14 @@
"phpstan/phpstan-doctrine": "^0.12",
"phpstan/phpstan-phpunit": "^0.12",
"phpstan/phpstan-symfony": "^0.12",

   "symfony/browser-kit": "5.3.*",

   "symfony/css-selector": "5.3.*",

   "symfony/debug-bundle": "5.3.*",

   "phpunit/phpunit": "^9.5",

Is it required? Because we use simple-phpunit to run test and not phpunit
directly
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/j0k3r/f43.me/pull/819#pullrequestreview-805786432,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEXIQIN3VBYRGCKSZOMCELUMDD43ANCNFSM5H74FGJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hmm, I removed it, and now I can't seem to get the tests to run locally,
even after following
composer require --dev symfony/phpunit-bridge
C
Can you tweak this PR please?
On Mon, Nov 15, 2021 at 7:37 AM Tac Tacelosky @.***> wrote:

I prefer the latest phpunit, as Symfony no longer appears to mention
simple-phpunit in it's documentation:
https://symfony.com/doc/current/testing.html#the-phpunit-testing-framework
But honestly I don't know, both work, I think simple-phpunit is now at
8.5, while phpunit is at 9.5.
I can remove it, though, until there's a better reason to switch.
On Mon, Nov 15, 2021 at 4:01 AM Jérémy Benoist @.***>
wrote:

@.**** commented on this pull request.
In composer.json
https://github.com/j0k3r/f43.me/pull/819#discussion_r749117905:

@@ -65,13 +65,14 @@
"phpstan/phpstan-doctrine": "^0.12",
"phpstan/phpstan-phpunit": "^0.12",
"phpstan/phpstan-symfony": "^0.12",

   "symfony/browser-kit": "5.3.*",

   "symfony/css-selector": "5.3.*",

   "symfony/debug-bundle": "5.3.*",

   "phpunit/phpunit": "^9.5",

Is it required? Because we use simple-phpunit to run test and not
phpunit directly
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/j0k3r/f43.me/pull/819#pullrequestreview-805786432,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEXIQIN3VBYRGCKSZOMCELUMDD43ANCNFSM5H74FGJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I'll check when I got some spare time

What do you think about bumping to the latest Symfony/PHP?
This is a cool project, since it's not a library or bundle, there's little downside in tagging a new version and upgrading.

I'm still running PHP 7.4 for some other pet projects and that's mostly the reason I didn't upgrade the Symfony version.

OK, I think my fork now works handing both situations.  If php 7.4, it installs Symfony 5.4, and if PHP 8, it install the Symfony 6.1 components.
While it's working for me locally, I'm not sure I migrated security.yaml correctly.
PHP 7.4 will stop receiving security fixes in 2 months...


Published config overwritten

Hi there,
The app's published config gets overwritten by the default configuration because the config file's name is "hashids.php".

Fixed in https://github.com/vinkla/instagram/pull/17.

Whoops, sorry about this. Thanks for finding it!


Save cards locally on computer without Anki and sync later

Some user can't have Anki on work computers so the extension become useless in such case.
It needs to take advantage of chrome storage sync API to save and sync data across computers.
Steps needed:
Store: on successful connection

deckNames,
modelNames,
noteTypes,
noteFields
allTags

Check: while starting
if there is above stored data,

retreive data
show a button to submit locally.

Submit:
Store the whole note in locallySavedNotes object.
Settings: Restore Notes
Loop through `locallySavedNotes'
and send each note to Anki
Additional tab with saved notes

providing a deleteNote to delete saved notes before sending them to Anki.

deleteNotes:

loop through the object

delete specific note.

update list of locally saved notes.

Implemented saveNotes feature to save notes locally and sync later on