Infinite loop with MultiProcessMapDataZMQ

There is an infinite loop with the following code:
from tensorpack.dataflow import MultiProcessMapDataZMQ, FakeData

ds = FakeData(((50, 50, 3), (1,)))

import numpy as np

def proc(dp):
    img = np.random.randint(0, 255, size=(1012, 1012, 3))
    img[img < 120] = 0
    return dp

mp_ds = MultiProcessMapDataZMQ(ds, map_func=proc, nr_proc=10, strict=True)

mp_ds.reset_state()

for i, (_, _) in enumerate(mp_ds.get_data()):
    if i % 100 == 0:
        print(i, end=" . ", flush=True)

Important part is strict=True and small size of FakeData. If change size to (512, 512, 3), then loop ends properly. Probably, there is something with buffer filling and dequeing...
Execution stucks here.

Cannot reproduce. Please update

Actually, I have already updated to the master.

@ppwwyyxx could you reproduce the issue ?

I can not. Maybe upgrade/reinstall msgpack?

Could you try please this code too:
from tensorpack.dataflow import MultiProcessMapDataZMQ, RNGDataFlow, MultiThreadMapData

dataset = [("file_%i" % i, i % 3) for i in range(500)]

class TestDataset(RNGDataFlow):

    def __init__(self, dataset):
        super(TestDataset, self).__init__()
        self.dataset = dataset

    def size(self):
        return len(self.dataset)

    def get_data(self):
        for k in range(len(self.dataset)):
            yield self.dataset[k]

test_dataset = TestDataset(dataset)
test_dataset.size()

def data_transform(dp):
    return dp

mp_test_dataset = MultiProcessMapDataZMQ(test_dataset, nr_proc=10, map_func=data_transform, strict=True)

mp_test_dataset.reset_state()

for i, (fp, _) in enumerate(mp_test_dataset.get_data()):
    if i % 100 == 0:
        print(i, end=" . ", flush=True)

Okay, I'll try to upgrade msgpack, which version do you use ?

The code successfully exits. I use the latest version of msgpack & msgpack-numpy. Maybe also try upgrading pyzmq.

Strange configuration I have. Here is a list of versions of some of packages I have:
msgpack (0.5.6)
msgpack-numpy (0.4.3)
msgpack-python (0.5.5)
numpy (1.14.1)
pickleshare (0.7.4)
pip (9.0.1)
pyzmq (17.0.0)
tensorpack (0.8.1)

https://github.com/msgpack/msgpack-python#pypi-package-name
Maybe related.

I could reproduce the issue using this docker file. Could you try it please?
Dockerfile.txt
test_tensorpack_inf_loop.txt
Please remove .txt extensions from Dockerfile and replace it for test_tensorpack_inf_loop.txt by py
Github do not allow include py and dockerfile as is.

I can reproduce the issue in docker. Looks like I'm using zmq socket in a wrong way where messages can get lost if the sockets aren't created with a desired order.

Awesome ! 🎉


ARROW-14842: [C++] Improve precision range error messages for Decimal

Decimal128: Invalid: Decimal precision out of range [1, 38]: 0
Decimal256: Invalid: Decimal precision out of range [1, 76]: 100

@nealrichardson , looks the RTools 35 job timed out
https://github.com/apache/arrow/runs/4320157653?check_suite_focus=true

@nealrichardson , looks the RTools 35 job timed out https://github.com/apache/arrow/runs/4320157653?check_suite_focus=true

I'm not sure why that would be, but it seems to have happened again.


Next Page button issue

I have found out that if in response "current" is string,
next button will concat "current" value + current page
I suppose a parseInt would be nice to resolve this.

Ran into this, but couldn't figure out why, I was able to work around it thanks to your issue description.  Thanks.
+1 for bug fix :D


Validate llm_config passed to ConversableAgent (issue #1522)

Based on #1522 (and a follow-up discussion in this PR), this commit implements the additional validation checks in ConversableAgent.
Add the following validation and raise ValueError if:

The llm_config is None (validated in ConversableAgent).
The llm_config has no model specified and config_list is empty (validated in OpenAIWrapper).
The config_list has at least one entry, but not all the entries have the model is specified (validated in OpenAIWrapper).

The rest of the changes are code churn to adjust or add the test cases.

Why are these changes needed?
The root cause is #1522. The intent here is to enforce the contract for input parameters that are passed to ConversableAgent. With these changes the following happens:
from autogen import UserProxyAgent, AssistantAgent

# Throws an error because "config_list" is empty and "llm_config" does not
# have a value for "model" specified.
assistant = AssistantAgent("assistant", llm_config={"config_list": []})

# Throws an error because "config_list" has no "model" specified.
assistant = AssistantAgent("assistant", llm_config={"config_list":
                                                    [{"model":"", "api_key":
                                                      "sk-mysecretkey"}]})

# Works.
assistant = AssistantAgent("assistant", llm_config={"config_list":
                                                   [{"model":"gpt-4", "api_key": "sk-mysecretkey"}]})

# Throws an error because one of the "config_list" entries has an empty model.
assistant = AssistantAgent("assistant", llm_config={"config_list":
                                                    [{"model":"gpt-4",
                                                      "api_key": "sk-mysecretkey"},
                                                     {"model":"", "api_key":
                                                      "sk-mysecretkey"}]})

# Throws an error because no "llm_config" is specified.
assistant = AssistantAgent("assistant")

# Works.
assistant = AssistantAgent("assistant", llm_config=False)

# Works: "llm_config" specifies the "model" attribute.
assistant = AssistantAgent("assistant", llm_config={"model": "gpt-4"})
proxy = UserProxyAgent("user")

proxy.initiate_chat(assistant)

Related issue number
Hopefully fixes #1522.

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ X] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ X] I've made sure all auto checks have passed.

Codecov Report
Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (d01063d) 37.79% compared to head (265e8ba) 23.67%.
Report is 2 commits behind head on main.

Files
Patch %
Lines

autogen/oai/client.py
50.00%
1 Missing and 3 partials :warning:

autogen/agentchat/conversable_agent.py
0.00%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1654       +/-   ##
===========================================
- Coverage   37.79%   23.67%   -14.13%
===========================================
  Files          50       50
  Lines        5704     5736       +32
  Branches     1295     1410      +115
===========================================
- Hits         2156     1358      -798
- Misses       3377     4216      +839
+ Partials      171      162        -9

Flag
Coverage Δ

