Change K8s CPU Memory Requirement form Cores to VCPU

.Change CPU Memory Requirement from Cores to VCPU
In the Kubernetes Compute Requirements section.  The CPU and Memory requirement should be changed from cores to VCPU
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c2db390f-ad4b-8b27-0794-76d7ca046419
Version Independent ID: 4c9d937f-69f1-e9fd-2118-0fa8b82510d0
Content: Overview of Kubernetes cluster on Azure Stack Edge Pro GPU, Pro R, Mini R device
Content Source: articles/databox-online/azure-stack-edge-gpu-kubernetes-overview.md
Service: databox
Sub-service: edge
GitHub Login: @alkohli
Microsoft Alias: alkohli

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

@malcatraz
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly

@alkohli
Can you please check and add your comments on this doc update request as applicable.


Implement named structs

Simple struct support should be functioning.
e.g.
struct MyDataType(x,y)

def test(obj):
    print(obj.x) # "A string"
    print(obj.y) # 17
end

def main():
    obj = MyDataType("A string", 17)
    test(obj)
end

Out of scope:
Deconstruction by pattern match:
MyDataType(x,y) = obj

Note:
This can be made superfluous by making a small change to dict notation:
obj = {x: "A string", y: 17}
print(obj.x)
print(obj.y)

# can be wrapped to be explicit about dict contents
def MyDataType(x, y):
    return {x: x, y: y}
end

obj = MyDataType("A string", 17)
print(obj.x)
print(obj.y)

Also, struct MyDataType(x) can be treated as syntactic sugar for def MyDataType(x) return {x: x} end

This now works:
obj = {x: "A string", y: 17}
print(obj.x)
print(obj.y)

Some more work needs to be done (returning dict loses type information), but struct is being put on ice for the moment.


greenclip.history lost if storage has no space left

Hello,
the history file, in my case ~/.cache/greenclip.history, seems to be overwritten with nothing if the storage device holding the file runs out of space.
Latest version of greenclip (4.2) is installed on Debian 9.

Hello,
Well sadly, you are not supposed to run out of disk space. A lot of programs will start to misbehave or corrupt their data if you hit  the wall at the end of your disk.
Greenclip is not going to manage this case, as it would require too much complexity to add in the tool

Aaah yep of course, that makes sense. I know this and I didn't even think of it!
I understand. Thanks for the response!


Mismatch of  RingNet output and FLAME parameter

Greetings.
RingNet output a 159-dimensional vector. which contains 100-dimensional shape parameters, 50-dimension expression parameter and 6-dimensional pose parameter.
However, in Flame, the shape parameter is in shape (300,), expression parameter is in shape (100,), pose parameter is in shape (12,)
https://github.com/Rubikplayer/flame-fitting/blob/d3c4d3d4284d9ba8d36be0b224de7ce133301ebc/hello_world.py#L25-L27
If you can give some explanation, I'd be most grateful.
Thanks in advance!

RingNet outputs a subset of the FLAME parameters. These parameters are the first 100 shape parameters, first 50 expression parameters, and the pose parameters for the global rotation (FLAME pose parameters 1-3) and the jaw rotation (FLAME pose parameters 7-9). Does this answer your question?

RingNet outputs a subset of the FLAME parameters. These parameters are the first 100 shape parameters, first 50 expression parameters, and the pose parameters for the global rotation (FLAME pose parameters 1-3) and the jaw rotation (FLAME pose parameters 7-9). Does this answer your question?

Thanks for your kindly reply :)
Still I am curious on two points. 1. In order to use RingNet output on FLAME, the rest paramters should be padded with zeros? 2. Why RingNet output subset instead of full set of parameters?
Looking forward for your reply.

Yes, you just set the remaining parameters to zero. First, 100 shape and 50 expression parameters are sufficient to explain most of the data variation. Second, we minimize a landmark loss when training RingNet, and these landmarks only provide sparse supervision. Using fewer parameters makes it then easier to train.

I see.
Just wondering if this few parameters is enough for RingNet, why FLAME should use that many parameters?

FLAME is previously also used to register high-resolution scans. Explaining detailed 3D scans provide you the information you need to optimize for all parameters. Landmarks only sparsely sample the face and a significant amount of information about the face shape is lost when using landmarks only. Hence more parameters will not provide you better shape results. The sparse supervision provided by the landmarks is the main limiting factor, not the number of FLAME parameters.

FLAME is previously also used to register high-resolution scans. Explaining detailed 3D scans provide you the information you need to optimize for all parameters. Landmarks only sparsely sample the face and a significant amount of information about the face shape is lost when using landmarks only. Hence more parameters will not provide you better shape results. The sparse supervision provided by the landmarks is the main limiting factor, not the number of FLAME parameters.

Thanks a lot!

Hi, thanks for the great work. I am wondering if there is a way to add the expression parameters into the visualize function in demo.py. I want to observe the coherence of an expression sequence showed in Flame model, but I don't know how to obtain the 2D projection of Flame model, could you do me a favor on this?


(HAL-27) LOCKEDTOKEN INCOMPLETE TOKEN RELEASE

(HAL-27) LOCKEDTOKEN INCOMPLETE TOKEN RELEASE
Auditor: Halborn
Severity: Medium
Description
An improper implementation of the lock removal process within the release function's loop of LockedToken.sol prevents users from fully releasing their eligible tokens in a single transaction, leading to potential confusion, increased costs.
This behavior occurs because:
When a lock is processed and removed, it's replaced by the last lock in the array.
The loop then moves to the next index, effectively skipping the lock that was just swapped into the current position.
This process repeats, causing approximately half of the locks to be skipped.
The lock is swapped to index i, which was already processed, and the next iteration will be on i+1, skipping the lock that was swapped in the line 103:

BVSS
AO:A/AC:L/AX:L/R:N/S:U/C:N/A:N/I:N/D:N/Y:M (5.0)

Recommendation
It is recommended to iterate the unlocks in reverse order, ensuring that swapping and popping don't affect upcoming iterations.

This was resolved a while ago. Let me find the PR...

#337


macho_file: Refactor MachOFile#sections.

Takes advantage of a case to determine the correct class.
cc @UniqMartin

Closing this; it'll be part of a general refactoring PR.

:+1: Heading over to the general refactoring PR …


Can't see dates in markdown/ event area

Jonathan,
I can't see the date/ calendar in the events area on symphony.  This has been like this for a while, but I'm hoping you can fix it so I don't break the website again.
Thank you!

@atheycreek/support Fixed.


Release 0.12.2

Signed-off-by: Sylvain Corlay<EMAIL_ADDRESS>Describe your changes
Releasing 0.12.2

@jasongrout @kaiayoung this is the 0.12.2 release PR.
It seems that I cannot merge it because of the requirement for a review with the new configuration.
Could someone please merge this before anything else gets in?


bug: Fix code scanning alert - Use of a broken or weak cryptographic hashing algorithm on sensitive data

Tracking issue for:

[x] https://github.com/ToolDelta/ToolDelta/security/code-scanning/1

无法解决的，这是fbapi要求的

This issue should closed as not planned


TLS version fallback deprecation post should include instructions for administrators

In https://developers.google.com/web/updates/2016/03/chrome-50-deprecations#remove-insecure-tls-version-fallback, the TLS version fallback section ideally would include a sentence or two for administrators. Something generic like: "Administrators should ensure their server software is up-to-date." should do. In the Intent email I also added "If this is still unresolved, reach out to the software vendor". I don't know how useful that is.
(This is caused by bugs in, usually, old server software. I'm not aware of any concrete bugs remaining, apart from one Windows issue fixed years ago. But there might be some I'm not aware of.)

Can you give me a revised paragraph of what you'd like the "Remove Insecure TLS Version Fallback" to be and I'll make the changes, I don't know enough about this to comment on any of the topics you are raising.
Are there any steps to diagnose is this is the issue? I.e. error messages in the DevTools security panel or something that might get caught in a google search?

Can you give me a revised paragraph

The only thing you need to add is that affected sites should get this bug fixed. There really anything more specific. This is fundamentally a server bug. Whatever software or appliance they're using for TLS is defective and never implemented the spec correctly. Something simple like this at the end should do:
Affects sites will fail to connect with ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION. Administrators should ensure their server software is up-to-date. If still unresolved, contact the server software vendor to see if a fix is available.

Are there any steps to diagnose is this is the issue?

If the connection fails with ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION

Ping

@gauntface I will add this in now.


dev: tox fails with matplotlib on Windows

I am not able to run tests with tox on Windows which import anything from ixdat, since they crash when matplotlib is imported. Even the trivial test
def test_blank_measurement():

    from ixdat.measurements import Measurement

