CUBIC congestion control

Implemented based on RFC8312 "CUBIC for Fast Long-Distance Networks"
CUBIC is the default CC algorithm.
CUBIC specific variables is stored to cubic::State. I added
this to Recovery structure itself. If you use Reno only
this will be a waste of memory if you use Reno, but the overhead
is small (4 fields) for now. It can be dynamically allocated later.
f64 is used for various calculations. Optimization using integer ops is a future task.
Use libm::cbrt to avoid linking with -lm for C applications. Note that libm:cbrt
is slower than C cbrt() which is asm-optimized (roughtly 2x when I
test in MacOS) but the difference is small.
For config API, to use Cubic explicitly for the connection, call the following:
Rust: config.set_cc_algorithm(recovery::CongestionControlAlgorithm::Cubic);
C: quiche_config_set_cc_algorithm(config, QUICHE_CC_CUBIC);
CongestionControlAlgorithm exported as public. Also fixed the documentation.
CongestionControlOps: add collapse_cwnd()

I applied the nits manually since they are pretty minor. Will merge after CI is green.


[BUG] Node interface not defined in IE8

Current behavior

On-demand header fails in IE8 because Node is not defined in https://github.com/cfpb/cfgov-refresh/blob/master/cfgov/unprocessed/js/modules/util/behavior.js#L74

Expected behavior

