🌍 feat: Extend regex to support international usernames

Summary

update regex: api/strategies/validators.js
update test: api/strategies/validators.spec.js

As suggested by @NoobSkie on Discord, and in alignment with our ongoing efforts towards internationalization, this pull request introduces significant enhancements to our username validation mechanism.
Previously, our username validation regex was limited to Latin script and a handful of symbols, restricting users from non-Western regions from registering with usernames in their native scripts. Recognizing the importance of inclusivity and the global nature of our user base, I expanded the regex to include:

Cyrillic (for users in Russia and Eastern Europe)
Devanagari (for users in India and Nepal)
Han (covering Chinese, Japanese Kanji, and Korean Hanja)
Arabic (for users in the Middle East and North Africa)
Hiragana and Katakana (for Japanese users)
Hangul (for Korean users)

Change Type

[x] New feature (non-breaking change which adds functionality)

Checklist

[x] My code adheres to this project's style guidelines
[x] I have performed a self-review of my own code
[x] I have commented in any complex areas of my code

thanks!


CustomizeColumns flyout offset is incorrect

CustomizeColumns flyout offset is incorrect
The CustomizeColumns flyout has a position: absolute and it seems to be positioned based off the DatagridToolbar. This is a problem because when you add other actions to the toolbar the offset is incorrect.

The right property is 308px (this should also be using Rems and not px) of the parent which is DatagridToolbar

What package(s) are you using?

[x] Carbon for IBM Products (or Carbon for IBM Cloud & Cognitive)
[ ] Legacy/CDAI
[ ] Legacy/Security

To fix

[ ] Make the customize column flyout position based on the button and a parent to wrap both
[ ] change the top and right property to use rem instead of px

Closing as #2433


测试数据

您好，非常感谢您提供的数据处理代码！我最近在关注HOI4D的object challenge，但是并没有看见网站上有公布关于位姿跟踪的测试数据集，请问是我哪里有疏忽吗？

Hi huihui0613,
I am sorry for the missed data of the Objpose Challenge. We are going to update the "Objpose Challenge Data" link.
As an alternative solution, we recommend to download data from "RGB Video", "Depth Video", "CAD Model", "Annotations" and "Camera Parameters" and then process the data with the relevant codes from this repository.

非常感谢你的回答~

Hi huihui0613,
I am sorry for the missed data of the Objpose Challenge. We are going to update the "Objpose Challenge Data" link. As an alternative solution, we recommend to download data from "RGB Video", "Depth Video", "CAD Model", "Annotations" and "Camera Parameters" and then process the data with the relevant codes from this repository.

我下载的就是官方网站链接中的数据集，但是我发现这里面只有训练数据，并没有测试数据

The test set of HOI4D is specified by the file "testset.txt" in this repository. For the Objpose Challenge, only rigid categories in the test set are included in the challenge.

The test set of HOI4D is specified by the file "testset.txt" in this repository. For the Objpose Challenge, only rigid categories in the test set are included in the challenge.

以刚体马克杯为例，我并没有在数据集中找到对应的测试列表

We have re-uploaded the files of Objpose Challenge.

真的非常感谢你不厌其烦的解答！非常感谢！

We have re-uploaded the files of Objpose Challenge.

您好，这个链接里的测试集每个视频只有第一帧有object pose的ground truth，无法用来测试模型性能。请问可以release所有帧的gt pose吗？


fix: Added config folder resolve fallback, Closes #1476

I haven't found any tests for resolving the configs @antfu, if needed I can try to come up with some. Tested with ExtensionDevelopmentHost VSCode instance.

I am not sure if I understand how this fixes. I have pushed https://github.com/unocss/unocss/commit/804608ad80838c9015f49e55a31ac9da321cb9c3 to fix the original issue, or can you share more details?

I am not sure if I understand how this fixes. I have pushed 804608a to fix the original issue, or can you share more details?

With this fix, the astro config was successfully loaded @antfu, as there was a issue with resolving the correct path with the reference provided by the issue. I will close this PR, as you created an alternative fix 😀


[Feature Request] allow to control the text baseline

Are you using the latest version of jsPDF?
yes
I see that there is a private method _getBaseline(y). But I could not find out how i can set the textbaseline  to be "hanging" from my application.
Would it be possible to have  an entry in the text options (baseline: 'hanging')?

I tried to investigate the testcases but was not at all successful. In the code I find some traces of "baseline" (e.g.         _getBaseline: function _getBaseline(y)  ) but I was not able to find out how I can apply the baseline of a doc.text ...

Sorry after I found out how I could test this on your master branch, if find out that lineheightfactor is great but does not address this problem.
var doc = new jsPDF();
var doc = new jsPDF();

doc.setFontSize(40);
doc.line(0,20,210,20)
doc.text(["lhf .7", 'test','test'], 10,20, {lineHeightFactor: 0.7});
doc.text(['lhf 1','test','test','test'], 50,30, {lineHeightFactor: 1});
doc.text(['lhf 0','test','test','test'], 90,40, {lineHeightFactor: 0});
doc.text(['hanging','test','test','test'], 130,30.5, {lineHeightFactor: 0});

Yields

I would like to achieve the "hanging" example without manually fiddling the y position.
We see that lineHeightFactor: 0 does not work.

added baseline functionality with #2125
please check and report if it works like expected.

I tried with
var doc = new jsPDF();

doc.setFontSize(40);
doc.line(0,20,210,20)
doc.text(["lhf .7", 'test','test'], 10,20, {lineHeightFactor: 0.7});
doc.text(['lhf 1','test','test','test'], 50,20, {lineHeightFactor: 1});
doc.text(['lhf 0','test','test','test'], 90,20, {lineHeightFactor: 0});
doc.text(['hanging','test','test','test'], 130,20, {baseline: 'hanging'});

doc.line(0,100,210,100)
doc.setFontSize(10);
doc.text(["My", 'size 10','size 10'], 10,100, {baseline: 'hanging'});
doc.setFontSize(20);
doc.text(['My','size 20','test','test'], 50,100, {baseline: 'hanging'});
doc.setFontSize(30);
doc.text(['My','size 30','test','test'], 90,100, {baseline: 'hanging'});
doc.setFontSize(40);
doc.text(['My','size 40','test','test'], 130,100, {baseline: 'hanging'});

doc.line(0,200,210,200)
doc.setFontSize(20);
doc.text(["My", 'bottom'], 10,200, {baseline: 'bottom'});
doc.text(["My", 'top'], 40,200, {baseline: 'top'});
doc.text(["My", 'middle'], 60,200, {baseline: 'middle'});
doc.text(["My", 'hanging'], 90,200, {baseline: 'hanging'});
doc.text(["My", 'alphabetic'], 120,200, {baseline: 'alphabetic'});
doc.text(["My", 'ideographic'], 160,200, {baseline: 'ideographic'});

Result is

It works like expected. It is somehow a bit imprecise, but I am afraid, this would be hard to fix with reasonable effort. It might depend on font and font metrics:

Thanks a lot for this fix. I think we can close the issue.


How to build LiteOS by GCC toolchain

Are there anyway to build LiteOS by GCC toolchain, it seem we can now only build from IAR embedded workbench and Keil.
Both of the IDE can't use it on Linux.
Thanks.

LiteOS can build by GCC toolschain. But from now on ,we run LiteOS on ARM Cortex M use iar or Keil  as example.I am sorry for this，Please wait a GCC version，We will provide soon.

close it.

Closed #14 via b29d4036


TheDTSS Clan Family (Update)