fails in tox.
It does not matter whether I call tox from Anaconda Prompt or from git bash.
The key line of the error message is
AttributeError: module 'sip' has no attribute 'setapi'
The full error message (from Anaconda Prompt) is below.
The only constructive answer I could find googling this was https://stackoverflow.com/questions/64291087/matplotlib-module-sip-has-no-attribute-setapi, which suggests limiting matplotlib version to =3.2. However, I tried this and it didn't work.
Importing matplotlib is of course no problem normally. It seems to be a dependency issue - that tox installs the wrong sip and/or matplotlib. In the Anaconda prompt, they are both in the Anaconda3 site packages:
(base) PS C:\Users\scott\git\ixdat> python
Python 3.8.5 (default, Sep  3 2020, 21:29:08) [MSC v.1916 64 bit (AMD64)] :: Anaconda, Inc. on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import matplotlib
>>> matplotlib.__file__
'C:\\ProgramData\\Anaconda3\\lib\\site-packages\\matplotlib\\__init__.py'
>>> import sip
>>> sip.__file__
'C:\\ProgramData\\Anaconda3\\lib\\site-packages\\sip.pyd'

Googling "tox fails with matplotlib" surprisingly did not lead me to anything useful.

Another strange result is that, even with that requirement, sip does not behave as expected when tox is running.
In anaconda prompt:
$ python

>>> import sip
>>> sip.SIP_VERSION
267021
>>>

But, the test
def test_sip_import():

    import sip
    print(f"sip version = {sip.SIP_VERSION}")

fails when running tox with:
E       AttributeError: module 'sip' has no attribute 'SIP_VERSION'
So I'm pulling out hairs.
I found that this is an unsolved error for at least one other user: https://github.com/skelouse/mlframe/issues/2

Looks very unpleasant. I would suggest to disable the commit hook for now.
I will see if I can reproduce at home.
Only thoughts is that it would be nice with a print of the imported sip module, to see what it identifies it self as and where it is imported from.
The tests probably don't need matplotlib for anything else than to be imported, so a possible (although naughty) workaround would be to inject a Mock object into the cache of imported modules under the name matplotlib in the test setup... but I'm not sure that would work.

Update:
I can't reproduce it either (I guess this is both good and bad news)
I'm on another computer (Spectro Inlets DELL). It is running Anaconda python 3.7 as the default python. The problem was on a computer (Imperial College HP Elitebook) running Anaconda python 3.8 as the default python. Both computers are Windows 10. However, tox passes in python 3.8 as well on the second computer!
SIDE NOTE:
I've had a bit of trouble getting tox to identify the py38 interpreter. I created an environment called py38 with python=3.8 installed in Anaconda. Its python executable is C:\Users\scott\Anaconda3\envs\py38\python.exe. I added
both C:\Users\scott\Anaconda3\envs\py38\ and C:\Users\scott\Anaconda3\envs\py38\Scripts to the system PATH variable, which should be enough. But still when I run tox in git bash, or Anaconda Prompt (base), it says InterpreterNotFound except for py37. Only if I run from Anaconda Prompt (py38) can it find both interpreters:
$ tox
...
___________________________________ summary ___________________________________
ERROR:  py36: InterpreterNotFound: python3.6
  py37: commands succeeded
  py38: commands succeeded
ERROR:  py39: InterpreterNotFound: python3.9
ERROR:  pypy3: InterpreterNotFound: pypy3
  flake8: commands succeeded

END SIDE NOTE.
I can also confirm that tox works now when called by the pre-push hook. 😄  . So I have at least one system from which I can run all the tools!
I wonder if the difference has to do with the tox installation or its environment management? I do remember you helped me set up tox on the computer where it works. I probably pip installed it on the other computer through Anaconda Prompt, but will check when in tomorrow. For my reference:
(base) C:\Users\scott\git\ixdat>conda list tox
# packages in environment at C:\Users\scott\Anaconda3:
#
# Name                    Version                   Build  Channel
tox                       3.15.2                   pypi_0    pypi

(base) C:\Users\scott\git\ixdat>conda list virtualenv
# packages in environment at C:\Users\scott\Anaconda3:
#
# Name                    Version                   Build  Channel
virtualenv                20.4.7                   pypi_0    pypi

(base) C:\Users\scott\git\ixdat>conda list pip
# packages in environment at C:\Users\scott\Anaconda3:
#
# Name                    Version                   Build  Channel
pip                       21.0.1                   pypi_0    pypi

Anyway, agree, if I can't solve it I will just disable git hooks on the problematic computer.