unittests
23.64% <40.00%> (-14.16%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Create a hot-reload for development stage

Executing npm start will now activate development environment which will also activate the hot-reload function.
This change require 'electron-reload' package, so please install it to make sure this change is working properly

#3

Great job!


I hope it will continue to update and support PHP7

This project is great.
PHP7 is a high performance product，I hope it will continue to update and support PHP7.
Thank you

@lobtao still trying, maybe after a few months it will :smile:

Is this project dead

check this
https://github.com/devlephant/soulengine


Keeps re-opening closed editors

Does this issue occur when all extensions are disabled?: Think so

VS Code Version: 1.92.0-insider (Universal) Commit: c37f4a49e28831cec1aec1af0f626edaada1f7ce
OS Version: Macos Sonoma

Steps to Reproduce:

Open a new editor with no contents and don't save it
Close it
It's re-opened again even though you closed it

This is the callstack to the openEditors method being called straight after it was closed:

https://github.com/microsoft/vscode/assets/13242392/0356bc90-5f58-4bab-8267-27efb797315a

I have the same issue on 1.91.1 version, OS Windows_NT x64.
Closing vscode and deleting files from \AppData\Roaming\Code\Backups  helps - after reopening vscode when I close a file it doesn't reopen anymore.

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

@bpasero i added a screenshot to the description (but didn't point out why if was significant). Here's the stack showing it the re-opening coming directly from the closeEditors call.

I can try without extensions though

Please do.

Issue stooped occur in my installation. I didn't do anything special... :/
list of active extensions that were updated in last two weeks:

oracle developer tools
gitlens
cody ai
project manager for java
.net install tool
live preview


URL with parameters

Hello, if a video URL with parameters, the parameters of each request is not the same, how do I use this cache?

I've reopened this issue. It is a good question and actually library hasn't good solution for it.

Oh, same issue has already existed.


Conditionally output all help groups on empty groups vector

I wanted to output all groups using the help() method without specifying them all manually.
As I couldn't find this feature in the current code, I just added this feature.
I decided to just use an empty groups vector as the condition to output all help groups.

This change is

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


clicking on "Ask HN" enteries gives 404

Nice catch! sounds like a relative url is returned for 'Ask items'

and if you are still interested in who regrets choosing Elixir here are the answer 😆 🤣


Add a License

Please can you add a license to this project? Right now without a license it defaults to all rights reserved.

Thanks for your interest. I have added MIT license to allow everyone to use it without restrictions.

Thanks for your interest. I have added MIT license to allow everyone to use it without restrictions.


Do manual swap

We should perform a manual swap between bitcoin and tfchain to see how it works and what the output is

Manual Swap was completed successfully.


Send a counter to StatsD for csv download time

What
Send a StatsD metric for elapsed time in seconds to generate the CSV
Adds start_time to the Sidekiq worker call.
The Sidekiq worker then uses this to send a counter to StatsD
with the number of seconds elapsed.
Why
We want to know how long the users are waiting
for a CSV download.

Review Checklist

[ ] Changes in scope.
[ ] Added/updated unit tests.
[ ] Added/updated feature tests.
[ ] Added/updated relevant documentation.
[ ] Added to Trello card.

Trello: https://trello.com/c/3Eg16r1C/1257-3-build-sli-grafana-dashboard

 (3) Build SLI Grafana Dashboard


Autocomplete on transformed paths

I'm trying to transform path autocompletions to use "%20" instead of spaces but the following settings only ever replace the first space in the autocompletion, e.g. I get "../Some%20Folder Name/" as a suggestion. That's an issue as I need every space to be a "%20" for Markdown paths to work. Am I doing something wrong?
"path-autocomplete.transformations": [{
    "type": "replace",
    "parameters": [" ", "%20"],
    "when": {
        "filename": "\\.md$"
    }
}],

But regarding the title of this issue, even if I manually type the correct paths in with all the "%20"s, the next Ctrl + Space I do doesn't suggest anything, presumably because of the path string not matching the paths reported by VS Code. For this reason, it would be great if the extension could look up what is being used as a transformation  (in my case "%20" instead of " ") and invert the transformation to know what the path actually is so that an autocompletion can be shown: "../Some%20Folder%20Name/" should be able to trigger autocompletions, for example.
This will only work with simple regex transformations, but in general, I assume people will only use the transformation option to substitute characters so the suggested feature should work for most people. Alternatively, maybe a secondary transformation should be supported "Substitute" to be sure that the rule can be inverted.
Thanks.
v1.22.1

@mihai-vlc Hello Mihai. Could you kindly inform me whether it is possible to replace all instances of a character in a path using path-autocomplete.transformations? E.g. foo bar baz.md to foo_bar_baz.md (spaces to underscores)?

Support for this has been added in 1.24.0
Please try it out and feel free to reopen the issue if it doesn't match your use case.
  // replace spaces with %20
  {
      "type": "replace",
      "parameters": [ " ", "%20", "g" ],
      "when": {
          "path": ".*routes"
      }
  },

  // replace %20 with spaces when reading the already inserted path
  {
      "type": "inputReplace",
      "parameters": [ "%20", " ", "g" ],
      "when": {
          "path": ".*routes"
    }
  },

Thank you! It works great. Unsure why to use "path": ".*routes" over filename, but what I have is functioning as expected anyhow.
By the way, the README.md examples wrongly contain mentions of fileName when they should be filename (otherwise it will not work).

The fileName and path can be used for filtering the items/instances where the transformation should be applied.
For the replace transformation considering we selected /home/mihai/a.txt:

fileName - regex applied to the basename of the selected suggestion a.txt
path - regex applied to the the full path of the selected suggestion /home/mihai/a.txt

For the inputReplace transformation considering that what we typed so far is /home/mihai:

path - regex applied to the path inserted so far /home/mihai


feat: add keys option to disable arrow keys drag

Is it an expected behavior that keys can't be disable if target is window? In the this example, keys continue to trigger the drag handler.
new DragGesture(window, () => { ... }, {
  eventOptions: { passive: false },
  preventDefault: true,
  pointer: { keys: false }
})

I will try to take time to make a reproductible example.

Good catch, that's a bug @willybrauner. Fixing now. Merci ;)

Fixed now @willybrauner in 10.2.22, should be working with Vanilla as well. https://github.com/pmndrs/use-gesture/releases/tag/%40use-gesture%2Fvanilla%4010.2.22

Wow merci ! 🙏🏽


Tabler react loading time is too much

I'm using these utilities from tabler react in login page
import { Button, Card, Form, Icon } from 'tabler-react';
and it is taking way too much to load e.g 19.24s
download speed of internet is 13 mb and upload is 2mb

any help will be appreciated

It's stil not issued?

I think it loaded the entire tabler module.


Change expected error code from fd_prestat_dir_name

In the case that the user provides a buffer which is too small to fit the directory name, it makes more sense to return EINVAL rather than ENAMETOOLONG. ENAMETOOLONG has the speficic connotation that a path was longer than the maximum size permitted by the OS - that doesn't really match this error condition.
previous discussion on the more suitable error code.

is it strictly mentioned in the spec?
otherwise, i guess it's safer to allow both error codes.
wasmtime returns ENAMETOOLONG, doesn't it?

It's not mentioned in the spec, https://docs.rs/wasi/latest/wasi/fn.fd_prestat_dir_name.html. But I'd say it's better to standardise on a single error code. In this case it shouldn't be much work to change it either way. As far as I understand, the purpose of the tests isn't so that they pass immediately on all runtimes, it's to highlight and standardise any differences in behaviour.

wasmtime returns ENAMETOOLONG, doesn't it?

It probably does since this test is originally from the wasmtime set of tests.
I've raised https://github.com/WebAssembly/WASI/issues/555 to discuss standardising error codes from filesystem functions in general.

It's not mentioned in the spec, https://docs.rs/wasi/latest/wasi/fn.fd_prestat_dir_name.html. But I'd say it's better to standardise on a single error code. In this case it shouldn't be much work to change it either way. As far as I understand, the purpose of the tests isn't so that they pass immediately on all runtimes, it's to highlight and standardise any differences in behaviour.

my point is such a standardization should happen in spec, not tests.

wasmtime returns ENAMETOOLONG, doesn't it?

It probably does since this test is originally from the wasmtime set of tests.
I've raised WebAssembly/WASI#555 to discuss standardising error codes from filesystem functions in general.

i see.

my point is such a standardization should happen in spec, not tests.

True, I've kept both error codes until we decide how to proceed with standardising error codes in general.


support assuming role

Coverage remained the same at 100.0% when pulling 0b49201f976c5107854979b6f610720aaec3deca on cmedley:support-assume-role into f4e30400ae61381077b6c78b00b02ddc4642a331 on dtan4:master.

Awwww yeeeeee. Let's get this merged! :)

LGTM 👍  Thanks ❗

YUSSSSSS! It's merged! :D

+1


[Identity] 1.3.0 changelog entry sync

Adding the 1.3.0 changelog into the master changelog.
Do we use to merge hotfix branches into master? I don't remember.

We merge the hotfix branch to master if the former was where we did the changes first and we are porting it over to the master branch. Or if the two branches are close enough that doing a merge would not result in a ton of merge conflicts. Given that we are a mono repo, that is rarely the case...
So, the approach here is good


Make CellInput TextInput's ref accessible

Added a new prop to make CellInput TextInput's ref accessible. Example usage:
<CellInput
    {/*...*/}
    textInputRef={(r) => {this._inputRef = r}}
/>

The reason for it is e.g. when using Keyboard aware ScrollView mechanisms and need to keep track of TextInput's focus state.

I wouldn't recommend getting the TextInput ref this way. I think it would be better to create a method in the component e.g.:
getInputRef() {
  return this._textInput;
}

In your implementation, you can then use the method:
// render
<CellInput ref={component => this._cellInput = component} />

// somewhere in your code
const inputRef = this._cellInput.getInputRef();

Another solution is to replicate available methods from a TextInput to achieve your goal. Similar to providing the focus, blur and setNativeProps. CellInput is suppose to act as a TextInput so this solution will make sense.

props are directly passed to TextInput so you still have access to the events. If you need certain methods, open a separate PR and add those methods inside CellInput -- similar to the focus method


Static JS file unavailable in Meteor app after "modulus deploy"

I'm upgraded a Meteor app to <IP_ADDRESS> and upgraded all its packages. There's a ShareJS package using the Ace editor. Everything works correctly locally.
I run '''.demeteorizer''', cd into the .demeteorized directory, then run '''modulus deploy'''. The build and deploy is successful, but the browser receives a 500 error when trying to retrieve this file:
'''packages/mizzao_sharejs/.npm/package/node_modules/share/webclient/ace.js'''
Here's the broken production website:
https://www.seemecode.com/
Here's the server log:
'''{"line":"457","file":"webapp_server.js","message":"Error serving static file Error: ENOENT, stat '/mnt/data/2/programs/web.browser/packages/mizzao_sharejs/.npm/package/node_modules/share/webclient/ace.js'","time":{"$date":1419661767968},"level":"error"}'''
Any ideas why this works locally, but not after running '''.demeteorizer''' and '''modulus deploy'''? Thanks!

Did you ever figure this out? I've got a similar problem with a different static file (on a project created with . demeteorizer but deployed to a different host (via Dokku)

My problem is unrelated! The file just wasn't there for me because it was .gitignored and didn't get pushed!


It works on Local, but when I create Docker Image, It gives returned a non-zero code: 255.

Hello,
I installed the latest version of sentry-laravel, when I run it on my local.. it works absolutely fine, but when I create the docker image for it.. the build fails with  returned a non-zero code: 255.
When I add it to dont-discover, the build succeeds.
Here I am adding my composer.json and dockerfile, Please have a look and let me know If I am doing anything wrong.

COPY --chown=www-data --from=vendor /app/vendor/ vendor/
COPY --chown=www-data --from=vendor /app/bootstrap/ bootstrap/
COPY --chown=www-data --from=frontend /app/node_modules/ node_modules/
COPY --chown=www-data --from=frontend /app/public/js public/js/
COPY --chown=www-data --from=frontend /app/public/css public/css/
COPY --chown=www-data --from=frontend /app/public/mix-manifest.json public/mix-manifest.json

RUN mkdir -p storage/app \
    storage/app/public \
    storage/framework \
    storage/framework/cache \
    storage/framework/sessions \
    storage/framework/testing \
    storage/framework/views \
    storage/logs

COPY keyfile.json storage/app/keyfile.json

RUN ls -als

RUN chown www-data:www-data /var/www
RUN chown -R www-data /var/www/storage

RUN rm /etc/localtime && ln -s /usr/share/zoneinfo/UTC /etc/localtime

ENTRYPOINT ["dumb-init", "docker-php-entrypoint"]
CMD ["apache2-foreground"]
STOPSIGNAL SIGQUIT

Composer
{
    "name": "laravel/laravel",
    "type": "project",
    "description": "The Laravel Framework.",
    "keywords": [
        "framework",
        "laravel"
    ],
    "license": "MIT",
    "require": {
        "php": "^7.2.5",
        "erusev/parsedown": "^1.7",
        "fideloper/proxy": "^4.2",
        "fruitcake/laravel-cors": "^1.0",
        "guzzlehttp/guzzle": "^6.3",
        "intervention/image": "^2.5",
        "jenssegers/agent": "^2.6",
        "laravel/cashier": "^11.2",
        "laravel/framework": "^7.0",
        "laravel/horizon": "^4.3",
        "laravel/slack-notification-channel": "^2.0",
        "laravel/tinker": "^2.0",
        "laravel/ui": "^2.0",
        "mpociot/vat-calculator": "^2.4",
        "predis/predis": "^1.1",
        "sentry/sentry-laravel": "^1.8",
        "spatie/laravel-cookie-consent": "^2.12",
        "spatie/laravel-permission": "^3.13",
        "spatie/laravel-web-tinker": "^1.7",
        "stancl/tenancy": "^2.3",
        "superbalist/laravel-google-cloud-storage": "^2.2",
        "unicodeveloper/laravel-password": "^1.0"
    },
    "require-dev": {
        "facade/ignition": "^2.0",
        "friendsofphp/php-cs-fixer": "^2.16",
        "fzaninotto/faker": "^1.9.1",
        "mockery/mockery": "^1.3.1",
        "nunomaduro/collision": "^4.1",
        "phpunit/phpunit": "^8.5"
    },
    "config": {
        "optimize-autoloader": true,
        "preferred-install": "dist",
        "sort-packages": true
    },
    "extra": {
        "laravel": {
            "dont-discover": [
                "sentry/sentry-laravel"
            ]
        }
    },
    "autoload": {
        "psr-4": {
            "App\\": "app/"
        },
        "classmap": [
            "database/seeds",
            "database/factories"
        ]
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "minimum-stability": "dev",
    "prefer-stable": true,
    "scripts": {
        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover --ansi"
        ],
        "post-root-package-install": [
            "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate --ansi"
        ]
    }
}

It's a big Dockerfile so a bit impractical for me to try out, but there is 1 thing I notice, you copy the composer.json/.lock and run composer install and only then copy the application sources, possibly this could be an issue you could try to make sure all the application sources are in the container before running composer install.
I also can't see the config/sentry.php (if you have one) but if you have this code uncommented (it's commented by default) it tries to use Git to find a release version which might cause a error since the git repo (or maybe even the git binary) is not available inside your container:
   // 'release' => trim(exec('git --git-dir ' . base_path('.git') . ' log --pretty="%h" -n1 HEAD')),

It would really help to see the error output leading up to the non-zero code to see where it's getting stuck because I don't see much Sentry specific code running and I have no clue why a simple composer install would break otherwise.

I am closing this issue because of inactivity, if there is still an issue please re-open / open a new issue so we can investigate 👍


Improvements of docker environment

This PR tells docker-compose to use the official postgres image and adds ability to read email configuration from the EMAIL_URL env variable.

Current coverage is 48.27%

Merging #401 into master will increase coverage by +0.06% as of d3fe24a

@@            master    #401   diff @@
======================================
  Files           85      85
  Stmts         3385    3389     +4
  Branches       321     321
  Methods          0       0
======================================
+ Hit           1632    1636     +4
  Partial         29      29
  Missed        1724    1724

Review entire Coverage Diff as of d3fe24a

Powered by Codecov. Updated on successful CI builds.

:+1:


lntop - an interactive text-mode channels viewer for Unix systems

Great tool to view LND channels in realtime.
Manual instructions to install for now:
# install Go
config.scripts/bonus.go.sh on

# install with Go
go install github.com/edouardparis/lntop@latest

# or install from source
git clone https://github.com/edouardparis/lntop.git
cd lntop && go install ./...

Start once with (CTRL+C to exit):
/home/admin/go/bin/lntop

Edit the config file:
nano .lntop/config.toml

Use:
cert = "/home/admin/.lnd/tls.cert"
macaroon = "/home/admin/.lnd/data/chain/bitcoin/mainnet/admin.macaroon"

Start with:
/home/admin/go/bin/lntop

Once the tls.cert and admin.macaroon is copied over works great with a remote node also (modify the setting accordingly) - related https://github.com/rootzoll/raspiblitz/issues/2392

closing as the project is no longer maintained


find and findOne query fails with error

Repro steps:

Connect to a database
Open a scrapbook
Type any of the following queries:

db.user.findOne(<key>: <value>)
db.user.find(<key>: <value>)

Execute the MongoDB Command

Expect:
VSCode to display the JSON for the document
Actual:
Action: cosmosDB.executeMongoCommand
Error type: Error
Error Message: Error near line 0, column 23, text ':'. Please check syntax.
Environment:
Version: 0.7.2
OS: darwin
Insiders Build
Gush:
I love being able to do database stuff in Code, and it's one of the several things I brag about to other engineers when trying to convert them 😄

Hi Jason,
Thanks for the feedback! Appreciate it!
Do you have a sample value for the key and value?
We have seen a few users report a similar issue. Have you enclosed the strings in double quotes? We currently don't parse non-double-quoted strings well (JSON standards, etc.), see #466 and #467. We are working on fixing this, you can follow it at: #685 .
If the issue is not due to quotes, we'd appreciate a sample of what you pass as arguments - we're improving the parser with every release.

Here are a few samples that all fail with the error Error Message: Error near line 0, column 26, text ':'. Please check syntax.

db.user.find("userId": "6b0ab018-0872-4a19-9698-571a106dd837")
db.user.find("firstname": "Moana")
db.user.findOne("userId": "6b0ab018-0872-4a19-9698-571a106dd837")
db.user.findOne("firstname": "Moana")

and so on. Note that yesterday I tried double-quotes, single-quotes, no quotes (Robo 3T allows no quotes for the key), and all permutations thereof, and every attempt failed with either the above error or a similar one.
The key/value pairs are all copied directly from the database so I didn't mistype anything. For reference here is the sample, randomly-generated document I'm trying to query against:
  {
    "_id": {
      "$oid": "5af9ae8812b9a01200914c3a"
    },
    "userId": "6b0ab018-0872-4a19-9698-571a106dd837",
    "firstname": "Moana",
    "loginDates": [
      {
        "$date": "2018-05-02T03:37:41.319Z"
      },
      {
        "$date": "2018-04-26T23:58:02.221Z"
      },
      {
        "$date": "2018-04-11T19:53:33.404Z"
      },
      {
        "$date": "2018-03-23T17:31:00.669Z"
      },
      {
        "$date": "2018-03-21T20:41:04.707Z"
      }
    ],
    "contactType": null,
    "companyId": null,
    "address2": null,
    "admin": false,
    "createdAt": {
      "$date": "2018-05-14T15:43:04.136Z"
    },
    "updatedAt": {
      "$date": "2018-05-14T15:43:04.136Z"
    }
  }

I think you're just missing some curly braces.
db.user.findOne({ <key>: <value> })
db.user.find({ <key>: <value>})

so try db.user.find({ "userId": "6b0ab018-0872-4a19-9698-571a106dd837" })
Find accepts a query object and you're just passing strings separated by a colon.

Closing issue because I had the wrong syntax.
Haha, oops. Don't mind me 🐑
Thanks @fiveisprime! Missed some basic syntax.

Yay! Glad that solved it. 😄 Thanks for following up.


Add cpu & memory hot add enable option

PR add option to create vm with cpu & memory hot add enabled which can let users add cpu & memory on a running instance.
References:
cpu hot add enabled
memory hot add enabled

For now cpu can be increased from vsphere web client .

Can be enabled as a resource pool property
cloud_properties:
    cpu: 2
    ram: 4_096
    disk: 20_000
    cpu_hot_add_enabled: true
    mem_hot_add_enabled: true

Interesting. We'll pull it in: https://www.pivotaltracker.com/story/show/117369019
Out of curiosity when would you need this feature?

@cppforlife

Out of curiosity when would you need this feature?

sometime it is useful to increase cpu on run for debugging or incase there is high load and want to increase cpu at that moment instead of recreating the vm.
I will add another plug to this commit for memory hot add.
Also some future work will be needed when need to reconfigure the vm on run using bosh if these options are enabled, but that is out of scope of this PR.

@cppforlife Added the change and rebased, now this PR allows cpu & memory hot add plugs . Final for pulling in.

Hi @ronakbanka it turns out there are some failing unit tests. See the failing check below; the details for the "concourse:unit-tests" check will bring you to a Concourse pipeline with the output from failing unit tests.

@flawedmatrix There were some missing arguments for existing tests which are added in this PR.
Fixed.

@ronakbanka We recently finished a large refactor that made it difficult to merge this PR directly. We made the change out of band which you can see here. Closing this out, thanks for the PR!

@ljfranklin I had a look at changes and want to cross check one of the changes which was there original PR and not in the master commit .
here: https://github.com/cloudfoundry-incubator/bosh-vsphere-cpi-release/pull/6/files#diff-d67348453c426402f004a15d36658cebR4
because if you check the original properties on vmware references they have camel case naming .
Can you confirm it the cpi changes work on your side without vmodl helper changes??

@ronakbanka That bit of code confused us at first as well, we added a comment to clarify. The code does the camel casing automatically, but by default it gets confused if there are consecutive capital letters. For example, importVApp becomes import_v_app instead of the desired import_vapp. You only need to add an entry to that map in cases where a capital letter should not be preceeded by an underscore. The two new properties fortunately follow the normal pattern.


我无法使用密码"abc"打开output.pdf

您好
我使用origin/encryption生成了output.pdf，但是无法打开
uint8_t password[] = {""'a', 'b', 'c'""};
pdf_set_encryption(pdf, 0, password, sizeof(password), NULL,
0); // password, sizeof(password));
上面代码不是真实密码么？

Sorry I cannot read chinese.
Unfortunately, the code does not work, it is just an experiment. I haven't finished it yet and am not working on it at the moment.
抱歉我看不懂中文。
不幸的是，代码不起作用，它只是一个实验。 我还没有完成它，目前没有工作。

Thanks   (●'◡'●)

I'll close this issue for now - there is an existing issue #92 used to track encryption support. Please comment on that one if you would like to progress this further. Thanks.


pl.dir: convert dir.walk from coroutines to iterators, take 2

I missed converting dir.walk on my previous PR, sorry about that! Thanks @Tieske for jumping in and making a conversion, but that approach doesn't work — I did not dissect your algorithm fully because it was definitely faster to redo it from scratch than to debug the existing one, but I noticed you were not not keeping track of a stack of pending tasks. Coroutine-based algorithms for iterators effectively exploit the call stack as a data structure; when converting them to non-coroutine-based, you need to keep that data structure elsewhere.
I have not tested this extensively, but it passes both the tests and examples suites. I hadn't noticed the examples suite at all when I submitted #344 — thanks @alerque for the ping about it.
Fixes #348.

I went ahead an merged #349 in hope that it would then run on this PR, but it looks like that won't happen unless the commits change or somebody restarts the Travis job for the PR (not the push, the pr since that tests what a merge to master would look like). I don't have permissions on Travis for that.
I did checkout this branch locally and tested it there and it seems fine to me.


Documentation update about editable mode

Add info about path dependencies being installed in editable mode according to information here:
https://github.com/sdispater/poetry/issues/519#issuecomment-440028167
Pull Request Check List
This is just a reminder about the most common mistakes. Please make sure that you tick all appropriate boxes.  But please read our contribution guide at least once, it will save you unnecessary review cycles!

[x] Added tests for changed code.
[x] Updated documentation for changed code.

Note: If your Pull Request introduces a new feature or changes the current behavior, it should be based
on the develop branch. If it's a bug fix or only a documentation update, it should be based on the master branch.
If you have any questions to any of the points above, just submit and ask!  This checklist is here to help you, not to deter you from contributing!

Thanks!


fix: upgrade to version 3.1.346

from: https://github.com/jenkins-x/jx-cli

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign macox
You can assign the PR to them by writing /assign @macox in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

tls
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test tls

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

tls
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test tls

gsm
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test gsm

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test tls

/test kube

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

tls
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test tls

gsm
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test gsm

kube
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test kube

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

tls
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test tls

gsm
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test gsm

kube
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test kube

vault
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test vault

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test gsm

vault
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test vault

kube
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test kube

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

/test kube

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test gsm

vault
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test vault

kube
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test kube

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test gsm

vault
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test vault

kube
539a1e660c4cf486ff70e0eb0f80409ad2525d39
link
/test kube

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.


Initial pre-release

Design documentation #4 and basic library functions.

@loleg
I'm not able to review now. So I'm merging.
Please feel free to work on master here for now.


[Bug] demo not show menu

Describe the bug
react demo not show menu
To Reproduce
open https://milkdown.dev/zh-hans/react
Expected behavior
show editor menu
Screenshots

Desktop (please complete the following information):

OS:macos
Browser chrome
Version 101

Menu is a plugin and not installed in demo

@Saul-Mirone 怎么配置这个菜单啊，在官网上面也没看到

https://milkdown.dev/plugin-menu


[utils] fix windows console read

On windows freerdp_interruptible_getc did not work at all. Fix this so that reading characters works. This still does not hide input for passwords or is actually interruptible, but at least it reads the data correctly.

@freerdp-bot please test again


Add rustycl0ck as a maintainer

I would like to invite @rustycl0ck as a maintainer if they're interested.

Sure! With guidance from yourself and @roidelapluie, I'd be glad to be a maintainer for this.


[BD-46] resolve bootstrap conflicts with design tokens

Description
resolve some of the bootstrap conflicts with design tokens

Thanks for the pull request, @viktorrusakov!
When this pull request is ready, tag your edX technical lead.

@viktorrusakov 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

:tada: This PR is included in version 21.0.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Is it possible to redeclare class definitions to add new statics?

I'm trying to figure out how to add new statics to a class that is already declared by a library. For example, say we have the following:
// Third party library
class A {}
declare class A {}

// Other library adds new statics to A
A.foo = 'xyz'

// flow error
// property `foo`. Property not found in statics of A

I've tried redeclaring the A and add the statics myself, but that doesn't seem to be possible. What other options might I have?

Any news on this one?

This won't be supported


Invalid OpenAPI v2 Specification for Form Recognizer API

The OpenAPI v2 (Swagger 2.0) specification for the Form Recognizer API (version 2023-07-31) contains multiple errors that impede client code generation. The specification was sourced from this documentation page.
Upon validation, the file exhibits the following issues:

Schema validation errors in /documentModels/{modelId}:analyze.post parameters
Missing item definitions in query parameters
Unresolved references, e.g., "AzureBlobFileListSource"
Undefined required properties in "DocumentPage" definition

For full context, these are the errors when validating the file with go-swagger
$ swagger validate FormRecognizer_2023-07-31.swagger.json
The swagger spec at "FormRecognizer_2023-07-31.swagger.json" is invalid against swagger specification 2.0.
See errors below:
- "paths./documentModels/{modelId}:analyze.post.parameters" must validate one and only one schema (oneOf). Found none valid
- items in paths./documentModels/{modelId}:analyze.post.parameters is required
- paths./documentModels/{modelId}:analyze.post.parameters.in in body should be one of [header]
- some references could not be resolved in spec. First found: object has no key "AzureBlobFileListSource"
- could not resolve reference in "/documentModels:build".POST to $ref : object has no key "AzureBlobFileListSource"
- could not resolve reference in "/documentClassifiers:build".POST to $ref : object has no key "AzureBlobFileListSource"
- param "queryFields" for "AnalyzeDocument" is a collection without an element type (array requires item definition)
- "kind" is present in required but not defined as property in definition "DocumentPage"
- could not resolve reference in /info to $ref : object has no key "GetInfoResponse"
- could not resolve reference in /documentClassifiers to $ref : object has no key "GetModelsResponse"
- could not resolve reference in /operations/{operationId} to $ref : object has no key "GetOperationResponse"
- could not resolve reference in /documentModels/{modelId} to $ref : object has no key "ModelInfo"
- could not resolve reference in /documentClassifiers/{classifierId} to $ref : object has no key "AzureBlobFileListSource"
- could not resolve reference in /documentModels to $ref : object has no key "GetModelsResponse"

Thanks

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

ID: 8c5873f6-4bbb-1981-838c-3e84535b0143
Version Independent ID: 96824d5d-b00b-937f-ad11-a9d4fec1cd8f
Content: Document Intelligence (formerly Form Recognizer) v3.1 SDKs - Azure AI services
Content Source: articles/ai-services/document-intelligence/sdk-overview-v3-1.md
Service: azure-ai-document-intelligence
GitHub Login: @laujan
Microsoft Alias: lajanuar

@dtuit
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Hi @dtuit,
Thanks for your feedback.
You are correct. Here is a link to our official Swagger definition: azure-rest-api-specs/specification/cognitiveservices/data-plane/FormRecognizer/stable/2023-07-31/FormRecognizer.json at main · Azure/azure-rest-api-specs.
Thanks again! 🙂

#please-close


Return zero if value rounds away to zero

Currently, if you pass round: true and the value to be formatted is less than half of the smallest allowed unit, you get an empty string as result:
> humanize(500, {round: true});
'0.5 seconds'
> humanize(499, {round: true});
''

IMO this makes more sense:
> humanize(500, {round: true});
'0.5 seconds'
> humanize(499, {round: true});
'0 seconds'

(i.e. if we're on the last unit and we haven't added anything to the result yet, do it regardless of whether the unit count is zero)

Good catch—this is a bug.
Related question: right now, there's a bit of code that returns "0" if you pass exactly zero.
humanizeDuration(0)  // => "0"

What should happen there?

my preference would be to return 0 in the smallest allowed unit in either case - then it still reads as a duration, e.g.
humanizeDuration(0, {units: ['day']}); // => "0 days"

Agreed.

+1


Read annotation in doc comment for exception

Ocamldoc has special annotation @raise Invalid_argument that we can add in the doc comment.
And when building the doc we can see it. A example of the stdlib https://caml.inria.fr/pub/docs/manual-ocaml/libref/List.html#VALinit and in the code https://github.com/ocaml/ocaml/blob/trunk/stdlib/list.mli#L82. We can see that the Exception is highlighted in the generated html.
Atm reanalyze support only [@raise ] in the implementation file as attribute so it is not read by ocamldoc. It would be convenient if reanalyze could read doc comment and suggest to add in the comment. This way it help us to write good comment.

@Et7f3 one issue with doc comments is how to read them from libraries.
In the case of bucklescript, libraries are in a conventional place.
But in the case of native, libraries are wherever the build system looks for them (dune, or dune + esy), and it would be complex to replicate the same logic here.

one issue with doc comments is how to read them from libraries.

# (*comment*);;
# (**comment*);;
Ptop_def
  []
Ptop_def
  [
    structure_item (//toplevel//[1,0+0]..[1,0+12])
      Pstr_attribute "ocaml.text"
      [
        structure_item (//toplevel//[1,0+0]..[1,0+12])
          Pstr_eval
          expression (//toplevel//[1,0+0]..[1,0+12])
            Pexp_constant PConst_string("comment",None)
      ]
  ]

We can see that doc comment are preserved in the ast.
if comment are in interface file: then their is a .cmti/.cmi next to the implementation corresponding .cmt/.cmo.

it would be complex to replicate the same logic here.

So the logic is quite simple (remove the 'o' if it is last char and add 'i')

I think what's possible is a bootstrapping process, where doc comments can be used as a starting point. However, some manual tweaking has already been necessary:
    ("blit_string", [invalidArgument]),
    // ("concat", [invalidArgument]), if longer than {!Sys.max_string_length}
    // ("cat", [invalidArgument]), if longer than {!Sys.max_string_length}
    // ("escaped", [invalidArgument]), if longer than {!Sys.max_string_length}
    ("index", [notFound]),

where the commented-out functions would lead to mostly noise.


No License file

This project seems to be exactly the solution that I am looking for.  But it doesn't have a licence file, so not sure if I'll be able to use it.
Any chance you'd be able to include a license with the code?

Hey @steddy-inmarsat ,
sorry for sure, I provided MIT.
Cheers


Fix Larimer County, CO

Broken:
http://results.openaddresses.io/sources/us/co/larimer
not sure why current pull is failing. went to service and it works manually:
https://maps1.larimer.org/arcgis/rest/services/MapServices/Parcels/MapServer/0
New:
ftp://ftp.larimer.org/GISData/GIS_CadastralSHP.zip

Fixed.


EmbedBlock.Meta.help_text not used

Found a bug? Please fill out the sections below. 👍
Issue Summary
When subclassing the EmbedBlock and setting the help_text in the Meta class, this help text does not show up in the admin.
When providing the help_text argument to the constructor of the block it is used.
See this example from the bakery demo:
class CustomEmbedBlock(EmbedBlock):

    class Meta:
        help_text='Insert an embed URL e.g https://www.youtube.com/embed/SGJFWirQ3ks'
        icon="fa-s15"
        template="blocks/embed_block.html"

class BaseStreamBlock(StreamBlock):
    """
    Define the custom blocks that `StreamField` will utilize
    """
    heading_block = HeadingBlock()
    paragraph_block = RichTextBlock(
        icon="fa-paragraph",
        template="blocks/paragraph_block.html"
    )
    image_block = ImageBlock()
    block_quote = BlockQuote()
    embed_block = EmbedBlock(
        help_text='Insert an embed URL e.g https://www.youtube.com/embed/SGJFWirQ3ks',
        icon="fa-s15",
        template="blocks/embed_block.html")
    custom_embed_block = CustomEmbedBlock()

Steps to Reproduce

Subclass the wagtail.embeds.blocks.EmbedBlock
Define the Meta class with a help_text attribute.
Add this block to a stream field definition without arguments.
Open the Wagtail admin and create a page with the custom embed block in a streamfield.
Observe that when adding the custom block to the stream field the field is not showing the help text

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (yes / no)

Technical details

Python version: 3.9.9
Django version: 3.1.11
Wagtail version: 2.15.1 (and main)
Browser version: You can use https://www.whatsmybrowser.org/ to find this out.

This is because EmbedBlock is derived from URLBlock, which passes help_text directly from the constructor argument to the field object, without any intervention from the meta class:
https://github.com/wagtail/wagtail/blob/c54f7852d04316279fe9d4a3ab2b3a751e5df18f/wagtail/core/blocks/field_block.py#L237-L244
I don't think this counts as a bug though - there's nothing in the docs that suggests that subclassing EmbedBlock or any other FieldBlock-derived block type is a supported mechanism.

@gasman Hm, interesting. True, I had not checked if this is a documented behaviour. I just assumed that it works like that because it does for the structural block types.
I am happy to convert this from a bug report to a feature request, as I think it makes sense to have the help_text be consistent with other attributes like icon or template, which can be defined in the EmbedBlock.Meta class.

OK, yep, that sounds fair enough. There are some extra considerations around migrations when subclassing other block types, detailed in https://docs.wagtail.org/en/stable/advanced_topics/customisation/streamfield_blocks.html#handling-block-definitions-within-migrations, so I'm not sure that this is something we want to actively encourage as part of the documented API - but as long as that note remains in place in the docs I guess we can support it for 'power users'.


rolling_update: do not fail on missing keys

We don't want to fail on key that are not present since they will get
created after the mons are updated. They will be created by the task
"create potentially missing keys (rbd and rbd-mirror)".
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1650572
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>

What was the stable-3.2 change for this? There's no cherry-picked-from line.


No data-collector config for Automate-installed Chef Server

:nut_and_bolt: Description: What code changed, and why?
data-collector config not needed for Chef Server installed with Automate
Signed-off-by: Sean Horn<EMAIL_ADDRESS>:chains: Related Resources
:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change
:white_check_mark: Checklist
All PRs must tick these:

[X] I have read the CONTRIBUTING document.
[X] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[X] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[X] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[X] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[X] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[X] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

[ ] Tests added/updated? (all new code needs new tests) no test, just docs
[X] Docs added/updated? (all customer-facing changes)

These failures in the pipeline are unrelated to my change which was only for docs


Enable passing secrets to action server.

Related to https://github.com/Sema4AI/langchain/pull/1

@bakar-io How about if we add "additionalHeaders" or similar key to the config with key:value pairs as the value.
Then you can place there whatever headers with their values.
The value could then be directly stored as it is sent in the db and handled on the calling side. This might also make it easier to later have testing capabilities related to Action Server calls that are not directly linked to OpenGPTs backend.

@bakar-io How about if we add "additionalHeaders" or similar key to the config with key:value pairs as the value. Then you can place there whatever headers with their values.
The value could then be directly stored as it is sent in the db and handled on the calling side. This might also make it easier to later have testing capabilities related to Action Server calls that are not directly linked to OpenGPTs backend.

That was one of the options considered. Spoke with Kari this morning and he was conflicted between these two options.
'
Can you elaborate on "The value could then be directly stored as it is sent in the db and handled on the calling side."

"The value could then be directly stored as it is sent in the db and handled on the calling side." === I would like as little logic to OpenGPTs backend as possible.


Event page improvements

Reorder event tabs w/ Rankings first
Change "Results" tab to "Matches" for clarity
Set default active tab to be most useful tab
Teams if only team info exists
Matches if only match schedule exists
Rankings otherwise
Add # of entries in each tab (like teams) so users see which tabs are populated without having to click them.

Brings up Teams by default if no other data exists.

Brings up Rankings by default if full data is available.
Also will bring up match schedule by default if teams and matches exist but no rankings exist.


[CU-868az9udm] Removes localStorage filtering in tool feed pages

Task linked: CU-868az9udm Image feed filters apply to Collections and Tool pages


Hangman: Only English Characters

Closes https://github.com/DevChatter/devchatterbot/issues/265
Checks to make sure guesses are English letters. Tested with emojis, symbols and numbers.

OK I made a bit of a pig's ear of that one but commit is looking right now. This change implements a large number of changes to the hangman commands. Allowed characters are now configured on the DB and only passwords which only contain the allowed characters will show.  This should help support multicultural letters.  A small spelling error was spotted while I was making this commit and I've removed an unnecessary variable.


torch.cat(): expected a non-empty list of Tensors

Repeatedly getting this error after using all example workflows and installation instructions.  Any ideas?

I have the same error too

Please ask the open-source author to solve the problem. Thank you

What kind of garbage author and open source project closed without solving the problem?


Add organisations?

One additional question - now that I can see all the issues from my repositories - how c an I add Organisations to it?

I'm not sure Cashew supports Organisations, but I haven't looked into it much. The codebase is still really new to me. What kind of organisation support are you after specifically?

It has a point “If you don’t see your organisation’s repositories. click here” in the Repository Picker, and this re-directs to an expired domain (cashew.app I think). So it should work. I think it might be an issue with authentication in GitHub? Any chance of getting hold of the original web site?

On 20 Mar 2019, at 06:14, bellebethcooper<EMAIL_ADDRESS>wrote:
I'm not sure Cashew supports Organisations, but I haven't looked into it much. The codebase is still really new to me. What kind of organisation support are you after specifically?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/bellebethcooper/cashew/issues/68#issuecomment-474687472, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdvBBu0W4lOAdG835TDyrlAM4C7wyQYks5vYcOmgaJpZM4b7ffS.

--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)
Department of Evolutionary Biology and Environmental Studies
University of Zürich
Office Y34-J-74
Winterthurerstrasse 190
8075 Zürich
Switzerland
Office:	+41 (0)44 635 47 64
Cell:       	+41 (0)78 630 66 57
email<EMAIL_ADDRESS><EMAIL_ADDRESS>Skype:     RMkrug
PGP: 0x0F52F982

Ah, I see. No, I don't have access to the original site. I don't have anything to do with the original creators. It looks like it's just a dead link to a help page, so there's probably some info on the GitHub site about working with private organisations and 3rd party apps. I'm happy to take a PR if you or someone else wants to add a link to this info on the GitHub site or add some help copy to the app itself.


[$500] Android-Room-Enter multi-line description, shows dots in header below title

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.37 -0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation:
Action Performed:

Launch app
Tap on a room chat
Tap header
Tap room description
Enter a multi-line message, in that enter first line message as 1 or 2 character( eg: 4,y, fg, 23)
Tap back button
Note room chat header

Expected Result:
When we enter multi-line room description with first line message as 1 or 2 character, only dots must not be shown in header below title.
Actual Result:
When we enter multi-line room description with first line message as 1 or 2 character, only dots shown in header below title.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/e5f24783-bf48-4baf-a5ad-e0d4a65d44e8

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0115b48f34c4193ce8
Upwork Job ID:<PHONE_NUMBER>633886720
Last Price Increase: 2024-02-07

We think that this bug might be related to #vip-vsb
CC @quinthar

Hey @fedirjh we have a proposal here, can you review when you get a sec?

Not able to reproduce this, even on Android.

Yeah this feels like expected behavior to me also. Given that this does not fit in with a product wave,  I am gonna close this


Removed ended LTS versions django

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (0ca1a20) to head (8d962c0).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main        #3   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines           93        93
=========================================
  Hits            93        93

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix locale parsing

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

The locale module has been parsing locale strings in the wrong format. The correct format is "language-script-region" instead of "language-region-script". This wrong format broke the system language parsing.
> defaults read -g AppleLanguages
(
    "zh-Hans-CN"
)

Besides the real output above, you can also refer to: https://en.wikipedia.org/wiki/IETF_language_tag#Syntax_of_language_tags.

Are there any casks using the script in lang stanzas?

Thanks so much for your first contribution (hopefully of many)!  You rock, @stevenlele!


[Enhancement] Support the creation of lake table in pseudo cluster

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

starrocks_be_unittest succeeded.

starrocks_be_unittest succeeded.

starrocks_be_unittest succeeded.

starrocks_be_unittest succeeded.

starrocks_be_unittest succeeded.

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
2
2
100.00%
[]

run starrocks_admit_test


GitHub Raffle at Hackcon 2024 - Leave a comment to enter

Random Name Picker for GitHub prize draw at Hackcon 2024!

:pray: First, huge shout-out to @icelam for a great and simple name picker we could fork and use for the GitHub booth!
:rocket: This site is deployed to GitHub Pages using GitHub Actions. The Actions workflow pulls entrants from commenters of a GitHub Issue.
:ticket: To enter the draw, add a comment at the bottom of this issue 👇
🏆  The prize will be drawn on

August 23 at 10:00 PM
August 24 at 7:30 PM
August 25 at 12:00 PM

Check out the original README

A couple of T&C's:

Entry into this raffle will NOT constitute your consent to be contacted for anything else
We will not be adding you to our marketing database (but if you want to subscribe to our newsletter, you can do so here)
The raffle prize cannot be swapped or changed,
The winner of the prize at Hackcon MUST be present when we draw a winner, otherwise we will redraw!

Good luck!

Definitely not testing if this works!

First comment! ♥✨

Using Github helped me survive my internship 🤯

Its Nishchit here…..

Chinat LFG!!

first (ignore all above)

Heyy, saludos desde Shellhacks 🐚🏖

Reppin' Shell!! 🐚🌴 Join us in a month: shellhacks.net/

Hey, from GDSC Hacks 💪

Love Github

Muahahahah

git push --force origin master does not scare me 🤩

 yipppeeeeee!

hackru!
thehackru on all your favorite socials 🦅🦅🦅

UMD represent!

Hackcon is awesome :D

I love stickers

I want to win (please)

Hi hackcon

Looks good to me!

:)

Here's what GitHub taught me about B2B sales:

Hello from WaffHacks

Github was my childhood

Hey from St. John’s University! HackSJU coming soon 👀

Hey from St. John’s University!

Hiiiiii from St. John’s :D

BostonU letsgooo Terriers!! 🐾🐾

Hellooooo

Hey y’all!!
We are moving today raffle for tomorrow at 3 pm and another at 7:30.
Enjoy the night y’all 🔥🔥

Yayyy Hackon!

🔥🔥

GitHub!!

hello from sunhacks!

Meowwww

Hello from HackUPC team! We hope see you all in Barcelona in may!!

git commit -m "Hello from HackUPC"

git push

Hello from HackViolet at Virginia Tech!!!😆

LOVE GITHUB
Don't git push --force yall

Hello from nwPlus UBC!

im batman

LGTM 👍

Hackcon checkin! 💖

Commenting! 👍

Hello!

Hola! Hackcon is awesome!

Hello!

hello from nwPlus !

Layke from A&T was here 😎

Hello!

The goats!

wow! i love github

yay mlh!

uOttahack for the win

emilio estevez

Come to HackKU 25!!

HackKU for the win!!!

hackku.org

Come to HackTX

GirlHacks September 28th at New Jersey Institute of Technology

Add your comment here…

hackuta 2024 dee dee

yippee from bostonhacks

dhravya from sunhacks

Hackcon 24!!

here for pj!

Hello Hackconn!

Hello 👋

Haiiii 👀👋

hi hackcon!

commenting!! :)

let’s goooooo

DYLAN VIDAL WILL WIN

DELTAHACKS ROCKS

LET'S WIN

Thank you all for participating ❤


[3pt] Simplify names of necessary-for-inundation files

For example, change "gw_catchments_reaches_filtered_addedAttributes.tif" to "catchments.tif"

@nickchadwick-noaa please get with @LauraKeys-NOAA and @CoreyKrewson-NOAA to decide on these file names.

This issue is being addressed in #88


Fix cross compilation breakage

happened becasue of two independent commits

Signed-off-by: Alessandro Boch<EMAIL_ADDRESS>

LGTM


Band-aid NS REGISTER fix

Addresses #410 in a temporary way. Honestly, this has told me that I'm not at all happy with the current NS REGISTER command, so for v1.1.0 I reeeally want to overhaul it entirely and replace it with something more standard.

Nice. Yeah, let's continue discussion over on #410.


[Workflow] Add python to patterns doc

What content needs to be created or modified?
Add Python tab to patterns doc
Where should the new material be placed?
https://v1-11.docs.dapr.io/developing-applications/building-blocks/workflow/workflow-patterns/

@hhunter-ms Also need to update the supported SDKs here https://docs.dapr.io/developing-applications/building-blocks/workflow/workflow-overview/#workflow-sdks to include python

@hhunter-ms Also need to update the supported SDKs here https://docs.dapr.io/developing-applications/building-blocks/workflow/workflow-overview/#workflow-sdks to include python

looks like this was already added for 1.11: https://v1-11.docs.dapr.io/developing-applications/building-blocks/workflow/workflow-overview/#supported-sdks

Just noticed the python-sdk doc PR - reopened to track that

dapr/python-sdk#575

https://github.com/dapr/python-sdk/pull/575 has been merged. I think we're good to close this now.

@cgillum - Thanks. Closing


failed to add the host (veth2df6899) <=> sandbox (veth5480d98) pair interfaces: operation not supported

I setup a new Raspberry OS using rpi-imager and followed the blog post on a Raspberry Pi 3. internet-monitoring isn't able to start with docker-compose up -d. This error also shows up in JSON in ansible-playbook main.yml.

pi@raspberrypi:~/internet-monitoring $ docker-compose up -d
Starting internet-monitoring_ping_1      ... error
Starting internet-monitoring_speedtest_1 ...
Starting internet-monitoring_nodeexp_1   ...

Starting internet-monitoring_speedtest_1 ... error
(veth95bb9fb) pair interfaces: operation not supported

ERROR: for internet-monitoring_speedtest_1  Cannot start service speedtest: failed to create endpoint internet-monitoring_speedtest_1 on network internet-monitoring_back-tier: failed to add the host (vethb9d885Starting internet-monitoring_nodeexp_1   ... error

ERROR: for internet-monitoring_nodeexp_1  Cannot start service nodeexp: failed to create endpoint internet-monitoring_nodeexp_1 on network internet-monitoring_back-tier: failed to add the host (veth2ff6291) <=> sandbox (veth09de4a7) pair interfaces: operation not supported

ERROR: for ping  Cannot start service ping: failed to create endpoint internet-monitoring_ping_1 on network internet-monitoring_back-tier: failed to add the host (veth3b16487) <=> sandbox (veth95bb9fb) pair interfaces: operation not supported

ERROR: for speedtest  Cannot start service speedtest: failed to create endpoint internet-monitoring_speedtest_1 on network internet-monitoring_back-tier: failed to add the host (vethb9d8856) <=> sandbox (vethf9a355b) pair interfaces: operation not supported

ERROR: for nodeexp  Cannot start service nodeexp: failed to create endpoint internet-monitoring_nodeexp_1 on network internet-monitoring_back-tier: failed to add the host (veth2ff6291) <=> sandbox (veth09de4a7) pair interfaces: operation not supported
ERROR: Encountered errors while bringing up the project.

Same issue.
No workaround ?

My workaround was to buy a Raspberry Pi 4

A reboot fixed this for me. If that didn't work, I was going to try out the solution mentioned here: https://askubuntu.com/questions/1372912/pair-interfaces-operation-not-supported-error-in-docker

A reboot fixed this for me. If that didn't work, I was going to try out the solution mentioned here: https://askubuntu.com/questions/1372912/pair-interfaces-operation-not-supported-error-in-docker

Thanks; it fixed my issue too !!


Set Up Business Process Management Services in Cloud Cockpit

Tutorial URL: https://developers.sap.com/tutorials/cp-starter-ibpm-employeeonboarding-1-setup.html
Please specify the step you are referring to: 8
I've created the Destination as is explained at step 8, however later, when I run the workflow instance, I got this error message:
Error message:
The OAuth token request to URL 'https://0eee2d8btrial.authentication.eu10.hana.ondemand.com/oauth/token?grant_type=client_credentials' failed with HTTP status code 401 (Unauthorized) and response body '{"error":"unauthorized","error_description":"Bad credentials"}'
Please let me know how I can check what I'm doing wrong.
Thanks

Please check your token service URL. It's must not not correct. In the end its should have /oauth/token for example: Token Service URL should be: https://p787658trial.authentication.eu10.ondemand.com/oauth/token (also check the setup chapter, its clearly mentioned there)

Hello,
I've rebuilt all the components/services/destinations... and now it's working properly. Thanks!


Improve sentence tokenization

Should use a tokenizer library to handle edge cases.

https://github.com/diasks2/pragmatic_segmenter/blob/master/README.md#the-golden-rules

Decided against doing this for now, due to performance, file size, and html tag issues.


[Maintenance] Allow flex plugin during plugin installation

Q
A

Branch?
1.4

Bug fix?
yes

New feature?
no

Related tickets
Follow up of https://github.com/Sylius/Sylius/pull/14106

Fixed in https://github.com/Sylius/PayPalPlugin/pull/254, thank you Łukasz! 🖖


How to add a component to a default install?

Hi,
I just got kubernetes up and running and noticed that the graph component isn't in the default installation. Is there some documentation on how to add this or any component to a default installation?
Thanks!

Hello @sheriffmohamed @jackgr is working on documenting the steps needed.

Great! Thank you. @jackgr I'm assuming the steps are still being worked on?


feat: fee model implementation

Description

implementation of fee model, not yet consumed
https://ipfs.io/ipfs/QmVsox8WdUhpWK35Pm3LvmSGGwtzSMFwwWojWJ7K8Dat7s
Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

n/a
Risk
incorrect fee calcs, the fee boogeyman scares everyone away

Testing

Engineering
see test cases, compare to curve in proposal for sanity

Operations
not testable by ops

Screenshots (if applicable)
n/a

Current dependencies on/for this PR:

develop

PR #5353   👈

This comment was auto-generated by Graphite.


How to use vueuse/head?

Since the renderToHtml call is inside the module, would it be possible to install and use https://github.com/vueuse/head?

@thalesagapito I'm integrating vueuse/head in a local branch already and will probably merge it this week. For now, there's a component called Helmet to do the same thing. Example here.

Cool! Nice work, I'll close this for now then, and wait for the integration

@thalesagapito Released in 0.5.0!
import { createHead } from '@vueuse/head'

export default viteSSR(App, { routes }, ({ app }) => {
  const head = createHead()
  app.use(head)

  return { head }
})


go_*: don't force gcc8 on aarch64-linux

Description of changes
This was originally set in #68029 and has been copied along since, but it's probably not needed anymore.
I've run some tests, but would definitely like some other people to verify this.
This should be a no-op on anything that's not aarch64-linux, so IMO could go directly to master, but if anyone disagrees, I'm happy to retarget to staging.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I tried this last year, seems it was still needed.
@ofborg build go_1_16 go_1_17 go_1_18 go_2-dev

1.18 builds but the others have test failures. The go 2  derivation is really outdated and needs several other fixes applied anyway that I've been meaning to get to, 1.16 is EOL and 1.17 will be EOL in 5 months. If you don't want to bother with fixing tests we can just drop it for 1.18 and leave the others as they are.

1.16 is EOL

Are there any plans on removing it before 22.05 or is that infeasible?

we can just drop it for 1.18 and leave the others as they are

done. I just want this to be fixed going forward. IMO keeping the status quo for the old versions is fine.

Are there any plans on removing it before 22.05 or is that infeasible?

Maybe, there are a dozen or so packages that still depend on it. IIRC a few of them are non-trivial fixes. I'd be fine with just marking them all as broken and removing 1.16 but that'll likely annoy a few people.

Thanks!


Stay in cask repo when repairing

For a first-time user, this instruction leaves them in
/usr/local/Homebrew unexpectedly. Everything works fine... it's just
weird.
The only important think about being in brew --repository is that it
is known to be a gitlab repo, so it's a good, confident bet, fine to
keep using.
But by running this in a subshell, it will keep the user in their
existing directory

Agreed. Thank you.


nixos/firejail: add example for wrappedBinaries

Motivation for this change
It's not very obvious how to use programs.firejail.wrappedBinaries. See also https://discourse.nixos.org/t/firejail-seems-uneffective/3756
Things done

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

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

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

cc @peterhoeg

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/firejail-seems-uneffective/3756/3


[Wayland] Magic Connector and Format Painter cursors are too small at 200% scaling

Archi 4.8.1
Ubuntu 20.4 with Wayland at 200% scaling
The Magic Connector and Format Painter cursors are too small at 200% scaling.
When we create a cursor on Linux X11 (and Mac) we get the image data at 100%. This is different in Wayland and we need to get the image data at 200%.
I have a fix for this - query the environment variable XDG_SESSION_TYPE which will return x11 or wayland. From this we can determine what image data scaling to use.

Fixed


Roadmap

This repo now has few more maintainers (including myself).
Before making any big changes would like to:
Say Hi

hi

Make a todo list

[ ] Add some CI and browser testing
[ ] Fix https://github.com/eligrey/classList.js/issues/48
[ ] Publish a new version
[ ] Close my fork https://github.com/yola/classlist-polyfill/issues/9
[ ] Cleanup whitespace
[ ] Rewrite tests
[ ] Minify via npm prepublish
[ ] Start addressing open issues

Flesh out any preferences, paint a bikeshed
When writing JS I generally stick to airbnb-ish style.
For testing, prefer Mocha+chai (with karma running the tests) instead of QUnit.
Prefer plain old shell or JS scripts instead task managers.

I fixed #48 in the "Consolidated closures" commit in #53.

@stevenvachon another preference is for single-purpose pull requests.
I agree with @eligrey about #53. IMO it does too much at once. Before the closures can be consolidated, lets cleanup the whitespace. Before we touch every line with whitespace cleanup, lets get the tests in working condition.  I would expect a fix for #48 to have a diff of ~2 lines, something like:
-}(self));
+}(typeof self !== 'undefined' ? self : this));

