DBZ-4341 log batchSize in BaseSourceTask

https://issues.redhat.com/browse/DBZ-4341
DBZ-4341 log batchSize in BaseSourceTask

Hi @tooptoop4, batch size doesn't necessarily mean the number of records changed though.  I don't think any of us are opposed to logging the batch size this way but I want to be clear that if your batch size is 10,000 and 225,000 rows are emitted over the output interval that line will indicate `Batch size: 10000. 225000 record sent in previous ...".  Is that really helpful though?

Good point, @Naros. In fact, the message didn't make much sense before already, because we logged the total number of emitted since task start (recordCounter) together with the duration of the last polling interval. So we should simply change this to log batchSize together with that duration and otherwise keep the message as-is. The total number of emitted records is already exposed via JMX metrics.
That being said, on the issue itself we spoke about breaking down event count metrics per event type, but that's not what you've implemented here, @tooptoop4. So that's no longer important to you then?

recordCounter didn't make sense so batch size is a quick win. the breakdown would be good but I imagine higher effort

Closing in favour of https://github.com/debezium/debezium/pull/3018/. Will leave the metrics change for another time then, tbh. I don't think it'd add super-much value.


How is formula 12 derived from formula 7?

Thank you for your contribution, it's wonderful.In the article,  the score function in the reverse SDE in (7) can be replaced by (11),but I don't know the specific derivation process.Can you explain exactly how it was replaced?I'll appreciate it if you could tell me.

I have the same question. Additionally, what does $W$ stand for in (12)


added a check to the base.py settings file to see if AWS settings are defined in env file

Addresses: #85
The changes I made include the following:

add check for AWS .env variables in base.py settings file.  If present, use those settings plus the boto3 DEFAULT_FILE_STORAGE setting.  If not, use the default 'DEFAULT_FILE_STORAGE` setting.
added /media/* to .gitignore file

@looselycoupled Can you please check over this PR when you get a chance?  If you don't have time, I can try to punt it over to @tojeda instead.  Thanks! :smile:

The first time TravisCI ran, it failed because of a social_django module.  I did some googling to try and figure it out and did a new push to the PR.  Travis ran again and this time failed, but there was no error log.  Not sure why the make test is failing here?

@looselycoupled @ojedatony1616 Finally resolved the issues with the test build.  It is now ready to be reviewed.  Thanks!

@looselycoupled @ojedatony1616 So, the social auth dependencies have been driving me nuts.  First, the make test wasn't working due to dependencies and set up.  After I fixed that, then, I noticed running the app via python manage.py runserver <IP_ADDRESS>:8000 produced a map has no len error.  So, I had to play around with the dependencies again (the issue was with open_id).  So, after I felt like I fixed it, I removed my virtualenv, created a new one, and installed requirements from scratch.  Then I ran the make test and ran the main server again and everything appears to be working fine now.  I just wanted to briefly summarize what occurred so you can understand why I changed versions of certain dependencies.  Please take a look at this PR when you get a chance.  Thanks 😄

@looselycoupled @ojedatony1616 I will add one more thing to note.  As noted in the base.py file, when the DEFAULT_FILE_STORAGE parameter is using the default setting, it uses the MEDIA_ROOT setting to define the location in which files are stored.  I noticed this is defined in the development.py file:
MEDIA_ROOT       = os.path.join(PROJECT, 'media')
but not in the production.py file.  I'm not sure if it makes sense to add this to the prod file, but I thought I would note it here.

Thanks @bahadasx, and yes the social auth stuff is known to be a problem right now and I think there is an open ticket for it.  I definitely appreciate the work you've put into this.  I'll take a look when I can but it may not be until Sunday.

Whaaaat a can of worms that was. I was going down the 'check if OAuth still works' rabbit hole for a while there. Basically turns out out that the package we are using deprecated last December (see deprecation note) and the way they decided to do that was to bump up to version 0.3+ that basically turned it into a skin of the new package which is configured differently (and breaks those configured against the 0.2.x series). So maybe we want to migrate to that for real some time, but I'm on board with pinning to the latest 0.2.x series for now (I put it to the latest/final non-deprecated version 0.2.19).
I added some docs and took out some unnecessarily restricting pip requirements since it worked with the latest on those and I'm not sure how pin-happy we want to be as a general rule.
@bahadasx I would say it's fine to leave the MEDIA_ROOT setting out of production.py since we expect to have AWS credentials set in production every time.
Gonna go ahead and merge this and ask for permission/forgiveness laterrrr @looselycoupled fight me

@lauralorenz Thanks for looking over this.  Yes, it was a whole can of worms to deal with!


Update Composer dependencies (2022-02-09-00-10)

Visual regression test passed!
View the visual regression test report


Load glitch when running multiple canvases with SpriteStage

After some trial and error, I have managed to create a setup for GitHub for SpriteStage to get things going.
Thing is, I need to run multiple canvases on the page, as I need some animations above or below various DOM elements (z-index), thus, I need separate canvases. All works well, the only problem is that when I run a new spritesheet animation, the existing/running ones glitch for a bit (see example from repo). So if I have 10 canvases with animations, starting another one would make all the others glitch for a bit and then continue normally. Whenever a new animation starts, it gets everything stuck until it loads, I guess? This seems to be happening as long as I load resources directly and not through PreloadJS.
Are you guys aware of this? Is this normal behavior?
Also, let me know if jsFiddle is needed, I can try to make one fast
Thanks!

A couple of suggestions:

You don't have to create a new SpriteStage for each animation.  Create one sprite stage for each canvas and add/remove SpriteContainers from it as required
When you first add a SpriteContainer to a SpriteStage if creates a webgl texture from the associated image.  This process is likely what's causing the glitch in your demo.  If you want to front load all of this, you'll have to create all the SpriteContainers first and add them to the SpriteStage first to get the textures to load, then manipulate them on button press rather than destroy/recreate them.

Also, you may hit some performance issues on mobile with the amount of textures that you're talking about, see #536 for more

Thanks for the suggestions, I will take a look at it soon and return with feedback

Great suggestion! I have now created only one stage and I handle childs inside of it (Which should have been the normal behavior from the beginning) however, I still get the glitch, unless I preload all resources individually for each canvas.

So, the reason this occurs is because SpriteStage generates a WebGL texture for each image, then appends it as a property to the image, so that it doesn't recreate the texture if it sees the same image elsewhere. The downside of this, is that if you then use that image in another canvas, it tries to use that texture, but is unable to.
If this is a common use case (we certainly didn't expect it to be), we could also attach a property pointing back to the canvas, and then clone the image if it was used in a different one.
If weakly referenced dictionaries were widely supported, we would use them instead, but that's a ways off in JS.
Thoughts are welcome.

My scenario is a tad different, and I believe an example would explain things better than I would.
If you have time to checkout a setup I made on Github with an example in index.html here, look at the first canvas when loading the second sprite after the first one, there is a glitch and it uses different images, switching back to the first sprite is smooth, going back to the second one is glitchy, I have a hard time figuring out why.
Surprisingly this does not happen in IE11, everything is smooth there (Again, surprisingly)
Also, the above solution with cloning the image should indeed fix another problem, and that is the use of the same preloaded image in multiple canvases :)

Disregard the comment above, the glitch was because the second sprite was a large PNG and it glitched due to taking extra time loading/rendering it, and since I did not use a preloader, it loaded it every single time, I guess.
The only issue that remains is using the same preloaded image in multiple canvases and the cloning solution might do the trick.

Yeah, I think there're actually two issues here:

Easeljs stores the texture on the image meaning the same image can't be used across multiple spritestages.  I think this needs a solution if you're pushing the multiple stages methodology.
There's no way to get easeljs to to create a webgl texture for a particular stage (ie webgl canvas) other than to add it to the stage.   Keep in mind that this is not the same as preloading the image.

OP's problem was kind of both.  The browser will usually cache the underlying image after its first use, but the image object being used by his code will be different every time (created from the src string) so it will never have a texture already attached.   This is why it worked on both canvases (image object recreated every time without a texture to conflict with the canvas) but also why it glitched (texture needs to be created every time).
I think that both issues should to be addressed.

If we can get a unique id for each stage we could store it on the image as image.__textures[stageid].  This might hang around if a stage is disposed of, but the browser might actually destroy the underlying texture as part of its canvas clean up anyway.
First step would be to make an interface to allow the user have a texture created for a stage without directly adding it to the stage.   It looks like this isn't even an asynchronous call so no callbacks are necessary.   I guess this would be along the lines of stage.createTextures(image1, image2, image3) or the same with an array.

Agreed! I would love to see those issues addressed.
WebGL is being integrated more and more in apps and games, but since it's not yet sufficiently supported, there are folks like myself who prefer to create hybrid solutions of DOM + WebGL, where multiple canvas/stages have to run and would be nice to see EaselJS ready for it, as I've already enjoyed its fantastic help so far :)

Any updates on this? Or plans to address the two issues above?


Visualize upload states

Context

Uploading data happens when the device is connected to a known WiFi.
As a user I do not know when exactly the uploads happens, if at all and when it is done.

Proposal

The device should signal via a documented color code that the WiFi connection is established and that the upload

is starting
is happening
is done

The upload states could be visualized as specific colors or via a blinking pattern.

When the upload is done, the box shuts down.  So this is, at least for me, a good marker that the upload is done.

How do you know that the upload actually happened? How do you know that the box has shut down (light off)?

During the workshop they explained: If you leave the box idling on your desk it will search for the configured WiFI. When it is connected it will upload the collected data and then shut down or go to a deep sleep.
You have to (hard) turn it off and on  to restart the box.

True. I remember the explanation, too. Thank you for the code pointer.
I however would find it useful if I could recognize just by observing the device if an upload happens. Specially, the first time one becomes somewhat uncertain if it works. The WiFi credentials might have a typo. The only way to find out if the upload worked is to check the website. Thus, I would welcome a visual status feedback of the device a UX improvement.

I thought about this too but one thing kept me from actually implementing this.
The powerbank which powers the MCU demands a "minimum energy output". When this minimum energy output is not met the powerbank shuts off(Abschaltautomatik)) This way for example the powerbank would not overcharge your phone if it is at 100%. The senseBox only produces this minimum energy output with all sensors on and connected. So in order to give visual feedback that the upload was successful the box and all its sensors would need to be powered.
Now, one could implement a solution which gives visual feedback and then turn the box off after some minutes but not powering anything but the LED would not work here. In the end I decided instead of all the hassle that would come with implementing this, the visual feedback that the box turns off would be more straight forward and easier. I see your point though that some kind of feedback would be nice for the upload states.

How do you feel about a solution that lets the LED blinks for 5 minutes (according to the different color codes you mentioned) and then shuts itself off ?

Thank you for the explanation regarding the power bank restrictions.

[...] lets the LED blink [...]

... to visualize that the upload is taking place. I think this would already be an improvement. :heart:


[elasticsearch] Add service account and configure helpers.tpl

Signed-off-by: Naseem<EMAIL_ADDRESS>
[x] Chart version not bumped (the versions are all bumped and released at the same time)
[x] README.md updated with any new values or changes
[ ] Updated template tests in ${CHART}/tests/*.py
[ ] Updated integration tests in ${CHART}/examples/*/test/goss.yaml

