[FLINK-17827] [scala-shell] scala-shell.sh should fail early if no mo…

…de is specified, or have default logging settings

What is the purpose of the change
Try to avoid the exception that log4j.properties and logback.xml are set wrongly when illegal mode or no mode is specified when running Flink Scala shell using start-scala-shell.sh
Brief change log

Added an additional if-else branch to set the default log4j.properties and logback.xml when  illegal mode or no mode is provided.

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@zentol Thank you for your suggestion and now I changed my code. I would be glad if you take some time to review the updated solution.


Add Google Analytics via Tealium (common.js)

https://www.ibm.com/standards/carbon/developing/building-for-ibm-dotcom#ibm.com-tag-management-and-site-analytics
https://pages.github.ibm.com/digital-behavior/docs/tms-instrumentation.html

If GA could be added sooner than v1.0, we could begin to test and ensure we are seeing the data in GA.

@ljcarot do we have this information that we will need to add this? category, siteID, industry, owner? This is a screen shot from the IDL website.

Per the docs (https://pages.github.ibm.com/digital-behavior/docs/tms-instrumentation.html#23-sample-code), we'll have to call window.ibmStats.pageview() in places after Next.js web app hydration and subsequent page views.

Hey team! Please add your planning poker estimate with ZenHub @alisonjoseph @francinelucca @jdharvey-ibm

We can reference this as an example: https://github.com/carbon-design-system/carbon-website/pull/2953


Rendering the same component twice doesn't work

If the same component gets used twice, the rendering is not working correctly.
<PageContent>
  <Finance />
  <Finance />
</PageContent>

I used the sandbox example to try the above case.

I don't think that is the case, you can render the same component a hundred time: https://codesandbox.io/s/jikji-issue-21-t9s3w4?file=/src/AnnualReport/index.tsx
The issue is the component use ChartJs and there is an issue in applying the layout on the chart depending on the chart position on the page


Documentation: flogogen not rendering properly

When reading it on Github the ending ``` is correctly identified but when using flogo.io documentation page it isn't, and is then swapping everything after it.

Am I the only one that doesn't see this fixed? I'm even using a different explorer to avoid cacheing issues. I though it could be just it being solved in GitHub but not ported yet to the docs (I'm not sure if Hugo requires this kind of process or if he reads it from GitHub directly) but I'm seeing the new section FaaS now and that was merged after the solution to this issue but I'm still seeing the same problem.

It might be :(
The snippet of HTML that caused the problem is now rendered correctly in the gh-pages branch (the closing code tag was missing due to extra spaces at the end):

With the trigger command of flogogen you can create a custom flogo trigger. To do so, run:

flogogen trigger mytrigger

I've looked at the page on different browsers and different machines and it displays the page correctly. Can you try doing an empty cache and hard reload if you're using Chrome and see if that forces your machine to get the latest pages?

Opened developer tools and selected that option from the dropdown menu that appears when you right-click the reload button a couple times and still nothing.
We are looking at the same place, aren't we?


Task1

Issue: #2
Kali linux downloaded

Hey @shrut2606
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @shrut2606
Your PR has been merged 🥳🥳 and you have earned 20 points.
Thanks for contributing in OpenCode'24 ✨✨


Vulnerability issue on dependency log4j

Hi
I use org.owasp.dependencycheck to check vulnerabilities on my project and esapi to filter all data provided by users.
Unfortunately, the owasp plugin shows a critical issue on log4j... coming for esapi module

log4j-1.2.17.jar
cpe:2.3:a:apache:log4j:1.2.17:::::::*
<EMAIL_ADDRESS>CRITICAL
1
Highest
32

log4j with version 1.2.17 is very old and must be replace at least by  org.apache.logging.log4j » log4j-core or by org.slf4j:slf4j-api.
Could you please update the dependencies?
Thanks in advance

ESAPI does not expose this vulnerability to users in an exploitable manner.
It is a false positive for us. I have written a security bulletin do
describe all the details and workarounds which I shall be uploading to our
"develop" branch shortly.

Also, this is against the wrong repository.  This is for the future ESAPI 3.X branch.  Issue should be applied against ESAPI/esapi-java-legacy

Good point. I had been planning on creating a new GitHub issue to track this for the security bulletin that I was already in the process of writing up. I will do that and link to https://github.com/ESAPI/esapi-java/issues/9#issue-562048527
But since this CVE doesn't affect this 'esapi-java' repo, I am closing this issue.


Github import fails

Once I enter ? From which repo do you want to import issues from (e.g. "facebook/react") I get this error message:
TypeError: Cannot read property 'id' of null
    at /Users/a/Projects/linear-import/dist/import.cjs.development.js:1140:39
    at Array.filter (<anonymous>)
    at _temp3 (/Users/a/Projects/linear-import/dist/import.cjs.development.js:1139:69)
    at o (/Users/a/Projects/linear-import/dist/import.cjs.development.js:33:39)
    at _settle (/Users/a/Projects/linear-import/dist/import.cjs.development.js:70:4)
    at _resumeAfterBody (/Users/a/Projects/linear-import/dist/import.cjs.development.js:219:5)
    at processTicksAndRejections (node:internal/process/task_queues:93:5)

@xarg is this issue still happening? Can you give me more details about your input?

No, I used the main branch and it worked.


Fisheye Extension of Demo2d

Hello,
I just finished working on the fisheye extension we were talking about for a while. I just wanted to put out a working version but adjustments can obviously be made as necessary. I added the file demo2fisheye.html that should show this version. I made it so that when a user clicks on a parent node, it displays its children below it and allows for a fisheye effect when a user hovers over the children. The children then disappear when a user clicks outside of the graph. I disabled all other features of being able to click on a node and display it's properties, show nav history, etc. to focus on getting the fisheye correct first but those can also be added back easily depending on what we want with the fisheye version of the graph. Let me know what you guys think.

Nice to see your progress on this.
This is a very mild fisheye effect: the node positions don't change at all, only the radii. It's not going to solve our problem of trying to compress many nodes into a limited amount of screen space. Contrast this with the behavior of the NY Times demo at https://www.nytimes.com/newsgraphics/2013/09/13/fashion-week-editors-picks/index.html. Ndes get thinner (but not shorter) and shift their positions. That's the behavior we should be trying to emulate.

Ok here are some observations I'm seeing with the NY Times demo that I'll try to implement with our demo:

The overall horizontal space that the nodes take up doesn't change
The outer nodes look like they reach the same minimum size so the size decrease isn't going to be the same for the left and right nodes unless the mouse hovers over the middle node. (I.e. the size decrease of the left and right nodes of the current focus node is dependent on the number of left/right nodes of the current focus node)
The vertical positioning of the nodes doesn't change
The farther away a node is from the focus node, the closer it is to the max left/right distance and the farther away it is from the current focus node

This sounds good. The last time I looked at this demo I viewed the source code and found the equation they used for the fisheye effect. I just did it again and searched for "fisheye": the code is pretty simple. See for yourself: view-source:https://www.nytimes.com/newsgraphics/2013/09/13/fashion-week-editors-picks/index.html
Try just stealing their algorithm and see how it looks.

In the fisheye view, let's leave out the Q numbers for nodes. That just clutters the display.

Ok sounds good

I believe the newest version of demo2fisheye.html should have implemented most of these changes. Let me know what you think @touretzkyds

This is closer to the fisheye we had in mind, but it's still not right. It doesn't behave the way the NY Times fisheye behaves. Are you using their equations?

I am not using their exact equations. I already had an algorithm I was working on that I was trying to manipulate to behave similarly to the NY Times demo one. I was trying to understand/parse through the NY times equations and it was hard for me to see how they were manipulating the x positions of the nodes. I think (and I could very much be wrong) they made it look like the "nodes" (i.e. pictures) were changing x positions with mostly only the changes in width. I.e. nodes were changing x positions only because every node had a change in width. This type of behavior is hard to mimic with the nodes in the Cytoscape graph because if we just focus on just a change in width then it won't appear that the nodes are changing x positions as we saw in the first version of the fisheye I posted. My next step could be to scratch the current demo I have and I could try to reconstruct the fisheye entirely to try and mimic the NY Times demo, it just might take some time because they use a lot of variables and functions that aren't readily accessible in the index.html file.

I think you should probably switch from circles to rectangles for your fisheye view. Or, if you stick with circles, they'll become ellipses, which could also work.


[DOCFIX] Remove indentation for sitemap

remove the indentation in sitemap and manage indentation in css

alluxio-bot, merge this please


APIEmbed.type and EmbedType deprecated

Issue description
APIEmbed.type and EmbedType are both listed as deprecated in the library. However, the Discord API page linked in the deprecation notice and the Discord API page for Message show no deprecation of the embed.type property.
Code sample
message.embeds.filter(embed => embed.data.type === EmbedType.Image)
// will give two deprecation warnings. One for `type` and the other for `EmbedType`

Package version
0.37.50
Runtime
Node.js
Runtime version
v22.12.0
Priority this issue should have
Low (slightly annoying)

It seems https://github.com/discord/discord-api-docs/pull/7050 removed the deprecation message. Feel free to remove the deprecation!


Deploy job while devspace dev is running

What happened?
I'm trying to deploy a kubernetes job with devspace 6 while devspace dev is running.

devspace dev
devspace deploy -p xyz-my-job-generate
run_dependencies: couldn't execute 'devspace deploy -p xyz-my-job-generate', because there is another DevSpace session for the project (xyz) already running inside this namespace

What did you expect to happen instead?
The job inside profile xyz-my-job-generate will be deployed.
How can we reproduce the bug? (as minimally and precisely as possible)

the easiest way to generate this case

run twice devspace dev in separate consoles

In my case:
run devspace dev in one console
run devspace deploy -p xyz-my-job-generate in another console

My devspace.yaml:
version: v2beta1
name: xyz

vars:
  PHP_IMAGE: "xyz-webapp-php"
  PHP_MY_JOB_IMAGE: "xyz-my-job"
  NGINX_IMAGE: "xyz-webapp-nginx"

deployments:
  webapp:
    namespace: xyz-dev
    kubectl:
      manifests:
        - kustomize/overlays/dev/webapp/
      kustomize: true

dev:
  php:
    imageSelector: '${PHP_IMAGE}'
    sync:
      - path: ./:/app
        excludePaths:
          - .git/
          - .idea/
          - .devspace/
          - var
          - docker
          - terraform
          - k8s
        uploadExcludePaths:
          - node_modules
        initialSync: preferLocal
        printLogs: true
    logs: { }
  nginx:
    imageSelector: '${NGINX_IMAGE}'
    sync:
      - path: ./public:app/public
        initialSync: preferLocal
        disableDownload: true
        printLogs: true
    logs: { }

profiles:
  - name: xyz-my-job-generate
    replace:
      images:
        php:
          image: '${PHP_MY_JOB_IMAGE}'
          tags:
            - 'dev-php-my-job-${DEVSPACE_GIT_COMMIT}-${DEVSPACE_TIMESTAMP}'
          dockerfile: docker/web/Dockerfile
          context: .
          target: php-dev
          buildKit: { }
      deployments:
        xyz-my-job-generate:
          namespace: xyz-dev
          kubectl:
            manifests:
              - kustomize/overlays/dev/my-job/
            kustomize: true

images:
  php:
    image: '${PHP_IMAGE}'
    tags:
      - 'dev-php-${DEVSPACE_GIT_COMMIT}-#####'
    dockerfile: docker/web/Dockerfile
    context: .
    target: php-dev
    buildKit: { }

  nginx:
    image: '${NGINX_IMAGE}'
    tags:
      - 'dev-nginx-${DEVSPACE_GIT_COMMIT}-#####'
    dockerfile: docker/web/Dockerfile
    context: .
    target: nginx-dev
    buildKit: { }

...

Local Environment:

DevSpace Version: devspace version 6.2.5
Operating System: linux
ARCH of the OS: AMD64
Kubernetes Cluster:
Cloud Provider: minikube
Kubernetes Version: Client Version: v1.24.3 Kustomize Version: v4.5.4 Server Version: v1.22.12

Anything else we need to know?
It works in devspace 5
pkg/devspace/pipeline/pipeline.go:108

Hello! Thanks for reporting this issue. We will look into a fix, since this worked in DevSpace v5.


New Command /design

Complete the following REQUIRED checkboxes:

[x] I have thoroughly read and understand The Odin Project Contributing Guide

[x] The title of this issue follows the command name: brief description of request format, e.g. /help: add optional @user parameter

The following checkbox is OPTIONAL:

[x] I would like to be assigned this issue to work on it

1. Description of the Feature Request:

Over my time in the discord, I have seen a good amount of people looking for outside resources for design. Or worried too much about "making their project look good" or question if can go into web development because they don't have an eye for design.
I went ahead and wrote a quick post about it here: https://dev.to/baguirre03/web-developer-designer-5aik
I would like to have this be linked in the bot command.
2. Acceptance Criteria:

[ ] Think if this is a necessary command, and thoughts on the short writeup about it.
[ ] create bot command

3. Additional Information:

I think this is something that can be addressed in different ways. But my short writeup gives a few tips as well and think it encapsulates the idea + worry that people may have about designing and their projects.
Any feedback is greatly appreciated as well :)

I like the idea and your write up, but I do have an alternative more elaborate view on this.
I'd personally prefer to see a TOP resource or small lesson on this in the curriculum which we can link to that's a bit more elaborate. I've considered and mentioned wanting to add one for a while but there have been many things that also needed to be done.
Some points I've mentioned on discord that I believe are important to be included. Mainly because they touch every part, from layout, to font and colour choice that people need to design a project, which will be all they need I hope to complete every project and make it look decent. I have a UI/UX connection that showed interest in collaborating on a lesson like that as well from their experience.
So I'm definitely not against it, I just think we could offer more than the insights you've shared in your article.
Would like to hear the opinion of @TheOdinProject/maintainers on this however.

@ManonLef I thought about this as well. I just was unsure if it is something important enough to make it a TOP resource, but I think that a quick resource from TOP or lesson in the curriculum could save learners some time.
I definitely have no UI/UX connection but would still love to be a part of this if it happens. And definitely agree that more can be touched to help people with design. I can also add more points into the article if that is an appropriate action.

A personally feel even a short bit of lesson time on realistic expectations around design-related matters will really help and reduce the number of people coming into the server and asking about design-based resources/worrying about poor design, and thus reduce the need for people to use a bot command/advise to refer to the right lesson.
Especially since the course is focused on making a web developer out of you and not a web designer, it ought to emphasise and help people realise there's a difference and thus a point at which "design" matters are no longer within the direct scope of a web developer per se.

@ManonLef I'm not sold on a UI/UX lesson yet. But knowing you, I'll be convinced eventually lol. I'll suggest to create an issue or a discussion somewhere

@ManonLef , going to start a discussion or issue today regarding this topic.

I don't think we are really in a rush, so I can convert this to a discussion I believe when I'm back at my computer. I don't think this warrants a temporary fix since it's not a priority.

Very supportive of this. A design lesson in the curriculum would be my preference, its a non-brainer for me. Anybody that needs to work with HTML & CSS, will find it a lot easier and more enjoyable with even just a little bit of basic design knowledge in their toolbox.

@ManonLef Should we move this to a curriculum discussion?

@Baguirre03 If you don't mind, I'd like to propose an idea on this lesson since I've discussed this with the team (and the discord as you know) in the past in different ways. Once I have it ready, I will ask the team's input. I have most of the layout and idea on paper already and would really like to see if I can also ask the UI/UX designer that offered to collaborate as well and see if they have time.

Sounds good. Closing this.


More comprehensive error handling

[ ] Make frontend handle the new error as well
[ ] Also do this in listFolders and listSharedDrives

Codecov Report

Merging #743 (da29559) into master (bb2f8d6) will decrease coverage by 1.93%.
The diff coverage is 92.85%.

@@             Coverage Diff             @@
##            master     #743      +/-   ##
===========================================
- Coverage   100.00%   98.06%   -1.94%
===========================================
  Files           11       12       +1
  Lines          133      155      +22
  Branches        16       19       +3
===========================================
+ Hits           133      152      +19
- Misses           0        3       +3

Impacted Files
Coverage Δ

src/backend/move.ts
93.75% <75.00%> (-6.25%)
:arrow_down:

src/backend/move/moveFolderContents.ts
91.30% <87.50%> (-8.70%)
:arrow_down:

src/backend/move/moveFile.ts
100.00% <100.00%> (ø)

src/backend/move/resolveDestinationFolder.ts
100.00% <100.00%> (ø)

src/backend/utils/MoveContext.ts
100.00% <100.00%> (ø)


UI: search criteria nits

Define a search criteria, for example maxDuration, then click on one of the traces to go the detail and then from the detail press the browser back button. On the overview page the maxDuration drop down is expanded, it should not be.
When multiple search criteria are defined they do not keep their order in the search component when going back (browser back) from the trace detail to the search overview.

This is using Chrome 76 on windows, zipkin server 2.16.2

These were all fixed in https://github.com/openzipkin/zipkin/pull/3076


apple/t2: Update linux-t2-arch patches to latest commit

Update includes 7a7e3c123d620fb529115a746fd807be0e643747, which fixes swap_fn_leftctrl on some devices.

I'm closing this as I updated the patches in 70d0c6ad6bd227ca5faecc973910ac2900264ed1.

I'm closing this as I updated the patches in 70d0c6ad6bd227ca5faecc973910ac2900264ed1.


Monero Syncer: Require a minimum sweep balance

Codecov Report

Merging #417 (51dd25d) into main (4ddfb71) will increase coverage by 0.0%.
The diff coverage is 15.4%.

@@          Coverage Diff          @@
##            main    #417   +/-   ##
=====================================
  Coverage   13.2%   13.2%
=====================================
  Files         27      27
  Lines       7800    7813   +13
=====================================
+ Hits        1028    1030    +2
- Misses      6772    6783   +11

Impacted Files
Coverage Δ

src/swapd/runtime.rs
0.0% <0.0%> (ø)

src/syncerd/monero_syncer.rs
0.0% <0.0%> (ø)

src/walletd/runtime.rs
0.0% <0.0%> (ø)

src/syncerd/types.rs
25.5% <16.7%> (-0.3%)
:arrow_down:

src/syncerd/syncer_state.rs
89.9% <100.0%> (+<0.1%)
:arrow_up:

src/error.rs
0.0% <0.0%> (ø)

Continue to review full report at Codecov.

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


Track down likely invalid qscript

There are signs that the qscript we generate, under certain circumstances, may be broken.  When testing with mimir, we saw:

[ ] MatchError
[ ] AssertionError
[ ] A bunch of timeouts indicative of broken plans

Traces can be seen here.  Each query should be examined to see what kind of qscript (educated) is being generated and why it is that mimir is barfing on it.  We can't actually rule out bugs in mimir, but it's more probable for the moment that these are bugs in qsu.

Timeouts and assertion errors are gone now.  Though there are a couple interesting test failures, where we produced incorrect results: https://gist.github.com/b9f54dd8b9b7db692d88f8deba70a62a

Checked, these issues will all be fixed by #3112 and #3079; they're caused by some stray IncludeId's, there's extra map keys and array indices all over the results of every flatten.

Closing this, since the thought process which led to the query initially is now addressed.


Methods

If I don't want to use react, how can I access to ReactPlayer methods"traditionally"?
I need something like:
ReactPlayer.load(url)
ReactPlayer.stop()
ReactPlayer.play()
ReactPlayer.volume(volumeLevel)
ReactPlayer.seekTo(position)
Thank you!

Hi @franz976,
If you don't want to use React, unfortunately it makes no sense to use ReactPlayer. It may be possible to abstract the logic of the player interactions to a vanilla JS library, but this would be a large undertaking and is definitely outside of the scope of this repo.


Provide a build option to sort all info in the schema.xml from the 'reverse' task so that the xml structure is always in guaranteed order

Right now the schema.xml is ordered by when a table/column/index/etc is added to the schema, not alpha order. Well, actually table entries are alpha, but I think that's coincidence.
The problem is that if multiple people work on the DB at the same time, their changes may cause the "reverse" task to generate "changes" to the schema file that don't actually exist. This makes changesets larger than they have to be and adds risk to committing re-built code.
I propose that a new build option be added that allows you to have the reverse task sort all entries alphabetically so that the order of the schema can be counted on to be the same for an "equivalent" database.
I will write this code and submit a patch shortly.

This is a new feature, then we'll add it in Propel2. I agree with your work, and we talked about it in a Propel2 issue.
Let's way for now.


pull request template added

Added a PR template for checklist items:

[ ] closes #xxxx
[ ] tests added
[ ] tests passed
[ ] all linting tests pass
[ ] example notebook updated (if relevant)
[ ] changelog entry

and a description,

Thanks for adding this!


How do you specify the gpu ids to use?

In case, the gpu 0 to 5 have already been used, how could i make use of gpu 6 or 7, I had tried CUDA_VISIBLE_DEVICES=6,7 but seemed NO EFFECT at all, neither did changing the gpu parameter in yml file to range like gpu: 6-7.

I have just added some new functionality. Could you, please, install pip install mlcomp==19.10b or pull from master.
Then, you can specify the environment variable at the start of the worker:
stop the worker: mlcomp-worker stop
start the worker with the specified environment variable: CUDA_VISIBLE_DEVICES=6,7 mlcomp-worker start
Please note, that gpu section in .yml files specifies only gpu count, not the indexes.

@lightforever i tried to make hot-restart the workers after had mlcomp upgraded to version 19.10b0, but was unable to make it work still. The problem is, once the workers stopped, they can't get started again unless I restart the server.

@power0341, pardon for such a pause.
Could you, please try to install pip install mlcomp==19.10rc0 and retry. I think the bug has been fixed.

@lightforever have a look pls

Could you, please:

Provide me with the logs: tail -n 50 ~/mlcomp/logs/log.txt (after not-working restart)

Show the logs tab on the web site

Try to start in the different way: CUDA_VISIBLE_DEVICES=3 mlcomp-worker start --daemon=False --log_level=DEBUG

Try to restart without CUDA_VISIBLE_DEVICES: mlcomp-worker start --daemon=False --log_level=DEBUG. Does the problem repeat?

@power0341, I have managed to reproduce your case. It seems that you are starting mlcomp in such a way: mlcomp-server start (that command starts server and worker). If you want to start only server, there is a command mlcomp-worker start-site :)
Then, mlcomp-worker stop (that command kills worker and server because they are started together) and CUDA_VISIBLE_DEVICES=3 mlcomp-worker start (starts only worker but not server). Am I correct?
The the solution should be: starting with the following command:
CUDA_VISIBLE_DEVICES=3 mlcomp-server start That is it.

yes,   CUDA_VISIBLE_DEVICES=3 mlcomp-server start that works now !!!!!
Thanks a lot

You are welcome!


fix: Handle warnings for default_app_config

they are only defined for django versions < 3.2

closes #1649

I think a couple of other warnings for django41 and django40 can be fixed. would it be wise to do it in a separate commit?

Yeah lets open a new one for 4.0 and 4.1 related warnings.
Then I'll merge this one :-)

Thanks !

i have opened another one for 4.0 and 4.1 warnings at #1656.


If libuv doesn't unwind gracefully log a warning

We added 3 critical logs to see if there was a resource leak happeing during the loop thread shutdown, turns out that during testing its very common for the thread to not end immediately because of the latency of thread pool dispatching (the latency between queuing and execution of the work item). As a result, we log a warning instead of an error.

Fixes https://github.com/aspnet/AspNetCore-Internal/issues/2606

QB Approval was granted for this (just noting for tracking).


Small correctness and clarity mistakes in introduction page

Not a bug! These are just some small correctness and clarity issues with the introduction page text, such as missing commas and used wrong words.

This could be done for all pages in the documentation.


Make use of http.ServeContent

Sorry if I missed something, though ServeHTTP might be improved with https://golang.org/pkg/net/http/#ServeContent (handles mime types based on filename, range requests, last modified caching)

Hi! It's not possible to use ServeContent with compressed data, because you can't seek a GZIP reader. This would mean that the server needs to decompress everything on load, leading to more memory usage and such, which is why I decided against it.
I implemented mime types and modtime/etag caching myself, so it's just range requests that won't work.
Thanks for the suggestion!


HELP WANTED – Endpoint for Ranked 2.0 & Operation: Solar Raid

https://github.com/Seems2Legit/Rainbow-Six-Siege-Player-Stats-API/issues/91#issue-1485588198

Thanks for letting me know about this, i am however dumb enough to not be able to make it work even with all the info that's already in the thread.. 🥲
(Even spent a solid few hours trying to copy, step-by-step, what Daniel has done in r6api.js.. No success there either..)


Unable to get Kasada, Try again ...

Following is shown either immediately, or after a single follower creation.
Unable to get Kasada, Try again ...
Unable to get Kasada, Try again ...
Unable to get Kasada, Try again ...
Unable to get Kasada, Try again ...
Unable to get Kasada, Try again ...
Unable to get Kasada, Try again ...
Unable to get Kasada, Try again ...
Unable to get Kasada, Try again ...
(node:6072) UnhandledPromiseRejectionWarning: RangeError: Maximum call stack size exceeded
    at console.value (internal/console/constructor.js:276:13)
    at console.log (internal/console/constructor.js:344:26)
    at KasdaResolver (/tmp/twitch-account-creator/main.js:51:13)
    at KasdaResolver (/tmp/twitch-account-creator/main.js:52:18)
    at KasdaResolver (/tmp/twitch-account-creator/main.js:52:18)
    at KasdaResolver (/tmp/twitch-account-creator/main.js:52:18)
    at KasdaResolver (/tmp/twitch-account-creator/main.js:52:18)
    at KasdaResolver (/tmp/twitch-account-creator/main.js:52:18)
    at KasdaResolver (/tmp/twitch-account-creator/main.js:52:18)
    at KasdaResolver (/tmp/twitch-account-creator/main.js:52:18)
(node:6072) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an asying a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `-js.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:6072) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are noth a non-zero exit code.