The whitespace commit occurs before the closure consolidation commit.

-}(self));
+}(typeof self !== 'undefined' ? self : this));

This is what I do with every polyfill I deal with.
BTW I'm gonna send a PR regarding !a===!b at the bottom of the polyfill, tha last thing which is a thorn.

@stevenvachon:

another preference is for single-purpose pull requests.

I agree ... about #53. IMO it does too much at once.

That's @beck responding to:

I fixed #48 in the "Consolidated closures" commit in #53.
I fixed whitespace in the "Whitespace fixes" commit in #53.
I rewrote the tests in the "Improve tests" commit in #53.

He's telling you he would like those to be separate PRs, not just separate commits. Condescension is not an appropriate response.

He's telling you he would like those to be separate PRs, not just separate commits. Condescension is not an appropriate response.

And I'm telling him and anyone else that they can go through the commits. I have little interest in redoing my PRs after all this time.


TestFileReaderSeek fails on go1.18

$ go test -run TestFileReaderSeek
--- FAIL: TestFileReaderSeek (0.00s)
panic: runtime error: slice bounds out of range [13313:13312] [recovered]
        panic: runtime error: slice bounds out of range [13313:13312]

goroutine 7 [running]:
testing.tRunner.func1.2({0x7fb820, 0xc00002e198})
        /usr/lib/go-1.18/src/testing/testing.go:1389 +0x24e