Fixes #61

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Hi @naseemkullah,
Thank you for your great work on this PR.
We merged https://github.com/elastic/helm-charts/pull/265 a few days ago which is already implemented service account creation and your PR now has conflicts with master branch.
I'll close this PR but don't hesitate to open a new one with the new labels you added here.


Can u provide a tutorial to generate dataset with ones's own data for training?

@zhuyr97 Thank you for your interest! We plan to open-source the relevant code in the next few days, which will allow you to easily generate datasets using your own data for training. Stay tuned!

thanks! Fine-tuning with one's own data based on the open weights of Vis-Ret is something many people would find interesting!

thanks! Fine-tuning with one's own data based on the open weights of Vis-Ret is something many people would find interesting!

Totally agree!

Apologies for the long wait. We have now released the relevant code for generating training data for VisRAG-Ret using GPT-4o. The code is available in scripts/data/batch_api.py. Before running this script, please save each page of the PDF files you wish to use as training data in JSON format, ensuring that each JSON file contains an image_base64 field. All these JSON files should be placed in the input_dir. After that, you can execute the script by running:
python batch_api.py input_dir output_dir

This will generate queries for each page and save them as files in the output_dir.

@zhuyr97 Apologies for the long wait. We have now released the relevant code for generating training data for VisRAG-Ret using GPT-4o. The code is available in scripts/data/batch_api.py. Before running this script, please save each page of the PDF files you wish to use as training data in JSON format, ensuring that each JSON file contains an image_base64 field. All these JSON files should be placed in the input_dir. After that, you can execute the script by running:
python batch_api.py input_dir output_dir

This will generate queries for each page and save them as files in the output_dir.

The file batch_api.py provides a pipeline to generate training data in JSON format. However, it would be beneficial to provide a pipeline for generating training data in Parquet format, as this is the default format used in this repository. Are there any differences or gaps between these two pipelines?

Your suggestion is great, and we will work on improving the code as soon as possible. Regarding the data generation, there is only one pipeline, which is the one we have currently provided. The Parquet files are generated later for easier visualization of images on Hugging Face.

thanks! I also send more detailed questions via email<EMAIL_ADDRESS>） @tcy6


[Question] Where is the log file?

I tried to find the log file of miniflux, but cannot find /var/log/miniflux.log or similar file. Does miniflux write its log to a file, if yes where is the log file? If not where the log goes?
OS is CentOS 8. The miniflux version is 2.0.21.

I think the log file isn't written by default, the "log" goes to stdout or stderr. You can set a variable DEBUG=1 for more verbose logging and pipe the stdout and stderr to a file.
DEBUG=1 miniflux ... 2>&1 | tee ~/miniflux.log

Miniflux is started as a service, How can I pipe stdout and stderr to a file? And More importantly I want to monitor the log of miniflux using fail2ban? As far as I know fail2ban excepts a log file.  ( This may be a simple question, but I am a beginner to Linux).

The command I posted above creates a file in your home called miniflux.log, you can modify it accordingly for /var/log etc. You will have to modify your service file - it should be located in /etc/systemd/system/miniflux.service.

After more search, I found I can get miniflux log in /var/log/messages and journald by run the commands: sudo cat /var/log/messages | grep "miniflux" or sudo journalctl -u miniflux. However, I do not know why.

Miniflux send all the logs to stderr and let the operating system takes care of the logs.

If you use systemd, then you can watch the logs with journalctl.
If you use Docker, then you can use docker logs.


capacity of storage folder and htpasswd

My reason:
Hello i had two issues

what is the capacity of the storage folder ?

how many max users can we register

Steps to reproduce:

App Version:

Config file:

Additional information:

$ set DEBUG=express:* verdaccio enable extreme verdaccio debug mode
$ npm --verbose prints:
$ npm config get registry prints:
Verdaccio terminal output
Windows, OS X/macOS, or Linux?:
Verdaccio configuration file, eg: cat ~/.config/verdaccio/config.yaml

Container:

I use local environment
I develop / deploy using Docker.
I deploy to a PaaS.

Additional verbose log:

that depends mainly on your hardware
as much you can, I've never heard about issues with that.

What's the issue?  🤔

Juan it is not an issue i just had a general question about the storage folder , the max capacity of the folder


Published ports are not routed

After starting an instance and launching an nginx container with docker run -d -p 80 nginx the nginx container port was not routed:

The URL pattern for published ports mentioned in README.md also looks to be outdated:
http://pwd<hyphen-ip>-<port>.<host#>.labs.play-with-docker.com (i.e: http://pwd10-2-135-3-80.host3.labs.play-with-docker.com)

My session had a different URL structure and a different IP range assigned to individual nodes:
https://labs.play-with-docker.com/p/b83jgu363jcg00f93rt0#b83jgu36_b83jh0363jcg00f93rtg

Try with docker run -d -p 8080:80 nginx. That should work
sent from mobile
On Nov 11, 2017 15:02, "Leonid Makarov"<EMAIL_ADDRESS>wrote:

After starting an instance and launching an nginx container with docker
run -d -p 80 nginx the nginx container port was not routed:
[image: image]
https://user-images.githubusercontent.com/1205005/32692053-28695688-c6c6-11e7-8b9f-81346334b110.png
The URL pattern for published ports mentioned in README.md also looks to
be outdated:
http://pwd-.<host#>.labs.play-with-docker.com (i.e: http://pwd10-2-135-3-80.host3.labs.play-with-docker.com)
My session had a different URL structure and a different IP range assigned
to individual nodes:
https://labs.play-with-docker.com/p/b83jgu363jcg00f93rt0#b83jgu36_b83jh0363jcg00f93rtg
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/play-with-docker/play-with-docker/issues/213, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABgV2sK9R1HuiNwdgJEOEcLWSYpNjfznks5s1eE4gaJpZM4Qak-i
.

@marcosnils I tried that as well, but the result was the same.

fixed!.


NPM  install

I am trying to download the newest release v2.2.0 on a ubuntu 14.04 machine.
gitmiester@music:~/koel$ npm install

npm WARN deprecated<EMAIL_ADDRESS>graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible.
Killed

And then if I run again:
gitmiester@music:~/koel$ npm install

> koel@ postinstall /home/gitmiester/koel
> cross-env NODE_ENV=production && gulp --production

sh: 1: cross-env: not found

npm ERR! Linux 3.13.0-79-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.4.0
npm ERR! npm  v2.14.20
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! koel@ postinstall: `cross-env NODE_ENV=production && gulp --production`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the koel@ postinstall script 'cross-env NODE_ENV=production && gulp --production'.
npm ERR! This is most likely a problem with the koel package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=production && gulp --production
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs koel
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls koel
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/gitmiester/koel/npm-debug.log

npm --version
2.14.20

gulp --version
CLI version 1.2.1
Local version 3.9.1

Sorry to open issue about npm but npm install is working fine on a few other projects on this server with same user but I am having specifically issues with Koel only.  Any idea why?  I have went through all the npm issues in this repo but nothing helped me.  Thank you and Koel is amazing.

sudo npm install npm -g


Add dublin module for PyLadies Dublin website

PyLadies Pull Request
Please document the following. We will aim to be as timely as possible in processing your pull request, however as this is a volunteer staffed project anticipate at least a week for pull requests to start to be reviewed.
Does this PyLadies previously exist in the main PyLadies repo?

[ ] Yes
[X] No

If you marked yes, have you deleted it from the the main PyLadies repo?

[ ] Yes, and here is the pull request: [Insert pull request url here]
[ ] No

Is this pull requesting adding a PyLadies chapter website?

[X] Yes
[ ] No

If you marked yes, is this chapter registered in the PyLadies Chapter Directory?

[X] Yes
[ ] No

If you marked no, please register your chapter using the following form here. The form can only be accessed by being logged into your official PyLadies email account. Were you able to complete the registration?

[ ] Yes
[ ] No, I could not because [add response below]:

Is this pull request updating a PyLadies website?

[X] Yes
[ ] No

Pull Request Checklist

[X] Fill out all sections above

/cc @pyladies/tech-and-infra-admins

Hi there!
So our intent is to start centralizing pyladies repos and have them owned by the pyladies GitHub organization. I’ll make one and I can pull the content from your repo into the repo the pyladies organization owns.
To get this started could you fill out an issue like NYC did here https://github.com/pyladies/chapter-websites/issues/8?

huh, i thought i submitted an issue to github (why i pinged slack). i’ll
check it out and see what happened to my issue (prob fogot to hit submit🤔).
On Sunday, July 5, 2020, Lorena Mesa<EMAIL_ADDRESS>wrote:

Hi there!
So our intent is to start centralizing pyladies repos and have them owned
by the pyladies GitHub organization. I’ll make one and I can pull the
content from your repo into the repo the pyladies organization owns.
To get this started could you fill out an issue like NYC did here #8
https://github.com/pyladies/chapter-websites/issues/8?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pyladies/chapter-websites/pull/10#issuecomment-653891270,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABROZICFJ72U64PSI7M6KLR2CAHFANCNFSM4OQTJHDA
.

--
/// Vicky
~ eventgeek.ie ~
Pronouns: she/her/hers

Here it is, thanks for pinging me. I really thought I submitted it as it was all filled out. https://github.com/pyladies/chapter-websites/issues/11

Closing this due to opening another to add the pyladies org owned repo. See  #11 for more info!


Translates Blender introduction in french

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

I wasn't aware of the not acceptance of French translations, sorry for this.
If, in future, they will be accepted, where can I be notified? I would like to participate!
Thank you.


DataFrameMakerIterDataPipe now allows dtype_generator to be passed.

Stack from ghstack (oldest at bottom):

-> #537

This is required for the usecases when dtype itself is not serializable and can't be part of the graph.
Differential Revision: D37522091

@VitalyFedyunin has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.


@InjectExtra not working with startActivityForResult

Hi,
My "@InjectExtra" annotations doesn't work when I start my activity by launching "startActivityForResult". Is that a normal beavior?
Thanks,

Hi @Shargotth
I should work using startActivityForResult.
Could you provide more details or some code? (target activity @InjectExtra definition code, intent creation code, ...)
Thanks

This doesn't make much sense, it should work without any problem. Please re-open if needed and add detals.


"Make this form public?"

Hide the "Make this form public" checkbox, so a forms designer cannot inadvertently check this.

@ayushdamani @Stella-Archer
"Make this form public?" field hide. Changes are up on DEV and TEST environment.