its a spaghetti code, its coded very badly. The call stack grows until it hits a limit and it crashes.
You need to change the KasdaResolver function. One solution for example is setting a failsafe/limit:
const KasdaResolver = async (retryCount = 0, maxRetries = 30) => {
//code
return KasdaResponse;
} catch (e) {
// console.log(e);
}
console.log("Unable to get Kasada, Try again ...")
if (retryCount < maxRetries) {
return await KasdaResolver(retryCount + 1, maxRetries);
} else {
throw new Error("Kasada resolution failed after maximum retries");
}
};


Resetting particular stub

This is more of a question than an issue. I just started using ts-mockito and I am wondering if it is possible to "re-stub" a method to return different value? I am stubbing my method in beforeEach with a value that works for all tests but there is one particular test where I want it to return a different value. I know I can reset the mock, but that would remove ALL of the stubs, while I just want to change one. Is it possible?

Looks like writing a new when() works, I guess it was my code that invalidated it when I tried it at first.

Thanks for info. I Hope You like ts-mockito :)


settings.json get reset and lock down jmm

I remember someone having same issue as this.
Build few jmm few times and running in DEBUG sometimes (had this issue first time after discord chat)
wipe config and not every setting is readded to file  - Why it wipe out config file ?!
I didn't save that setting file but I recall that it only had 1,5 KB or less.
It lacked information about database etc.
The worst part is that the exception is not handled and shutdown jmm with error about null ref.
As currently this happen first time when using DEBUG mode I cannot exclude this from happening on RELEASE build.