About terminal output, that's a good point. Because both pytest and tox captures output, that might be difficult. Rather that punching a whole through that, you can just write to file conveniently with print:
(ixdat) PS C:\venv\ixdat\ixdat> python
Python 3.9.1 (tags/v3.9.1:1e5d33e, Dec  7 2020, 17:08:21) [MSC v.1927 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> f = open("output.txt", "w")
>>> from functools import partial
>>> print = partial(print, file=f)
>>> print("hello")
>>> print("world")
>>> f.close()
>>> exit()
(ixdat) PS C:\venv\ixdat\ixdat> cat .\output.txt
hello
world

As for the real problem, I'm wondering if anaconda is enough of a exotic python env that we are going to run into more problems with tox. What happens on the same machine, if you cut tox out of the equation, by changing the git push hook (in .git/hooks/pre-push to run:
..... Lot's of comments at the start
#
# This script should be copied or better yet sym-linked into .git/hooks/

invoke checks
exit $?

instead of
..... Lot's of comments at the start
#
# This script should be copied or better yet sym-linked into .git/hooks/

invoke tox --single
exit $?

The command in itself seems to work well enough for the checks (although maybe it needs a "called_from_git" option that modifies the output a little to make it easier to tell the output of the checks from that from git. What we would loose by this is that checks don't get run in separate environments and in parallel, but maybe it is better if tox and anaconda is a bad combo. And we can still keep the tox config to run the tests in as many python environments as possible on the machines where it works.

This is solved!
I needed to upgrade pip, and make sure pip was installed by pip and not by conda or something else.
(base) PS C:\windows\system32> conda list pip
      # packages in environment at C:\ProgramData\Anaconda3:
      #
      # Name                    Version                   Build  Channel
      pip                       20.2.4           py38haa95532_0

(base) PS C:\windows\system32> pip install --upgrade pip
      Collecting pip
        Using cached pip-21.1.3-py3-none-any.whl (1.5 MB)
      Installing collected packages: pip
        Attempting uninstall: pip
          Found existing installation: pip 20.2.4
          Uninstalling pip-20.2.4:
            Successfully uninstalled pip-20.2.4

(base) PS C:\windows\system32> conda list pip
      # packages in environment at C:\ProgramData\Anaconda3:
      #
      # Name                    Version                   Build  Channel
      pip                       21.1.3                   pypi_0    pypi.

After that, tox works in both git bash and Anaconda prompt. It requres a --recreate option the first time to force it to reinstall the py38 environment using the correct pip.
$ tox --recreate
      ...
      ___________________________________ summary ___________________________________
      ERROR:  py36: InterpreterNotFound: python3.6
      ERROR:  py37: InterpreterNotFound: python3.7
        py38: commands succeeded
      ERROR:  py39: InterpreterNotFound: python3.9
      ERROR:  pypy3: InterpreterNotFound: pypy3
      ERROR:   flake8: commands failed


Patch phpdoc 1

Added patchList to ResourceInterface
Added setters and getters for Identity and InputFilter to ResourceInterface
Some other small phpdocs improvements...

Marked as BC break, and scheduled for 2.0.0, due to interface additions.

This repository has been closed and moved to laminas-api-tools/api-tools-rest; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-rest/issues/3.

This repository has been moved to laminas-api-tools/api-tools-rest. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

Squash all commits in your branch (git rebase -i origin/{branch})
Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
Run the laminas/laminas-migration tool on the code.
Clone laminas-api-tools/api-tools-rest to another directory.
Copy the files from the second bullet point to the clone of laminas-api-tools/api-tools-rest.
In your clone of laminas-api-tools/api-tools-rest, commit the files, push to your fork, and open the new PR.
We will be providing tooling via laminas/laminas-migration soon to help  automate the process.


Add document how to integrate a custom Job with Kueue

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Add a document in website which shows how to integrate a custom job with Kueue.
Which issue(s) this PR fixes:

Fixes #777
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

Could you also do #1007 as a preparation for this?

/close
because it's duped


Inquiry About PixLevelModule Usage in LViT Network Structure

Dear Zihan,
I hope this message finds you well. As I delve deeper into the LViT model, I have encountered a specific aspect of the network structure that I am eager to understand better with your guidance.
In my thorough examination of the LViT's network architecture, I observed that the PixLevelModule, as defined in the code, appears not to be used in the forward pass. To better illustrate my point, I am referencing the following sections of the code from your GitHub repository:

This observation has led to some confusion about its role in the overall network structure as described in your paper. Could you kindly provide clarification on this and, if possible, share the correct code that reflects the implementation used in the paper?
Your insights are invaluable to my understanding and proper implementation of the LViT model. I greatly appreciate your time and the support you've provided thus far.
Thank you once again for your assistance.
Best regards,
Pengyu

There is some redundancy in the code, but you can use it freely. And the code has been the proper implementation of the LViT model.


proposal: Go 2: errors: return if

Amazing news. I no longer have a broken keyboard.

In celebration, I've made yet another error proposal.
Fundamentals
Contrary to popular belief, using words that make you sound smart isn't what makes a good error proposal. It's having fundamentals. Those aren't defined by silly language concepts, but by looking at the code. panic, recover, _ are mostly used to handle errors, but they can also handle non-errors too. That's because errors are values.

In short, a valid errors srorre' proposal is one that follows these rules.
Proposal
The Form
Would you consider yourself a novice, intermediate, or experienced Go programmer? What other languages do you have experience with?
https://switchupcb.com/projects
Has this idea, or one like it, been proposed before?
I couldn't find a return if using search nor @seankhliao's website.
Is this change backward compatible? Does this affect error handling?

The Explanation
So the issue with proposals like https://github.com/golang/go/issues/37141 and https://github.com/golang/go/issues/52416 is that they focus too much on the errors. We go on and on about technical nonsense, only to end up with: "This proposal would be good if it was limited to errors." Once you hear those words, it's time to buy the casket. Some people want new keywords, some people don't. Others are if err != nil maxis, but they have a point: Why add a new mechanism for errors when it was right in front of us the whole time?
You could take pass and rename it to rinn (return if not nil), allow it to be used on values and functions, then call it a day. Or... we could just figure out how to make using the if statement better?
JavaScript and Ruby have return if. Other languages have ternaries. We are not the same.
The Code
func bezo(baller, dollers string) error {
    bucko, err := strconv.Atoi(baller)
    return if err != nil { err }
    bucks, _ := strconv.Atoi(dollers)
    fmt.Println("$:", bucko + bucks)

    ballin, err := isBaller(bucko + bucks,<PHONE_NUMBER>)
    return if err != nil { fmt.Errorf("error: balled too hard\n%w", err) }
    if ballin {
        err := MakeMackenzieHappy()
        return if err != nil { err }
    }
    return nil
}

Alternative Implementation
func bezo(baller, dollers string) error {
    bucko, err := strconv.Atoi(baller)
    return err if err != nil
    bucks, _ := strconv.Atoi(dollers)
    fmt.Println("$:", bucko + bucks)
    ...

Alternatively
func bezo(baller, dollers string) error {
    bucko, err := strconv.Atoi(baller)
    if err != nil { return err } // allow one-line
    bucks, _ := strconv.Atoi(dollers)
    fmt.Println("$:", bucko + bucks)
    ...

The Theme Song
I will travel across the land, searching far and wide.
To teach Go devs to understand, the power that's inside.
(Go Errors, Gotta Catch Em All) It's you and me
I know it's my destiny
(Go Errors) Oh, you're my best friend
In programs we must defend
(Go Errors, Gotta Catch Em All) If err not nil
A return will pull us through
You teach me and I'll teach you
Go Errors! (Gotta Catch 'em all) Gotta Catch 'em all (Go Errors!)

Testimonials

I love using if statements on a nice summer evening. Using them with return would be even better!
— @sirkon

Security consultant here.
The fact that Golang has no return if is a huge thing. I've read countless amount of code that abused return if statements (unfortunately developers think they have to use  return if all the time if they are available) and is probably completely insecure for the simple reason that very few people manage to audit/understand the code. If  return if could only be used when necessary, yes, but there are no technical ways to enforce this.
What I'm saying is that in my years of security consulting, Golang codebases have always been the clearest ones to read and have always been the most secure ones. I feel like a lot of the negative perspectives are given from the writing point of view, but the reading perspective is clearly a huge win for Golang.
— Security Consultant

Voting
Democracy basically means... government... by the people... of the people... for the people... but the people are... r  ust zealots?? macros??? The only macros I want are macronutrients from Go Cereal on a summer morning.

Look.  I know how a lot of you are. You have some idea in your head so you downvote everyone else's without thinking. That's the problem. It's not your idea. Yet no one will remember these posts. No one will remember who solved Go errors. As long as you are concerned, your idea is ours.
Thanks :D
Now go submit your idea because we need more ideas. Go is the source of the next web revolution.
To the inevitable person who is supposed to be all serious and logical, but then cries about the delivery of this post: You are not special. We get paid to press buttons. It's really not that complicated.

Potential Supporters: @hummerd, @jdmaguire, @griggsca91, @SealOfTime, @dfreilich, @mccolljr, @komuw, @gweithio, @rw-access, @kalverra, @Splizard, @elnardu, @schrej, @schwrzstrbn, @4ad, @efronlicht, @pierrec, @codemicro, @pacuna, @Drache93, @oz, @maja42
Shoutout: @ianlancetaylor (mega baller alert)
and maybe @griesemer when asts can handle comment manipulation.

Please don't mention me out of nowhere.

I have no idea what this proposal is for but I love it nonetheless.

I don't understand, why I have been mentioned, but nonetheless I wouldn't support this proposal at this stage.
To begin with at this moment this proposal is lacking example of code for function with multiple return values.
Moreover, this proposal suggests a syntactic synonym of existing and wide-spread go idiom
if err != nil {
    return fmt.Errorf("wrapped: %w", err)
}

Alternatively, it just suggests adding another way to write this down to be allowed in  go fmt.
In my opinion, this would only decrease the code readability by introducing another way to do just one thing, which from my experience leads to incoherent codebase.

Single line if ... { } is #33113 #27135
This looks like #27794 #32860 with the order switched
Closing as dup

And, as Ian already mentioned before, please follow the code of conduct. The majority of your post is completely unrelated to the proposal at hand, the overall tone is distracting, and you're pinging two dozen people at once - none of which are a good start for a productive proposal discussion.


fix Go SDK codegen for engagementfabric

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

Automation for azure-sdk-for-js

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

Automation for azure-sdk-for-node

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java


Disable scrape metrics by default

Description
When using the prometheus or istio feature of the MetricPipeline, for every source typical scrape metrics are getting produced, concrete:

scrape_duration_seconds
scrape_samples_scraped
scrape_samples_post_metric_relabeling
scrape_series_added
up

These are rather technical metrics very useful for debugging a problem. However, they are also causing data for a price, so they should be configurable and probably disabled by default.
Criterias

As a user I will not push the mentioned metrics by default
There is an API either on pipeline level or module level to enable the metrics, so that I can debug problems

Reasons

Attachments

Release Notes

Metric gateway filter-out the diagnostic metrics by default for input type istio and prometheus when they enabled
When diagnostic metrics are required, collection of diagnostic metrics have to be enabled explicitly per input type, like :

apiVersion: telemetry.kyma-project.io/v1alpha1
kind: MetricPipeline
metadata:
  name: backend
spec:
  input:
    prometheus:
      enabled: true
      diagnosticMetrics:
        enabled: true
  output:
    otlp:
      endpoint:
        value: https://backend.example.com:4317


fix: Wallet Balance

fiat balance display
currency formatting
added tests for WalletBalance
added test coverage scripts
bumped haveno-ts to v0.0.5

Merged via CLI


GLB import / export has issues

I am experiencing multiple problems with the UnityGLTF component. It is very unfortunate, as we would benefit greatly from having proper GLTF support in our project.
One of the major issues is importing / exporting to GLB. Importing a GLB from Sketchfab, ie, works just fine, and it imports impressive models with no issues. However, creating a few 3D objects in Unity and exporting and then reimporting does reveal issues!
Try this;

Create a cube on root. Create a sub object for this cube, say a cylinder. And again, for this cylinder, add a sub object capsule.
You have this object now:

Now; export to GLB using 'GLTF -> ExportGLB Selected'

Import it back in. Several problems occur:
a. Imported object looks like this:

The capsule node is lost, but the capsule mesh has merged with the cylinder mesh, and is placed on the cylinder node. This completely messes up the structure of objects.
b. Additionally, most but not all times I get this exception thrown:

(this example is from a different different test object)

Anyone else experience this?

Would be great if you try out the dev branch / this PR, which greatly improves export:

https://github.com/KhronosGroup/UnityGLTF/pull/644

Thanks!


Client won't load if there wouldn't be corresponding hash in config

Client requires config to have an entry called client or it will fail

added empty config.json in parent image to prevent such errors


feature/50825 - Wishlist module

Ad. 1. Done
Ad. 2. If line with classes do not exceed 80 chars then indentations are not needed.
Ad. 3. Fixed :slightly_smiling_face:


Disable save bar if no action is available

I want to merge this change because it hides save bar if no action is available.
PR intended to be tested with API branch: master
Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Translated strings are extracted.
[ ] Number of API calls is optimized.
[ ] The changes are tested.
[ ] Data-test are added for new elements.
[ ] Type definitions are up to date.
[ ] Changes are mentioned in the changelog.

Test environment config

API_URI=https://master.staging.saleor.rocks/graphql/

Task linked: SALEOR-1058 Save bar should appear only when there is an active action


RTC abstraction layer

create a class which configures the real time clock (RTC) and provides utility methods for setting/retrieving the time

solved in b89a9c9eb5fadcca03c706cb1c5f3e3a98926e7d


casting complex type is order dependent when docs say different

The cast docs mention:

If val is a record (or if any of its nested value is a record):
...

fields are matched by name and are order independent and the input order is retained.

❯ zq -version
Version: v1.16.0

❯ zq 'type foo={a:string,b:int64} yield {} | fill(this,<foo>) | cast(this,<foo>)'
{a:null(string),b:null(int64)}(=foo)

❯ zq 'type foo={a:string,b:int64} yield {b:1} | fill(this,<foo>) | cast(this,<foo>)'
{b:1,a:null(string)}

❯ zq 'type foo={a:string,b:int64} yield {a:"x"} | fill(this,<foo>) | cast(this,<foo>)'
{a:"x",b:null(int64)}(=foo)

The middle example shows that the casting fails (returns the original input) because the order of fields isn't correct, but the docs say that "fields are matched by name and are order independent".
As a result of looking for similar issues, I discovered the shape function, which is what I can use going forward and not be impacted by this.

@chrismo: Actually, I think the middle example is behaving in a way that's aligned with the docs, though your experience shows there's room for improvement.
Let's start from the base of your middle example.
$ zq 'type foo={a:string,b:int64} yield {b:1}'
{b:1}

So that {b:1} becomes the this at the input to fill(). Adding that on:
$ zq 'type foo={a:string,b:int64} yield {b:1} | fill(this,<foo>)'
{b:1,a:null(string)}

That's is in line with where the fill docs say:

The fill function adds to the input record val any fields that are present in the output type t but not in the input.

What's implied here (but should likely be called out explicitly) is that the order of such added fields is undefined. There's a separate order function that would take care of this.
$ zq 'type foo={a:string,b:int64} yield {b:1} | fill(this,<foo>) | order(this,<foo>)'
{a:null(string),b:1}

Putting order aside for now and getting back to your original middle example, now that fill's behavior is rationalized, you can probably see that:
$ zq 'type foo={a:string,b:int64} yield {b:1} | fill(this,<foo>) | cast(this,<foo>)'
{b:1,a:null(string)}

...does line up with what you quoted from the cast docs:

fields are matched by name and are order independent and the input order is retained.

i.e., b came before a in the record value that cast saw as input, so cast intentionally did not disturb that order.
Ultimately, it's good that you found your way to shape because I think what you ultimately learned here is something we'll want most users to know: The way the shape function applies the "a la carte cast, fill, and order functions all at once is probably what most users will want (maybe crop too depending on use case). To that end, in addition to more explicitly addressing that "undefined" behavior of fill, the other docs improvement I envision based on your experience would be for us to add a very obvious "Note:" early in the pages for those "a la carte" functions effectively telling the reader that they're probably looking for shape whereas the individual functions are there as building blocks for advanced users.
@chrismo: Before I put pen to paper on those changes, do you have any feedback on the above?

The added note sounds good.
I feel like I'm still interpreting the cast docs on "order independent" to mean the order is not important for cast to work, so maybe it should say the "field order must match the ordering in the declared type" for cast to work in that part? What do you think about that wording?

@chrismo: Hmm! I'm not sure where the remaining confusion lies, since it still matches what I think of as "order independent". Let me cook up a slightly simpler example, since the prior examples used int64 as one of the types and it makes it a little harder to see when cast is having its effect since ZSON doesn't decorate int64 by default since that's the tooling's default integer type.
$ zq 'type foo={a:float16,b:uint16} yield {b:1.5,a:2} | cast(this,<foo>)'
{b:1(uint16),a:2.(float16)}

So that's in line with your interpretation that "the order is not important for cast to work", i.e., even though a comes before b in the type definition, cast matched up respective fields by name between the input record and the type definition and applied each individual type cast, turning b unto a uint16 and lopping off its fractional portion, and a into a float16 as evidenced by the trailing . and decorator. And it did this without rearranging the relative order of b and a as they were on the input record, as the docs also say to expect.
Any clearer? 😄

Any clearer? 😄

Ahhhh! So you're saying the cast was successful in this case, too, because the two fields in the record were cast to their appropriate types:
❯ zq 'type foo={a:float16,b:uint16} yield {b:1.5,a:2}'
{b:1.5,a:2}

❯ zq 'type foo={a:float16,b:uint16} yield {b:1.5,a:2} | cast(this,<foo>)'
{b:1(uint16),a:2.(float16)}

But it can't cast the entire record to foo because the order isn't correct, right? That's what I've been focusing on. I'm reading "order independence" as meaning the cast of the record to foo will work. I wasn't paying attention to the fields inside the record as having been cast.

@chrismo and I further discussed this online. I now understand that what made this most confusing was that in his middle example:
❯ zq 'type foo={a:string,b:int64} yield {b:1} | fill(this,<foo>) | cast(this,<foo>)'
{b:1,a:null(string)}

...the final output record lacked the =foo type decorator, and he took this as a sign that cast failed. I understand better now why this could be so confusing to a new user. Field order has significance in Zed records, and this cast operation is casting to a record type, so the current behavior of cast that changes the types of just the "leaf" fields without affecting order to make its output fully conform to the destination record type could indeed be seen as failure.
The shaping functions are due for some revision (#2342), so I'll keep this issue open to make sure this is considered in that effort.


Carthage builds ExampleModel.framework

Since Example.xcodeproj and JSQCoreDataKit.xcodeproj are at the same level, Carthage builds ExampleModel.framework which is undesired. Moving /Example into /JSQCoreDataKit seems to me to be the best way to resolve this if you have no objections.

thanks @alexcurylo !

hey @alexcurylo - actually, i just tried this and carthage did not build ExampleModel.
Running from the root directory:
$ carthage build --no-skip-current
*** xcodebuild output can be found in /var/folders/tx/s__fjnns3yd_23813_gwk7sh0000gn/T/carthage-xcodebuild.LwNg08.log
*** Building scheme "JSQCoreDataKit" in JSQCoreDataKit.xcworkspace

Then:
$ tree
├── Carthage
│   └── Build
│       └── iOS
│           └── JSQCoreDataKit.framework
│               ├── Headers
│               │   ├── JSQCoreDataKit-Swift.h
│               │   └── JSQCoreDataKit.h
│               ├── Info.plist
│               ├── JSQCoreDataKit
│               ├── Modules
│               │   ├── JSQCoreDataKit.swiftmodule
│               │   │   ├── arm.swiftdoc
│               │   │   ├── arm.swiftmodule
│               │   │   ├── arm64.swiftdoc
│               │   │   ├── arm64.swiftmodule
│               │   │   ├── i386.swiftdoc
│               │   │   ├── i386.swiftmodule
│               │   │   ├── x86_64.swiftdoc
│               │   │   └── x86_64.swiftmodule
│               │   └── module.modulemap
│               └── _CodeSignature
│                   └── CodeResources

And, running carthage update with the following Cartfile produces the same results:
github "jessesquires/JSQCoreDataKit"

Can you provide steps on how to reproduce your issue?

Sure: here's a cartfile on a shell project demonstrating the problem.

Well, we're clearly getting different results. :smile:
I recently did a bit of refactoring regarding the project setup/organization. There is no longer an ExampleModel scheme in the workspace. So I think this is a caching problem.
Trying clearing DerivedData/ and the carthage cache, and everything should be working.

Yup, cleared out everything Carthage-related and it rebuilt fine. Sorry to bother you!

No worries! :smile:


hook_utils.py: Bugfix

tf.train.latest_checkpoint() may return None, which can cause type error in tf.gfile.IsDirectory(self.checkpoint_path) call.

Thanks for contributing! LGTM

Thanks for contributing! LGTM


Multi-scale version

Hello,
Did you implement your model in multi-scale versions ? If yes, is it possible to release the associated code?
Thank you

Thank you for being so interested!
This is the implementation code for https://arxiv.org/abs/2103.11731v3, which has a significant difference with https://arxiv.org/abs/2103.11731v1.
The latest version of Meta-DETR does not have a multi-scale version. Thank you.


Support for gateway in process

Description
We would like to see an enhancement where support for decission point is introduced in the process in order to support attestation for "kompensasjonmelding". This is called "gateway" in BPMN terminology. The app itself (or its configuration) must be able to decide the way out from the decission point (next process step).

The app must  be able to decide the next step in the process without this being noticable for the SBS. The SBS shall only relate to processNext(). This is important to us as we don't want SBS not implementing the support for "kompensasjonsmelding" to be bothered with implementing chenges.
We must be able to decide the roles the user must posess in order to go from one process step to the next, even when this logic is involved. In other words; roles and rights must work as today also with the enhancement.

Additional Information
No response

Our current implementation does not treat gateways as a first class citizen in the process.
I think that we should change that, but that would require som larger changes and testing. As a quick-fix/workaround I suggest we implement a way for service owners to add some custom code where they can filter possible flows out of an exclusive gateway.
This code should run when GET /process/next and PUT /process/next endpoints are called.
This should cover the needs described in this issue as far as I can see, and buy us some time to get the gateways properly implemented in the process

Pre-Release 7.1.0-preview.1 is now out. The release contains support for making flow decisions based on instance data.
Not sure what version your app is, but please follow the upgrade guides located in breaking changes for each major version until you app is on v7 as documented here
The documentation has not been written so I will try to explain the steps necessary:
Prerequisites:

Your app is on v7
Your process has a process similar to the one described in this issue

Example application that navigates to the Confirmation task if the ammount supplied in the datamodel is greater than 1000. If not it skips the confirmation step.
The visual representation of the process in the example app:

Steps:

Upgrade Altinn.App.* nugets to version 7.1.0-preview.1 App.csproj in the example app
Get the ID of your exclusiveGateway. In the example app it can be found here
Create a class Implementing Altinn.App.Core.Features. IProcessExclusiveGateway. The GatewayId should match the one found in step 2. Implementation in the example
Register your newly created class as a transient in Program.cs. Registration in the example

If you have any questions pleas don't hesitate to comment on this issue or contact me on slack 🙂

Support added through #59. Released in v7.1.0


Use environment in evaluation of function definitions

@jwiegley Would you prefer me to merge that kind of things directly, or would you prefer that I wait for another pair of eyes?

This sort of thing you can just push directly, especially if it comes with a test.  Thanks!


Update Nuget package for C# to non pre-release status

Are there plans to bump Grpc for C# to non pre-release status? If yes, when? Do we have any timelines for this?
Being conservative is fine, but this issue prevents prevents consumers from using Grpc Nuget packages in other packages due to this Nuget issue.

bump Is no one else trying to use the Grpc C# nuget packages for production?

Yes, we will publish nuget packages for 0.13.1 as soon as we actually tag that release.

(that should happen before the end of this week).

Awesome, exactly what I needed. I'll look forward to this!

0.13.1 has been pushed!


chore: bump version to 1.2.0

What does this PR do

Bumps version to 1.2.0

Checklist:

[x] I ran make validation locally with success
[x] I have not introduced new bugs
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new errors

Warnings

:warning:
The library files were changed, but the tests remained unmodified.
Consider updating or adding to the tests to match the library changes.

  Generated by :no_entry_sign: Danger Swift against 9d875abb9123fa5b591fee79d94d33fd33b09db2


Bug: Sagas can no longer be array

To reproduce:
git clone
git checkout dev
yarn install
in app/containers/HomePage/saga.js change it to
export default [
githubData,
]
Error occurs.
We can no longer export array of saga watcher, like so in 3.4 ?

I think you should take a look at here, it help me a lot

Anyone reading this in the future can consider the suggestion by @Dattaya, explicitly
export function* rootSaga() {
  yield all([
    watchSaga1(),
    watchSaga2(),
  ])
}


Added 1 more question

I have added 1 More question in #1 as the first step towards Hactoberfest 2021.

Hello, the tag in the repo is mispelled 'hactoberfest' instead of 'hacktoberfest' don't forget to change it before accepting PR otherwise it won't count.

@yoobi Thanks made the changes

Hy @KunalRaghav, can you please review the PR and let me know if it is done.

I think now there is no need for this PR.🙂


Markdown backticks render as block elements

First off, thanks for the great work on this add-on. We are using it a ton, and it's very helpful to the whole team 😄
I've just noticed that in the current version, markdown backticks are being rendered as display: block by highlight.js which is causing some layout problems.

When I fix my version of storybook-readme to 1.2.0 the problem seems to go away, along with the hljs classes.

How can I reproduce this? Could you please provide markdown with layout problems?

Sure, try this:
Here I use a `backtick`, it should not be treated as a code block.
```javascript
console.log("This is a normal code block");
```

It should look like this:

But ends up looking like this:

All code blocks are wrapped with <pre> before  <code> whereas backticks are not.

Changing the highlight selector back to look for pre code will fix this.

yep. got it.

Merged and released. Try v1.3.2


Login via Facebook is broken

HybridAuth throws the Exception "Authentication failed! Facebook returned an invalid user id."
Probably Facebook changed its API and we need to upgrade HybridAuth.

HAuth Log says ...

2.8.0 - October 29 2016
BREAKING:
#688 - [Facebook] Update Provider to use newer API version

@fedys : can you take a look to this issue? It'seems, that we have to upgrade HybridAuth. Can you try to do this?

Yes, I can look at that on this weekend.

Perfect. If you need access to the facebook app used by our demo, please
let me know.

Fixed in 2eed95beb1b8663e4475442ce1af6edf4a5f751b
Merged into release/0.29

Facebook login is working.
Bit now linkedin is broken. I've created: https://github.com/cross-solution/YAWIK/issues/366


Error reported by virt launcher container

error: failed to get emulator capabilities
error: internal error: Failed to start QEMU binary /usr/libexec/qemu-kvm for probing: libvirt:  error : cannot execute binary /usr/libexec/qemu-kvm: Permission denied
k8s: v1.23.1
os: ubuntu 20.04.2 LTS

已解决：https://github.com/kubevirt/kubevirt/issues/4303


Custom Scrollbar Width

Updates Scrollable, adding facilities for updating the width of the scrollbar and scroller independently. We also gain control of the margin around the scrollbar.
Adds an example showing various ways these values interact.

RIP my beautiful color scheme 😞
Latest version looks good to me! 🚢


Catch failed to post tracking errors

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on improving error handling in the track.ts file by catching errors during tracking operations to prevent them from being reported to error services.
Detailed summary

Modified the promise chain in track.ts to catch errors by adding a .catch(() => {}); statement.
Updated the changelog in changeset/rotten-weeks-raise.md to reflect the change in error handling for tracking operations.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5065  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MananTank and the rest of your teammates on  Graphite


Redesign the email address search bar and sign-up button

The email address search bar and the button in the footer are not visually appealing. They should be resized, and additional styling should be implemented to enhance the website's appearance.

no need for redesigning them , they are good


Should devcontainer add remoteUser?

Description
(base)  ~/dev/ loco new
✔ ❯ App name? · todolist
✔ ❯ What would you like to build? · Rest API (with DB and user auth)

🚂 Loco app generated successfully in:
/Users/fanzhao/dev/todolist
(base)  ~/dev/ cd todolist
(base)  ~/dev/todolist/ code .
(base)  ~/dev/todolist/

Use vscode to open in a container, vscode's rust-analyzer not working properly and cargo loco doctor has permission issues

vscode ➜ /workspaces/todolist $ cargo loco doctor
    Updating crates.io index
  Downloaded ptr_meta v0.1.4
error: failed to download replaced source registry `crates-io`

Caused by:
  failed to open `/usr/local/cargo/registry/cache/index.crates.io-6f17d22bba15001f/ptr_meta-0.1.4.crate`

Caused by:
  Permission denied (os error 13)
vscode ➜ /workspaces/todolist $

I add "remoteUser": "root" to devcontainer.json and it can return to normal.
Should remoteUser be added to the default devcontainer.json, or should the developer add it themselves? Or are there other ways to solve it?

Hi @fan-tastic-z,
In the Dockerfile, when building, we have the option to grant write access to the vscode user in the /usr/local/cargo path. This should address the issue without the need to include removeUser: root.
Would you like to proceed with this solution and open a pull request?

Hi @fan-tastic-z,
In the Dockerfile, when building, we have the option to grant write access to the vscode user in the /usr/local/cargo path. This should address the issue without the need to include removeUser: root.
Would you like to proceed with this solution and open a pull request?

OK, I'd love to


CUBLAS_STATUS_ARCH_MISMATCH

Describe the bug
When the model  begins to train, I come up with the following error:
Logs

done building sapmles index maping
saved the index mapping in models/bert/my-bert_text_sentence_test_indexmap_20mns_512msl_0.10ssp_1234s.npy
elasped time to build and save samples mapping (seconds): 0.000438
loading indexed mapping from models/bert/my-bert_text_sentence_test_indexmap_20mns_512msl_0.10ssp_1234s.npy
loaded indexed file in 0.000 seconds
total number of samples: 204
finished creating BERT datasets ...
[after dataloaders are built] datetime: 2022-09-09 08:42:57
done with setups ...
time (ms) | model and optimizer: 8546.43 | train/valid/test data iterators: 227.91
training ...
[before the start of training step] datetime: 2022-09-09 08:42:57
CUDA error at /home/jovyan/data/tmp/fastmoe-megatron-patch/cuda/moe_compute_kernel.cu:132 code=8(CUBLAS_STATUS_ARCH_MISMATCH) "cublasXgemm( smgr->handle(i), CUBLAS_OP_T, CUBLAS_OP_N, out_feat, expert_count[i], in_feat, &alpha, weight + i * in_feat * out_feat, in_feat, input_buf + ptr * in_feat, in_feat, &beta, output_buf + out_feat * ptr, out_feat )"

Platform

Device: [e.g. NVIDIA V100]
CUDA version: [11.1]
NCCL version: [2.8.3]
PyTorch version: [1.8]
fastmoe version: [0.1.2]

Any idea about this problem?

According to NVIDIA's document,

The function requires a feature absent from the device architecture; usually caused by compute capability lower than 5.0.

I suppose that when compiling FastMoE, cuda's architecture flag is not specified properly, or your cuBLAS library's version mismatches the one for your GPU.

Closing due to lack of further response. Feel free to re-open if you have any progress.


Hold note hit sounds

As a player, I want the hold note hit sounds to be consistent so that I know exactly when I've messed up.

Currently, hit sounds can only play when you press and release the hold note. There are certain scenarios where the hit sound never plays.
A miss sound should play if you miss the hit time
A miss sound should play if you never release at the end time

Reliant on #378

Implemented in  #418


Error in android devices

From @SaiKarthikMalyala on July 16, 2018 15:0
URL: https://pub.dartlang.org/packages/url_launcher
When I tried to open .pfd and .docx files in android devices it exist displaying the blank black screen.
The same files when I opened the Iphone they are opened.
Copied from original issue: dart-lang/pub-dartlang-dart#1461

@SaiKarthikMalyala This repository is for the pub site, please submit your issues to the package's issue tracker. I'm moving it this time.

@SaiKarthikMalyala are you still seeing this?


Eventually does not work with RSpec expect statements

eventually(40) { expect(roles.user).to see :list_item }
The issue is that when the expectation fails, it throws RSpec::Expectations::ExpectationNotMetError, which subclasses Exception, not StandardError. Eventually only catches StandardError. This means the code above waits only as long as the Capybara wait time (defined in Dill's see?), not the 40 seconds that have been given the eventually
Here's the PR that changed the subclass.
https://github.com/rspec/rspec-expectations/pull/426

Resolved with https://github.com/mojotech/dill/pull/107


[Feature] Jenkins configuration-as-code

Motivation and Context

Setting Jenkins and getting it to run with Artemis is time consuming due to the many manual steps needed (install plugins, create credentials, etc).
Description

This pr introduces a couple of quality-of-life changes that help speed up the setup process. These are the features:

Update the Jenkins dockerfile to automatically install the Jenkins plugins required by Artemis. The plugins are maintained in src/main/docker/jenkins/plugin.yml
A new jenkins-casc-config.yml file: We take advantage of JCasC to provide a file that pre-configures the Jenkins environment.
A new gitlab-jenkins-mysql.yml docker-compose file which deploys all three environments into containers. Here we configure the jenkins service so that it automatically reads jenkins-casc-config.yml on startup.
Update the docs with a Jenkins quick-start guide.

Test Coverage
Nothing changed

This makes the local development setup a lot easier. GJ!
I had to make a few changes to the configuration to get all containers started as intended.
The Jenkins Plugins seem to get installed properly and Build-Jobs start, so the CASC-setup seems to generally work.
I need to retest it again, though, as at the moment setting up the Webhooks in Gitlab fails (‘Invalid URL’) and Jenkins couldn’t pull code from Gitlab. I assume that is just my fault by having old API-Tokens somewhere that were only valid in some other older containers.

Thank you @b-fein for your review! Are you running the local environment on a Mac or on a Linux machine? I could try to re-deploy everything and see if I encounter the same problems.

Are you running the local environment on a Mac or on a Linux machine?

It’s on Linux, with no special system-wide Docker/networking configurations as far as I know. (Docker version 20.10.5-ce, docker-compose version 1.28.5)

This makes the local development setup a lot easier. GJ!
I had to make a few changes to the configuration to get all containers started as intended.
The Jenkins Plugins seem to get installed properly and Build-Jobs start, so the CASC-setup seems to generally work.
I need to retest it again, though, as at the moment setting up the Webhooks in Gitlab fails (‘Invalid URL’) and Jenkins couldn’t pull code from Gitlab. I assume that is just my fault by having old API-Tokens somewhere that were only valid in some other older containers.

Thank you @b-fein for your review! Are you running the local environment on a Mac or on a Linux machine? I could try to re-deploy everything and see if I encounter the same problems.

Are you running the local environment on a Mac or on a Linux machine?

It’s on Linux, with no special system-wide Docker/networking configurations as far as I know. (Docker version 20.10.5-ce, docker-compose version 1.28.5)

Did you check the spring.server.url entry inside the application-dev.yml file? I had to add the external Ip of the Artemis server (it's displayed when it's started) including the port. For some reason the port isn't taken from the spring.server.port entry.

I actually had
server:
    port: 8080
    url: http://<IP_ADDRESS>:8080

as part of application-local.yml before. Changing url to url: http://<IP_ADDRESS>:8080 the IP inside the Docker network works.

The pipelines need the cleanWs task which is provided by the Workspace Cleanup plugin.
Adding - artifactId: ws-cleanup to src/main/docker/jenkins/plugins.yml fixes failing pipelines.
After adding that change I tested setting up various exercises with Java (+ optional SCA), Swift, and Python. Repos were created, build jobs ran, and results were delivered to Artemis. Additionally I tested creating users which were successfully created in Gitlab+Jenkins, too.
The communication between the different containers and Artemis therefore worked as intended.
With the remaining little change to plugins.yml I approve!

Thanks for testing out the changes! I committed the missing plugin and the mysql volume.


Remove use of netstat in tests

update autest to 1.4.2 as this has fix for portopen to be like netstat, but portable

[approve ci]

[approve ci autest]

[approve ci autest]

[approve ci autest]


#128 custom constraints (issue/128)

Fixes #128

Current coverage is 100% (diff: 100%)

Merging #129 into master will not change coverage

@@           master   #129   diff @@
====================================
  Files          25     26     +1
  Lines         470    482    +12
  Methods       445    455    +10
  Messages        0      0
  Branches       25     27     +2
====================================
+ Hits          470    482    +12
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update e422082...4ec1544


Markup view mode

The application is a joy to use :) but what about the possibility of having a way to alternate from UI view mode to Markup view mode?

+1

@danielalmeidagoncalves & @codesharkasm : What do you want concerning a "Markdown mode" ?
Just a preview of the output code ? If it's the case, I could implement that.
A complete Markdown edit mode view ? I will not do that.
(Un)colored is a WYSIWYG editor that export into HTML or Markdown, it's not a Markdown editor :)

@n457 I see what you mean and yes I completly understand the purpose of the project, so for me still  would be very nice to have that kind of preview mode, as there are Markdown editors that allow the other way around, namely giving us a preview mode of the markup code :)

Alright, I wait for @codesharkasm proposals before deciding on this feature

Typora has a "Source Code Mode".

It looks like a regular IDE.
Does this help?

@codesharkasm Yep that could be a nice approach :)

@danielalmeidagoncalves @n457 Sometimes it's nicer & faster to write in markdown. But whatever you want... It doesn't require any UI changes... so only power users would use it. But I definitely would like to see this functionality in UC.

One way to support Mardown would be to allow to type markdown into the normal editor. So if I want a new title I type # my title, and when the new line is added Uncolored automatically turns that in a title visually. That could be a nice hybrid approach to avoid the clumsy double screen.
Some editor having similar hybrid approach: Abricotine (less WYSIWYG), HyperMD (the demo website seems half broken, but you still get the idea), Emacs with LaTeX or OrgMode configured well.

@Mayeu That's a good idea!

Hi @danielalmeidagoncalves @codesharkasm @Mayeu :)
@codesharkasm @Mayeu : so hmm see the comment https://github.com/n457/Uncolored/issues/24#issuecomment-262007576 of this topic :

A complete Markdown edit mode view ? I will not do that.
(Un)colored is a WYSIWYG editor that export into HTML or Markdown, it's not a Markdown editor :)

➔ (Un)colored is not a code editor. You already have full dedicated Markdown editor (like Typora). Sorry guys I can't accept your request this time :/
@danielalmeidagoncalves : I will implement a Markdown preview mode 👍
Thank you all for contributing, it's always a pleasure !


cross build error

pending https://github.com/rustformers/llama-rs/issues/101

solved since v0.0.16


Use BlueBrain/Neurom codecov status icon.

Current coverage is 100.00%

Merging #58 into master will not affect coverage as of b20ee61

@@            master     #58   diff @@
======================================
  Files           26      26
  Stmts          896     896
  Branches         0       0
  Methods
======================================
  Hit            896     896
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of b20ee61

Powered by Codecov. Updated on successful CI builds.


relax requirement for unknown fields in json-to-proto decoding

Current json-to-proto decoding does not recognize unknown fields and fails to load things like proxy mesh config, e.g.
  Error: failed to create injection webhook failed to convert to \
      proto. unknown field "policyCheckFailOpen" in v1alpha1.MeshConfig

fixes https://github.com/istio/istio/issues/9593

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

Needs approval from an approver in each of these files:

pilot/OWNERS [ayj]

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

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

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-local-tests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-k8s-tests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-unit-tests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth-mcp.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test e2e-mixer-no_auth-mcp

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

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

Needs approval from an approver in each of these files:

pilot/OWNERS [ayj,rshriram]

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth-mcp.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test istio-integ-local-tests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth-mcp.sh
da37207d92b16cc918d4c3d185cd8a576d0c4cdf
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test istio-integ-k8s-tests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test istio-unit-tests

prow/e2e-mixer-no_auth-mcp.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test e2e-mixer-no_auth-mcp

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

/retest

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test istio-unit-tests

prow/e2e-mixer-no_auth-mcp.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test istio-unit-tests

prow/e2e-mixer-no_auth-mcp.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-unit-tests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-simpleTests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-simpleTests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-simpleTests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-simpleTests

prow/e2e-dashboard.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-dashboard

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-simpleTests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-simpleTests

prow/e2e-dashboard.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-dashboard

prow/istio-pilot-multicluster-e2e.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-multicluster-e2e

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
0c349abbaea731f054f1090b3aae6338a5299a44
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-simpleTests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-simpleTests

prow/e2e-dashboard.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-dashboard

prow/istio-pilot-multicluster-e2e.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-simpleTests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-simpleTests

prow/e2e-dashboard.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-dashboard

prow/istio-pilot-multicluster-e2e.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth-mcp.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-mixer-no_auth-mcp

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

/test e2e-simpleTests

/test istio-unit-tests

/test e2e-dashboard

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

Needs approval from an approver in each of these files:

pilot/OWNERS [ayj,rshriram]

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/istio-pilot-multicluster-e2e.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth-mcp.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-mixer-no_auth-mcp

prow/e2e-dashboard.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-dashboard

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

/test e2e-dashboard

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test e2e-mixer-no_auth

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

/test e2e-mixer-no_auth

/test istio-pilot-e2e-envoyv2-v1alpha3

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/build-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test build-tests

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

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-integ-k8s-tests

prow/build-tests.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test build-tests

prow/istio-pilot-multicluster-e2e.sh
f840ddc56fd9cd5cf868bccb5e83237991c0b25b
link
/test istio-pilot-multicluster-e2e

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


React Shopify

This project was bootstrapped with Create React App.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

Pull request has done

The pull request is very good and well documented but the issue is its haveing merge conflicts could you update your fork of the repository to the latest version of the MLSA repo and recommit your changes and apply for the pull request it will help


L2capBle.prototype.setServices on linux always appends generic access service

I want to add other characteristics to the generic access service, and it doesn't make sense to have two identical services enumerated with different characteristic lists.
Can we get the option to turn this off (besides just deleting the code?)

In order to keep OS X and Linux functionality similar, this will not be implemented at this time.


Update to 0.4 version of Karafka

Routing
ApplicationWorker
ApplicationController

Up - update to the most recent master including new routing and other changes :)

Also we need to update it to the new app.rb loading order:
ENV['RACK_ENV'] ||= 'development'
ENV['KARAFKA_ENV'] ||= ENV['RACK_ENV']

Bundler.require(:default, ENV['KARAFKA_ENV'])

Karafka::Loader.new.load(Karafka::App.root)

# App class
class App < Karafka::App
  setup do |config|
    # In most of the cases, Karafka will figure out kafka hosts automatically based on the zookeeper
    #   data. Set it manually only if you know what you are doing
    # config.kafka_hosts = %w( <IP_ADDRESS>:9092 )
    config.zookeeper_hosts = %w( <IP_ADDRESS>:2181 )
    config.wait_timeout = 60 # 1 minute
    config.max_concurrency = 5
    config.name = 'example_app'
    config.redis = {
      url: 'redis://localhost:6379'
    }

    routes.draw do
      # topic :example do
      #   controller ExampleController
      #   interchanger CustomInterchanger
      # end
    end
  end
end

It should also include a new version of WaterDrop


[e2e tests]: Use default scp protocol instead of explicitly using legacy

Signed-off-by: Alex Kalenyuk<EMAIL_ADDRESS>
What this PR does / why we need it:
Some testing environment may have an older SCP, and thus not have the -O option.
I don't think there is a particular reason to opt for the legacy method:
https://wiki.archlinux.org/title/SCP_and_SFTP
Note: Since OpenSSH 8.8 the scp utility uses the SFTP protocol by default. The -O option must be used to use the legacy SCP protocol.

Warning: The scp protocol is outdated, inflexible and not readily fixed. Its authors recommend the use of more modern protocols like sftp and rsync for file transfer instead:
https://lists.mindrot.org/pipermail/openssh-unix-dev/2019-March/037672.html

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/hold
20:45:51:   Warning: Permanently added 'testvmi-4wctk.kubevirt-test-default2' (ECDSA) to the list of known hosts.
20:45:51:   sh: /usr/libexec/sftp-server: not found
20:45:51:   scp: Connection closed
20:45:51:   exit status 255```
SFTP server not available on fedora 34 runner?

@fossedihelm FYI

/hold cancel
/retest

@xpivarc @acardace Can you have a look, please? Thanks

/approve

/retest-required


For help，How to bring the Badge  to the center of the segment cell instead on to the top

Report

The more information you provide, the faster we can help you.

⚠ Select what you want - a feature request or report a bug. Please remove the section you aren't interested in.
A feature request
What do you want to add?

Please describe what you want to add to the component.

How should it look like?

Please add images.

Report a bug
What did you do?

Please replace this with what you did.

What did you expect to happen?

Please replace this with what you expected to happen.

What happened instead?

Please replace this with what happened instead.

Your Environment

Version of the component: insert here
Swift version: insert here
iOS version: insert here
Device: insert here
Xcode version: insert here
If you use Cocoapods: run pod env | pbcopy and insert here
If you use Carthage: run carthage version | pbcopy and insert here

Project that demonstrates the bug

Please add a link to a project we can download that reproduces the bug.

i need like this


bug(datepicker): Datepicker control is marked as dirty

Bug description:
Datepicker control is initially marked as dirty.
Link to minimally-working plunker that reproduces the issue:
I was not able create plunker (becouse of other errors), but you can check this behavior in documentation of datepicker control - https://edcarroll.github.io/ng2-semantic-ui/#/modules/datepicker
datepicker controls has ng-dirty instead of ng-pristine class.
Version of Angular, ng2-semantic-ui, and Semantic UI:
Angular: latest / current
ng2-semantic-ui: latest / current
Semantic UI: latest / current

I made pull request for this bug: #328

ng2-semantic-ui - Datepicker control is initially marked as dirty. Making it pristine using Angular's Lifecycle hooks also didn't solves the problem.Bug fix is required.

The issue still exist. Any progress on it?


decoration of id

Currently id is decorated as PAAUobjc_object@@ which undname is unable to symbolicate.  However, It is unclear whether this is accidental and the decorated name should be PAUobjc_object@@.  This properly is undecorated by undname as struct objc_object *.

CC: @DHowett-MSFT @DHowett

@compnerd Thanks for reporting this. It looks like it should be PAUobjc_object@@.
What issue are you seeing because of this? I think PAAUobjc_object@@ should still unmangle as Uobjc_object* (losing the struct typekind.)

(source: MicrosoftMangle in llvm-mirror here primes the mangled name with PA, then calls mangleArtificalTagType, which should emit U then the name. The code here looks right.)

Yeah, it does result in `Uobjc_object *.  I shall fix clang (upstream) to generate this name properly.  However, doing so means that

previously compiled objects will need to be rebuilt
the exception handling needs to be adjusted for the correct mangling of id for the root type CatchableType entry

SVN r3117617 will now mangle id, Class, and @interface appropriately in the C++ context.  I have more questions about the decorations, is this the best channel for them?

clang now generates the right thing.


Vite6

This is an extension of https://github.com/privatenumber/vite-css-modules/pull/14, because I'd like to use this myself again.
I had to rollback typescript as pnpm doesn't seem to like typescript 5.6 (more of a yarn person myself)...tsc was throwing all lkinds of weird errors that a rollback to 5.5.4 (or a switch to yarn) fixed. I then noticed that tsc wasn't run as part of the CI job, so added that.
The missing filename I think is trivial; the test harness doesn't provide a closest package.json, so let's just provide the static name as suggested. I then took the commit from #14, massaged the types, and the tests seem to pass!
closes https://github.com/privatenumber/vite-css-modules/pull/14
fixes https://github.com/privatenumber/vite-css-modules/issues/13

Thanks, I'll try to review over the weekend!

I've been unable to reproduce this since in storybook

Thank you @mrginglymus & @skewballfox !

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore: remove unnecessary await

Here val is already awaited. In the next line in _body for conditional checking, we have given await again for val. Also the code editor is saying await has no effect here like that. That's why I thought may be we may remove it.

changed after #822

Thanks @pi0


Apply security update.

And make whitesource happy.

And make whitesource happy.

We have not yet run a scan on the ev-dashboard :-)

And make whitesource happy.

We have not yet run a scan on the ev-dashboard :-)