Check existence of Node support before calling it or check nodeType instead (see http://stackoverflow.com/questions/13377887/javascript-node-undefined-in-ie8-and-under)

Steps to replicate behavior

Run gulp scripts:ondemand
Open /test-fixture/ in sauce labs (won't work in local VM unless localhost routing is set up).
See error in JS console that a function is expected for Node.

Screenshots
Current

In on-demand header behaviorElement where this error is thrown is actually the string a[href^="#"]``, but it hits the second else ifthat checksNodebefore getting to the thirdString` check.

I thought IE8 was getting the no JS experience.

@sebworks ah right, good point! The on-demand header must not be falling back properly.

@anselmbradford, can i close this issue?

I believe this is still a cfgov-refresh issue in that https://github.com/cfpb/cfgov-refresh/blob/master/cfgov/legacy/templates/front/base_update.html looks like it needs this code. @rosskarchner do you know what pages are using base_update.html linked above?


Error selectedIndexId when KeysType of table is UNIQUE

Describe the bug
When user query the UNIQUE table, the new mv selector could not select correct indexId.
The warning log like
2020-06-04 14:45:58,361 WARN 101 [OlapScanNode.updateScanRangeInfoByNewMVSelector():232] Using the old scan range info instead of the new one. The key type of table is aggregated., The new selected index id 0, pre aggregation tag true, reason null. The old selected index
id 213392 pre aggregation tag false reason No AggregateInfo

To Reproduce
Steps to reproduce the behavior:

Create a unique table

 create table unique_table(k1 int, k2 int) UNIQUE KEY(k1) distributed by hash(k1) properties("replication_num" = "1");

insert value

insert into unique_table values(1,1);

query

select * from unique_table;

see fe.log

2020-06-04 15:18:01,420 WARN 131 [OlapScanNode.updateScanRangeInfoByNewMVSelector():232] Using the old scan range info instead of the new one. The key type of table is aggregated., The new selected index id 0, pre aggregation tag true, reason null. The old selecte        d index id 10007 pre aggregation tag false reason No AggregateInfo

Expected behavior
No warning log, the new selector choose the correct index id which is same as the rollup selector.

In my 0.12.17 log, this warning also appear.

WARN 8695 [OlapScanNode.updateScanRangeInfoByNewMVSelector():232] Using the old scan range info instead of the new one. The key type of table is aggregated., The new selected index id 461162, pre aggregation tag false, reason The aggregate operator does not match. The old selected index id 461162 pre aggregation tag true reason null

配置开启了物化视图 enable_materialized_view = true


Allow the user to customize the scraper

I am a newbie to web crawler. Now I am gong to build a django web app, in a part of which users fill up a form(keywords and time,etc.) and submit it. Then the scraper will begin to work and craw the data according to the user's requirement at a specific website(set by me). After that the data will pass to another model to do some clustering work. How can I do that?

After I made the scraper as shown in the tutorial, I put the model work I had to do within the pipelines.py file since by then all the data is available.

So It is not available at this moment?
By the way, when I did as you say in the DDS tutorial of creating model classes. I ran  python manage.py makemigrations craw(DDS belongs to this app). But there were errors:
SystemCheckError: System check identified some issues:
ERRORS:
craw.Article.checker_runtime: (fields.E300) Field defines a relation with model 'SchedulerRuntime', which is either not installed, or is abstract.
craw.NewsWebsite.scraper: (fields.E300) Field defines a relation with model 'Scraper', which is either not installed, or is abstract.
craw.NewsWebsite.scraper_runtime: (fields.E300) Field defines a relation with model 'SchedulerRuntime', which is either not installed, or is abstract.

In addition, I got an error when I ran
scrapy crawl article_spider -a id=1 -a do_action=yes
ImportError: No module named settings.

Hi @rylanchiu, if you have such specific requirements, I'm not sure, if django-dynamic-scraper is the right library for you, maybe you should deal with Scrapy directly?
Your last problem with the ImportError sound like a path problem, if he's not finding the settings.py file.

I need to scrap js content. But scrapy seems to just enable me to get static content

My path is as below, @holgerd77 :
-news
|___scrapy.cfg
|___cluster
|___craw
|___migrations
..........
|___scraper
|____pipelines.py
|____settings.py
|____spiders.py
|____spiders.pyc
|___news

Hmm, looks good, are you running the scrapy command from within the news directory?
If you want to scrape JS content, you can also use Scrapy with the Scrapy-Splash/JS library which is also used for scraping JS content in DDS.

@rylanchiu , hey i dont know if this problem was resolved but i had the same issue with settings.py not  found. Incidentally i fixed this by adding an init.py file in the same directory are the settings.py file. I also changed the directory itself from scraper to another name then altered the scrapy.cfg file to the new name.
@holgerd77  i really like this project and i see myself using it alot. If you dont mind me asking is there a way to follow links like the CrawlSpider?

my path as below:
├── scrapy.cfg
└── stack
├── init.py
├── items.py
├── pipelines.py
├── settings.py
└── spiders
└── init.py
i have same error with @rylanchiu
i try remove init.py but nothing happen.
@cmwaura can y tell about how to fix this error
thanks

@giangnm58 i would suggest checking the scrapy engine(scrapy.cfg) and try and figure out if its pointing directly to to settings.py   in the folder containing the spiders. if that is fine try and play around with the folder names you may have used the same folder name twice and thats why the engine is getting confused. If thats fine, check the SPIDER_MODULES in the settings.py and make sure that is configured properly like the this example. If all that is fine, hit me up and send me the source code i will look at it.

@holgerd77 so i have been religiously going through the documentation and it seems that you actually included the properties of crawl spider with the detail page on the django interface. Cheers

@cmwaura Hi Crispus, sorry for being so super-late with my answer.

Yes, an __init__.py file has generally to be in every folder with Python files to be interpreted as Python modules, that's a general Python thing, see:
http://stackoverflow.com/questions/448271/what-is-init-py-for

There is an open issue to integrate the flexibility of Scrapy CrawlSpider into DDS, see https://github.com/holgerd77/django-dynamic-scraper/issues/11, no estimated time though when this will be implemented


feat: add new lsp semantic token highlight groups

catppuccin/nvim#427
rose-pine/neovim#141

Thanks you for using every colorscheme :)


Revert "use random port for catalyst mock server (#1860)"

This reverts commit 275b69576e427a5f094858516142d3082b6e40fa.
Looks maybe like this contributed to CI failures?

Nope.


question about backbone

Hello and thanks for your amazing work.
I noticed that in the paper it is mentioned that for both MSCIL and FSCIL settings, Resnet18 is used as the main network architecture, however in the code a pre-trained ViT model is used.
I would like to know whether the results in the FeCAM paper are based on ResNet18 or ViT.

Hi, the results in the FeCAM paper are based on both Resnet18 as well as pre-trained ViT. Most experiments in the paper for MSCIL and FSCIL are using Resnet18. We have the experiments using ViT models only in Table 2 of the paper. The network used for experiments is mentioned appropriately in the paper. Have a look.
So, we release the code for reproducing all these experiments.

Thank you for your response.
I misread the code regarding Table 1. I'm sorry for bothering you.


update the notificaitonRecord name to distinguish with spec.notificaiton

What type of PR is this?
refactor
What this PR does / why we need it?
Update the key value from status.Notification to status.NotificationRecord

To match the type name of notifiactionRecord
To distinguish with the spec.Notification

Which Jira/Github issue(s) this PR fixes?
Special notes for your reviewer:
Pre-checks (if applicable):

[ ] Tested latest changes against a cluster
[ ] Ran make generate command locally to validate code changes
[ ] Included documentation changes with PR

Codecov Report

Merging #33 (6e4e4f9) into master (9947798) will not change coverage.
The diff coverage is 90.90%.

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   58.65%   58.65%
=======================================
  Files          22       22
  Lines        1144     1144
=======================================
  Hits          671      671
  Misses        413      413
  Partials       60       60

Impacted Files
Coverage Δ

pkg/util/test/generated/mocks/client/cr-client.go
40.00% <ø> (ø)

...pis/ocmagent/v1alpha1/managednotification_types.go
80.48% <66.66%> (ø)

...test/generated/mocks/ocmagenthandler/interfaces.go
100.00% <100.00%> (ø)

/lgtm


The Raulnarok PR of 2018

This PR does a number of things, which couldn't really be broken out into smaller pieces:

It moves all of runtime, platform, and tracelib under a src top-level directory
It creates a src/planning directory and moves strategizer.ts into it
It modifies the TS compiler config to take input from src/runtime and src/planning, and put it's output in parallel directories under build
It makes imports of non-TS js files by TS files work by hard-linking a long list of stuff from src to build, so that imports during compile find the files in src, and imports at runtime find the same files in build.

All tests pass.
There is much more to do. Most notably, the linking mechanism should go away as soon as possible. As JS is converted to TS, entries for the JS files should be removed from the list. Hence the name of the list file is 'tools/reducethislist'. Many files are linked that aren't js, (mostly test artifacts) because they live in the src tree and are loaded at runtime. These should be moved out, or the loads adjusted, so links in the build tree aren't necessary. There is lots of low-hanging fruit. The big win is that there are no longer any ts or ts-build directories, and ts files can live anywhere, as it's now very easy to add a new directory to the tsc input.

Nice work Raul!


buildBazelPackage: fix directory symlink handling

Motivation for this change
The previous behaviour would work fine as long as symlink is a link to
a file. If is a link to a directory though, the new ln wouldn't
overwrite it but would create a new link in that directory (with the
name of the link source).
Instead, we can precompute the target location, then first remove the
symlink and write the new one in its place.
CC @uri-canva
Things done

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

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

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

This shouldn't cause any changes in existing packages (since if they worked, the symlinks must all have been files and nothing has changed for files).

I pushed another commit that avoids network timeouts due to multithreading.

Also CC @kalbasit

@GrahamcOfBorg build bazel-watcher


Show UI instantly (#1665)

@ihaid Could you please test it with all routes? The thing is that now we will show components even if the account state is not fetched yet. So I made all changes needed, but want to be sure that all routes work when you refresh the page and don't throw any errors.

@corwinharrell Could you please check one thing? With a slow network, there might be a situation when the UI is shown immediately but we still are loading the account state, so I added animated three dots into the select account box - but maybe you can propose a better solution without many changes needed. Here's how it looks:


Free text in description.

There are certain risks associated with free text, some of which are elaborated in threads like these (though not entirely) [https://github.com/openid/OpenID4VP/pull/220#discussion_r1696310253(https://github.com/openid/OpenID4VP/pull/220#discussion_r1696310253)
I probably won't be able to convince the authors in removing the free text description property from the metadata, which is defined as A human-readable description for the type, intended for developers reading the JSON document. So at least would be great if security considerations for free text can be added.
Thanks.

I'm not sure... While the risk is real, so are many other risks. It's 2024 and developers should have learned not to trust information. We also don't consider warning people of SQL injection attacks via JSON metadata files. But maybe we should?
Anyway and nonetheless, to see what it would look like, I drafted a PR: https://github.com/oauth-wg/oauth-sd-jwt-vc/pull/262


Arrays, or Groups Feature

Hello, just wondering if there are any plans for groups, or arrays.
I noticed stacks, but besides the visual implementation, i can't seem to access an array of nodes in a stack
Or maybe is there another style of visual coding where multiple nodes can be grouped together.
any suggestions, or even some direction where to look would be great.

Hey!
Groups already exists but it's the standard GraphView implementation:
 you can create them with the context menu in the graph
I have no plan to add new "containers" right now.
Note that you can access the nodes in a stack with this API: https://github.com/alelievr/NodeGraphProcessor/blob/master/Assets/com.alelievr.NodeGraphProcessor/Runtime/Elements/BaseStackNode.cs#L30 which gives you the GUID of the nodes, you can then get the node back using the nodesPerGUID field like I do here: https://github.com/alelievr/NodeGraphProcessor/blob/master/Assets/com.alelievr.NodeGraphProcessor/Editor/Views/BaseStackNodeView.cs#L59

Thank you for the reply
Based on the info, stacks should work well,
thanks and keep it up.
Mike


jit_compile control in BaseImageAugmentationLayer

This is just a follow-up of
https://github.com/keras-team/keras-cv/issues/165#issuecomment-1083502165
@qlzh727 What do you think about adding an extra parameter to the base class for jit_compile?
https://github.com/keras-team/keras/blob/master/keras/layers/preprocessing/image_preprocessing.py#L413-L414
So that we could optionally use something like:
f = def_function.function(self._augment, jit_compile=True)
self._map_fn(f, inputs)

From Keras 3, jit_compile is set to auto in the model.compile, which means it will use JIT if the model allows it.
Can we close the issue, considering the Keras 3 implementation.

Is it binary for the library user?  e.g. whole model compile or nothing?

From the doc: https://keras.io/api/models/model_training_apis/

jit_compile: Bool or "auto". Whether to use XLA compilation when compiling a model. For jax and tensorflow backends, jit_compile="auto" enables XLA compilation if the model supports it, and disabled otherwise. For torch backend, "auto" will default to eager execution and jit_compile=True will run with torch.compile with the "inductor" backend.

But here we were talking about BaseImageAugmentationLayer not the whole model interface. In any case I don't know all the new refactors so do what you want with this ticket.

BaseImageAugmentationLayer subclasses Keras Layer class and Keras Layer has an argument for operating in jit by default using self.supports_jit = True
Below are the code references.
https://github.com/keras-team/keras/blob/7ce3d62af7cc6959fc5a5841cfe17043dfcb8615/keras/layers/layer.py#L275
https://github.com/keras-team/keras/blob/7ce3d62af7cc6959fc5a5841cfe17043dfcb8615/keras/layers/layer.py#L275
Please check and close the issue if there is no question. Thanks

As self.supports_jit it is a bool how we control XLA vs torch.compile dynamo VS other compilers?
A layer that could be compiled for one stack doesn't meant that it could be compiled with another backend.


FAQ dark theme answer seems to be wrong

Describe the bug
The answer to the FAQ "Does Ghidra have a dark theme?" says:
Ghidra 10.3+ provides a dark theme out-of-the-box. To enable this theme, from the Front-End GUI, click Edit → Theme → Switch... → Flat Dark Theme.
But there is no "Theme" entry when I click "Edit" on the Front-End GUI:

Environment (please complete the following information):

OS: macOS 14.4 (23E214)
Java Version: Java 8 Update 421
Ghidra Version: 11.1.2
Ghidra Origin: official GitHub distro

Can you please confirm your version of Ghidra by doing Help -> About Ghidra?

Also, that action is controlled by the ThemeManagerPlugin.  From the Front End GUI, click File -> Configure.  Then click Configure under the first Utility group.  You should see a checkbox for the ThemeManagerPlugin in the popup.

Also, that action is controlled by the ThemeManagerPlugin. From the Front End GUI, click File -> Configure. Then click Configure under the first Utility group. You should see a checkbox for the ThemeManagerPlugin in the popup.

Ah OK this fixes it. I think some of the plugins etc sometimes go missing when I get certain kinds of errors quitting Ghidra while working on my Java Loader extensions under Eclipse, and I don't always notice all of the things that break when it happens.

I've seen the plugins in the CodeBrowser tool get messed up, but I don't think i've ever seen them get messed up in the Front End.

I've seen the plugins in the CodeBrowser tool get messed up, but I don't think i've ever seen them get messed up in the Front End.

Yes I have to fix the CodeBrowser every now and then. I got help with that here. I also lost all my hotkeys/shortcuts inside the CodeBrowser once. Usually I don't use most of the other features so don't notice other things going awry. I've never attempted to change themes until now.


Interconnection

This pull request adds:

cmod_grid.cpp, a model to take incoming total site generation and enforcing a grid interconnection limit.
Tests for the interconnection model

@nickdiorio Looks good to me. I see that you've implemented this grid compute module and the fuel cell one a little bit differently than we historically have (header file with constructor), maybe you can walk me through that decision at some point.

@janinefreeman , the reason for implemented the compute modules this way is primarily:

To encapsulate IO management within another structure accessible by the compute module.  Similar to the IO manager, this should make the main compute module code more readable and shorter.

Thanks for the review!


 Fix locally by clearing the Client's channel which was initialized with the old creds and left in-memory. In retrospect, this is an obvious problem 😖.
 Backward/forward compatibility checks

[x] Client+Server: this change is compatible with old servers
[x] Client forward compatibility: this change ensures client can accept data intended for later versions of itself

if we inject creds worker side then i think we can remove this code?

we do actually do this already. We swap out the creds and emit a warning.

@thundergolfer does this need to be merged still?


A better way to rotate windows between displays

I'd like to rotate windows between displays to avoid typing for long time with my neck turned left or right. I have three monitors in front of me and I'm concerned about staring the monitors on the sides for too long.
I've started using yabai recently and I was wondering how to improve the following script.
# swap windows in display
alt - g : wins=($(yabai -m query --windows | jq 'map(select(."is-visible"))[].id')) \
  && yabai -m window ${wins[1]} --swap ${wins[2]}

Any advice on how to improve it further?

After some iterations I have found a better way to swap windows between displays. I switched to stack and alway use 4 desktop no matter how many displays I have.
https://github.com/amiorin/dotfiles-v2/blob/main/yabairc
https://github.com/amiorin/happy-yabai

On master (in v7.0.0 when released) the space --swap command can be used for spaces across display boundaries, and it will basically swap all windows.


peft integration

adds command line args to the gpt2 sentiment example so we can  more easily benchmark different models.
Add a new example using lora / peft examples/sentiment/scripts/gpt2-sentiment_peft.py
some minor compatibility changes

Note: that gpt2 models use Conv1D layers instead of Linear, which is currently not supported in 8bit mode. Benchmarks of memory usage and convergence should be undertaken on some other models such as GPT-J
This should resolve issue #145
Fixes #145

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I just pushed a commit that resolves most of these changes.
Remaining questions / todo:

For the upstreaming of properties / methods missing from PretrainedModelBase I added them as follows:
        model.config = model.pretrained_model.config       model.prepare_inputs_for_generation = model.pretrained_model.prepare_inputs_for_generation
Alternatively, I could implement these actual methods?

I agree with making peft a soft-dependency, but I have not implemented this yet.

I agree with tests, but I have not implemented these yet.

I will implement the rest of the changes later in the week.

Thanks @lvwerra for the review!
1- yes we can do it in a follow-up PR regarding docs
2- As the base model is kept untouched during training, you can just share the model-id of the base model and use it - that is also how the models are pushed using peft , we never share the entire model but the adapters only, as you can retrieve the model id of the base model using PeftConfig. Here is a nice example: https://huggingface.co/crumb/FLAN-OPT-6.7b-LoRA


[Logger] Add the log file creation path of the logger instance

[Logger] Add the log file creation path of the logger instance

Add the log file path for application using nntrainer in enviroments other than Android and Tizen (Android and Tizen don't make logger)
The application in nntrainer is created it under build directory but others using nntrainer can not make it and runtime error occurs.
Now, log is created current directory
In the near future, it seems likely that we will be ablie to add an option to specify where to generate log file

Self evaluation:

Build test:   [X]Passed [ ]Failed [ ]Skipped
Run test:     [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: hyunil park<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2043. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @songgot, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2043-202211181002500.020884990692139-b6111e0af49d0093be4b8d18cdc6c0fe420341bf/.

:octocat: cibot: @songgot, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2043-202211181209470.60273504257202-d5d3a3fad9a691b9a7e8944f1b296960351d17d7/.

Use getcwd() instead of std::filesystem::current_path().
/var/www/html/android/android-ndk-r21e/sources/cxx-stl/llvm-libc++/include/filesystem:1458: undefined reference to `std::__ndk1::__fs::filesystem::__current_path(std::__ndk1::error_code*)'


Add inspect to "Object" interface

Add inspect method to Object. Call inspect instead of to_s on child elements from from Hash.to_s and Array.to_s
Reference #698, still need to expose inspect on all classes before closing.

so far so good 👍

I think you can merge this ❤ @st0012
Then I'd like to try this.

@mweitzel thanks for your work ❤ sorry took so long to merge this


Result Collection Service

As a user, I would like to have the results generated by my applications to be routed to the sinks I have configured so my export clients can export them to where I wanted.
Acceptance Criteria

Poll job's status
Download results when a job is completed
Distribute the results to the sinks user has configured

Closing due to redesign


Allow custom deployments?

I don't know if it would be a useful case or easy to implement but, I have deployed codellama using vLLM and I found this extension that allows me to change the model name, openai api base. Is it possible if you can allow custom deployments which does still imitate openai api documentation but have different API base and model names other than the ones that are available in openai?
Moreover, can the format restriction of openAI API Key be removed, right now I changed it from my command line but if this feature is enabled, other people can use their own API Keys which may or may not follow the openai api key format

Hi @aliozts
There have been similar requests before. I will work on the implementation. To help, could you list the exact requirements?
For example

Allow Additional Security Type (None, ApiKey, Custom)
Models (if the model list doesn't exist, then allow manual entry of model name)
....

Hi @arbs-io  is there anything I can help with by the way? I use Python sadly for this one

Hey, this would make it easier to be integrated for Ollama.ai, for example.

Sorry for the slow responses. I've got a lot on at the minute. I'll remove the validation and allow manual model entry (if the api doesn't exist). I think this should cover the local instance if they are compatible with openai APIs

Hi @arbs-io  is there anything I can help with by the way? I use Python if it's useful

Thanks so much for the offer any and all help is greatly appreciated. Unfortunately python and vscode don't mix well as not all users will have the tollchain installed. But please if you wanted to get involved typescript is a he core language I use. Alternatively rust for some of the wasm features. But you've greatly help with ideas and feature requests. Thanks so much!

Thanks for the log.
I've checked everything and can't see any issues with the feature. I've added additional logging if either gitService in vscode can't be found (or is unavailable), and if the git diff hasn't detected any changes. I can't easily check these conditions but can see some clients do have issues when locating the git service/provider.
The log enhancement will be added to the version 1.5.3 release tomorrow. Could you emulate the issue once the new version has been installed

Hi @josetesan, @aliozts
I've added a custom setup. There is still a dependence on openai compatible API., so for Ollama.ai, llama-2 native might not work without a general interrupter.

Hi @arbs-io,  thank you so much for this! I have deployed a Llama-2 model with vllm where we can give EMPTY as the API key. I can create a configuration without any errors and I can see the settings updated properly but when I try to run

I get the respective error. One more question is, is code completion available with this extension?

vllm provides support for the older completion API endpoint. I will add an option for the host to override the API endpoint.
Regarding code completion, I still need to add it. But it wouldn't be difficult. The problem is the "cost" of public services. Sending partial code blocks

Hi @aliozts
I can see people successfully use llama-2 and codellama using the custom setup. I presume the host mechanism is using the newer API standard support from openai. I'm going to close as dropping back to completion is not feasible and is flagged as deprecated.


On Alphabet click , list does not scroll to that section as expected. Scroll Alignment is improper.

I have provided cellHeight, headerHeight too . Still I can see it does not scroll right. Am I missing something or doing wrong?
<AlphabetListView
data={data}
cell={data => {
return this.renderItem(data.item);
}}
cellHeight={50}
sectionListItem={data => {
return (
<View
style={{
alignItems: "center",
alignSelf: "center",
justifyContent: "center"
}}
>

{data.title}

);
}}
sectionHeader={data => {
return this.renderSectionHeader(data);
}}
sectionHeaderHeight={22.5}
updateScrollState={true}
/>

any solution ?

I have submitted a PR which might be a workaround for this issue: #63


Syntax highlighting for inlay hints

We have been doing a language integration primarily targeting VS Code and noticed, that there's no way to have the inlay hints colored. It would be nice, if inlay hints could be treated as regular code and could get the same syntax highlighting as the rest of the text, just maybe be a bit darker/transparent. In their current form, they are a bit harder to read.
I understand that treating inlay hints as code is not universally applicable, so we might need to propose something like a flag to LSP too to signal that the given inlay hint fragment can be treated as part of the code or something, this is partly a feature request and partly trying to start a discussion to see what people think of this.

https://github.com/microsoft/vscode/issues/225400

@RedCMD No, inlay hints are labels within source code that are not actually part of the source code, they merely provide extra info for readability - like parameter names, inferred variable types,  etc. For example: https://code.visualstudio.com/docs/typescript/typescript-editing#_inlay-hints


MFA Reporting

MFA reporting can also be done from the azure portal (this article points to the wrong blade currently)
https://learn.microsoft.com/en-us/azure/active-directory/authentication/howto-authentication-methods-activity#user-registration-details
https://portal.azure.com > active directory > security > authentication methods > user registration details
https://portal.azure.com/#view/Microsoft_AAD_IAM/AuthenticationMethodsMenuBlade/~/UserRegistrationDetails

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

ID: c695a366-7220-081a-8e04-ab84c6f201b7
Version Independent ID: bec85559-f35b-d6ff-4ea9-92a3d411d37f
Content: Sign-in event details for Azure AD Multi-Factor Authentication - Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/authentication/howto-mfa-reporting.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@jonwbstr
Thanks for your feedback! We will investigate and update as appropriate.

@jonwbstr sorry for delay and thanks for raising this. I created an internal work item for SMEs to review and update the topic as needed. #please-close


Confirmation URL Broken

Hello, my confirmation link({{ .ConfirmationURL }}) used to work without any problems it used to redirect to my app. But out of nowhere it started sending the link to a url1556.....com and when I click on the confirmation button on the email, ex. signup confirmation it just says page can not be found and it doesn't redirect. Is there a way to change the url for the {{ .ConfirmationURL }} in the Email Templates? I couldn't figure out where it gets that url from.
Thank you.

hi @mreky, can you please create a support ticket through https://app.supabase.com/support/new so we can take a look at the issue with your project?

@kangmingtay Done, thank you!

This issue has been resolved, we found out that using SendGrid as a custom SMTP provider in Supabase resulted in the email links sent being overwritten when link tracking is enabled (https://docs.sendgrid.com/ui/account-and-settings/tracking). To ensure that the email links sent by gotrue works, you need to disable link tracking on your Sendgrid account.


running jest  doesn't update code cov when running yarn test:coverage

this would be nice for my workflow 😄
running yarn test:unit updates the code cov at http://<IP_ADDRESS>:8080 but jest FileName doesn't.
using the refactor label because its the closest thing to a developer label.

jest fileX only updates the coverage for fileX and imports for that file. The website for the coverage is newly written every time. The problem: the navigation changes. You may nee to go back to http://<IP_ADDRESS>:8080 and navigate to your file from there. Can you try again?

ping @jbibla

we can close for now.


Google Map Embed displays max Zoom level

Bug Description
Related to  #256
The map no longer errors when using the embed link but it is max zoomed in so all I see is green (map background color)
Steps to reproduce

From Google Map click share, copy link to share
Paste url into Embedded Assets
Display iframeCode or html output

Expected behaviour
Expected same zoom level as when using the browser bar url, I think the default is around 8 or 9?
Embedded Assets version
5.2.0
Craft CMS version
5.4.9

Your map URL from https://github.com/spicywebau/craft-embedded-assets/issues/256#issuecomment-2239746570 is saving the embedded asset at zoom level 12.5 for me - what level (if any) is it saving in the JSON file for you?

Thanks for that - I think we might be mishandling share links for specific places. We'll look into it and I'll update here when we have more.


Multipart upload fails for large files

Tested with 5GB and 8GB files.
Works fine for a 2GB file.

I realized what the problem is. When the file is too large, it gets stuck on creating the arrayBuffer and fileHash.

Interesting @sorin89 - computation of file hash would happen locally so I wouldn't expect that being a problem but good to know. I believe we should make it optional.

I tried using the solution in Nextjs 14, however I'm hvaing 405  error.

hi @sorin89 have you tried with removing the hashing function? Please let us know if it helped.
also @steveoni would you mind commenting with your latest tests - I know that you've been playing with the multi-part upload recently 😄. We'd be interested in what's the largest size you tried to upload, what is the issues (if any) and did you remove the hashing function?

hi @sorin89 have you tried with removing the hashing function? Please let us know if it helped.
also @steveoni would you mind commenting with your latest tests - I know that you've been playing with the multi-part upload recently 😄. We'd be interested in what's the largest size you tried to upload, what is the issues (if any) and did you remove the hashing function?

It’s true that for large file , generating the hash string breaks the app. So I tried with a fixed hash string and was able to upload a 10gb file.
So the solution will be to find other alternatives to generate hash string

@steveoni I would say we don't need to generate file hash at all by default. Hashing is useful if you would like to have:

Versioning so that md5 hash can be used as a signature of the file content.
Save storage, i.e., the same file content wouldn't be stored multiple times.

I think the main purpose of this library is to provide a basic app to be able to upload files from local disk to a bucket.
Could you please open a pull request removing hashing function? We can use file name as a prefix in the bucket.

FIXED in #12


[!!] Refactor

What's been done?

Chopped the code down to functions
Organized files in folders :stuck_out_tongue:
Replaced all calls to Array.prototype.slice.call to Array.from for readability
Add browser action (show popup)
Bump firebase to v4.5.0
A lot of callback hell

Related Issues
Closes #11
Tested on
Ubuntu 15.10 - Chrome 60
Windows 10   - Chrome 62
@jovit, @carlosamds please review
There a lot of changes in the PR and since I started working on this some time ago there might be some kind of code regression

Thanks @carlosamds!
Just applied the fix, should be working now

The code is waay more reasonable now, this should make future changes a lot easier.
I'll run some tests to be on the safe side but everything looks fine

Awesome, collection working perfectly!
Just bump the version for the upload and note that the name on the manifest is the name that goes on the store.

fixes https://github.com/jovit/fy-moodle/issues/11


show "inflated brain" for connectivity map (from jeff)

Ping jeff to clarify

from jeff:
Hello Xiaoyun,
I do not remember the context in which I provided this suggestion, or what you call exactly a connectivity map, but the point is
rather simple, and hold for any information projected on the cortical surface, including the Julich Brain.
Because of folding, it is not possible to visualize the complete cortical surface (of course here I mean one side of the cortical surface).
Since 2/3 of the cortex is in the folds, some information is hidden, even when you deal with the white matter surface, where the folds are opened.
Therefore, the trick used in freesurfer is to inflate the mesh, to unfold the cortical surface, at least partially, so that you have less or no hidden areas.
Some people like David Van Essen push even further. They cut the cortical surface so that after the inflation they can also map it on a 2D plane. This is something often done my the team ov Win VanduFell for Macaques.
I attach so images to illustrate the process.
Practically, for the EbrainsViewers, it is not that difficult to deal with these 2 representations, because they can rely on exactly the same mesh, but the vertices have different coordinates.
best
Jeff

Judging from his response, I wonder if this has already been achieved, since (with the assistance from Jeff, Denis & Yann), Julich brain has been projected to fsaverage space and displayed in the viewer (with assistance form Casey).

fixed
from fsaverage -> inflated projection -> show connectivity

fixed
from fsaverage -> inflated projection -> show connectivity


Fixes #3722 REPL indent is not calculated correctly

Uses correct text buffer comparison to determine when to map the result.

Don't merge yet - the git merge I was forced into still reverted some of the changes.

As discussed, this fix is working unreliably for me. Sometimes it will indent, sometimes not. Let's take this into master instead.


Make SyntaxBuildableType hashable

This is a small change that implements __hash__ for SyntaxBuildableType on the Python-side, thereby making it possible to use SyntaxBuildableType in sets and dictionaries as keys.
Since the type already implements a fieldwise __eq__, having a corresponding __hash__ feels like a natural extension.

Note that the Swift version of this type (in SwiftSyntaxBuilderGeneration) is also Hashable.

@swift-ci please test


Just fixing the sample code in the readme

Really silly, minor updates.

Thanks for that!

Ah, thanks a bunch @Nelson69, wrote those off the top of my head — should've tested them! :star2:


Rewrite the tree transformations

The current proof of concept has all the necessary tree transformations but they are not done in a logical and nice way. A rewrite of the tree transformations is in order.

Both @mvo5 and @achilleas-k have poc concepts for a new tree transform implementation that simplifies things. Assigning there.

Done.


Extract strings in preparation for localization

Currently the app uses hard-coded strings.  We're prepping to localize everything into some other languages.  The first step is to extract the strings in the app into strings files so we can hand these off to translators.

What do you think about using something like R.swift for the localization strings?

Not familiar with it, looking now.
Sent from my iPhone

On Feb 5, 2017, at 6:16 PM, Alex Robinson<EMAIL_ADDRESS>wrote:
What do you think about using something like R.swift for the localization strings?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Tracking this in #61


Response time of first query

Dear team,
We are running ArangoDB 3.1rc2 in redhat 6.6 machine. and having a huge database with millions of entries on multiple collections.
So when we run some complex queries, it is taking 10 to 20 seconds, sometimes more than a minute only for the first time. Next time onwards, it is very fast and takes only few milli seconds.
Is there a way to make the first query faster by preloading the indexes and data into main memory.
Regards,
Sajeev

Yes, the loading time of collections affects query response time.
There is already a feature request for this in #1821. I am closing this issue as a duplicate of it.


Dependencies conflict

Package conflict
We are using V4.0.0 of this package and also using the https://github.com/symfony /
mercure-bundle
auth0/jwt-auth-bundle uses V7 of auth0/auth0-php, which uses a fork of lcobucci/jwt package, with same namespace but added breaking changes.
mercure bundle use the original lcobucci/jwt package
see this issue
Resolution
There is a simple way to resolve the problem, since auth0/jwt-auth-bundle *V8 address that exact problem. By upgrading your dependencies on auth0/jwt-auth-bundle to V8 you will solve it.

Hi @francis-roux-serret 👋 Thanks for your report. This is a known issue. The fork of the JWT library was necessary for PHP 8 support, as the upstream author did not want to backport changes necessary to support PHP 8 on the 3.x branch. The fork did not include breaking changes, but was incompatible with other libraries with the same dependency.
We will be upgrading this library to use the underlying Auth0-PHP 8 library to resolve this, but I don't have a firm timeline on that to provide you right now.

+1. Also have the same issue here 👋

👋 I've pinned this issue for public reference. I'll be closing the ticket for now, as our policy is not to leave tickets open that are not actionable in the short term based on our bandwidth/schedule. However, I assure you this work has been backlogged and is on our radar, our closure of the ticket is not indicative of us dismissing its necessity. We'll update this thread and re-open the ticket when we come back to this work.

Package conflict
We are using V4.0.0 of this package and also using the https://github.com/symfony / mercure-bundle
auth0/jwt-auth-bundle uses V7 of auth0/auth0-php, which uses a fork of lcobucci/jwt package, with same namespace but added breaking changes. mercure bundle use the original lcobucci/jwt package
see this issue
Resolution
There is a simple way to resolve the problem, since auth0/jwt-auth-bundle *V8 address that exact problem. By upgrading your dependencies on auth0/jwt-auth-bundle to V8 you will solve it.

It doesn't work for me, because JWTAuthBundle class calls Auth0\SDK\API\Helpers\ApiClient in its constructor. But this class was removed in auth0/auth0-php v8.0.0. It was there in v7.9.2 though.


GEO_CONTAINS behaves differently with less precision

My Environment

ArangoDB Version:        3.10.0
Deployment Mode:       Single Server
Deployment Strategy:   Docker
Configuration:
Infrastructure:              On-premise
Operating System:       MacOS 13.0
Total RAM in your machine:      64GB (MacBook Pro 16" Apple M1 Max)
Disks in use:        SSD
Used Package:    Docker

Component, Query & Data
Affected feature:

GEO_CONTAINS AQL function
AQL query (if applicable):
WITH events
FOR e IN events
    FILTER GEO_CONTAINS( {
        "type": "Polygon",
        "coordinates": [
          [
            [
              24.743952,
              59.436789
            ],
            [
              24.743952,
              59.441999
            ],
            [
              24.754449,
              59.441999
            ],
            [
              24.754449,
              59.436789
            ],
            [
              24.743952,
              59.436789
            ]
          ]
        ]
      }, e.location)
    RETURN e.location

AQL explain and/or profile (if applicable):

Dataset:
events collection with the following data:
{
  "title": "test event with location",
  "location": {
    "type": "Point",
    "coordinates": [
      24.750137329101562,
      59.43931579589844
    ],
    "properties": {
      "zoom": 11
    }
  },
}

Steps to reproduce
Query the event with the following precision:
WITH events
FOR e IN events
    FILTER GEO_CONTAINS( {
        "type": "Polygon",
        "coordinates": [
          [
            [
              24.74389969390228,
              59.441914343792746
            ],
            [
              24.74389969390228,
              59.43699338551801
            ],
            [
              24.754407217831385,
              59.43699338551801
            ],
            [
              24.754407217831385,
              59.441914343792746
            ],
            [
              24.74389969390228,
              59.441914343792746
            ]
          ]
        ]
      }, e.location)
    RETURN e.location

The event is found, now let's query with less precision even though the polygon is almost identical:
WITH events
FOR e IN events
    FILTER GEO_CONTAINS( {
        "type": "Polygon",
        "coordinates": [
          [
            [
              24.743952,
              59.436789
            ],
            [
              24.743952,
              59.441999
            ],
            [
              24.754449,
              59.441999
            ],
            [
              24.754449,
              59.436789
            ],
            [
              24.743952,
              59.436789
            ]
          ]
        ]
      }, e.location)
    RETURN e.location

The event is not found.
Problem:
GEO_CONTAINS behaves differently with less precision even though Polygons are the same.
Expected result:
GEO_CONTAINS must behave the same regardless of lesser precision.
--

Here are the polygon boxes used in queries.
https://geojson.io/#map=14.72/59.43777/24.74688
{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {},
      "geometry": {
        "coordinates": [
          [
            [
              24.74389969390228,
              59.441914343792746
            ],
            [
              24.74389969390228,
              59.43699338551801
            ],
            [
              24.754407217831385,
              59.43699338551801
            ],
            [
              24.754407217831385,
              59.441914343792746
            ],
            [
              24.74389969390228,
              59.441914343792746
            ]
          ]
        ],
        "type": "Polygon"
      }
    },
    {
      "type": "Feature",
      "properties": {},
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              24.743952,
              59.436789
            ],
            [
              24.743952,
              59.441999
            ],
            [
              24.754449,
              59.441999
            ],
            [
              24.754449,
              59.436789
            ],
            [
              24.743952,
              59.436789
            ]
          ]
        ]
      }
    }
  ]
}