testing.tRunner.func1()
        /usr/lib/go-1.18/src/testing/testing.go:1392 +0x39f
panic({0x7fb820, 0xc00002e198})
        /usr/lib/go-1.18/src/runtime/panic.go:838 +0x207
github.com/distribution/distribution/v3/registry/storage/driver/inmemory.(*file).ReadAt(0xc0008912c0?, {0xc000380000?, 0x0?, 0x0?}, 0x0?)
        /home/zhsj/go/src/github.com/distribution/distribution/registry/storage/driver/inmemory/mfs.go:287 +0x7a
io.(*SectionReader).Read(0xc0008a2060, {0xc000380000?, 0x0?, 0x1000000000000?})
        /usr/lib/go-1.18/src/io/io.go:512 +0x54
bufio.(*Reader).Read(0xc0000385a0, {0xc00089c390, 0x10, 0x1?})
        /usr/lib/go-1.18/src/bufio/bufio.go:236 +0x1b4
github.com/distribution/distribution/v3/registry/storage.(*fileReader).Read(0xc00031def8, {0xc00089c390, 0x10, 0x10})
        /home/zhsj/go/src/github.com/distribution/distribution/registry/storage/filereader.go:63 +0x62
github.com/distribution/distribution/v3/registry/storage.TestFileReaderSeek(0xc0001191e0)
        /home/zhsj/go/src/github.com/distribution/distribution/registry/storage/filereader_test.go:142 +0xa85