Yep it will be happier if we proactively run npm audit fix before ;)

Yep it will be happier if we proactively run npm audit fix;)

Hahaha, yes! Kill it in the egg!
Thanks!


fix($compile): do not initialize optional '&' binding if attribute not specified

Also, do not set up an expression in scope if the '&' binding is optional.
BREAKING CHANGE:
Previously, '&' expressions would always set up a function in the isolate
scope. Now, if the binding is marked as optional and the attribute is not
specified, no function will be added to the isolate scope.
Finally, if the '&' expression is not optional, and the attribute is not
specified, then rather than the function being essentially a NOOP, it will
instead throw an error indicating to the programmer that a required attribute
was not specified.
Closes #6404

@caitp - I am also feeling uncomfortable about this change.
How about this compromise:

if the expression is not optional then we leave the behaviour as-is (i.e. we just pass a noop to the scope)
if the expression is optional (new feature) then we do not define it on the scope

This way, we do not break existing directives; plus we provide a way for directive developers to specify optional expressions and easily check for their existence in the template, etc.
What do you think?
(cc @IgorMinar)

updated

Great - taking a look!

Not so easy to cherry pick to 1.3.x ...

i'm not sure we should backport it

I realise after trying to do so manually that it is effectively a breaking change. So yes, you are right