It doesn’t seem like the issue is necessarily due to using less precision in the polygon.  Taking digits off the original coordinates still works.  I was able to reproduce the issue with the second polygon.  This is a big concern for me too.

The interpretation of polygons changed regarding the winding but lines are also geodesic now, which can change results.
See https://www.arangodb.com/docs/stable/indexing-geo.html#geojson-interpretation for details.
Starting from v3.10.10, the web interface correctly displays polygons with geodesic lines. However, it only displays the polygon lines and doesn't fill the area the polygon covers currently, so you cannot see what is interior and exterior.


Added a new concat argument.

This can be using for who showing lists, broadcasting config values ect. You could put a space (" "), you could put a comma with a space (", ") and lots more.
This was done in GitHub so sorry for any errors that may occur.

Trimming?

Ah yes, I will sort this.


Any reason my .buttons::before are sticking to the left of container?

Hi,
Trying to recreate a dropdown menu with bass, but somehow hovers on buttons are always sticking to the left of the parent. Is there anything specific I am missing?

I can't figure out how in your example .button-transparent::before stays in place when it says:
.button-transparent:before {
    top: -1px;
    left: -1px;
}

If I change it to top: 0; left: 0 – everything seems right here.

Found it. Problem was in neat
*, *::after, *::before {
   box-sizing: inherit;
}