testing.tRunner(0xc0001191e0, 0x857278)
        /usr/lib/go-1.18/src/testing/testing.go:1439 +0x102
created by testing.(*T).Run
        /usr/lib/go-1.18/src/testing/testing.go:1486 +0x35f
exit status 2
FAIL    github.com/distribution/distribution/v3/registry/storage        0.010s

We don't have any immediate plans to move to Go 1.18 at the moment. Feel free to open a PR, though.

I think for the main branch, it'd make sense to switch to (or at least start testing) on go1.18

I think for the main branch, it'd make sense to switch to (or at least start testing) on go1.18

We should defo look into it --  as I said, we're not against it but let's see when it happens. I wonder how much other stuff could get borked by the switch...I suspect this issue has been uncovered by fuzzing in 1.18 -- previous version didn't complain 🤔


Problem with ghcide, NixOS, cabal and cradle

I've been trying to migrate my development from Ubuntu to NixOS. No issues with my project and ghcide on Ubuntu. However, when I build my project on NixOS using "cabal new-build", I get an error about missing zlib:
Configuring library for zlib-<IP_ADDRESS>..
cabal: Missing dependency on a foreign library:
* Missing (or bad) header file: zlib.h
* Missing (or bad) C library: z

I fixed that by creating nix files with all the dependencies and building my project via nix-shell. However, my ghcide cradle is still defined as:
cradle: {cabal: {component: "MyProject"}}
Which fails for the same reason - unavailable zlib. Is there a way to instruct the cradle to go via nix-shell ?