Sorry for digging out an old thread. I noticed that there is a breaking change regarding =? between 1.3 and 1.4 as well and I would like to figure out if that's due to what is described in this issue. It seems this issue is only referring to & bindings but it seems to be related.
This example throws with an exception when you try to toggle the second zippy because it doesn't use the open binding and the binding isn't marked as optional. The example is based on 1.3.
http://plnkr.co/edit/Ef2iKOde3TmGzJHRGEhE?p=preview
The same example using 1.4 does not throw however.
http://plnkr.co/edit/cWxO6shBz7OaiewCDMHp?p=preview

That is weird @cburgdorf - can you open a new issue for it. I think it is a bug.

Thanks for the fast reply! I opened this one https://github.com/angular/angular.js/issues/13367


msgpackrpc.error.RPCError: rpclib: function 'enableApiControl' (called with 2 arg(s)) threw an exception.

I think that this issue is about num_agent settings. Could you help me to do this code..

---------------------------------- Environment ----------------------------------
Successfully loaded environment: indoor_techno
------------------------------------- Drone -------------------------------------
Connected!
Client Ver:1 (Min Req: 1), Server Ver:1 (Min Req: 1)
Traceback (most recent call last):
File "main.py", line 87, in
eval(name)
File "", line 1, in
File "C:\Users\hshsh\OneDrive\Desktop\pedra2\algorithms\DeepQLearning.py", line 26, in DeepQLearning
client, old_posit, initZ = connect_drone(ip_address=cfg.ip_address, phase=cfg.mode, num_agents=cfg.num_agents)
File "C:\Users\hshsh\OneDrive\Desktop\pedra2\aux_functions.py", line 247, in connect_drone
client.enableApiControl(True, name_agent)
File "C:\Users\hshsh\Anaconda3\envs\hs\lib\site-packages\airsim\client.py", line 37, in enableApiControl
return self.client.call('enableApiControl', is_enabled, vehicle_name)
File "C:\Users\hshsh\Anaconda3\envs\hs\lib\site-packages\msgpackrpc\session.py", line 41, in call
return self.send_request(method, args).get()
File "C:\Users\hshsh\Anaconda3\envs\hs\lib\site-packages\msgpackrpc\future.py", line 45, in get
raise error.RPCError(self._error)
msgpackrpc.error.RPCError: rpclib: function 'enableApiControl' (called with 2 arg(s)) threw an exception. The exception contained this information: Vehicle API for 'drone0' is not available. This could either because this is simulation-only API or this vehicle does not exist.