I remember having this problem. I did a special case inside the save to not
save the config in case the number of config items where less than 2. It
only happens in debug and alas putting a breakpoint in there will no hit
seems a side effect of manual stopping the debug. I was unable to pinpoint
the cause but seems when you stop somehow it tries to save the already
disposed object.
El Thursday, November 3, 2016, BigRetroMike<EMAIL_ADDRESS>escribió:

I remember someone having same issue as this.
Build few jmm few times and running in DEBUG sometimes (had this issue
first time after discord chat)
wipe config and not every setting is readded to file - Why it wipe out
config file ?!
I didn't save that setting file but I recall that it only had 1,5 KB or
less.
It lacked information about database etc.
The worst part is that the exception is not handled and shutdown jmm with
error about null ref.
As currently this happen first time when using DEBUG mode I cannot exclude
this from happening on RELEASE build.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/japanesemediamanager/jmmserver/issues/503, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABHDbT40XMwRJ42mzrhHqKSlWcUqGsc4ks5q6ii2gaJpZM4Koweq
.

@maxpiva if its a case for only 2 items, than my config had more than 2 items only;
oh. So its because of exiting debug manually when he try to save config back ?
Maybe he should try to save new config to new file like settings_new.json and as last function to
File.Move("settings_new.json","settings.json")
That was manual stoping it or unexpected crash wont overwrite config


⚠ Spryr has degraded performance

In e008d8f, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 5970 ms

Resolved: Spryr performance has improved in 6c55854 after 34 minutes.


Add data change filter handler

Related to https://github.com/nauful/LibUA/pull/123.
Added a delegate to optionally handle data change and event filtering.

This code is not correct: If the filter returns false, it will skip adding but will still flag the queue as overflowed if the queue was at capacity. I'll fix it after merging.

Thanks.
I'm not sure though I fully understand your point on the overflow. I thought the overflow shall be flagged anyhow since the capacity limit has been reached, independently of additional enqueueing - but I shall also admit I am no expert with regards to the OPC UA specification.

Overflow for notifications means that one or more notifications occured but were not published because there was no space in the pending queue to store them. It's a signal from a server to a client that notifications were lost.


Spec Document Cache Writer effect for getAndReplace

From: https://github.com/jsr107/jsr107spec/issues/357
Page 69. Table entry for V getAndReplace(K key, V value) is now:

Yes, if this method returns true

Should be:

Yes, if this method returns a non-null value

Changed it to "Yes (when the key is associated with an existing value)"


Incorrect example in write-your-plugin

In the description just above you state that documents is an array of type { filePath: string, content: DocumentNode } but then in the subsequent example definitions is accessed directly instead of first via content.

Also worth noting that on OperationDefinition name can be undefined and on SchemaDefinition and SchemaExtension name is not present at all meaning the example will crash at runtime.

Thank you!
The codegen core warn when there is an unnamed operation (and also for duplicates).


Add a wiki: Uncomprominsing Mode Wiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://uncompromising-mode.fandom.com
Link to destination (independent) wiki: https://uncompromisingmode.wiki.gg

Will be in the v3.11.1 release, pending approval from Chrome and Firefox


BuildConfig is already defined

