"ERROR: Support only RTSP-stream" on all cameras when using WebRTC (but direct camera URLs work with WebRTC Card)

Checklist:

[ X ] I updated to the latest version available
[ X ] I cleared the cache of my browser

Release with the issue:
v1.0.1 (also occurred on v0.1.4)
Last working release (if known):
None
Browser and Operating System:
All (Windows/Chrome, Android app)
Description of problem:
Whenever I specify a camera entity using WebRTC playback, I immediately get this error on the top of the player:
"ERROR: Support only RTSP-stream"
Debug steps taken:
This issue also occurs if I use the WebRTC card directly, and specify the camera via entity: instead of url:. Ultimately, using the WebRTC card with 'url:' directly to any camera works, so the cameras are compatible.
Javascript errors shown in the web inspector (if applicable):
mediaSource.onsourceopen @ webrtc-camera.js?v2.0.2:158 WebSocket is already in CLOSING or CLOSED state.

Additional information:
I suspect this problem is occuring because Frigate re-streams cameras as RTMP, not RTSP. This is all very confusing, because the Readme for this project implies that Frigate cameras should work with WebRTC playback without a problem. The WebRTC plugin recommended in the readme does not support RTMP... therefore, specifying the camera entity will always be broken. Yet, the Readme implies that this setup works and I should be able to view Frigate cameras now. Am I missing a step?

I think you may be misunderstanding how this is supposed to work, or more likely, the documentation is unclear.
When you're using WebRTC as your live provider, the Frigate card is little more than a wrapper around the WebRTC card that adds some Frigate fanciness such as events. You must have WebRTC already working & configured, and WebRTC fundamentally requires an RTSP stream. If you want to avoid using the url argument in the webrtc configuration, you must provide an entity argument (under webrtc:) but that must be independently configured as a separate RTSP camera in HA by you manually.
e.g. you must configure "raw" RTSP entries in Home Assistant with something like this:
  - platform: generic
    stream_source: !secret rtsp_path_cam_back_yard
    name: Back Yard RTSP
    still_image_url: [path to some still]

... and then use that RTSP entity in your WebRTC configuration. This is all a requirement of WebRTC, not of the Frigate card.
General advice: Get WebRTC working exactly as you want it first, then just copy that card configuration into the webrtc section of your Frigate card, and it should all work.

Okay, yes, the docs are unclear. After combing over them multiple times I finally figured out that I must go in and edit the card in YAML mode and add the url: parameter to get working operation. This is sorta hidden in the middle of your steps, when it's really the ONLY step that matters :P
You should state this clearly: "Live streams from Frigate camera entities are not supported with this card. One must bypass the Frigate camera by adding the direct URL of a camera via yaml mode."
Just to clarify, I DID mention in my original post that I had WebRTC working fully. I think your docs just need to be clearer about YOUR card actually using the same params from the WebRTC card.
I would not qualify this plugin as "Working" with Frigate cameras in this case, at least not for live streaming. When you say something like that, it implies I should just be able to reference the entity directly. Especially since the URL field is the only field missing from the GUI configuration. You just mention that one should "set up "WebRTC and you link to the other pluygin, but this is confusing as there isn't really a "set up" process for that plugin... there is just configuration of the actual card itself, which I didn't expect would apply to an entirely different card (your card).
You could probably reduce this confusion by adding a "URL" field in the GUI of the WebRTC section of your card. I was actually pleasantly surprised to see that GUI, but I think it's what started to throw me off too :)

@oramirite Thanks again for the valuable feedback. Please take a look through the merged PR, I hope (?) it's clearer now on the limitations and utility. I also added editor support from webrtc.url since you suspected that may also have reduced confused.


Build and push images to ibm container registry

Summary
xref: #298
Add actions to build and push images to IBM Container Registry
Details and comments
Adds new workflow / actions for IBM Container Registry (as we'll be retiring DockerHub in the near future, I just duplicated the files rather than adding a registry parameter to the existing one as we can remove the Docker ones once we're happy with the ICR images).
For the image tag, we're going from qiskit to icr.io/quantum-public
For the authentication to IBM Cloud, I used https://github.com/IBM/actions-ibmcloud-cli action, which adds the IBM Cloud CLI and logs in to IBM Cloud / Container Registry.

Would you enable multi-architecture build if you don't mind?  Simple enabling should work all images except the ray-node.
ref: https://blog.thesparktree.com/docker-multi-arch-github-actions.

enable multi-architecture build