This is editor specific. For Emacs I would use direnv, in VSCode I've had success with https://marketplace.visualstudio.com/items?itemName=arrterian.nix-env-selector

Thanks, I use VSCode, but wasn't successful enough with the extension you've mentioned. I'll keep on trying though.

You could just open vscode inside nix-shell using its command-line tool code

As I'm pretty new to nix(OS), can you tell me how to do this ? I've tried both "nix-shell code" and "nix-shell ~/.nix-profile/bin/code" without a much success.

@bratfizyk Personally, I have a shell.nix or default.nix in my project that declares the necessary dependencies.
Then I drop into that shell via nix-shell. After that you have a shell where your dependencies are available. You can just type code . or codium . and it should work.

@fendor Thanks, that sounds much clearer to me now. I made one step forward, but still no good.
Here's my shell.nix:
{ nixpkgs ? import ./pkgs.nix {} }:
let
  inherit (nixpkgs) pkgs;
  inherit (pkgs) haskellPackages;

  haskellDeps = ps: with ps; [
    aeson base bytestring Cabal cassava containers dates directory
    esqueleto http-api-data lens lucid monad-logger mtl persistent
    persistent-sqlite persistent-template regex-posix resourcet servant
    servant-lucid servant-server text time transformers unliftio-core
    utf8-string vector wai warp wreq
  ];

  ghc = pkgs.haskell.packages.ghc865.ghcWithPackages haskellDeps;

  nixPackages = [
    ghc
  ];