Actually why not switch to border-box?

I think you have uncovered a small bug in the basscss-button-transparent module.
Regarding border-box, docs are coming, but see #80 for a brief explanation.


Arrange paper's in year-wise order

All paper's need to be arranged year-wise beside's adding sub-catergories

hey i'm working on this

Cool

Fork it and work on it!

check out my PR

Closed by #12


CDN download returns 404

(node:60848) [steam-user] Warning: No branch name was specified for app 730, depot 731. Assuming "public".
(Use `node --trace-warnings ...` to show where the warning was created)

node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^
OperationalError: HTTP error 404
    at ClientRequest.<anonymous> (/Users/-/melo/-/stickers/node_modules/steam-user/components/cdn.js:585:13)
    ... 9 lines matching cause stack trace ...
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
  cause: Error: HTTP error 404
      at ClientRequest.<anonymous> (/Users/-/melo/-/stickers/node_modules/steam-user/components/cdn.js:585:13)
      at Object.onceWrapper (node:events:628:26)
      at ClientRequest.emit (node:events:513:28)
      at HTTPParser.parserOnIncomingClient (node:_http_client:701:27)
      at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
      at Socket.socketOnData (node:_http_client:542:22)
      at Socket.emit (node:events:513:28)
      at addChunk (node:internal/streams/readable:324:12)
      at readableAddChunk (node:internal/streams/readable:297:9)
      at Readable.push (node:internal/streams/readable:234:10)
      at TCP.onStreamRead (node:internal/stream_base_commons:190:23),
  isOperational: true
}