The issue could be the outdated environment. Can you download the environment from the link again and check if the error persists?

Also, can you share the settings,json file? It should be in the documents folder.

It is updated environment version. Other environments doesn't work too.
setting.json file is in C:\Users\hshsh\Documents\Airsim. Is this the right path?

Did you update PEDRA to version 2.0 as well?
Yes that's the right path

Yes. I updated PEDRA version 2.0. Have you heard of any cases like this kind?

I have not heard of any similar case.
If you could share config.cfg and settings.json file, I might be able to help

config.cfg setting
[general_params]
run_name:                   Tello_indoor
custom_load:                True
custom_load_path:           models/trained/Indoor/indoor_cloud/Imagenet/e2e/e2e
env_type:                   Indoor
env_name:                   indoor_long
mode:                       train
SimMode:                    Multirotor
drone:                      ARDrone
ClockSpeed:                 20
algorithm:                  DeepQLearning
ip_address:                 <IP_ADDRESS>
num_agents:                 1
[camera_params]
width:                      320
height:                     180
fov_degrees:                80
setting.json setting
{
"Vehicles": {
"drone0": {
"Yaw": 180.0,
"VehicleType": "SimpleFlight",
"Z": 0,
"X": 0.0,
"Y": 0.0
}
},
"ClockSpeed": 20,
"CameraDefaults": {
"CaptureSettings": [
{
"Height": 180,
"ImageType": 0,
"Width": 320,
"FOV_Degrees": 80
},
{
"Height": 180,
"ImageType": 3,
"Width": 320,
"FOV_Degrees": 80
}
]
},
"LocalHostIp": "<IP_ADDRESS>",
"SettingsVersion": 1.2,
"ViewMode": "NoDisplay",
"PawnPaths": {
"DefaultQuadrotor": {
"PawnBP": " Class'/AirSim/Blueprints/BP_ARDrone.BP_ARDrone_C' "
}
},
"SimMode": "Multirotor"
}
Thanks for you help..