in
pkgs.stdenv.mkDerivation {
  name = "snadbox-haskell-workspace";
  buildInputs = nixPackages;
}

What I get from ghcide is error: "Cannot satisfy -package-id Cabal-<IP_ADDRESS>". I get the same error in both cases, e.g.

while running VSCode with nix-env-selector extension pointing to my shell.nix.
while running code after executing "nix-shell shell.nix".

I guess that means something's wrong with my shell.nix file. Any obvious mistakes there ?
Also, I've got slightly different files defined with cabal2nix ("default.nix"):
{ mkDerivation, aeson, base, bytestring, Cabal, cassava, containers
, dates, directory, esqueleto, http-api-data, lens, lucid
, monad-logger, mtl, persistent, persistent-sqlite
, persistent-template, regex-posix, resourcet, servant
, servant-lucid, servant-server, stdenv, text, time, transformers
, unliftio-core, utf8-string, vector, wai, warp, wreq
}:
mkDerivation {
  pname = "FortPolio";
  version = "<IP_ADDRESS>";
  src = ./.;
  isLibrary = false;
  isExecutable = true;
  executableHaskellDepends = [
    aeson base bytestring Cabal cassava containers dates directory
    esqueleto http-api-data lens lucid monad-logger mtl persistent
    persistent-sqlite persistent-template regex-posix resourcet servant
    servant-lucid servant-server text time transformers unliftio-core
    utf8-string vector wai warp wreq
  ];
  license = "MIT";
  hydraPlatforms = stdenv.lib.platforms.none;
}

I use it via another file called "release.nix"
let
    pkgs = import ./pkgs.nix { };
in
    pkgs.haskellPackages.callPackage ./default.nix { }

(pkgs.nix is just a pinned nixos-20.03). This file causes the entire project to build just fine when used via: nix-build release.nix. However, doesn't work for ghcide.

After some time researching the problem I think it can be summarized as follows:

all fine when using "nix-build ./release,nix" - it builds fine and outputs a binary
executing "nix-shell ./release.nix" and then "cabal new-build" doesn't work.

Is there anything else that nix-build does and nix-shell doesn't do ?

Update from my side: I've just migrated from nixos-20.03 to nixos-20.09, which contains ghcide version 0.3.0. Migrating to the newer version solved my problem and I can now use ghcide in VS Code following the hints you had provided here. Many thanks for the help.


fix: opening sidebar resets scroll position

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix

Context

[x] Closes #5565

Changes