I think it's related to steam-user package.

Fixed in pull request #48

thanks @wavpro

Also make sure the steam-user is on its latest version it will still throw 404 errors otherwise

Make sure the steam-user is on its latest version it will still throw 404 errors otherwise
@wavpro Would you mind adding a new commit to adding the .gid to the debug log so there is no object object in the message

Fixed! I've also already fixed it in my fork, cs2-cdn.


可以更新vcpkg版本不

Search before asking

[ ] I searched the issues and found no similar issues.

What happened + What you expected to happen
Reproduction way
Anything else
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

可以的，希望社区的同学帮助升级vcpkg版本，参考之前的PR。

已经更新最新了


Guide to Enhanced settings are missing

I came to this page from D365 after clicking the Collaborate button > Lear More. But the details are missing...
below is the pop up showed*******
Connect with Microsoft Teams to easily collaborate, chat and share files with your Dynamics 365 teammates.
Clicking Get started opens Microsoft Teams. To collaborate right in Dynamics 365, ask your tenant admin to enable the Enhanced experience in system settings. Learn more

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

ID: 6cc7ef0b-2e46-0b81-3182-edc6cc31bc88
Version Independent ID: 1f8b2b10-a844-f001-12d8-91f9171c72b8
Content: Integrate Dynamics 365 for Customer Engagement appswith Microsoft Teams
Content Source: ce/basics/teams-integration.md
Service: crm-online
GitHub Login: @mduelae
Microsoft Alias: mkaur