Just a new issue in order to update and add more clans to our clan family and also update a few things. Also first time updating so I have a quick question: what would I need to include into the issue (e.g. Do I still need the social links if I'm not updating them?).
name: TheDTSS Clan Family
key: TheDTSS
color: blue
emblem: Coin_03
info:
  logo: https://cdn.royaleapi.com/static/img/brands/logo/thedtss.png?t=7590867bc
  description: >
    TheDTSS is a fun and friendly environment of active and skilled Clash Royale players. Officially started in November of 2020, the clan family is a steadily growing and positive place for anyone who enjoys playing the game. We have a great selection of clans and also have a few notable players. Dedicated to helping out everyone and leaving no one behind, we pride ourselves on making sure every member is satisfied even though we may not be the best! Be selfless and humble: that is TheDTSS way!

clans:
  - name: TheDTSS
    tag: LL8P0GJY
  - name: TheDTSS Second
    tag: LPL9QPJU
  - name: Ghost House
    tag: YJGL92VU
  - name: Budski
    tag: YJPCJ9QQ
  - name: Old Trafford
    tag: 2JQCLPQ
  - name: TheSwishies
    tag: YGU0JCGU

No, It's not needed to update Social links for another time if you guys aren't updating that key. Onlay mention those keys which are to be updated/ modified.


Install the program via pip

Make it possible to install the library via pip.


refactor: use OnceLock to remove lazy-static

Feature or Problem

This commit removes the use of lazy-static in favor of std::sync::OnceLock
Related Issues

Release Information

Consumer Impact

Testing

Built on platform(s)

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

Tested on platform(s)

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

Unit Test(s)

Acceptance or Integration

Manual Verification

Moving this to wasmcloud/wasmcloud!


Low Voltage Solar Lanterns

[ ] Low-voltage Solar Lanterns

I had a idea to add Solar Path / Garden Lights to ELN2 since they would be pretty easy to design, all they would need for a recipe to craft would be a solar panel, led, battery, light sensor, and some metal and glass to make one.
Like in real life they come on at dusk, run until their battery is dead and recharge during the day to come on again and run the next night.
i have put in images of some solar lights for a perfect example you could model the item off of.

I have this in the Single Cell Blocks milestone because I think that it should be a good test for a stand-alone circuit simulation within a cell that doesn't need to connect to anything around it but still ticks the simulator. It also has the added benefit of being in a model that is no larger than a single block. So it should be a nice test.

Most solar lanterns are implemented as seen in the image below:

Pretty cheap, no charge controller or anything fancy like that. Just a diode to prevent the battery from backflowing into the solar panel (since it's effectively a very inefficient LED). The red circle next to the 100 ohm resistor is simply a LED (Falstad makes it look like that)

Oh, don't bother with crafting for this. Just make it work in creative. We'll add crafting at a later date.

@Ye-Old-Apple So, Cameron didn't like that the lantern isn't nearly as blocky as it could be... do you think you could make the post and the frame of it more blocky and less triangle-y? I really like the model but he says it really doesn't fit into the mod's art style. It would be great if you could do that. I think he would likely have similar comments about the indicator light so perhaps let's also make that light a 6x6 with a 4x4 flat light panel inset into the light frame (no angles)?


fix: experiment audit persists using post handler

Added experimentation-ess-all audit, which will crunch the RUM data for 6 months. This will not be scheduled, but will be manually triggered when on boarding the customer to get all the historical experiments into persistent store
Implemented Post handler for experimentation audits to update the experiments entity in persistent store after experiment audit is run
Added context for audit postProcessor logic so that we can access the dataAccess methods in the postHandler and updated documentation

Fixes: SITES-23404

:tada: This PR is included in version 1.22.2 :tada:
The release is available on:

v1.22.2
GitHub release

Your semantic-release bot :package::rocket:


Speeding up a script that uses Img2Vec

Is there a way to run this across 4 GPUs or speed it up any other way? The script takes a really long time. Also, I have 4 GPUs each with 11G of GPU memory. However, this code only takes ~1G of one of the GPUs.
from img2vec_pytorch import Img2Vec
from PIL import Image
import torch
import glob
import os

# # Initialize Img2Vec with GPU
img2vec = Img2Vec(cuda=True)
for dirpath, dirname, filename in os.walk('/SeaExp/ABC/'):
    if dirpath.endswith('XYZ'):
        images_full_path = dirpath + '/*.jpeg'
        for img in glob.glob(images_full_path):
            rgb_img = Image.open(img)
            vec = img2vec.get_vec(rgb_img, tensor=True)
            vec_name = os.path.basename(img)[:-5] + '.pt'
            dir_name = os.path.dirname(img)
            torch.save(vec, dir_name + '/' + vec_name)

If getting the vector is the bottleneck, you could explore the batching option available in the get_vec() funciton. Try passing in a list of PIL images instead of one at a time.


Macros enabling removal of explicit Fact naming

Previously, Facts had to be declared and named manually to guarantee uniqueness of names inside the engine:
object MyGlossary extends Glossary {
  val MyFact = new SingularFact[Int]("MyFact")
}

The redundancy of the Fact's name is not just a nuisance to type, it actually causes trouble when renaming the Fact, or trying to copy its declaration. In both situations, you must also alter the name parameter manually. The compiler and IDE tooling cannot help you track these errors down and so you are bound to find out about them at runtime, with potentially uninformative error messages.
This pull request adds several macros to the project which allow for much easier declaring of Facts. The macros run during compile-time and transform their invocation into the line of code above, extracting the name of the val and providing it as the name of the Fact being constructed.
Using these macros, the above example could be rewritten as follows:
import org.scalarules.utils.FactMacros._

object MyGlossary extends Glossary {
  val MyFact = defineFact[Int]
}

There are alternatives of the macro for creating SingularFact and ListFact instances, as well as variations accepting a value for the description parameter of the base fact.
In light of this added feature, this PR also includes a bump in the minor version of the project. Backwards compatibility is guaranteed because the old method of defining Facts manually is still available and unaltered.

I lied a bit about the backwards compatibility. I replaced the body of the Glossary class and anyone currently using it will be facing compiler errors. I'm just about to push a commit restoring it to its former glory and moving the new code to a new class called MacroGlossary.

I think this is extremely cool stuff.
I'm not sure about your intent though, judging from your story. Do you mean to have the macro implementation replace the old implementation? Or do you always want to have the old one as a fallback?
I would assume the former, because of the issues you mention with renaming them etc.
But it feels like the macro implementation is still kind of a second class citizen. I notice you did deprecate the Glossary class, but not its methods. (Which means you can hide the warning in the imports, not in the code actually using it.) Also, the new glossary is called MacroGlossary, which refers to its implementation details and therefore feels uncomfortable as a general purpose solution. Are you worried that there are still issues with the macro implementation?
In other words: why not just throw out the old implementation and replace it with the macro stuff? Even in semantic versioning, you're allowed to have breaking changes when the major version is still 0 (which it is). I'm not sure how large your client code base has become, but it doesn't seem like such a big deal to just change everything to the macro implementations there -- or am I missing something here?
But: extremely cool stuff!

As I stated out-of-bound: here I am trying to actually be backwards-compatible and you encourage me not to ;)
Anyways, you certainly have a fair point. Our user-base is probably still just 1 project, which is also in our own control. And actually the 'old way' is easy enough for someone to recreate if they're too scared of macros.
All in favour of removing the old way without deprecation and provide the macro-way as our pre-1.0 default, please +1 this particular comment. ( @jqno @vzorge @NRBPerdijk )

Because of these changes, the value false is now always given for the isResult parameter for a Fact. We should probably remove this parameter for now. Its intended use was to differentiate between types of Facts (inputs, partial results and outputs). This was always a sub-optimal solution and it would be better to redesign this from scratch

Yes, I agree. I'll remove it, since it has no value anymore whatsoever.
As a replacement, I was thinking about allowing users to define their own 'metadata' to associate with Facts, but I haven't worked out a design for it yet.

What is keeping this pull request from being merged?

Me giving @NRBPerdijk a chance to take a look at it first :)

Reviewed, looks rather nice! Macro's sure are different... :)

Closes #11


viewing changingChildren example