ready for deployment

Andrew tested and this works. Okay to close


Proxy crashes when GSSAPI session encryption is requested

Looks good 👍
Just noting that there's another bug waiting to be uncovered here. According to the same Message Flow page,

To issue a cancel request, the frontend opens a new connection to the server and sends a CancelRequest message, rather than the StartupMessage message that would ordinarily be sent across a new connection. The server will process this request and then close the connection. For security reasons, no direct reply is made to the cancel request message.

I'm not suggesting we would handle cancel requests in the proxy but we want to at least log a descriptive error message when a client sends it.

Yeah, handling that would be extremely complicated. But good catch, I'll handle it with some kind of grace

Beautiful!


Single file import

How can I build a single JS and CSS file import? I don't want to install an npm package and complicate my old project front-end workflow, so it will be very helpful if I can get a dist version of the JS and CSS and import it directly with my project using CDN or local static file?

<EMAIL_ADDRESS>for Vue 1.x support
<EMAIL_ADDRESS>for Vue 2.x support

  Test single file import
  <vue-multiselect v-model="value" :options="options">

but this error appeared:
Uncaught ReferenceError: MultiSelect is not defined

Any help?

After adding Multiselect with the

the new error
vue.js:525 [Vue warn]: Failed to mount component: template or render function not defined.
(found in component <vue-multiselect>)

:D Thanks man!
I use
VueMultiselect: window.VueMultiselect.default

and it working now.
Thanks again 👍


NDArray usability improvements

Add .rank() and .size(int) methods
Rename SerializedNDArray to something shorter and more user friendly

Rank and size methods added here: https://github.com/KonduitAI/konduit-serving/pull/430


Caching Rules panel is seperate from Azure?

Clicking the "Caching Rules" button only allows you to open another separate panel, there should be instructions for using this panel instead.

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

ID: 454efdf2-6764-efd3-0c96-b372bd7fc436
Version Independent ID: 73f53a96-7cfc-897f-c7d7-bc07740db699
Content: Manage expiration of web content in Azure CDN
Content Source: articles/cdn/cdn-manage-expiration-of-cloud-service-content.md
Service: cdn
GitHub Login: @mdgattuso
Microsoft Alias: magattus

@VergilPrime Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Assigning to PM for review
#reassign:@sohamnchatterjee

#please-close


fix markers offset

Issue was solved in https://github.com/flower-platform/react-timeline-10000/pull/29


Update starter kit

Please read and mark the following check list before creating a pull request (check one with "x"):

[X] I read and followed the CONTRIBUTING.md guide.
[X] I read and followed the New Feature Checklist guide.

Short description of what this resolves:
Updates starter kit to latest master

Shouldn't you have made this PR against the starter-kit branch and not the master ?


RAT result text no certificate (EXPOSUREAPP-8544)

Ticket
Use figma text when no RAT test certificate is available or requested

Martin Hermes confirmed that "Sie können den hier angezeigten Befund auch als Nachweis für das Vorliegen eines negativen Schnelltest-Ergebnisses verwenden....." is outdated.
In addition, he said that https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-8544 should not be considered a bug, but a user story, as we then need to distinguish two cases (user has not requested digital certificate, user has requested digital certificate + test site doesn't support it), and we need to consider i/OS then as well.
So this PR is obsolete and can be reverted.


Homebrew installer documentation is wrong

What happened:
There is no gardener/tap/gardenctl-v2 in https://github.com/gardener/homebrew-tap.
What you expected to happen:
For brew install gardener/tap/gardenctl-v2 to work as per the readme found here: https://github.com/gardener/gardenctl-v2#installation
Got an error that the formula was not found.
Enviornment:
MacOS

The issue is that there is no formula with the name gardenctl-v2 in the tap.
`brew tap-info gardener/tap --json
[
{
"name": "gardener/tap",
"user": "gardener",
"repo": "tap",
"path": "/usr/local/Homebrew/Library/Taps/gardener/homebrew-tap",
"installed": true,
"official": false,
"formula_names": [
"gardener/tap/gardenctl",
"gardener/tap/gardenlogin"
],
"formula_files": [
"/usr/local/Homebrew/Library/Taps/gardener/homebrew-tap/gardenctl.rb",
"/usr/local/Homebrew/Library/Taps/gardener/homebrew-tap/gardenlogin.rb"
],
"cask_tokens": [
],
"cask_files": [

],
"command_files": [

],
"remote": "https://github.com/gardener/homebrew-tap",
"custom_remote": null,
"private": false

}
]`
i initially thought that you might have kept the same formula name and upgraded the version but that was not the case. The best bet is to use curl and install from github release as per the docs

It should be fixed once we release the first version (2.0.0). We already have the workflow in place that will create the formula https://github.com/gardener/homebrew-tap/blob/master/.github/workflows/update-gardenctl-v2.sh

/close as the first version is released and it should work now


Avoid using scientific notation

With default scipen=0, resulting bed files may contain "1.27e+08" instead of "127000000" (example in GRCm38/vM14/promoters.3000.bed.gz), which by some downstream bed tools will be read as 1.

Thanks @bug1303! Sorry, this went unnoticed for a long time.


Metadata is missed in child classes for models with HubMixinModel

Describe the bug
If ModelHubMixin is added to the model's base class, then metadata (such as repo_url, docs_url, ...) is missed in any class that inherits a class with mixin (its easier to show with an example, see below).
import torch
from huggingface_hub import PyTorchModelHubMixin

class BaseModel(
    torch.nn.Module,
    PyTorchModelHubMixin,
    repo_url="my-repo",
):
    pass

class DummyModel(BaseModel):  # <--- inherit BaseModel
    pass

base_model = BaseModel()
print(base_model._hub_mixin_info.repo_url)
# my-repo

model = DummyModel()
print(model._hub_mixin_info.repo_url)
# None

Is it supposed to be that way or is it unexpected behavior?
This happens because in__init_subclass__ we override cls._hub_mixin_info.
https://github.com/huggingface/huggingface_hub/blob/main/src/huggingface_hub/hub_mixin.py#L215
Would it be better to update parameters for _hub_mixin_info instead of overriding them?
P.S.
Arguments can be provided for DummyModel, and that would be correctly handled
class DummyModel(BaseModel, repo_url="new-repo"):
    pass

model = DummyModel()
print(model._hub_mixin_info.repo_url)
# new-repo

System info
- huggingface_hub version: 0.24.0.dev0
- Platform: Linux-5.15.0-1056-aws-x86_64-with-glibc2.31
- Python version: 3.10.9

Thanks for the report @qubvel! This is indeed a bug. Fixed it in https://github.com/huggingface/huggingface_hub/pull/2305.


Include option to include Bitbucket Pipeline to project

CI pipelines were configured in https://github.com/sixfeetup/cookiecutter-sixiedjango/pull/114 and https://github.com/sixfeetup/cookiecutter-sixiedjango/pull/111


AZ Cli not working with Python > 3.6

This is autogenerated. Please review and update as needed.
Describe the bug
when running az an error message is received if python version is not equal to python 3.6
Command Name
az
Errors:
-bash: /usr/local/bin/az: /usr/local/opt/python/bin/python3.6: bad interpreter: No such file or directory
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
``

Expected Behavior
Environment Summary
Darwin-18.7.0-x86_64-i386-64bit
Python 3.7
Shell: bash

azure-cli 2.0.77 *

Extensions:
aks-preview 0.4.17

Additional Context

@AnassKartit can you provide more information on how your installed azure-cli?

Close due to inactivity. Please feel free to reopen the issue if it still exists.


Update conditional-access-user-flow.md

Add template for sign-in risk-based CA policy.

@sjiang26 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Taking over PR ownership of this doc update from Vikas. Replacement of this PR: https://github.com/MicrosoftDocs/azure-docs/pull/73778

(Internal note: This pull request has not been PR-reviewed--links and formatting checked, etc. I do see that locales need to be removed from docs.microsoft.com URLs. Awaiting author approval for PR review.)

@videor
I'm moving these changes to the private repo. I will close this PR once that one is signed off.

PR created in private repo, and author review requested. Closing this.


MDC Web is based on Sass, yet Sass is not well supported in React tools

Material-components-web is being ported to different libraries, including Vue, and it seems any library or framework other than React has been happily integrated with Sass.
It is known that the state of styles in React is a mess. This mess is two fold: First whether to write css in javascript. Seconds whether to process css by tools like Sass.
Another problem is starting a new project with React is hard. Hence, many of us opt to use CRA so that we can delegate dealing with nightmares like Webpack to other developers, which leads us to another problem: Weak or nonexisting support of Sass in CRA.
There are half baked approach for how to have Sass processing in CRA 1.x. None of them, including the one suggested in material-components-web-react guide, are ideal.
Sass is supposed to be supported in CRA 2.x, but it only works properly for the application code, and not for the npm packages that import sass files from other npm packages, which is the case of material-components-web-react components. Specifically see https://github.com/facebook/create-react-app/issues/4651, https://github.com/facebook/create-react-app/pull/4195 and https://github.com/facebook/create-react-app/pull/4195#issuecomment-398739989.
Unfortunately, CRA authors are highly opinionated, inflexible and not very responsive when it comes to these Sass issues. At the moment, using material-components-web-react with CRA 1.x is possible with some hacks, and completely broken in CRA 2.x. Even Google project material-components-web-catalog uses an ejected version of CRA 1.x.
Given these high barriers, and given that Sass is a hard dependency of developing production quality with Material-components-web, the question is what can be done to stay away from Sass mess in React tools? Specifically, is it possible to change sass imports in material-components-web-react so that it can work with CRA 2.x, without CRA code being changes?

@moog16 Would it be possible to prefix the sass import path of external dependencies with a tilde ~? That might help us to not depend on CRA for resolving this.

@jimbojetlag How would adding the ~ help? You would still need some type of sass importing tool to use those files, correct? Also I believe if the Sass dependencies don't have ~s then we will still see that same issue.
RE MDC React Guide:
I understand that modifying the package.json is not ideal, but it is fairly straightforward. And once setup it works. What other issues do you run into with this process?

@moog16 You are right about Sass dependencies as demonstrated in the below:
Currently with CRA 2.0, importing an MDC React Sass module like this:
// App.css
@import<EMAIL_ADDRESS>
, gives this error:
Failed to compile.

./src/App.scss)
Module build failed:
@import "@material/top-app-bar/mdc-top-app-bar";
^
      File to import not found or unreadable: @material/top-app-bar/mdc-top-app-bar.
      in<EMAIL_ADDRESS>(line 1, column 1)

If we add ~ prefix in the MDC React module:
// @material/react-top-app-bar/index.scss
//@import "@material/top-app-bar/mdc-top-app-bar";
@import "~@material/top-app-bar/mdc-top-app-bar";