@sing-ideas thank you for your feedback. @CindyLiu-D365, can help?

@sing-ideas, looks like your Dynamics 365 environment is enabled for Oct 2019 release preview. We are working on the detail description page for basic experience vs enhanced experience. Will publish it when the release wave is open to public.

@sing-ideas  I am close the loop on this question. Feel free to reply back if you have further questions.
Thanks,
Mints


KAFKA-5241: GlobalKTable does not checkpoint offsets after restoring state

Ensure checkpointable offsets for GlobalKTables are always written on close.

@twbecker thanks for the PR. Can you please add a test that fails without this change?

Added the test, @dguy. While you're looking at this would you mind looking at the comment I put in the JIRA? It seems wrong to me that the existing DB is reused when there is no checkpoint; should it not be deleted first in that case?

@twbecker this is the case for all state stores. But, yes they probably should be deleted. I'd raise it as a separate JIRA.
Looks like you need to rebase

@guozhangwang I think we should backport to 0.10.2 as well

LGTM. Merged to trunk and cherry-picked to 0.10.2.

My store is in-memory store and I think this is causing empty stores in case a restart on same machine. I am new to Kafka land and wanted to be sure before file an issue. Is this expected behaviour for in memory stores behing GlobalKTable @twbecker @guozhangwang ?

Hello @cemo , I saw you've filed KAFKA-6711 for this specific issue.


Deprecate internal properties

Currently we expose properties for backgroundColor, backgroundView, stackView, axis seperatorViewFactory and scrollView. Ideally a user won't be able to modify the state of stackView, seperatorViewFactory and scrollView without going through StackViewController directly.
Being able to modify properties of the stack view directly makes it possible for a user to reconfigure it in such a way that it isn't compatible with the current configuration of the StackViewController anymore. Similarly being able to change the axis after initialization complicates the implementation of StackViewController because it always needs to account for the fact the the axis might change.
axis, separatorViewFactory and backgroundView should be injected in the initializer and not changed after StackViewConroller is initialized.
stackView scrollView properties that we want the user to modify should be exposed directly on the StackViewController. For example if we want the user to be able to scroll we could expose scroll(toViewController:) or scroll(toRect:) on StackViewController directly.
We can keep backgroundColor, but I think it should be implemented as a convenience for backgroundView.backgroundColor = .

I saw that these were deprecated in a few commits such as this one, but it is causing a lot of warnings to crop up when using StackViewController as a dependency.
Here is one example below:

Those warnings should go away because the deprecated properties will be made (file)private. Afaik there is no way to tell Xcode to only mark properties deprecated to the outside so unfortunately you'll get warnings if you build the project as part of your app's build process (CocoaPods does this).


fixed code style for php_grpc.c

Hi @feilengcui, thanks for this contribution.  Can you make sure you have accepted the Contributor License Agreement please ?

yeah,I've signed the Contributor License Agreement with the email<EMAIL_ADDRESS>account,its different from my commit email,does that matter?

Thank you for your contribution.
However, I am hesitant to merge this. All of the C and C++ code in the repository is formatted with clang-format-3.5, and I'm not sure I want to change the code to conflict with that formatting.

ok,I just thought it's weird for a php extension^_^


[UNDERTOW-1485] fix some wrong letter

Issues: https://issues.redhat.com/browse/UNDERTOW-1485
Upstream PR: https://github.com/undertow-io/undertow/pull/1142

I'm closing this one because it changes method signatures in UndertowServletMessages, it will just go to master, but not to 2.0.x.


toArray Escapes unnecssarily

Closing this because of old age. If the issue persists, discuss it here and/or open a Pull Request please.


SPFX WebPart shows error in IE when deployed on a Site as WebPart

[X] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

When I test the WebPart within the workbench with IE11, everything works as it should. But when I deploy the WebPart on a Page, then it shows the following error:
Something went wrong
If the problem persists, contact the site administrator and give them the information in Technical Details.
Technical Details
[SPLoaderError.loadComponentError]:
***Failed to load component "..." (...).
Original error: ***Failed to load entry point from component "..." (...).
Original error: Error loading https://component-id.invalid/...
Object doesn't support property or method 'startsWith'
***INNERERROR:
***Failed to load entry point from component "..." (...).
Original error: Error loading https://component-id.invalid/...
Object doesn't support property or method 'startsWith'
The WebPart runs in the Workbench since I added the required polyfills. But on the Sharepoint Page the polyfills seem to be ignored. In Chrome everything works everywhere as expected. So I guess it must be a polyfill problem.
Does anyone had the same problem?
I use SPFX with React and within one component I use the react-wysiwyg Rich Text Editor. (I guess the RTE- component is the culprit since when I added it, the errors shows up)
Any suggestions and help is very appreciated
Thank you

Update:
The error with startsWith only occurs when the page is in Read Mode.
If I change to Edit Mode, the WebPart loads without any problems.
But when I save the changes and refresh the page, then the error shows up again.
SharePoint mystery...

Hi @Crash753 , are you bundling react-wysiwyg RTE with the web part code or are you externalizing it ?

Dang it... wrong button^^

@Crash753 , which polyfills did you add to the page? Also, are the polyfills also bundled, or are they externalized?

You need to add the starts-with polyfill from for instance coreJS.
Run npm i core-js, then in the webpart code import the starts-with polyfill corejs/fn/string/starts-with

@nickpape-msft I tried to bundle the polyfills but that does not work really well.
But I can't belief that the solution was that simple...
My own polyfills alone do not work but when I imported the polyfill 'startsWith' from coreJS as @colindekker recommended it works. But only in comination with my own polyfills.
Import all polyfills from coreJS does not work either.
Bottom line is...it works now...
Thank you all

@Crash753  Can u pls share the Import order.

@Crash753 or @colindekker I am running into a similar issue. What is the import order you used?


[FEAT]: Add option to test all user-defined attributes to "Create Testing Keys"

Testing keyframes would go through every user-defined attribute setting calling them in isolation. Useful for when testing their connections.
Options:
-Min/Max values

Will track using GitHub projects


fix: refine error resean with invalid pipelinename in taskrunspecs

Changes
This PR tries to modify the scene where the pipelineRun containing an invalid pipeline name in taskRunSpecs displays an error mismatch.
fix:  #6956
/kind bug
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
When the taskRunSpecs of the pipelineRun contains an invalid pipeline task name, the cause of the `InvalidTaskRunSpecs` error is displayed.

/ok-to-test

/cc @vdemeester


Failed to update on windows 10

<EMAIL_ADDRESS>install C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport

node-pre-gyp install --fallback-to-build