Hi,
I'm trying to view the changingChildren example, so I changed the gulp file to
gulp.task('watch', function() {
connect.server({
root: 'examples/changingChildren',
livereload: true,
port: 8003
});
...
Then ran 'gulp watch', but I'm getting 'Uncaught SyntaxError: Unexpected token import     main.js:1'
Could you please let me know how to go about it?
Thanks!

got it figured out


chore: Test identity

Description
Introduction of a test identity, that allows for service access testing. With a use case.
Checklist

[x] Investigated and inspected CI test results
[x] Unit test and regression tests added
[ ] ~Evaluated and added CHANGELOG entry if required~
[ ] ~Determined and documented upgrade steps~
[ ] ~Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

Testing Performed
Tested with a use case unit test. More tests could be added to the authn/test package, perhaps.

Current dependencies on/for this PR:

master

PR #7035

PR #7053   👈

This comment was auto-generated by Graphite.

I probably miss some context, but why this additional structure is needed when we have mock identity:
https://github.com/stackrox/stackrox/blob/ec1304f0aa4caa32a76c6fbba291ce35f824a1fe/pkg/grpc/authn/mocks/identity.go#L18-L18

I thought mock identity is too invasive to use for when we don't test identity providers.
Compare a test identity usage:
goodID := testid.NewTestIdentity("test", s.T())
goodID.AddRole("Administration", storage.Access_READ_ACCESS, role.AccessScopeIncludeAll)

with functionally similar mock identity (a minimal setup for my case):
goodID := mockid.NewMockIdentity(s.mockCtrl)
rr := []permissions.ResolvedRole{roletest.NewResolvedRole("test",
	map[string]storage.Access{"Administration": storage.Access_READ_ACCESS}, role.AccessScopeIncludeAll)}
goodID.EXPECT().Roles().AnyTimes().Return(rr)
goodID.EXPECT().Permissions().AnyTimes().Return(utils.NewUnionPermissions(rr))

@0x656b694d IMHO mocking identity when you test authorization is a valid use case and not too invasive. I also think being more compact with line count is not the goal when it comes to tests.
However, if you want non-mock identity you can add roles to, why roleBasedIdentity does not work? From what I see, your struct is very similar to it. Then we will have a unit test that calls the method with the actual identity struct it will receive.

This is what I'm trying to avoid doing in our services unit tests:
https://github.com/stackrox/stackrox/blob/michael/test-identity/central/graphql/resolvers/vulnerability_requests_test.go#L175

Closed as useless.


On t-SNE for MNIST

Hi Kyle, this is not really an issue with parametric t-SNE, so apologies for posting it here but I could not find a more appropriate way to contact you (somehow failed to find your email).
My question is about running t-SNE on MNIST data. What I often experience myself is that some of the MNIST digits get "split" by t-SNE into two clusters, presumably stuck in a local minimum. This happens very often. The figure shown here https://github.com/DmitryUlyanov/Multicore-TSNE shows this issue with red cluster. The MNIST t-SNE plot shown here https://twitter.com/leland_mcinnes/status/963230617600184320 shows this issue even stronger with yellow cluster (look at the bottom). However, your plot shown here https://www.flickr.com/photos/kylemcdonald/26620503329/in/album-72157662596196708/ is completely free of such artifacts.
How did you achieve that? Did you try it out multiple times with random initialization until it worked? Did you use some specific initialization? Did you use some carefully selected parameters? (Perplexity, PCA preprocessing, early exaggeration, etc.) Some other trick?
I'm really curious. Thanks.

Let me know if there is a more appropriate venue to contact you about that. Cheers!


bazel: use distroless/static to base image

WHAT
Use distroless/static to base image.
WHY
more smallest container image.
Ref

https://github.com/bazelbuild/rules_docker/blob/v0.12.1/go/image.bzl#L113

the branch name is wrong... ignore it.

close for now. send PR again.


chore(python): improve build time

Description

Motivation
Improve Python tracer build times by leveraging CMake parallel build env var.
Workflow

⚠⚠ Create your PR as draft
Follow the style guidelines of this project (See how to easily lint the code)
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Once your PR is reviewed, you can merge it! :heart:
Reviewer checklist

[ ] Check what scenarios are modified. If needed, add the relevant label (run-parametric-scenario, run-profiling-scenario...). If this PR modifies any system-tests internal, then add the run-all-scenarios label (more info).
[ ] CI is green

[ ] If not, failing jobs are not related to this change (and you are 100% sure about this statement)

[ ] if any of build-some-image label is present

is the image labl have been updated ?
just before merging, locally build and push the image to hub.docker.com

[ ] if a scenario is added (or removed), add (or remove) it in system-test-dasboard nightly

Hi @gnufede , do you still plan to work on this ?

Seen on slack, closing in favor of #2876


Standardisation of annotation names

Since the Ingress resource itself doesn't support many features, a lot of configuration is done via annotations.  This raises potential compatibility issues between Ingress implementations, as there's no schema validation for these annotations, and they aren't documented in the official API specification.
For my own Ingress controller, I've re-used annotation names from the nginx/gce controllers where possible (such as "ingress.kubernetes.io/ssl-redirect").  However, in other cases I've had to invent new names for features the nginx controller doesn't support (for example, "ingress.torchbox.com/auth-satisfy" and "ingress.torchbox.com/hsts-max-age").  This is bad, because it makes the annotation names specific to my implementation, even when the feature should work with many different implementations, if/when it's implemented in those controllers.
Is there, or should there be, an "official" list of recognised Ingress annotations, beside the list in the documentation for the nginx/gce Ingress controllers, which only lists annotations actually supported by those implementations?

Is there, or should there be, an "official" list of recognised Ingress annotations, beside the list in the documentation for the nginx/gce Ingress controllers, which only lists annotations actually supported by those implementations?

The idea was to use the generic ingress controller annotations located here to expose generic annotations that can be optional supported by any Ingress implementation.
If you use the generic controller as base for your controller, then after implementing the interface the method OnUpdate you will receive all the servers, locations and parsed annotations ready to configure the software you choose as backend for the ingress controller.

Okay, but this still leaves the problem that if I want to implement something that the generic Ingress controller doesn't support (perhaps because neither GCE nor nginx support that feature, or just because no one has implemented it for those yet), there won't be any standard name for it.
Should I just make up my own name (not using ingress.kubernetes.io) and accept that there won't be any cross-controller compatibility for those options?

@unixwitch the implementation of the annotations is optional. Your hsts example is generic so I think we should add that to the generic controller

Closing. PR #776 is merged


Search Parameters Question

I am new to this API and was curious if there are query parameters for searching (ex: Bugs where price is 160 (/bugs?price=160). Is this something that I'm not seeing in the docs or not implemented? I definitely think this would be beneficial so the responses would only contain certain items you want.

+1 to this as well.
I can see the benefit to this. Current state I'm just taking the JSON data and manipulating the data by the different attributes on the frontend or using js.


Markdown in Gogs incorrectly renders nested lists when nested list uses bullets

According to Markdown Basics you can have nested list in form of:
1. Item 1
  1. A corollary to the above item.
  2. Yet another point to consider.
2. Item 2
  * A corollary that does not need to be ordered.
    * This is indented four spaces, because it's two spaces further than the item above.
    * You might want to consider making a new list.
3. Item 3

In Gogs only first scenario (both outer and inner list uses numbers) works fine. When you have second scenario (outer list uses number, inner list uses bullets), this is ignored and you end up with dual number nested list. See below images as examples.
From left to right: Markdown code | rendering effect in GitHub | rendering effect in Gogs:
Case 1: Inner list uses dashes and items are separated with blank line:

Case 2: Inner list uses asterisks and items are separated with blank line:

Case 3: Inner list uses asterisks, but there is no blank line separation:

You can also notice, that in case 1 and 2, when there is a blank line separation after each item, inner list also has an ugly empty line intro in the beginning.
Please, consider fixing this ASAP, as nested lists are very useful for step-by-step guides or TODO lists. Currently, they can't be used in Gogs, because rendered final effect is quite ugly.
Issue somehow related to #1416.

Thanks a lot!

I made this pull request to solve the nested unordered list inside an ordered list appearing as an ordered list.
About the the ugly line it must be solved in blackfriday library. Or maybe there is an option to configure blackfriday in a way that it won't happen. We will need to append a new commit with the configuration solution if there is one.

Thank you for a super-fast response and fix! I'm shocked to see how quick things happens here! :>

See https://try.gogs.io/manfer/MarkDownSample for fixed version on develop.

I must admit, that I don't understand you! :> Without fix introduced in @manfer PR Gogs was not rendering nested list correctly. See my examples (case 3) and compare with link you provided. Do you mean, that after this PR is merged, then now all styles from given example should work fine?

@trejder Yes, all should look the same as they look on github. Needs to be fully tested anyway.
I down recall if this issue had the first markdown sample that it has now at the beginning which has a second nested unordered list on the second item of the ordered list. That one in gogs is not rendering a new list but interpreted as items of the same unordered list. But that could be just that the markdown is not valid for blackfriday markdown. We will have to find which is the correct markdown so it is interpreted as a new list. Maybe with four spaces instead of two or maybe a new line is needed to break the first unordered list. Anyway that would be for sure a blackfriday issue.
The blackfriday output of your markdown sample is:

Item 1

A corollary to the above item.

Yet another point to consider.

Item 2

A corollary that does not need to be ordered.

This is indented four spaces, because it's two spaces further than the item above.

You might want to consider making a new list.

Item 3

And there is little gogs can do about it.

I added list samples at the end of the demo in https://try.gogs.io/manfer/MarkDownSample

I added a nested unordered sample and I can confirm you need four spaces to nest unordered lists, two spaces is not enough.
I added the needed spaces to this sample:
1. Item 1
  1. A corollary to the above item.
  2. Yet another point to consider.
2. Item 2
  * A corollary that does not need to be ordered.
      * This is indented six spaces, because it's four spaces further than the item above.
      * You might want to consider making a new list.
3. Item 3

And now it works fine https://try.gogs.io/manfer/MarkDownSample

@manfer amazing examples, thanks!

@manfer Thank you for detailed explanation and examples. Now (nearly) everything is fine and understandable. The only thing is I don't know or I do miss is your last example with nesting code inside a list. It is a key of my #1416 bug report and now (in your examples) it seems fixed (i.e. nested code is rendered as line code, not as in-line code) thought there is no PR to #1416 nor I can find any change to Gogs, that would fix that. And #1416 remains open. What am I missing? Why examples works fine for this part? When and how it was fixed?

Same PR https://github.com/gogits/gogs/pull/1425 fixes both ;)

@manfer Thank you for detailed explanation and examples. Now (nearly) everything is fine and understandable. The only thing is I don't know or I do miss is your last example with nesting code inside a list. It is a key of my #1416 bug report and now (in your examples) it seems fixed (i.e. nested code is rendered as line code, not as in-line code) thought there is no PR to #1416 nor I can find any change to Gogs, that would fix that. And #1416 remains open. What am I missing? Why examples works fine for this part? When and how it was fixed?

Normally I will for poster's confirmation then close issue.
But will be forced close after a certain days like now... :joy:


Improve Markdown Rendering when using Webview

Opening Repos with a lot of Markdown content in its Readme.md file crashes the app. Also in a lot of cases even if the Markdown is not huge it is unable to render it completely.
Examples:

https://github.com/transloadit/uppy
https://github.com/mdn/content
https://github.com/openpgpjs/openpgpjs

Thanks for the feedback.
Could you please provide more device info, for example, Android or iOS, System version?

@pd4d10 I am having the same issue, on latest fdroid build 1.11.1.
Device: Google Pixel 4 non-xl, Android 11 Janurary 2021 security update.
The other application, OctoDroid which I was looking to switch from as this integrates other services like Gitlab, also had similar issue was was addressed in an earlier update.

I have the same issue. How about setting the flutter render engine as default before this issue is properly solved?

Yep, it seems that the Android webview widget may have some problems, for example #123 and #194

setting the flutter render engine as default

Makes sense. We could make Flutter render engine as default on Android.

The reason we prefer Webview is that inline HTML is not supported in the Flutter markdown widget.
BTW, this issue could be submitted to the official repo: https://github.com/flutter/flutter/issues?q=is%3Aopen+is%3Aissue+label%3A"p%3A+webview"


Xlink kai install script issue

In line 102 of the xlink kai install script (/ansible/install_xlink-kai.yml) it says "ansible.mport.playbook" instead of "ansible.import.playbook" which causes an error when running the script

Thanks, this typo is now fixed in the testing branch
Thankfully this should not have prevented the install of the application as ln:102 is just logging the package id for our internal use

Well the typo gave me this output when installing the application, thats why i filed the issue


Allow bounce property greater than 1

Currently the bounce property of RigidBody nodes must be between 0 and 1, where all energy is lost for a bounce of 0 and no energy is lost at a bounce value of 1. It would be nice if the bounce property could have a value greater than 1, where for example a bounce value of 2 would double the energy returned to the RigidBody, thus having somewhat of a launching effect (think Pinball bumpers). I have seen this in other game engines.

Not surely how useful that would be as your ball's speed would quickly diverge towards +∞. But if it's supported by Bullet, we can always expose it while keeping the inspector field slider from 0 to 1 (using allow_greater in the hint to allow manual higher input).
CC @AndreaCatania

@Oranjoose  Isn't this possible and more logical, to use the body_exited signal?
I mean that even in real life the bumpers are responsible for the extra bounce of the ball.

@kakoeimon is correct, increase bouncing limit is not a good idea

@kakoeimon: Isn't this possible and more logical, to use the body_exited signal? I mean that even in real life the bumpers are responsible for the extra bounce of the ball.

Yes, and as such you can set the bounce property on the StaticBody bumpers, which in turn affect the ball. And by body_exited, do you mean to multiply the the linear_velocity by 1.2 in a body_exited callback, instead of having a bounce of 1.2?
The point is, consider the inverse. If there wasn't already a hard upper limit, then there wouldn't be a particularly strong reason to add one. If someone wants to set a bounce property to more than 1, let them. As an anecdote, in the game development summer camp I run, it seems to be somewhat of a rite of passage that as soon as we go into physics bodies, the teenagers immediately--without being told--increase bounce past 100% and have a blast doing so (different game engine than Godot).

I may come back to this

PhysicsMaterial already allows manually entering a Bounce value greater than 1.0: https://github.com/Calinou/godot/blob/df936cc9336bb9c572d5e6c1f7cd31993ded5855/scene/resources/physics_material.cpp#L48
However, PhysicsBody3D does not: https://github.com/Calinou/godot/blob/df936cc9336bb9c572d5e6c1f7cd31993ded5855/scene/3d/physics_body_3d.cpp#L2994

You could try to see if my version works for you...I only worked in 2d though. If similar changes are done in the 3d code?
https://github.com/90PlusWorks/godot-air forked from Godot in 2022.


async / await support

Doesn't look like there's support for async/await style functions. For instance, This isn't getting picked up:
const myFn = async function({
 val1: mappingVal,
 val2,
 val3
}) {
  // ...
})

You are right. I plan to add a few TypeScript-oriented features this week-end and I will certainly find time to add this too.

@justinabrahms could you take a look at last commit (56ae576)?

Works super well! Thanks so much.


Language server critical regression from 2.0.5 to 2.0.6

Actual
Hi, I am facing some critical language server issue on 2.0.6. It was a very mysterious issue, so after seeing 2.0.6 is a new release I decided to regress to 2.0.5, which does not have this problem as it turns out.
I'm not sure what information is needed, if any, but I am willing to provide the required details.

Expected
Language server works; installing 2.0.5 and reloading does this
Environment
Volar (vue.volar)
2.0.6
VSCode
Version: 1.87.1 (user setup)
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:21:36.258Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

My colleagues do not seem to be having this issue but it is consistent for me. Feedback appreciated

Same issue for me in Nuxt. Vue highlighting is not working in 2.0.6.

The fix is to revert back to Vue - Official 2.0.5

Just upgraded to 2.0.6 this morning on a vue/webpack project and am not seeing this issue.
I have a separate vue/nuxt project that seems to have lost all typing for any imported components or nuxt builtins though.
    "nuxt": "^3.10.3",
    "vue": "^3.4.19",

Not Nuxt related I'm on Vue / Vite (Rollup)

Got it - in my case it was due to #3942 - having the styled-components extension installed.
disabling styled-components.vscode-styled-components resolved, does not seem to be Vue extension version related. I was able to use v2.0.6 once I disabled.

Should


RunAsNonRootUser

Describe the solution you'd like
csi driver pods are ran with root
Anything else you would like to add:
AKS security reports that the pods in our cluster are running with root user. And we find that csi driver is ran with root.
Is it possible to run the csi driver pods with non root user?
Environment:

Secrets Store CSI Driver version: (use the image tag):
Azure Key Vault provider version: (use the image tag):
Kubernetes version: (use kubectl version):
Cluster type: (e.g. AKS, aks-engine, etc):

@yktd26 Thanks for opening the issue. The driver pod need to run as root in order to mount the volume as tmpfs in pod. We recommend installing driver and provider in kube-system namespace.
Please refer to Why kube-system section in the doc for additional information.

@nilekhc thank you a lot, closing it.


Remove support for swildfly-swarm

Swarm currently treats camel as "unsupported" and has not taken in the 4.8.0 nor the 4.9.0 update. We are removing this for now and resurrect in case there is demand from the swarm folks.
[16:25:25]  <tdiesler>	@bobmcw, kenfinnigan, I assume you want to stick with what you have or perhaps don't bother at all with camel any more
[16:25:51]  <kenfinnigan>	tdiesler: we told you want was required to fix the PR, and you ignored us, so I closed it
[16:27:31]  <tdiesler>	kenfinnigan, lets perhaps first talk about what you'd like to do with camel in swarm.
[16:28:54]  <kenfinnigan>	tdiesler: flipped the other way, what does the Camel team see as the benefit? After all, it was yourselves that brought it to us
[16:31:37]  <tdiesler>	kenfinnigan, the fuse team is is offering camel integration with Karaf, SpringBoot and EAP. I year ago or so, I thought I'd do you a favor integrating what I have (for wildfly) with swarm. IIRC, there was some attempt to bring in camel to swarm, which did not leverage the camel subsystem
[16:36:59]  <kenfinnigan>	tdiesler: but what are the benefits to being able to run Camel on WF Swarm? We honestly don't see them, and we don't hear of people using that functionality
[16:37:46]  <tdiesler>	kenfinnigan, that's the answer then. I'd say lets park this topic until there is demand in swarm for camel. wdys?
[16:40:20]  <tdiesler>	kenfinnigan, I'd say if there is no demand, there may also not be a real need to do this just yet. I'm sure you have more important things to worry about.
[16:41:51]  <kenfinnigan>	tdiesler: i'm good with that approach, and somewhat ties into something we've been thinking about
[16:42:04]  <kenfinnigan>	which will be discussed on the group soon
[16:42:50]  <tdiesler>	kenfinnigan, great. If you should change your mind, the latest update is here https://github.com/tdiesler/wildfly-swarm/tree/wfc-4.9.x
[16:43:56]  <tdiesler>	kenfinnigan, I guess, we can resurrect this any time when needed

Swarm currently treats camel as "unsupported" and has not taken in the 4.8.0 nor the 4.9.0 update. We are removing this for now and resurrect in case there is demand from the swarm folks.

Swarm currently treats camel as "unsupported"

Do you know why? Esp. is this rather for technical reasons?

Whoa this is news too me. I go around giving talks about containers with OpenShift and k8s and demo running with both WF-Swarm and SB and that they play happily together. And yeah also that Apache Camel run equally well on both of them. That brings people choice.
We have many people in the community that are not on the spring pill, and are happy to use EAP / jboss middleware and are glad to hear that they can use Camel on WF-Swarm as well on os/k8s.


Simplify operator-related UI with element folding on mouseover

Introduction
This PR is to make the current UI relate to operators cleaner, namely, "less green". Currently, every piece of information is displayed near an operator, but when the workflow gets complicated and large, these (unnecessary) information makes the frontend unbearable to look at. In particularly, these are the main culprits:

Operator delete button
Operator statistics ("Processed: ...", "Output: ...") that are displayed as green text
Operator state which is also displayed as green text
The canvas's "black dots" since they overlap with all the texts and make texts hard to read

Solution
To address 1, 2, 3, UI element folding/unfolding is introduced, with mouseover and mouseout as folding/unfolding conditions. Additionally:

For 2, when folded the statistics are abbreviated.
For 2, source/sink operators are treated differently.
For 3, when folded the texts are hidden, but now we use operator boarder (stroke) color to indicate different states.
For 3, a new color is introduced to avoid conflict with color used in workflow validation:
paused state: red(#FF0000, old)->magenta(#FF00FF, new).
To prevent flickering when mouse moves between operator sub-elements, a new rect boundary sub-element is introduced to cover all the sub-elements.

To address 4, tentatively text background is introduced. But it should be noted since all the texts are SVG elements, which DO NOT support text background,  a simple hack is used. The downside of this hack is that it introduces more new elements and the background is not rectangular.
Demo
Below is a demo of the improved UI:

Files changed

joint-ui.service.ts: The main changes take place here.

Added elements and element styles
Implemented the style change logic for folding and unfolding
Changed some existing elements to support the added elements, in particularly, added names for rect svg class to distinguish between operator body and operator's "invisible" boarder; changed the order of delete-button in the HTML text or else it would be covered by text backgrounds.

workflow-editor.component.ts: Added calling logic for folding and unfolding
workflow-editor.component.scss: See rect above.

Update: CI not passed because of failed unit tests. Should also change unit tests for related files.

The PR looks very structured and clean! We should all learn from you with this standard. I Left some minor comments.
For the PR description, it's better to highlight the color change for the state. Mark it explicitly with some clear format: workflow state: old color -> new color. I also wonder if that's a good idea to include a markdown for the color visualization. https://stackoverflow.com/questions/35465557/how-to-apply-color-in-markdown/35485694

I modified my original comment and now it should show the color. FYI, Github does NOT support font color for security reasons because Font Color in Markdown is done through HTML element. But the good thing is Github does allow a color indicator using code-formatted HEX, like #FFFF00.

GUI unit test error fixed; CI passed.


Updating serverless to 1.32.0 and pinning version

Resolves customer-support issue 18 and serverless-plugin-iopipe issue 94. (Though I'll want to test both sad-path as well as happy path on my local.)

Closing as this wasn't the issue with Serverless.


Add hardcoded whitelisting into the config file

Documentation for https://github.com/api3dao/airnode/issues/1197

Hi @amarthadan, when creating docs issues, please add the Documentation label to it so it's immediately clear what's what. Thanks.

@kolenic-martin You can see that by the repository where the issue resides.

You can also filter the board by the repository if you need.

@amarthadan that's a good point, thanks. Although, why do we have that label in the first place when we're not using it?

In the Airnode repo? Just historical reasons I guess. That will be (hopefully) cleaned up at some point.


[Feature] Support rudr :run command

$ rudr deployment:run frontend --port 80 --image oam-dev/demo:v1

I'm working on this

fixed by #70


Fixed redundant PYIMATH_EXPORTS causing compile issues on Windows Clang

Compilation of the python bindings fails using Clang on Windows, due to declared __declspec(import)'s on code without external linkage. The behavior in MSVC is to throw these declarations away, but Clang will error out. It doesn't cause issues to remove them, as they don't serve a functional purpose -- the changed lines are in an anonymous namespace in PyImathStringTable.cpp and on deleted functions in PyImathUtil.h. Currently the PyImathTestC and PyImathTest_Python3 tests fail in my environment, though that's unrelated to the changes in this PR.

Closing because I didn't have my git config set properly for the commit. Will open a new one in a bit.


Problems when I change from a chat to another chat - The talks crashes at all

Same as:
https://github.com/RocketChat/Rocket.Chat/issues/4258

Seems to happen when you let the browser/App idle for a long time and then try to change channels


Support Regtest

I see testnet=False kwargs on various functions, but I don't see any way to do regtest. Could support for regtest be added?

Oh nevermind. Regtest addresses are the same as testnet.


Bot is getting deployed in http port

Hi
I have created a bot long back with DOTNET 4.6 framework & Microsoft framework v3
Now we are trying to deploy in azure web app  using azure publishing profile but it is getting deployed in "HTTP" port
Any suggestions how can i change port from "Http" to "Https"

HI @Krishna-chinthireddy Can you please give some more information?
Just to clarify, you mean v3.x of the Bot framework SDK and .NET framework v4.6? Or are you talking about v3 of the Direct Line service, and version 4.6.x of the Bot framework SDK?
What method are you using to deploy? Are you using Visual Studio, az cli, powershell or code?

Hi @dmvtech
It is Bot Framework SDK v3  &  .NET framework v4.6
Deployed using visual studio 2019

Thank you. You might try removing the publishing profile in VS and re-creating it. Can you explain more of what you mean by it is being deployed to the http port? Is the bot's messaging endpoint configured properly in it's azure portal settings? You can verify in the Azure portal that your WebApp/AppService is setup with the url as https?

Closing as no activity. Please let us know if you still are having issues.


Missing opengraph-image.jpg

I cannot seem to locate this opengraph image, after cloning the next-learn repo, searching for this file returns nothing:
find . -iname 'opengraph-image.jpg'

For reference, this discrepancy is mentioned in the 'Adding metadata' section of Chapter 16. Specifically under 'Favicon and Open Graph image'.
The statement: "In your /public folder, you'll notice you have two images: favicon.ico and opengraph-image.jpg."
In the public folder, there is a large-image.jpg which is likely what was intended to be referenced here. To utilize the next.js Metadata API, large-image.jpg should presumably be renamed to opengraph-image.jpg as well as the related references.

The documentation states that the file is opengraph-image.jpg, however the actual file in the repo is opengraph-image.png. So just replace jpg with png and it should work.
For reference, this is mentioned in Chapter 16,  specifically at the section 'Favicon and Open Graph image'.
Statement: 'In your /public folder, you'll notice you have two images: favicon.ico and opengraph-image.jpg.'

I really don't see it there:
find . -iname 'opengraph-image*'
#^ returns nothing
tree public
[4.0K]  public
├── [4.0K]  customers
│   ├── [7.8K]  amy-burns.png
│   ├── [7.8K]  balazs-orban.png
│   ├── [5.7K]  delba-de-oliveira.png
│   ├── [4.0K]  emil-kowalski.png
│   ├── [1019]  evil-rabbit.png
│   ├── [6.1K]  guillermo-rauch.png
│   ├── [5.5K]  hector-simpson.png
│   ├── [6.3K]  jared-palmer.png
│   ├── [5.5K]  lee-robinson.png
│   ├── [9.7K]  michael-novotny.png
│   ├── [7.0K]  steph-dietz.png
│   └── [7.2K]  steven-tey.png
├── [487K]  hero-desktop.png
└── [114K]  hero-mobile.png

2 directories, 14 files

It must've been added in after I cloned the repo, because I do see it now:
git clone --depth=1 https://github.com/vercel/next-learn.git
Cloning into 'next-learn'...
remote: Enumerating objects: 244, done.
remote: Counting objects: 100% (244/244), done.
remote: Compressing objects: 100% (183/183), done.
remote: Total 244 (delta 59), reused 165 (delta 34), pack-reused 0
Receiving objects: 100% (244/244), 1.14 MiB | 6.02 MiB/s, done.
Resolving deltas: 100% (59/59), done.
cd next-learn
find . -iname 'opengraph-image*'
./dashboard/final-example/app/opengraph-image.png
./dashboard/starter-example/public/opengraph-image.png


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v2.6.14 to before v5.10.46",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=815f62bf742718458ba822a7e1f51f285eb997f2",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=290b0b6432e2599021db0b8d6046f756d931c29f"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "815f62bf742718458ba822a7e1f51f285eb997f2",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "290b0b6432e2599021db0b8d6046f756d931c29f",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net: hamradio: fix memory leak in mkiss_close\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.46 by commit 290b0b6432e2599021db0b8d6046f756d931c29f, it was introduced in version v2.6.14 by commit 815f62bf742718458ba822a7e1f51f285eb997f2. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000989


platformio-atom-ide-terminal installed but doesn't work

Today I first install AtomSetup-x64.exe on My windows 64-bit machine
When I try to install "platformio-atom-ide-terminal", it works well without errors
However, no icon in the leftlower corner was found and the package menu is grey.

Plus: Terminal Plus can't be installed too which show
`Failed to install terminal-plus because Git was not found.
The terminal-plus package has module dependencies that cannot be installed without Git.
You need to install Git and add it to your path environment variable in order to install this package.
You can install Git by downloading, installing, and launching GitHub for Windows: https://windows.github.com
Run apm -v after installing Git to see what version has been detected.`

https://github.com/platformio/platformio-atom-ide-terminal/issues/297

https://github.com/platformio/platformio-atom-ide-terminal/issues/297


Open app when button is pressed

Hello! Thank you very much for this package, I was really looking forward to it.
How can I open an application with an argument when a button is pressed in a Tile?
It would be good to add this information to the documentation.

Its a known issue I'm trying to resolve, hopefully it will come in the next version.
I will update this issue when its fixed !
Thank you for the feedback 👍


Submitting Adobe Reader version<PHONE_NUMBER>.yaml

Microsoft Reviewers: Open in CodeFlow

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


add citation source.

Adds link to the quote: "Git is a four-handle, dual boiler espresso machine, not instant coffee."
Note: The quote is already paraphrased. So maybe no need to put it in double quotation.

Thanks for the find!


Support string literal dependency notation for add calls

This currently fails with parsing:
dependencies {
  add("myconfig", "com.example:foo:1.2.3")
}

parse error:
1: extraneous input '"' expecting {'file(', 'files(', 'project', ID}, 2: extraneous input '"' expecting {'}', ID}

NOTE: as a workaround, version catalog references are ok, e.g. this will work:
dependencies {
  add("myconfig", libs.foo)
}


Merge lit-unicode-*.inc.h-related generator scripts

The conversions and ranges files had separate generators, which
shared some functionality through a 3rd python module, and were
quite similar to each other -- but also had some differences.
Moreover, as they were separate scripts, nothing forced to keep the
outputs in sync (to re-generate them at the same time from the same
inputs).
To fix these maintainability issues, this patch

merges the two python files and part of the 3rd utility module
into a single script while keeping the existing functionality,
names the new file gen-unicode.py to align better with other
generator script in tools, and
adds some extra documentation how to retrieve the input files
(as they are not part of the repository).

The refactoring affected the utility module as well, so this patch
also

renames c_source_helper.py to gen_c_source.py (again, for
naming consistency),
reorganizes some of its functions not to export module-local
helper functions, and
adapts js2c.py, as it also uses this utility module.

JerryScript-DCO-1.0-Signed-off-by: Akos Kiss<EMAIL_ADDRESS>

@robertsipka please check this change

I strongly endorse this merge. I also think it is better to keep the outputs in sync. Previously, the version of the inputs were different, but after adapting the generator script of unicode ranges (to python code from bash script), and updating it with the latest version of Unicode Standard, it's not needed to re-generate them from different inputs and scripts anymore.
LGTM (informally)


git clone error: invalid path

When cloning this repository on WINDOWS, there are some errors and it seems that the file name contains invalid characters, such as :.
error: invalid path 'depth-test_z-acc_spatial-noise/point-clouds/Camera: Astra.ply'
error: invalid path 'depth-test_z-acc_spatial-noise/point-clouds/Camera: OAK.ply'

I think the invalid characters in the file name should be changed to other characters

Thanks for catching that. I accidentally added some unfinished code to the pull request.


Error executing v10 to v14

When running the plugin I get the following error
[ERROR] Failed to execute goal com.sebastian-daschner:jaxrs-analyzer-maven-plugin:0.14:analyze-jaxrs (default) on project core: Execution default of goal com.sebastian-daschner:jaxrs-analyzer-maven-plugin:0.14:analyze-jaxrs failed: An API incompatibility was encountered while executing com.sebastian-daschner:jaxrs-analyzer-maven-plugin:0.14:analyze-jaxrs: java.lang.VerifyError: Cannot inherit from final class
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>com.sebastian-daschner:jaxrs-analyzer-maven-plugin:0.14
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/ppasler/.m2/repository/com/sebastian-daschner/jaxrs-analyzer-maven-plugin/0.14/jaxrs-analyzer-maven-plugin-0.14.jar
[ERROR] urls[1] = file:/home/ppasler/.m2/repository/com/sebastian-daschner/jaxrs-analyzer/0.14/jaxrs-analyzer-0.14.jar
[ERROR] urls[2] = file:/home/ppasler/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
[ERROR] Number of foreign imports: 1

With v9 it works as expected.
I am not quite sure if this is related to https://github.com/sdaschner/jaxrs-analyzer/issues/109
Any help will be apprechiated.

Please see the update in #109


Use sunpy's remote data manager to handle external instrument files - [merged]

In GitLab by @wtbarnes on Oct 22, 2019, 22:27
Merges remote-data-api -> master
Closes #34.
This PR uses the new remote data manager feature in sunpy to manage the instrument files need to compute the wavelength response functions. If the files are not present locally, they are downloaded automatically from the specified URL. If for whatever reason those files change at some point in the future and it tries to download them again, an error will be thrown. See the remote data manager example for more information.

In GitLab by @wtbarnes on Oct 23, 2019, 10:50
added 1 commit
039b5b95 - put euv and fuv decorators on single function
Compare with previous version

In GitLab by @wtbarnes on Oct 23, 2019, 11:40
added 1 commit
3b434301 - move download logic to separate method
Compare with previous version

In GitLab by @wtbarnes on Feb 14, 2020, 15:10
This needs a rebase

In GitLab by @wtbarnes on Nov 20, 2019, 13:41
This feature has just been merged into sunpy master and it will likely make it into sunpy v1.1. This change could potentially make it into v0.1 of aiapy.

In GitLab by @wtbarnes on Oct 23, 2019, 11:10
Depending on whether file downloads are delayed in the merged version of remote data manager, it may be necessary to offload the download data logic to a separate function. This will prevent unnecessary downloads if the user has supplied a filename or a data structure with the preloaded data.

In GitLab by @wtbarnes on Feb 25, 2020, 14:00
unmarked as a Work In Progress

In GitLab by @wtbarnes on Feb 24, 2020, 21:48
added 35 commits
3b434301...8a7edd3a - 32 commits from branch LMSAL_HUB/aia_hub:masterac8717e4 - first go at using remote data manager apia8ac8500 - put euv and fuv decorators on single functionb4c54b32 - move download logic to separate method
Compare with previous version

In GitLab by @wtbarnes on Feb 25, 2020, 13:51
added 1 commit
0f619d83 - update hashes to sha-256
Compare with previous version

In GitLab by @wtbarnes on Feb 25, 2020, 19:00
added 1 commit
daaacb0a - need at least sunpy 1.1
Compare with previous version

In GitLab by @wtbarnes on Feb 25, 2020, 21:17
added 1 commit
4a645c4d - separate out download functions into euv and uv
Compare with previous version

In GitLab by @Cadair on Mar 5, 2020, 14:15
Commented on aiapy/response/channel.py line 70
I would consider moving the read into the functions below which use the data manager, it feels a bit cleaner with the data manager API as it is, you would be asking "get me this data" and it would get the file and return the info.

In GitLab by @Cadair on Mar 5, 2020, 14:15
Commented on aiapy/response/channel.py line 74
You can set up mirrors here if you want.

In GitLab by @markcheung on Feb 28, 2020, 11:44
approved this merge request

In GitLab by @Cadair on Mar 5, 2020, 14:23
This looks good. There is a bit of an impedance mismatch between the way we designed the API and the way you are using it here. I have left a few comments about how I think it could be moved about to fit a little better, but would be interested to know if you think any changes to the API shape could be useful? Maybe the ability to use something like require not as a decorator?

In GitLab by @wtbarnes on Mar 8, 2020, 21:09
Commented on aiapy/response/channel.py line 74
changed this line in version 8 of the diff

In GitLab by @Cadair on Mar 5, 2020, 14:15
Commented on aiapy/response/channel.py line 22
Given your version is fixed throughout the rest of this file, why don't you generate the urls up here so you you have a version: (url, hash) map that you could *args into the decorator below.

In GitLab by @wtbarnes on Mar 8, 2020, 21:21
Thanks for your comments @Cadair. I've responded to your comments above. The restructuring of how the URLs and hashes are stored makes things a bit neater.
I like simplicity of the data manager. It would be nice to be able to use require outside of a decorator. Having to sepate out the _get_*_data functions into FUV and EUV feels a bit icky. Either that, or not have the check trigger until manager.get('...') is called.

In GitLab by @wtbarnes on Mar 8, 2020, 21:18
Commented on aiapy/response/channel.py line 70
The reason for these functions not returning the output of read_genx is that the instrument_file being passed into this function is potentially a string (e.g. if the user wants to use a file already on their machine). This means we can just call read_genx in one place.
I see why your suggestion is cleaner though. The logic of how to get the instrument data is a bit complicated as we accept three possible inputs for instrument_file:

None (in which case we defer to the data manager)
A path to a local instrument file
the output of read_genx

Maybe the whole thing needs a bit of a rethink in light of the addition of the data manager...

In GitLab by @wtbarnes on Mar 8, 2020, 21:09
added 1 commit
ad3633f2 - minor refactoring following feedback
Compare with previous version

In GitLab by @wtbarnes on Mar 8, 2020, 21:11
Commented on aiapy/response/channel.py line 74
I'm not aware of any particular mirrors we should add yet, but have made the URLs a list and added a comment to the effect that they should potentially be added in the future.

In GitLab by @wtbarnes on Mar 11, 2020, 12:40
I'm going to go ahead and merge this. The data manager provides a really nice way of making sure we are getting the files we expect to. We can always refactor the exact way we are using it later on down the road

In GitLab by @wtbarnes on Mar 11, 2020, 12:41
mentioned in commit bc79626547a8c1b5a37580b66b694cf603ebf3df

In GitLab by @wtbarnes on Mar 11, 2020, 12:41
merged

In GitLab by @wtbarnes on Mar 11, 2020, 12:41
resolved all threads

In GitLab by @wtbarnes on Mar 23, 2020, 13:30
mentioned in commit 2a7714f9ed9c605cb0ae21564cded9b71323aeb1


Incorrect syntax near the keyword 'WITH' BulkMergeAsync

I tried
var mergedRows = await connection.BulkMergeAsync(syncConsumers, batchSize: 1000, hints: SqlServerTableHints.NoLock, bulkCopyTimeout: 300);

This caused
System.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near the keyword 'WITH'.
Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
Incorrect syntax near the keyword 'AS'.

If I remove the hints then it worked. Note that I used the same hint for the BulkInsert command with success.
Is there an option to get the last generated SQL statement in such cases to further see what could be wrong?
BTW: Great lib!

Hey, thanks for reporting, we will look into this. When do you need the fix?

Not urgent; just wanted to report; I removed the hints for now as it's not crucial at the moment.

@stefandevo - I had investigated this one. The fix is very simple, we just have to switch the line  526 and line 527 from the SqlConnectionExtension.cs class.
Would you be able to provide a PR for this? Your help is highly appreciated - that matters and counts. TIA

Hi @mikependon no problem, but investigated the source and I see same for GetBulkUpdateSqlText, GetBulkDeleteSqlText. The Insert statement is the only one where the table alias is not place, and so the hints are added after the tableName.

Cool and thanks for sleuthing around ;) - see my Tweet here. Therefore, you do not need to worry the other methods IMO.
Also, the RepoDb.SqlServer method CreateMerge has the proper ordering, unlike the one in the BulkOperations.

The fixes for this is now available on the version >= RepoDb.SqlServer.BulkOperations v1.1.2-beta1. Please upgrade your copy by simply typing the command below in your PCM.
> Install-Package RepoDb.SqlServer.BulkOperations -version 1.1.2-beta1

Thank you for the PR in relation to this issue.

Closing this one now.


Interoperability with dual numbers

I want to obtain the Jacobian sparsity of a function whose body contains a ForwardDiff.derivative call. This leads to this error:
ERROR: MethodError: *(::SparseConnectivityTracer.GradientTracer{...}, ::ForwardDiff.Dual{...}) is ambiguous.

Possible fix, define
  *(::SparseConnectivityTracer.GradientTracer, ::ForwardDiff.Dual{Ty}) where Ty

Does this have a quick fix?
Edit: I worked around it, so you can close the issue if you don't find this important.

Maybe we're running into the issue described here: https://docs.julialang.org/en/v1/manual/methods/#Abstract-containers-and-element-types

If this is a desired feature, we should rework the function overloading utilities for 2-to-1 functions to accept an optional type argument.
Then you could add a package extension for ForwardDiff and call something like
eval(SCT.generate_code_2_to_1(:Base, Dual, ops_1_to_1))

However, I'm not sure we can make this work in combination with other package extensions.

Essentially the more general takeaway is that SCT doesn't play nice with other packages based on operator overloading

Maybe for operations between a Tracer and a number we can handle things better through promotion?

Essentially the more general takeaway is that SCT doesn't play nice with other packages based on operator overloading

More generally packages implementing 2-to-1 Base functions.

the solution was promotion. But the error wasn't a method error so idk.

I'm not sure how we would hit type promotion if the method call itself is ambiguous.
I'll open a draft PR and see how much complexity it adds.

Basic operators from Julia Base should now work with ForwardDiff.Dual on main.
I'll tag a release tomorrow.

After thinking about it for a day, I'm starting to think #200 shouldn't be released.
With #200, ForwardDiff.Dual are treated just like any other Real number, meaning that multiplication with a global tracer basically ignores the ForwardDiff.Dual. However, ForwardDiff.Dual could in theory contain SCT's tracers, thus returning wrong, non-conservative sparsity patterns.
While this is a general issue with Real number wrapper types, I feel like adding a ForwardDiff extension would signal full support for ForwardDiff.Dual. I therefore suggest reverting the changes in #200.

I agree with that, good catch.

#200 has been reverted. The newly tagged v0.6.6 release does not contain a ForwardDiff extension.


import flow type from index.js.flow file:

When I do import type MyType from '.' flow itself correctly assumes that file index.js.flow should be used, but eslint plugin searches for index.js first and only then for index.js.flow. For other filenames, this works normally. For my case, I should use import type Type from './index.js.flow', that is quite verbose. Otherwise, I get Unable to resolve path to module '.'  import/no-unresolved error

I don't know how much we are willing to support Flow. I started using it recently (and really like it), so I'm all for supporting it, especially as we already have some rules that handle Flow differently. I don't know how @benmosher feels about this though.
That said, this might be a better fit for a custom resolver (see https://github.com/tleunen/eslint-import-resolver-babel-module for instance).
Either way, it would be nice to have docs on how this gets resolved. cc @thejameskyle.

Would it not make sense to try .js.flow when you see import type since you already support that?

That sounds good to me. Are there any other files that you attempt to resolve it to when foo.js.flow is not found (except for foo.js? I just want to be clear on the resolver logic.

@jfmengels seems not for me. And don't forget about specific '.' or '/' case for 'index.js' - 'index.js.flow' case.

This could be handled by configuring the Node resolver with ['.js', '.js.flow'] as its extensions, see https://www.npmjs.com/package/eslint-import-resolver-node for config example.

Actually, maybe this would be best handled with a Flow-based shared config, like the existing React, Electron, etc. ones.

Is this issue still relevant?  If not let me know and I will open a new issue for my specific problem.
Related to example provided by OP, it is also not possible to import types that are exported by an npm module in a natural way.  For example, this works with flow but results in named error from eslint-plugin-import
import type {FormProps} from 'redux-form'

but this works and results in no eslint error
import type {FormProps} from 'redux-form/es/index.js.flow'

It's working, at least in 2.3.0. Though we've agreed to put all type definitions in types.js files everywhere.

Thanks for the update.
I don't think that is our particular issue - we don't have redux-form in our flow-typed directory.
I will open a new issue since it sounds like this one is for a different, resolved problem.


BugFix: make sure bg can scroll after modal is closed

looks like original implementation mistook the 2nd argument as boolean for "should the class be there or not" when in reality the 2nd argument is a boolean for "force".
https://developer.mozilla.org/en-US/docs/Web/API/DOMTokenList/toggle
also ensure bg-scroll gets re-enabled if p-modal gets unmounted without resetting showModal

The original implementation looks correct to me? If showModal is true then the force argument is true which forces the class to be added. If showModal is false then the false argument is false forcing the class to be removed. I've used that pattern dozens of times, pretty sure it's correct.

@pleek91 interesting, not what I expected by a param "force".
Do you think there is value in the the onBeforeUnmount piece?

@stackoverfloweth seems like a logical safeguard though I've never run into that scenario personally

@pleek91 I reverted the classList toggle piece, up to you if you wanna merge or close for the onBeforeUnmount piece. I ran into it because I had a v-if around my p-modal


fixed Windows CI

MSYS2 added kvazaar HEVC encoder, so added copy operation of kvazaar binaries to site_packages.

Amazing things happens, FreeBSD  maintainer of the libheif package just simple dropped libde265 replacing it with ffmpeg decoder and ffmpeg decoder can not decode half of test images.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274546#
Looks like we need to start building libheif ourselves again for FreeBSD during CI now, as default FreeBSD build is unusable.


Tags are not applied to plugin entities in the generated declarative config

Describe the bug
When the x-kong-plugin entity is used in a spec, when generating config using one of the entry point methods (for example generateFromString, the default tag or any tags provided are not applied to the generated declarative config of the plugin.
See example in the comment  below.
To Reproduce
Steps to reproduce the behavior:

In Insomnia Designer or the inso CLI, take a spec
Click Generate Config or run inso generate config

Expected behavior
The generated declarative config should tag the Services, Routes and plug-ins appropriately.
INS-175

Example spec:
openapi: 3.0.0
info:
  version: '1.5'
  title: LCE Order API
servers:
  - url: 'http://mockbin.org/request'
    description: mockbin
paths:
  '/v1/order/{id}':
    get:
      summary: Fetches an order
      x-kong-plugin-mocking:
        enabled: true
        config:
          api_specification_filename: orders.yaml
      x-kong-plugin-rate-limiting:
        enabled: true
        config:
          minute: 5
          limit_by: ip
          policy: local

Should generate the following config:
_format_version: "1.1"
services:
  - name: LCE_Order_API
    url: http://mockbin.org/request
    plugins: []
    routes:
      - tags:
          - OAS3_import
        name: LCE_Order_API-path-get
        methods:
          - GET
        paths:
          - /v1/order/(?<id>\S+)$
        strip_path: false
        plugins:
          - name: mocking
            config:
              api_specification_filename: orders.yaml
+           tags:
+	          - OAS3_import
          - name: rate-limiting
            config:
              minute: 5
              limit_by: ip
              policy: local
+           tags:
+             - OAS3_import
    tags:
      - OAS3_import
upstreams:
  - name: LCE_Order_API
    targets:
      - target: mockbin.org:80
    tags:
      - OAS3_import

With the tag value sourced from wherever the other tag values are sourced from - the various entry points in https://github.com/Kong/insomnia/blob/develop/packages/openapi-2-kong/src/index.js.

I'm a little confused about the examples provided for this issue. In the original post, the provided example shows a case where there is a tags array specified at the plugin object level, and it is not passed through to the plugin's declarative config. However, the "expected behavior" from the original post (as well as the example provided by @develohpanda) seem to refer to a different issue, where tags provided to the plugin's parent are not passed through to the plugin's output. Both of these appear to be issues, but I'm not sure which one should be fixed (maybe both :smile:).
I'll work a PR assuming that both items need to be addressed, but please let me know if it's actually one or the other.

Good eyes, and thanks for clarifying upfront 👀
The only way to provide tags (currently) is to send them as arguments to the entry point functions in index.js. Here is some documentation showing how tags behave currently.
The original issue report overlaps another feature request - to provide tags from the spec #2682 - which is not yet accepted.
I will remove the example from the original post and move it to the related issue. That will leave my comment with the example spec and the expected output, with no tags in the spec. In this example, the default OAS3_import tag, or any provided as an argument to, for example, generateFromString should be applied to the plugin.
Does that clear things up?

That clears it up, thank you!

Marking as closed as this appears to be resolved on 2021.6


Image Resizer should display dimensions of source image

The actual dimensions of the source image (and maybe some other information, like the size of the file) might influence which choice the user makes.

A new version of Image Resizer is being worked on: #1053 and there should be more information, just like you suggest.

Thank you


python38Packages.ntc-templates: 2.0.0 -> 2.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.ntc-templates is: "TextFSM templates for parsing show commands of network devices"
meta.homepage for python38Packages.ntc-templates is: "https://github.com/networktocode/ntc-templates"
meta.changelog for python38Packages.ntc-templates is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.2.0 with grep in /nix/store/5h8b509k90cmbka3xppfvhnq83v72cfr-python3.8-ntc-templates-2.2.0

found 2.2.0 in filename of file in /nix/store/5h8b509k90cmbka3xppfvhnq83v72cfr-python3.8-ntc-templates-2.2.0

directory tree listing: https://gist.github.com/d2eef49d486314661c21ef203c63ac22

du listing: https://gist.github.com/6ed8a2310a104e66af1be64d8753cacd

Rebuild report (if merged into master) (click to expand)

16 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.junos-eznc
python38Packages.ntc-templates
python39Packages.junos-eznc
python39Packages.ntc-templates

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5h8b509k90cmbka3xppfvhnq83v72cfr-python3.8-ntc-templates-2.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.ntc-templates https://github.com/r-ryantm/nixpkgs/archive/eba2235eca0bb5f97078c3ab078bc9ba77a471a1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5h8b509k90cmbka3xppfvhnq83v72cfr-python3.8-ntc-templates-2.2.0
ls -la /nix/store/5h8b509k90cmbka3xppfvhnq83v72cfr-python3.8-ntc-templates-2.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

python38Packages.junos-eznc
python38Packages.ntc-templates
python39Packages.junos-eznc
python39Packages.ntc-templates

Maintainer pings
cc @mweinelt for testing.

Result of nixpkgs-review pr 134807 at eba2235e run on aarch64-linux 1

4 packages built successfully:

python38Packages.junos-eznc
python38Packages.ntc-templates
python39Packages.junos-eznc
python39Packages.ntc-templates


Inconsistent results in Table 3 (SYNTHIA->Cityscapes)

Hello, thank for sharing the great work.
I find some inconsistent results in Table 3. Why the reported results of the CAG-UDA model in two mIoU metrics (13- and 16-class subsets) are different? Previous SOTA methods, like AdvEnt,  report the results on the 13-class subset based on that of 16-class subset. Could you please explain it?

from [arxiv](https://arxiv.org/abs/1910.13049)

Hi,
Thanks for your interest. 'IoU' means intersection over the union. When the class number decreases from 16 to 13, the redundant 3 classes should be ignored, leading to the denominator decrease during computing IoU. Thus the reported results on each class are inconsistent.

Hello, thank for sharing the great work.
I have a puzzled question for you. Is syhthia's warmup stage training conducted in 19 categories? Are 19 categories still used in the next three stages?
PS: can you share the model weight of Synthia dataset that you work in CAG? Thank you very much.


chore: disable clippy checks on fsevents

Description
Since we just vendor the fsevent module, I want to disable clippy from running on it. We could also fix up all of the lints, but that is slightly more invasive.
I have my rust-analyzer check command set to cargo clippy so I get all clippy warnings and for whatever reason, one of the clippy warnings in fsevent prevented compiler errors from showing up in my editor.
Testing Instructions
cargo clippy on turborepo-lib now doesn't hard fail.
Closes TURBO-1305

Closing now that #5891


Issue with Standard Fields

Hi Andrew,
I was wondering about how to do retrieve and deploy standard Fields using Metadata API. I read in Metadata API documentation , that standard fields can be retrieved as a "CustomField" Type. However, for Metadata API type "CustomField", I only get custom fields.
Thank you.

What code are you using?

Hi Andrew,
I'm using MetadataAPI wsdl and MetadataService class for *version 33. *
//fills the list of metadataTypes and gives default value to the chosen meta
public static List initialisation(string sessionId){
List MetaDataTypes=new List();
MetadataService2.MetadataPort service = createService(sessionId);
System.debug('initialisation retrieve utils');
MetadataService2.DescribeMetadataResult describeResult =
service.describeMetadata(33);
List  metadataTypeNames = new List();
for(MetadataService2.DescribeMetadataObject metadataObject :
describeResult.metadataObjects)
{      metadataTypeNames.add(metadataObject.xmlName);
system.debug('xxxxxx'+metadataObject.xmlName);
// Include child Metadata Types (such as CustomField,
ValidationRule etc..)
if(metadataObject.childXmlNames!=null)
for(String childXmlName : metadataObject.childXmlNames)
if(childXmlName!=null){
metadataTypeNames.add(childXmlName);
system.debug('cccccc'+ childXmlName);}
}
// Sort Metadata Types
metadataTypeNames.sort();
MetaDataTypes = new List<SelectOption>();
    for(String metadataTypeName : metadataTypeNames){

  MetaDataTypes.add(new SelectOption(metadataTypeName, metadataTypeName));
      }

return MetaDataTypes;
}
//list MetadataItems
public static List listMetadataItems(String
SessionId,String MetaDataType)
{
// List Metadata items for the selected Metadata Type
List MetaDataItems = new List();
MetadataService2.MetadataPort service = createService(SessionId);
List<MetadataService2.ListMetadataQuery> queries = new

List<MetadataService2.ListMetadataQuery>();
MetadataService2.ListMetadataQuery queryLayout = new
MetadataService2.ListMetadataQuery();
queryLayout.type_x = MetaDataType;
queries.add(queryLayout);}
MetadataService2.FileProperties[] fileProperties =
service.listMetadata(queries, 33);
// Sort
List<String> fullNames = new List<String>();
if(fileProperties!=null)
{
  for(MetadataService2.FileProperties fileProperty : fileProperties)
    fullNames.add(fileProperty.fullName);
  fullNames.sort();
  for(String fullName : fullNames)
    MetaDataItems.add(new ItemSelection(new

SelectOption(fullName,EncodingUtil.urlDecode(fullName,
'UTF-8')),false));
}
return MetaDataItems;
}
*Normally, for Metadata Type "CustomField", I suppose to get Standard
Fields as well (Metadata API documentation). *
I was also wondering if it's possible to deploy standard Objects and
Fields in other organizations.
Thank you.
2015-04-14 20:19 GMT+00:00 Andrew Fawcett<EMAIL_ADDRESS>
What code are you using?
—
Reply to this email directly or view it on GitHub
https://github.com/financialforcedev/apex-mdapi/issues/85#issuecomment-93048434
.

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

Why are you not using the MetadataService.cls from this repo?

Hi,
I'm using my own MetadataService.cls for version 33, in order to get new
version of Metadata Types list. However, I already tried to use
MetadataService.cls
from the repo, and I still can't retrieve or deploy Standard Fields.
Thank you.
2015-04-16 9:00 GMT+00:00 Andrew Fawcett<EMAIL_ADDRESS>
Why are you not using the MetadataService.cls from this repo?
—
Reply to this email directly or view it on GitHub
https://github.com/financialforcedev/apex-mdapi/issues/85#issuecomment-93683625
.

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

Ok can you include your updated code using the MetadataService.cls from the repo in a Gist or formatted as code in this issue so its easier for me to read. Also tell me clearly at what line (easier if you use a Gist link reference) your getting an error and what it is.

Hi Andrew,
Actually, I'm not getting any error. I'm using the same code from the repo,
but I still can't retrieve standard fields.
Thank you.
2015-04-19 10:30 GMT+00:00 Andrew Fawcett<EMAIL_ADDRESS>
Ok can you include your updated code using the MetadataService.cls from
the repo in a Gist or formatted as code in this issue so its easier for me
to read. Also tell me clearly at what line (easier if you use a Gist link
reference) your getting an error and what it is.
—
Reply to this email directly or view it on GitHub
https://github.com/financialforcedev/apex-mdapi/issues/85#issuecomment-94259942
.

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

Have you tried looking at my FAQ blog (linked from README) and review the component names of standard object custom fields via the Developer Workbench tool?

Yes, I did. My problem doesn't concern custom fields of standard objects,
it's actually about standard fields.
2015-05-05 13:11 GMT+00:00 Andrew Fawcett<EMAIL_ADDRESS>
Have you tried looking at my FAQ blog (linked from README) and review the
component names of standard object custom fields via the Developer
Workbench tool?
—
Reply to this email directly or view it on GitHub
https://github.com/financialforcedev/apex-mdapi/issues/85#issuecomment-99074308
.

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

Oh i see.... Sorry!
Looks like this might be a gap, see here...
https://developer.salesforce.com/forums?id=906F00000009CWNIA2
Also here....
http://www.salesforce.com/us/developer/docs/api_meta/Content/customfield.htm
"Only standard fields that you can customize are supported, that is, standard fields to which you can add help text or enable history tracking or Chatter feed tracking. Other standard fields aren't supported, including system fields (such as CreatedById or LastModifiedDate) and autonumber fields. All standard picklist fields are supported except for Lead.CampaignMemberStatus, Opportunity.ForecastCategoryName, and Order.Status."

I can't retrieve standard fields that can be  customized.
2015-05-05 13:24 GMT+00:00 Andrew Fawcett<EMAIL_ADDRESS>
Oh i see.... Sorry!
Looks like this might be a gap, see here...
https://developer.salesforce.com/forums?id=906F00000009CWNIA2
Also here....
http://www.salesforce.com/us/developer/docs/api_meta/Content/customfield.htm
"Only standard fields that you can customize are supported, that is,
standard fields to which you can add help text or enable history tracking
or Chatter feed tracking. Other standard fields aren't supported, including
system fields (such as CreatedById or LastModifiedDate) and autonumber
fields. All standard picklist fields are supported except for
Lead.CampaignMemberStatus, Opportunity.ForecastCategoryName, and
Order.Status."
—
Reply to this email directly or view it on GitHub
https://github.com/financialforcedev/apex-mdapi/issues/85#issuecomment-99076714
.

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

Normally, those standard fields that are supported, suppose to be retrieved
with custom fields
2015-05-05 13:28 GMT+00:00 ELALAOUI SARA<EMAIL_ADDRESS>
I can't retrieve standard fields that can be  customized.
2015-05-05 13:24 GMT+00:00 Andrew Fawcett<EMAIL_ADDRESS>
Oh i see.... Sorry!
Looks like this might be a gap, see here...
https://developer.salesforce.com/forums?id=906F00000009CWNIA2
Also here....
http://www.salesforce.com/us/developer/docs/api_meta/Content/customfield.htm
"Only standard fields that you can customize are supported, that is,
standard fields to which you can add help text or enable history tracking
or Chatter feed tracking. Other standard fields aren't supported, including
system fields (such as CreatedById or LastModifiedDate) and autonumber
fields. All standard picklist fields are supported except for
Lead.CampaignMemberStatus, Opportunity.ForecastCategoryName, and
Order.Status."
—
Reply to this email directly or view it on GitHub
https://github.com/financialforcedev/apex-mdapi/issues/85#issuecomment-99076714
.

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

In the MetadataServiceExamples.updatePicklist method it retrieves a custom field on the Lead standard object like so, are you saying this doesn't work for you?
    // Read Custom Field
    MetadataService.CustomField customField =
		(MetadataService.CustomField) service.readMetadata('CustomField',
			new String[] { 'Lead.picklist__c' }).getRecords()[0];

No. The problem is :  In the
MetadataRetrieveController.retrieveMetadataItem method it retrieves only
custom Fields when MetadataType="CustomField". Normally, it suppose to
retrieve supported standard fields,such as Account.Industry, as well.
Thanks.
2015-05-17 11:30 GMT+00:00 Andrew Fawcett<EMAIL_ADDRESS>
In the MetadataServiceExamples.updatePicklist method it retrieves a custom
field on the Lead standard object like so, are you saying this doesn't work
for you?
// Read Custom Field
MetadataService.CustomField customField =
    (MetadataService.CustomField) service.readMetadata('CustomField',
        new String[] { 'Lead.picklist__c' }).getRecords()[0];

—
Reply to this email directly or view it on GitHub
https://github.com/financialforcedev/apex-mdapi/issues/85#issuecomment-102785864
.

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

but it doesn't.
2015-05-18 15:20 GMT+00:00 ELALAOUI SARA<EMAIL_ADDRESS>
No. The problem is :  In the
MetadataRetrieveController.retrieveMetadataItem method it retrieves only
custom Fields when MetadataType="CustomField". Normally, it suppose to
retrieve supported standard fields,such as Account.Industry, as well.
Thanks.
2015-05-17 11:30 GMT+00:00 Andrew Fawcett<EMAIL_ADDRESS>
In the MetadataServiceExamples.updatePicklist method it retrieves a
custom field on the Lead standard object like so, are you saying this
doesn't work for you?
// Read Custom Field
MetadataService.CustomField customField =
    (MetadataService.CustomField) service.readMetadata('CustomField',
        new String[] { 'Lead.picklist__c' }).getRecords()[0];

—
Reply to this email directly or view it on GitHub
https://github.com/financialforcedev/apex-mdapi/issues/85#issuecomment-102785864
.

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

--
*Sara ELALAOUI *
Élève Ingénieur en Génie Informatique École Nationale des Sciences
Appliquées de Safi**Université Cadi Ayad - Maroc

Ok i see, so your using the sample MetadataRetrieveController class and page. Can you give me the steps to reproduce your problem with screenshots i think this will help me better understand.

Let me know if you still want me to follow up with you on this.

@SaraELA  hi, I'm facing the same issues, I'm trying to update the field values of a standard picklist field, but it is only working for custom fields
did you find any solution, please reply


Made pyshark optional.

Status
IN DEVELOPMENT
Description
Made pyshark and pyshark-legacy optional. They are now only checked when Icetea actually tries to instantiate the Wireshark object. This is a band-aid for https://github.com/ARMmbed/icetea/issues/101
Todos

[ ] Tests
[x] Documentation

Mbed OS stil uses Icetea 1.2.* release https://github.com/ARMmbed/mbed-os/blob/master/requirements.txt#L21
So this is not going to fix, unless 2.x is compatible.

I'll create a separate PR to go in that branch.

Pull Request Test Coverage Report for Build 1229

4 of 10 (40.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 77.076%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

icetea_lib/wireshark.py
4
6
66.67%

icetea_lib/TestBench/NetworkSniffer.py
0
4
0.0%

Totals

Change from base Build 1215:
-0.04%

Covered Lines:
6173

Relevant Lines:
8009

💛  - Coveralls

Pull Request Test Coverage Report for Build 1228

4 of 10 (40.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 77.076%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

icetea_lib/wireshark.py
4
6
66.67%

icetea_lib/TestBench/NetworkSniffer.py
0
4
0.0%

Totals

Change from base Build 1215:
-0.04%

Covered Lines:
6173

Relevant Lines:
8009

💛  - Coveralls

Pull Request Test Coverage Report for Build 1230

4 of 10 (40.0%)  changed or added relevant lines in 2 files are covered.
25 unchanged lines in 11 files lost coverage.
Overall coverage decreased (-0.1%) to 76.979%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

icetea_lib/wireshark.py
4
6
66.67%

icetea_lib/TestBench/NetworkSniffer.py
0
4
0.0%

Files with Coverage Reduction
New Missed Lines
%

icetea_lib/wireshark.py
1
67.3%

icetea_lib/TestSuite/TestcaseContainer.py
1
81.61%

icetea_lib/tools/GitTool.py
1
74.7%

icetea_lib/TestSuite/TestSuite.py
1
79.46%

icetea_lib/ResultList.py
1
82.03%

icetea_lib/TestSuite/TestcaseFilter.py
1
90.91%

icetea_lib/Searcher.py
2
93.62%

icetea_lib/AllocationContext.py
2
56.17%

icetea_lib/ResourceProvider/ResourceProvider.py
3
85.37%

icetea_lib/LogManager.py
5
78.24%

Totals

Change from base Build 1215:
-0.1%

Covered Lines:
6166

Relevant Lines:
8010

💛  - Coveralls


Update codemirror

Currently stuck at 5.17, could update to 5.42 if we want. Involves a build process is all (yecch).

fixed in 1eb691fa8627543060f55f10f5861549962267da


Is normal this spam??

Start in the lane 1516 when the centepide spawn
LogOutput.log

Ah, that's just some debug logging that I had forgotten to remove. I actually thought I had released a version with this removed, but I guess not, so let me do that now.

Thanks for answering :)

Pushed version 1.2.1 to remove the debug spam.


handle cases when subscript inserted / removed but not at end

For some types of subscript symbols (e.g. lists or numpy arrays), we need to shift other symbols if something is inserted / deleted in the middle. Maybe other types as well, but handling at least these properly would be a good start.

Update: this is implemented for lists, and numpy doesn't really have much support for in-place insertion / deletion, I think we can mark this issue as solved.


Improve accessibility with ARIA

Work in progress

Closed, because I implemented this feature.
I'll commit this feature soon.


Set "TreatWarningsAsErrors" before NuGet restore

Ensures our build stays clean of NuGet warnings

@ryanbrandenburg,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Merging since this passes locally.


Minor fix in Inference class docstring to avoid warning when building docs

Codecov Report

Merging #122 into master will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #122      +/-   ##
==========================================
- Coverage   95.88%   95.79%   -0.09%
==========================================
  Files          34       34
  Lines        1457     1475      +18
==========================================
+ Hits         1397     1413      +16
- Misses         60       62       +2

Impacted Files
Coverage Δ

scvi/inference/variational_inference.py
93.82% <ø> (ø)
:arrow_up:

scvi/inference/inference.py
95.55% <ø> (-0.55%)
:arrow_down:

scvi/inference/classifier_inference.py
96.42% <ø> (ø)
:arrow_up:

scvi/metrics/early_stopping.py
84.09% <0%> (-2.28%)
:arrow_down:

scvi/metrics/adapt_encoder.py
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


add new Card Images for Giant Snowball and Royal Hogs

add new Card Images for Giant Snowball and Royal Hogs

Hey! Those look great, could you rename to giant-snowball and royal-hogs? To keep the naming convention.

oops! my bad, will do in a minute.


Added forgotten changeset for Cypress-Electron-interactive-mode change

What Changed

I forgot to add a changelog to #72, so this PR is just to make sure those changes get released.

Closing this since #72 actually introduced a regression. Since it didn't publish to npm, I'll do a direct revert and this PR will be unnecessary.


Moving some action tests to modules

flyby adding test for invoking apply for an action accepting an rvalue

retest

Note, this is not ready by a long shot. More changes are needed.

This is ready for review now

retest lsu

The LSU tests are fine now as well, merging...


chore: add CODEOWNERS

Summary
Setup CODEOWNERS for easier reviewer assignments.
@hardfist Can you assign these to the correct person, you can push to this branch.
Related issue (if exists)

Types of changes

[ ] Docs change / Dependency upgrade
[ ] Bug fix
[x] New feature / Improvement
[ ] Refactoring
[ ] Breaking change

Checklist

[ ] I have added changeset via pnpm run changeset.
[ ] I have added tests to cover my changes.

@web-infra-dev/rspack

@web-infra-dev/rspack

@web-infra-dev/rspack Can you double check and assign the node packages as well?

@hardfist can you double check?


Support apps with hypens in their name (i.e. dry-test)

I tried generating a new app today using this command:
dry-web-roda dry-test

The app generated fine, but when I went to run this app with rackup, I saw this error:
/Users/ryanbigg/code/playground/dry-test/system/boot.rb:4:in `require_relative': /Users/ryanbigg/code/playground/dry-test/system/dry_test/container.rb:4: syntax error, unexpected '-' (SyntaxError)
module Dry-test

It appears that the module name for the application here is not correctly constantized. I couldn't find one Inflecto method which handles this case, so I'm using a combo of underscoreize + camelize methods to produce the right output DryTest.

Hey @radar! I'm excited to see you're giving this a try! Your change looks good to me, I'll merge it in as soon as I can figure out what went wrong with that build.

(The problem is that we only create a single named database in our Travis setup). I'll pull this in when I next have an hour or so to make that more flexible - next week sometime, if not earlier.

Thanks @radar, I incorporated your fix and pushed it up in a new gem release :)


Canonical visualization layer fix for missing data layer

The linked issue contains the steps to reproduce.
Changes might impact everything related to layer sorting (needed on visualization creation and layer addition, among others) and table dependency registration (the logic that shows the modal when you try do delete a dataset with a visualization, warning about related maps).
The problem appeared with a user that has Google Maps as default basemap. That basemap doesn't have labels on top. There's an iteration through layers that reloads the map layers in order to be sure that the map contains the actual layers so we can compute the order. As a side effect, that reloading keeps map.layers up-to-date for a next saving. As a map without layers on top doesn't have a layer after the data layer, the data layer addition wasn't refreshed and wasn't saved. The fix refreshes map just after layer addition, keeping it up-to-date as early as possible.

Did some testing including:

Imports
Duplication
Adding/removing/moving layers
Checking table dependencies at each step

Everything seems to work alright. This 🚀 is ready for departure! 👏