, then the error gets propagated to the dependency, in this case an MDC Web module:
./src/App.scss)
Module build failed:
@import "@material/top-app-bar/mdc-top-app-bar";
^
      File to import not found or unreadable: @material/top-app-bar/mdc-top-app-bar.
      in<EMAIL_ADDRESS>(line 1, column 1)

I cannot see a way for MDC React to stop this error propagation.

RE MDC React Guide:
I understand that modifying the package.json is not ideal, but it is fairly straightforward. And once setup it works. What other issues do you run into with this process?

The guide is based on CRA 1.x, I was trying to get MDC React work with CRA 2.x, which claims to support Sass and sooner or later will replace the current version, making the guide obsolete. I understand that CRA 2.x is still in alpha.

It may not be as heavily supported as CRA (and not Facebook approved), but I'm sure there are some pretty solid ones. I was going to explore other options and link them in MDC React's docs. How does that sound?

The difference between CRA and other boilerplates, apart from being official, is that CRA is not a boilerplate. Boilerplates are like ejected CRA, that is you as the developer will inherit the future maintenance burden of the build tools. Depending on the project size, this maintenance may not be trivial.
I think the getting stared guide should continue to be based on CRA, but we need to push CRA to have Sass support for dependencies. Like I explained at the beginning of this issue, Sass is not a first class styling tool in React and it community, yet it is the case for MDC. This may cause MDC React having a hard time.

I agree integrating Sass with CRA has been a big hurdle for us to overcome, but we've been able to get it working between the catalog and using the getting started guide. I think its too early to be looking at CRA 2.0 since its only in alpha. As you know, a lot can change while in alpha. I do see that CRA is stating that they will support Sass compilation, but to what extent and how exactly it'll be enabled is still up in the air.
+1 to being different from other boilerplates as it removes "webpack hell" and maintenance.

Noting that following the getting started guide on Windows 10 leads to this sass issue as described here. I've seen half a dozen solutions, but for someone that's not an expert at webpack configurations - it only leads to confusion. Going try out https://github.com/jamesmfriedman/rmwc to see if that gets me where I want to be.
File to import not found or unreadable: @material/react-button/index.

@mswezey23 I just tried CRA with @material/react-button on windows 10 and it worked fine.
Let me know what issues you're running into and I can help :)

I respect the amount of work and technological decisions that have gone into Material Components Web and this project. As far as Sass goes, in my opinion it's better to replace it with more modern CSS preprocessors like PostCSS or CSS in JS solutions like styled components for all practical purposes (especially if you're using a dynamic frontend view framework like React). I understand that MDC may have a hard requirement on using Sass for design purposes, and I'm sure the styles are high quality, but it would be great if we could wrap the Sass approach in alternatives that don't require end users to compile or write Sass files. This would allow users more of a choice in tooling. For example, Bootstrap 4 is written in Sass an provides CSS custom properties for customization without a build tool (I think this would be the easiest approach for dynamic theming in React). Additionally, Material UI is written in a fork of CSS in JS, and other CSS in JS solutions or even plain CSS can be used instead (though there are unfortunately a lot of issues with selector precedence when writing a project in CSS in JS and trying to support alternative CSS in JS tools).

I am a fan of CSS in JS and PostCss. We do have PostCSS in our build process, and am not sure how we could use PostCSS to make things easier for the end developer.
I haven't used much CSS in JS in projects. How would something like that look like? And how would you go about selecting a framework.  Just based off of this list there are a ton of libraries out there.
Would you be willing to do a little bit of code in one of the components to show us?

Personally if I maintained a project in Sass and I didn't need dynamic styles, I would port it to modern CSS (mainly custom properties), optionally using postcss if necessary for legacy browser support. I understand the team may want to continue using Sass, but you can still create CSS custom properties in Sass so they can be changed by end users that don't use Sass (see Bootstrap 4). Then a plain old CSS build can be distributed with the package, which would solve the issue of this not working with CRA without having to wait for v2 to stabilize.
I'm pretty new to CSS in JS to be honest, but I don't think it would be possible to use it in core unless you want to completely rewrite and rearchitect all styles in MCW and MCWR. That being said, Styled Components looks like the strongest option to me, but it only works with React. Emotion has a very similar syntax that's almost completely compatible with Styled Components, but it works in any JS framework. Both support writing Sass, but I would still prefer writing CSS custom properties if I were using a CSS in JS library.
Ultimately I think just adding CSS custom properties to Sass is the best approach, since they can be set in CSS, CSS modules, Sass, Less, CSS in JS, etc.

We already use CSS custom properties in a few of MDC Web's packages. However, they are not a silver bullet. Here are a few problems we've already encountered in MDC Web:

IE 11 doesn't support CSS custom properties. Handling variables at the preprocessor level allows us to expose customizations that can work in all browsers MDC Web supports.
There are things we would like to use custom properties for, but can't due to current limitations in CSS. One prime example is maintaining colors and alpha values separately and composing them together, which can be done in Sass, but has no widely-supported CSS equivalent.
Using a preprocessor allows us to perform calculations (some of which have no CSS equivalent) based on defined variables. Thus we can expose Sass variables that are configured pre-calculation rather than making users calculate the correct value themselves; this would not be possible with CSS custom properties exposed through the built CSS.

Also, tangentially, I'm not really sure what warrants the insinuation that Sass isn't modern. It's being actively worked on full-time. As far as I can tell, PostCSS plugins would (ideally) just be a different means to the same end.

I think it would really help the non-Sass development workflow if we added as many custom properties as possible, allowing users to use Sass in more advanced use cases.

I'm aware that IE doesn't have custom properties, but often it's more useful to have basic static custom properties than fully dynamic custom properties, so I think polyfills solve the issue well (Sass doesn't have dynamic variable at all, so it's not any worse than Sass's support given the right preprocessor).
That color and alpha problem sounds interesting, is it solvable with math or any other new specs?
I'm not sure I understand, couldn't you make a custom property based on a calculation from another custom property? Is this only an issue for calculations that can't be made in standard CSS (in which case a user can reimplement it in JS to avoid using Sass)?
To be honest, I don't like Sass, I think it encourages antipatterns like deeply nested selectors and specificity hacks. That being said I'm mainly against using it in React projects because it has too many features that break standard CSS enough to make extension via CSS in JS difficult. I'm fine with allowing users that like Sass to continue using it, but it causes issues with common React styling practices.

@lynnjepsen please do not direct discussions to a chat channel. There are three good reasons for this:

Whatever happens in those channels, are not searchable and googlable by others. Many people who have contributed to this issue, for instance, would have never been able to contribute and make suggestions.
There is no structure in those chat channels, there are no such things as threads and states to track the progress of a discussion. Those texts are just ephemeral.
Your team on Discord is not responsive. Many questions are never answered. My questions and concerns in this very issues would have had a single line respond, if any. Compare that with the lengthy discussions that happened here.

You could instead simply tag these issues as discussion type.


feat: add typescript payload options

This adds more typescript payload options

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Release-1.26] - pods with runtimeClassName: nvidia get killed after a few seconds

Backport fix for pods with runtimeClassName: nvidia get killed after a few seconds

#7130

I'm going to close this out as we weren't able to reproduce the main issue itself and are waiting on input there from the reporters. The change looks good and doesn't cause regressions.


Feature Request: Masking

Is it possible to support Flash's masking in Flump?

What about support for masking MoveClips in the future? Animation effects are really limited without the ability to mask.

Hey SoleilSmile - it's possible, though it's unlikely to happen unless somebody who needs the feature also implements it, as it's a non-trivial amount of work.
However, with Starling's recent support of the stencil buffer it may be a bit easier to implement now than when we began on Flump a few years ago.

were there ever any updates on this?


Update index.html

These examples are intentionally broken. No need to submit fixes. But glad you got it working!


Athena driver

Hi, thanks for usql, I really quite enjoy using it and is the only SQL tool that makes me think about leaving psql by choice (I also have to use SQLite and Athena).
On the Athena though, I am trying to connect via usql 'athena://____:____@athena.eu-west-2.amazonaws.com/dev-databasing?s3_staging_dir=s3%3A%2F%2Fmy-bucket-%2F' which is the best I've been able to figure out, but it's giving the error:
error: athena: sql: unknown driver "athena" (forgotten import?)

However if I do \drivers I get
$ usql
Pager usage is off.
Null display is "·".
Type "help" for help.

(not connected)=> \drivers
Available Drivers:
  athena [s3, aws]
  avatica [av, phoenix]
  bigquery [bq]
  --- SNIP ---

It could well be user error, but I'm a bit flumoxed... help would be appreciated.

$ usql --version
usql 0.10.0

@forbesmyester can you check if the latest version of usql fixes this issue? Thanks.

Hi @kenshaw
I have:
$ usql 's3://__S3_STAGING_DIR_NOT_URL_ENCODE_WITH_TRAILING_FORWARDSLASH_ALSO_NOT_ENCODED?WGRemoteCreation=true&accessID=__THE_ACCESS_KEY__&db=__DATABASE_NAME_PROBABLY_URLENCODED_&missingAsEmptyString=true&region=eu-west-2&secretAccessKey=__THE_SECRET_URLENCODED__'

Which does work / can query, though \d does not (not supported by awsathena driver).
$ usql --version
usql 0.12.13

Can you open another issue about implementing metadata introspection for Athena, so that the \d commands and completion would work?
Looks like the issue reported here is resolved and you could close this one.


flatten dict

Add the flattening dict capability to transform a record (json) to a flattened dictionary.

Solved in #15.


Support user style sheet as mandated by CSS 2

I want support for user style sheet as specified in the CSS spec[*]. In practice, this could be implemented without any UI. The feature would be specified as follows:

During VS Code startup, check if file ~/.config/Code/User/userstylesheet.css exists (and the corresponding alternative for Windows users).
If that file exists, inject it as <link rel> element using absolute file: URL into the DOM of workscape.html: <link rel="stylesheet" href="..." />
Proceed as usual. None of any other VS Code implementation should even mind that user style sheet has been added. The user is taking full responsibility for all modifications done via user style sheet.

Document that this feature does exist and none of the class names, id selectors or DOM structure are part of permanent API, and those will be changed without a warning both during runtime and as part of software updates.
Explicit non-features:

Ability to have multiple CSS files.
Ability to specify different CSS files for different projects.
Any kind of automatic reload of the CSS when the user stylesheet is modified.

