The Freaky Red Glitch is Back/Still Here

Uh Oh!
In #218, stuff would turn red when four nests of four normal squares are grouped as one square and drawn.
The glitch is still happening.
https://github.com/user-attachments/assets/aea6e417-1f7f-454a-9b5c-c0ae6000ac47

try with this fork


Tooltips for layer view drawer

Description
It isn't obvious to some users that layers can be expanded (to reveal layer descriptions, style settings/legends and filters). Being able to add tooltips to a layer would enable users to access information about a layer, before having to expand. It would also help to reduce the space taken up in the left-hand panel (from layer descriptions in the meta).
On a mobile, layer tooltips could be disabled.
Type of Issue

✅ New Feature

We can add tooltips but we cannot replace the meta tag.

This would break legacy support.
The meta tag can include html, a tooltip cannot.
Tooltips are not avilable on touch screen.

At best this will add complexity but won't get rid of the meta tag.

optional information modal?

adding a button to the header for the information to show in a dialog would be my preferred option.

Needs further specification!


(maint) Move tests to github actions

Just experimental for now.

Just experimental for now.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Talking with Rob, we should allow failures on the Travis Docker tests.

I did start working on travis allow_failures for those tests, as the team had discussed, but I hadn't finished figuring out how to handle that correctly (so it only affected those tests) with the matrix build.
Probably not very hard, and I was about to test the way I thought it might work (the docs I found weren't completely clear), the last time I was looking at it.  Though I was also planning to handle that change as a separate pr, since I didn't know whether people would end up wanting us to proceed with this one.

Looks like the failing Jenkins PR job is a transient? This EZBake job caused the failure:
13:30:31 [MIRROR] puppet6-release-el-7.noarch.rpm: Curl error (28): Timeout was reached for https://yum.puppetlabs.com/puppet6-release-el-7.noarch.rpm [Resolving timed out after 30000 milliseconds]
13:33:02 [MIRROR] puppet6-release-el-7.noarch.rpm: Curl error (28): Timeout was reached for https://yum.puppetlabs.com/puppet6-release-el-7.noarch.rpm [Resolving timed out after 30000 milliseconds]
13:35:32 [MIRROR] puppet6-release-el-7.noarch.rpm: Curl error (28): Timeout was reached for https://yum.puppetlabs.com/puppet6-release-el-7.noarch.rpm [Resolving timed out after 30000 milliseconds]
13:38:02 [MIRROR] puppet6-release-el-7.noarch.rpm: Curl error (28): Timeout was reached for https://yum.puppetlabs.com/puppet6-release-el-7.noarch.rpm [Resolving timed out after 30000 milliseconds]
13:38:02 [FAILED] puppet6-release-el-7.noarch.rpm: Curl error (28): Timeout was reached for https://yum.puppetlabs.com/puppet6-release-el-7.noarch.rpm [Resolving timed out after 30000 milliseconds]

btw just fyi there is a ticket for this work, so it might be good to add that to the commit messages: https://tickets.puppetlabs.com/browse/PDB-5485


Use templateDataStorage

It would be nice to ise Template Storage, so we don't make a request to the endpoint every time the variable is used.
Docs:
https://developers.google.com/tag-platform/tag-manager/server-side/api#templatedatastorage

Hi,
Done https://github.com/stape-io/http-lookup-variable/commit/28b8d3a2b25bb542cbe3bca0ad913bc6e1a8f9fd


AMQP-529: Remove pre-2.0 Deprecations

JIRA: https://jira.spring.io/browse/AMQP-529

Merged as https://github.com/spring-projects/spring-amqp/commit/15be4868e689f9b4723f19e0393cb5683bff8e65 after resolving conflicts during rebase.
(Will hope everything is OK. Haven't checked locally :innocent:)


"$varExist" Feature Request

Type

[  ] Functions: $varExists[var name]

Description
It checks if the bot has a prefix with a name that was inputed in the field!
Without Var:
Example:
$varExists[kxjejx]
Result: false
because kxjejx is not a var that the bot has!
With Var:
Example:
$varExists[prefix]
result: true
because var prefix does exists

Type

[  ] Functions: $varExists[var name]

Description
It checks if the bot has a prefix with a name that was inputed in the field!
Without Var:
Example:
$varExists[kxjejx]
Result: false
because kxjejx is not a var that the bot has!
With Var:
Example:
$varExists[prefix]
result: true
because var prefix does exists

umm I don't think it required to be made as Function cause it's basically
$djseval[client.variables[d.args.join(" ")] ? true : false;yes]

@ExtremeStylez


Fixes #369 by adding a heartbeat

Proposed changes in this pull request
Adds a heartbeat every 100ms.
Checklist

[x] New tests have been added
[x] npm test passes successfully
[x] Documentation has been updated

@amir20 to review

Closing in favor of #371

Should also fix what I said in https://github.com/amir20/phantomjs-node/pull/371#issuecomment-186738607


invalid number of arguments in "upstream" directive in /etc/nginx/conf.d/default.conf:49

When I run docker-compose up I get this error:
nginx-proxy_1        | forego     | starting dockergen.1 on port 5000
nginx-proxy_1        | forego     | starting nginx.1 on port 5100
nginx-proxy_1        | nginx.1    | 2017/05/31 17:44:00 [emerg] 17#17: invalid number of arguments in "upstream" directive in /etc/nginx/conf.d/default.conf:49
nginx-proxy_1        | forego     | starting nginx.1 on port 5200
nginx-proxy_1        | forego     | sending SIGTERM to dockergen.1
nginx-proxy_1        | forego     | sending SIGTERM to nginx.1

Any ideas?

I ran the project completely clean (removed all docker containers and images) and didn't get any errors. Did you change anything?


Search

As a user... I want a text box where I can search for a place, address, or feature, get results, and display them on a map.
Min Ship (High Priority):

User can search for place or address
Suggestions are returned (if supported by locator).
Out of the box, the search bar works with AGOL world geocoding service. No configuration required. Just add to your app, and you can geocode and show results on map.
Works with API Keys
When user selects a suggestion or hits enter, a default graphic is added to the geoview and optionally the viewpoint is changed
Added graphics contain attributes with geocode result information, so that developer can identify and display a callout with the geocoded address info
works in 2D and 3D
Developer can clear geocode result graphics from the view

Nice-to-haves (Moderate Priority):

Developer can customize to specify their own locator, whether online (service endpoint/item) or offline (either locator file or from MobileMapPackage.locatorTask)
Developer can easily modify style of graphic "pin" that is dropped (they might want to change the picture marker symbol or simple marker symbol style)
Developer can opt to continue adding new pins with each search (add to), or to always only have 1 pin with the latest search (add as new).
To consider - how can we build this so we can pull it into the route directions control when we get to that later? (https://developers.arcgis.com/javascript/latest/sample-code/widgets-directions/)
To consider - how do we handle multiple results? If I search for "Coffee" and there are 8 results, can the developer opt to show all 8?
Can search feature tables for features
Customize search pins for the returned category ("coffee", "restaurants", "gas station", etc)

Resources:

https://www.mapuipatterns.com/location-finder/

Here is the JS Search Widget - https://developers.arcgis.com/javascript/latest/sample-code/widgets-search-3d/

Addressed by #380

This is complete, closing


bug: Wrong indentation

Did you check existing issues?

[X] I have read all the tree-sitter docs if it relates to using the parser
[X] I have searched the existing issues of tree-sitter-php

Tree-Sitter CLI Version, if relevant (output of tree-sitter --version)
No response
Describe the bug
I get an extra indentation/tab when I create a new file in certain php files.
Steps To Reproduce/Bad Parse Tree

enable indent for treesitter
install php parser for treesitter
open file included below
place yourself at line 12 (function up)
press  or o in nvim
notice the wrong indentation

Expected Behavior/Parse Tree
Correct indentation
Repro
<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration
{
    /**
     * Run the migrations.
     */
    public function up(): void
    {
        Schema::create('jobs', function (Blueprint $table) {
            $table->id();
            $table->string('queue')->index();
            $table->longText('payload');
            $table->unsignedTinyInteger('attempts');
            $table->unsignedInteger('reserved_at')->nullable();
            $table->unsignedInteger('available_at');
            $table->unsignedInteger('created_at');
        });

        Schema::create('job_batches', function (Blueprint $table) {
            $table->string('id')->primary();
            $table->string('name');
            $table->integer('total_jobs');
            $table->integer('pending_jobs');
            $table->integer('failed_jobs');
            $table->longText('failed_job_ids');
            $table->mediumText('options')->nullable();
            $table->integer('cancelled_at')->nullable();
            $table->integer('created_at');
            $table->integer('finished_at')->nullable();
        });

        Schema::create('failed_jobs', function (Blueprint $table) {
            $table->id();
            $table->string('uuid')->unique();
            $table->text('connection');
            $table->text('queue');
            $table->longText('payload');
            $table->longText('exception');
            $table->timestamp('failed_at')->useCurrent();
        });
    }

    /**
     * Reverse the migrations.
     */
    public function down(): void
    {
        Schema::dropIfExists('jobs');
        Schema::dropIfExists('job_batches');
        Schema::dropIfExists('failed_jobs');
    }
};

See relevant issue: https://github.com/nvim-treesitter/nvim-treesitter/issues/4848

Turns out there's nothing to do on this end---indent queries are Neovim specific. However, I'll still try to submit a PR for the issue above


rename "bearer" to "session" in Authorization header

rename bearer in our Authorization header to session, because that’s what it is, and we don’t use bearer tokens anywhere else in our code. It’s unnecessary confusing. So instead of Authorization: bearer sessionid123 header, we would have Authorization: session sessionid123

@gr2m wish I had noticed this a bit sooner as I have a question on this..
This issue makes sense in the current context, but would we not be better longer term to look at JWT? I'm not trying to block this issue so late in the game, as I think this question will be a longer running discussion, but curious to others' thoughts.

You mean JSON Web Token? I don’t know anything about it, I’ll have to look into it. But the plan is that besides Session there will be other ways to authenticate, like Token that can be used once to reset a password, and probably plugins will find other ways to use the Authorization header?

I sure do :)
I bring it up as it does provide a bit more flexibility with what information is passed in this token, and it's signed with a private key which allows for distributed authorization (i.e. by any of your servers knowing the private key, you can let a user in knowing the provided JWT hasn't been tampered with.). A use case I considered at one point was checking auth on our reverse proxy server (running hapi/h2o2 etc) to reduce load to the app servers - not the best example as loading proxy servers isn't always smart haha.
In saying that, I can now see the other uses you're thinking of - so it feels like the hoodie default should be Session, and a plugin later down the track could wrap the account plugins providing jwt etc, while still providing your mentioned use cases, such as Token.

done via done via e63a0dd, 65c6a3f, f3dd07e


[5.7][CSSimplify] Allow referencing typealias declarations via leading-dot…

… syntax in generic context
Cherry-pick of https://github.com/apple/swift/pull/60080

Explanation:

Previously only static methods found on protocols were allowed but
it is reasonable to reference a typealias to perform an implicit call
to .init on its underlying type.

Scope: Using leading-dot syntax in generic context  in combination with typealiases.

Main Branch PR: https://github.com/apple/swift/pull/60080

Resolves: rdar://88513939

Risk: Very low

Reviewed By: @hborla

Testing:  Added a regression test-case to the suite.

Resolves: rdar://88513939
(cherry picked from commit 12776182f0e2cd7ef870849ccdefcb39c2cad61a)

@swift-ci please test

@swift-ci please nominate

@swift-ci please test macOS platform


Instagram Login/Signup Page Clone

Project title
Instagram Login/Signup Page Clone
Project Description
An Instagram Login/Signup Page Clone built using HTML/CSS. This is a beginner level project.
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[X] Html
[X] CSS

Demo
https://user-images.githubusercontent.com/80174214/161272538-9928bdf2-436f-4b3e-a34e-a5f0d829d259.mp4

/assign


Error configuring ANTHROPIC API KEY in.env file

I added "ANTHROPIC_API_KEY=s****" to the.env file
"No Anthropic API key found. Please add the environment variable ANTHROPIC_API_KEY to backend/.env"

@bigfishnew a couple of clarifications: is it definitely in backend/.env , not frontend/.env? In your screenshot, there's a " at the start, I'd recommend removing that.

If you're still having problems, let me know.

@bigfishnew can you get rid of the double quote (") at the start of your .env file?
And after we're done debugging this, please revoke this API key and use a new one so other people don't use your API key.

Without the double quotes, it still gives me an error. Another problem is that when I use Claude3, it also gives me an error if I don't set the OpenAI API Key in the Settings

@bigfishnew thanks for bringing the bug "when I use Claude3, it also gives me an error if I don't set the OpenAI API Key in the Settings" to my attention. I just fixed it.
Unfortunately, I'm not able to replicate your issue with the .env file. It works for me. Can you try directly modifying the code here: https://github.com/abi/screenshot-to-code/blob/7f44228a9582f6e39e8dbcee7598b86328ef7e74/backend/config.py#L6 and let me know if that fixes it?

Just replace "ANTHROPIC_API_KEY" in the configuration file and there will be no error. But the console will raise an Error like this,"PermissionDeniedError: Error code: 403 - {'error': {'type': 'forbidden', 'message': 'Request not allowed'}}" I don't know if it has anything to do with me being in China. I don't know how to configure the agent in this software

Yeah, I don't see China on this list: https://www.anthropic.com/supported-countries
You could try a VPN or proxy. I also just released Claude support to the paid version here: https://screenshottocode.com


Error message not specific enough

edit
find

for edit edit xxx and find find xxx

planned enhancement known issue

[ ] UG
[ ] DG


Making sense of the related langs

Thanks for extracting all this data! I've been investigating the formation of German compounds. However, I'm confused by the related_lang fields. e.g.
term_id,lang,term,reltype,related_term_id,related_lang,related_term,position,group_tag,parent_tag,parent_position
ualTS6tTUg2mdZtsSJV-Lw, German, wahrscheinlich, compound_of, 79PzrNZxUaqTC9uOjKOtsQ, Yangum Dey, wahr, 0, , ,
ualTS6tTUg2mdZtsSJV-Lw, German, wahrscheinlich, compound_of, EPBI80uLWHGxYzTpI7ICCw, Yangum Dey, scheinen, 1, , ,
ualTS6tTUg2mdZtsSJV-Lw, German, wahrscheinlich, compound_of, v6mhJCsCVRSysICgubOQbg, Yangum Dey, -lich, 2, , ,

I'm not sure where the "Yangum Dey" comes from. The wiktionary pages for those three don't mention that language. What does it mean there?

Hey there, I think the issue mentioned here is a result of the wiktionary_codes file being incorrect. The 2-digit codes are correct, but the 3-digit codes are all being read as 2-digit codes, which means that there is accidental overlap between languages. eg. latin has wiktionary code la and Yaul has wiktionary code yla, but since the first letter of 3 letter codes is being cut off, yaul's code is being stored as la, so all of the latin related terms are listed as Yaul instead of latin.

Hey there, I think the issue mentioned here is a result of the wiktionary_codes file being incorrect. The 2-digit codes are correct, but the 3-digit codes are all being read as 2-digit codes, which means that there is accidental overlap between languages. eg. latin has wiktionary code la and Yaul has wiktionary code yla, but since the first letter of 3 letter codes is being cut off, yaul's code is being stored as la, so all of the latin related terms are listed as Yaul instead of latin.

Thanks for catching this! I've updated the data/code with the fix.


Minor suggestion

I wanted to play around with the new code. I ended up making some minor changes. Also, I moved the tests into their own file. But I don't know what the "best practice" is on organizing tests. Should these be in their own file? Or should they go back into the "core" tests?

Do you know what the best organization for tests should be?

@arichar6 Sorry I didn't realize we could do this on git! Maybe we can make a test file for all new features in different releases? Or we could make a different test file for all of the classes in core (their subclasses included in the same file).

Those both sound like reasonable solutions. Do you mind doing a bit of research to see what the standard/best practices are for python packages that use pytest? Maybe check to see what numpy does, or plasmapy?
Thanks!

This article suggests splitting into suites that test for configuration/initialization, unit tests, and integration tests. plasmapy and numpy have a different test file for each module, like we have right now, but neither of them have different classes in one file.

That is a pretty helpful article. I that that, since our core.py has quite a lot in it, it's ok to split up the tests. I may also split up the source files, too, eventually.


ios navigation bar problem

Hi ihadeed, i am really thankful for ur swiping tabs.
Here i notice a problem when i implement this swiping tabs on ios emulator.

same problem here, have you been able to fix it?


Crashing issues and difficulty enabling/disabling the nro file

Smash Ultimate crashes when I use the mod. I have arcropolis 1.0.5, and I can't disable the nro file in ARCadia.

Found the issue with ARCadia. I had the old version of the mod in my disabled_plugins folder, as it was disabled before I updated it


Main-net 20.04 image "apt upgrade -y" fails

was working on a deployment today that uses 20.04, when running apt upgrade -y this error occurred and the VM became unresponsive.

Did you use this flist?
https://hub.grid.tf/tf-official-vms/ubuntu-20.04-lts.flist

closing in favor of https://github.com/threefoldtech/zos/issues/1821


Repartition Ray dataset if number of shards is too small

Currently we throw an error when the number of partitions in a data source is too small for the number of workers.
However, in the case of Ray datasets, we can actually repartition the dataset ourselves.
This will also ensure our quickstart examples, such as in https://docs.ray.io/en/latest/train/train.html#quick-start-to-distributed-training-with-ray-train will work out of the box.

@krfricke I am a little confused - we should not be throwing any errors as we have moved to a split based solution for Ray Datasets (see get_actor_shards). That's the recommended way instead of repartitioning. How is this error triggered?

The errors comes up when running e.g. the quickstart example from our docs:

import ray
from ray.train.xgboost import XGBoostTrainer
from ray.air.config import ScalingConfig

# Load data.
dataset =<EMAIL_ADDRESS>
# Split data into train and validation.
train_dataset, valid_dataset = dataset.train_test_split(test_size=0.3)

trainer = XGBoostTrainer(
    scaling_config=ScalingConfig(
        # Number of workers to use for data parallelism.
        num_workers=2,
        # Whether to use GPU acceleration.
        use_gpu=False,
    ),
    label_column="target",
    num_boost_round=20,
    params={
        # XGBoost specific params
        "objective": "binary:logistic",
        # "tree_method": "gpu_hist",  # uncomment this to use GPU for training
        "eval_metric": ["logloss", "error"],
    },
    datasets={"train": train_dataset, "valid": valid_dataset},
)
result = trainer.fit()

But I see what you mean - we do the split ourselves, so no need to actually call repartition. We can just check if the data source supports automatic repartitioning.
I've updated the PR.


Friendly not using readline

On Debian typing, inside friendly, print←←←←← gives:
$ python -m friendly

friendly-traceback: 0.4.60
friendly: 0.4.26
Python: 3.9.8
Type 'Friendly' for help on special functions/methods.

[1]: print^[[D^[[D^[[D^[[D^[[D

I mean, if I hit my arrow keys, left, up, right, down, it prints ^[[A/^[[B/^[[C/^[[D instead of moving through history (for up/down) or inside the line (for left/right).
One can use rlwrap python -m friendly as a temporary fix.

Thanks. I will have to figure out how to test this as it works perfectly on Windows, which is what I use. I wonder if the Linux subsystem (which I have never tried) might be helpful in figuring out how to fix this.

Closing as it was moved to https://github.com/friendly-traceback/friendly/issues/17

@JulienPalard Did you install Python by building it?  Reading this StackOverflow question (https://stackoverflow.com/questions/55768178/no-line-history-autocomplete-available-in-python-repl) lead me to this set of instructions https://dzone.com/articles/install-python-370-on-ubuntu-1804debian-95 which mentions the need to use libreadline-dev in the build process.   Is this what you have done?

Yes I do compile a lot of Pythons versions myself but I have libreadline-dev when I do so.
And for this particular case I was running the system Python, and in all my Pythons readline do work in the builtin Python REPL.

I've read in a comment today on a video about rlwrap (https://www.youtube.com/watch?v=WizvitXOsLk) that simply adding import readline in a program might fix this problem.
Could you do this either in friendly/__init__ or perhaps in friendly/console.py which is where I use input().
On Windows, readline is not present. If this works, then I'll add
try:
   import readline
except ModuleNotFoundError:
   pass

@JulienPalard I've attempted to fix this with friendly-traceback version 0.4.70.  Could you see if it works?

The behavior is very strange, it "jumps" over the prompt, either using backspace or the left key, see this gif where I try first using backspace, then using the left arrow.

Thanks for trying it out.  On the plus side, the escape characters are no longer present .... but, I admit that the behaviour is less than ideal.  :(

The same behaviour was reported in https://github.com/willmcgugan/rich/issues/299 ... and fixed there. I do not use Rich's input() but Python's.  I will see if I can use Rich's input() on Windows and, if so, will upload a new version.

It reminds me of a bash bug: the program does not know a prompt was printed, so it thinks it's at the 1st column. When the user hits backspace it thinks it's safe to emit a \r to directly jump to the front of the line, but it's not. I'm digging.

Try the new friendly version (0.4.27)

Same with 0.4.27. It's easy to reproduce:
import readline

print("[1] ", end="")
input()

(Do you need an access to a Linux box to test it? I may be able to provide you with one, if sdf.org is not enough to test this, just ask me.)

For my previous reproducer there's an easy fix:
import readline

input("[1] ")

Ok, that's what I did with the version.
If it works, I will see if I can do something with the styling as I do not like the default with just using input.


Add nvidia drivers data

Nvidia driver on windows come with not needed service "NvTelemetryContainer", more info:
https://www.ghacks.net/2016/11/07/nvidia-telemetry-tracking/
someone posted commands to disable this service and other related scheduled tasks at:
https://www.reddit.com/r/privacy/comments/gmwlv5/do_nvidia_drivers_include_telemetry_or_other/fr6lieg/
sc stop "NvTelemetryContainer"

sc config "NvTelemetryContainer" start=disabled

schtasks /change /disable /tn "NvTmMon_{B2FE1952-0186-46C3-BAEC-A80AA35AC5B8}"

schtasks /change /disable /tn "NvTmRep_{B2FE1952-0186-46C3-BAEC-A80AA35AC5B8}"

schtasks /change /disable /tn "NvTmRepOnLogon_{B2FE1952-0186-46C3-BAEC-A80AA35AC5B8}"

The picture in old tool at:
https://github.com/NateShoffner/Disable-Nvidia-Telemetry
show that another scheduled tasks need to be disabled & modification needed for registery key, looks like it's handled by code in:
https://gist.github.com/alex-anenkov/8d6c9bfef9b0142ced8dabfbb5d5db61#file-fuck_telemetry-cmd-L67-L76

It deserves a mention, sure. I'll see what I can do, but as with Windows - no promises about unofficial stuff.


fixed user follow button appearing on logged in user's profile

closes #352
[ x ] hide follows button from the logged-in user profile.
As a logged-in user, the follow button won't appear in my profile but will rather appear in other users' profiles.
screenshot below

Prettier Run Failed. @okumujustine

Prettier Run Failed. @okumujustine

oops, my bad, sorry.. fixed it


fix(storybook):can't resolve '@nextui-org/react'

📝 Description
fix storybook issues
⛳ Current behavior (updates)
If you use yarn start:sb or yarn sb ,you can't run storybook and get Module not found: Error: Can't resolve '@nextui-org/react' in 'C:\Users\user\Downloads\nextui-main\nextui-main\packages\storybook\.storybook'
🚀 New behavior
storybook runs as normal
💣 Is this a breaking change (Yes/No):No

📝 Additional Information

Codecov Report

Merging #536 (023a8f5) into main (c54c84c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #536   +/-   ##
=======================================
  Coverage   74.82%   74.82%
=======================================
  Files         200      200
  Lines        3098     3098
  Branches      956      956
=======================================
  Hits         2318     2318
  Misses        765      765
  Partials       15       15

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c54c84c...023a8f5. Read the comment docs.

I clean unused dependencies in docs and updated next-theme


Add a URL field to config, make the router optional

What happened (or feature request):
Feature request, touching on a few related concerns. #321 is the motivation for this request.
Currently, all ddev sites get a url at .ddev.local. We provide a way to run on a port alternate from 80, but it is not very intuitive. We also assume that users will want a domain like the one we provide, while there are valid use cases for throwing a site on localhost at an available port.
What you expected to happen:
I think we should introduce a URL field to the config.yaml to be used to address these concerns. The field would allow users to define the URL the site is served from in the following ways, achieving the following result for each way:

Set to "localhost". The router is not used for the site, and instead we output the published port of the web container as the site URL. e.g. after ddev start: "Your application can be reached at http://localhost:4379
Set to "localhost:8089". The router is not used for the site, and port 8089 is used to expose the site, provided it is available.
Set to "[sitename].ddev.local:8089". The router is used for the site, port 8089 is used to expose the site, provided it is available. e.g. after ddev start: "Your application can be reached at http://[sitename].ddev.local:8089"
At this point we may as well allow the URL to be defined how the user wants, unless there's a reason not to that I'm not seeing. e.g. user can have there site at http://sitename.banana.dev or whatever.

This would entail changes to the prompts in "ddev config" to add a URL prompt, and list the possible options for the user. I think we should still provide [sitename].ddev.local as the default value.
I suspect this approach would also entail changing configurations in the docker-compose.yml. We will need to come to a decision on if we are going to control / maintain this file, or allow users to configure it.
How to reproduce it (as minimally and precisely as possible):
Anything else do we need to know:
Related source links or issues:
#321
#323

Hi @tannerjfco. I see your point in making this very flexible. Question: does it make sense to add this to the ddev config step? It seems to me that providing a default and then a link to customizations within the config.yml would be the most useful for those that care enough to make this modification.

We wouldn't necessarily need to add it to ddev config prompts if we didn't want to, and linking to documentation of the various configuration options would be more approachable than trying to summarize the options on a prompt.

I feel like these changes should probably be discussed and considered in isolation, as I feel like they can be implemented independently, and I don't think there's a huge driver to combine them.

Hostname configurability
I think there's value in this feature. I do feel that it should probably not be surfaced in `ddev config` and just be a documented key in the yaml config if we were to do it. My biggest concern here would just be that without additional legwork we can't stop users from doing silly things, like trying to use the same hostname on every site. We also lose some guarantee that a committed config which has a hostname would be portable to another developers machine. I think the risk there is small but just pointing out that it does exist.
per-site optional usage of router
I have some concerns about this, at least right now. I think this potentially creates a lot of testing and support overhead if we allow so many configurations. So much so, that I'm fairly sure if this feature landed how people had their router configured would likely turn into a standard question for most support requests. I haven't looked at the port configurability work yet since I was out of town last week, but my strong preference would be that if it's not very intuitive that we rally around that feature and provide the right messaging and context to help make it more intuitive.
I believe this feature would also have a high likelihood of creating portability issues between developer machines, as there is no guarantee an arbitrarily chosen port (such as 8089) would be available on another developers machine. We also have the same issues here as we do for hostnames, which is that we'd need to do a lot of legwork to ensure sites didn't conflict with each other (i.e. someone using port 8888 on all their sites).
All that being said, I wouldn't be dead set against this if it was driven by feedback and a clear need being demonstrated by users, but I do feel like we should be cautious and not go down this road unless we really need to.

Flagging w/"needs decision" because there is an open discussion of how much do we open up for the end-user and is this truly valuable or does it create more issues than it solves.
Counter proposal might be to detect when a user it trying to use a custom port and prompt/push for a more consistent approach. Just spit balling at the moment...

These changes can certainly be considered independently, but the primary motivation I had in combining them was to provide an intuitive way for the user to define what URL they access their site from.
Hostname configurability concerns: I agree with not exposing the config prompts, and treating as optional config in the yaml. It wouldn't be hard to validate the hostname when config is read, and similarly it wouldn't be too difficult to check that the hostname isn't in use by another ddev site, if we wanted to do so. The risk for reduced portability and invalid configuration is indeed higher, but I think acceptable when being treated as an optional configuration.
per-site optional usage of router concerns: We can try to explain HTTP_EXPOSE better, but I don't have a lot of confidence a better explanation will clarify. That's certainly not to say the url key idea is the only way to solve it though. Re: overhead, my thinking for this scenario is that if a localhost url is defined, then we simply skip router start/stop. If the router was being used for a site, and if a site was started that didn't use it, I don't think it would be problematic to still have the router configure for the site that isn't using it. The router could configure like the site was using it, but we output the localhost url to the user and they interact with the site that way.
My larger concern re: configuration on this would be in terms of how we handle changing the port configurations for the site's compose. If we decide to manage the main compose file as in #343, we could potentially write the main compose to our whim. If not, we could use additional compose files to override the configurations of the main compose, but additional files for this concern could be confusing to the user.

Related and possibly sort-of-duplicate: #376: "ddev describe" should report information about the routed and unrouted web ports

I'm moving this v1.1.0 because I don't see this a release blocker for v1.0.0 and this will warrant additional discussion at an architecture/end-user level.

I feel like this needs a scheduled conversation to unblock and determine the true priority. Also, the related/linked issues might determine a different solution/path forward on this.

Relating to a recently filed issue regarding multiple domain support https://github.com/drud/ddev/issues/620

In https://github.com/drud/ddev/issues/796, currently scheduled, we're going to show the ephemeral port as one of the url options in ddev describe I think this does enough of the requested functionality.  Also, in the intervening time since this was filed we've added additional hostname support and will probably add TLD changing and arbitrary hostnames as well. Closing.


peer connection is not closed when call is end. app is running on background. how i can handle it.

@saghul
I have tried to close all peer connection before call disconnect.
I think it does not disconnecting properly, Cause,
When i try to join same meeting just after disconnect without refresh it won't shows my the stream to other web peer.
If i try to join same meeting after disconnect with refreshing app then everything works fine. every user can see every other user.
What is the standard way to handle disconnect peer connection in this library?
React: 16.6.0
React-native: 0.57.4
react-native-webrtc: 1.67.1

Well, I firstly use:
localStream.getTracks().forEach(t => t.stop());
localStream.release();
then i use close method of RTCPeerConnection object.
Afterward, because I use react-navigation, with StackActions i reset navigation stack and navigate to initial screen


Feature Request: Calculating with unit-suffixed values

If i want to perform arithmetic on values that have a unit suffix, i can do it like so in sass:
$base: 12px;
$double: 2 * $base;

while there isnt really an easy way to make this work in js, polished could provide helper functions that take care of the necessary regex to strip the unit, perform the calculation and return a the result as a string with the original unit. the main benefit here would be that the unit type is retained, which it wont be if stripUnit is used.
Mock usage:
import { multiply, add } from 'polished';

const base = '12px';
const double = multiply(base, 2); // returns '24px'

const one = '1px';
const plusOneplusOne = add(base, one, one); // returns '14px'

It could also have an idx-like syntax:
import { calc, stripUnit } from 'polished';

const  base = '12px';
const double = calc(base, baseAsNumber => baseAsNumber * 2); // returns '24px'

const one = '1px';
const plusOne = calc(base, baseAsNumber => baseAsNumber + stripUnit(one)); // returns '13px'

I've seen a few similar issue tickets and this linked PR all closed without resolution. Why is this?
Being able to perform calculations on values with units is one of the most basic features in SCSS and I don't see the point in extending styled components functionality with Polished unless it has this sort of thing.


Only allow 1 login at a time

I have 2 models: Admin and Writer.
How can i only allow a user to be logged in at one at a time?
Thanks!

Please use StackOverflow for questions/help, where a wider community will be able to help you. We reserve the issues tracker for issues only. Thank you!


WithDate.ts (contains date / dateFromIsoString)

Also going to add a StringFromIsoDateStrict trying to follow the standard defined here: https://tc39.es/ecma262/#sec-date-time-string-format

Closed by #191


global: logout_listener fails when using logout_user

Problem:
Using logout_user() after calling login_user(user) in tests will fail. This happens because they are used in a test_request_context and, as explained in flask documentation
"the before_request() and after_request() functions are not called automatically."
As login_listenercreates the session after the request, using @flask.after_this_request, the session is not created when calling login_user(user). However  logout_listener deletes the session immediately instead of also doing it in @flask.after_this_request, which fails as the session does not exist.
Suggested solution:
Moving the code deleting the session in the after request function.
@lnielsen Do you see any issue with the suggested solution. All the tests in invenio-accounts and invenio-oauthclient seem to pass when I do this.

No. But just test the login/logout in the browser with two separate sessions: 1) Login session a 2) Login session b 3) View security tab in both sessions and see that there's two sessions. 4) Logout from session a 5) Check in session b the security tab and verify that only one session is now displayed.

@lnielsen I just tested with invenio-app-ils. It works.
Also the test you created to check that sessions are removed still passes as it calls logout via the views, which means that the after request triggers are called properly.


fix a bug

Fix a bug with rev
Improve zero(MeshArray)

Codecov Report

Merging #100 (babad1c) into master (51afd39) will increase coverage by 1.24%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #100      +/-   ##
==========================================
+ Coverage   73.11%   74.35%   +1.24%
==========================================
  Files          12       12
  Lines         424      429       +5
==========================================
+ Hits          310      319       +9
+ Misses        114      110       -4

Impacted Files
Coverage Δ

src/mesharrays/MeshArrays.jl
75.00% <100.00%> (+35.00%)
:arrow_up:

src/meshgrids/imfreq.jl
94.44% <100.00%> (+3.01%)
:arrow_up:

src/meshgrids/imtime.jl
92.59% <100.00%> (+4.13%)
:arrow_up:

src/mesharrays/dense.jl
73.77% <0.00%> (+1.63%)
:arrow_up:

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


update to mantine 7.14.0

This updates Mantie from 7.13.3 to 7.14.0

added restrictToMarks prop to Slider  (Note this prop is not yet available for RangeSlider)
added barLabelColor to BarChart

I think the next release should be 0.15.0 given that it's a minor release from Mantine, plus there is a a breaking change.

restrictToMarks prop for Slider:

Here is a sample app on PyCafe:  https://py.cafe/amward/dmc-slider-with-restrict-to-marks


Edit: Typo in Line 143 in PROMPT_COMMAND

Noticed a typo in Line 143 so I thought I'd point it out.

Docs Build status updates of commit d6318c3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

TerminalDocs/tutorials/new-tab-same-directory.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Nice catch! Thanks @oseughu!


feat: genetic algo based optimizer

metric =AspectCritic(name="answer_correctness",definition="Given the user_input, reference and response. Is the response correct compared with the reference",llm=llm_4o)
metric.train("alignment_sample.json")

dummy data

The progress bar for this now is not neat. I would like to have it as one single bar with a subprocess shown with progress. I'm not sure what the best way to do it is.

@shahules786 check out this https://github.com/explodinggradients/ragas/blob/99d1a47b9025ea46625d3f4985309eff24025c63/src/ragas/executor.py#L146-L181
which does something similar for batching

@jjmachan thanks, just fixed it. Please review


Files in the output directory

Hello,
I just wonder the role of checkpoints, positions and states in the output folder. Are they for the analysis? I plan for a long production run and these files take a lot of storage space.
I think we can use the gamd_restart.checkpoint to restart the simulation. I'm not sure how to use the files in those folders.
if (step % ntave) == 0:

    state_filename = os.path.join(output_directory, "states", str(step) + ".xml")
    step_checkpoint_filename = os.path.join(output_directory, "checkpoints",  str(step) + ".bin")
    positions_filename = os.path.join(output_directory,  "positions",  "coordinates-" + str( step) + ".csv")
    simulation.saveState(state_filename)
    simulation.saveCheckpoint(step_checkpoint_filename)
    integrator.create_positions_file(positions_filename)

Thanks,
Tien

Hi @TienMPhan ,
After discussing with @dyelar, we determined that these outputs weren't typically used for any analysis beyond debugging. So we've removed them from the main branch. You can also safely delete the contents of checkpoints/, positions/, and states/ to save space for yourself.

Hi @lvotapka,
The reason I asked for this is that the performance of GaMD is much slower than the conventional simulation without potential boost (~ about 6-fold slower). At first I suspected that writing files may have slowed down the simulation. I commented out the lines and reinstalled the package but it didn't improve much.
I tested the chignolin (10 residues) system in an octahedron box length of 5nm (attached files). The system has 9318 atoms. The performance of conventional simulation on an A100 GPU ~1.1 microseconds/day while the GaMD-OpenMM is ~200 nanoseconds/day. Is this performance normal? Did you guys observe something similar when implementing the algorithm?  With a larger system, I suspect that you'll see less of a performance hit by using GaMD.
Nevertheless, @dyelar, we ought to do an analysis of performance comparing cMD and GaMD for different systems, and possibly on different GPU models as well (and that would be something good to add to the manuscript).

Thanks Lane. I am looking forward to seeing the comparison in your manuscript.


Fix TLS support

This wires up creating the TLS client based on the fsouza API.
Signed-off-by: Daniel Hiltgen<EMAIL_ADDRESS>

@dhiltgen I feel a bit more confortable with using tlsconfig pkg to build the TLSConfig as it's the same package used by the docker client.  Is TLS currently broken with the fsouza client?  Is there anyway we can continue to use pkg/tlsconfig and use the fsouza client?

This was the first time I've used libcompose, and it was DOA for TLS configured systems for me.  If it works for others, maybe the problem is on my side, but this change fixed it for me.

@dhiltgen I don't doubt that TLS broke when we switched clients.  @imikushin Did you by chance test TLS?  Testing against docker-machine is usually the easiest for me since it sets up TLS for you.

I confirm this PR fixes TLS support. The only problem is golint is pissed off.
I'll rebase this PR and try to calm golint.

Carried by #106, closing this one. Thanks @dhiltgen


[FEA] Add extra packages in docker entrypoint

I would like to use the rapids docker image more interchangeable with the dask docker image.
Describe the solution you'd like
The dask image (along with others) implements an entrypoint script which installs extra packages from environment variables (EXTRA_APT_PACKAGES, EXTRA_CONDA_PACKAGES, EXTRA_PIP_PACKAGES). This allows users to customize their containers without having to build their own.
Describe alternatives you've considered
The alternative to this is for people to build their own docker images backed on the rapids image and host it somewhere like Docker Hub. It would be good if users could get started with the docker image without prior knowledge of docker.

@jacobtomlinson, we're currently going through these older issues to see what still needs to be addressed. I just wanted to confirm whether or not this feature request is still valid. Please let me know.

No problem, these things happen!
I think this would still be valuable for existing Dask users who are transitioning over to RAPIDS as they have come to expect this in the Dask images. It comes up from time to time.

@jacobtomlinson, addressed in #170. Feel free to review!


Resizing?

Great library!  I noticed that resizing the browser on desktop causes the previously animated content to disappear.  It doesn't seem to re-animate consistently either after resize.  Is this s known issue?  You can replicate it on the demo site.

Confirmed the issue, i will need to add a check after to readd elements in view.

Hi @volkandkaya did you happen to have a chance to look into this issue?

It would be good to get a fix for this :)

Fixed, please give it a try.

I didn't think about mobile height changes, so I removed some code that might have fixed that (reduce bundle size).
I will test tomorrow on a Safari device.

Cool, thanks. I'm not great with JS so I don't have my own suggestions to make but with the help of a certain AI I did come up with this temporary solution that may help, or not. https://gist.github.com/RyanRoberts/6260530cf100c37a1f3bb3795dcbd1a3/revisions?diff=split
Thanks for looking into it.

When resizing it needs to rerun initElement to get offsets and set the trigger for each element. I had some performance and other issues. This seemed to be the best solution.

Updated can you try 1.0.5 @RyanRoberts

That's working great! Thanks for the update.

Thanks @volkandkaya - I think this may still be an issue on desktop resize.  Was this fix just for mobile?

What issue are you having on desktop resizing?

What issue are you having on desktop resizing @cmalpeli ?

@volkandkaya on desktop, if I resize, the previously animated content disappears and then re-animates on the next scroll event.

@volkandkaya if you see here on the example site, all the animated content disappears and then re-animates on scroll when you resize the window:
https://versoly.com/taos#fade


UnityContext not working for unity 2019 version

Please avoid duplicates

[X] I checked all open issues and discussions and none of them matched my problem.

Language and Compiler
Babel and WebPack JavaScript
What environment are you using?
Local Development Server
When does your problem occur?
While writing code
What does your problem relate to?
The problem seems React related
React-Unity-WebGL Version
7.x
React Version
17.0.2
Unity Version
2019.1.5f1
What happened?
{UnityContext} doesn't seems to exist when I install React-Unity-WebGL Version 7.x.
It seems to be {UnityContent} instead.
But I have the following error :
Uncaught TypeError: UnityContent1 is not a constructor or
TypeError: UnityContext1 is not a constructor using UnityContext
My component script:
import React from "react";
import Unity, { UnityContent  } from "react-unity-webgl";

const ETA_Body = () => {
    const UnityContent = new UnityContent({
        loaderUrl: "unity/Eat Them all/build/UnityLoader.js",
        dataUrl: "unity/Eat Them all/build/Eat Them all.data.unityweb",
        frameworkUrl: "unity/Eat Them all/build/Eat Them all.wasm.framework.unityweb",
        codeUrl: "unity/Eat Them all/build/Eat Them all.wasm.code.unityweb",
      });

    return (

           <Unity UnityContent={UnityContent} />

    )
}

export default ETA_Body

my webGl folder is located in the public directory public/unity/Eat Them all/build
Error screenshot
Thank you for you help.
Reproducible test case

import React from "react";
import Unity, { UnityContext  } from "react-unity-webgl";

const ETA_Body = () => {
    const UnityContext  = new UnityContext  ({
        loaderUrl: "unity/Eat Them all/build/UnityLoader.js",
        dataUrl: "unity/Eat Them all/build/Eat Them all.data.unityweb",
        frameworkUrl: "unity/Eat Them all/build/Eat Them all.wasm.framework.unityweb",
        codeUrl: "unity/Eat Them all/build/Eat Them all.wasm.code.unityweb",
      });

    return (

           <Unity UnityContext  ={UnityContext  } />

    )
}

export default ETA_Body

Would you be interested in contributing a fix?

[ ] yes, I would like to contribute a fix

Does anyone have a fix for this?

I found the fix, it's working so good ❤
import React from "react"
import Unity, { UnityContent } from "react-unity-webgl"

export class ETA_Body extends React.Component {
  constructor(props) {
    super(props)

    this.unityContent = new UnityContent(
      "unity/Eat Them all/build/Eat Them all.json",
      "unity/Eat Them all/build/UnityLoader.js"
    )
  }

  render() {
    return (
      <div style={{ maxWidth: `700px`, maxHeight: `400px`, marginBottom: `1.45rem` }}>
        <Unity unityContent={this.unityContent} />

    )
  }
}

export default ETA_Body

Thank's Jeffrey for this awesome package.


Moved editor to user control; updated json to 11.0.2

Thanks for your interest and participation! 👍
Here are some comments that prevent me from accepting this merge request:

I don't think that it's a good idea to include the menu in JsonEditorControl because it may be embedded anywhere in a form that may also have its own menu.
I have a concern with the project structure: the new control should be in its own project (named JsonEditorControl) and depend on the existing JsonTreeView project (call it "Single Responsibility Principle" applied to the project level).

If you are able to resolve this 2 concerns I'll review and may accept a merge request.


⚠ Minecraft has degraded performance

In 4808f6a, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1239 ms

Resolved: Minecraft performance has improved in 507e794.


code - page component

#3
@todo

[ ] implement page component

[ ] #1
[ ] #2
[ ] #5
[ ] #7
[ ] #9
[ ] #10
[ ] #11
[ ] #12
[ ] #13
[ ] #14

[ ] implement page component

@input :question: button from #1
@input :question: navbar from #2
@input :question: windowbar from #5
@input :question: home_page from #7
@input :question: timeline card from #9
@input :question: app timeline mini from #10
@input :question: project card from #11
@input :question: app projects mini from #12
@input :question: about us from #13
@input :question: app footer from #14
[ ] compose all components into page component
@output :question: webpage component from comment

next #15

feedback 2023.06.08
Updated project structure and linking everything together.
It was quite a bit of work.
Hope we can keep the clean structure going forward :-)
If you make more sub components, just link the into the above issue and also add the next field for the appropriate outputs that will be used here above as inputs.


Intermediate Data Structure for Compiled Expressions

Brief
Compile ExpresisonSyntax's into an intermediate data structure (or language) that's used to evaluate the expressions faster.
Currently the largest cost in the evaluation of an expression is the several iterations over the ExpressionSyntax's tokens in order to figure out order of operations. If what this algorithm calculates was pre-computed then this would greatly increase the evaluation performance.
This language needs to be capable of describing "Function calls" (described in #1).
Examples
Simple Mathmatics
The expression 1 + (2 * 5) would compile to:
src = [1, 2, 5]
dist = [0]
trm = []

dist[0] = Multiply, src[1], src[2]
dist[0] = Add, src[0], dist[0]

Simple Logic
The expression 10 > 5 would compile to:
src = [10, 5]
dist = [0]
trm = []

dist[0] = GreaterThan, src[0], src[1]

Term Importing
The expression 20 / (Width - 5) would compile to:
src = [20, 5]
dist = [0]
trm = [Width]

dist[0] = Subtract, trm[0], src[1]
dist[0] = Divide, src[0], dist[0]

trm and src are interchangeable in fetching variables.
Multiple Destination Elements
The expression (5 + 5) / (15- 5) would compile to:
src = [5, 15]
dist = [0, 0]
trm = []

dist[0] = Add, src[0], src[1]
dist[1] = Subtract, src[1], src[0]
dist[0] = Divide, dist[0], dist[1]

Functions
The expression max (15, 5 * 4, 10) would compile to:
src = [15, 5, 4, 10]
dist = [0]
trm = [max]

dist[0] = Multiply, src[1], src[2]
dist[0] = Invoke, trm[0], src[1], dist[0], src[3]

Implementation
By using a similar method to CalculatedSpan's currently being used to evaluate the ExpressionSyntax, we can (instead of evaluating the operators found) record the order in which to execute the instructions.
Parameter Describing
Parameters could be described as an array of structs that reference indexes. If anything wants to be passed into an Invoke then it will have to be defined in an array.

This feature has now been implemented.
It has resulted in a 50% slower expression compile time and 30x faster typical expression evaluation (the benefits are even more tangible on longer expressions).


A proof of concept for making strippedSaveRequests optional

A quick PR regarding https://github.com/Laravel-Backpack/CRUD/issues/2104.

The copy in the config probably isn't in tone with what you've already got, and I'm not sure if it's necessary to exclude() anything from the request if we're working under the assumption that getStrippedSaveRequest() exists (in part) to obviate $fillable.

Yup, totally agree. Thank you for the POC @evanrthompson , it really helped. I moved things around and renamed them - please take a look at PR #2174 which builds on this one, and let me know what you think!
Cheers!


rust seems to be missing an so: dependency

Our rust package doesn't provide so:librust_driver...... Other distros including alpine do.  This hasn't been an issue because nothing was requiring that library.  After  https://github.com/chainguard-dev/melange/pull/1526 the dependency is being added in rust but isn't present as a provides in rust.
tar tvf ./packages/x86_64/rust-1.81-1.81.0-r0.apk  | grep librustc_driver
-rw-r--r-- root/docker  78827616 2024-09-28 20:00:07 usr/lib/librustc_driver-28b4e9cad0e1dafd.so

tar -Oxz .PKGINFO < ./packages/x86_64/rust-1.81-1.81.0-r0.apk | grep librustc_driver
depend = so:librustc_driver-28b4e9cad0e1dafd.so

Current with no provides or depends but does have the file installing into /usr/lib/.
https://apk.dag.dev/https/packages.wolfi.dev/os/aarch64/rust-1.81-1.81.0-r0.apk@sha1:37ab7c46fc4e41f9fcecf1993d175ef53956677e/.PKGINFO

@xnox  is this what you predicted? As far as I can tell it seems like providing that depending and providing that .so are correct.

Hopefully I just missed some corresponding '.so.'

Also it has this cute thing: usr/lib32/*.so as in that.

it also sets rpath
0x000000000000000f (RPATH)              Library rpath: [$ORIGIN/../lib]

we can turn rpath off in the configure, I have it off on my current local builds.

and the soname is
 0x000000000000000e (SONAME)             Library soname: [librustc_driver-28b4e9cad0e1dafd.so]

so this sounds like legitimate thing. haskell ocaml do similar as well btw. pretty sure the hash here depends on the compiler version and source code content etc. meaning it is stable abi; for matching compiler and toolchain.
given it is shipped within the same packakge; one can argue that one doesn't need to neither depend nor provide it.
As provides are exclusive.
In most other packaging systems, when trying to resolve and find shared library dependencies, normally the ${{targets.destdir}}/usr/lib,${{targets.contextdir}}/usr/lib,.... are all added to the search path. Such that self-referencing libraries are declared in provides; but not in depends.
However, self-serve provides and depends works too. Also not sure if it is a public library; or private to rust.
36eddaa8f776:/# apk info --provides systemd | grep so: | sort -u
so:libnss_myhostname.so.2=2
so:libnss_mymachines.so.2=2
so:libnss_resolve.so.2=2
so:libnss_systemd.so.2=2
so:libsystemd-core-253.so=0
so:libsystemd-core-254.so=0
so:libsystemd-core-255.so=0
so:libsystemd-core-256.so=0
so:libsystemd-shared-253.so=0
so:libsystemd-shared-254.so=0
so:libsystemd-shared-255.so=0
so:libsystemd-shared-256.so=0
so:libsystemd.so.0=0
so:libudev.so.1=1

36eddaa8f776:/# apk info --depends systemd | grep so: | sort -u
so:ld-linux-x86-64.so.2
so:libblkid.so.1
so:libc.so.6
so:libcap.so.2
so:libcrypt.so.1
so:libcrypto.so.3
so:libfdisk.so.1
so:libm.so.6
so:libmount.so.1
so:libssl.so.3

36eddaa8f776:/# find . -name libsystemd-core-256.so
./usr/lib/systemd/libsystemd-core-256.so

I'm not sure how the above is achieved. In most other packaging systems, this private internal library is neither provided nor depended upon. But we would want provides and depends if/when we split binaries that use that private internal library.

@justinvreeland  a file that is not a symlink and starts with lib.*.so and is in the public dlopenable location should generate depends and provides.
I don't know what should or should not happen with /usr/lib/systemd/libsystemd-core-256.so though. As that's not a default search location.

most packaging systems allow one to include/exclude extra search paths. and treat them as public or private (include in dependency graphs or not). It is confusing.

Seems like libsystemdcore is being properly detected as vendor'd. I've never had to use that functionality from my package manager and I think I'm glad for that.

Attempted rebuild
https://github.com/wolfi-dev/os/pull/30128
elastic build - did not generate neither depends nor provides
github actions - did not generate provides, did generate depends
I am perplexed as to why. Also perplexed as to the difference between the two.

Fetching download from https://github.com/wolfi-dev/os/pull/30128/checks?check_run_id=31130590397 and copying in yaml file and using melange scan on it, produces the GHA output. So can debug from here.

adding lots of print statements:
2024/10/06 06:25:21 INFO scanning usr/lib/librustc_driver-28b4e9cad0e1dafd.so
2024/10/06 06:25:21 INFO usr/lib/librustc_driver-28b4e9cad0e1dafd.so: wrong permissions

It is not marked as executable for some reasons.

library is not marked as executable, and hence no provides generated.
once marked as executable, provides is generated and depends is excluded (as it's the same package).


Pipeline fails due to Segmentation Fault

Culprit seems to be test_graph_pyg in tests/test_frameworks.py.

After discussion with @timkucera this can only be due to a version change in the dependencies that changed recently.

Fixed in #100


[Bug]: chromadb 0.4.18 Multi-modal Collection query does not work

What happened?
Huggingface is blocked.The only way I can get openclip model is from [https://www.modelscope.cn/models/AI-ModelScope/CLIP-ViT-H-14-laion2B-s32B-b79K/files].It's embedding is 1024.
I used it as the OpenCLIPEmbeddingFunction's model.Put images into collection,it seems OK . But when I query use one image,the result is random(every time get different image as result).
Versions
OS: windows 10    chromadb: 0.4.18    open_clip:2.23.0    torch:2.1.1+cu118
\venv\Lib\site-packages\open_clip\model_configs\ ViT-H-14.json  --> put model files from modelscope   under  /ViT-H-14
bug.zip
Relevant log output
No response

python 3.10

What do you mean by hugging face is blocked

Huggingface can not be visited from CN.


[microTVM][ARM] Keep microtvm testing only in QEMU Image

This would prevent rebuilding multiple image on each update on CMSIS, ethosu, etc.
cc @Mousius @alanmacd @areusch @gromero @leandron

In order to reason about this, it would be great to understand why do we maintain two seperate containers for microTVM and TVM, especially when QEMU is a software that runs on the cpu. (Sorry I might've missed the discussion why went on to create to two seperate images)
In an alternate world, we could consolidate all testing dependencies to ci_cpu and keep TVM and microTVM aligned in-terms of testing environment, unless we need conflicting dependencies in the testing for TVM vs microTVM not just additive ones.

Adding to Andrew's point, I think we can remove USE_MICRO since it's almost always ON. Also, I prefer to keep ci_qemu separate and also call it ci_microtvm. I believe this image could grow larger in future and if we combine it with ci_cpu it becomes similar to ci_cpu.

Adding to Andrew's point, I think we can remove USE_MICRO since it's almost always ON. Also, I prefer to keep ci_qemu separate and also call it ci_microtvm. I believe this image could grow larger in future and if we combine it with ci_cpu it becomes similar to ci_cpu.

I support this approach as well, having two smaller containers with a specific responsibility rather than one monolithic container should make it easier to manage in the long term as the needs evolve. The only downside is the typical container hopping for development, though I think we can figure out how to get that to work also.
Minor note, I think ci_micro rather than ci_microtvm as it's already identified as a tvm image?

I agree that having modular (smaller) container aids the ease of reproducability from a developer PoV.
I'm worried with this approach is that this creates a room for set of diveregent dependencies to be introduced between microTVM vs TVM (the deps that are not specific to micro), especially when they are not seperate projects. Right now, only thing that keeps the common deps align is on the basis that we use the same helper scripts (ubuntu_install*.sh) to construct the image.
E.g. : This could open up the possibility to advance the version of tensorflow supported by TVM project while microTVM lacking behind because there will now be tested in two environments.
Maybe we could create a base container with such common deps to ensure such divergence are harder to do ? (and extend that image into ci_cpu and ci_qemu)

cc : @leandron

Looking at the alternatives being proposed until now, I feel that for our current type of usage is makes more sense to unify ci_qemu into ci_cpu, for two reasons:

According to our Jenkinsfile, both jobs that require ci_cpu and ci_qemu will run on the same target machines, so the expectation is that our Jenkins nodes will more commonly pull ci_cpu + ci_qemu in terms of storage
Creating a base image with common dependencies, would also generate a side problem, which is a time dependency to rebuild our images (we can't build all of them at the same time), and the need to create a generic label e.g. latest or last-successful for this base image to be picked up in the dependant images. I'd like to avoid this if possible.

Given our current Docker update practices that don't require updating all images at once, I feel we better to consolidate the dependencies in one single image until we can devise better rules for Docker updating.

i think while i'm sympathetic to reducing the overall image disk size, in practice:

DockerHub stores these for us and we don't have a concern there
we have the problem of docker image bloat hogging disk on our CI nodes anyway due to image revisions, and have already solved that.

so i don't think we need to make that a priority in this decision. i think then that it comes down to what's operationally easier, and i think that's the POV @Mousius and @manupa-arm were advocating. i tend to agree here--another way that we could get into trouble with consolidating ci_cpu and ci_qemu is two different docker/install scripts could add conflicting packages. we can mitigate that by keeping microTVM separated, and I'd vote for continuing that with renaming ci_qemu to ci_micro.
cc @driazati @konturn in case they have other thoughts from a CI perspective.

I'm in favor of having a base image with common dependencies to eliminate human errors in build process for each docker image, but even with that people might add any script to any of the docker files. So as a reviewer we need to keep an eye on changes on those files. Also I think there shouldn't be any divergence between TVM and microTVM dependencies and I would like to second @manupa-arm's point on this.
For now, I think we can try to keep all microtvm testing in a single docker image and rename it to ci_micro to it make more readable. We can think about other proposals and maybe discuss it in one of the TVM community meetings.

Thanks all for the discussion!.

we can avoid dependency drift by being careful in reviewing Docker image changes.

If we are solely relying on the reviewers, we need would need better written guidance in an OSS project to aid both reviewers (to cite) and authors (to follow), on what could be added to : ci_base (if we are taking this approach), ci_micro and ci_cpu.
NOTE : Im scoping this discussion to the specific issue being discussed here.

but even with that people might add any script to any of the docker files. So as a reviewer we need to keep an eye on changes on those files.

I suppose how ci_base would help here is that we can make the above guidance to be simplified to say all the layers in the image added by ci_micro Dockerfile has to be micro specific.

@manupa-arm I agree with you. Both better documentation and having a ci_base image which has common dependencies are great ideas.
It would be great if we can make an action items list based on the discussion here.

i think most of the discussion here has aligned around purpose-built CI images. @leandron are your concerns assuaged?
regarding ci_base: I'm somewhat supportive of this, but currently unsure whether this would move the needle very much in practice and there are some operational concerns. we currently build images mostly automatically around the same time via the nightly rebuild and also in CI. the common deps we're talking about here are mostly a mix of apt packages plus some things built from sources downloaded from (i think) version-pinned URLs. there are some other things in here, to be sure--rust packages, for instance. i do agree that ci_base would enforce that we don't diverge, but just stating that i don't know, given the above, that i expect to see a huge effect in creating that. i agree with @Mousius that the layers would ideally be reused; i wouldn't underestimate the network transfer time, however.
I do want to note that we also mitigate drift in other was e.g. via common install scripts and (soon) via locked python dependencies (this more addresses the example of tensorflow divergence). however, i acknowledge the drawback that this is merely convention and dependent on reviewers.
for verticals like microTVM, i think a separate image makes sense. for e.g. backends, it's less clear--what if you want to test cuda with paddlepaddle? there is no such paddlepaddle dep for arm64, so it can't go in the base image. does this mean base images need to be arch-specific--if so, where's the line (e.g. what if it's available for 20.04 but not 18.04)?
so far as action items, i think we should capture the need of either a common base image or documentation into a GH issue. we should also update our docs accordingly. would love to hear more thoughts @Mousius @manupa-arm @leandron @driazati

@manupa-arm can you take a look again?

Thanks! looking good.
It would be great to capture the steps discussed and agreed in the issue (as per @areusch) and link to the PR.
@ashutosh-arm could you take a look as well from cmsis tests, whether they would be all run in ci_qemu now ?

afaik CMSIS-NN tests do not run on ci_qemu at present. In this code change, I don't see CMSIS-NN tests moved to tests/scripts/task_python_microtvm.sh. I am referring to https://github.com/apache/tvm/blob/6eb3a1fc3688bede69efd7f14b313b35497ccf02/tests/scripts/task_python_integration.sh#L64. Am I missing something @mehrdadh / @manupa-arm ?

I see.
Yes none of the contrib tests are run (that is how cmsis tests are run today in ci_cpu).
We need to add that as well then.

@ashutosh-arm thanks for catching this. I moved test_cmsisnn tests to qemu, there's also test_ethosn which we should move, but we need to update qemu image for that.
I think I need to send another PR for that along with sharding the qemu tests since it has timeout issue right now

@mehrdadh test_ethosn (unlike test_ethosu) is not related to microTVM.

@manupa-arm thanks for clarification! Then I think this PR is ready, I just need to figure out the timeout issue.
cc @areusch @driazati

just musing about naming--previously we called this image ci_qemu because it contained qemu. it seems like with this effort + riscv32 + the hexagon effort, we are gravitating more towards purpose-driven CI images (we discussed this before). there is already a ci_arm--shall we consider a container rename such as:

ci_arm -> ci_arm_aarch64
ci_qemu -> ci_arm_cortexm

@areusch I like to change the name, but I think ci_arm_cortexm is too specific. We could have riscv support with Zephyr in future which I assume the testing is gonna be part of this image. Then it would be confusing. I think ci_micro works better here. wdyt?

just musing about naming--previously we called this image ci_qemu because it contained qemu. it seems like with this effort + riscv32 + the hexagon effort, we are gravitating more towards purpose-driven CI images (we discussed this before). there is already a ci_arm--shall we consider a container rename such as:

ci_arm -> ci_arm_aarch64
ci_qemu -> ci_arm_cortexm

I'd suggest that ci_arm is renamed to ci_aarch64  .
Ramana

@u99127 i'm fine with that, should we then ci_cortexm instead?

@manupa-arm please take another look when you have a minute

just rebased with main, timeout issue should be resolved.

@manupa-arm friendly reminder about this PR. thanks!


Update Media Design School

School URL: https://www.mediadesignschool.com/
Course URL: https://www.mediadesignschool.com/courses/undergraduate-studies/bachelor-software-engineering-game-programming
The school email domain for students changed from @mediadesign.school.nz to @mds.ac.nz, the details of the change can be found here: https://www.mediadesignschool.com/student-information

@clancyduncan Thank you for the update! Pull request merged.


add debug logs to print cert chain

https://github.com/istio/istio/issues/9035
add more logs for debugging

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: quanjielin
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS [quanjielin]

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: quanjielin, wattli
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

security/OWNERS [quanjielin,wattli]

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

@quanjielin: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
88e969041ef6a9e2de461750aa5d1415b600e66c
link
/test istio-pilot-multicluster-e2e

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

/cc @wenchenglu to get to 1.1


Optimize hexWrite with an array lookup table

Should fix the slowdown introduced by the hash table lookups in #303
My own benchmarks seem to indicate a 10x speedup.

Wrote a proper benchmark. Here are the numbers:
Without this PR:
$ node perf/write-hex.js
BrowserBuffer#write(4096, "hex") x 5,697 ops/sec ±0.29% (91 runs sampled)
NodeBuffer#write(4096, "hex") x 105,578 ops/sec ±0.04% (90 runs sampled)
Fastest is NodeBuffer#write(4096, "hex")

With this PR:
$ node perf/write-hex.js
BrowserBuffer#write(4096, "hex") x 34,100 ops/sec ±0.07% (93 runs sampled)
NodeBuffer#write(4096, "hex") x 105,699 ops/sec ±0.04% (92 runs sampled)
Fastest is NodeBuffer#write(4096, "hex")

Though, on my local machine I was getting an even larger speedup.

I added more cases to the test. It's a bit spammy now. Let me know if you want me to reduce that.

Thanks for your work @chjj


fix: Vs Code debugger does not use https protocol when starting dev server

Description

Created security context for method  serve(handler, ip, port, securityContext: securityContext) as listed in the documentation.
Ran the dev server using Dart Frog: Start and Debug Development server option in the Command Pallet of VS code.
Specified port as 8443 when asked "which port number server should start on"
Specified 8181 when asked "Which port number the Dart VM server should listen"
Browser opens up and shows http://localhost:8443/ in the URL window and  following message:
6 This site can’t be reached. The webpage at https://localhost:8443/ might be temporarily down or it may have moved permanently to a new web address.  ERR_FAILED

Expected Behavior

Response returned in index.dart page is expected to be displayed.
https protocol to be shown in URL when security context used in the serve() call in run() method.

@Tusshu thanks for opening an issue!
I haven't tried to reproduce, but as far as I believe what you're stating is a valid request. The browser should open with https when a security context is specified.
As far as I am concerned, the Dart Frog Daemon doesn't report the information on whether or not the Dart Frog project is using a Security Context or not. Hence, to land this change we would have to:

Update the Daemon to report if a security context is being specified
Update the VS Code extension to check with the Daemon if the current Dart Frog project is using a security context and open with HTTPS accordingly

I'm not sure if the team has bandwidth to prioritise this work right now (cc: @tomarra ), however, if you're interested in contributing to this effort we can definitely help you review and land the Pull Request.

Thanks for your response!
I would love to do what you are suggesting. But with current assignments,
it will be difficult to find the time this task requires.
I will try to understand the code as and when I find some time but I am not
able to commit.
Currently I will continue my project using Shelf. But I was impressed with
Dart_frog and really wanted to move to that platform.
Thank you again for your response.
Tushar Kale
On Tue, Jul 9, 2024 at 5:01 AM Alejandro Santiago @.***>
wrote:

@Tusshu https://github.com/Tusshu thanks for opening an issue!
I haven't tried to reproduce, but as far as I believe what you're stating
is a valid request. The browser should open with https when a security
context is specified.
As far as I am concerned, the Dart Frog Daemon doesn't report the
information on whether or not the Dart Frog project is using a Security
Context or not. Hence, to land this change we would have to:

Update the Daemon to report if a security context is being specified
Update the VS Code extension to check with the Daemon if the current
Dart Frog project is using a security context and open with HTTPS
accordingly

I'm not sure if the team has bandwidth to prioritise this work right now
(cc: @tomarra https://github.com/tomarra ), however, if you're
interested in contributing to this effort we can definitely help you review
and land the Pull Request.
—
Reply to this email directly, view it on GitHub
https://github.com/VeryGoodOpenSource/dart_frog/issues/1440#issuecomment-2217044119,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4AJMA43U4XRFOD3EPO2FTZLORGLAVCNFSM6AAAAABKNYFOLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJXGA2DIMJRHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Tusshu no worries I understand. You can still use Dart Frog and launch using Dart Frog CLI instead of the extension, or simply update the URL to include the "s" manually.
If at any point you would like to contribute let me know and I can get you assigned. For the time being you can track how the team prioritises this issue by watching it within the Full Board.

That is good news!!!
You mentioned "simply update the URL to include the "s" manually"
I am not sure how to do that. In VSCode, I click on the Run | Debug above the response function to start the server. It asks for two ports, 8080 and 8081 before starting the server. I can specify  8443 instead of 8080. But there is no access to URL where I can specify https.
How or where do I get access to the URL?
Thanks!

You mentioned "simply update the URL to include the "s" manually"
I am not sure how to do that. In VSCode, I click on the Run | Debug above
the response function to start the server. It asks for two ports, 8080 and
8081 before starting the server. I can specify 8443 instead of 8080. But
there is no access to the URL where I can specify https.
How or where do I get access to the URL?
Thanks!
On Tue, Aug 13, 2024 at 7:12 AM Alejandro Santiago @.***>
wrote:

@Tusshu https://github.com/Tusshu no worries I understand. You can
still use Dart Frog and launch using Dart Frog CLI instead of the
extension, or simply update the URL to include the "s" manually.
If at any point you would like to contribute let me know and I can get you
assigned. For the time being you can track how the team prioritises this
issue by watching it within the Full Board
https://github.com/orgs/VeryGoodOpenSource/projects/1/views/4.
—
Reply to this email directly, view it on GitHub
https://github.com/VeryGoodOpenSource/dart_frog/issues/1440#issuecomment-2285988288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4AJMAKOOO4IDPPH6RBNPTZRHS3DAVCNFSM6AAAAABKNYFOLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBVHE4DQMRYHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

You first need to set the security context as specified in the documentation.
Once you have that going, you can attach a debugger by using the "Debug" above the response function, such will open a web browser, but using HTTP rather than HTTPS. If you modify the browser URL to include an "s", you'll see how the breakpoints are hit when in debug mode. Another option is to use tools like Postman, curl, and use the endpoint you wish.
I hope this makes sense 🙌 , let me know if it helps.


Add AlexVulaj to approvers

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 26.32%. Comparing base (820bf4e) to head (82659c8).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #243   +/-   ##
=======================================
  Coverage   26.32%   26.32%
=======================================
  Files          11       11
  Lines        1056     1056
=======================================
  Hits          278      278
  Misses        764      764
  Partials       14       14

/lgmt

/lgtm

/lgtm


www/caddy: Add remote_ip matcher for access list functionality in Layer4 proxy

This PR adds:
layer4.matchers.remote_ip - matches connections based on remote IP (or CIDR range).
Configuration example (generated Caddyfile):

With Access List: Allow IPs <IP_ADDRESS> and 10.0.04 to access SSH on <IP_ADDRESS>:22
Without Access List: Allow any IPs to access http host opnsense.example.com on <IP_ADDRESS>:8443

{
	servers {
		listener_wrappers {
			layer4 {
				@797661c7-8925-4bc5-88c1-2dda4682194c ssh
				route @797661c7-8925-4bc5-88c1-2dda4682194c {
					subroute {
						@allowed_ips remote_ip <IP_ADDRESS> <IP_ADDRESS>
						route @allowed_ips {
							proxy <IP_ADDRESS>:22 {
							}
						}
					}
				}
				@85a414c7-2142-4332-9917-1995aeb887aa http host opnsense.example.com
				route @85a414c7-2142-4332-9917-1995aeb887aa {
					proxy <IP_ADDRESS>:8443 {
					}
				}
				route
			}
			tls
		}
	}
}

Tested it and it works fine.
The final piece in the puzzle that was missing to make this new Layer4 feature good. xD

Merged, thanks!


Add a default implementation for setBlocks.

Contains
Makes the setBlocks addition added by #2453 not break the Pathfinding module.
How to test
Build this PR with Pathfinding module. There should be no compile error.

Uh oh, something went wrong with the build. Need to check on that

X-reference: https://github.com/Terasology/Pathfinding/pull/25

Compile error here was just from importing Maps from a wrong package, the one that previously came from a PC Facade dependency now out of the way. @flo: you might want to run a gradlew cleanIdea idea to make sure the dependencies are fully updated and cleaned up :-)
Fixed up and merged, thanks! This may be our first example of an engine API break then quickly resolved via default method, woot!


(GH-1998) Create rakelib directory for Rake tasks

This adds a new rakelib directory in the repository root. This
directory contains rake tasks for generating docs, schemas, powershell
module files, and running tests. Each of these files is automatically
loaded by rake when running the rake command.
This also wraps several tasks and require statements in a begin
block, allowing rake to attempt to load development gems and still
continue if they are not available in the environment. This lets other
tasks, such as the powershell module tasks, to be loaded and executed
even if other tasks cannot be loaded.
Several tasks have also been removed, such as rubocop and
update_submodules, as they were either redundant or unused.
Lastly, this renames several tasks to better indicate what the tasks are
used for. All of the tasks previously under the integration namespace
are now under the tests namespace. Standalone rspec tasks, such as
unit, have also been placed under the tests namespace. Tasks used in
CI have been placed under the ci namespace. Tasks under the ci
namespace have also had their descriptions removed so they are not
displayed in the list of tasks when running rake -T, as they typically
will not be run directly by users.
!no-release-note

CLA signed by all contributors.

I would prefer to just run rake docs:all and rake schemas:all rather than have rake generate_docs and rake  generate_schemas that are outside the normal hierarchy.

This new list of tasks is soooooo much nicer.

LGTM - I think we just need to make sure https://github.com/puppetlabs/bolt-vanagon/pull/143 get's merged after this and before release.

We'll also need to merge https://github.com/puppetlabs/ci-job-configs/pull/7192 so the docs publishing job uses the new docs:all task.


Add Django 1.11 support

No code is impacted by Django 1.11 and tests pass fine

Coverage remained the same at 87.97% when pulling 3f3e524a6ce1337b626be39d5b2c498340da6b79 on yakky:feature/django-11 into b47015e472f6c90e9955e8fd13912f7f18e11da7 on aldryn:develop.

Coverage remained the same at 87.97% when pulling<PHONE_NUMBER>7adac237bd214af2bc3e7c068ee02a on yakky:feature/django-11 into b47015e472f6c90e9955e8fd13912f7f18e11da7 on aldryn:develop.

This looks great!  Any plans for a release on PyPI?

While not such a big deal using straight pip, when using pipenv, the current release triggers an error if you try to create a Pipfile.lock with Django>=1.11.
$ cat Pipfile
[[source]]

url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[dev-packages]

[packages]

django = "==1.11.8"
aldryn-common = "*"
$ pipenv lock
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.


How to Create a user for BC Device License type  in Docker Environment ?

@freddydk
Hi Freddy
Can we create a user for BC Device License type  in Docker Environment ?
if possible ,then can you please suggest me steps for creating  a user  for BC Device License type  in Docker Environment.
Also please suggest what are the limitations for BC Device license.
Thanks in advance
Thanks and Regards
Divjot Singh

This repo is for issues in the AL language/compiler, not other topics. Try Docker if you want to ask Freddy something as he's pretty active there.

This repo is for issues in the AL language/compiler, not other topics. Try Yammer if you want to ask Freddy something as he's pretty active there: https://www.yammer.com/dynamicsnavdev#/home


SSR problem in vue.draggable context

Problem:
Hello @owen-m1 , version <IP_ADDRESS> of sortable.js introduced a call to navigator global property.
This is breaking SSR usage of vue.draggable: building the template on the server-side using node (none browser context).
I tried a fix to require sortable.js only in browser context (https://github.com/SortableJS/Vue.Draggable/issues/724), but it seems

not to cover all scenarios (see discusrion on https://github.com/SortableJS/Vue.Draggable/issues/724)
to introduce regressions (https://github.com/SortableJS/Vue.Draggable/issues/731, https://github.com/SortableJS/Vue.Draggable/issues/730, https://github.com/SortableJS/Vue.Draggable/issues/728)

I can not think of another fix on vue.draggable side thougth.
Could it be possible to check for navigator early in sortable.js to avoid to raise exception when navigator is not defined?

https://github.com/SortableJS/Vue.Draggable/issues/732

I am trying to figure out a solution but it does not make sense to me since the older versions of sortable had the exact same reference to the navigator. The only difference is that in the older versions, Sortable threw an error if the window was not defined, but that is still an error so I don't understand how SSR ever worked with Sortable.

The difference should be the code executed just by calling import vs the code executed by the new Sortable.
Vue.draggable is calling the new Sortable only when window is defined.
That solution was working till version 1.9.0 of Sortable.js.
Now the problem is happening during the import.

In the previous versions (such as 1.9.0), the navigator code was executed when Sortable was imported. You can see the code here. It is not within the Sortable function but within the UMD function that is called when the script is loaded.

That's weird

In version 1.9.0, you had this early return:
})(function sortableFactory() {
	"use strict";

	if (typeof window === "undefined" || !window.document) {
		return function sortableError() {
			throw new Error("Sortable.js requires a window with a document");
		};
	}

Could you re-introduce it in version 1.10?

@David-Desmaisons I have done this in commit 5fccf71d9c9971a48acc6aa02d911bd9ebfeed08.
Please build Sortable and test it or ask the people who reported this bug to test it, just to make sure it actually fixed the problem.

"TypeError: u is not a constructor"
This is what i am seeing

@David-Desmaisons Could it be possible to release a new version with these changes?

I am using it in vue-electron it not coming up

it seems it can only work on browser environment

Error in mounted hook: "TypeError: Sortable is not a constructor"

@David-Desmaisons Is it confirmed that it works?

@owen-m1 I will perform some manual test with the fixed version locally. If everything runs OK, I will let you know.

Hi Owen, I've tested the fix, and it doesn't work for me. The problem is that there is quite a few browser specific code executed as soon as someone import/require this library.
I'm using Vue.Draggable that require Sortable. The import is made on serverside and on clientside. But the Sortable constructor is only called in mounted function, which is only executed on the client. I tried to move all the browser specific code in the constructor instead of the root of the module and it works.
I've a commit with the changes https://github.com/Tarrask/Sortable/commit/8ff64de40ca8ef28e30b3559d7463ec2e40c1f2e that works in my case. It's a bit to early to submit a merge request as I don't know yet if it break anything else. For exemple, if you call the constructor more than one time, it will register some listeners twice.

@Tarrask Ok, so Sortable never worked for SSR, even before version 1.10.0. That makes more sense.

@owen-m1 Exactly, that what I found. But importing it should be harmless.
Actually, a very simple test is with a small js script that just require the library, eg: const Sortable = require('Sortable'). when executing with node, it should not throw anything. It was ok with the 1.9.0 but throw a ReferenceError exception with the 1.10.0. And with the latest it throws the custom exception from windowCheck.js

@Tarrask Thank you, I see the issue now. Sortable never supported SSR, but if you imported Sortable without a window object, it would only throw an error when you called the Sortable constructor.

@owen-m1 to clarify: sortable by itself did not support SSR but vue.draggable do.
Mainly vue.draggable is avoiding to run any sortable code in o node context.
The problem in version 1.10.0 is that the simple fact of importing Sortable in a node context will throw an exception.

Create file test.js containing:
require('sortablejs');
Run in command line node test.js

I have traced some refresh issues back to this, what's the ETA of the fix? Thanks!

@UnaiRA @stuta Please try building commit 576e33540c545dcefe0d805754ac2f454b55538f and tell me if it fixes the problem. I just made it so that Sortable will not throw any errors on import if the window or document is not defined. Obviously it won't work properly unless it is imported in a browser context, but this has always been the behaviour of Sortable.

@owen-m1 for me, it works

@owen-m1 Great, is this making it to a RC anytime soon?

@UnaiRA I will release 1.10.1 tonight.

Thank @owen-m1 , look forward to new release.

@David-Desmaisons @serdarkok @UnaiRA @Tarrask 1.10.1 is released

Thanks!!! I will release a new version of Vue.draggable by Today

Version 2.23.2 released! Thanks @owen-m1 and @Tarrask


SAMZA-2267: Allow overriding RocksDB file size parameters

@mynameborat Thanks for the quick review. I have made the changes that you suggested.

Reverted.


A error in the code.

Hey,
I'm really sorry for opening this but I have this error:
 node index.js
node:internal/modules/cjs/loader:936
throw err;
^
Error: Cannot find module 'dotenv'
Require stack:

/home/runner/just-woirk-please/index.js
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:94:18)
at Object. (/home/runner/just-woirk-please/index.js:2:20)
at Module._compile (node:internal/modules/cjs/loader:1101:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:79:12) {
code: 'MODULE_NOT_FOUND',
requireStack: [ '/home/runner/just-woirk-please/index.js' ]
}
exit status 1

use npm i dotenv

Sorry I was very dumb I never do node.js shit


CellularTile: stop annoying me, Google

No need for this yet

We will have a better implementation in future


feat(client): ts-migrate /client/src/analytics

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Refers to #42256

Hi @raisedadead I have gone ahead and checked the boxes off. I believe the PR should be fine now.


Task:418942 Fix insufficient error message when wrong username and password are provided in DeployTestAgent Task

Hi @prawalagarwal, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Prawal Agarwal). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

put some description in the pr, so that its easier to review and refer in future.
fix looks good.

bump up the task minor version as sid as asked

approved with suggestions

I saw at many places this --verbose is not being followed please check other files too


local configure broken on macOS since 7.8.2

7.8.1 works like a charm:
 2018-07-25 22:32:58 ⌚  Zrzka in ~
○ → sudo resin local configure ~/Downloads/resin-rust-thermometer-raspberrypi3-2.13.6+rev1-v7.14.0.img
? Network SSID (My_Wifi_Ssid)

7.8.2 and 7.8.3 not, stuck in a limbo, it's waiting for something, no output, nothing. Let me know how can I help if you have no macOS around.

It's been a little while now @zrzka, but does this work now if you retry?
I've only just managed to find time & an OSX machine to do more thorough testing, but now everything seems fine to work fine for me with:

CLI: 7.9.2
Node: 8.11.4
OSX: 10.11.6

It's surprising we haven't had any other user reports in the meantime too, if it's an ongoing issue. If you're still seeing it, can you tell me a bit more about your environment? Are you using an unusual shell by any chance? I think I've seen similar issues in some cases like that elsewhere.

@pimterry last version I did test was 7.8.3. Here're the results of newer versions:

7.8.4 - doesn't work
7.8.5 - doesn't work
7.8.6 - doesn't work
7.9.0 - doesn't work
7.9.1 - doesn't work
7.9.2 - doesn't work

Downgraded to 7.8.1 and it works. I don't have anything weird installed ...

I do use iTerm.app, but I did test all these versions in macOS Terminal.app as well
I do use bash

Versions:

bash 3.2.57
node v8.11.3
macOS 10.13.6 (17G65)

The only difference here is node (8.11.3 vs 8.11.4) and macOS version (10.13.6 vs 10.11.6). Did update to 8.11.4 and no luck, still nothing.
It's stuck here. reconfix.readConfiguration is called and .then(getConfiguration) is never called. So the problem is inside readConfiguration.
When I check diff between 7.8.1 (works) and 7.8.2 (doesn't work), there was a reconfix update 0.0.3 -> 0.1.0. Which kind of confirms reconfix issue?

Further details, for reference:

This only happens on dashboard-downloaded images with wifi configured.
It appears to be caused by ext2fs, which hangs when trying to read more files in parallel than the threads Node has been configured with. See https://github.com/resin-io/node-ext2fs/issues/46 for details.
We can fix by increasing the thread count (UV_THREADPOOL_SIZE=64) in the short-term or reading sequentially, and medium-term we need to resolve the underlying deadlock itself.

Confirmed, 7.9.3 fixes my issue and it works like a charm.


feat: separate tagged image providers

This PR makes the following top-level changes:

image.Provider interface has been reworked so providers have Name() method
image.Provider.Provide is adjusted to accept userInput and must return an image object fully populated (e.g. .Read() has been called)
A top-level stereoscope.ImageProviders function is added, allowing interested parties (e.g. syft) to get access to the individual tagged image providers
A top-level stereoscope.ImageProviderConfig is added which is the uber-configuration needed by all stereoscope-defined providers

Note: the top-level GetImage and GetImageFromSource remain unchanged with the caveat that the image.Source has changed from an int to a string. These functions will use the default set of image providers, so should continue to behave about the same as before, with the other caveat that if the user has a docker daemon and another supported daemon (containerd, podman), each daemon may be tried instead of stopping after attempting docker, which is the behavior today.
TODO:

[ ] naming: is Resolver better than Provider (or something else)?
[ ] should image.Platform be a parameter to the Provide function instead of configuration?
[ ] fix existing tests
[x] add more tests exercising the full functionality of each image provider
[x] fully integrate with syft PR https://github.com/anchore/syft/pull/2610

should image.Platform be a parameter to the Provide function instead of configuration?

yeah, I think so

naming: is Resolver better than Provider (or something else)?

I'm a fan of "provider" here, but will give it some thoughts