autoFocus causes document.documentElement.scrollTop to always be reset to 0, so I disabled it first.
The changes above may cause the modal-background to go out of view, because the default position of modal-background was previously based on document.body instead of window. Therefore, I changed it to fixed so that no matter where the scrollbar is, it can ensure that the modal-background covers the entire screen.

Had issue bounty label?

[x] Fill up your KSM address: Payout

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

https://user-images.githubusercontent.com/128157824/232310538-8fadad96-742b-437a-9412-bbbb8f33511b.mp4

yup, works fine, can you please apply the same behavior to the notification sidebar as well @leo-anderson-x

pay 10 usd

😍 Perfect, I’ve sent the payout
💵 $10 @ 35.93 USD/KSM ~ 0.278 $KSM
🧗 DzUbHCk3Fr3XdCPNKo7uCJvtBH7YfgiFbn4Gr3VmCMiFy1C
🔗 0x2a048bbbb0d74cba8a9b124ac15ff72617ac73d9cc330f51090147328cb5a76a
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


[Compilation] GDB patch broked the compilation

build/libyaul/release/common/gdb/sh2-704x.o
common/gdb/sh2-704x.c:16:30: error:  ':' without preceding '?'
common/gdb/sh2-704x.c: In function 'device_init':
common/gdb/sh2-704x.c:554:30: error:  ':' without preceding '?'
common/gdb/sh2-704x.c: In function 'device_read':
common/gdb/sh2-704x.c:564:30: error:  ':' without preceding '?'
common/gdb/sh2-704x.c: In function 'device_write':
common/gdb/sh2-704x.c:574:30: error:  ':' without preceding '?'
make[1]: *** [/home/shazz/libyaul/build/libyaul/release/common/gdb/sh2-704x.o] Error 1
make[1]: Leaving directory `/home/shazz/libyaul/libyaul'

remove ":" at the end of the elif

What a horrible mistake. This is what happens when I write too much Python and don't compile for other cases.


Update jquery.listing-actions.js

1. Why is this change necessary?
Bugfix for $.overridePlugin
2. What does this change do, exactly?
Changes this to me
Adds a subscriber
3. Describe each step to reproduce the issue or behaviour.
create a jquery.xx.js file and fill it with
/* integrates automatic submit */
(function ($, window) {
  $.overridePlugin('swListingActions', {
    disableActiveFilterContainer: function () {
      var me = this;
      disabled = false;
      me.superclass.disableActiveFilterContainer.apply(disabled);
  });

  var filterBtn = $('.filter--actions.filter--actions-bottom');
  filterBtn.hide();
  $('form#filter input').bind("change",function(){
    $.loadingIndicator.open();
    $('form#filter').submit();
  });
})(jQuery, window);

4. Please link to the relevant issues (if any).
///
5. Which documentation changes (if any) need to be made because of this PR?
///
6. Checklist

[x] I have written tests and verified that they fail without my change
[X] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21389
Please use this issue to track the state of your pull request.

Hi @jinnoflife, your change got merged in 26a5c3c4d59, thank you for your contribution! 💙


Refresh only refreshes current page

Description
When using refresh from useInstantSearch only the current page is refreshed instead of all pages. Algolia seems to refresh all pages that are loaded.
Steps to reproduce
use useInfiniteHits or paginate to e.g page 2 call refresh
Expected Behavior
all loaded pages get refreshed when calling refresh()
Actual Behavior
only current page gets refreshed.
Metadata
26.0
OS:

The more I stare at this the more I think its an issue with instantsearch.


Bolts: Fetch turtle club user activity

Fuul needs an API which returns all active users in our Turtle Club campaign
See discussion in Telegram

Information from Turtle sent to fuul


Link to the docs is incorrect

Here the link: https://github.com/adafruit/Adafruit_CircuitPython_OAuth2/releases/tag/1.0.14 returns a 404 error

Looks like a capitalization issue, fixed now.  Thanks for catching!


Documentation improvements

I'd like to apply "Improves documentation", but not "Fixes typos", can you resubmit the first one ?
Cheers,


npm run config fails reproducible (locally + Cloud9) with default settings

Running npm run config fails reproducible when following the deploy instructions.
I get the following error:
Could not complete the operation.
Cannot set properties of undefined (setting 'default')

I verified npm run config failing in different environments and configurations

node v18 & v20
Cloud9 & locally
Default config values vs custom config

Steps to reproduce:

Clone the repository and checkout main. This will point to v3.1.3 of the aws-genai-llm-chatbot
Follow the instructions for Cloud9 / local deployment
Use default values for all inputs

v4.0.14 works, but main still points to v3.1.3 so this likely affects everyone following the deploy instructions in the docs

Workaround

Download v4.0.14 or higher manually from here
Unzip
Continue with Step 2 of the deployment

Added a fix in #594

That was fast. Thanks!

Well, when I run "npm run config" in Cloud9 in eu-central-1, selecting RAG with Knowledge base, it exits without asking me to save a config file and no config.json is created. Same with "npm run create". I suspect it is related to the change done to config.ts for this fix.

Thanks @charles-marion. The fix works fine. However, when I create a bedrock based RAG configuration, it does not ask me for the embedding model (embeddingModels[]) to use. As a result, the cdk bootstrap operation falls later with "no embedding model set".
A work around is to change one of the embeddingModels[].default to true.

Added a fix in the PR https://github.com/aws-samples/aws-genai-llm-chatbot/pull/598 .
Please use the work around listed above until merged.

Thank you for reporting the issue @yoavchaws , the change it merged.


HTML / REACT ELEMENTS

how can I make it type out HTML elements? I want to change the color of (for example) the first two letters to black and the next two to red.

I believe you could change the styles of entire words/strings by changing the wrappers className or style attribute via React state with callbackFunctions, but single words won't work currently, because the package only compares and manipulates text inside one specific DOM node (no child nodes, which would be required).
I agree that this would indeed be a great feature, but it would require completely fundamental changes to the code. I may look into this and see if I'd be able to find an easier solution to achieve what you described in the near future.

I see thanks!


Stacktrace broken fix (WIP)

Fixes  #541 and #579 (duplicate)

Maybe I was smart to first create a 3.2.1 branch and then create the PR?

That would be great. Then I'll fix the issue with variables too, and create
a new patch release

Wont work. THe SkipAssembly(Assembly assembly) conflicts with new unit test When_Wrapped_Ignore_Wrapper_Methods_In_Callstack

@304NotModified since you're near SkipAssembly method, could you take a look on this issue:
SkipAssembly checks whether the LogManager.HiddenAssemblies contains an assembly, but accessing that property incurs copying its internal list storage to an array.
Since this occurs on every stack frame being analyzed on every log record being made, this can create a serious memory pressure.

@ilya-g good idea. Any idea how to prevent this? 'static caching'?

@ilya-g is there a issue ticket for the possible memory issue?

@Xharze can you explain the method FindCallingMethodOnStackTrace?
I think it needs to be reimplemented

@304NotModified no there was no ticket, just an observation.
Proposed PR https://github.com/304NotModified/NLog/pull/4 for your branch.

The only way I see to have all the requirements, set out in tests, met is to extend the frame skipping condition to the loggerType and any of its subtypes.
Proposed this in PR https://github.com/304NotModified/NLog/pull/5 for this branch.

@ilya-g excellent!
Can you add some comments to the code? I have to admit it unclear what exactly is happening. Also it will prevent new bugs if it's more clear for everyone: )

Is this PR ready to be merged?

Almost. I will remove WIP and inform you when it's ready

No problem

I've been trying to document the FindCallingMethodOnStackTrace method, and have stumbled across a question: what is the legal use case when it's loggerType parameter is null?
Technically it can come from Logger.Log(Type wrapperType, LogEventInfo logEvent), but what are the real use cases when it would be required to pass null as wrapperType and thus disable frame skipping, based on logger type, leaving only assembly-skipping?

Isn't just defensive programming?

I believe so too, just defensive.

Ok, I've moved this defense to another level: when null is passed as wrapperType to the WriteToTargets method, it's substituted with the value of the loggerType field, which is constantly typeof(Logger)
PR https://github.com/304NotModified/NLog/pull/8 is ready to merge.

If the merge errors are fixed, This PR is ready

@304NotModified, could you merge current NLog/master to this branch? It would require manual merge in Logger.cs.
After merging master into this branch, this branch can be seamlessly merged back into master.

This is ready. Credits to @ilya-g

I was currently looking into merging this for the v3.2.1 release, but this pull request is based of the master branch not the v3.2.1 branch. Could you create a new pull request for this? Otherwise it cannot be included in the patch release

Ahh sorry we already talked about this. I'll remove the v3.2.1 milestone and change it to v4.0

Well i'm favor of including in 3.2.1. I will try a new PR this weekend


Added 'bank' formatter to Payment provider which returns bank name.

Added 'bank' formatter to Payment provider  which returns one of 150 largest US bank names.
Source: http://onlinebankingreport.com/resources/100.html

The data isn'y open-source, closing.


How can l extend your code to handle irregular graph (not a grid) with variable number of edges ?

Hello,
l would like to know whether your code extends to irregular graph structure , such that  :
number of edges is variable (rather than  number_edges = 8) and the graph is not a grid but an irregular graph (variable number of nodes and vertices. In your MNIST example you set  grid_side = 28)
Thank you

The same question as@pinkfloy06,    how to deside the grid side if I have 17 nodes in a fix graph,and the feature dim of every node is 2048.  Thx.


Certificate : Test certificate signing request with EC

@rahulmah please take a look at the test with EC in certificate. Thanks

GUI + back end testing

Completed


SNOW-1239792: disable oob telemetry in stored procedure

Please answer these questions before submitting your pull requests. Thanks!

What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

skip oob telemetry tests as stored proc does not support oob telemetry

Fill out the following pre-review checklist:

[ ] I am adding a new automated test(s) to verify correctness of my new code
[ ] I am adding new logging messages
[ ] I am adding a new telemetry message
[ ] I am adding new credentials
[ ] I am adding a new dependency

Please describe how your code solves the related issue.
Please write a short description of how your code change solves the related issue.

Is there a successful precommit run?

@sfc-gh-stan precommit test is running, will hold the PR until there is a successful running

precommit running finished, there are two tests failing unrelated to oob telemetry.
one is related to test code, the other is related to udf infra.
will fix the test code in another PR.