OMG..There was another setting.json in C:\Users\hshsh\OneDrive\Documents\AirSim..
After moving setting.json file to this path, it works.
Sorry for taking your time thank U!

Everytime you change the config.cfg file, settings.json is updated.
I recommend you update the 'filename' variable in main.py on line 17 under the module generate_json to the path you moved settings.json to. This way you wont have to copy paste it everytime
filename = 'C:\Users\hshsh\OneDrive\Documents\AirSim\settings.json'


feature: Add pm2 process manager for self-reboot

Installed pm2 (http://pm2.keymetrics.io/)
Updated npm start command and kept npm run dev without pm2
Updated README

Reopening 👍


Add support for a space after open parenthesis

rgba(#fff, .75); was converted but rgba( #fff, .75 ); not.
See #17.

Thanks! Should probably use a regex pattern here for more robust rule matching.
But happy to just merge this if you cbf, this plugin is kinda unmaintained from me since I don’t use postcss anymore (I’m building Satchel as it’s successor).

Thanks for the feedback! You mean using a regex instead of the include()? I thought about that too but there’s https://github.com/seaneking/postcss-hexrgba/pull/21/.

Hmm yeah okay, let's just stick with a basic string then. Personally I'd prefer robustness over perf, since this is just a CLI tool, but if that tradeoff is the standard set by other plugins happy to follow suit.
LGTM 👍

@seaneking Looking at the code again, you're probably right. There's already a check for rgba here so the includes() part kind of duplicates the check.
Initially I thought that the check in ruleHandler() runs on the whole CSS but it's only the value of each declaration so I think we can revert to using a cached regex pattern.
postcss-color-rgba-fallback is a related plugin which uses postcss-value-parser to parse the value. It's used by quite a few plugins so maybe something for this plugin too?

Yeah sure thing, go for it. As long as it passes the tests I'm happy 👍

For memory the includes check was added in another PR for perf reasons, I think it was the one you linked to earlier