I'll do that in a follow-up PR... I'd like to ensure the ICR piece works first before adding new functionality (as it'll be easier to troubleshoot if something goes wrong)

would help to add the actual action... :facepalm:


missing wildcard in src/main/java/serversync/forge/loader/ServerSyncLoader.java

I noticed that the search for the syncserver.jar is not consistent with the release names.
orig:    .filter(f -> f.getFileName().toString().matches("serversync-\\d\\.\\d\\.\\d\\.jar"))
fixed:   .filter(f -> f.getFileName().toString().matches("serversync-\\d\\.\\d\\.\\d\\*.jar"))
The current version is named serversync-3.6.0-all.jar so it isn't found because of the "-all".
I think the above should fix it.

After looking into regex I found that a * wasn't the solution.
Especially not where I suggested to put it.
I modified the line and created a pull request #4

Added extra conditions to match against alpha/beta versions and versions greater than a single digit


How to use the MvpLceRxPresenter with 4 Horizontal RecyclerViews in the same screen.

I have used MvpLceRxPresenter  when I have 1 RecyclerView in the screen but how to use it if I have 4 different RecyclerViews

That's a very vague question. That depends on your use and how you load data ...
EITHER
you see each RecyclerView as its own independent MvpView  (use LCEView only if all three states (showLoading(), showError(), showContent() are reachable and in each independent MvpView on screen) with its own MvpPresenter that loads items to display just for this single RecyclerView
OR
Use one single View for the whole screen that loads the data for all 4 RecyclerViews and gives the result back to the View in a optimized PresentationModel (generated by the Presenter) like this:
interface MyView extends MvpLceView<MyPresentationModel>

class MyPresentationModel {
   List<Item> row1; // displayed afterwards by first RecyclerView
   List<Item> row2 // displayed by second RecyclcerView
   List<Item> row3 // displayed by third RecyclcerView
   List<Item> row4 // displayed by fourth RecyclcerView
}

class MyPresenter extends MvpLcePresenter<MyView> {

    public void loadData(boolean pullToRefresh) {
        retrofit.loadSomething() // RxJava observable
           .map( singleData) -> transformToPresentationModel(singleData) )
           .subscribe (  ... ); // showLoading() , showError(), showContent()
    }

    private MyPresentationModel transformToPresentationModel(List<Item> singleData){
         MypPresentationModel presentationModel = new MyPresentationModel();
         for (Item i : singleData){
             // fill presentationModel
         }
         return presentationModel;
    }
}

btw @jjvargas  I would appreciate if you would ask those kind of questions on stackoverflow, because it's not Mosby related, it's more general MVP question. I also have an eye on questions tagged with mosby. Furthermore, stackoverflow is well indexed by google, so it's easier for others to find your question / answer on stackoverflow and you might also get  better answers and other suggestions / opinions ... Thanks


CASMINST-6534: Remove chart source fields from manifest, to force it to use the source specified on the loftsman command line

Description
A problem was found with the chart redeploy procedure in cases where the manifest obtained from Loftsman specifies a nonexistent chart location (even if a good location is specified on the deploy command line). This PR updates the relevant procedure to remove the chart sources from the manifest being deployed, forcing it to only consider the source specified on the command line.

Resolves CASMINST-6534

Checklist

[X] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[X] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[X] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.4 release/1.3


Fix custom RPC node entry

Fix vulnerability where malicious RPC could be entered via a website inject.

Thanks @seabornlee all good observations!


Added Item VR Headset as requested in Issue 22

Added Item VR Headset as requested in Issue 22

@Jonah-gr ready to merge !!


Add logging option to inits

We now save logs to /var/logs/st2chatops.log on debian and el6, upstart on u14 automatically saves it to /var/log/upstart/st2chatops.log and systemd in el7 stores logs in journald by default.
I'm gonna merge this PR to unblock @emedvedev on pushing new version of the container, but your input on the logging solution is welcome.


[FEEDBACK]: Improving the footer

Type
Suggestion to Improve
Feedback
I am seeing that their is so much space between the footer and its components. So I want to make it even more prettier. That's why I am opening this issue.
Screenshots

developer.tbd.website URL
https://developer.tbd.website/
Browser
Chrome
Relevant log output
No response

@parag477 is there a mockup of what you have in mind?

I don't have any mockup rn

ok I don't see any issues with the spacing. not sure what you had in mind for improvement


Add source button in Docs

The source button present in docs for tch-rs as a sample -

No such button for burn-rs docs

It would greatly help looking into pin-pointing the definition and implementation of modules in this vast repo

It's available on docs.rs, we are probably missing a feature flag when building the docs, but I'm not able to find it.

It's not a feature flag that is missing here but the fact that the burn package's docs are build with --no-deps. While rustdoc still expands and documents re-exported items (in this case these from burn-core), it can't produce the source links to the code of the dependency. Docs.rs doesn't suffer from this as it generates the docs for every uploaded library crate and interlinks them (including the links to the source code).
I wasn't able to find where the API docs are build in the CI, are they build manually? I think the most sensible fix would be to build the whole workspace instead of just the burn package for the API docs. Or build the burn package without the --no-deps flag. The former can be done with --no-deps to avoid 3rd-party crates to be added to the docs, which should be fine if burn doesn't re-export any items from them. If it does, the source links for said items would be missing again. Maybe something like cargo doc -p burn -p burn-core -p burn-train --no-deps would be enough to add the source links to every item, I haven't checked whether burn-core or burn-train re-export any items themselves.

@jofas analysis is correct. If I remember correctly,  we have removed the --no-deps option because of the great amount of time in bulding the docs.  Here and here are the CI APIs.
Since documentation should be independent from any operating systems (@nathanielsimard @antimora @louisfd  please confirm whether my previous statement is correct for what concerns burn), a possible solution might be the creation of a specific documentation task. This task can be run both locally and on CI.
This kind of task would:

Do not run cargo doc ... command for each operating system
Run a specific virtual machine in parallel only for the documentation
The same task can be added to the publish workflow

What do you think @syl20bnr?

This might be outdated? I see currently source links in the docs:
https://docs.rs/burn/latest/burn/nn/conv/struct.Conv2d.html

This issue is about the docs hosted on burn.dev, which are missing the source buttons.


client: log error message when image does not exist

When the image specified in config.js does not exist, the
single-client.js script exits with no failures, and no logged errors.
Catch this error and log it to the console.
Change-type: patch
Signed-off-by: Joseph Kogut<EMAIL_ADDRESS>

LGTM

@rcooke-warwick Didn't we have an observation that the client would fail way sooner without an image and not even reach the part for single client. If this actually solves it then I think it works out and closes #397

Tested it today, does work.
[2021-08-12T11:50:17.635Z][-os] INFO: WORKER URL: https://.balena-devices.com/
[2021-08-12T11:50:19.252Z][-os] [Error: ENOENT: no such file or directory, stat '/usr/src/app/workspace/balena.img.zip'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'stat',
  path: '/usr/src/app/workspace/balena.img.zip'
}
Downloading DUT serial log with https://.balena-devices.com//reports/dut-serial.txt


spirv-fuzz: Make a synonym via OpSelect

We have TransformationAddSynonym, which makes synonyms via various opcodes, and it would be good to add OpSelect as one of the possibilities.

@Vasniktel I cannot decide whether to try to add this as a new case in TransformationAddSynonym, or make it a separate transformation.
Three things make it not fit the pattern of the other cases in TransformationAddSynonym:

We want to turn %r into either "OpSelect %true %r %anything" or "OpSelect %false %r %anything".  If we want both of these cases we would need to encode whether "true" or "false" is desired, or have another transformation to invert an OpSelect.

We would need to supply the id for %anything - the other cases don't have this.

When operating on vectors, OpSelect can either use a scalar boolean condition or a vector condition.  The vector condition case could be quite interesting.  For two vectors %v and %w we could end up with a vector %u such that some components of %u are synonyms for some components of %v and some components of %w.

Perhaps this merits its own transformation and fuzzer pass; what do you think?
Or: the OpSelect case with a scalar condition could be folded in to TransformationAddSynonym (it's very similar to OpCopyObject), and another transformation could be added for the vector case.

I think it's better to focus only on scalar operands right now. The original and transformed modules will look as follows:

original:

...
%a = ... ; some instruction of scalar type - say %type
...

transformed:

...
%a = ... ; the same instruction
%b = OpSelect %type %false %irrelevant_zero %a
...

In the above:

%type is some scalar type.
%false is a non-irrelevant boolean constant (%false = OpConstantFalse %bool)
%irrelevant_zero is an irrelevant scalar zero constant with type %type.

Also, now the fact manager has the fact that %a and %b are synonymous.
Later, we can extend this to support vector operands and maybe swapping operands of the OpSelect but that should be a different PR.


Add DLC fix and frame parsing from slice

Fix issue where DLC was decoded as 3 bits instead of 4
Add new functionality to parse a frame from a &[u8] slice

Tested in HW on Teensy 4, DLC decoding is now working properly.


Make the progress-bar more nuanced than in steps of 1% from 0% to 100%

Is your feature request related to a problem? Please describe.

Describe the solution you'd like
why is this line in ~/.local/lib/python3.10/site-packages/ffmpeg_progress_yield/ffmpeg_progress_yield.py:
yield int(elapsed_time / total_dur * 100)
creating an int?
I gather from the source I've read so far (and what I understood) that you parse the ffmpeg progress output time string and from that calculate the point in the duration of the stream of the file.
Can this not be done as a float? Is the display of a float not a better thing to have?
How often do you update this number? I don't know if that could be a drawback.
Additional context
I created a custom script which I can watch. It parses the progress output of ffmpeg-normalize (redirected into a log-file) to make it "more nice" and more like I want it, for that reason it would be nice to have more precise values than in steps of 1.
Since the calls for one file take so long, the time between increases of 1% is larger than I would like. Normalizing a whole movie on my NAS-machine takes multiple hours, so it takes several minutes for a percent to get done.
Of course, this script is very personalized with probably far too many hard coded things:
https://github.com/joshinils/bin_shell/blob/master/format_normalize_progress.py
This is the script with which I was starting the normalization procedure.
https://github.com/joshinils/bin_shell/blob/master/normalize
I am in the process of re-writing it in python to be able to set a different bitrate per stream depending on the channel-layout of it, because of slhck/ffmpeg-normalize#232
https://github.com/joshinils/bin_shell/blob/master/normalize.py
Which is probably all sorts of bad code and not optimal, but it works, for now.

Moved this issue here, as it's a function of this project.

Will make a new release of ffmpeg-normalize in a few minutes.

thank you very much.
Stream 1/1:  14%|█▍        | 14.177270684137696/100 [08:26<59:45, 41.78s/it]

Stream 1/1:  14%|█▍        | 14.19241500561823/100 [08:26<57:01, 39.88s/it]

Stream 1/1:  14%|█▍        | 14.207559327098766/100 [08:27<54:23, 38.04s/it]

Stream 1/1:  14%|█▍        | 14.238940859238841/100 [08:28<51:58, 36.36s/it]

Stream 1/1:  14%|█▍        | 14.25439743477052/100 [08:28<51:00, 35.69s/it]

Stream 1/1:  14%|█▍        | 14.270010137327771/100 [08:29<50:19, 35.23s/it]

I think you should still limit the number of digits, though?
I mean, it's nice to have this much precision, no doubt. (and I don't see it because of my script, which parses it away behind the scenes)
But I think someone else might complain.
The total number of digits seems to vary, which means the progress bar will look like it flickers.
I think 2 or 3 significant digits after the decimal point should be enough. So something like f"{percent:7.3f}"

Hmm. I thought that tqdm would handle this more gracefully. I'll see if I can round it myself before passing the percentage. Thanks for letting me know!

FIxed in the latest release.

That was probably not intended, as the remaining API was using floats. Thanks for catching this. Made a new release for this lib, and fixed it upstream: https://github.com/slhck/ffmpeg-normalize/commit/d21b49d0e3a3508fa6f1ed52ca233cd800e8bce5
Should be working in latest ffmpeg-normalize like this:


Update to package.sh as requirements.txt is empty

Issue #, if available:
requirements.txt is empty and no longer creating initial zip file
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks @darf53 for submitting this.  It does avoid a lot of confusion.


polyline over 3d object

Environment details
javascript, google maps, threejs
Steps to reproduce

i draw a polyline with google maps and put the 3d objects whit threejs but the line draw over the 3d object

example

Following these steps will guarantee the quickest resolution possible.
Thanks!

This is expected behavior. What's happening is that the 3D object is rendered directly as part of the basemap, but polylines are actually rendered in a separate overly on the map. The only way to achieve the effect you are looking for would be to also draw the polyline using ThreeJS (or WebGL directly or some other WebGL library). Then you could control the stacking order.


Repeatedly clicking buttons within drawer causes drawer to close

See the following screen recording for repro:
https://github.com/shadcn-ui/ui/assets/6355370/3fa82130-35cb-465d-922d-dd17ede1d90a

See the following screen recording for repro: https://github.com/shadcn-ui/ui/assets/6355370/3fa82130-35cb-465d-922d-dd17ede1d90a

Interesting discovery. I cannot reproduce the issue 10/10 times.

I tried on latest iOS/Safari and I get a different but also strange behavior. When I try to click the plus button repeatedly, most of my clicks don’t cause the number to change, but do cause the backdrop to flicker.

Is the same behavior happening locally or just the site demo?

I tried to repo in StackBlitz and was unable to. Must be something to do with the demo site then?
https://stackblitz.com/edit/stackblitz-starters-hvuoqn?file=app%2Fdrawer.tsx

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Apptainer version 1.2.0.

I was able to build this locally using the instructions in the README:
docker build --build-arg APPTAINER_COMMITISH=v1.3.2 -t apptainer:1.3.2 https://raw.githubusercontent.com/kaczmarj/apptainer-in-docker/main/Dockerfile

See issue for details: #17

thanks @gilmorera !


Test a

Product Version(s):

Issue:

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

 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.4 out of 5 committers have signed the CLA.:white_check_mark: aaaaaaaalex:white_check_mark: ctauchen:white_check_mark: lwr20:white_check_mark: tmjd:x: dependabot[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


initial transfer of LG model from gpjet

Ready for review @whoburg
Also, I added a constraint and the result got much closer to the actual 737! Unfortunately, I have no idea why it changed the things it did....

Looks good. a number of equality constraints can be converted to inequalities; otherwise I think this is ready to go.
Also interesting is that for me LandingGear().test() takes about 2 seconds with cvxopt, and under one second with mosek.

@bqpd I think we're starting to get enough models that it would make sense to have models-gpkit unit tests that just run all the test() methods. Do we already have that in place? How do I run it? Should we ask Marshall to set up Jenkins to run it too?

I'd say import a testing.py file which imports ask the desired models to
top level, then for through dir running everything with a test method.
On Jan 13, 2016 05:17, "Warren Hoburg"<EMAIL_ADDRESS>wrote:

@bqpd https://github.com/bqpd I think we're starting to get enough
models that it would make sense to have models-gpkit unit tests that just
run all the test() methods. Do we already have that in place? How do I
run it? Should we ask Marshall to set up Jenkins to run it too?
—
Reply to this email directly or view it on GitHub
https://github.com/aeroa/gpkit-models/pull/27#issuecomment-171077703.

(smartphone typos, sorry)
On Jan 13, 2016 05:34, "Edward Burnell"<EMAIL_ADDRESS>wrote:

I'd say import a testing.py file which imports ask the desired models to
top level, then for through dir running everything with a test method.
On Jan 13, 2016 05:17, "Warren Hoburg"<EMAIL_ADDRESS>wrote:

@bqpd https://github.com/bqpd I think we're starting to get enough
models that it would make sense to have models-gpkit unit tests that just
run all the test() methods. Do we already have that in place? How do I
run it? Should we ask Marshall to set up Jenkins to run it too?
—
Reply to this email directly or view it on GitHub
https://github.com/aeroa/gpkit-models/pull/27#issuecomment-171077703.

The only reason I'm hesitant to convert equality constraints to inequalities is because I have a suspicion that it makes them more susceptible to being dual infeasible in the future (if another model is added that puts a stronger pressure in the opposite direction). Do you buy that? The four changes you propose don't affect the result in the present model, but when I debug dual infeasibility, the first thing I do is make all inequality constraints equalities wherever possible, and it can sometimes help.

@pgkirsch, regarding your points about equality constraints, this illustrates to me that we still need a more formal way to talk about the assumptions/pressures of a model. Until we have that I don't think we can issue a blanket policy on when to use equality constraints.
@bqpd, two questions regarding your suggestion to have a testing.py file import "the desired models" and then dir through everything with a test method:

dumb question, but dir returns a list of strings. Is it obvious how to get the actual python objects from the strings?
Would you do things like from beam import *, trying to require less updates to testing.py, or would you use explicit imports?

TESTS = []

import beam
TESTS.append(beam)

for attr in dir(beam):
    if hasattr(getattr(beam, attr), "test"):
        getattr(beam, attr).test()  # wrap this in a nice error message

Ah - got it. I thought you were suggesting using dir to find the modules.
I'll take a shot at adding the testing script today.

test() currently fails for me:
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
<ipython-input-3-b8860f1c5b14> in <module>()
----> 1 lg.test()

/Users/whoburg/MIT/dev/models-gpkit/aircraft/landing_gear.py in test(self)
    249     def test(self):
    250         sol = self.localsolve()
--> 251         npt.assert_almost_equal(sol('x_n') + sol('B'), sol('x_m'), decimal=5)
    252         npt.assert_almost_equal(sol('\Delta x_n') + sol('x_n'), sol('x_{CG}'),
    253                                 decimal=1)

/Users/whoburg/anaconda/envs/gpkit/lib/python2.7/site-packages/numpy/testing/utils.pyc in assert_almost_equal(actual, desired, decimal, err_msg, verbose)
    488         pass
    489     if round(abs(desired - actual), decimal) != 0 :
--> 490         raise AssertionError(_build_err_msg())
    491
    492

AssertionError:
Arrays are not almost equal to 5 decimals
 ACTUAL: 21.284771127378246
 DESIRED: 21.284763621703661

also, I added the testing script discussed above in #29 -- we can move that conversation there


The scroll bar of your website is not looking good and it is default which is not suited in your website.

https://github.com/user-attachments/assets/fa545210-e2db-430d-b824-04359cb04da3
The side scroll  bar is not looking good on website I want to make it good UI like this below video with your website suited colour.
https://github.com/user-attachments/assets/b434cdca-5b21-46c9-b702-7d741f1fb445
so assign this issue under gssoc extended and hactoberfest.

yeah agree, you got this 👍

i would like to work this

yeah agree, you got this 👍

thankyou i will work on it. and @varma-101 sorry but this issue is assigned and i am just working on it.

@varma-101 as per the guidlines it's first come first serve, please find some other issues, I would be more than happy to see wider variety of issues


Broken cuda-10.1.243 container

The cuda-10.1.243 container is broken when trying to build code with nvcc. The gcc version the container is using targets<EMAIL_ADDRESS>nvcc10 doesn't support gcc past 8.X.

Thanks for reporting this @mdavis36

@davidbeckingsale I can give a shot at fixing this - what is the recommended action?

I think just putting<EMAIL_ADDRESS>and making sure that was the default would be a good fix. Alternative might be to use an older Ubuntu base like 18.

So you mean hard coding it into the Dockerfile for all images?

@davidbeckingsale this is a dynamically generated matrix and gcc is not a variable (it's whatever is provided in the container) https://github.com/rse-ops/docker-images/blob/main/ubuntu/cuda/uptodate.yaml.
Why is nvcc only supporting gcc that is so old? Lame.

Because it's an old NVCC :'(

:ghost: boo! :laughing:


Selector not visible to frame.waitForSelector(selector), but is found with frame.$(selector)

Steps to reproduce
I am using Puppeteer 1.5.0. NodeJS 6.1.0. Windows 10 Pro. I have a selector that I know to be valid. When I call frame.$(selector), I get an elementHandle object back. This signifies to me that it successfully found the element. However, I immediately followed that function call with frame.waitForSelector(selector). I got the following error:
"Error: Node is either not visible or not an HTMLElement
at ElementHandle._assertBoundingBox (C:\some path)
at process._tickCallback (internal/process/next_tick.js:68:7)"
I would copy the output from print the ElementHandle, but it is long. The following should reproduce it, I think. The error comes up on the very last time of code below.
await page.goto('https://www.google.com/');

selector = 'html>body>div>div:nth-child(8)>form>div:nth-child(2)>div:nth-child(2)>div>div>div:nth-child(2)>div>div>div:nth-child(2)>div>input';
container = await getContainer(selector); //gets the appropriate frame for the element
await container.type(selector, `nam`);

await page.keyboard.press(keyDictionary[`\${KEY_ENTER}`]);

selector = 'html>body>div:nth-child(8)>div:nth-child(2)>div>div>div>div>div:nth-child(2)>div:nth-child(2)>ul>li:nth-child(3)>a';

container = await getContainer(selector);

console.log(await container.$(selector)); //works as expected
await container.click(selector); //somehow does not work

Also, when I do the following, click works. It just does not update the page when navigating to a new link: container.evaluate( (s) => { document.querySelector(s).click(); }, selector);

@calakin looks like clicking sometimes doesn't work for you. Could you please try with Puppeteer v1.6.0? We did a lot of work to make clicking much more reliable.


exception with nodes at block zero

Traceback (most recent call last):
File "/home/vit/Documents/dev/python/cutecoin/src/cutecoin/core/registry/identities.py", line 66, in
reply.finished.connect(lambda: self.handle_lookup(reply, identity))
File "/home/vit/Documents/dev/python/cutecoin/src/cutecoin/core/registry/identities.py", line 109, in handle_lookup
data = json.loads(strdata)
File "/usr/lib/python3.4/json/init.py", line 318, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.4/json/decoder.py", line 343, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.4/json/decoder.py", line 361, in raw_decode
raise ValueError(errmsg("Expecting value", s, err.value)) from None
ValueError: Expecting value: line 1 column 1 (char 0)
Some nodes are at block zero. ucoind version is not displayed for those nodes.
My certifications are wrong in the wot.
One identity has renew date at start of unix time.

Multiple bugs there :

The network incorrectly thinks offline nodes are still online. Actually, no code exists right now to define nodes as offline... ;)  https://github.com/ucoin-io/cutecoin/blob/dev/src/cutecoin/core/net/node.py
Thought, requests are going to these offlines nodes and returns errors
The errors are not handled in handle_lookup : https://github.com/ucoin-io/cutecoin/blob/dev/src/cutecoin/core/registry/identities.py

All bugs should be fixed with last commit.


Support for Amazon Linux AMI 2018.03

Hello, I do realize its "pretty old" OS, but still can it be supported by script?
./falcon-linux-install.sh
Fatal error: Unrecognized OS: Amazon Linux AMI

Here is some output from EC2:
cat /etc/os-release
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"

I opened pull request https://github.com/CrowdStrike/falcon-scripts/pull/51

Got next issue:
./falcon-linux-install.sh
Falcon Sensor Install  ... Fatal error: Unable to locate matching sensor: Amazon Linux, version: 2018

Need some universal way of transforming “2018.03” and variations to version “1”

I created pull request - tested the changes, sensor got installed.
https://github.com/CrowdStrike/falcon-scripts/pull/52


Allow proxy url with parameters

Summary
Currently, proxy url's cannot have parameters.
This PR fixes/implements the following bugs/features
2098
Explain the motivation for making this change. What existing problem does the pull request solve?
If a proxy url contains a parameter such as:
http://abc.com/myproxy.jsp?myparam=foo
html2canvas will call the proxy using the following url:
http://abc.com/myproxy.jsp?myparam=foo?url=abc.com....
Notice there are two question marks in the url which is incorrect. The second parameter should begin with an ampersand.
The code had automatically put a question mark (?) after the proxy url. I fixed the code to check whether there is already a parameter at the end of the url. This was properly done in the the 0.5 version:
Test plan (required)
Pass a proxy url which ends with a parameter(s) as an option.
Code formatting
Please make sure that code adheres to the project code formatting. Running npm run format will automatically format your code correctly.
Closing issues

Fixes #2098
Closes #2098

What is the status of this PL? Can we please expedite this as it seems like a common use case where proxy url can have existing query params.


Critical dependency: the request of a dependency is an expression

🐛 Bug description
i write below code:
#[wasm_bindgen]
pub fn test() {
    let tmp =  client_random(28);
}

pub fn client_random(len: usize) -> Vec<u8> {
    let mut data: Vec<u8> = vec![0; len];
    let mut rng = rand::thread_rng();
    for i in 0..len {
        let n = match SystemTime::now().duration_since(SystemTime::UNIX_EPOCH) {
            Ok(n) => n.as_millis(),
            Err(_) => 100,
        };
        let ir = rng.gen_range(0..n as usize);
        data[i] = ((n + ir as u128) % 256) as u8;
    }
    data
}

and use
🤔 Expected Behavior
👟 Steps to reproduce
npm run found error:
Critical dependency: the request of a dependency is an expression
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version:  0.10.0
rustc version:  1.53.0 (53cb7b09b 2021-06-17)

@weihualiu Hi, have you ever resolved this?

This repo is for Rust->WASM
Perhaps you meant to file this for wasm-bindgen which is WASM->JS
https://github.com/rustwasm/wasm-bindgen/issues/2706


Fix showtimes/ticket selection on main page

After clicking on the 'See Showings' button next to an event on the main page, the drop down fields for date/time/ticket selection are no longer populating correctly. Will require front/back end work to modify SQL queries and handle their results properly.

I fixed the date parsing on the bac end and the site now displays the correct dates.
The time is being correctly parsed on the back end, but is being displayed incorrectly still

Definitely going to need some front end assistance, this whole ticket selection mechanism is going to need refactoring


AttributeError: 'super' object has no attribute 'conv2d_forward'

when inferece image:
raceback (most recent call last):
File "tools/demo.py", line 101, in
result = inference_detector(model, img_path)
File "/mnt/mmdet/apis/inference.py", line 86, in inference_detector
result = model(return_loss=False, rescale=True, **data)
File "/root/miniconda3/envs/mmdetection/lib/python3.7/site-packages/torch/nn/modules/module.py", line 493, in call
result = self.forward(*input, **kwargs)
File "/mnt/mmdet/core/fp16/decorators.py", line 49, in new_func
return old_func(*args, **kwargs)
File "/mnt/mmdet/models/detectors/base.py", line 149, in forward
return self.forward_test(img, img_metas, **kwargs)
File "/mnt/mmdet/models/detectors/base.py", line 130, in forward_test
return self.simple_test(imgs[0], img_metas[0], **kwargs)
File "/mnt/mmdet/models/detectors/htc.py", line 311, in simple_test
x = self.extract_feat(img)
File "/mnt/mmdet/models/detectors/rfp.py", line 98, in extract_feat
x = self.backbone(img)
File "/root/miniconda3/envs/mmdetection/lib/python3.7/site-packages/torch/nn/modules/module.py", line 493, in call
result = self.forward(*input, **kwargs)
File "/mnt/mmdet/models/backbones/resnet.py", line 583, in forward
x = self.conv1(x)
File "/root/miniconda3/envs/mmdetection/lib/python3.7/site-packages/torch/nn/modules/module.py", line 493, in call
result = self.forward(*input, **kwargs)
File "/mnt/mmdet/ops/conv_ws.py", line 84, in forward
return super().conv2d_forward(x, weight)
AttributeError: 'super' object has no attribute 'conv2d_forward'

Thanks for reporting this!
This seems to be a PyTorch version problem. PyTorch 1.5 has changed its internal API. Here's the environment we use:
pytorch==1.4.0
torchvision=0.5.0
cudatoolkit=10.1.243
I'll also add this to README so other people won't have to deal with this issue. Thanks again.

@pengxiaoxiao PyTorch used to have it:
https://github.com/pytorch/pytorch/blob/v1.4.0/torch/nn/modules/conv.py#L334

I think super().forward(x) can replace the conv2d_forward here.
Then the code works with pytorch 1.1.0 to 1.1.4.
Right? Not very sure.

@pengxiaoxiao PyTorch used to have it:
https://github.com/pytorch/pytorch/blob/v1.4.0/torch/nn/modules/conv.py#L334

function name changed in latest pytorch v1.7.0x version,
super()._conv_forward(...)


npm package contains dist/reference-1.6.0.html

Starting with version 1.7.0, the npm package contains the following three files in dist/:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Those files seem to be left-overs from testing or a former build.

Fixed!


[ClientRuntime] Added PATCH as a valid method when Created status is returned on LRO

Description
As per https://github.com/Azure/azure-sdk-for-net/issues/3592 , PATCH long running operations return a 'Created' HTTP status code. This change adds this as a valid response.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

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

@ScottHolden this is no longer needed as a PR has been opened to fix this issue.
#3625


question about technical report

Hello, I would like to ask if there is a template for the technical report?

We recommend cvpr template.
Best
Chonghao Sima

From: yabuke @.>
Sent: Sunday, June 2, 2024 10:08:14 AM
To: OpenDriveLab/DriveLM @.>
Cc: Subscribed @.***>
Subject: [OpenDriveLab/DriveLM] question about technical report (Issue #102)
---- External Email: Use caution with attachments, links, or sharing data ----
Hello, I would like to ask if there is a template for the technical report?
—
Reply to this email directly, view it on GitHubhttps://github.com/OpenDriveLab/DriveLM/issues/102, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM6RGLVIUJ6KSPFCQYSA2ELZFJ5A5AVCNFSM6AAAAABIUULODWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDSNBSHA2DCOI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


v-bind="$attrs" and problems with "value" attribute for multi-checkboxes

Version
2.5.16
Reproduction link
https://codepen.io/anon/pen/aYqoYL?editors=1010
Steps to reproduce

Check the checkbox
See that the value is set to "null" even though the input element has its value (correctly) set to "foo"

What is expected?

The value passed through "$attrs" should be the checkbox's value used

(or, the value never hits the DOM element, the fact that it is present on the DOM element but isn't used in the model is a conflict IMO)
What is actually happening?

Null is set

Check the modified codepen. I changed the component logic to match default native multi checkbox behavior.
https://codepen.io/anon/pen/NYQWzo?editors=1011

@emanuelmutschlechner I don't think your codepen is relevant here (though I appreciate you working toward a solution!). Adding an explicit value prop to my original pen and putting that prop on the input field works around the bug - as can be seen in this modified pen. The point is that that shouldn't need to be done.
v-bind=$attrs should be passing value to the input already in my original pen, and it isn't doing so in a way v-model is picking up on.

I get your point, but I'm not sure if this is a bug or not. We need some feedback from the core team.
My solution is partly based on this example code, where value is bound explicit and used with disabled attribute inheritance. source
Vue.component('base-input', {
  inheritAttrs: false,
  props: ['label', 'value'],
  computed: {
    inputListeners: function () {
      var vm = this
      // `Object.assign` merges objects together to form a new object
      return Object.assign({},
        // We add all the listeners from the parent
        this.$listeners,
        // Then we can add custom listeners or override the
        // behavior of some listeners.
        {
          // This ensures that the component works with v-model
          input: function (event) {
            vm.$emit('input', event.target.value)
          }
        }
      )
    }
  },
  template: `
    <label>
      {{ label }}
      <input
        v-bind="$attrs"
        v-bind:value="value"
        v-on="inputListeners"
      >
    </label>
  `
})

Maybe this issue is somewhat related to #6216?

I think both of you are right. And, @emanuelmutschlechner, you are correct, right now this is the way of doing it: @chrisvfritz explains the state of the art and future approaches here:

(https://www.youtube.com/watch?v=b554XmaTWrw)

Just wanted to that i've also faced this in my project.
Basically the problem can be narrowed to this:
// this works with emit('input')
v-bind:value="value"

// this fails to work with emit('input')
v-bind="{ value:value }"

So yeah, we have to explicitly set the :value to make things work, as @emanuelmutschlechner said earlier.
Imho, this seems more like a bug.


minor style fix on knowledge graph and summary

Description
Added some paddings and margins to knowledge graph and summary tools.
Type of change

Bug fix (non-breaking change which fixes an issue)

Screenshots

Reference JIRA tickets :

none

Checklist:
Put an "x" in the brackets to check the checkbox.

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code in particularly hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have made corresponding changes to JIRA tickets
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have merged develop into my branch and resolved possible conflicts

Looks good!


Sliding animations within a Bootstrap grid messes up border radius

The most simple replication I can come up with is here:
https://jsfiddle.net/kruser/vxszvdjs/8/
Notice that while animating, the border radius of the image container are removed.
In gif form below.

I should note that I can't reproduce this on Firefox or Safari. Only Chrome.

Closing as this seems to be a browser issue. Here is the workaround I used in case anybody comes across this: https://stackoverflow.com/questions/40131314/overflow-hidden-with-border-radius-not-working-in-chrome


Fixed id pamam's behavior to set column's value as document id

This pull-request is based on pull-request #11, and I corrected confliction of code.
I confirmed it worked fine.
id option of cuurrent version(v0.1.8) doesn't work correctly.
For example, I run with followwing config.yml,
out:
  type: elasticsearch
  id: id
  nodes:
    - {host: localhost, port: 9300}
  index: embulk
  index_type: embulk

I can get like follwing result.
{
    "_index" : "embulk",
    "_type" : "embulk",
    "_id" : "AVFWxh4LT8S5KFvme3FD",
    "_score" : 1.0,
    "_source":{
        "id":4,
        "account":11270,
        "time":"2015-01-29T11:54:36.000Z",
        "purchase":"2015-01-29T00:00:00.000Z",
        "comment":"NULL"
    }
}

But expected result is like below.
We can set document id correctly and we can search with id params via REST API.
$ curl -XGET localhost:9200/embulk/embulk/4
{
    "_index" : "embulk",
    "_type" : "embulk",
    "_id" : "4",
    "_score" : 1.0,
    "_source":{
        "id":4,
        "account":11270,
        "time":"2015-01-29T11:54:36.000Z",
        "purchase":"2015-01-29T00:00:00.000Z",
        "comment":"NULL"
    }
}

I merged.


Add new parameters for jail configuration

This pull request, if I understand the ruby correctly, should add support for:

rlimits (on|off)
quota (Disk Max for jail)
memoryuse (RAM cap)
pcpu (CPU usage cap)
release (FreeBSD release to deploy)

Thanks for the contribution.


python311Packages.tldextract: 5.1.0 -> 5.1.1

Diff: https://github.com/john-kurkowski/tldextract/compare/refs/tags/5.1.0...5.1.1
Changelog: https://github.com/john-kurkowski/tldextract/blob/5.1.1/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 270077 run on x86_64-linux 1

4 packages failed to build:

python310Packages.warcio
python310Packages.warcio.dist
python311Packages.warcio
python311Packages.warcio.dist

68 packages built:

certbot-full
cloudhunter
corsair (python311Packages.corsair-scan)
corsair.dist (python311Packages.corsair-scan.dist)
ghauri
ghauri.dist
ioccheck
ioccheck.dist
lexicon (python311Packages.dns-lexicon)
lexicon.dist (python311Packages.dns-lexicon.dist)
python310Packages.asyncwhois
python310Packages.asyncwhois.dist
python310Packages.certauth
python310Packages.certauth.dist
python310Packages.certbot-dns-ovh
python310Packages.certbot-dns-ovh.dist
python310Packages.corsair-scan
python310Packages.corsair-scan.dist
python310Packages.dns-lexicon
python310Packages.dns-lexicon.dist
python310Packages.scrapy
python310Packages.scrapy-deltafetch
python310Packages.scrapy-deltafetch.dist
python310Packages.scrapy-fake-useragent
python310Packages.scrapy-fake-useragent.dist
python310Packages.scrapy-splash
python310Packages.scrapy-splash.dist
python310Packages.scrapy.dist
python310Packages.shodan
python310Packages.shodan.dist
python310Packages.surt
python310Packages.surt.dist
python310Packages.tldextract
python310Packages.tldextract.dist
python310Packages.wsgiprox
python310Packages.wsgiprox.dist
python311Packages.asyncwhois
python311Packages.asyncwhois.dist
python311Packages.certauth
python311Packages.certauth.dist
python311Packages.certbot-dns-ovh
python311Packages.certbot-dns-ovh.dist
python311Packages.scrapy
python311Packages.scrapy-deltafetch
python311Packages.scrapy-deltafetch.dist
python311Packages.scrapy-fake-useragent
python311Packages.scrapy-fake-useragent.dist
python311Packages.scrapy-splash
python311Packages.scrapy-splash.dist
python311Packages.scrapy.dist
python311Packages.shodan
python311Packages.shodan.dist
python311Packages.surt
python311Packages.surt.dist
python311Packages.tldextract
python311Packages.tldextract.dist
python311Packages.wsgiprox
python311Packages.wsgiprox.dist
qutebrowser
qutebrowser-qt5
qutebrowser-qt5.dist
qutebrowser.dist
sewer
sewer.dist
theharvester
theharvester.dist
wtfis
wtfis.dist

Result of nixpkgs-review pr 270077 run on x86_64-linux 1

72 packages built:

certbot-full
cloudhunter
corsair (python311Packages.corsair-scan)
corsair.dist (python311Packages.corsair-scan.dist)
ghauri
ghauri.dist
ioccheck
ioccheck.dist
lexicon (python311Packages.dns-lexicon)
lexicon.dist (python311Packages.dns-lexicon.dist)
python310Packages.asyncwhois
python310Packages.asyncwhois.dist
python310Packages.certauth
python310Packages.certauth.dist
python310Packages.certbot-dns-ovh
python310Packages.certbot-dns-ovh.dist
python310Packages.corsair-scan
python310Packages.corsair-scan.dist
python310Packages.dns-lexicon
python310Packages.dns-lexicon.dist
python310Packages.scrapy
python310Packages.scrapy-deltafetch
python310Packages.scrapy-deltafetch.dist
python310Packages.scrapy-fake-useragent
python310Packages.scrapy-fake-useragent.dist
python310Packages.scrapy-splash
python310Packages.scrapy-splash.dist
python310Packages.scrapy.dist
python310Packages.shodan
python310Packages.shodan.dist
python310Packages.surt
python310Packages.surt.dist
python310Packages.tldextract
python310Packages.tldextract.dist
python310Packages.warcio
python310Packages.warcio.dist
python310Packages.wsgiprox
python310Packages.wsgiprox.dist
python311Packages.asyncwhois
python311Packages.asyncwhois.dist
python311Packages.certauth
python311Packages.certauth.dist
python311Packages.certbot-dns-ovh
python311Packages.certbot-dns-ovh.dist
python311Packages.scrapy
python311Packages.scrapy-deltafetch
python311Packages.scrapy-deltafetch.dist
python311Packages.scrapy-fake-useragent
python311Packages.scrapy-fake-useragent.dist
python311Packages.scrapy-splash
python311Packages.scrapy-splash.dist
python311Packages.scrapy.dist
python311Packages.shodan
python311Packages.shodan.dist
python311Packages.surt
python311Packages.surt.dist
python311Packages.tldextract
python311Packages.tldextract.dist
python311Packages.warcio
python311Packages.warcio.dist
python311Packages.wsgiprox
python311Packages.wsgiprox.dist
qutebrowser
qutebrowser-qt5
qutebrowser-qt5.dist
qutebrowser.dist
sewer
sewer.dist
theharvester
theharvester.dist
wtfis
wtfis.dist

The warcio changes seem unrelated to the tldextract update. Why are thy in the same PR? Does one of them have a dependency on the other?


Add entry_point to include proxy url

depends on openprocurement/openprocurement.auction#100

Coverage remained the same at 84.179% when pulling 1e5f3aff2698455bc93d6bd76bd2df0e0dea6821 on oleksiyVeretiuk:backward_compatibility_proxy into c5ec7e7c432316eed5a5747d774456028fa50df8 on openprocurement:sandbox.


luci-base:Add some Simplified Chinese translation for luci.

I've done my best to finish the translation in luci-base:-)I left something because I don't know how to translate them.

Please sign your pull requests.
Thanks
Christian


Add warning when ID cannot be extracted

Currently function g.analyse tries to extract the participant ID based on argument idloc, but no warrning is given if this fails.
By adding a warning it may become easier for users to optimise the idloc argument setting.

Unrelated, but to save the effort of creating another issue and another development branch:
I am now also deprecating function g.metric as has been announced since summer 2020.


Release 0.2

Merge develop to main and release 0.2
Waiting for these PRs, necessary to facilitate the transition to the new mlflow server:

#83
#86

Optional but nice to include:

#82
#88

 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.10 out of 11 committers have signed the CLA.:white_check_mark: anaprietonem:white_check_mark: sahahner:white_check_mark: JPXKQX:white_check_mark: JesperDramsch:white_check_mark: gareth-j:white_check_mark: MeraX:white_check_mark: gmertes:white_check_mark: b8raoult:white_check_mark: da-ewanp:white_check_mark: theissenhelen:x: floriankrbYou have signed the CLA already but the status is still pending? Let us recheck it.


HV-528

Updating to the latest JAXB versions and forcing the jaxb2-maven-plugin to use these updated versions. This aligns the behaviour between JDK6 and JDK7
See also http://www.mojavelinux.com/blog/archives/2006/09/the_great_jaxb_api_blunder/ and http://java.net/jira/browse/JAXB-131
This resolves the basic compilation problem. Now there is a problem with the tests in hibernate-validator-annotation-processor. Most test assertions fail in JDK7. Will create a new issue for that

Nice now it compiles with OpenJDK 7!

Nice now it compiles with OpenJDK 7!

Jupp. Next step are the ap problems

The problem is that the AP is annotated with
@SupportedSourceVersion({SourceVersion.RELEASE_6)

One solution might be to define the following method in the AP:
@Override
public SourceVersion getSupportedSourceVersion() {
    return SourceVersion.latest();
}


json types: add support for inferring type of "extra" fields

A new boolean field inferextra  is added to the json type config. If true, the json typed reader no longer returns an error upon encountering fields not present in the current descriptor, but instead applies plain old json type inference and adds them to the end of the record. If false, the reader follows the prior behavior of returning an error.
Fields are added to the end of the record, at the top level, with a "flattened" field name. For example, assuming the incoming json object has a top-level field uid2 and a nested field id2 that are not in the schema, such as:
...
{
...
"uid2": "asdfasdfasdf",
"id2": {"orig_h": "<IP_ADDRESS>"}
}

then those fields will show up as "uid" and "id2.orig_h", both at the record top-level. On the one hand, this is is not very ergonomic, but on the other, it is necessary to allow "pushing" the extra fields to the right. And perhaps more importantly, leaving the inferred fields "in their place", would require a substantially bigger change to the typed parser, which does not seem worthwhile given its expected TTL.
First part of #1841

I just gave this a test drive since we know it's a bit of a hack, so we want to be prepared to live with the consequences.
In terms of the data surviving the type conversion, I'd say "mission accomplished". Here's an example alert with a bonus field added.
$ cat bonus.json | jq .
{
  "timestamp": "2020-03-26T11:03:29.986905-0700",
  "flow_id":<PHONE_NUMBER>515531,
  "pcap_cnt": 7,
  "event_type": "alert",
  "src_ip": "<IP_ADDRESS>",
  "src_port": 53262,
  "dest_ip": "<IP_ADDRESS>",
  "dest_port": 80,
  "proto": "TCP",
  "community_id": "1:DgCqAi4bQYb/4BoblZb/Iz//T70=",
  "tx_id": 0,
  "alert": {
    "action": "allowed",
    "gid": 1,
    "bonus": "LookAtMe!",
    "signature_id": 2013028,
    "rev": 5,
    "signature": "ET POLICY curl User-Agent Outbound",
    "category": "Attempted Information Leak",
    "severity": 2,
    "metadata": {
      "updated_at": [
        "2020_04_22"
      ],
      "created_at": [
        "2011_06_14"
      ]
    }
  },
  "app_proto": "http"
}

With current master of zq (commit 4585f9b0 at the moment), this fails as the user observed.
$ zq -version
Version: v0.25.0-20-g4585f9b0

$ zq -t -i ndjson -j ~/work/zq/ppl/zqd/ingest/suricata-types.json bonus.ndjson
bonus.ndjson: line 1: incomplete descriptor

With this branch, it works. The field appears flattened and positionally off to the right as @henridf indicated.
$ zq -version
Version: v0.25.0-21-g7b2e07e0

$ zq -t -i ndjson -j ~/work/zq/ppl/zqd/ingest/suricata-types.json bonus.ndjson
#port=uint16
#0:record[event_type:bstring,src_ip:ip,src_port:port,dest_ip:ip,dest_port:port,proto:bstring,app_proto:bstring,alert:record[severity:uint16,signature:bstring,category:bstring,action:bstring,signature_id:uint64,gid:uint64,rev:uint64,metadata:record[signature_severity:array[bstring],former_category:array[bstring],attack_target:array[bstring],deployment:array[bstring],affected_product:array[bstring],created_at:array[bstring],performance_impact:array[bstring],updated_at:array[bstring],malware_family:array[bstring],tag:array[bstring]]],flow_id:uint64,pcap_cnt:uint64,timestamp:time,tx_id:uint64,icmp_code:uint64,icmp_type:uint64,community_id:bstring,[alert.bonus]:string]
0:[alert;<IP_ADDRESS>;53262;<IP_ADDRESS>;80;TCP;http;[2;ET POLICY curl User-Agent Outbound;Attempted Information Leak;allowed;2013028;1;5;[-;-;-;-;-;[2011_06_14;]-;[2020_04_22;]-;-;]]1186020564515531;7;1585245809.986905;0;-;-;1:DgCqAi4bQYb/4BoblZb/Iz//T70=;LookAtMe!;]

In that "mixed" view without the columns, it seems it's not rendered at all. If I isolate just that one record, the field name does show up as a column header in the expected "rightward" location, but the value is absent.

Without digging into the frontend code, I'm not altogether shocked by this. We don't have places where field names with dots in them are easily read in (e.g. echo '{"foo.bar": 1}' | zq -t - creates a nested record[foo:record[bar:float64]], for better or worse) so perhaps we never had to confront rendering these.
The good news is that they do show up in a Log Detail drill down, which I expect is where more users might be looking.

On the whole, I'm ok with all this. Revisiting the priorities as I interpreted them, our goal here is to:

Not halt pcap import due to an unexpected Suricata field
Not drop the unexpected field+value from the imported record

While the experience of working with these added fields is not ideal, it does seem like it hits the original goals. Assuming we're able to present the user with warnings when this happens to increase the likelihood that we find out about it, I'll feel even better about it.


Expose pulumi log level via runner parameters

What does this PR do?

Adds runner parameters to control pulumi logging to make debugging pulumi issues easier.
example .test_infra_config.yaml options
configParams:
  pulumi:
    logLevel: 9
    logToStdErr: true

Like other options, can be set via env vars

E2E_PULUMI_LOG_LEVEL=9
E2E_PULUMI_LOG_TO_STDERR=true

Motivation

pulumi's default log output doesn't contain enough information to debug issues
Additional Notes

test-infra config model PR: https://github.com/DataDog/test-infra-definitions/pull/561
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


Bypass String(format:) to prevent escaping percentage symbols

Now that strings are always formatted using String(format:) (even strings without arguments) we have to escape any percentage signs (%) with %%
Our strings are hosted on phrase.com and also used in our Android project. This means I cannot go to the source and replace things like "get a 40% discount" with "get a 40%% discount", because that will have effects on other platforms as well.
Is there a possibility to opt out of this behavior, so that we don't have to escape the percentage symbol in strings that do not contain arguments?

func escapePercentIfNeeded(_ input: String) -> String {
if input.contains("%") {
return input.replacingOccurrences(of: "%", with: "%%")
} else {
return input
}
}
Just add this Function and use it where you need this.
Like:
String(Format: escapePercentIfNeeded("get a 40% discount"))
or
String(Format: escapePercentIfNeeded("get a 40% discount"))
Both will work Fine.
Let Me Know If I am Wrong Somewhere.

@mokshitgogia this is wrong code and doesn't solve the issue.
I've got same problem. I think using String(format:locale:arguments) when no arguments is just a mistake and generates wrong text whenever % is in the translation.
@mac-cain13 could you check it out?

The issue is in StringResource+Integration:
    init(key: StaticString, tableName: String, source: StringResource.Source, developmentValue: String?, locale overrideLocale: Locale?, arguments: [CVarArg]) {
        switch source {
        case let .hosting(bundle):
            // With fallback to developmentValue
            let format = NSLocalizedString(key.description, tableName: tableName, bundle: bundle, value: developmentValue ?? "", comment: "")
            self = String(format: format, locale: overrideLocale, arguments: arguments)

        case let .selected(bundle, locale):
            // Don't use developmentValue with selected bundle/locale
            let format = NSLocalizedString(key.description, tableName: tableName, bundle: bundle, value: "", comment: "")
            self = String(format: format, locale: overrideLocale ?? locale, arguments: arguments)

        case .none:
            self = key.description
        }
    }

I think when there are no arguments provided String should initialise from format, otherwise keep old implementation. Am I missing something?

Correct. This issue was introduced by https://github.com/mac-cain13/R.swift/pull/768 by @tomlokhorst.
I think there should be a way to opt-out of this behavior.

I've run into the very same problem as well.
Temporally as a workaround I've added a script with a small regex substitution to escape % sings in translations. It's not perfect but sufficient for my project.
I run it after downloading translations.
s/%?%(?!(?:[0-9]+\$)?(?:(?:l|ll)?(?:i|u|d)|@|[0-9]*\.?[0-9]*f))/%%/g
it ignores only simple specifiers d, u, i, f and @ and escapes the rest
PS. Remember not to push modified files to the phrase back


Fix stn-install.sh to work with the new Dockerfile

Coverage remained the same at 75.21% when pulling 6cfaa1b4624e71d535daaa4cbea11d06a46921ea on rastislavszabo:master into dd63f32477d691c92550769f668f459d6ffdc167 on contiv:master.

What is broken? How do we check?

executing stn-install.sh was returning an error, since it was relying on the location of the STN binary. In the new version of Docker, the binary is in /stn, whereas in the old one, it was /root/contiv-stn. Since the entrypoint is set properly in both versions, specifying the path is not neccessary and fixes the issue.


Require that local variables with header-like types are initialized i…

…nvalid

In discussion on the 2020-May-04 LDWG meeting on issue #845 and #846, it was resolved to create a PR to address #845 to strengthen the requirements, such that all headers, header_union, and header stack local variables (even if they are embedded within a struct or tuple) must be initialized as invalid.
This PR attempts to make these changes.  It modifies some text in the only two places in the spec that I know of where such initialization is mentioned, making the stronger initialization requirements explicit.

I am going ahead and merging this, given that it has been approved on Github, and in the 2020-May-04 P4 LDWG meeting.  I have created a related issue that was raised during that meeting, where it was suggested that perhaps a future P4_16 language spec version should consider making such header initializations as no longer required: https://github.com/p4lang/p4-spec/issues/849


refactor(operator-yaml): Set default value of sparse pool create to false

Going ahead with default enabled for now. We will revisit this in the future.


Create visualisations for VaR Project.

Currently , The project "Hedging-of-Financial-Derivatives/VaR /VAR (1).ipynb" don't have any visualisations in it. I would like to add Interactive Visualizations using Plotly, Seaborn etc.

Hi @Akshat111111 , I have raised this issue. Please assign it to me.


Performance: Show FPS counter

We should make it easy to add an FPS counter / track FPS - on both the native and JSOO side.
Related to #230 , in the sense of having a performance metric be front-and-center (FPS counter gives a view of overall performance, while a tracking square can help identify stutter/jitter).
Thanks @sgrove for the suggestion!
A couple of things we'll have to consider:

What's the right place for this? Should the rendering pipeline track FPS, and expose a boolean option, or should we implement an <FPSCounter /> in user-space?
In the case where there is no animations active / no active re-renders - should we just show FPS: -? Alternatively, we could show a metric like 'lastRenderTime' which is the time in ms spent to render the last frame.

I decided to work on this and my progress is on my add-fps-counter branch.
Keeping track of fps is simple, I just needed to add a counter to the window type in Core/Window that stores the tick (from SDL's getTick) after each render cycle, and the time it took to render the last frame, using that.
Then I gave the Window module two new functions: getFPS, which returns the FPS as a float, and getLastRenderTime, which returns the last render time in milliseconds as an int.
I'm gonna see about adding an <FPSCounter /> and then make a PR with my changes.

Since my PR was merged this issue can be closed. Sorry I forgot in to write "resolves #..." in the message.

Thanks for the PR @Grinshpon!


Request: 1 cent purchases on Amazon

My bank requires 10 debit card transactions a month. Since I get 5% cashback on my Amazon.com purchases from my credit card, I would lose less money if I made 120 1 cent purchases than if I were to reload 50 cents 120 times annually with my no-cashback debit card.
There was a list posted by FifenC0ugar on Reddit for 1 cent items: https://amazon.com/hz/wishlist/ls/2OD38KEKFXVT4

I have the same credit card. The opportunity cost of using debbit is about 2.5 cents if you intend to actually spend the gift card money. I do like this idea though since it would give non-Amazon folks the opportunity to automate purchases without having to spend the gift card values later. I'll consider implementing this but it's low priority for now.


Support for Firebase Cloud Firestore

Would it be possible to support Cloud Firestore as you support Realtime Database?
Currently, this.$fireStore refers to the Storage service, which is different from the Firestore service.
Thanks!

@Pitouli Are you going to make that PR? I'm also interested in using cloud firestore and this would be super helpful :)

Yes, I'll try to do it tomorrow :)

@daniel-centore @mdocter @scriptPilot
I've made a push request: https://github.com/scriptPilot/app-framework/pull/778

Any updates?
I am waiting for this feature


Add the signature to the path instead of query params

This won't fly as we need it to be backwards compatible to deploy

We're not really doing any signing any more so this doesn't matter


Fail gracefully

When magic-trace first starts up, it should detect conditions that we know will never work and bail out early with a good error message when they're hit. This wiki page  contains a list of constraints we know about. Let's automate as much as we can.

Related: https://github.com/janestreet/magic-trace/issues/34


[User Story] - notation trust policy and store authentication

As a user, I want to configure trust policy and trust store so that I can authenticate signed artifacts
Note: CLI based experience is out of scope, the trust store / policy itself will be there and configurable in filesystem.  Need to manually add what you trust.
Desire – make usability reasonable in RC1 even if it is editing a configuration file.

https://github.com/notaryproject/roadmap/issues/38 was updated to reflect this user story, so closing this out now with Samir since it's duplicate.


Italian speaker to talk with a flat host by phone

nameSurname: Ruslan Skoryk
phoneNumber: ''
email<EMAIL_ADDRESS>title: Italian speaker to talk with a flat host by phone
recipients: ''
description: I am trying to book a flat in Italy, I have found a flat but flat host
  speaks only Italian. If Italian-speaker could call him, ask some questions and arrange
  a booking that would be great.
url: ''
location:
  mode: autocomplete
  address: {}
iConfirmToHaveReadAndAcceptedPrivacyInformativeToThreatPersonalData: true
label: help
submit: true

Con questa che facciamo? @favoeva @luciroma @patriziacar


cognitiveservices release

https://github.com/Azure/sdk-release-request/issues/4283

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-arm-cognitiveservices

@MaryGao please help test openai cases,thanks


create().fetch() is not a function error.

Sails version: v1.0.2
Node version: v10.7.0
NPM version: 6.2.0
DB adapter name: sails-mongo
DB adapter version: 1.0.1
Operating system: mac

Hi everyone, I'm trying to insert a data and calling fetch() to return the new data that have been created. But I'm getting this error  TypeError: User.create(...).fetch is not a function. Without the fetch it works fine. I'm not sure whether this is sails or waterline issue.
I have tested using meta({fetch: true}) and the result is the same. Meta is not a function.
The only way I can get something similar to fetch is to enable  fetchRecordsOnCreate on config/models.js but I know this is a temporary fixed.
This is my file
UserController.js
  register: async function(req, res){
    try{
        const user = await User.create({name:req.body.name, email: req.body.email, password: req.body.password}).fetch()
        return res.ok(user);
    }
    catch(err)
    {
       console.log(err);
       return res.serverError({'err':err});
    }

  },

User.js
/**
 * User.js
 *
 * @description :: A model definition.  Represents a database table/collection/etc.
 * @docs        :: https://sailsjs.com/docs/concepts/models-and-orm/models
 */
const bcrypt = require("bcryptjs")

module.exports = {

  attributes: {
    name: {
      type: 'string',
      required: true
    },
    roles: {
      type: 'json',
      columnType: 'array',
      defaultsTo: ["DEFAULT_USER"]
          },
    email: {
      type: 'string',
      unique: true,
      isEmail: true,
      required: true
    },
    password: {
      type: 'string',
      required: true
    },
    tickets: {
      collection: 'ticket',
      via: 'assign_user'
    }
  },
  customToJSON: function () {
    return _.omit(this, ['password'])
  },

  /**
   * this is called so we can create our password hash for us
   *
   * before saving
   * @param values
   * @param cb
   */
  beforeCreate: function (values, cb) {

    // Hash password
    bcrypt.hash(values.password, 10, function (err, hash) {
      if (err) return cb(err)
      values.password = hash
      cb()
    })
  }
}

ok, fixed!

Removing the try / catch block should solve the issue. Not entirely sure why, could it be a scope problem?

I remove the try / catch block but the problem still persist

Create automatically returns the new record, so that is why there is no .fetch() function for it.

@valehelle Yeah I was wrong about that, sorry.

@valehelle - I noticed there's no semicolon at the end of .fetch() in your example - is that missing from the actual code?  Also, I'm curious if you've seen this issue with the latest Sails v1.1.0 or with other adapters and their databases besides sails-mongo?  Being that the error is claiming .fetch() is strangely not a function when it is, it may be worth verifying if the sails-mongo adapter is installed and configured properly as well.

@valehelle what version of sails-hook-orm are you using?

(can't reproduce this)

I'm currently facing thesame issue and this is 2019 and it seems this issue hasn't been resolved yet....
I get this error everytime i try to get a newly created
TypeError: Hobby.create(...).fetch is not a function
My application dependencies
"dependencies": {     "@sailshq/connect-redis": "^3.2.1",     "@sailshq/lodash": "^3.10.3"<EMAIL_ADDRESS>"^5.2.0",     "bcrypt": "^3.0.6",     "body-parser": "^1.19.0",     "cookie-parser": "^1.4.4",     "dotenv": "^8.0.0",     "grunt": "1.0.4",     "jsonwebtoken": "^8.5.1",     "passport": "^0.4.0",     "passport-jwt": "^4.0.0",     "passport-local": "^1.0.0",     "sails": "^1.2.3",     "sails-hook-grunt": "^4.0.0",     "sails-hook-orm": "^2.1.1",     "sails-hook-sockets": "^2.0.0",     "sails-hook-validation": "^0.4.7",     "sails-mongo": "^1.0.1",     "striptags": "^3.1.1"   },
what could i have done wrong , i followed the examples provided here https://sailsjs.com/documentation/reference/waterline-orm/models/create but yet i still get that same error

@TheDhejavu  Mine is working properly, [in 2019]
Book.create(_.extend(inputs, { user: this.req.me.id }))
      .intercept("E_UNIQUE", "bookAlreadyExist")
      .intercept({ name: "UsageError" }, "invalid")
      .fetch();

// Viola! it works

My dependencies
  "dependencies": {
    "@sailshq/connect-redis": "^3.2.1",
    "@sailshq/lodash": "^3.10.3",
    "connect-mongo": "2.0.3",
    "faker": "^4.1.0",
    "moment": "^2.24.0",
    "nodemailer": "^6.3.0",
    "nodemailer-mailgun-transport": "^1.4.0",
    "sails": "^1.2.2",
    "sails-hook-apianalytics": "^2.0.3",
    "sails-hook-cloud": "^0.1.1",
    "sails-hook-organics": "^1.0.0",
    "sails-hook-orm": "^2.1.1",
    "sails-hook-sockets": "^2.0.0",
    "sails-hook-uploads": "^0.4.3",
    "sails-mongo": "^1.0.1"
  },

can you reproduce your issue on a fresh sails app and share the repo? maybe you're missing something - not sure

this is the code block
create: async function(req, res){

    let { id: userId } = req.user;
    let { name } = req.body;

    if(!name || name == ""){
      return res.badRequest(null, null, "Hobby name is missing")
    }

    try{
      let uid = shortid.generate();
      let data = {
        name:  striptags(name),
        userId: userId,
        uid: uid
      }
      await  Hobby.create( data ).fetch()

      if(hobby){
        return res.created(hobby);
      }else{
        return res.badRequest(null, null, "Something went wrong")
      }
    }catch(error){
      console.log( error );
      return res.serverError(error)
    }
  },

Still not working

@TheDhejavu do you mean
let hobby = await Hobby.create( data ).fetch()

@TheDhejavu  it should work but looks like you're using traditional controllers, can you replicate this using  actions 2 [i don't really have time to re-write yours]
http://node-machine.org/spec/machine

why do i have to follow actions2 to fetch! it's really exhausting to create actions2 for each and every action!!
Plus the guides only include one action module.exports={...bla}

I encountered this issue and although I'm not sure why Something.create(data) doesn't work, something that works is sails.models.something.create(data)

@onedebos's suggestion fixed this for me

For me, I upgraded to Sails 1.4 and got the above error. Eventually, I discovered that I had the "sails-hook-validation" package installed. Worked after uninstalling "sails-hook-validation"

I encountered this issue and although I'm not sure why Something.create(data) doesn't work, something that works is sails.models.something.create(data)

But then don't you think 'await Something.create(data).fetch()' should work rather than sails.models.something.create(data)` which seems rather an unsettling approach? The documentation on the Waterline query page suggests that this is indeed the correct way to go about it but somehow it doesn't work. This doesn't make sense to me at all.

Disclaimer: I am new to SailsJs.


[Flatlist] I want to adjust the scroll speed in android.

New Version
0.66.3
Old Version
0.66.3
Build Target(s)
android
Output of react-native info
info Fetching system and libraries information...
System:
OS: macOS 12.6
CPU: (20) x64 Intel(R) Core(TM) i9-10910 CPU @ 3.60GHz
Memory: 499.57 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
Yarn: 1.22.18 - ~/.nvm/versions/node/v16.13.0/bin/yarn
npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
Android SDK: Not Found
IDEs:
Android Studio: Arctic Fox 2020.3.1 Patch 3 Arctic Fox 2020.3.1 Patch 3
Xcode: 14.0/14A309 - /usr/bin/xcodebuild
Languages:
Java: 11.0.12 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.3 => 0.66.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Issue and Reproduction Steps
hello.
I am building a flatlist function with one video per page.
problem
For Android only, the scrolling speed is very fast when turning one page. Especially if you snap your finger quickly, it goes through very quickly.
We want to adjust this speed.
I've tried several methods.
Attempted to control through the decelerationRate property. This confirms that it rises very slowly when you do a slow finger snap. But if you do it quickly, this is ignored. Also, the scrolling speed is not adjustable.
Is it possible to achieve a constant scroll speed regardless of the speed of the finger snap?

@SangWonyy did you have done any custom implementations?

I've been looking for a solution for a long time,did you find a useful way??


[nativesql] load native lib from jar

mvn package -Dnative.cpp.build.dir=/path/to/native/lib/
Signed-off-by: Yuan Zhou<EMAIL_ADDRESS>What changes were proposed in this pull request?
package the native lib into target jar so we could load native lib from there
How was this patch tested?
manually tested on local cluster

in #1205


In-memory timestamp checks are not ideal and should be removed in order to keep watcher standardized

Some watchers have in-memory timestamp checks. These are not ideal, as they (1) are unstandard relative to the rest of the watchers, (2) might not work as expected on bonder startup (before memory is written), and (3) are difficult to debug.
These should be able to be removed, however, the updated implementation is not 100% clear to me.
Two cases where this matters:

settleAttemptedAt
commitTxSentAt

I think they could be moved to be a db item property to be consistent with the rest (like bondWithdrawalAttemptedAt) and would make debugging easier

That might work for commitTxSentAt (I'm not 100% sure if there is a reason why it is not like this in the first place).
I'm not sure that works for settleAttemptedAt. settleAttemptedAt currently serves the role of "Mark a settlement as attempted here so that multiple db reads are not attempted every poll. This comes into play when a transfer is bonded after others in the same root have been settled". Maybe that can be done in a more ideal way rather than an in-memory store.
I think this one requires some more thought through edge cases if/when it gets implemented.

I think the reason commitTxSentAt is in memory is because we don't know what the transferRootId is yet (we know what it is only after commitTransfers), so for that reason we can't update it in the db and I think we should leave it as is.
The settleAttemptedAt state has been moved to the transferRootsDb (PR). I think it was in memory because in the past we were indexing by transferRootHash and not by transferRootId and the db getters weren't as efficient.

Closed by https://github.com/hop-protocol/hop/pull/386


fix reversed udp server example in README

I try this example and it respond with reversed chunks of the input indefinitely instead of respond "hello" to any incoming packet.

THanks!


Require write on container for DELETE

See https://gitter.im/solid/test-suite?at=617fd9a9fb3dcd4e885f2ab5

Kjetil Kjernsmo @kjetilk 13:12
I found that NSS isn't checking write on the container for deletes, which is in the draft spec.
Just wondering what you're checking in the test-suite, is it checked there?

and

Michiel de Jong @michielbdejong 14:15
Hm, odd. That indeed seems to be what
https://github.com/solid/web-access-control-tests/blob/main/test/surface/delete.test.ts
is checking, and indeed it doesn't make sense.
if PUT-to-create and PATCH-to-create require write access on the container to create the
containment triple, then DELETE should also require write access on the container to remove it.

As expected (see #41), this increases the number of WAC test failures for CSS v2.0.1 from 6 to 7:
● Create › Using PUT in existing container › is disallowed without accessTo Write or Append
● Create › Using PATCH in existing container › is disallowed without default Write
● Create › Using PATCH in existing container › is disallowed without accessTo Write or Append
● Create › Using PUT in non-existing container › is disallowed without accessTo Write or Append
● Create › Using PATCH in non-existing container › is disallowed without default Write
● Create › Using PATCH in non-existing container › is disallowed without accessTo Write or Append
● Delete › Is disallowed without Write on parent


route().current() doesn't work with a port number in the URL

Running a fresh install of Laravel 8 with Jetstream (Inertia) scaffolding, I have come across an issue whereby route().current() does not work if there is a port number in the URL. For example, while developing using Browsersync (typically port 3000).
A quick way to check this is to access the dashboard URL on a fresh Jetstream/Inertia installation at http://laravel.local and then type route().current() in the console and it will correctly return dashboard. However, if you then run the same app through Browsersync and go to https://laravel.local:3000 (for example) and type route().current() then it will return undefined
Routing is not completely broken, though. It still works in terms of linking to named routes etc., it just seems to be the route().current() which isn't working.

That sounds like a problem with Ziggy, not inertia. There is no route() help in Inertia to my knowledge.
https://github.com/tighten/ziggy

Ah, ok. I'll close this and post a new issue there then.
Thank you!


fix eslint issue

Coverage remained the same at 94.34% when pulling 693186f27364d7c455fc1c4a858e4dbfd1e9eae4 on bug-fixes into 20439afae2205b99a8e85f396d7b3848ca26169d on master.


Refactor /endpoint/{id} Policy types for API 1.0 stability

*Note: This PR is a diff to #3400. Please don't merge.
See #3280 for background
Summary of changes:
Refactor endpoint Policy field to have Spec and Realized to distinguish between what's in the datapath and what's intended for it.
How to test (optional):
all tests should pass.

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please


Enhancement: Displaying 'No items' on the 'Starting Items' screen.

Description of Problem or Question
Today when starting a scenario (Delve Too Deep) I didn't receive any Starting Items. When I saw the screen, I was wondering if it's an error (i.e. items were not displayed) or everything is as it should be.
I don't think removing the step altogether when players don't receive any items would be a good idea. Therefore, I would say a statement like 'You don't receive any items' should be displayed for clarity that there is no error or something like that.
Valkyrie Version
2.15, @BenRQ 's 2.2.20181209

The step is there to give a place for investors to get their starting items regardless if the scenario gives them or not.
A 'dont have any items' statement would be good though.

Yeah, I know what is the purpose of this step. If you add the statement, I'd be great!

I'll need the translation in all languages to do this.
I'm afraid "don't have any items" may have a strange translation though if using automatic translation.
"You don't receive any items" is probably better to translate through Google

Agree. I just wrote a minor suggestion for the text. Not something binding :). Do whatever you find best but I think our proposal is ok.

PL:
Nie otrzymasz żadnych przedmiotów startowych


Failing to generate test report after every run

Describe a bug
Action fails to generate test report no matter what arguments are used. Multiple errors listed below.
Expected behavior
The action displays coverage and test report separately
Details

Action version: v2.2.1-rc.0

OS, where your action is running (windows, linux):

action.yml file
  - name: Find PR Number
     uses: jwalton/gh-find-current-pr@v1
     id: findPr

  - name: Jest coverage report
    uses<EMAIL_ADDRESS>    with:
      test-script: npm run test:ci
      prnumber: ${{ steps.findPr.outputs.number }}

jest:ci command w/ config
jest --runInBand --ci --json --testLocationInResults --outputFile=report.json
 import type {Config} from 'jest';

 export default async (): Promise<Config> => {
   return {
     preset: 'ts-jest',
     testEnvironment: 'node',
     testTimeout: 1000,
     collectCoverageFrom: [
       'src/**/*.[jt]s'
     ],
     coveragePathIgnorePatterns: [
       'src/server/[jt]s'
     ],
     testMatch: [
       '**/?(*.)+(spec|test).[jt]s?(x)'
     ],
     collectCoverage: true,
     coverageThreshold: {
       global: {
         branches: 95,
         functions: 95,
         lines: 95,
         statements: 95
       },
     },
   };
 };

Log File
[Hastebin of error log](https://hastebin.com/share/ovohixuxug.yaml)

Additional context

@ArmandAgopian I had the same problem with the latest version of the action. At the same time, it was fixed using an older version of 2.0.6. We need to wait until this bug is fixed.


Error when launching

this comes infinitely :
20:24:42: ::ffff:<IP_ADDRESS> - - [27/May/2018:17:24:42 +0000] "GET /debug HTTP/1.1" 404 144 "-" "-"

Did you start the json-server?

yes ..
npm install -g json-server

Loading generate.js
Done
Resources
http://localhost:3000/tweets
http://localhost:3000/userTweets
http://localhost:3000/login
http://localhost:3000/tweetReplies
Home
http://localhost:3000
Type s + enter at any time to create a snapshot of the database

this comes infinitely :
20:24:42: ::ffff:<IP_ADDRESS> - - [27/May/2018:17:24:42 +0000] "GET /debug HTTP/1.1" 404 144 "-" "-"

I also encountered this problem, have you solved it


Waiting on an http request

I need to wait for an API call to return before generating the chart; however its not clear how to do this.
Thanks!
Liz

i am in the same Endeavour, but it seems there are some issues to deal with.
i used the PieChart as a starting point. https://tomneyland.github.io/angular-dc/example/stocks/pie.html
and included the d3.request call instead of d3.json which doesn't allow to POST a query data.
	d3.request('url-to-query')
		.header('Content-Type', 'application/json' )
		.post(JSON.stringify(payload),
		function( experiments ) {

    ndx = crossfilter(experiments)
    $scope.runDimension = ndx.dimension(function(d) { return d.age; }),
    $scope.speedSumGroup = $scope.runDimension.group().all();

    		});


Code coverage target for whole codebase, not just diff

Is there a way of setting a target percentage code coverage for the whole codebase, not just for the changed lines in the Pull Request?
The linked documentation article refers to full coverage, but doesn't say how to use it in the azurepipelines-coverage.yml.

Is there a solution to this? I am interested in doing this as well.

same here

Any update on the above? I also need it for whole codebase.
One issue with this yml setting is, it even considers files which are removed from repo for code coverage and doesnt even consider "ExcludeFromCodeCoverage" attribute.


Plot additional "evolving conditions"

I just ran the chapman mechanism and wanted to plot the photodecomp rates alongside the O3 concentrations just to know when the sun was shining.
Could we provide plots of any data that is read in as part of the "evolving conditions file"?

@mattldawson did you complete this when we did the refactor?

Yes, it is fixed


Make soft skill's color configurable + add 'sky' and 'orange' colors

For Sky Color, which one do you prefer?
First one is the current one with #01e0fd hexcode.

In the second one I have made it little darker with #00c9e3 hexcode.

II think #2 is better looking #00c9e3 among the other colors

@ChapChap  What if we make this color code configurable? :thinking:  Instead of color name, he will provide color code. User can provide whatever color he want.

I think the best is to accept both options. The input is a string, if it is a color code, then the border-color is set to its value, else, seach its value among, predefined colors.
Most users (me included) struggle choosing the right color set... So for the convenience, its better to choose form predefined ones

Ok. Sound good to me.

@blueyetisoftware and @ChapChap I have made the colors configurable. Now, user can use either the pre-defined colors or he can provide his own color code. What do you think?

Great changes. I have been modifying the theme for my personal use by overriding the css. Being able to set the colors from the yaml is a nice feature.


Troubles when i get logged in

Hello everyone!
I come here with a strange issue...
To be clear, i have developed a complete API Endpoint with AdonisJS v3.1 and I had no problems. Now i wanted to begin a new development with this new version (V3.2) and i get troubles with the simple Authenticating method...
This is what i have till now:
My routes.js:

My AccountController (this is where my login method is located):

HomeController.js (For dashboard once i get logged in):

This is my config/auth.js file:

Now, i have made everything is supose to do: Make the migration with ./ace auth:setup, run migration and seeders, and of course the simple login form. But, everytime i try to logged into the app, it just crash:

I am pretty sure that the Authenticating method is working because i made a test and is working... but i don't know what happens with that error...
I have no idea what could it be... Does anyone have a clue?
Thanks in advance...

Mind sharing the content inside the dashboard view?

Hello man! Thanks for response!
Better, i can give you a fresh installation:

Thanks for your help!

@thetutlage i have updated the repo... Thanks!


Wait for resource exists before sampling for condition

wait_for_condition() cal self.instance and the resource me not be exists, add wait for the resource

/cherry-pick v4.14 v4.13

/verified


[SPARK-15913][CORE] Dispatcher.stopped should be enclosed by synchronized block.

What changes were proposed in this pull request?
Dispatcher.stopped is guarded by this, but it is used without synchronization in postMessage function. This PR fixes this and also the exception message became more accurate.
How was this patch tested?
Pass the existing Jenkins tests.

Hi, @vanzin .
Could you review this when you have some time?

Test build #60383 has started for PR 13634 at commit 75a5254.

Do you need the flag anymore? Maybe return an Option with the error instead

Thank you for review, @srowen .
Oh, right. That sounds much better to me.
I'll update this PR like that.

Test build #60383 has finished for PR 13634 at commit 75a5254.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60383/
Test PASSed.

Test build #60394 has started for PR 13634 at commit b9e90a8.

Test build #60397 has started for PR 13634 at commit 2446b37.

Thank you always, @srowen .

Test build #60394 has finished for PR 13634 at commit b9e90a8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60394/
Test PASSed.

Test build #60397 has finished for PR 13634 at commit 2446b37.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60397/
Test PASSed.

LGTM. Merging to master / 2.0.

Thank you, @vanzin !


nixos/sddm: add package option

Description of changes
We'll want this once we have it building on Qt6.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

are you sure this didn't break anything @K900 ? my system is lacking SDDM entirely (just getting stuck at "Reached target Sound Card") since my daily rebuild today, works fine with yesterdays lockfile and on 23.11.

It definitely shouldn't have. What does systemctl status display-manager output?

● display-manager.service - Display Manager
     Loaded: loaded (/etc/systemd/system/display-manager.service; linked; preset: enabled)
     Active: active (running) since Thu 2024-01-04 13:12:14 CET; 1min 46s ago
    Process: 1531 ExecStartPre=/nix/store/5mkgyyfappqwj202my9f3ajwcs9ywv3y-unit-script-display-manager-pre-start/bin/display-manager-pre-start (code=exited, status=0/SUCCESS)
   Main PID: 1546 (.sddm-wrapped)
         IP: 0B in, 0B out
         IO: 3.8M read, 0B written
      Tasks: 2 (limit: 38161)
     Memory: 5.5M
        CPU: 33ms
     CGroup: /system.slice/display-manager.service
             └─1546 /run/current-system/sw/bin/sddm

Jan 04 13:12:14 tranquility sddm[1546]: Loading theme configuration from "/run/current-system/sw/share/sddm/themes/breeze/theme.conf"
Jan 04 13:12:14 tranquility sddm[1546]: Greeter starting...
Jan 04 13:12:14 tranquility sddm-helper[1569]: [PAM] Starting...
Jan 04 13:12:14 tranquility sddm-helper[1569]: [PAM] Authenticating...
Jan 04 13:12:14 tranquility sddm-helper[1569]: [PAM] returning.
Jan 04 13:12:14 tranquility sddm[1546]: Greeter session started successfully
Jan 04 13:12:14 tranquility sddm-helper[1569]: [PAM] Closing session
Jan 04 13:12:14 tranquility sddm-helper[1569]: [PAM] Ended.
Jan 04 13:12:14 tranquility sddm[1546]: Auth: sddm-helper exited successfully
Jan 04 13:12:14 tranquility sddm[1546]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS

So it is running, just not rendering presumably. I'd check your GPU config. Nvidia?


GUI (Ableton 11, Windows 7)

The Gui is not opening. There is only a blank window.

Hello. Have you tried to check this on other DAWs? It's only Ableton's specific or global problem?


GEODE-8240: Back-Port to 1.13

Back-port to support/1.13 branch, of https://github.com/apache/geode/pull/5273 fix for GEODE-8240
I used git cherry-pick -x bfe1ca113124ea958dc02dd9be90cdb0aabe5c4d
In resolving conflicts I mostly accepted all non-conflicting changes from 1.13. An exception was that in many places where we were using version.compareTo(other) < 0 or version.compareTo(other) >= 0, I accepted the changes from the cherry-pick commit to replace those with version.isOlderThan(other) or version.isNotOlderThan(other). Those changes were all made by @pivotal-jbarrett on develop and they improve readability.
I did not change InternalDistributedMember.equals(other)—instead, I pulled in a couple minor changes to GMSJoinLeaveJUnitTest from the develop branch, to get that test running with the (wrong/unchanged) IDM.equals(other) functionality. Since this ticket is not about fixing IDM this was the better way to go.

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[x] Have you written or updated unit tests to verify your changes?

Thanks for the 👍 @mkevo!