In practice, the runtime performance cost would be one stat() syscall during the VS Code startup if this feature is not used and addition of one DOM element in case the userstylesheet.css does exist. Plus obviously any overhead that the users want to add with their custom styles, which is entirely on their own responsibility.
This feature is absolutely needed for accessibility alone. VS  Code users are already using ugly hacks such as https://github.com/be5invis/vscode-custom-css which cannot work in multiuser installations even in theory (e.g. VS Code installed via apt on Ubuntu Linux). The idea that everything that anybody could ever want to change change in the UI should be published as an official extension point doesn't hold water either. User style sheets were originally designed to be used for use cases where one user has some special need!
If I've understood correctly, this kind of feature (with more complex specification) has been denied previously because it supposedly cannot be understood (by software developers?!?) to not declare permanent API for DOM structures, or because implementing it would be so hard.
Would you accept this feature? If it's about resources needed to implement it, I'd be willing to create the missing patch for the spec I listed above, if that's what this takes.
If you do not want to allow this e.g. for branding or political reasons instead of technical issues, just say so and we know for real.
[*] The actual CSS spec says (emphasis mine):

UAs must allow users to specify a file that contains the user style sheet. UAs that run on devices without any means of writing or specifying files are exempted from this requirement.

Sorry, a user style sheet goes against a design philosophy of VS Code. A user style sheet would work against a DOM structure and class names that is not documented and we consider internal. To evolve, refactor or improve VS Code, we need the freedom to make changes to the UI. Each change would break user style sheets. This would result in frustration with user style sheet providers and a bad user experience: User style sheets that are half broken, resulting in potentially strange UI glitches that are hard to debug on our side.
Instead, we aim to a well-designed extension API. This one is documented, comes with tooling and samples, and is kept stable across all upcoming releases of VS Code.
Duplicate of https://github.com/microsoft/vscode/issues/459

This would result in frustration with user style sheet provider

How about the amount of trustration when this feature is not working at all currently? If DOM was changed too much to apply the existing style sheet, in worst case the situation would fall back to the current situation because the user written selectors would no longer match anything.
This is no different from how user style sheets work in normal web use.

user style sheet goes against a design philosophy of VS Code

I interpret that this is the real reason to not do this.

The worst case is half applied style sheets, causing UI glitches impacting the look and usability of VS Code resulting users to file issues (and blame) VS Code for it.

This is no different from how user style sheets work in normal web use.

Do you have examples where the stylesheet of a Web page is user provided?

Sorry my ignorance about what user style sheets are and can include. If styling is limited to a well-defined set of properties, that's certainly in the spirit of VS Code: We want styling to happen in a controlled, well defined and documented way, that allows us to evolve the product without breaking any users. We already allow that through color and icons themes as well as various settings in the UI.
If there's anything missing that you would like to style, please file an issue.
You mentioned the vscode-custom-css extension that is about injecting a stylesheet that works against everything in the DOM: that's out of scope.

Sorry my ignorance about what user style sheets are and can include. If styling is limited to a well-defined set of properties, that's certainly in the spirit of VS Code: We want styling to happen in a controlled, well defined and documented way, that allows us to evolve the product without breaking any users. We already allow that through color and icons themes as well as various settings in the UI.
If there's anything missing that you would like to style, please file an issue.
You mentioned the vscode-custom-css extension that is about injecting a stylesheet that works against everything in the DOM: that's out of scope.

In a light of https://github.com/iocave/customize-ui/issues/156, it seems like changes in VS Code already "break users", thus I believe that giving more freedom to people that want to customise VS Code is a lesser evil, even if those customisations break from time to time.

Very odd to me that product made for developers doesn't allow them to "hack" it.

Why oh why did you break compatability with Iocave/customize-ui . I am not updating to 1.74, am staying on 1.73 until I find an alternative to VSCode. This much hand holding for programmers is insulting.

If there's anything missing that you would like to style, please file an issue.

I have a lot of small things that I would want to tweak but I don't think that many other people feel the same. Do you really want me to file a new issue for every little thing simply to spam your issue tracker so that you can then mark it as "won't fix" because implementing official API point for every little thing makes zero sense?
Again, do you think that VS Code which is targeted to software developers has user base with lesser skills than Firefox that supports this out of box?
The only thing needed is ability to load a single CSS file from the user profile directory if one exists. Feel free to document that any CSS selectors one could use there will be changed without notice and before submitting bug reports, the issue must be repeated without user stylesheets.
Right now my customizations are in a CSS file which I copy paste to developer tools view every time after restarting VS Code. Do you think that's a good UX?


Changes

Great work so far. Can I hopefully add something worthwhile? Please let me know.
https://github.com/sc-pulsion/openvas-docker/commit/99b4095f2ea9a918fa7505a0af739fd563eeff62
Initially I was annoyed when I ran the container then added a credential using Greenbone. I am running my Ubuntu 16.04 Docker Hyper-V VM on a Windows server 2012 R2 host if that makes any difference. It seems that GPG takes HOURS in this situation due to entropy. When I left it overnight, the GPG process on the container was finally complete.
The 'fix' for my initial issue was to add the '-v /dev/urandom:/dev/random' to the test.sh file. It seems that mapping the entropy(?) of the host to the container means that something that took hours and hours previously takes less than a second and has no impact on performance any more. (yes, urandom and random are different - this just worked). We are mapping the host to the container here so no doubt there is some security issues
The rest of the changes are just optimisation and bug fixing. Hopefully they make sense.
Summary
Add smbclient package to Dockerfile - allows SMB test
Make setup.sh and start.sh executable in Dockerfile - this is why nothing was updated previously
Remove port 80 binding from Dockerfile - not used
Remove rebuild from setup.sh - not required
Remove admin user creation from setup.sh - not required
Remove openvassd kill from setup.sh - oh the humanity - and not required
Map the hosts urandom to the containers /dev/random - used to speed up the initial GPG stuff majorly
Next?
Next up, assuming you agree, would be to incorporate setup.sh into the Dockerfile, then (as I have seen in the issue tracker) to persist data. We need to remember old information especially when we report stuff as false positives.

Hi @sc-pulsion, thanks for your feedback! I'm going to look into this a bit tomorrow and see what we can do.  I really appreciate you giving back to the project. I'd like to do a bit of testing with your work.
As you probably sensed, alot of this project was built up over time to make things "just work" so I'm always open to others suggestions and help!  I haven't heard of the GPG issue before so that's new to me.  That issue may be unique to Hyper-V virtualization but regardless, that could be something useful for the docs.

Hi @mikesplain thanks for getting back to me!
Please test all you can but can you try with my latest commit rather than the one I linked above? I have made quite a few changes again. You can see everything in the commit history.
I have also tested database persistence using my new build which seems to work fine so far at least, although much more testing is required. We only need to mount the database folder e.g.
docker run -d -p 443:443 -p 9390:9390 -p 9391:9391 -v ~/openvasDB:/var/lib/openvas/mgr --name openvas openvas

@mikesplain I've added a new branch today that also includes the w3af scanner.
https://github.com/sc-pulsion/openvas-docker/tree/enable_w3af_scanner_test
The only issue I have right now is that even though the scanner shows up in OpenVAS as a separate scanner, I don't get the option to use it when creating a new scan. Have you seen that behaviour before?

Thanks for your additions. For now I'm going to close this as we've moved to OpenVAS 9.  Please reopen if you have any issues!


could ramme support proxy for that chinese cannot visit Instagram directly,