Failed to execute 'C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\bin\node.exe C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\bin\..\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport\build\Release\serialport.node --module_name=serialport --module_path=C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport\build\Release --msvs_version=2015' (1)
C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh
`-- (empty)
node-pre-gyp ERR! Tried to download(404): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-electron-v1.3-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(electron-v1.3 ABI) (falling back to source compile with node-gyp)
gyp ERR! configure error
gyp ERR! stack Error: Python executable "C:\Program Files\Python35\python.EXE" is v3.5.3, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack     at failPythonVersion (C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\node_modules\node-gyp\lib\configure.js:454:14)
gyp ERR! stack     at C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\node_modules\node-gyp\lib\configure.js:443:9
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:204:7)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at maybeClose (internal/child_process.js:827:16)
gyp ERR! stack     at Socket. (internal/child_process.js:319:11)
gyp ERR! stack     at emitOne (events.js:77:13)
gyp ERR! stack     at Socket.emit (events.js:169:7)
gyp ERR! stack     at Pipe._onclose (net.js:477:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\bin\node.exe" "C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\node_modules\node-gyp\bin\node-gyp.js" "configure" "--fallback-to-build" "--module=C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport\build\Release\serialport.node" "--module_name=serialport" "--module_path=C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport\build\Release" "--msvs_version=2015"
gyp ERR! cwd C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport
gyp ERR! node -v v4.4.5
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\bin\node.exe C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\bin\..\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport\build\Release\serialport.node --module_name=serialport --module_path=C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport\build\Release --msvs_version=2015' (1)
node-pre-gyp ERR! stack     at ChildProcess. (C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:827:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
node-pre-gyp ERR! System Windows_NT 10.0.14393
node-pre-gyp ERR! command "C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\bin\node.exe" "C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport\node_modules\node-pre-gyp\bin\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\node_modules\microbit-micropython\node_modules\serialport
node-pre-gyp ERR! node -v v4.4.5
node-pre-gyp ERR! node-pre-gyp -v v0.6.32
node-pre-gyp ERR! not ok
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\package.json'
npm WARN apm-install-dir-117229-11796-1ybr1nh No description
npm WARN apm-install-dir-117229-11796-1ybr1nh No repository field.
npm WARN apm-install-dir-117229-11796-1ybr1nh No README data
npm WARN apm-install-dir-117229-11796-1ybr1nh No license field.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\bin\node.exe" "C:\Users\jholt\AppData\Local\atom\app-1.15.0\resources\app\apm\node_modules\npm\bin\npm-cli.js" "--globalconfig" "C:\Users\jholt\.atom\.apm\.apmrc" "--userconfig" "C:\Users\jholt\.atom\.apmrc" "install" "C:\Users\jholt\AppData\Local\Temp\d-117229-11796-r1xmtv\package.tgz" "--runtime=electron" "--target=1.3.13" "--arch=x64" "--global-style" "--msvs_version=2015"
npm ERR! node v4.4.5
npm ERR! npm  v3.10.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs serialport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\jholt\AppData\Local\Temp\apm-install-dir-117229-11796-1ybr1nh\npm-debug.log
npm ERR! code 1

Hi,
looks like the serialport npm package (which is now installed as a dependency) bugs out. However, the serialport package states it has Windows 10 support. I need to try on Win 10 but might take a little time (not using Win on my machines).
Other question: the version before worked for you on Win 10? Also the REPL worked?
Regards,
Stefan

Oh, and one other ting. Even if the updated would have worked, I think REPL and execution with the current version will not work on Windows. However, it would be good to support Windows too but ... well ... :-)

Hi Stefan,
Thanks for the fast response. I have the previous version working but had
the problems when trying to upgrade.
Haven't tried the REPL so I'll give it a go and let you know.
Thanks
John
On Wed, 29 Mar 2017, 10:22 Stefan Wendler<EMAIL_ADDRESS>wrote:

Hi,
looks like the serialport npm package (which is now installed as a
dependency) bugs out. However, the serialport package states it has Windows
10 support. I need to try on Win 10 but might take a little time (not using
Win on my machines).
Other question: the version before worked for you on Win 10? Also the REPL
worked?
Regards,
Stefan
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wendlers/atom-microbit-micropython/issues/1#issuecomment-290033396,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACY9CB3Xpfi6Gzy84zuboQ0DKfqbCvjeks5rqiLLgaJpZM4MsrPV
.

Hi John,
I will try to check on this maybe on the weekend. Would be great if you could provide me the feedback on the REPL with Windows 10.
Stefan

Hi John,
I tired with Windows 10, and I get the same ERROR. It is caused by the "serialport" npm package. I also get the same error if I try to indipendently install "serialport" with npm. Actually I have no glue why this is caused (since the "serialport" package should support Windows). Currently I am thinking about to make that package an optional dependency to at least allow updates / installs on Windows too.
Regards,
Stefan

Hi Stefan,
Thanks for the update. I can't help test the REPL for you at the moment as
I uninstall the previous package and I can't install the new one.
Thanks
John
On Sat, 1 Apr 2017, 21:19 Stefan Wendler<EMAIL_ADDRESS>wrote:

Hi John,
I tired with Windows 10, and I get the same ERROR. It is caused by the
"serialport" npm package. I also get the same error if I try to
indipendently install "serialport" with npm. Actually I have no glue why
this is caused (since the "serialport" package should support Windows).
Currently I am thinking about to make that package an optional dependency
to at least allow updates / installs on Windows too.
Regards,
Stefan
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wendlers/atom-microbit-micropython/issues/1#issuecomment-290944686,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACY9CIYmTIf5kBw-z4HqfJ6-WMqdQBq6ks5rrrFcgaJpZM4MsrPV
.

I have the same issue in linux mint 18


Update rich_rule.rb

remove 1/m limit value default

:+1: I ran up against this today.

I just hit this today as well. Could this patch be merged?
Replacing my current rule with one that has a very high limit leaves the old rule in place as well.
    rule family="ipv4" source address="<IP_ADDRESS>/32" accept limit value="999/s"
    rule family="ipv4" source address="<IP_ADDRESS>/32" accept limit value="1/m"

Could this PR get integrated into master and the version bumped please?
I ran up against this the other day, having to specifically :remove rules with limit_value '1/m' to clean up, and add limit_value '1000/s' to stop firewalld from rate limiting connections.
Thanks!

Thanks!


FEATURE Don't hard code Discounts to silverstripe-products Product class

Is your feature request related to a problem? Please describe.
Currently, on Discount, we are hard coding many_many Products => Dynamic\Products\Page\Product. This limits the usefulness of the module by limiting discounts to that class or it's descendants.
Describe the solution you'd like
Ideally, the module could be reworked to allow discounts on any of the $product_classes spec'd via the FoxyHelper config. A DataExtension would need to be applied to the Discount class specing the many_many relation to each product class.
Additional context
Currently Discount is a DataObject, which makes it easy to add existing products to a discount. However, if there are multiple product classes, this relationship gets more complex and may require GridField_RelationEditor fields for each product class so they can be managed separately.
With this in mind, the existing Products gridfield in Discount would likely need to be moved to the DataExtension described above.

closed via #12


Bicep isn't working when loading up the extension i get this error below in visual studio

Does this occur consistently?
Repro steps:

Action: bicep.activate
Error type: string
Error Message: Launching server using runtime C:\Program Files\dotnet failed. Error: spawn C:\Program Files\dotnet ENOENT
Version: 0.29.47
OS: win32
OS Release: 10.0.19044
Product: Visual Studio Code
Product Version: 1.93.0
Language: en

it has never worked for me

Do you have the dotnetAcquisitionExtension.existingDotnetPath setting configured in VSCode? If so, could you try removing it and relaunching the extension? See here for info on settings.

i have removed it and i am getting this error now An error occurred while installing .NET (8.0): .NET Acquisition Failed: .NET install timed out.
You should change the timeout if you have a slow connection. See: https://github.com/dotnet/vscode-dotnet-runtime/blob/main/Documentation/troubleshooting-runtime.md#install-script-timeouts.
Our CDN may be blocked in China or experience significant slowdown, in which case you should install .NET manually., MESSAGE: Command failed: powershell.exe -NoProfile -NonInteractive -NoLogo -ExecutionPolicy unrestricted -Command "& { [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12; & 'c:\Users\user.vscode\extensions\ms-dotnettools.vscode-dotnet-runtime-2.1.5\dist\install scripts\dotnet-install.ps1' -InstallDir 'c:\Users\user\AppData\Roaming\Code\User\globalStorage\ms-dotnettools.vscode-dotnet-runtime.dotnet\8.0.8~x64' -Version 8.0.8 -Verbose -Runtime dotnet -Architecture x64 }"
dotnet-install: Downloading from "primary" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "primary" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
dotnet-install: Downloading from "primary" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "primary" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
dotnet-install: Downloading from "primary" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "primary" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
dotnet-install: Downloading from "primary" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "primary" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Could not find ".NET Core Runtime" with version = 8.0.8
Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET support
At C:\Users\ChrisHo.vscode\extensions\ms-dotnettools.vscode-dotnet-runtime-2.1.5\dist\install
scripts\dotnet-install.ps1:1330 char:5

throw "Could not find `"$assetName`" with version = $($DownloadLi ...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (Could not find ...on .NET support:String) [], RuntimeException
FullyQualifiedErrorId : Could not find ".NET Core Runtime" with version = 8.0.8
Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET support

, CODE: 1, SIGNAL: null, Error: .NET install timed out.
You should change the timeout if you have a slow connection. See: https://github.com/dotnet/vscode-dotnet-runtime/blob/main/Documentation/troubleshooting-runtime.md#install-script-timeouts.
Our CDN may be blocked in China or experience significant slowdown, in which case you should install .NET manually., MESSAGE: Command failed: powershell.exe -NoProfile -NonInteractive -NoLogo -ExecutionPolicy unrestricted -Command "& { [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12; & 'c:\Users\user.vscode\extensions\ms-dotnettools.vscode-dotnet-runtime-2.1.5\dist\install scripts\dotnet-install.ps1' -InstallDir 'c:\Users\user\AppData\Roaming\Code\User\globalStorage\ms-dotnettools.vscode-dotnet-runtime.dotnet\8.0.8~x64' -Version 8.0.8 -Verbose -Runtime dotnet -Architecture x64 }"
dotnet-install: Downloading from "primary" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "primary" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
dotnet-install: Downloading from "primary" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "primary" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
dotnet-install: Downloading from "primary" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "primary" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
dotnet-install: Downloading from "primary" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "primary" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-runtime-8.0.8-win-x64.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Downloading from "legacy" link has failed with error:
Uri: https://dotnetbuilds.azureedge.net/public/Runtime/8.0.8/dotnet-win-x<IP_ADDRESS>.zip
StatusCode:
Error: An error occurred while sending the request.
Unable to connect to the remote server
An attempt was made to access a socket in a way forbidden by its access permissions <IP_ADDRESS>:443
Could not find ".NET Core Runtime" with version = 8.0.8
Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET support
At C:\Users\user.vscode\extensions\ms-dotnettools.vscode-dotnet-runtime-2.1.5\dist\install
scripts\dotnet-install.ps1:1330 char:5

throw "Could not find `"$assetName`" with version = $($DownloadLi ...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (Could not find ...on .NET support:String) [], RuntimeException
FullyQualifiedErrorId : Could not find ".NET Core Runtime" with version = 8.0.8
Refer to: https://aka.ms/dotnet-os-lifecycle for information on .NET support

, CODE: 1, SIGNAL: null
at f.next (c:\Users\user.vscode\extensions\vscode-dotnet-runtime-library\dist\Acquisition\AcquisitionInvoker.js:70:50)
at Generator.next ()
at s (c:\Users\user.vscode\extensions\vscode-dotnet-runtime-library\dist\Acquisition\AcquisitionInvoker.js:5:58)

@chrishocoop The errors you're seeing are coming from the vscode-dotnet-runtime extension while it's attempting to download the .NET runtime, which is required by the Bicep extension. It seems like this could be related to your specific internet environment. Have you tried the workaround mentioned in the error message?
Our CDN may be blocked in China or experience significant slowdown, in which case you should install .NET manually

You can find instructions for manually installing .NET here: https://github.com/dotnet/vscode-dotnet-runtime/blob/main/Documentation/troubleshooting-runtime.md#manually-installing-net.


Reduce ExternalArtifact capabilities to value only

Describe changes
I reduced the function an ExternalArtifact can perform to only value inputs. Rest is covered by Client() or Model methods going forward.
Docs: https://app.gitbook.com/o/-MCl1Hlw9oU4xibZ-ymf/s/9oLgDi1mkUbwQiTmrEit/getting-started/introduction
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[ ] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

Please make sure the docs are updated accordingly :-)

Yeah, sure, it is WIP still, as mentioned in the description. I will ensure all cases are working fine and clean-up the docs in parallel.

/fulltest

/fulltest

Closed in favor of https://github.com/zenml-io/zenml/pull/2375


Require stack to be 'static

Fixes #43

Unfortunately changes to the coroutine_call benchmark slowed it down by around +108% of cycles and +69% of time. Should I add with_stack_unchecked and use it from the benchmark? Not sure what exact safety rules would I write for it.

Maybe we should have a with_scoped_stack constructor that takes a non-'static stack and allows you to use it only within a closure. This should avoid the issue with forgetting a coroutine.


Use respend framework for respends found in blocks

Reuse the new framework and avoid the need to repeat logging in CTxMemPool::removeConflicts(...)
Functional test txn_doublespend.py should succeed and log the respend found in a block, while txn_clone.py should succeed and not log the respend because the RespendLogger doesn't log equivalent clones.

Looks good. Nice to see duplicate mempool logic removed. Had a couple of nits.

Originally I didn't have a valid flag in MempoolRemover but because SetValid is required to be implemented and RespendLogger doesn't do anything unless valid, I added it with the intention of requiring it.  Update pushed.


multi-sig release

user story
As a team of devs developing one app, we would like to set up a multi-sig quorum to sign releases, so that we distribute signing responsibilities & risk.
acceptance criteria

devs can set up quorum m of n multi-sig for signing releases

questions

what happens if a dev retires, or steps away?

context
see https://njump.me/nevent1qqs8pmmae89agph80928l6gjm0wymechqazv80jwqrqy4cgk08epjacrrnpt0
see https://github.com/nickfarrow/frostr

Shouldn't we leave these things to emerge from users? Maybe there's little demand

Fair. Let me add a new label - unvalidated

Sure is there value in collecting issues that may never be implemented?

How about having ONE issue where we add these unvalidated ideas?  A lot of them adds clutter when trying to find the important stuff

How about having ONE issue where we add these unvalidated ideas? A lot of them adds clutter when trying to find the important stuff

OK
https://github.com/zapstore/zapstore/issues/105


Framerate Ticker and Command Line Arguments

This commit implements a framerate ticker in the bottom left corner of the window.
It also allows for further extension of command line arguments.
I do believe this could be further refactored to use a module such as argparse, but I felt that as the goal of this project is to teach people how to code, the implementation of sys.argv was more suitable.

Further, I do know this already existed within the label. However, I felt it was more accurate to establish a more consistent and stable visual of the framerate, to allow developers to see more clearly what is occurring. The current implementation moves too rapidly to make much of it, in my opinion.


Merge argo admin all

TODOs before merging

[x] Delete unused files
[x] Remove commit lint
[x] Update shared files inside .github like CODEOWNERS, ISSUE_TEMPLATE, pull_request_template.md
[x] Update shared files (tsconfig.json)

Tophat

Verify the yarn build can be run to build both Admin and Checkout libraries
Run dev server and verify that the example Playground scripts work
Run yarn workspace @shopify/argo-admin-cli run ts-node ./src/cli server --entry \"sample-extension.tsx\" --port=39351 --type=\"PRODUCT_SUBSCRIPTION\" --apiKey=subscriptions-dev-key and verify that the Simulator work. Make sure no shop param is passed in in order to show the Simulator

Follow up PRs

[ ] Use sewing-kit to run argo-admin tests
[ ] Use sewing-kit to build argo libraries
[ ] Update remote-ui dependency for argo-admin

@joeyfreund oops sorry, I renamed the commands but forgot to push the changes. Can you try again?

yarn server:admin seems good
% yarn server:admin
yarn run v1.19.2
$ yarn workspace @shopify/argo-admin-playground run server
$ SHOPIFY_DEV=true ts-node -r tsconfig-paths/register ./src
🔭 > Starting dev server...
🔭 > Available scripts:
🔭 > http://localhost:39355/3p-playground.worker.js
🔭 > http://localhost:39355/3p-components-list.worker.js
🔭 > http://localhost:39355/3p-inline-script.worker.js
🔭 > http://localhost:39355/3p-use-form.worker.js
🔭 > http://localhost:39355/3p-vanilla.worker.js
🔭 > http://localhost:39355/3p-subscription-content.worker.js
🔭 > | What's next?
🔭 > | Open https://cdn.shopify.com/shopifycloud/web/assets/v1/argo-admin-playground.html
Compiled successfully.

But, when I try to open http://localhost:8080/#/devtool I get

(notice that it's trying to load the extension code from argo-playground.myshopify.io.
And, if I try to load it from localhost:39355, I get:

@joeyfreund sorry the instruction is wrong - you need to do dev server:admin in order to have the file served at https://argo-playground.myshopify.io. Serving it without a secure url doesn't work.

Is this something that 3rd party developers will ever need to do?
What about potential contributors (once we open-source everything)

The way it works now is only intended for 1p as dev is internal. 1p can test local scripts and also use the local Web Argo Playground for developing new components.
3p can only use the example scripts to test with the hosted Argo Web playground (home page only) if they run their own tunnel. They cannot use the scripts in the same way as 1P since they don't have access to the host. Ex. They will not be able to contribute new components

yarn workspace @shopify/argo-admin-cli run ts-node ./src/cli server --entry \"sample-extension.tsx\" --port=39351 --type=\"PRODUCT_SUBSCRIPTION\" --apiKey=subscriptions-dev-key is ✅  as well.

Closing in favour of https://github.com/Shopify/argo-checkout/pull/77