Hey
I using android-sdk-plugin with scaloid and yesterday it worked well but after a restart I had problem compiling, since it tried to use scala version 2.10.4 with scaloid 3.6.1, which of course didn't work. Then i upgrade my scalaVersion and the depency problem disappeared. But instead I got this error, which I have no idea how to fix
embo-2:AalborgMTBMarathon henrik$ sbt clean; sbt compile
[info] Loading project definition from /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/project
[info] Set current project to AalborgMTBMarathon (in build file:/Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/)
[success] Total time: 0 s, completed Jan 15, 2015 10:25:45 PM
[info] Loading project definition from /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/project
[info] Set current project to AalborgMTBMarathon (in build file:/Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/)
[info] Updating {file:/Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/}dk-aalborgmtbmarathon...
[info] Resolving jline#jline;2.12 ...
[info] Done updating.
[info] Collecting resources
[info] Performing full resource merge
[info] Processing resources
[info] Regenerating TR.scala because R.java has changed
[info] Rebuilding all classes because R.java has changed
[info] Compiling 24 Scala sources and 4 Java sources to /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/bin/classes...
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/BuildConfig.java:6: BuildConfig is already defined as object BuildConfig
[error] public final class BuildConfig {
[error]                    ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/R.java:10: R is already defined as object R
[error] public final class R {
[error]                    ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:7: TypedResource is already defined as case class TypedResource
[error] case class TypedResource[A](id: Int)
[error]            ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:8: TypedLayout is already defined as case class TypedLayout
[error] case class TypedLayout[A](id: Int)
[error]            ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:10: TR is already defined as object TR
[error] object TR {
[error]        ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:43: TypedViewHolder is already defined as trait TypedViewHolder
[error] trait TypedViewHolder {
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:49: TypedView is already defined as trait TypedView
[error] trait TypedView extends View with TypedViewHolder
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:50: TypedActivityHolder is already defined as trait TypedActivityHolder
[error] trait TypedActivityHolder extends TypedViewHolder
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:51: TypedActivity is already defined as trait TypedActivity
[error] trait TypedActivity extends Activity with TypedActivityHolder
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:52: TypedDialog is already defined as trait TypedDialog
[error] trait TypedDialog extends Dialog with TypedViewHolder
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:54: TypedLayoutInflater is already defined as class TypedLayoutInflater
[error] class TypedLayoutInflater(l: LayoutInflater) {
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:61: TypedResource is already defined as object TypedResource
[error] object TypedResource {
[error]        ^
[error] 12 errors found
[error] (compile:compile) Compilation failed
[error] Total time: 4 s, completed Jan 15, 2015 10:25:54 PM

My build.sbt file is (i think) simple:
import android.Dependencies.AutoLibraryProject
import android.Keys._

localProjects in Android <+= (baseDirectory) {
  b => AutoLibraryProject(b / ".." / "GenericRaceAndroid")
}

android.Plugin.androidBuild

name := "AalborgMTBMarathon"

platformTarget in Android := "android-19"

javacOptions ++= Seq("-Xlint:unchecked")

scalaVersion := "2.11.4"

scalacOptions ++= Seq("-unchecked", "-deprecation", "-feature")

libraryDependencies ++= Seq(
   "org.scalaj" % "scalaj-time_2.10.0-M7" % "0.6",
   "org.scaloid" %% "scaloid" % "3.6.1-10" withSources() withJavadoc()
)

unmanagedBase := baseDirectory.value / "libs"

useProguard in Android := true

proguardOptions in Android ++= Seq(
  "-dontobfuscate",
  "-dontoptimize"
)

apkbuildExcludes in Android ++= Seq("META-INF/LICENSE.txt", "META-INF/NOTICE.txt")

ideaExcludeFolders ++= Seq (
  ".idea",
  ".idea_modules",
  "target",
  "bin"
)

Any idea's how to fix this?

Delete all pre-generated sources, if you're using autobuild and also
applying androidBuild, then you will need to deduplicate the source
generators.
On Thu, Jan 15, 2015 at 1:36 PM, Henrik Kirk<EMAIL_ADDRESS>wrote:

Hey
I using android-sdk-plugin with scaloid and yesterday it worked well but
after a restart I had problem compiling, since it tried to use scala
version 2.10.4 with scaloid 3.6.1, which of course didn't work. Then i
upgrade my scalaVersion and the depency problem disappeared. But instead I
got this error, which I have no idea how to fix
embo-2:AalborgMTBMarathon henrik$ sbt clean; sbt compile
[info] Loading project definition from /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/project
[info] Set current project to AalborgMTBMarathon (in build file:/Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/)
[success] Total time: 0 s, completed Jan 15, 2015 10:25:45 PM
[info] Loading project definition from /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/project
[info] Set current project to AalborgMTBMarathon (in build file:/Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/)
[info] Updating {file:/Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/}dk-aalborgmtbmarathon...
[info] Resolving jline#jline;2.12 ...
[info] Done updating.
[info] Collecting resources
[info] Performing full resource merge
[info] Processing resources
[info] Regenerating TR.scala because R.java has changed
[info] Rebuilding all classes because R.java has changed
[info] Compiling 24 Scala sources and 4 Java sources to /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/bin/classes...
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/BuildConfig.java:6: BuildConfig is already defined as object BuildConfig
[error] public final class BuildConfig {
[error]                    ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/R.java:10: R is already defined as object R
[error] public final class R {
[error]                    ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:7: TypedResource is already defined as case class TypedResource
[error] case class TypedResource[A](id: Int)
[error]            ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:8: TypedLayout is already defined as case class TypedLayout
[error] case class TypedLayout[A](id: Int)
[error]            ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:10: TR is already defined as object TR
[error] object TR {
[error]        ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:43: TypedViewHolder is already defined as trait TypedViewHolder
[error] trait TypedViewHolder {
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:49: TypedView is already defined as trait TypedView
[error] trait TypedView extends View with TypedViewHolder
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:50: TypedActivityHolder is already defined as trait TypedActivityHolder
[error] trait TypedActivityHolder extends TypedViewHolder
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:51: TypedActivity is already defined as trait TypedActivity
[error] trait TypedActivity extends Activity with TypedActivityHolder
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:52: TypedDialog is already defined as trait TypedDialog
[error] trait TypedDialog extends Dialog with TypedViewHolder
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:54: TypedLayoutInflater is already defined as class TypedLayoutInflater
[error] class TypedLayoutInflater(l: LayoutInflater) {
[error]       ^
[error] /Users/henrik/Private/AalborgMTBMarathon/AndroidBuild/AalborgMTBMarathon/gen/dk/aalborgmtbmarathon/TR.scala:61: TypedResource is already defined as object TypedResource
[error] object TypedResource {
[error]        ^
[error] 12 errors found
[error] (compile:compile) Compilation failed
[error] Total time: 4 s, completed Jan 15, 2015 10:25:54 PM
My build.sbt file is (i think) simple:
import android.Dependencies.AutoLibraryProject
import android.Keys._
localProjects in Android <+= (baseDirectory) {
b => AutoLibraryProject(b / ".." / "GenericRaceAndroid")
}
android.Plugin.androidBuild
name := "AalborgMTBMarathon"
platformTarget in Android := "android-19"
javacOptions ++= Seq("-Xlint:unchecked")
scalaVersion := "2.11.4"
scalacOptions ++= Seq("-unchecked", "-deprecation", "-feature")
libraryDependencies ++= Seq(
"org.scalaj" % "scalaj-time_2.10.0-M7" % "0.6",
"org.scaloid" %% "scaloid" % "3.6.1-10" withSources() withJavadoc()
)
unmanagedBase := baseDirectory.value / "libs"
useProguard in Android := true
proguardOptions in Android ++= Seq(
"-dontobfuscate",
"-dontoptimize"
)
apkbuildExcludes in Android ++= Seq("META-INF/LICENSE.txt", "META-INF/NOTICE.txt")
ideaExcludeFolders ++= Seq (
".idea",
".idea_modules",
"target",
"bin"
)
Any idea's how to fix this?
—
Reply to this email directly or view it on GitHub
https://github.com/pfn/android-sdk-plugin/issues/140.

Im only using applying androidBuild (as far as I know).
rm -r gen/* didn't have any affect.
Im a missing something.

so you didn't gen-android?
find . -name BuildConfig.java
Either you have it duplicate, or you use AutoBuild + androidBuild

find . -name BuildConfig.java
./gen/dk/aalborgmtbmarathon/BuildConfig.java
Ahh im using Intellij which creating BuildConfig. So where can i find documentation on deduplicating source generators?

Project Structure -> Modules -> Your Project -> Android -> Generated
Sources -> Generate sources automatically
On Thu, Jan 15, 2015 at 11:18 PM, Henrik Kirk<EMAIL_ADDRESS>wrote:

find . -name BuildConfig.java
./gen/dk/aalborgmtbmarathon/BuildConfig.java
Ahh im using Intellij which creating BuildConfig. So where can i find
documentation on deduplicating source generators?
—
Reply to this email directly or view it on GitHub
https://github.com/pfn/android-sdk-plugin/issues/140#issuecomment-70216711
.

Even still, sources in the same directory should not conflict.
On Thu, Jan 15, 2015 at 11:19 PM, Perry Nguyen<EMAIL_ADDRESS>wrote:

Project Structure -> Modules -> Your Project -> Android -> Generated
Sources -> Generate sources automatically
On Thu, Jan 15, 2015 at 11:18 PM, Henrik Kirk<EMAIL_ADDRESS>wrote:

find . -name BuildConfig.java
./gen/dk/aalborgmtbmarathon/BuildConfig.java
Ahh im using Intellij which creating BuildConfig. So where can i find
documentation on deduplicating source generators?
—
Reply to this email directly or view it on GitHub
https://github.com/pfn/android-sdk-plugin/issues/140#issuecomment-70216711
.

Sorry to say that it didn't make much of a difference. Even removed the localProject path from the build.sbt.
Should i downgrade to another version of scala 2.11.1-3?

You never answered whether or not you used gen-android, if you did, you must not use androidBuild

See #88

Sorry overlooked that part of your answer. I did indeed, copied it from a scaloid example project a couple of days ago. And removing
android.Plugin.androidBuild
then solved the issue.
Thx for great help and project.


Release google-cloud-workflows 0.2.0. Missing workflows_client.location_path

Environment details

OS type and version: OSX
Python version: python --version python37
pip version: pip --version: pip 20.1.1
google-cloud-workflows version: pip show google-cloud-workflows: Version: 0.1.0

Steps to reproduce

Try to use the function workflows_client.location_path(PROJECT, LOCATION) but you'll see a 'WorkflowsClient' object has no attribute 'location_path' error
You can use the workflows_client.workflow_path(PROJECT, LOCATION, WORKFLOW) https://github.com/googleapis/python-workflows/blob/ccddf0607d6af58ccf52e33ee1ff735a8034559a/google/cloud/workflows_v1beta/services/workflows/client.py#L149
Observe there's a common_location_path on GitHub, but we can't use it in our program. Why?

It looks like this function is only on GitHub, but not available in the latest package on pypi – 0.1.0.

Can we cut a new version of this library?
We have a branch: https://github.com/googleapis/python-workflows/tree/release-v0.2.0 and looks like there's a PR: https://github.com/googleapis/python-workflows/pull/14
Do we just need to merge that PR?
CC: @busunkim96

0.2.0 is now released. https://pypi.org/project/google-cloud-workflows/

0.2.0 is now released. https://pypi.org/project/google-cloud-workflows/

Thanks.

Thanks.


Jc/tuts

This PR adds the tutorials back into the main branch in /doc. They have been updated for changes to the API. Additionally, a bit of renaming has gone on to make concepts/APIs clearer to understand.
This relies on #82 which relies on #81.

@smswz Made changes, merge is on you if satisfactory


Seperate Circuit Elements tab and Properties tab

Put Properties on the right of the screen. This will make editing properties simplier(by not having to scroll down to see the properties when an element tab is open)

@armudgal I would like to work on this issue. Please assign me this.

I'll do it. Is that okay?

Go ahead, try different options and we will review.


Add flags & premium type to User

Hey @vince614 - it's great to see your pull request. I have a single question - why the isBot and other getters like isMfaEnabled have changed to non-strict return values? All other changes are good.

Hay @chonsser, I remove them because they are not mandatory.

Hey @vince614 - your pull request broke the tests. I've updated the tests to match your new features and added an additional test check on every new pull request. The latest version of this OAuth provider lib is v1.1.0 which requires PHP 7.3.
Cheers!


unable to find SetCompatibilityVersion

Any suggestions why it cant find SetCompatibilityVersion?
services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_1);

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

ID: 583ae3e7-5915-f22b-e54c-6c100cf2a7da
Version Independent ID: 95f2549e-29f9-e31a-b4d0-432b971643ff
Content: Create a Web API with ASP.NET Core and Visual Studio for Windows
Content Source: aspnetcore/tutorials/first-web-api.md
Product: asp.net-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

nvm, its because im running 2.0

here is the link to install 2.1  https://www.microsoft.com/net/download/visual-studio-sdks

@dstruve You're correct that 2.1 is required to use the SetCompatibilityVersion method.


Failure to build piral instance in Windows and node18

Bug Report
For more information, see the CONTRIBUTING guide.
Prerequisites

[x] Can you reproduce the problem in a MWE?
[x] Are you running the latest version?
[x] Did you perform a search in the issues?

Environment Details and Version

piral-cli / piral framework (v1.1.0)
Windows
node18 and npm9

Description
After setting up a new piral instance, and building the repo (to build the emulator and the distribution), the build returns an error, not being able to find dependencies/modules.
Steps to Reproduce

In Windows, with node18 installed, set up a new piral instance:

npm init piral-instance -- --target simple-piral --defaults
cd simple-piral

npm install and build the piral instance:

npm ci
npx piral build --bundler webpack5

Expected behavior
The emulator and distribution bundles get built.
Actual behavior
The following errors are presented:
ERROR in ./node_modules/piral-core/app.codegen 2:4-50
Module not found: Error: Can't resolve '..\tslib\tslib.es6.mjs' in 'C:\repos\local\simple-piral\node_modules\piral-core'
Did you mean './..\tslib\tslib.es6.mjs'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
 @ ./node_modules/piral-core/esm/helpers.js 3:0-70 15:4-21 16:4-21
 @ ./node_modules/piral-core/esm/index.js 2:0-26 2:0-26
 @ ./node_modules/piral/esm/index.js 1:0-27 1:0-27
 @ ./src/index.tsx 9:0-65 13:15-29 18:30-47 28:46-51

ERROR in ./node_modules/piral-core/app.codegen 3:0-41
Module not found: Error: Can't resolve '..\react\index.js' in 'C:\repos\local\simple-piral\node_modules\piral-core'
Did you mean './..\react\index.js'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
 @ ./node_modules/piral-core/esm/helpers.js 3:0-70 15:4-21 16:4-21
 @ ./node_modules/piral-core/esm/index.js 2:0-26 2:0-26
 @ ./node_modules/piral/esm/index.js 1:0-27 1:0-27
 @ ./src/index.tsx 9:0-65 13:15-29 18:30-47 28:46-51

ERROR in ./node_modules/piral-core/app.codegen 4:0-45
Module not found: Error: Can't resolve '..\react-dom\index.js' in 'C:\repos\local\simple-piral\node_modules\piral-core'
Did you mean './..\react-dom\index.js'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
 @ ./node_modules/piral-core/esm/helpers.js 3:0-70 15:4-21 16:4-21
 @ ./node_modules/piral-core/esm/index.js 2:0-26 2:0-26
 @ ./node_modules/piral/esm/index.js 1:0-27 1:0-27
 @ ./src/index.tsx 9:0-65 13:15-29 18:30-47 28:46-51

ERROR in ./node_modules/piral-core/app.codegen 5:0-60
Module not found: Error: Can't resolve '..\react-router\esm\react-router.js' in 'C:\repos\local\simple-piral\node_modules\piral-core'
Did you mean './..\react-router\esm\react-router.js'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
 @ ./node_modules/piral-core/esm/helpers.js 3:0-70 15:4-21 16:4-21
 @ ./node_modules/piral-core/esm/index.js 2:0-26 2:0-26
 @ ./node_modules/piral/esm/index.js 1:0-27 1:0-27
 @ ./src/index.tsx 9:0-65 13:15-29 18:30-47 28:46-51

ERROR in ./node_modules/piral-core/app.codegen 6:0-68
Module not found: Error: Can't resolve '..\react-router-dom\esm\react-router-dom.js' in 'C:\repos\local\simple-piral\node_modules\piral-core'
Did you mean './..\react-router-dom\esm\react-router-dom.js'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
 @ ./node_modules/piral-core/esm/helpers.js 3:0-70 15:4-21 16:4-21
 @ ./node_modules/piral-core/esm/index.js 2:0-26 2:0-26
 @ ./node_modules/piral/esm/index.js 1:0-27 1:0-27
 @ ./src/index.tsx 9:0-65 13:15-29 18:30-47 28:46-51

5 errors have detailed information that is not shown.
Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.

webpack 5.88.2 compiled with 5 errors in 18134 ms
✖ [0174] The bundling process failed: Invalid input.
+ Find detailed descriptions at https://docs.piral.io/code/search

Possible Origin/Solution
First attempt of setting webpack configuration to set preferRelative did not fix the problem.
module.exports = function (config) {
  config.resolve.preferRelative = true
}

In the piral-core codegen module, it looks like the import statements are being generated with the relative paths of the dependencies like react, react-dom, etc.  The relative paths are generated using the platform path separator (backslash in windows).  Since these relative paths are to be used in import statements, they should be normalized back to the posix/slash path separator and nodejs would process the path correctly, regardless of the platform.
https://github.com/smapiot/piral/blob/11a570fc7fbacb6c663f4a614d976730cb8d69be/src/framework/piral-core/src/tools/codegen.ts#L69-L70

Thanks for the report and the associated analysis - it helps a lot!
A fix for this is out in the preview and will be included in the 1.2.0 release coming this week. In the meantime you can use the next version.


Split the documentation pages into User guide and reference

This still needs some polishing. Before I invest too much time into it, I'd like to hear your opinion @shumonsharif and @famod whether the restructuring of the docs into

User guide containing some recipes for solving typical CXF related tasks and
Reference - a list of our extensions and their config options

makes sense to you?
You can view the generated site locally by running
$ cd docs
$ mvn test
$ google-chrome target/site/quarkus-cxf/dev/index.html

@shumonsharif @famod in case you have Windows or Mac, it would be great to know whether cd docs && mvn clean test works for you?
I would not necessarily want to fix it. I'd say setting some Junit assumes for skipping on Max/Windows would fine. WDYT?

BTW, the CI job is now publishing the generated Antora site as a zip file:

Hi @ppalaga Sorry for the late response, it's been a hectic couple days at the day job.  This is looking great, and I'm all for it; I think it's a simpler layout than we previously had - and therefore more consumable.
On my Mac, cd docs && mvn clean test works fine, and the pages are generated without issue.
One note worth considering - we did have an open ticket for a quarkus-cxf quickstart (https://github.com/quarkiverse/quarkus-cxf/issues/399) - I personally learn much faster about any given framework or extension by looking at example code, not as much through docs.  I'm wondering if it's worth revisiting the quickstart issue while also updating the docs.

On my Mac, cd docs && mvn clean test works fine, and the pages are generated without issue.

Great to hear that!
Now, let's wait for the first person who will complain that it does not work on Windows ;-)

we did have an open ticket for a quarkus-cxf quickstart (#399) - I personally learn much faster about any given framework or extension by looking at example code, not as much through docs. I'm wondering if it's worth revisiting the quickstart issue while also updating the docs.

I am all for improving the learning experience by all means. I got a bit lost by reading #399. Could you please sum up what is the latest objective there?

The last iteration ending with fa04a19 is still not perfect from my PoV, but already good enough to be merged.
It would be great if somebody could review the content.

I am all for improving the learning experience by all means. I got a bit lost by reading #399. Could you please sum up what is the latest objective there?

Hey @ppalaga The basic idea was to provide sample project(s) that would supplement the documentation.  So, if for example, a user wanted to see a WS-Trust implementation and how it would work with quarkus-cxf, there would be a pre-canned project they can refer to without going through all the docs or having to browse through the integration tests.
As far as summing up #399, the initial intent was to build out a set of codestarts (Andy's blog write-ups sums up codestarts nicely).  That would have been really nice if we could integrate, but after all the back-and-forth, we agreed a set of quickstarts may be more appropriate - like Quarkus provides here.

Got that yesterday on Winodws:
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.031 s <<< FAILURE! - in io.quarkiverse.cxf.doc.it.AntoraTest
[ERROR] antora  Time elapsed: 0.016 s  <<< ERROR!
java.lang.UnsupportedOperationException: View 'unix' not available
        at java.base/sun.nio.fs.AbstractFileSystemProvider.readAttributes(AbstractFileSystemProvider.java:93)
        at java.base/java.nio.file.Files.readAttributes(Files.java:2084)
        at java.base/java.nio.file.Files.getAttribute(Files.java:1983)
        at io.quarkiverse.cxf.doc.it.AntoraTest.antora(AntoraTest.java:47)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:568)
        at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)

But I don't mind as I'm working on Ubuntu in WSL2 (private PC) or Ubuntu natively (work laptop) anyway.

But I don't mind as I'm working in Ubuntu via WSL2 (private PC) or Ubuntu natively (work laptop) anyway.

My only concern with the Windows build would be not so much for the core group here, but more to allow public contributors to be able to participate with ease.  Granted, we don't get too many such PRs ... :) I think we can skip the test on Windows as @ppalaga suggested, but still curious why the unix uid is needed to begin with?

So, I found the answer to my question at link below, seems like it's to address volume mounts and SELinux issues.
https://docs.antora.org/antora/latest/antora-container/#option-flags
I'm now wondering if it's possible to to simply catch all exceptions when trying to identify the uid, and use the uid value only if it exists.  I believe that should should allow the test / doc-generation to also work on Windows without issues.

As far as summing up #399, the initial intent was to build out a set of codestarts (Andy's blog write-ups sums up codestarts nicely). That would have been really nice if we could integrate, but after all the back-and-forth, we agreed a set of quickstarts may be more appropriate - like Quarkus provides here.

Thanks for explaining. Mainly the role of codestarts was unclear to me.
As a maintainer of several current or past projects, where a separate quickstarts repo played a role, I must say I am not a big fan of them. It is a bit of overhead to keep them up to date with the main repo (CI) and a few more steps when releasing. I like it much more when integration tests are sold as quickstarts. Those are in the same source tree, they must work before and after each merged change, and it is only good (for both maintainers and end users) if they are well documented through READMEs and inline comments. Snippets from those can also be used in Antora docs, which I started doing with this PR.
Having said that I won't block you or anybody else from creating a separate Quickstarts repo. It would be nice if the additional release steps could be documented somewhere (a new release guide document maybe?)

As a maintainer of several current or past projects, where a separate quickstarts repo played a role, I must say I am not a big fan of them. It is a bit of overhead to keep them up to date with the main repo (CI) and a few more steps when releasing. I like it much more when integration tests are sold as quickstarts. Those are in the same source tree, they must work before and after each merged change, and it is only good (for both maintainers and end users) if they are well documented through READMEs and inline comments. Snippets from those can also be used in Antora docs, which I started doing with this PR.

Makes sense - I thought of some of these issues, but never having actually implemented any quickstarts, I wasn't sure on how the release process would work exactly ... definitely seems like more trouble than it's worth.  Thanks for your input on this!


Unable to see OpenTelemetry Span Events in AWS X-Ray

Describe the bug
When trying to add a Span Event to a span using the span.current.addEvent() method in OpenTelemetry, the event is not visible in AWS X-Ray. We can see our custom spans but none of the Events.
Steps to reproduce
We are using a Java SpringBoot application using the spring-boot-starter-parent version 2.4.5. We are using the opentelemetry-otlp-exporter-starter 1.4.1-alpha dependency.
We created a docker image for our application that adds the aws-opentelemetry-agent.jar (v1.4.1) into the image when we build it. We then run as a javaagent when the image is deployed. We deploy our application to ECS Fargate and we then run the aws-otel-collector as a sidecar with the default configuration.
What did you expect to see?
We expected to see our span events either as annotations or metadata in our spans.
What did you see instead?
We just saw our custom spans without any Span Events.
Additional context
We are also experiencing the same behaviour when we use Elastic as the backend for observability. This is due to this issue

Thanks for filing this @rcooper85 - indeed similar to Elastic, the X-Ray data model itself doesn't contain the concept of events so supporting them will be a big change including the backend. Events can be pretty interesting so hopefully we can add support for them but it will take some time.

Hi @anuraaga - thank you for your quick response on this. Is that the same for setStatus for spans too? As we are not seeing the status in X-Ray either when we use, for example:  Span.current().setStatus(StatusCode.OK, "Order Received");


chore: release main

:robot: I have created a release beep boop
cache: 0.3.0
0.3.0 (2023-08-05)
Features

terminals: add support for terminal paths (#236) (3fba7f6)

codegen: 0.5.0
0.5.0 (2023-08-05)
Features

codegen: derive macro for implementing FromSaved (#243) (48acae0)
terminals: add support for terminal paths (#236) (3fba7f6)

Dependencies

The following workspace dependencies were updated

dependencies

examples bumped from 0.1.0 to 0.2.0

dev-dependencies

substrate bumped from <=0.4.0 to <=0.5.0
sky130pdk bumped from <=0.4.0 to <=0.5.0
spectre bumped from <=0.4.0 to <=0.5.0

config: 0.2.2
Dependencies

The following workspace dependencies were updated

dependencies

cache bumped from 0.2.1 to 0.3.0

examples: 0.2.0
0.2.0 (2023-08-05)
Features

codegen: derive macro for implementing FromSaved (#243) (48acae0)

Dependencies

The following workspace dependencies were updated

dev-dependencies

substrate bumped from <=0.4.0 to <=0.5.0
sky130pdk bumped from <=0.4.0 to <=0.5.0
spectre bumped from <=0.4.0 to <=0.5.0

pathtree: 0.2.0
0.2.0 (2023-08-05)
Features

terminals: add support for terminal paths (#236) (3fba7f6)

scir: 0.4.0
0.4.0 (2023-08-05)
Features

terminals: add support for terminal paths (#236) (3fba7f6)

sky130pdk: 0.5.0
0.5.0 (2023-08-05)
Features

terminals: add support for terminal paths (#236) (3fba7f6)

Dependencies

The following workspace dependencies were updated

dependencies

substrate bumped from 0.4.0 to 0.5.0
spectre bumped from 0.4.0 to 0.5.0

spectre: 0.5.0
0.5.0 (2023-08-05)
Features

terminals: add support for terminal paths (#236) (3fba7f6)

Dependencies

The following workspace dependencies were updated

dependencies

cache bumped from 0.2.1 to 0.3.0
scir bumped from 0.3.0 to 0.4.0
substrate bumped from 0.4.0 to 0.5.0

spice: 0.3.0
0.3.0 (2023-08-05)
Features

terminals: add support for terminal paths (#236) (3fba7f6)

Dependencies

The following workspace dependencies were updated

dependencies

scir bumped from 0.3.0 to 0.4.0

substrate: 0.5.0
0.5.0 (2023-08-05)
Features

codegen: derive macro for implementing FromSaved (#243) (48acae0)
terminals: add support for terminal paths (#236) (3fba7f6)

Dependencies

The following workspace dependencies were updated

dependencies

config bumped from 0.2.1 to 0.2.2
examples bumped from 0.1.0 to 0.2.0
cache bumped from 0.2.1 to 0.3.0
codegen bumped from 0.4.0 to 0.5.0
scir bumped from 0.3.0 to 0.4.0
pathtree bumped from 0.1.0 to 0.2.0
spice bumped from 0.2.0 to 0.3.0
type_dispatch bumped from 0.1.0 to 0.2.0

dev-dependencies

sky130pdk bumped from <=0.4.0 to <=0.5.0
spectre bumped from <=0.4.0 to <=0.5.0

tests: 0.0.0
Dependencies

The following workspace dependencies were updated

dependencies

substrate bumped from 0.4.0 to 0.5.0
scir bumped from 0.3.0 to 0.4.0
cache bumped from 0.2.1 to 0.3.0
spice bumped from 0.2.0 to 0.3.0
spectre bumped from 0.4.0 to 0.5.0
sky130pdk bumped from 0.4.0 to 0.5.0

type_dispatch: 0.2.0
0.2.0 (2023-08-05)
Features

terminals: add support for terminal paths (#236) (3fba7f6)

Dependencies

The following workspace dependencies were updated

dependencies

type_dispatch_macros bumped from 0.1.0 to 0.2.0

type_dispatch_macros: 0.2.0
0.2.0 (2023-08-05)
Features

terminals: add support for terminal paths (#236) (3fba7f6)

Dependencies

The following workspace dependencies were updated

dev-dependencies

type_dispatch bumped from <=0.1.0 to <=0.2.0

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/codegen-v0.5.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/config-v0.2.2 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/examples-v0.2.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/cache-v0.3.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/pathtree-v0.2.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/scir-v0.4.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/spice-v0.3.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/type_dispatch-v0.2.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/type_dispatch_macros-v0.2.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/sky130pdk-v0.5.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/substrate-v0.5.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/spectre-v0.5.0 :sunflower:


Old connect links are broken

This is very useful to view old routes posted on discord for example

Probably https://github.com/commaai/connect/issues/520 instead


Game Test API crashing regular runs with seperated source sets.

When separating gametest code into its own source set, as the javadocs suggest, the testing library still trys to load the gametest entrypoint during regular runs causing a crash.
Expected Behaviour
The testing library only attempts to load quilt:game_test entrypoints when the quilt.game_test property is set to true.
Actual Behaviour
The testing library always trys to load quilt:game_test entrypoints during its own init entrypoint without checking if its a testing run.
Replication Steps

Clone https://github.com/JustPyrrha/qsl-testing-bug (minimal replication project)
Run either of the standard client or server runs.

Tested in both dev and prod environments. Dev using the above project with only qsl_base and testing (6.1.2+1.20.1), and prod using the above project and the latest qsl from modrinth (7.4.0+0.90.0-1.20.1).

You're supposed to create a new QMJ file in the separate source set as if it was a new mod (like it is done in QSL).

ah that makes more sense, though the separate qmj isn't mentioned in the javadocs so that might be worth updating.
 *

 *
Get Started

 * Writing tests for your mod is relatively simple: create a new class that extends {@link org.quiltmc.qsl.testing.api.game.QuiltGameTest}, and add it
 * as an entrypoint of key {@value org.quiltmc.qsl.testing.api.game.QuiltGameTest#ENTRYPOINT_KEY}.
 *


adds automl-text-sentiment-analysis-online notebook

Checklist for official notebooks :

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[x] This notebook has been added to the CODEOWNERS file under # Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

/gcburn

/gcburn

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun

/gcbrun


make enabliong statsd configurable

after this pr, I'd like to add prometheus support

@spikelu2016 please feel free to let me know if # ave

Can we make this backward compatible with people having StatsProvider set? This change is a breaking change.

if StatsEnabled is set to false, we will have nil pointer dereference error. can you help ensure that even when StatsEnabled is set to false, this error does not happen?

Thanks for pointing this. I will add an interface and makes statsd the default implementation.

Done.


The "greater than" sign

The greater than sign (>) provides information that shouldn't just be discarded. The docs state:

When query user returns information, a greater than (>) symbol is displayed before the current session.

I'm thinking that when that symbol exists on a row, I should add a [boolean] IsCurrentSession property and set it to $true.  Not having it at all on other sessions will serve the same purpose as setting it to $false. So, this example would become something like:
Server           : localhost
Username         : vertigoray
IsCurrentSession : True
Sessionname      : console
Id               : 1
State            : Active
IdleTime         : 03:11:00
LogonTime        : 7/26/2018 7:29:00 PM

or when the symbol doesn't exist on the row; it would stay the same as before:
Server      : localhost
Username    : vertigoray
Sessionname : console
Id          : 1
State       : Active
IdleTime    : 03:11:00
LogonTime   : 7/26/2018 7:29:00 PM

Turns out targeting a server strips the >:
PS C:\> C:\WINDOWS\system32\quser.exe /SERVER:localhost
 USERNAME              SESSIONNAME        ID  STATE   IDLE TIME  LOGON TIME
 vertigoray            console             1  Active      none   4/13/2019 3:18 PM
PS C:\> C:\WINDOWS\system32\quser.exe
 USERNAME              SESSIONNAME        ID  STATE   IDLE TIME  LOGON TIME
>vertigoray            console             1  Active      none   4/13/2019 3:18 PM

Will need to make adjustments for this as well ...


Properties of extensions that are containers should have Kotlin DSL accessors for existing elements

so they are easily discoverable and configurable.
Example below configuring the Android Gradle Plugin.
Expected Behavior
plugins {
  id("com.android.application")
}

android {
    buildTypes {
        debug {
            // ...
        }
        release {
            // ...
        }
    }
    signingConfigs {
        debug {
            // ...
        }
        release {
            // ...
        }
    }
}

Current Behavior
plugins {
  id("com.android.application")
}

android {
    buildTypes {
        named("debug") {
            // ...
        }
        named("release") {
            // ...
        }
    }
    signingConfigs {
        named("debug") {
            // ...
        }
        named("release") {
            // ...
        }
    }
}

Open questions

project schema collection rules
performance impact
adding more element accessors raises the chance of accessor target conflict if container type isn't specialized, and there's no public api to do it

Implementation notes
Implementation wise the ProjectSchemaProvider should be enhanced to iterate on the properties of each extension and handle those that are assignable to NamedDomainObjectContainer.

This also affects a plugin I wrote for a customer and makes it harder to discover its functionality.

This also makes the new JVM Test Suites feature rather ugly to use in Kotlin DSL. I should be able to write this:
suites.getByName<JvmTestSuite>("test").useJUnitJupiter()
like this:
suites.test.useJUnitJupiter()

Another use-case:
Publishing precompiled script plugins requires to add some metadata, like displayName and description. To configure these metadata, you need to call gradlePlugin.plugins.named("mypackage.myid") {}.
With generated accessors, you don't need to specify the generated id again but can simple use the accessor:
gradlePlugin.plugins.`mypackage.myid` {}

Doesn't this already work? The Kotlin DSL primer states:

Elements in project-extension containers (for example the source sets contributed by the Java Plugin that are added to the sourceSets container)

It works for project extensions added via project.extensions.create(...). But not for nested containers inside the extensions like the before mentioned testing.suites - there are no accessors for the elements in suites.


change case defaults, fix bugs

Closes #803
cc @jonathanpallant, @Emilgardis

I think it would be worth with this to add #[doc(alias = "<peripheral name in svd>")]

Looks like starting _ sometimes incompatible with PascalCase.

/ci diff pr

I don't have ideas what to do with Freescale.

ugh, why does the /ci triggers fail here, I have no issues with https://github.com/cross-rs/cross/blob/main/.github/workflows/try.yml ...
/ci diff pr

ugh, why does the /ci triggers fail here, I have no issues with

Are you sure someone else except you can run this?

There's nothing in it that would prohibit other members to run it, the only check is that the user making the comment is a member, which we both are

/ci diff pr

    {
      "id": "IC_kwDOBDHJwM5yw0Sf",
      "author": {
        "login": "burrbull"
      },
      "authorAssociation": "MEMBER",

I don't understand...
/ci diff pr

@Emilgardis run ci yet one time, please.

can you try it, this time put some text before

/ci diff pr

/ci diff --pager "git diff --no-index" pr

original behaviour would be

--ident-format field_reader::c:_R
--ident-format field_writer::c:_W
--ident-format enum_name::c:_A
--ident-format enum_write_name::c:_AW
--ident-format enum_value::c:
--ident-format interrupt::c:
--ident-format cluster::c:
--ident-format cluster_accessor::c:
--ident-format cluster_mod::s:
--ident-format register::c:
--ident-format register_spec::c:_SPEC
--ident-format register_accessor::c:
--ident-format register_mod::s:
--ident-format peripheral::c:
--ident-format peripheral_sigleton::c:
--ident-format peripheral_mod::s:
--ident-format peripheral_feature::c:

Seems like that's all

Lets try
/ci diff pr

I don't understand why you're not able to trigger it. Might just have to switch to a check in the binary instead of relying on githubs actions environment doing things correctly...
/ci diff pr
/ci diff --current "@pr --ident-format field_reader::c:_R --ident-format field_writer::c:_W --ident-format enum_name::c:_A --ident-format enum_write_name::c:_AW --ident-format enum_value::c: --ident-format interrupt::c: --ident-format cluster::c: --ident-format cluster_accessor::c: --ident-format cluster_mod::s: --ident-format register::c: --ident-format register_spec::c:_SPEC --ident-format register_accessor::c: --ident-format register_mod::s: --ident-format peripheral::c: --ident-format peripheral_singleton::c: --ident-format peripheral_mod::s: --ident-format peripheral_feature::c:"

/ci diff pr
/ci diff --current "@pr --ident-format field_reader::c:_R --ident-format field_writer::c:_W --ident-format enum_name::c:_A --ident-format enum_write_name::c:_AW --ident-format enum_value::c: --ident-format interrupt::c: --ident-format cluster::c: --ident-format cluster_accessor::c: --ident-format cluster_mod::s: --ident-format register::c: --ident-format register_spec::c:_SPEC --ident-format register_accessor::c: --ident-format register_mod::s: --ident-format peripheral::c: --ident-format peripheral_singleton::c: --ident-format peripheral_mod::s: --ident-format peripheral_feature::c:"

/ci diff -c stm32f103 --current "@pr --ident-format field_reader::c:_R --ident-format field_writer::c:_W --ident-format enum_name::c:_A --ident-format enum_write_name::c:_AW --ident-format enum_value::c: --ident-format interrupt::c: --ident-format cluster::c: --ident-format cluster_accessor::c: --ident-format cluster_mod::s: --ident-format register::c: --ident-format register_spec::c:_SPEC --ident-format register_accessor::c: --ident-format register_mod::s: --ident-format peripheral::c: --ident-format peripheral_singleton::c: --ident-format peripheral_mod::s: --ident-format peripheral_feature::c:"

oops, actual should be
--ident-format field_reader::c:_R
--ident-format field_writer::c:_W
--ident-format enum_name::c:_A
--ident-format enum_write_name::c:_AW
--ident-format enum_value::c:
--ident-format interrupt::c:
--ident-format cluster::c:
--ident-format cluster_accessor::s:
--ident-format cluster_mod::s:
--ident-format register::c:
--ident-format register_spec::c:_SPEC
--ident-format register_accessor::s:
--ident-format register_mod::s:
--ident-format peripheral::c:
--ident-format peripheral_singleton::c:
--ident-format peripheral_mod::s:
--ident-format peripheral_feature::c:

/ci diff -c stm32f103 --current "@pr --ident-format field_reader::c:_R --ident-format field_writer::c:_W --ident-format enum_name::c:_A --ident-format enum_write_name::c:_AW --ident-format enum_value::c: --ident-format interrupt::c: --ident-format cluster::c: --ident-format cluster_accessor::s: --ident-format cluster_mod::s: --ident-format register::c: --ident-format register_spec::c:_SPEC --ident-format register_accessor::s: --ident-format register_mod::s: --ident-format peripheral::c: --ident-format peripheral_singleton::c: --ident-format peripheral_mod::s: --ident-format peripheral_feature::c:"

cc @Emilgardis

Tested this on a PAC I'm working on for the LPC11U1x/2x/3x MCUs, and it leads to some bad names for pins. In the SVD and reference manual, they all follow the naming scheme of PIO{port}_{pin}, where port is 0,1, and pin is 0..=31. However, the defaults used in this branch result in Pio{port}{pin}, resulting in pin types being named things like Pio19, Pio110, etc. Additionally, some of the enumeratedValues names get treated poorly too; one example is BETWEEN_1_20MHZ, which turns into Between120Mhz, and BETWEEN_15_20MHZ, which turns into Between1520Mhz.
Personal opinion, but I believe defaults should keep underscores between numbers; Between15_20Mhz isn't the prettiest, but would be more sensible than the current defaults.

Tested this on a PAC I'm working on for the LPC11U1x/2x/3x MCUs, and it leads to some bad names for pins. In the SVD and reference manual, they all follow the naming scheme of PIO{port}_{pin}, where port is 0,1, and pin is 0..=31. However, the defaults used in this branch result in Pio{port}{pin}, resulting in pin types being named things like Pio19, Pio110, etc. Additionally, some of the enumeratedValues names get treated poorly too; one example is BETWEEN_1_20MHZ, which turns into Between120Mhz, and BETWEEN_15_20MHZ, which turns into Between1520Mhz.
Personal opinion, but I believe defaults should keep underscores between numbers; Between15_20Mhz isn't the prettiest, but would be more sensible than the current defaults being used in this branch.

It looks like we need custom logic for to_pascal_case instead of built-in. I've tried to make some workarounds but those fix only individual cases.

@BrokenR3C0RD try last changes

@burrbull Works as expected, PIO0_11 becomes Pio0_11 and BETWEEN_15_20_MHZ becomes Between15_20Mhz. However, I think there might be an issue with 324b12c (which stops the panic in #811). SVD
Generates the following for PIO1:
// ...
impl RegisterBlock {
    #[doc = "0x60..0xe0 - Generic I/O configuration for PIO pins, port 1."]
    #[inline(always)]
    pub const fn pio1(&self, n: usize) -> &Pio10 {
        #[allow(clippy::no_effect)]
        [(); 32][n];
        unsafe { &*(self as *const Self).cast::<u8>().add(96).add(4 * n).cast() }
    }
    #[doc = "Iterator for array of:"]
    #[doc = "0x60..0xe0 - Generic I/O configuration for PIO pins, port 1."]
    #[inline(always)]
    pub fn pio1_iter(&self) -> impl Iterator<Item = &Pio10> {
        (0..32)
            .map(move |n| unsafe { &*(self as *const Self).cast::<u8>().add(96).add(4 * n).cast() })
    }
}

#[doc = "PIO0 (rw) register accessor: Generic I/O configuration for PIO, port 0.\n\nYou can [`read`](crate::generic::Reg::read) this register and get [`pio0::R`].  You can [`write_with_zero`](crate::generic::Reg::write_with_zero) this register using [`pio0::W`]. You can also [`modify`](crate::generic::Reg::modify) this register. See [API](https://docs.rs/svd2rust/#read--modify--write-api).\n\nFor information about available fields see [`mod@pio0`]
module"]
#[doc(alias = "PIO0")]
pub type Pio0 = crate::Reg<pio0::Pio0Spec>;
#[doc = "Generic I/O configuration for PIO, port 0."]
pub mod pio0;
pub use pio0 as pio1;
pub use Pio0 as Pio1;

Note that Pio10 is referenced instead of Pio1.

Note that Pio10 is referenced instead of Pio1.

I think this is due to https://github.com/rust-embedded/svd2rust/blob/a23a780b091b238299ad91abb267fb9a2cbadef2/src/generate/peripheral.rs#L1192. But I don't remember when and why it was added. Maybe this is not needed more.

git blame reveals it was https://github.com/rust-embedded/svd2rust/pull/662

/ci try diff

/ci diff pr

a085e4e now generates the correct pio1/pio1_iter functions for me, so #811 can be closed when/if this is merged.

this is not solved, an invalid name, e.g cluster_accesor doesn't warn

Fixed.
@Emilgardis can we discuss themes in separate PR?

@Emilgardis can we discuss themes in separate PR?

Sounds good!

Should we discuss this broader or are we good with going forward with this breaking change? I kinda want one more team member to ack

Should we discuss this broader or are we good with going forward with this breaking change? I kinda want one more team member to ack

I can split of default formats changing (maybe with themes) in separate PR and we discuss them on next meeting.

Lets keep the default changes to this pr but split out the ident-format improvements to a new pr

Lets keep the default changes to this pr but split out the ident-format improvements to a new pr which we can then just merge

#812

I'm not sure myself if that is the best way to go about it, maybe we could have "themes" where there's a default theme (the new behaviour), and another theme that looks like how it used to look like. You can still set individual formats if wanted.
so maybe
ident_formats_theme = "legacy"

Done. Not sure about new theme name.

Done. Not sure about new theme name.

We could also not have a new theme, e.g not expose it

maybe default?
With this variant though (legacy and default/new), we get into a issue of versioning, where if we change the theme we'd probably have to introduce a new theme for the previous version. I think only having legacy makes sense for now. Maybe there's an argument for having ranged theme names, such that saying theme = "0.35.1" means you get the appropriate theme for that version, but sounds like hell to maintain and keep track of

2021 and 2024?

@Emilgardis Can you fix svd2rust-regress "unused" warnings?


Bug: Remove the bug that is inherent in the current Celery app setup

The current setup of the Celery app in the project produces different Celery app instances with inconsistent settings/configurations depending on the order the modules are imported. In particular, the task functions defined in tasks.py can be executed in the Flask app's context or not depending on the order those tasks function are imported in relation to creation of the Flask app. This is a problem because a task function may end up running without the Flask app's context when the context is needed, and the context may be ended up loaded more than once, resulting in corruptions.
This issue can be observed in some of the tests of the Celery tasks where the context of the Flask app has to be brought up explicitly to use a celery task. For example: https://github.com/datalad/datalad-registry/blob/8cb28e244f681895343321ea6b7ce0a930de04f5/datalad_registry/tests/test_tasks/test_extract_ds_meta.py#L15-L25
On the other hand, Celery tasks can bring up the Flask app's context by themselves in other usages. For example, https://github.com/datalad/datalad-registry/blob/8cb28e244f681895343321ea6b7ce0a930de04f5/datalad_registry/blueprints/api/dataset_urls/init.py#L49-L117
This issue can be resolved by integrating the Celery app with the Flask app in the project in the manner suggested by by Flask's documentation.

The entire Celery app setup process has been re-written as part of #222, so this bug is fixed.


Basic documentation for run pipeline

Here's basic documentation to be fleshed out and organized.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: adelelopez:x: svekarsYou have signed the CLA already but the status is still pending? Let us recheck it.


Labeling tool

A 🖌- tool to label images and export the labels, e.g., in coco format could be helpful.  One might even think about turning this into an imaging self-service tool including model training, e.g., facilitating Onnx.

Added documentation for the current version of the bounding box labeling tool with Commit 4f6d55f.

We now have

Bounding boxes
Polygons
Brush strokes


SpriteMethodTest - freeHardwareBuffers method crashes application when called.

What steps will reproduce the problem?

1. Run SpriteMethodtest

2. Run OpenGL render with option which uses hardware buffers (Use Draw
Extension, Use VBO extension).

3. Close application. When the application reaches the freeHardwareBuffers
method instead of clearing up the buffers it terminates the application on
the first call to glDeleteBuffers

What is the expected output? What do you see instead?

The application should shut down cleanly but it is in fact crashing.

What version of the product are you using? On what operating system?

Windows XP Home. Eclipse running emulator.

Please provide any additional information below.

The application 'looks' like it is shutting down when in fact it is
actually crashing.

Original issue reported on code.google.com by alistair.rutherford on 12 Apr 2009 at 7:25

Original comment by<EMAIL_ADDRESS>on 17 May 2009 at 4:58

Added labels: Application-SpriteMethodTest

Original comment by<EMAIL_ADDRESS>on 17 May 2009 at 4:57

Changed state: Accepted

Fixed.

Original comment by<EMAIL_ADDRESS>on 19 Jan 2010 at 5:03

Changed state: Fixed


Missing Alias New-VenafiTeam on function New-VdcTeam

Environment
Full Operating System: N/A
VenafiPS version: > 6.0
PowerShell version: 5.1
TLSPDC version (if applicable): > 20.0

Steps to reproduce
Create a new Team using older name of the function, for e.g.
New-VenafiTeam -Name 'The A-Team' -Member $membersForTpp -Owner $ownersForTpp -Product $Product -Description $Description -PassThru
Expected behavior
A new Team is created using older function name (New-VenafiTeam).
Actual behavior
Error is thrown by PowerShell. The term 'New-VenafiTeam' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
More info
Please add the alias for older name of the function to the new name to maintain backwards compatibility.

Hi @Saadi6.  This was a byproduct of the name change in v6.  If we were to add an alias for only 1 product when the prior function handled both, it would cause issues for scripts targeting the other.  Unfortunately, we won't be making this change.
I would either update your script to use the new dedicated function or perhaps add an alias into your script, Set-Alias -Name New-VenafiTeam -Value New-VdcTeam.


v4b1 - deadline-days counter resets after a failed update

if a macOS update fails, the --deadline-days counter resets and the user gets a new deferral cycle.

Do you have some example logging you can show?

This should fix it: https://github.com/Macjutsu/super/releases/tag/v4.0.0-beta4


Third party integration

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.40 :tada:

Comparison is base (6a04f12) 99.31% compared to head (8941d71) 99.72%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #74      +/-   ##
==========================================
+ Coverage   99.31%   99.72%   +0.40%
==========================================
  Files          60       60
  Lines        3208     3242      +34
  Branches      495      500       +5
==========================================
+ Hits         3186     3233      +47
+ Misses         18        9       -9
+ Partials        4        0       -4

Impacted Files
Coverage Δ

flagship/src/visitor/NotReadyStrategy.ts
97.72% <ø> (ø)

flagship/src/visitor/PanicStrategy.ts
95.91% <ø> (ø)

flagship/src/visitor/VisitorDelegate.ts
100.00% <ø> (ø)

flagship/src/visitor/VisitorStrategyAbstract.ts
100.00% <ø> (ø)

flagship/src/config/BucketingConfig.ts
100.00% <100.00%> (ø)

flagship/src/config/FlagshipConfig.ts
100.00% <100.00%> (ø)

flagship/src/decision/BucketingManager.ts
100.00% <100.00%> (ø)

flagship/src/depsNode.ts
100.00% <100.00%> (ø)

flagship/src/enum/FlagshipConstant.ts
100.00% <100.00%> (ø)

flagship/src/main/Flagship.ts
98.69% <100.00%> (ø)

... and 5 more

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


services/s3: Implement proposal 11-error-handling

Signed-off-by: Xuanwo<EMAIL_ADDRESS>

 Here is an overview of what got changed by this pull request:

Clones added
============
- services/s3/servicer.go  15
- services/s3/storager.go  24
- services/s3/utils.go  3

See the complete overview on Codacy


Package a .war-file for a release

Create a script that creates a versioned release of the UI packaged in a .war-file, that can be served by the Marathon backend.
AC

'npm run release'
Version number should be retrieved from the package.json version key
dist/ files should be created from the related Git Tag (version)
Creates a .war-file with the contents of the dist-folder (main., img/, index.html)
Released .war should be in the repository in an own release-folder

Update: there was a misunderstanding, this needs to be a WebJar file .

I am sorry, my fault.

No worries! There's a lot of similarity between the two, so we can still use some of this work.

Basic Steps provided.
If finished, we need to integrate that into TC.
I create a ticket for the Backend part.

PR created https://github.com/mesosphere/marathon-ui/pull/108, but TC integration is more difficult than expected because I need a Dockerimage with both Node.js and Maven integration.


should "prettier-eslint-cli" be a devDependency instead?

nps version:

./node_modules/.bin/nps --version
5.0.2

node version:

node --version
v7.5.0

npm version:

npm --version
4.1.2

Problem description:
I just installed nps and it installed 91 modules, I have recently been trying to understand why certain dependencies are added and try to reduce some if possible.
> yarn add -D nps
yarn add v0.20.3
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 91 new dependencies.
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>...

analysed a few of these with yarn why
$ yarn why rxjs
info This module exists because "nps#prettier-eslint-cli" depends on it.

$ yarn why babel-code-frame
info Reasons this module exists
   - "nps#prettier-eslint-cli#prettier-eslint#prettier" depends on it

Suggested solution:
Should this be a dev dependency instead?

Yes, it definitely should. My mistake. Could you submit a pull request? http://makeapullrequest.com

thank you that was very quick


Docker build BuildArg parameter doesn't seem right

Hello here is a pointer to the issue I published to the wrong repos :
https://github.com/nuke-build/nuke/issues/166

It's indeed a bug. Will release a new version later today. Thanks :)

The new version was just published to NuGet, thanks for reporting the bug. 🎉

Working fine now, thank you for this lightspeed fix !