Ramme already supports this (or other supports applications that'll load proxies)

This isn't something that needs, in particular, to be supported by Ramme itself, but it is rather something that you should configure in your OS. In fact, every OS that I know of right now supports using a VPN or some other proxy service to redirect traffic for all or specific applications on the computer through the aforementioned proxy.
With this in mind, the feature requested is not something that would typically be implemented within any arbitrary application, but rather a feature that already exists in the OS itself. Closing the issue.


Problem Description
请教一下，目前官网已支持免登录使用，我按照项目介绍部署了最新的代码，还是需要填入openai key才可以正常使用，能否不用输入key也能使用本项目搭建好的网站？

Solution Description
如上。
Alternatives Considered
No response
Additional Context
No response

这种需要逆向转API或者找镜像站的项目吧

I'd love to be a part of this in some way, although I don't know how to read Chinese and I can't code well enough yet to ask to be a part of such a cool project. I will continue to check them out and watch folks who do know what they're doing.

https://chat.chatapi.asia/


stackitem.Deserialize with custom limits

I'm looking for a workaround for this issue https://github.com/neo-project/neo/issues/2845 and a simple doubling of the limit would already be sufficient for my use-case, except I can't manually set it. It can be as simple as making this public (I think that would work at least)
https://github.com/nspcc-dev/neo-go/blob/bd26b9db8307567e77154d7a2fe17203b90b655b/pkg/vm/stackitem/serialization.go#L40-L44
It that an option?

We've workarounded this problem by ignoring contracts that can't be deserialized, but for some special cases like this maybe we can expose it. We have SerializationContext exported already (but it's not exactly symmetric to deserContext). @AnnaShaleva?

Any updates?

Oh, sorry, I've missed the GitHub notification, let me check it.


Escaping ' chars in field

The ConvertFrom-ExcelToSQLInsert did not escape ' characters and fails when a field has a ' character in it

Thanks for the PR. Please check/resolve the errors found in the checks that were run.


Error list does not get updated after a while

This issue is not new but the bigger our code base gets the sooner after a re-launch of the vscode window the error list stops showing the actual output of the tsc watcher.
Also, as soon as the problem occurs, 'go to definition' and other operations that need to understand the code stop working.
Only solution so far: Close and re-open vscode. We're doing this up to 50 times a day.

Yes and it's been there since at least the last year. We're using .NET reflection in order to generate a lot of TypeScript code and type definitions to describe our backend services and data types. This process replaces some 200 .ts and .d.ts files during the build process. That definitely kills the language service. But it stops working even without generating any file after some time (10 minutes or so).

We are facing the same issues with the latest stable. I assumed it's sth related to the "Angular Language Service" Plugin. I'm kinda fresh in the codebase/project which is quite huge. Me and others would love to use VS Code but this issue blocks us working productively and we have to switch to other alternatives...

Go to Definition takes up to 20 seconds.

I will try to find out the reasons tomorrow with the methods described here
VSCode Version: Latest Stable
OS Version: Windows 10
TypeScript Version: 2.6
Angular 5 Projekt

@markusmauch
Please collect the TS Server log on vscode insiders:

Add "typescript.tsserver.log": "verbose" to your user settings and restart VSCode.
Reproduce the issue
Run the TypeScript: Open TS Server log command. This should open a folder with a tsserver.log file. Open that file

Look at the end of the file. Can you share the last few line of what is going on? If you can share the  entire logs I can try looking through them

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this


Doesn't show cached files with 'artisan serve'

To see cached files using the PHP built-in web server you need to add this to the bottom of server.php:
if (file_exists(__DIR__.'/public/page-cache/pc__index__pc.html'))
    require_once __DIR__.'/public/page-cache/pc__index__pc.html';
else
    require_once __DIR__.'/public/index.php';

Ok then, would you prefer it if I submitted a pull request instead?

An issue is for... well, issues. You haven't described any issue here, so I closed it.


Check if related entry exists

If the given ID not exists it tries to insert it anyway and does not check it. Maybe this could be done via a validator?

Such validation should be performed in the model itself, the one you are attaching this behavior to. So, to continue the example given in the README:
public function rules()
{
    return [
        //...
        [['author_list'], 'each', 'rule' => [
            'exist',
            'targetClass' => Author::className(),
            'targetAttribute' => 'id'
        ]],
        //...
    ];
}

Just keep in mind that such validation will make an SQL query for every id passed in the array. You're welcome to implement your own validator optimized for efficiency.


Tweak NE to OSM transition

Refs #205.
This changes the zoom test for NE from <9 to <8 for landuse, landuse labels and roads. Boundaries were already <8.
Additionally, made a couple of fixes to existing layers:

Minor speed-up to boundaries by doing including a bbox && test as part of the join condition. This helps at lower zooms where there are many county boundaries. Better would be to cut them out at, say, zoom 10 and lower if we don't need to render them.
Several queries in the water layer weren't returning their responses ST_AsBinary(), but this didn't seem to cause any problems. In any case, for consistency, they all now have that.

@rmarianski, could you review, please?

:+1:
Good idea with the bbox filter on the join, and great catch on the ST_AsBinary. My guess is that postgresql inferred to make it binary if any of the queries in the union had that set, but like you say, it's better to be consistent.


memory corruption

I got a memory corruption while running it in ros2 humble for around 30 mnitutes.
The output is below
[dlio_odom_node-4] double free or corruption (!prev)
I have never faced this issue so not sure if is reproducible.
I will post it here one I face the same issue again.

I have also encountered with the same error. After running the code in ROS2 for a while, it says "double free or corruption (!prev)" and stops.
Can you help?


cyber-markets-47-trade

implements :
{"subscribe":"trades"} subscribe for all tokens pairs from all supported exchanges
{"subscribe":"trades","pairs":["BTC_ETH","ETH_USD"]} subscribe for given tokens pairs from all supported exchanges
{"subscribe":"trades","exchanges":["Poloniex","HitBtc"]} subscribe for all tokens from given exchanges
{"subscribe":"trades","exchanges":["Poloniex","HitBtc"],"pairs":["BTC_ETH","ETH_USD"]} subscribe for given tokens pairs from all supported exchanges

Fix build

@mgergalov @hleb-albau there is one more issue with market pairs - BTC_ETH and ETH_BTC markets forms via same trades, but type of trade (when we turn market pair) changes (sell to buy, and vice versa)

known issue, already have separate issue


Doesn't use "-pthread" on building precompiled header, if in add_definitions()

cmake states "cotire 1.7.2 loaded", and "CXX target myLibrary cotired."
"Building CXX precompiled header myLibrary/cotire/myLibrary_CXX_prefix.hxx.pch" shows clang is not being given "-pthread" as a compilation option.  myLibrary's CMakeLists.txt includes "add_definitions(-DXYZ -pthread)".  But, clang is being given "-DXYZ" as a compilation option.  So, I think cotire is maybe only passing along add_definitions that start with -D, or something along those lines.
Building CXX object myLibrary/CMakeFiles/myLibrary.dir/myLibrary.cpp.o" shows clang is being given "-pthread" as a compilation option.
This causes clang to give:
error: POSIX thread support was disabled in PCH file but is currently enabled
Using gcc, it does the same, except with this error:
error: .../cotire/...hxx.gch: not used because `_REENTRANT' is defined [-Werror=invalid-pch]
Running cotire from git (1.7.2), cmake 3.2.20150515-g2e4ea, clang (3.7.0-pre, git trunk 236925), gcc (6.0.0-pre, 5/17/2015).
I got around the problem by moving "-pthread" from add_definitions() to set(CMAKE_CXX_FLAGS_DEBUG...)
Happy to do that, and it makes more sense there.  But, the cmake documentation says you can specify switches with add_definitions() rather than CMAKE_CXX_FLAGS_*

Starting with CMake 2.8.12 it is recommended to use add_compile_options instead of add_definitions to add compile options, i.e.:
add_compile_options(-pthread)

All you need to do is link with pthread
target_link_libraries(BUILD_ARTIFACT pthread)
BUILD_ARTIFACT can be your project, or library name
P.S Add this line after defining your ARTIFACT


workon open issues

We could make workon a bit more "universal".
For example, if I want to work on an issue that has already been created, right now the workflow is
doing create pr <issue id>
git checkout <branch name>

What about allowing doing workon <issue> to automatically detect if the <issue> is an existing <issue id> and, if so, to create a PR based on that and checkout that branch?

Thought about this more. doing workon has 3 options, one for issue type, one for issue parent, and one specifying the reviewers.  If we allow for doing workon <issue id>, the first two options don't make sense. It also make doing workon a bit harder to document / explain.
That leaves the problem that doing create pr <issue id>  -a  -d -r "yourself" -c --delete-source-branch is too verbose. Setting up those defaults for those options (after we implement #29) is an option but also too involved. After we implement #27, we could create a new doing issue workon <issue id>. But having doing workon and doing issue workon is confusing.
The cleanest solution I can think of now, is change the defaults of doing create pr to match what doing workon is doing. If you don't want things like always creating a draft PR, always assigning yourself as reviewer to a PR, and setting autocomplete to true, you can change the defaults in the config.


Playstation Assets?

I have still the Game for the PSX Game Console. Are the assets compatible to OpenVIII?

Some of them are but we cannot read the iso. Deiling I guess knows where
the data is via offsets. Might be the best map we have right now. It's
possible one day. But we can read the textures and such.
On Sat, Feb 15, 2020, 2:39 PM nille02<EMAIL_ADDRESS>wrote:

I have still the Game for the PSX Game Console. Are the assets compatible
to OpenVIII?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MaKiPL/OpenVIII/issues/148?email_source=notifications&email_token=AAH45AJGZQJCSJFF4GDQNETRDBAIPA5CNFSM4KV3UDSKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4INZM6FQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH45ANDQUI4FV4L6TWSLUTRDBAIPANCNFSM4KV3UDSA
.


[REWARDS-417] Update Dedupe Queue TTL

Context
REWARDS-417 investigation led me to Chore, the job scheduler for SQS in TJS.
After some discussion and digging, it looks like the deduplication logic is removing messages from the queue before the retention window expires. This race condition happens when we 1. consume a message and 2. add the message to the dedupe  cache with a TTL based on the SQS visibility timeout. Between 1 and 2, some time passes which can be less than a second up to 2 seconds. (link to data) Sometimes the message in the dedupe cache does not expire before we see another request for the same Reward ID. This causes the message to be removed from the queue unintentionally.
Change Log

Created new attribute for received_timestamp on UnitOfWork that is auto populated with Time.now on creation
In Consumer, capture received_timestamp and pass that in to dedupe logic
In Worker, pass in UnitOfWork.received_timestamp to dedupe logic
Changed method definitions to accept received_timestamp
Added helper methods to adjust timeout
Added RSpec tests on new helper methods and updated methods

Example
Reward ID: 1e4651e2-9e9e-40d4-8a9d-9670d2b4996d
I greped for “dupl” in application.logs of the job-failures box to get Reward Ids that are duplicate and removed. We can see the job was deleted from the queue:
application.log.2:May 10 14:11:24 ip-172-16-9-215 tapjoyserver-jobs[1]: [2024-05-10 14:11:24 +0000 (24428)] INFO : Found duplicate job ["1e4651e2-9e9e-40d4-8a9d-9670d2b4996d", "1", 300]

application.log.2:May 10 14:11:24 ip-172-16-9-215 tapjoyserver-jobs[1]: [2024-05-10 14:11:24 +0000 (24428)] INFO : Found and deleted duplicate job NonManagedSendCurrencyJob

In BQ, I searched for the same Reward ID to see the attempt history.
It tried a total of 155 times, never succeeded, and the last run time was 2024-05-10 14:06:24 UTC.
BQ records the last attempt at 14:06 and the job is removed at 14:11, ~5 minutes after (the retry window).
Changes

Default timeout_offset to 10 seconds

The largest difference of the race condition (2 seconds) I observed, multiplied by 5.

Update Chore Dedupe logic to take in timeout_offset
Set TTL for messages added to Dedupe cache based on queue_timeout - timeout_offset

Testing
Local RSpecs pass

Updated 6/5/2024

End To End Testing (TIAB)
Instructions
Build the updated Chore gem

Checkout debugging/logging commit of Chore
Update the version.rb by incrementing minor/patch (ex. 4.4.0 -> 4.4.1)
In the Chore project build the .gem file

gem build chore-core.gemspec

Copy the gem file from Chore's root folder, probably named chore-core-<version>.gem
Paste the gem file into Tapjoyserver project's folder /vendor/cache/
Update the gem in Tapjoyservers Gemfile to the updated version

gem 'chore-core', '4.4.0

Update TIAB with Chore gem

Spin up TIAB
Push the TJS changes to your TIAB

tjsh tiab push -r

SSH into your TIAB

ssh <first.last>@<ip_address>

Install gem in the TJS directory of your TIAB

sudo su -
cd /opt/apps/tapjoyserver/current
bundle install

Send message to your TIABs SQS
1.. Login to AWS as a Rewards User under Tapjoy Development
2.. Find the SQS created for your TIAB. Should be named tapinabox_<tiab_name>_v2_SendCurrency_Failures
3. Send a message to the SQS queue

example can be found by polling the production SQS queue

Verify the changes by tailing logs

Tail the logs in /opt/apps/tapjoyserver/current/logs/application.log
Verify the message come in through TIAB by checking application.log you are tailing.
- Verify the new TTL that is being set for the deduplicate cache

Default Visibility timeout is 30 seconds, configured on SQS.
In each example, note the new TTL that is set.
Ex. 1 Pre Change (Legacy)
TTL is 30 seconds

30 seconds (sqs config)
[2024-06-04 20:05:32 +0000 (3951)] INFO : >>> MANNY <Duplicate Detector.02> New TTL for Msg ID 54638534-e774-4838-899a-737fafb4ef34 is TTL: 30

Ex. 1 Full Logs
### Pre Change (Legacy)
# Consumer Dupe Check
[2024-06-04 20:05:32 +0000 (3604)] INFO : >>> MANNY <Consumer.01> Dupe Check: message.id: aafc674e-088d-4531-9a13-89072350ce98, received_ts: 2024-06-04 20:05:32 +0000
  [2024-06-04 20:05:32 +0000 (3604)] INFO : >>> MANNY <Duplicate Detector.01> BEGIN
    Msg_Data: {:id=>"aafc674e-088d-4531-9a13-89072350ce98", :queue=>"https://sqs.us-east-1.amazonaws.com/331510376354/tapinabox_manny_v2_NonManagedSendCurrency", :visibility_timeout=>30, :received_timestamp=>2024-06-04 20:05:32.825042271 +0000}
  [2024-06-04 20:05:32 +0000 (3604)] INFO : >>> MANNY <Duplicate Detector.02> New TTL for Msg ID aafc674e-088d-4531-9a13-89072350ce98 is TTL: 30
  [2024-06-04 20:05:32 +0000 (3604)] INFO : >>> MANNY <Chore Consumer.00>, Duplicate Found? false
  [2024-06-04 20:05:32 +0000 (3604)] INFO : >>> MANNY <Consumer.02> Dupe Check: No Duplicate Found

    # Create Unit of Work
    [2024-06-04 20:05:32 +0000 (3604)] INFO : >>> MANNY <Unit of Work.01> Created w ID:aafc674e-088d-4531-9a13-89072350ce98, Consumer , Timestamp: 2024-06-04 20:05:32 +0000
    [2024-06-04 20:05:32 +0000 (3604)] INFO : >>> MANNY <Throttled Consumer.01>, CREATED UoW: aafc674e-088d-4531-9a13-89072350ce98, TS: 2024-06-04 20:05:32 +0000

      # Process Unit of Work
      [2024-06-04 20:05:32 +0000 (3951)] INFO : >>> MANNY <Worker.01> Processing Item: aafc674e-088d-4531-9a13-89072350ce98, 2024-06-04 20:05:32 +0000

        # Worker Dupe Check
        [2024-06-04 20:05:32 +0000 (3951)] INFO : >>> MANNY <Duplicate Detector.01> BEGIN
          Msg_Data: {:id=>"54638534-e774-4838-899a-737fafb4ef34", :queue=>"NonManagedSendCurrencyJob", :visibility_timeout=>30, :received_timestamp=>2024-06-04 20:05:32.825042271 +0000}
        # IMPORTANT: Note the TTL is set to SQS' Visibility Timeout Config
        [2024-06-04 20:05:32 +0000 (3951)] INFO : >>> MANNY <Duplicate Detector.02> New TTL for Msg ID 54638534-e774-4838-899a-737fafb4ef34 is TTL: 30
        [2024-06-04 20:05:32 +0000 (3951)] INFO : >>> MANNY <Chore Consumer.00>, Duplicate Found? false
      [2024-06-04 20:05:32 +0000 (3951)] INFO : >>> MANNY <Worker.03> Dupe Check: No Duplicate Found

# Errors out on TJS side (reward does not exist)
[2024-06-04 20:07:57 +0000 (3951)] ERROR : Failed to run job with error: Reward not found: 54638534-e774-4838-899a-737fafb4ef34

Ex. 2 Post Change (Updated)
TTL is 20 seconds

30 seconds (sqs config) - 10 seconds (timeout offset)
[2024-06-04 20:24:47 +0000 (30770)] INFO : >>> MANNY <Duplicate Detector.02> New TTL for Msg ID 54638534-e774-4838-899a-737fafb4ef34 is TTL: 20

Ex. 2 Full Logs
### Post Change (Updated)
# Consumer Dupe Check
[2024-06-04 20:24:47 +0000 (30508)] INFO : >>> MANNY <Consumer.01> Dupe Check: message.id: 57ea2b3c-4c7c-41e1-a357-645fd6b5b18c, received_ts: 2024-06-04 20:24:47 +0000
  [2024-06-04 20:24:47 +0000 (30508)] INFO : >>> MANNY <Duplicate Detector.01> BEGIN
    Msg_Data: {:id=>"57ea2b3c-4c7c-41e1-a357-645fd6b5b18c", :queue=>"https://sqs.us-east-1.amazonaws.com/331510376354/tapinabox_manny_v2_NonManagedSendCurrency", :visibility_timeout=>30, :received_timestamp=>2024-06-04 20:24:47.496270992 +0000}
  [2024-06-04 20:24:47 +0000 (30508)] INFO : >>> MANNY <Duplicate Detector.02> New TTL for Msg ID 57ea2b3c-4c7c-41e1-a357-645fd6b5b18c is TTL: 20
  [2024-06-04 20:24:47 +0000 (30508)] INFO : >>> MANNY <Chore Consumer.00>, Duplicate Found? false
  [2024-06-04 20:24:47 +0000 (30508)] INFO : >>> MANNY <Consumer.02> Dupe Check: No Duplicate Found

  # Create Unit of Work
  [2024-06-04 20:24:47 +0000 (30508)] INFO : >>> MANNY <Unit of Work.01> Created w ID:57ea2b3c-4c7c-41e1-a357-645fd6b5b18c, Consumer , Timestamp: 2024-06-04 20:24:47 +0000
  [2024-06-04 20:24:47 +0000 (30508)] INFO : >>> MANNY <Throttled Consumer.01>, CREATED UoW: 57ea2b3c-4c7c-41e1-a357-645fd6b5b18c, TS: 2024-06-04 20:24:47 +0000

    # Process Unit of Work
    [2024-06-04 20:24:47 +0000 (30770)] INFO : >>> MANNY <Worker.01> Processing Item: 57ea2b3c-4c7c-41e1-a357-645fd6b5b18c, 2024-06-04 20:24:47 +0000

      # Worker Dupe Check
      [2024-06-04 20:24:47 +0000 (30770)] INFO : >>> MANNY <Duplicate Detector.01> BEGIN
        Msg_Data: {:id=>"54638534-e774-4838-899a-737fafb4ef34", :queue=>"NonManagedSendCurrencyJob", :visibility_timeout=>30, :received_timestamp=>2024-06-04 20:24:47.496270992 +0000}
      # IMPORTANT: Note the TTL is set to SQS' Visibility Timeout Config
      [2024-06-04 20:24:47 +0000 (30770)] INFO : >>> MANNY <Duplicate Detector.02> New TTL for Msg ID 54638534-e774-4838-899a-737fafb4ef34 is TTL: 20
      [2024-06-04 20:24:47 +0000 (30770)] INFO : >>> MANNY <Chore Consumer.00>, Duplicate Found? false
    [2024-06-04 20:24:47 +0000 (30770)] INFO : >>> MANNY <Worker.03> Dupe Check: No Duplicate Found

# Errors out on TJS side (reward does not exist)
[2024-06-04 20:24:47 +0000 (30770)] ERROR : Failed to run job with error: Reward not found: 54638534-e774-4838-899a-737fafb4ef34

Ex. 3 Post Change (Updated + 5 sec delay after receiving message)
TTL is 15 seconds

30 seconds (sqs config) - 10 seconds (timeout offset) - 5 seconds (delay offset)
[2024-06-04 20:47:50 +0000 (10818)] INFO : >>> MANNY <Duplicate Detector.02> New TTL for Msg ID 54638534-e774-4838-899a-737fafb4ef34 is TTL: 15

Ex 3. Full Logs
### Post Change (Updated + 5 sec delay after receiving message)
# Consumer Dupe Check
[2024-06-04 20:47:50 +0000 (10290)] INFO : >>> MANNY <Consumer.01> Dupe Check: message.id: 997690ce-f1a5-4f2e-8844-3b8ae4e1ed9b, received_ts: 2024-06-04 20:47:45 +0000
  [2024-06-04 20:47:50 +0000 (10290)] INFO : [Aws::SQS::Client 200 0.066309 0 retries] get_queue_attributes(queue_url:"https://sqs.us-east-1.amazonaws.com/331510376354/tapinabox_manny_v2_SendCurrency_Failures",attribute_names:["All"])
  [2024-06-04 20:47:50 +0000 (10290)] INFO : >>> MANNY <Duplicate Detector.01> BEGIN
    Msg_Data: {:id=>"997690ce-f1a5-4f2e-8844-3b8ae4e1ed9b", :queue=>"https://sqs.us-east-1.amazonaws.com/331510376354/tapinabox_manny_v2_SendCurrency_Failures", :visibility_timeout=>30, :received_timestamp=>2024-06-04 20:47:45.330152286 +0000}
  [2024-06-04 20:47:50 +0000 (10290)] INFO : >>> MANNY <Duplicate Detector.02> New TTL for Msg ID 997690ce-f1a5-4f2e-8844-3b8ae4e1ed9b is TTL: 15
  [2024-06-04 20:47:50 +0000 (10290)] INFO : >>> MANNY <Chore Consumer.00>, Duplicate Found? false
  [2024-06-04 20:47:50 +0000 (10290)] INFO : >>> MANNY <Consumer.02> Dupe Check: No Duplicate Found

  # Create Unit of Work
  [2024-06-04 20:47:50 +0000 (10290)] INFO : >>> MANNY <Unit of Work.01> Created w ID:997690ce-f1a5-4f2e-8844-3b8ae4e1ed9b, Consumer , Timestamp: 2024-06-04 20:47:45 +0000
  [2024-06-04 20:47:50 +0000 (10290)] INFO : >>> MANNY <Throttled Consumer.01>, CREATED UoW: 997690ce-f1a5-4f2e-8844-3b8ae4e1ed9b, TS: 2024-06-04 20:47:45 +0000

    # Process Unit of Work
    [2024-06-04 20:47:50 +0000 (10818)] INFO : >>> MANNY <Worker.01> Processing Item: 997690ce-f1a5-4f2e-8844-3b8ae4e1ed9b, 2024-06-04 20:47:45 +0000

      # Worker Dupe Check
      [2024-06-04 20:47:50 +0000 (10818)] INFO : >>> MANNY <Duplicate Detector.01> BEGIN
        Msg_Data: {:id=>"54638534-e774-4838-899a-737fafb4ef34", :queue=>"NonManagedSendCurrencyJob", :visibility_timeout=>30, :received_timestamp=>2024-06-04 20:47:45.330152286 +0000}
      # IMPORTANT: Note the TTL is set to SQS' Visibility Timeout Config - 5 second delay
      [2024-06-04 20:47:50 +0000 (10818)] INFO : >>> MANNY <Duplicate Detector.02> New TTL for Msg ID 54638534-e774-4838-899a-737fafb4ef34 is TTL: 15
      [2024-06-04 20:47:50 +0000 (10818)] INFO : >>> MANNY <Chore Consumer.00>, Duplicate Found? false
    [2024-06-04 20:47:50 +0000 (10818)] INFO : >>> MANNY <Worker.03> Dupe Check: No Duplicate Found

# Errors out on TJS side (reward does not exist)
[2024-06-04 20:47:50 +0000 (10818)] ERROR : Failed to run job with error: Reward not found: 54638534-e774-4838-899a-737fafb4ef34

Verification

[ ] BQ

[ ] Verify increased retries coming in for day 4
[ ] Verify decreased retries coming in for days 1,2,3
[ ] Should also increase in rewrad success rate as we don't prematurely remove messages from the queue

[ ] HC

[ ] Spotcheck some reward ids from BQ and verify the retry attempts

References

REWARDS-417 Documention
REWARDS-417 BQ Data
REWARDS-417 JIRA

@obrie thanks for reviewing, hopefully this should be it 🤞rspecs pass locally, now looking into how to test e2e

@obrie @alanbrent I've tested this E2E with TIAB and put the examples in the description. I verified by outputting the new TTL we use when we add a message to the dedupe cache. Let me know if there's anything else!

Made requested changes and reran local tests. All local tests passed and updated picture in description


Added Legrand Wireless Remote Switch quirk

Added support for Legrand Wireless  Remote Switch 067773 (NLT type device).
It supports basic features, and power reporting at on/off as well as at check-ins.

Codecov Report
Base: 80.03% // Head: 79.93% // Decreases project coverage by -0.09% :warning:

Coverage data is based on head (8e298cf) compared to base (687adff).
Patch coverage: 67.24% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #1832      +/-   ##
==========================================
- Coverage   80.03%   79.93%   -0.10%
==========================================
  Files         240      241       +1
  Lines        7443     7501      +58
==========================================
+ Hits         5957     5996      +39
- Misses       1486     1505      +19

Impacted Files
Coverage Δ

zhaquirks/legrand/remote_switch.py
67.24% <67.24%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

39 of 58 (67.24%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 79.936%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

zhaquirks/legrand/remote_switch.py
39
58
67.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
5996

Relevant Lines:
7501

💛  - Coveralls

Why are we forcing reads of battery voltage from several clusters? The device should report this as it needs to. This can impact battery life.


[Feature][TASK-PLUGIN] AWS Database Migration Service (DMS)

Purpose of the pull request
close: #11672
Brief change log

[x] Create and start DMS task by interface
[x] Create and start DMS task by json data
[x] Restart DMS task by interface
[x] Restart DMS task by json data

Create and start DMS task by interface

Create and start DMS task by json data

Restart DMS task by interface

Restart DMS task by json data

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)

Codecov Report

Merging #11868 (8351dda) into dev (3664d85) will increase coverage by 0.10%.
The diff coverage is 60.25%.

@@             Coverage Diff              @@
##                dev   #11868      +/-   ##
============================================
+ Coverage     38.55%   38.65%   +0.10%
- Complexity     4037     4066      +29
============================================
  Files           993      998       +5
  Lines         36698    36904     +206
  Branches       4273     4295      +22
============================================
+ Hits          14148    14267     +119
- Misses        20923    21003      +80
- Partials       1627     1634       +7

Impacted Files
Coverage Δ

...olphinscheduler/plugin/task/dms/DmsParameters.java
0.00% <0.00%> (ø)

...lphinscheduler/plugin/task/dms/DmsTaskChannel.java
0.00% <0.00%> (ø)

...heduler/plugin/task/dms/DmsTaskChannelFactory.java
0.00% <0.00%> (ø)

...ache/dolphinscheduler/plugin/task/dms/DmsTask.java
59.25% <59.25%> (ø)

...ache/dolphinscheduler/plugin/task/dms/DmsHook.java
67.39% <67.39%> (ø)

...eduler/server/worker/task/WorkerHeartBeatTask.java
68.08% <0.00%> (-8.52%)
:arrow_down:

...org/apache/dolphinscheduler/remote/utils/Host.java
42.55% <0.00%> (-2.13%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
51.38% <0.00%> (-1.39%)
:arrow_down:

...che/dolphinscheduler/common/utils/HadoopUtils.java
15.94% <0.00%> (-0.73%)
:arrow_down:

... and 15 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hi @jieguangzhou is this pr ready for review?

@caishunfeng @EricGao888 PTAL, thanks.

PTAL

Done, PTAL, thanks

@Amy0104 PTAL, thanks

Thanks all


Incredible slow sync due to interrupted storing

Matthew complains on incredible slow sync, this appends when the previous saving was interrupted.
Notify the user should be useful here

We suggest keeping the existing storage until the end of the saving process.
The application should write the new data by creating new files, the existing storage will be replaced at the end of the saving.
If the saving is interrupted, the existing storage will be used to restore the local storage.
The saving process may still be interrupted when the existing storage is replaced, but this operation is faster. The probability to detect a corrupted storage should be reduced.
We still need to notify the user when the local storage is reset to fix file corruption.

Brief notes from talking to @manuroe about this on Monday:
I think we can fake atomic saves with rollback without having to resync the world, and without switching to using realm.io or similar:

persist per-room events/state to: ./messages/!curbaf:matrix.org-${previous_sync_token}.
rename the file for the room after persisting them to replace the original
if things crash during peristence, then on launch:

look for partially any persisted files with the -${previous_sync_token} suffix
load up all the existing non-partial files
start /sync-ing again from the $previous_sync_token in the partial filename.

If there were local echos being persisted in the partial file, then they will obviously get lost when resyncing from /sync results, but c'est la vie.

FTR, MXFileStore files has been reorganised like this: https://github.com/matrix-org/matrix-ios-sdk/blob/13cd0c3f6f16cfe6dc8c87055de98ed74d7d0616/MatrixSDK/Data/Store/MXFileStore/MXFileStore.h#L27


Health check between service + temporal servers

Is your feature request related to a problem? Please describe.
With cadence we have seen issues where clients lose their connection and are unable to reconnect to the cadence servers
Describe the solution you'd like
A health checking mechanism that allows me to check whether the workers/factory have a healthy connection. This would allow us to check something like factory.isHealthy() in a k8s health check endpoint and restart the worker services if necessary
Describe alternatives you've considered
None.
Additional context
We built this into the cadence java client by forking it and using the TChannel meta health check that cadence looks to already implement.

@bbottema does this pull request address your issue?


Effect interpreter equivalence

Summary
The interpreters for mocked wallet, real wallet, playground etc seem to be not equivalent. My contract works in both playground and in the test suite, but fails against testnet, because apparently txInfoSignatories are not automatically added. You have to add Constraints.mustBeSignedBy pubk to your txConstraint, but only when running real PAB against testnet.
Steps to reproduce
Steps to reproduce the behavior:

test this on playground via lock-redeem
run test suite
run this against testnet via PAB
Observe it failing due to missing signature

Expected behavior
Either I get a failure in playground etc as well or the real wallet effect handler auto-adds current pubkey to txInfoSignatories. Probably the former.
System info (please complete the following information):

OS: Fedora 34
v2021-11-05 pre-release

@migamake @iagon-tech

Also related: https://github.com/input-output-hk/plutus-apps/issues/128

I think it was fixed in #642. If not, please re-open.


Dash character closes the autocomplete dropdown / fails to match

I'm using NCM with the fuzzy matcher turned on, and I've noticed that when attempting to auto-complete CSS tags containing dashes (e.g. .shows-you-might-like), it matches fine after typing .shows but when followed with a -, it stops.
I am not sure if this is an NCM issue or a larger issue with Vim, but I figured I would start the discussion here.
Is there a way to include the - character as part of the autocomplete search? (I should note it is already included as part of iskeyword in my vimrc).
See the gif below for an example of this in action:

Which version are you using?
I cannot reproduce the issue.
Unfortunately, current implementation of the tag source only supports prefix matching.

If you're able to run Docker, I put together an image with my setup that should help reproduce it.
Run (or build the image yourself from the Dockerfile):
docker run --rm -ti mikehearn/ncm-dash-issue nvim wnyc-web-client/app/styles/legacy/_home-compat.scss

This will launch you into a containerized nvim instance, editing a .scss file.
Try adding .bucket-title, and you'll see it stop autocompleting after typing .bucket- (gif below, you should be able to reproduce this exactly). With the fuzzy finder, typing .buckettitle matches, but with a dash - .bucket-title - it fails.

THANK YOU!
Also just a heads up, it looks like 45a4812 just assigned _patterns['css'] to itself instead of to _patterns['scss']?


docs: fix typos

Description
Please explain the changes you've made.
Type of change

This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional).

Auto-generated summary

🤖 Generated by Copilot at 734a1bf
Summary
:pencil2::wrench::memo:

This pull request fixes several typos and formatting errors in various README.md files and one configSettings.md file in the radius-project/radius repository. The changes improve the spelling, readability, and accuracy of the documentation and configuration settings for the Radius platform and its components.

Typos fixed in docs
specifications spelled right
Winter of errors

Walkthrough

Fix typos in the word "specifications" in the Configuration sections of the README.md files for the AutoRest tool in the pkg/cli/clients_new, pkg/corerp/api, pkg/daprrp/api, pkg/datastoresrp/api, pkg/messagingrp/api, and pkg/ucp/api folders (link, link, link, link, link, link)
Fix typo in the word "certificate" in the server section of the configSettings.md file for the server configuration settings in the docs/contributing/contributing-code/contributing-code-control-plane folder (link)
Fix typo in the word "practices" in the Overview section of the README.md file for the Radius platform in the root folder (link)
Add missing backtick to close a code block in the Steps section of the README.md file for the Grafana dashboard setup in the test/infra/azure folder (link)

@shalabhms Please review .
Regards

@Mayureshd-18 thanks for the docs fixes! Could you visit the DCO page to sign off on the commits? Thanks!

@AaronCrawfis Done!


Revert "Bratseth/constants cleanup take 2"

Reverts vespa-engine/vespa#22582
Not quite there ...

👍


The output of the command "gramma check" with no argument contains a stack trace

Steps to reproduce

Run the application with the following command:

gramma check

The output contains a stack trace, starting with the following:

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be one of type string, Buffer, or URL. Received type undefined
...

Suggestion
I do not consider this as a bug or an invalid behavior (it may be indeed the expected behavior). But in general, I think that there is no point to print such an information to a non-developer.
Instead, there might be added a flag -d/--debug which would enable all commands to print stack traces in case of ~a failure~ particular failures.

Fixed with: https://github.com/caderek/gramma/commit/409388f893a9fa9d90d66da199b6f96ca3d7861a#diff-d9d9214113dea1c364abd4ba3c70be11R45
Thank you!


PMID:26422458

normal kinase activity (GO:0033857)
abolished GO:0052745 inositol phosphate phosphatase activity
increased GO:0052745 inositol phosphate phosphatase activity
decreased GO:0052745 inositol phosphate phosphatase activity
decreased iron-sulfur cluster binding
increased iron-sulfur cluster binding

normal diphosphoinositol-pentakisphosphate kinase activity FYPO:0005481
abnormal inositol phosphate phosphatase activity FYPO:0005482
increased inositol phosphate phosphatase activity FYPO:0005483
decreased inositol phosphate phosphatase activity FYPO:0005484
abolished inositol phosphate phosphatase activity FYPO:0005485
increased iron-sulfur cluster binding FYPO:0005486
decreased iron-sulfur cluster binding FYPO:0005487

edit file: 5f9e1f7f2c79f550643ff39dd9b6ca856a8f7c1b
(last two in 06ebb2016a382bd69e3464776cf6cf98c0de0f53)
release: da67beb7808271cd3cf2fc95521977f3fb0f9b42