Vm sandbox

A cleaner and less disrupting version of what we've seen on previous 'style proposal' branches.

There's no 'general purpose' wrapping of the Lua C API, just enough methods to make sandbox_loader.lua source readable.

Doesn't depend on app.lua calling app:relink(). Instead, adds an explicit :inject_links() method.

Cleaner method to share the packet freelist.

The engine.frees, .freebytes and .freebits are moved to an ipc.shmem.counters file, allowing any sandbox to update it.  It could also be an FFI struct shared in a similar manner to packet_fl. In a multithreaded future it could be a per-thread struct, updating the central statistics after each breath() cycle.

This is impressively simple on a few different levels.
I really like how simple basic apps like sink have become.
I also really like the way the Lua API is designed for VMs to be managed by C but then the C FFI is so powerful that you can even more easily control them from Lua :-).
Looking forward to taking it for a spin. Looks like the file core/stats.lua is missing at the moment.

Looks like the file core/stats.lua is missing at the moment.

D'oh!
i'll push it at lunchtime...

Thanks Javier! This runs now:
$ sudo ./snabb snsh -t apps.basic.test
link report:
          34,917,405 sent on source.output -> sink.input (loss rate: 0%)

I would like to spend some time with this and aim to merge it for next month's release.
I suppose there is nothing stopping you from attacking N:M threading now :-)

This is very interesting code to read. I am quite fascinated that engine.configure() does not need to know that some apps are now in their own sandboxes, because behind the scenes config.app() is creating backwards-compatible app "classes" that automatically create a sandboxed object when instantiated with new() and forward method calls to pull(), push(), etc. I had expected the meat of this change to be in engine.configure() but that code did not actually have to be touched at all. Clever.
I will come back and read through sandbox_loader.lua carefully. That code is quite intimidating at first glance :-)
I am also reflecting on the increasingly many use cases that we have for shared memory these days: sharing memory between Lua states, sharing memory between threads (potentially), sharing memory with other Snabb processes (SnabbTop), sharing memory with external application (Alex's NetSNMP plugin). I wonder if there is a simple way that we could consolidate the code for these.

@javierguerragiraldez This branch seems to be in quite good shape now. How about if you move your new development onto a new branch based on this one and shoot for a 1

@javierguerragiraldez I would like to merge this code onto a branch of my own and work on integrating it in the smoothest way with core.shm (#513) and SnabbTop (#472). I would close this PR and open a new PR from my branch that includes these commits. I am hoping there will be opportunities for cross-module simplifications. Would that be okay with you? (You should be able to keep doing the parallel hackery based on this same version and we can do a merge later when all parts are ready.)

Great!  if you want to do it yourself, the first things that could be simplified are the core.freelist, which wouldn't need the receive() function, and core.packet would just call freelist.new('core/packet/freelist', 'struct packet *', max_packets) instead of checking if it has the global lightuserdata pointer already injected.
Similarly with the core.link objects, the app:inject_links() method could simply pass the registered names of the links and then do for i,name in ipairs(inputlinknames) do input[i]=shm.map(name,'struct link*') end from the 'inside'.

Closing this PR because we have had a productive review and I think if/when/how we merge sandboxing will depend on the parallelism model we choose. (Can reopen if my understanding here is dodgy.)


uses()->in(...) should autocomplete directories

Hey! Thanks for your work on this, it's awesome!
This is just a QoL improvement, not a bug.

Here a list of directory could be shown.

Hi, thanks for suggesting an improvement!
I think it's a good idea and something we definitely should do 👍


Impossible to download video - Prohibition road sign on the download button

After downloading the video, when the percent arrives at 100%, the download button has a prohibition road sign when we put the mouse on it... We were never asked for a download location....

Agree, high resolution videos do not download.

Hey! can you please share a link to the stream?

Hey! can you please share a link to the stream?

It's not high resolution... I can't share the link because the page to access it is password protected...

@puemos
Since the link is encrypted, I cannot share the stream source.
There is a situation like this when we try to download large files.
No problem, I believe it will be fixed. For now, I get the stream source from your vehicle and download with "jdownloader" or "ffmpeg".

I can confirm this has been happenign to me since the last update, too.  I can see lots of quality options for videos, and they smoothly go from 0%-100%, but then at 100% the button to save the file gets the "disabled" style and nothing can be done.
Here's one example link that does it for me (lemme know if it expires and you need more - seems to happen with most twitch streams now):
https://www.twitch.tv/videos/622891737

can't download the streams need fix

First, thanks for taking the time to comment @dosiecki @ahmtaras @zigune @gitdev-bash
Second, It seems like the issue is related to the new chrome versions, I will try to use FileSystem which will take some time to develop.

This is happening to me on firefox.

Work in progress #132


Automate publishing OVA images to VMware Customer Connect

This is based on the conversation from https://kubernetes.slack.com/archives/C02GY94A8KT/p1637150411055100 where we realized that users can't try out RC versions (like v0.10.0-rc.1) on vSpere as OVA images haven't been uploaded to VMware Customer Connect, for example like this https://customerconnect.vmware.com/downloads/get-download?downloadGroup=TCE-090
It would be best to automate this part of the pipeline - as part of releases - especially stable (GA) releases and also think about rc or non-GA releases (alpha, beta etc) and think about how we want to automate that and also publish OVA images for those versions to VMware Customer Connect
Related - #1305

cc @navidshaikh

Putting this in icebox only because we don't know what release this is targeted for or if it'll be out of band of an "official" release. Feel free to update the milestone if you want to bind yourself to a specific TCE release.
Thanks!


Integrate structured data as well for QnA in addition to unstructured data from pdf files

can u suggest what should be steps to integrate structured data along with unstructured data from pdf files so that we can get answers for questions that combined data from structured and unstructured data sources both ?  looking forward to knowing which functions i need to modify .
I think I will have to call function
update_embedding_create_vector_index( graph, chunkId_chunkDoc_list, file_name)
with each row from the structured data set ? and create one embedding column that creates embedding for all columns combined for that instance of the entity /node?
For instance if I have a Person table and personname, city, state, Age, Occupation and 50 other such columns will I need to create 1 embedding value for each person and store it as a separate property in neo4j ?
Just wondering what all will I need to modify for the QnA code to answer questions combing structured and unstructured data both

You can integrate your structured data separately e.g. with the data importer tool (which currently supports CSV) or by manually importing structured data into the graph.
https://neo4j.com/docs/data-importer/current/

Hi @jexp , i already imported structured data using cypher load csv as i believe data importer is only available for Aura workspace or as a web tool and not part of desktop.
However the problem is since this tool is retrieving data only using embedding similarity search despite creating relationships i am unable to retrieve the structured data using the chat interface of this tool. So my original question 'Just wondering what all will I need to modify for the QnA code to answer questions combing structured and unstructured data both' is still open

Data importer/workspace can also connect to local neo4j instances.
Good point on integrating the structured data, we'll think about it.

Added an enhancement here: https://github.com/neo4j-labs/llm-graph-builder/issues/596


添加头像

最大大小为3x3cm

#2

When i comment avatar, the name is not centered properly, which breaks the style without an avatar.


Providing a custom findInput method

Are you submitting a bug report or a feature request?
Feature Request
What is the current behavior?
I am using custom components in my form (react-select components in this case). They don'r render any input components, so they aren't found with the findInput method that is currently implemented.
What is the expected behavior?
I suggest adding an optional parameter to the createDecorator function, which is used to find the input if provided. Just like the getInputs parameter.
What's your environment?
final-form: "^4.8.3",
react-final-form: "^3.3.1",
Chrome Version 67.0.3396.99  on MacOS 10.13.6
node v10.7.0
Other information
I have forked this and implemented it for my own use. I can create a PR out of it, if needed. But it's only a very simple change.
https://github.com/nik-lampe/final-form-focus/tree/feature/find-input

I'd love to see a PR. 👍

Update the README, too, please.

Done.
This is my first PR ever, so I'd love feedback if I made any mistakes. 🙂

Published fix in v1.1.0.

@nik-lampe, would you mind giving an example on how to implement passing in GetInputs and FindInput?

@nik-lampe  Hello, I don't know if I use the select component, how to make the interface slide to the corresponding position when the validation fails. Can you tell me how to use findInput? Can it fulfill my needs?
PS: It is best to have a demo demo, thank you very much.

Hey,
sure here is a fork of the original codesandbox example:
https://codesandbox.io/s/react-final-form-focus-on-first-error-egxcq
Hope this helps


TypeError: can't pickle weakref objects

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
tf 2.11.0
Custom Code
Yes
OS Platform and Distribution
Windows 11
Mobile device
No response
Python version
3.7
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
TypeError: can't pickle weakref objects

Standalone code to reproduce the issue
import tensorflow as tf
import pickle
output_file=open('save.dat','wb')
pickle.dump(tf.keras.optimizers.Adam(),output_file)

Relevant log output
No response

@NoteDancing
Could you please refer to the similar issue_1 & issue_2 and find the workaround here and let us know if it helps ?
Thank you!

@NoteDancing Could you please refer to the similar issue_1 & issue_2 and find the workaround here and let us know if it helps ?
Thank you!

Whether the optimizer cannot be pickled？

@NoteDancing ,
Please find the workaround to serialize the Optimizer using Pickle here.
Please let us know if proposed solution won't work for you.
Thankyou!

@NoteDancing , Please find the workaround to serialize the Optimizer using Pickle here.
Please let us know if proposed solution won't work for you.
Thankyou!

Is there a way to serialize optimizer instead of opt_config like tensorflow version 2.0.
Thankyou!

@NoteDancing , We have tf.keras.optimizers.serialize() API which will convert the optimizer to JSON form.Please find attached gist here.Hope it will solve your purpose.Thanks!

@NoteDancing , We have tf.keras.optimizers.serialize() API which will convert the optimizer to JSON form.Please find attached gist here.Hope it will solve your purpose.Thanks!

How can I restore optimizer from opt_serialized?Thankyou!

For restoring the opt_serialized TF have tf.keras.optimizers.deserialize API.We can do it like below.
opt_restored = tf.keras.optimizers.deserialize(opt_serialized)

@SuryanarayanaY Thank you for your answer.


redpanda: 23.1.10 -> 23.1.11

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/redpanda-data/redpanda/releases.
meta.description for redpanda is: Redpanda client
meta.homepage for redpanda is: https://redpanda.com/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 23.1.11 with grep in /nix/store/pxs4wf9wqlfi4zl5m1cxqjda93cgxsqi-redpanda-rpk-23.1.11
found 23.1.11 in filename of file in /nix/store/pxs4wf9wqlfi4zl5m1cxqjda93cgxsqi-redpanda-rpk-23.1.11

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
redpanda
redpanda-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pxs4wf9wqlfi4zl5m1cxqjda93cgxsqi-redpanda-rpk-23.1.11 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pxs4wf9wqlfi4zl5m1cxqjda93cgxsqi-redpanda-rpk-23.1.11
ls -la /nix/store/pxs4wf9wqlfi4zl5m1cxqjda93cgxsqi-redpanda-rpk-23.1.11/bin

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

1 package failed to build:

redpanda-server

1 package built:

redpanda

Maintainer pings
cc @avakhrenev @happysalada for testing.

redpanda is (still) broken since #220193

Yeah thats why i dont try to merge these, i have it on my list to look at this at some point.

Superseded by #235240.


Fix validation implementation

Hi, I got below error during initialize ApiClient
Uncaught (in promise) Error: options.0 must be set
    at validate (validation.js?9521:42:1)
    at new ApiClient (endpoints.js?7cbd:91:1)
    ...

A code for validating object type in array schema seems not working correctly.
schema is array and it looks like ['object', {...}], so we need to use subSchema to check each attributes and to call validation method recursively.
I also think, need some test code for that complex method if possible.

You're right, that's my fault for not writing tests for that validation function. I'll push out this change and test it more thoroughly.

Published as<EMAIL_ADDRESS>Thank you for the upstream fix!


IGNITE-3897 Test transactional behaviour of caches during rolling restart

This submission includes 2 new tests for the IgniteCacheFailoverTestSuite that validate the results of an aggregation function running against a cluster undergoing rolling restart.
It also includes a new Assertion, EventualAssertion - this assertion has a timeout and retests the assertion with exponential back-off until successful, or failure, allowing tests to wait in a deterministic fashion for a condition before continuing with the test. This is particularly useful in Rolling-Restart type tests, to ensure after a node is killed that the system has time to rebalance before continuing with the restarts.

Hi John!
Thank you for your contribution! I have just had a chance to reivew it.
First question. Why did you file this issue? Was there a discussion on dev list? Can you porvide a link if any?
I fixed some naming/formatting issues in GridCacheRebalancingAggregationTest and pushed everything to ignite-3897-pr1059. Please review and consider going furhter.
As far as GridCacheRebalancingAggregationTest - it obviously has a bug. If on some random iteration update thread throws exception, test does not fail. This should fail the test for sure.
As a general note I would say that when you dealing with restart/failover tests one thread doing updates is not enough. You should send massive and variable load to your tests topology from multiple threads prefferrably having contended keys between them.
I would aslo encourage you to take a look at our current failover threads. It seems we already have tests of the kind:
IgniteCacheCrossCacheTxFailoverTest
GridCacheTxNodeFailureSelfTest
etc
Please let me know if you have any questions.

Hi Yakov,
Thank you for the feedback - I will look at ignite-3897-pr1059 and update this PR with the changes, and also look at the failure of GridCacheRebalancingAggregationTest to fail on Exception - thank you for spotting that.
Just a little background - these restart tests began with https://issues.apache.org/jira/browse/IGNITE-3789 - these tests kill -9 <pid> a node in the grid, rather than sending a Callable to shut down nodes gracefully. We find that this type of test can uncover unusual/unintended behaviours.
IgniteCacheCrossCacheTxFailoverTest and GridCacheTxNodeFailureSelfTest don't override GridAbstractTest.isMultiJvm() to start external processes for testing, and GridAbstractTest doesn't currently have the ability to kill nodes - this ability was added in GridRollingRestartAbstractTest#stopGrid(int idx)
If these new tests we're adding are duplicating the existing failover tests, perhaps I could modify the existing tests so they start nodes as separate processes and randomly stop nodes with kill -9 instead of a graceful stop callable? Or perhaps I can keep these as a distinct type of failover test, and I will try to reuse the existing tests - simply run them in the context of a grid undergoing "RollingRestart" (which is achieved by subclassing GridRollingRestartAbstractTest).
Let me know what you think would be the best way to get test coverage in this area (whether by reusing GridRollingRestartAbstractTest, or modifying the existing failover tests to allow them to be run while a rolling restart is in progress).
Thanks!
John

Hi @yzhdanov , I've merged your review feedback into the branch. I added code to ensure the update thread logs any exceptions and also the test checks that the thread exited without encountering an exception.
If the updateThread exited, either while (restartThread.isAlive()); or an exception occurred, so the test that assertEquals(getMaxRestarts(), restartThread.getRestartTotal()); was trying to ensure that updateThread exited due to restartThread/test finishing, rather than an exception - but I've made it test explicitly that the updateThread hasn't encountered an exception - it's much cleaner/clearer this way, thanks for questioning it.
Cheers
John


Improve handling of fallback theme colors in terminal

See https://github.com/Microsoft/vscode/issues/56864#issuecomment-414939406

I would like to pick this up. Before the PR, clarification on the change:
https://github.com/Microsoft/vscode/blob/07618102efdd63f09949ce54c161e7fd2a954ee8/src/vs/workbench/parts/terminal/common/terminalColorRegistry.ts#L16-L29
I believe the changes are to set the default nulls to their respective editor colors as defaults.
Ex:registerColor('terminal.background', { 	dark: editorBackground, 	light: editorBackground, 	hc: editorBackground }, ...
I think that hardcoded defaults such as TERMINAL_FOREGROUND_COLOR need not be disturbed.

@ParkourKarthik great! Background and border should be changed to the better as they are the ones that fallback:
https://github.com/Microsoft/vscode/blob/f7b8c9b7df54f23b02fb36ba0cb12a5a96c8c4e9/src/vs/workbench/parts/terminal/electron-browser/terminalPanel.ts#L313-L316


null vs 0 values in aggregate outputs

placeholder - will fill in detail

@simonhac rules here are 0 if its 0 from the source, null if its a gap - correct?


feat: Cambiando Escena Principal StackPane Por BorderPane

Se cambió la escena Principal Por Border Pane por considerar más facil de ubicar los Elementos en pantalla.

Codecov Report

Merging #45 into V1.0 will decrease coverage by 1.99%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               V1.0      #45      +/-   ##
============================================
- Coverage     86.85%   84.86%   -2.00%
  Complexity       76       76
============================================
  Files            22       22
  Lines           213      218       +5
  Branches          9        9
============================================
  Hits            185      185
- Misses           28       33       +5

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/edu/fiuba/algo3/App.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

Continue to review full report at Codecov.

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


Each update grows the utilization of RAM

Hello,
After each update, a little more RAM is used and it grows until memory is full (16Go).
I have to reboot for better performance. Is the same for everyone ?
What can I do to avoid this ?
Thanks !

Don't think this is a "Question" but an actual issue, just worded poorly?
Also having this issue. Though mine seem to be with every backup.
Attached logs and also RAM usage from my Docker container.
If I leave Valheim running in Docker, it crashes the whole LXC... Which is no beuno and does not help a 24/7 server.
As you cans see from this screenshot, at around 10:36 (server time)

The logs are offset by 1hr (due to daylight savings), so at 11:36 it looks like the World backup also starts.
The issue is that the RAM increases exponentially with every backup?
_valheim_logs (1).txt

Confirming issue by running Portainer Stat page during backup and you see RAM increase during backup and then remain at the higher level. This would mean each backup would exponentially add to RAM usage:

Hello, thanks for your reply.
I use proxmox too, I saw exactly the same thing.
But since the last update (3 days ago) and UPDATE_CRON="*/60 * * * *" the increase in RAM usage is very limited. I keep an eye on it anyway.

Yeah I realised that my backups were running every 30mins but after reading the docs they should have defaulted to every hour???
Regardless, I've now swapped over to once daily with the CRON varialable.
Still, if running backups is for some reason adding RAM usage after every run, then a fix will still be required or we'll still have to be restarting the container every so often...

I mean, maybe the quotation marks were too much and negated the updates. So the last update of valheim-server-docker do not solve the issue.
The issue is still here :

I seem to be running in the same issue when the docker image does a world save. As you can see in the graph it causes a slight uptick in CPU and RAM usage during the backup. The CPU utilization goes back to normal, but the memory is never freed unless I restart the docker image.

same for us.
Yesterday the server crashed for the first time due to 100% RAM usage.
its starting with around 3,8GB and go up for about ~1GB per step.

Do you know where the world save is landing?  If it's in some tmpfs this might make sense.

Thanks for the role since I've talked on this as well but I am also facing the same issue. Mitigate it in the mean time of essentially just set up a cronjob to restart the container every week. As you can imagine that's not ideal...
When I have some time I'll exec in and poke about..

I've tried to replicate the issue but couldn't. Can you see if there's a process that's getting stuck with each backup? Do you have any pre/post backup hooks that might hang?
For memory to leak there has to either be a continuously running process that's allocating more memory than it is freeing, or there have to be new processes occupying memory that are adding up with each backup run.
Looking at the backup script, the list of external commands it is calling are
zip and cp for the backup and find, sort, cut, tail, xargs and rm for the cleanup of old backups.
Steps that would help with debugging the issue, next time it happens:

exec into the container and get a process list. See if there's an excessive amount of any of the before mentioned external commands running.
identify which of the processes running inside the container are occupying which amount of core memory. This can be done inside the container or on the host system.

I also went over the valheim-backup script itself but couldn't see any obvious spot where it would leak memory. As far as I can tell there is no point where it appends any data or otherwise uses a variable that grows in size. But I would appreciate a second pair of eyes. The script is only like 160 loc and fairly straightforward.

we disabled the valheim backup function and only use the backup function coming with this docker image. but its still using a lot of memory...

Hello :)
After monitoring for 2 days, I can tell that's the "buff/cache" wich grows according to the "free" command.
The used mem is stable : 3Gi
OS : Ubuntu Server 22.04.1

Then you should monitor for growth in /proc/meminfo and see which entry grows.  And also review the meminfo section of proc.txt for more detail.
But the conventional wisdom is that if it's in buffers and cache, it's not really "used" because the kernel can give it to another process.  See also: free(1) which explains the fields, and then from proc.txt above:
     Buffers: Relatively temporary storage for raw disk blocks
              shouldn't get tremendously large (20MB or so)
      Cached: in-memory cache for files read from the disk (the
              pagecache).  Doesn't include SwapCached

So if there's really a leak and it's only manifesting as buff/cache from free growing, I don't think you've found the indicator.

@fuse1985 if you look in the running Docker container, and your backups are going to /backups, what does df -h /backups show?  (or wherever your backups are going)

I was thinking it could be a tmpfs, but doesn't seem to be...  Seems like you must also be setting BACKUPS_DIRECTORY if it's not /config/backups though?

I added the "BACKUPS_MAX_COUNT=3" environment variable and now the RAM usage is stable around 3Gio.
So I conclude that each backup was keep in cache in some way.

If that's the case you should be able to recover the memory using /proc/sys/vm/drop_caches:
       /proc/sys/vm/drop_caches (since Linux 2.6.16)
              Writing to this file causes the kernel to drop clean
              caches, dentries, and inodes from memory, causing that
              memory to become free.  This can be useful for memory
              management testing and performing reproducible filesystem
              benchmarks.  Because writing to this file causes the
              benefits of caching to be lost, it can degrade overall
              system performance.

              To free pagecache, use:

                  echo 1 > /proc/sys/vm/drop_caches

              To free dentries and inodes, use:

                  echo 2 > /proc/sys/vm/drop_caches

              To free pagecache, dentries, and inodes, use:

                  echo 3 > /proc/sys/vm/drop_caches

              Because writing to this file is a nondestructive operation
              and dirty objects are not freeable, the user should run
              [sync(1)](https://man7.org/linux/man-pages/man1/sync.1.html) first.

[1] https://man7.org/linux/man-pages/man5/proc.5.html

This is the result of running the above that opello suggests (taken from portainer GUI):

ie:
# sync
# echo 3 > /proc/sys/vm/drop_caches

Note that this was run on the host system, not the container.  Note that the container I'm running is running with the defaults (internal backups every 15 minutes, create worlds-YYYYmmdd-HHMMSS.zip backup every 60 minutes), and running for about 2 days-ish.  Note that the game db is roughly about 50MB give or take.
Note also that the performance of the system seemed fine.  The system never reported that all that much RAM was being consumed on the host (free never showed more than 7-8 gigs of usage, not bad considering its hosting 2 Valheim services and 3 Minecraft worlds), and the physical storage isn't too much either.

It's completely normal and advantageous for Linux to use memory for caching when there is memory available.  If something needed this memory it would be made available to it.  Dropping the caches when you aren't doing some kind of testing where you don't want the effects of caching to affect your results is just going to hurt performance for no reason.

If dropping the caches recovers the memory thought to be going to a leak it's safe to do nothing going forward.

While I agree that it's advantageous for a Linux system to fully utilize for buffers/cache any available RAM, I find it odd that the amount or RAM consumed continues to increase in lockstep with the valheim-updater service in the container that's triggered every (by default) 15 minutes.  Surely, there can't be any appreciable amount of performance gained by the Linux system for caching these .zip files every 15 minutes+?  I'll let the system run for about a week+ and see what the buff/cache looks like after that time period.  Though based on relevant sar -r data I've been tracking for a few days, the buff/cache size isn't really increasing all that much  I'll also see how long it takes to run out of RAM (Free+Swap) and the system crashes, as that appears to be the case for at least some people in this thread.
Besides, if this was an issue with the host consuming more buff/cache, then this wouldn't show up through the container stats view in portainer.  The other containers that I'm running on the host (a couple of Minecraft docker containers) are better-behaved, and don't exhibit the steady, continuous rise in RAM usage as reported by the container in 15 minute increments exactly corresponding with the valheim-updater process, even when actively used.  Either way, I'll actively not maintain the server (ie no stop/start of the valheim container) for the next 2 weeks and hopefully remember to report back here what I've found.

@jonvel Please also collect some additional data:
docker stats --no-stream --no-trunc <container>
I imagine this is an artifact of an older portainer, prior to v1.20.0 which introduced separating out the cache from the memory usage:

https://github.com/portainer/portainer/issues/1961
https://github.com/portainer/portainer/issues/2380
https://github.com/portainer/portainer/issues/2074#issuecomment-429574769

Since docker stats ignores caches having that along with the other data collected should be helpful in confirming.

Surely, there can't be any appreciable amount of performance gained by the Linux system for caching these .zip files every 15 minutes+?

On a system with low file I/O it seems reasonable that any write that can be held would be on the off chance it was read again, especially when it can easily be evicted.

Besides, if this was an issue with the host consuming more buff/cache, then this wouldn't show up through the container stats view in portainer.

Per https://github.com/portainer/portainer/issues/2380 it depends on the version.  Based on your graph I expect yours is prior to v1.20.0 since it doesn't have the cache separate on the graph.  The drop_caches affecting the graph based on your earlier comment also supports this conclusion.
As for your Minecraft containers, they probably aren't writing out new files but updating existing ones?  I guess I'm not real familiar with how Minecraft persists changes at the server.

@opello - no, running the portainer container from about 2 weeks ago (v2.19.0, but Community Edition, because I'm cheap).  However, the interesting parts here are:
CONTAINER ID        NAME              CPU %     MEM USAGE / LIMIT     MEM %     NET I/O          BLOCK I/O         PIDS
3da1bdd5e346c1adf   valheim.service   21.78%    4.627GiB / 30.71GiB   15.07%    8.29GB / 1.7GB   16.4GB / 37.3GB   64

Note that one of these days, I'll do better tuning to restrict how much RAM the container can use, but I don't do this professionally, and this is really only on a whim to learn more about containerization.  The Minecraft services were mostly irrelevant, other than to point that I found it odd that so much "RAM" was being consumed.  But that's fine.  I'll let it sit for a while longer, and see what the stats look like in the future.
Also - I'll edit my response above, but the steps up in usage occur not when a backup is created but when the valheim-updater process runs (once every 15 minutes).

@jonvel, sorry for the misread, I was stuck thinking about backups and you'd said it was the updater.
This is starting to make sense after reviewing the valheim-updater code and the stdout log.  When it runs it does a few things, most relevant to this issue is asking steamcmd.sh to +app_update but it also passes STEAMCMD_ARGS which according to the README.md (and the behavior in my log anyway) includes validate:
INFO - Downloading/updating/validating Valheim server from Steam
Redirecting stderr to '/home/valheim/Steam/logs/stderr.txt'
Logging directory: '/home/valheim/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version<PHONE_NUMBER>
-- type 'quit' to exit --
Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
 Update state (0x5) verifying install, progress: 0.14 (2097152 /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 21.70 (329012463 /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 52.05 (789104462 /<PHONE_NUMBER>)
 Update state (0x5) verifying install, progress: 84.08<PHONE_NUMBER> /<PHONE_NUMBER>)
Success! App '896660' fully installed.
.d..t...... ./
INFO - Valheim Server is already the latest version

https://developer.valvesoftware.com/wiki/SteamCMD#Downloading_an_App

To also validate the app, add validate to the command.

So, during the update every 15 minutes, steamcmd is validating the download, which means it's reading the ~1.4GiB of the download directory from disk.  This makes sense to load into cache and not hit the slower disk if there's available memory.  I think it's "not a concern" but if you disagree you should be able to remove validate from STEAMCMD_ARGS.
I'm not sure why cache isn't separate from memory in your latest portainer version, but that drop_caches makes the number go down clearly shows that caches are included in the value.

I'm seeing similar issues where my swap is getting maxed out and slowing everything down to the point where the server connection is timing out:
                  total        used        free          shared    buff/cache   available Mem:         7.7Gi       2.9Gi       119Mi        22Mi       5.0Gi       4.8Gi Swap:         2.0Gi       2.0Gi        33Mi
In preliminary troubleshooting, this does appear to happen after the update check.


Update typescript definition

TS definition was using old style declaration, which was also not exporting the namespace.  Use this as import * as Waypoint from 'react-waypoint' and it allows access to everything in the namespace e.g. CallbackArgs

@fongandrew @nicolas-schmitt could you please review this PR when you have a moment?

LGTM.

Thanks @rosskevin!


WIP continue work on develop-tmsp from PR

oh... something just clicked, the proper fix should be a one-liner, so i'm looking into that.

@silasdavis alright, so this has been a bit messy, but at least it is at the state of "failing tests"; I have to put these test-passes and test-failures next to those currently in tmsp-unified to get some picture of how successful this merge has been.  Hope this makes some sense to you :)

can we include all the commits on 10th May from here: https://github.com/eris-ltd/eris-db/commits/tmsp-unified there are a number of fixes relating to renaming txs

absolutely, but they should be there.  I will now both check explicit commits are included and put the tests side-by-side

Merging this to try and get us all to a consistent base to work off, @benjaminbollen will open another to work through some issues, develop-tmsp should become our base to accept PRs into


Gradient Penalty Implementations

Can you tell me where I can find the Gradient Penalty Implementations code ?

https://github.com/Aixile/chainer-gan-experiments/blob/master/common/models/ops.py
https://github.com/Aixile/chainer-gan-experiments/blob/master/common/models/backwards.py
https://github.com/Aixile/chainer-gan-experiments/blob/master/dragan/updater.py
Ref differentiable_backward function

so I have to call the functions in backwards.py layer by layer ?

Yes, I did the backward procedure manually. But you can wait for Chainer 3.0 (Release next month) which will officially support gradient penalty.

oh, thanks!


Why use bootstrap.py in S3 not github?

https://github.com/cf-platform-eng/bosh-azure-template/blob/master/azuredeploy.json#L361

bootstrap.py is also on github. what is the concern ?

We deploy assets to S3 automatically from our CI pipeline. This allows us to keep versioned releases and we also consider the availability of AWS to be more reliable than Github.


Support environments

as a developer, I want to be able to switch between "production" and development so I can choose between hitting a real Brigade API or a local mock one.
AC:

brigade API hostname will be set based on whether a developer launches ng serve in production or develeopment mode
in production, the API hostname is https://cors-anywhere.herokuapp.com/http://acid-api.technosophos.me:7745
in development, the API hostname is blank ('')
the dashboard and project page work in both production and dev mode

This is a good story to enforce our mock data being the same as the real world.

Fixed by #154


Solution of 410 Error on only login state. (BUG IN 1.7.1)

After 1.7.1 patch, 410 errors were found again.
When you log in on TL, you get 410 Error on any video download
But if you reset the user setting of TL, you won't get 410 Error.
I used the chrome developer tool to observe the network on the video replay page of the Twitch Front End.
Twitch is using a request URL such as " https://api.twitch.tv/api/vods/508093581/access_token?oauth_token=4yvywu5fvbcli4q6gg2l32cj5cijgc&need_https=true&platform=web&player_type=site&player_backend=mediaplayer " to get sig.
However, TL is sending the request URL such as "https://api.twitch.tv/api/vods/{0}/access_token " from the  'RetrieveVodAuthInfo' function of "TwitchLeecher/TwitchLeecher.Services/Services/TwitchService.cs"
regardless of the login status.
And, there is no 'Authorization' property in request header of XHR(to get sig) on Twitch frontend .
SO, Here is my solution.

Use ' _twitchAuthInfo.AccessToken ' as a query parameter for the Request URL in line 212
Use 'CreateTwitchWebClient()' instead 'CreateAuthorizedTwitchWebClient()' on 'RetrieveVodAuthInfo' function

I'm sorry I sent you an issue without testing it.
I hope the problem will be solved soon.

@sfsepark is there a way to avoid 410 Error without waiting for update? :?

@Tomijs  No. There's no other way but to re-compile.

@sfsepark I just emptied the "C:\Users{user}\AppData\Roaming\Twitch Leecher" and the error is gone. Not exactly what You suggested but did the same job by resetting settings as well. Anyway, now I can download videos. :)

@Tomijs what version of twitch leecher are u using? I am still having that error after i empty the folder! Please help

@sfsepark You have to differentiate between the web client to the v5 Kraken API and the private Tiwtch API for retrieving the auth info and video playlist.
https://dev.twitch.tv/docs/authentication#sending-user-access-and-app-access-tokens
For the Public v5 API you MUST include the Authorization header, otherwise you won't get any info from the API when using scoped calls.
the interesting point is that the public and private API worked the same way so far. I also saw that the public API now uses the query parameter but in all the hassle and email spam I did not test the 1.7.1 update with a logged in account.
I need some testing for that.

@sfsepark And just in order to confirm:
The reason why you got the 410 in 1.7.1 was because you had an auth token in the user settings (you were logged in). Cleaning the settings delets the access token and therefor works. If you login again, it fails again...

@Franiac is twitch leecher working now?

@vyperszn please don't post unrealated stuff in github issues. 1.7.1 only works when you are not logged in

I did not test the 1.7.1 update with a logged in account.

Not sure if that helps, but I downloaded a sub-only vod yesterday directly after updating to 1.7.1, so at least I can confirm it worked for a time before breaking again.

Fixed & closed...
I will roll out 1.7.2 later.

410 Error on only login state is happening again


New Grpc.Core.Server creation not working in a Mac M2

What version of gRPC and what language are you using?
I am using C# with the latest grpc-dotnet (2.59.0) and the project includes the Grpc.Core and Grpc.Tools nuGet packages (2.46.6).
What operating system (Linux, Windows,...) and version?
MacOS Sonoma 14.1.2 (23B92) - RID: osx-arm64
What runtime / compiler are you using (e.g. python version or version of gcc)
.NET Core SDK 8.0.100 (runtime: 8.0.0)
What did you do?
Execute "dotnet run" in an application containing a line of code with "new Grpc.Core.Server(...)" in an M2 Mac.
What did you expect to see?
An application running without errors, and properly communicating with other applications through gRPC.
I know it is possible because it worked on a different Mac with the same setup, same code, same .NET SDK and runtime, same .NET version, etc. but with the Intel chip (older Mac) - hence my guess that maybe it's a bug related to the M2 chip.
What did you see instead?
When I execute "dotnet run", I get this error:
Note: I used (...) as a replacement for my specific irrelevant stuff
[18:33:31 FTL] Unhandled exception!
System.IO.FileNotFoundException: Error loading native library. Not found in any of the possible locations:
  (...)/bin/Debug/net8.0/libgrpc_csharp_ext.arm64.dylib,
  (...)/bin/Debug/net8.0/runtimes/osx-arm64/native/libgrpc_csharp_ext.arm64.dylib,
  (...)/bin/Debug/net8.0/../../runtimes/osx-arm64/native/libgrpc_csharp_ext.arm64.dylib
   at Grpc.Core.Internal.UnmanagedLibrary.FirstValidLibraryPath(String[] libraryPathAlternatives)
   at Grpc.Core.Internal.UnmanagedLibrary..ctor(String[] libraryPathAlternatives)
   at Grpc.Core.Internal.NativeExtension.LoadNativeMethodsUsingExplicitLoad()
   at Grpc.Core.Internal.NativeExtension.LoadNativeMethods()
   at Grpc.Core.Internal.NativeExtension..ctor()
   at Grpc.Core.Internal.NativeExtension.Get()
   at Grpc.Core.Internal.NativeMethods.Get()
   at Grpc.Core.GrpcEnvironment.GrpcNativeInit()
   at Grpc.Core.GrpcEnvironment..ctor()
   at Grpc.Core.GrpcEnvironment.AddRef()
   at Grpc.Core.Server..ctor(IEnumerable`1 options)
   at Grpc.Core.Server..ctor()
   at (...).Grpc.GrpcServer.StartServer() in (...)/Grpc/GrpcServer.cs:line 41
   at (...).Grpc.GrpcServer..ctor(...) in (...)/Grpc/GrpcServer.cs:line 24
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)
   at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.ConstructorMatcher.CreateInstance(IServiceProvider provider)
   at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.CreateInstance(IServiceProvider provider, Type instanceType, Object[] parameters)
   at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.CreateInstance[T](IServiceProvider provider, Object[] parameters)
   at (...).Program.MainAsync() in (...)/Program.cs:line 196
   at (...).Program.Main() in (...)/Program.cs:line 39
[18:33:31 DBG] Flushing logs....
[18:33:31 INF] Trapped SIGTERM: shutting down...

Line 41 mentioned in the error message is the first line of this code block:
        var server = new Grpc.Core.Server
        {
            Services = { MyService.BindService(myService) },
            Ports =
            {
                new Grpc.Core.ServerPort("<IP_ADDRESS>", myPort, Grpc.Core.ServerCredentials.Insecure)
            }
        };

Anything else we should know about your project / environment?
Not sure. I have a gut feeling that it is related to the Intel vs M2 chip difference. I spent some time checking all possible differences between the two Macs, and that's the major one. Also, the OS is 14.2.1 on the old Mac (I still had no opportunity to upgrade to the newer one from its 14.1.2).

Additional note: I was able to run the same application in a Docker container in the same Mac M2, using this image: mcr.microsoft.com/dotnet/sdk:8.0.100-1-bookworm-slim-amd64
Still not sure why it doesn't run directly in my host during development (I am using JetBrains Rider, and running the application in the console using "dotnet run").

@ropinheiro There is some confusion since you meantion both grpc-dotnet (2.59.0) and grpc.core (2.46.0) which are different implementations for gRPC for C#.
The stack trace shows that you are using grpc.core.
I think the general problem is that the Mac M2 version of the grpc_csharp_ext native library isn't available (we only ship the native library for Intel Mac). The Grpc.Core implementation is now in maintenance mode and we're only going to focus on critical and security fixes. You should consider migrating to the grpc-dotnet  implementation instead. See https://learn.microsoft.com/en-us/aspnet/core/grpc/?view=aspnetcore-8.0
I don't have access to a Mac to know why your applications runs with the docker image. Maybe it can run using Rosetta to run the intel binaries?

Thanks for the comments! We now understand that we should choose one of the approaches and not the other. The obvious choice almost always goes for the latest and still supported one, so we are going for grpc-dotnet. The main issue I see now (but I may be too conservative or have understood something wrong) is grpc-dotnet requiring ASP.NET libraries to have the server part working. Therefore, I will have to turn my tiny edge app running in a low CPU/RAM gateway into a full-blown web application. Is that correct? Won't it be too much impact?

You can run a grpc-dotnet ASP.NET Core server in an app that you start from the console. It can use the kestrel web server which is the default if you follow the tutorial: https://learn.microsoft.com/en-us/aspnet/core/tutorials/grpc/grpc-start?view=aspnetcore-8.0&tabs=visual-studio
A gRPC server application needs a server, whether it is the c-core based one used in legacy grpc, or an ASP.NET server used by grpc-dotnet. If one is more lightweight that the other I cannot say.


Closes #153 with documentation update

See #153 for discussion..

Switching from cross-env to cross-env-shell did indeed do the trick.


Newlines missing in sidecar

I installed this easyocr version via pipx and I went to compare a bunch of files between the original ocrmypdf and this one, and found that while easyocr is WAY more accurate at getting the letters right, the sidecar is all one line.  Less than ideal and sounds like a bug to me.
If I pdftotext the pdf, it comes out on multiple lines.  But the sidecar is jacked.
to reproduce, use --sidecar  I can provide a jpg for sure if you want.

The output format from easyocr doesn't really have line group, so that information has to be inferred. Using pdftotext -layout should give an accurate reconstruction.


Performance improvements retrieving files

[ ] Improve speed of opening the main meta-analysis page, this is still slow compared to opening a job. My guess a lot of object creation.
[ ] Improve either how get_accessible_filepath_ids retrieves all ids or like in this case change it that so it doesn't retrieve all fp ids but just checking if fileA can be accessed by UserB

@antgonza, can you clarify? The main meta-analysis page seemed fast when I did them on qiita.colorado.edu

The speed is related to the amount of things you have access to, try
it as an admin. Note that (1) I'm talking about access to analysis
that are already completed and (2) that I believe the problem comes
from: https://github.com/biocore/qiita/blob/master/qiita_db/analysis.py#L470
as it basically is retrieving everything you have access to and then
checking if element x is in that list. Perhaps the easiest way to do
this is to simply have a single SQL command that checks in all tables
with an EXISTS that returns if that element exists in one of those
tables.

Oh, yes, that is not a scalable solution. Since we're dealing with IDs, do
we care about order? Any reason that get_by_status must return a list?
(same with the properties in question)?
On Tue, Mar 10, 2015 at 11:37 PM, Antonio Gonzalez<EMAIL_ADDRESS>
wrote:

The speed is related to the amount of things you have access to, try
it as an admin. Note that (1) I'm talking about access to analysis
that are already completed and (2) that I believe the problem comes
from:
https://github.com/biocore/qiita/blob/master/qiita_db/analysis.py#L470
as it basically is retrieving everything you have access to and then
checking if element x is in that list. Perhaps the easiest way to do
this is to simply have a single SQL command that checks in all tables
with an EXISTS that returns if that element exists in one of those
tables.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/issues/887#issuecomment-78208001.

No, about order. AFAIK it's a nice to have to return a list of all elements
for certain things but not for this ...

i'm gonna try toying with the order... the only possible use i can see of
the order is if its ascending or descending, in which case that can be done
external if necessary. the order returned ought to be interpreted as
arbitrary and as though it doesn't matter anyway
On Wed, Mar 11, 2015 at 12:20 AM, Antonio Gonzalez<EMAIL_ADDRESS>
wrote:

No, about order. AFAIK it's a nice to have to return a list of all elements
for certain things but not for this ...
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/issues/887#issuecomment-78211443.

Reopening as only one issue was addressed.

Closing in favor of https://github.com/biocore/qiita/issues/1010


Allow 5-digit splashtag #s

Allow number to go up to 99999 insteas of 9999. There are a couple occurrences of this in my battle JSONs:

Maybe a bug by Nintendo, but if we don't allow it, the battles can't be uploaded.

Docs will have to be updated too: https://github.com/fetus-hina/stat.ink/wiki/Spl3-API:-Post-v3-battle

I'm going to try to make a new one to fix the "Check Author" CI command.

If a 5-digit number is displayed during a game or on SplatNet, it must be supported.
However, this is not the case, so this is a matter for consideration.


Why use calcWorkerId?

I'm interested in the codes.
I noticed that every worker name has a workerid, which is calced by a hash function.(code comment link to a Birthday_attack wiki page).
Is that just for speed optimization or has any other concerns?

It's for speed optimization. And we need a fixed length data in sharelog or the sharelog parser will be more complex.

Thanks for your information :)


Some certificates are v1 certificates unnecessarily

https://self-signed.badssl.com, at least, is a v1 certificate. It would be better to make it a v3 certificate. Otherwise, an implementation that rejects v1 certificates will never test the self-signedness aspect of the certificate.
The same applies to any other v1 certificates in the set.

Note also that v1 certificates are not supposed to contain v3 extensions. This means that a v1 certificate will also lack a subjectAltName extension.
In general, every certificate should have just one problem, unless the test is specifically testing the intersection of problems.

This is a problem with the particular self-signed cert that @lgarron is using.  The certs that cert-generator.sh uses do not have this problem:
$ openssl s_client -connect self-signed.badssl.com:443 -servername self-signed.badssl.com | openssl x509 -noout -text

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            f3:5f:5f:7c:55:f6:40:40
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=US, ST=California, L=San Francisco, O=BadSSL, CN=*.badssl.com
        Validity
            Not Before: Jun  8 02:05:42 2015 GMT
            Not After : Jun  7 02:05:42 2017 GMT
        Subject: C=US, ST=California, L=San Francisco, O=BadSSL, CN=*.badssl.com
        [...]

Lucas, if you just want any self-signed cert, you can use the one that I just generated today:
-----BEGIN CERTIFICATE-----
MIIDhjCCAm6gAwIBAgIJAPNfX3xV9kBAMA0GCSqGSIb3DQEBCwUAMGIxCzAJBgNV
BAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1TYW4gRnJhbmNp
c2NvMQ8wDQYDVQQKEwZCYWRTU0wxFTATBgNVBAMUDCouYmFkc3NsLmNvbTAeFw0x
NTA2MDgwMjA1NDJaFw0xNzA2MDcwMjA1NDJaMGIxCzAJBgNVBAYTAlVTMRMwEQYD
VQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1TYW4gRnJhbmNpc2NvMQ8wDQYDVQQK
EwZCYWRTU0wxFTATBgNVBAMUDCouYmFkc3NsLmNvbTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAJrEDW/pVUcQc0/6WiGmusFagyBUkR25QQXhfz516t+n
23M/V2E6N0JjuAnfkGyd0eMyN2fCY9Pot22Q8L2ZTfvtVBrqy8mGDg6uZ7NyBDYC
vjwStIwTbySe4/BtevBFt9AUtSq/FG2q2gXdUudIJ7EZkT+IjEZrGiWTmHgMuOA8
FnMHPDEgHPDCD6I/GeCYFHAWoqLpNX0TXOSOttuqrHBWBd2vEPqDBmDTsWSOLbrP
a7GQi9L+szHS8CfJG5c730HD2SIgHJiNxBrJHqSXxbKe5woyG5+sK5xbmIRFymOc
+tLH+FKa24ma/2TskNv6ESeONZToD/LTEuQFIzNreTcCAwEAAaM/MD0wCQYDVR0T
BAIwADALBgNVHQ8EBAMCBeAwIwYDVR0RBBwwGoIMKi5iYWRzc2wuY29tggpiYWRz
c2wuY29tMA0GCSqGSIb3DQEBCwUAA4IBAQA3oEKDomJ0yCaIub4/QT7rjnn5ZDJV
7A3FUSCB+ulv+AdoNJ2eGszDCcDpcNIsVUBNOTVWytmQMyLElLvtVubXYvUXWoHi
hCpbzbc+XQv6ZXLIRO4+a5gfIyDVb87mFYUWUnwfkao+0WupbaWg2+tglidRXuDY
o3ywHGswEAitOiA//brYScOe5Yz16pcNsH3svKs4L4nDQEjkU1u4MMEJ7MnXJRku
eLRs9QYhQRTKV9UFlrMCpf1KdbSkHCYFRJg51bvcXB0kWm8DJHvTlIlay0kyxhMl
mfm1YBbQqhfUVc1bTBLhIyotBl3vBFYiSd8s9ku3kHpVubFiFukE2o8p
-----END CERTIFICATE-----

The same applies to any other v1 certificates in the set.

As April suspected, the self-signed cert is the only v1 cert (no doubt to my old CSR scripts). I'll update it tomorrow.
Is there any use case for testing clients that actually reject v1 certs?
(i.e. is it worth hunting to see if any CA will still sign a v1 cert? :-P)

Is there any use case for testing clients that actually reject v1 certs?
(i.e. is it worth hunting to see if any CA will still sign a v1 cert? :-P)

Yes: libwebpki does not support anything other than v3 certificates. That's how I found this issue in the first place.
Hopefully, you will not find a commercial CA that will issue a v1 certificate. They are required to add a subjectAltName extension and v1 certificates are not allowed to have extensions.

v3 cert is live.

And thanks for sending me a cert, April. But I needed one for the existing private key. ;-)


ocamlPackages.mirage-stack: 2.1.0 → 2.2.0

Motivation for this change
https://github.com/mirage/mirage-stack/releases/tag/v2.2.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build jackline


Added Bytes property to Utf8String

Now that we have ReadOnlySpan, there is no reason to expose the bytes,
and it allows to avoid copies in many scenarios.

@dotnet-bot test this please


can not  see office 2021 ltsc product key referring official documents

https://docs.microsoft.com/en-us/microsoft-365/admin/setup/download-software-licenses-csp?view=o365-worldwide
I can not see my office 2021 LTSC product key which is from CSP program referring to this document ,why ?

@iovex  Thank you for your feedback. Office LTSC 2021 is available only via volume licensing, so it is not included in this article. We have an end to end deployment guide for LTSC 2021 which can be found here -  https://docs.microsoft.com/en-us/deployoffice/ltsc2021/overview
It includes deployment, update, and activation.
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @iovex Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Switch to using ThreeJS WebGPU renderer?

With the recent changes in ThreeJS, and the introduction of NodeMaterials in core ThreeJS accessible when using the WebGPURenderer, it may be interesting to look into switching to using it.
Though after a quick look, it seems the stencil buffer is not usable yet using this renderer? So this may be a no-go as of today.
Using node materials could eventually allow us to fix the z-fighting issue when using the logarithmic depth buffer (failed attempt in https://github.com/jupytercad/JupyterCAD/pull/503 with using the default renderer).
Node materials would allow tweaking the depth computation in the fragment shader, by extending MeshBasicNodeMaterial.

For reference, this is where the logarithmic depth computation is performed using the new ThreeJS shading language (TSL) https://github.com/mrdoob/three.js/blob/48e6e2ee4e769013b911a079a433aecc2686d5b2/src/nodes/display/ViewportDepthNode.js#L119.
We could then simply offset the result of this function, and pass this to the depth parameter of the NodeMaterial.


Column is lowercased when being used in 1-to-many relation

We have following data structures:
User struct {
Id            uint64        json:"id" gorm:"column:USER_ID;primary_key"
// ...
PhoneNumbers  []PhoneNumber json:"phoneNumbers" gorm:"foreignkey:UserId"
}
PhoneNumber struct {
Id     uint64 json:"id" gorm:"column:PHONE_NUMBER_ID;primary_key"
UserId uint64 json:"userId gorm:"column:USER_ID"
// ...
}
usersFromDb := []User{}
db.Find(&usersFromDb)
for i, _ := range usersFromDb {
db.Model(usersFromDb[i]).Related(&usersFromDb[i].PhoneNumbers)
}
Results in following SQL (from strace output):
SELECT  * FROM "USER"
SELECT  * FROM "PHONE_NUMBER"  WHERE ("user_id" = ?)
SELECT  * FROM "PHONE_NUMBER"  WHERE ("user_id" = ?)
And the following error:
(SQL Error 260 - invalid column name: user_id: line 1 col 39 (at pos 38))
The problem seems to be that the USER_ID gets lowercased somewhere along the way, i.e. we specify USER_ID and it's USER_ID in database yet the generated query has user_id.
The same lowercasing happens when using Preload (the query is different, uses IN), the generated query also use user_id instead of USER_ID as specified in the model.
The lowercasing does not happen all the time, e.g. db.Find(&u, 1) correctly uses USER_ID.

Oops, this is not an actual bug, our tag (json:"userId gorm:"column:USER_ID") was missing a double quote.


Kubernetes objects have too much potential accesses

ServiceAccount objects listed below have too broad access and are able to modify coredns ConfigMap. As such this can result in CoreDNS poisoning attack. We should disallow those SAs to have such access.
    ServiceAccount - opentelemetry-operator-controller-manager
    ServiceAccount - opentelemetry-operator-controller-manager
    ServiceAccount - tobs-kube-prometheus-operator
    ServiceAccount - test-timescaledb

This should be implemented in upstream helm charts.


Create an Article for Map, Filter and Reduce

[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.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi,
Thanks for this pull request (PR).
Unfortunately, we are marking closing this PR, because it is a direct copy/paste from by pythontips website.
Feel free to submit another PR though.
Thank you


Typos in built_in.any

As you can see in the screenshot, there are two typos in the built_in.any example snippet.

The description states "An example for using all with list" and the actual snippet outputs "ant" instead of "any".
Thank you

I update it.
Thank you for your comment.


Turn on CodeQL scanning

https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository
GitHub has a new security scanning tool that's available through GitHub Actions. It looks pretty easy to set up, would be nice to integrate into the existing PR and CI runs.

Hi @dpogue I'd gladly take on this task


Created an installable Python Package

Re-wrote the main and created an installable Python package. cheers.

Very nice, thank you very much!
I have added some notes regarding Python 3, fixing the import works - tested with softflowd ;)


Create Swagger API specification for Mobility Database

Description
Create a swagger API specification for MobilityData Database. References to the previous Catalog API swagger version can be found at https://app.swaggerhub.com/apis/MobilityDataOrg/MobilityDataCatalogs/1.0.0.
Acceptance criteria

Have a  swagger API  specification for MobilityData Database public available on swaggerhub.
Share the swagger specification and gather feedback.
Meet V1 requirements from the PRD

Terminology

Feed = continuous stream of data (use the term feed instead of source)
Dataset = specific feed version, e.g June 2023 dataset

Resources
Architecture diagram for this iteration: https://docs.google.com/document/d/12PE2du2eEkHBdfAbJTGiW6RxIr4K1dpDDvgxRL-P9zc/edit#heading=h.3bbt32rot360
UI references: https://docs.google.com/document/d/1Kl3bvqb8sBLvkPbFWgLqDq56cJmEHBx8MLRzulBS4VI/edit#heading=h.byefkz7u88ee
TransitFeed's original API docs: https://transitfeeds.com/api/swagger/
Transitland's API docs: https://www.transit.land/documentation/rest-api/feeds
API PRD: https://docs.google.com/document/d/19n5kaIPKLYNKToBLEFOO5QzqPjAHGAneCBNcvhw7y4g/edit#

@jcpitre Added the PRD for the API as well if the context helps!

@jcpitre's API draft: https://app.swaggerhub.com/apis/MobilityDataOrg/MobilityDataCatalogProposedVersion1/1.0.0#


[LIVY-756] Add Spark 3.0 and Scala 2.12 support

What changes were proposed in this pull request?
This PR is based @tprelle 's PR #289 , and address all the left issues in that PR:

multi-scala version support in one build (Scala 2.11 and 2.12 support).
make SparkR work.

Also reverts most of the unnecessary changes. Besides this PR remove the build below 2.4 (2.2, 2.3), since Spark 2.2 and 2.3 only ships with Scala 2.11, hard to maintain multiple version. But user could still use 2.2 and 2.3 without changes.
All credits to @tprelle.
How was this patch tested?
Run UT and IT with Spark 2.4.5 and 3.0.0 locally.

@jerryshao How you manage to make sparkR work ?

Travis image seems too old to support Spark 3.0 R version, we should also upgrade Travis script.

reopen to trigger the test again.

@tprelle @andrasbeni would you please help to review, thanks!

I've triggered the travis test several times, seems everything is fine. I'm going to merge this, thanks @tprelle for the contribution.

Hey, are there any plans to release this feature :) ?

There still have some minor issues in JDBC side related to Scala versions. Will prepare a new release when everything is done.

@jerryshao will this be released soon?

@jerryshao Is it possible that you add the instruction to build the Spark 3.0 version of Livy to the README? I'd been struggling with Maven Profiles and didn't get anywhere.

@jerryshao Is it possible that you add the instruction to build the Spark 3.0 version of Livy to the README? I'd been struggling with Maven Profiles and didn't get anywhere (some tests are failing when I try to run mvn package -P spark-3.0)

There's 3 tests failing in module livy-rsc yes @Dom-nik, I guess we missed something ;)
Tests in error:
  TestSparkClient.testConnectToRunningContext:338->runTest:575->runTest:588 » Execution
  TestSparkClient.testImpersonation:321->runTest:575->runTest:588 » Execution ja...
  TestSparkClient.testRemoteClient:213->runTest:575->runTest:588 » Execution jav...

@jerryshao Is there any progress with 0.8.0 release?

@jerryshao Is there any progress with 0.8.0 release?

The changes introduced here upgrade Kryo from 2.22 to 4.0.2. This change makes the API incompatible. The latest AWS EMR release (6.2.0) includes Spark 3 and Livy 0.7.0 together with Kryo 2.22 and works fine. Can we revert the Kryo upgrade before the Livy 0.8.0 release to keep the API compatible?

Hi @jerryshao I have a Cloudera CDP Private Cloud 7.1.6 Hadoop system. As CDP Private Cloud 7.1.6 supports Spark 3.1 along with Spark 2.4, I have separately installed Spark version <IP_ADDRESS>.1.7280.2-11 on the system (as per Cloudera document https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/cds-3/topics/spark-spark-3-overview.html). I am trying to use Livy (version livy-0.7.1-incubating) to connect to Spark <IP_ADDRESS>.1.7280.2-11. Does livy-0.7.1 support Spark version 3.1? If so, are there any requirements that need to be followed?


MOS update/recovery functionality

Updating MOS has the potential to be slightly problematic.  A faulty MOS that fails to start up correctly can leave your machine in a completely unusable state, requiring re-flashing of the MOS using the agon-vdpflash utility.
The VDP could detect when the computer is stuck in the "wait_eZ80" state, and drop into a recovery mode.
Recovery mode could function in a very similar manner to the agon-vdpflash utility.
Extended functionality could include the ability of the VDP to automatically detect "known working" versions of MOS and automatically restore to that version.
If the VDP has built into it the ability to perform MOS recovery, then it may also make sense to use the same mechanism for more general MOS version updates.

There are two problems with this idea as of the time of writing.
Firstly the vdpflash utility requires a cable connection to be made on the board to allow the VDP to flash the z80.
Secondly as noted in #13 the VDP code currently uses too much RAM, so adding in any additional functionality is problematic.


AttributeError: partially initialized module 'cv2' has no attribute 'gapi_wip_gst_GStreamerPipeline' (most likely due to a circular import)

Expected behaviour
cv2 could be successfully imported.
Actual behaviour
After I install the opencv-python or opencv-python-headless, I import cv2, it will raise a exception:
AttributeError: partially initialized module 'cv2' has no attribute 'gapi_wip_gst_GStreamerPipeline' (most likely due to a circular import)
Steps to reproduce
OS: ubuntu22.04 in docker.
opencv-version:  <IP_ADDRESS>
Issue submission checklist

[x] This is not a generic OpenCV usage question (looking for help for coding, other usage questions, homework etc.)

P.S.: I can solve this issue using the answer. I use the version <IP_ADDRESS>, everything will be ok. However, that is the problem, I do not know why the new version will cause the error.
Thank you.

Most probably you faced the same issue as here: https://github.com/opencv/opencv/issues/23177
The most probable reason: multiple OpenCV instances installed on your system.

Closed as related OpenCV ticket has been resolved.


fix: make automountServiceAccountToken configurable

Makes automountServiceAccountToken configurable
Defaults to true by default for both ServiceAccount and Deployment resources.

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


CLOUD-58082: Logging Nullpointer fix

@akanto or @keyki pls review

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2508/


lobbying Costs Greater 100000 field not parsed

it appears that the field "Lobbying-Aufwand > EUR 100.000" (Register B) is not parsed.

fixed with https://github.com/OKFNat/lobbyScraper/commit/16c60c3250c746554a062e83400b1801cffd2756


Bug Report

I Updated v0.41.3
FancyZones and layout editor not working after update.
I always execute PowerToys as administrator.
Please Fix it.

Hi. Please use our bug report issue template for reporting a bug and attach a bug report.
You can create a bugreport with rightclick on the systray icon and then "Bug report"

@broodwar234   Please include a report bug zip file.
  Without that, we lack enough information here


Mentor assignment

Hello @dvjsharma myself Vikas Sharma, I am assigned as a mentor to your project. I have mailed you many times in this regard but no reply. Due to which i have to create this issue request. So I request you to provide me with the powers to label contributor issues, review their changes,

Sorry @sharmavikas4. Please connect with me on discord, same username.

@dvjsharma i have sent a request to @dvjsharma  on discord. Mu username is @vikas04052003 . Please accept the request as soon as possible


Isotopes are ambiguous in carbon chains

When a chain of 13Cs are drawn, there is no indication that any or all of the carbons are 13C isotopes.
For example: [13CH2]([13CH2][13C@@H]([13C](=O)O)N)[13CH2]N
All carbons in this molecule are 13C, but this is only clear in the COOH group.

Or with compoundDrawing: false, it's not clear that any of the carbons are 13C.

Related:

#173


Timestamps

Currently we only record the timestamps when a level was started and completed (this could be lost or won). If we want to understand how long someone took per decision, we would need to add that info to be collected in the database.

has been implemented

has been implemented


Update deny-transact-sql.md

Corrected typo by changing "grantor_prinicpal_id" to "grantor_principal_id".

Thanks, @sidesw1pe!


drivers: i2c: support multiple I2C addresses at runtime

Support storing multiple reg addresses with a new Kconfig symbol, I2C_FALLBACK_ADDRESSES. It is relatively common for I2C devices to be available in several variants with the only difference being the I2C address. This change allows all the possible addresses to be specified. This opens up the potential for boards to populate any variant depending on component availability, without changing binaries. The alternative is defining N devices for each potential device, which comes with a much larger footprint overhead than storing a 2 byte address in ROM and a 1 byte index in RAM.
This is particularly important at the moment with component shortages everywhere. The ability to load whichever variants you
can purchase is particularly valuable.
The si7210 driver is one such example (12 variants), which has been updated to support this new feature. Below is a portion of the datasheet demonstrating the above use case.

This solves the problem for some simple variants of #30692.

I think this is a good start. But I hope that it can be improved on.
I2C doesn't really support discovery. You are expected to know what is where. In practice this means that if you put another chip on that address that isn't what you expect you will never know and things will just fail.
This can happen for example if you need to change multiple chips or after a couple of hw revisions.
As an example to illustrate this: I have had this exact problem where we had to replace one LED chip that was compatible, but the new had another I2C address also(call all) that had the same address as a second chip, so the second chip had to get a new address. So now chip 2 had a new address, but the original address still gives a response, but from he wrong chip.
So for both the academic/theoretical and the practical reason, I'm not a fan of this solution.
My preference (if we keep this to only solve it for I2C) would be to runtime define the address. Then the software can check the version of the board (for example by using version GPIO pins) and tell what I2C addressed to be used based on the board version.

I2C doesn't really support discovery. You are expected to know what is where. In practice this means that if you put another chip on that address that isn't what you expect you will never know and things will just fail.

Agreed, this is not about generalized discovery, just attempting a limited subset of alternate addresses.

This can happen for example if you need to change multiple chips or after a couple of hw revisions.

If multiple chips are changing or you have literal hardware revisions, this is not intended to be a solution. Board revisions are still the intended solution in that use case.

So now chip 2 had a new address, but the original address still gives a response, but from he wrong chip.

Honestly I would chalk that up to bad luck, and roll the update as a new board revision.

My preference (if we keep this to only solve it for I2C) would be to runtime define the address. Then the software can check the version of the board (for example by using version GPIO pins) and tell what I2C addressed to be used based on the board version.

Not sure what other interfaces you would want it solved for?
RE the runtime definitions, that would require moving the i2c_dt_spec struct out of ROM, which is a much more invasive change than this. Furthermore this change is almost sufficient to get the behaviour you want. For drivers that you want that behaviour for, expose the spec_idx variable through an API call (instead of attempting to auto-detect it) and provide it early in the init process from the result of the GPIO read.

If multiple chips are changing or you have literal hardware revisions, this is not intended to be a solution. Board revisions are still the intended solution in that use case.

Yeah. It would be really nice not to have multiple binaries for a small change like that though. It does involve extra work. So board revisions is nice in some ways, have the big drawback of multiple binaries.

My preference (if we keep this to only solve it for I2C) would be to runtime define the address. Then the software can check the version of the board (for example by using version GPIO pins) and tell what I2C addressed to be used based on the board version.

Not sure what other interfaces you would want it solved for?

I don't have a specific example of this right now. Just keeping things open. Fixing it for I2C would probably cover a majority of cases.

RE the runtime definitions, that would require moving the i2c_dt_spec struct out of ROM, which is a much more invasive change than this. Furthermore this change is almost sufficient to get the behaviour you want. For drivers that you want that behaviour for, expose the spec_idx variable through an API call (instead of attempting to auto-detect it) and provide it early in the init process from the result of the GPIO read.

It would be nice if it was part of the API so all I2C had to implement it so it was always there if needed, without having to modify a driver and get that up streamed and so on.
Here is someone suggestion using hwinfo for a related solution. https://github.com/zephyrproject-rtos/zephyr/issues/49942#issuecomment-1237787253

It would be nice if it was part of the API so all I2C had to implement it so it was always there if needed, without having to modify a driver and get that up streamed and so on.

I agree it would be nice, but the existing API is designed around i2c_dt_spec being ROM (placed in driver config structs, not data). This feature requires runtime detection, so it requires some form of mutable state, so I'm not sure if that is possible.

Here is someone suggestion using hwinfo for a related solution. https://github.com/zephyrproject-rtos/zephyr/issues/49942#issuecomment-1237787253

That proposal is essentially a driver for reading the state of GPIOs, I'm not sure how it's relevant.

It would be nice if it was part of the API so all I2C had to implement it so it was always there if needed, without having to modify a driver and get that up streamed and so on.

I agree it would be nice, but the existing API is designed around i2c_dt_spec being ROM (placed in driver config structs, not data). This feature requires runtime detection, so it requires some form of mutable state, so I'm not sure if that is possible.

Here is someone suggestion using hwinfo for a related solution. #49942 (comment)

That proposal is essentially a driver for reading the state of GPIOs, I'm not sure how it's relevant.

To answer both. By having the version implemented in a standard way Zephyr can know about it and therefore will be able to select I2C address based on it or forward it to the driver. The driver then needs to get that information in the init function on one way or another. Or Zephyr can have helper functions that uses that driver to get the correct configuration, that the I2C driver can use. The figured out valid I2C address will have to live in RAM no matter how it is done, so I don't really see the ROM/RAM conflict here.
The key is just that how to read those pins/the hw version needs to be abstracted away in a standard way for the drivers and/or Zephyr to be able to use that information.

The key is just that how to read those pins/the hw version needs to be abstracted away in a standard way for the drivers and/or Zephyr to be able to use that information.

I disagree that an API to return a hardware version is the "key" to the features described. It is definitely required, but it is also the first and easiest step. I would love to be proven wrong, but I don't see an easy path toward what you describe, maybe just because it is lacking in detail.

The key is just that how to read those pins/the hw version needs to be abstracted away in a standard way for the drivers and/or Zephyr to be able to use that information.

I disagree that an API to return a hardware version is the "key" to the features described. It is definitely required, but it is also the first and easiest step. I would love to be proven wrong, but I don't see an easy path toward what you describe, maybe just because it is lacking in detail.

Sorry. I meant that that was the key reason that I linked to that. It is a small, but important part, to get it working. It is not the key to the whole solution.
However, I just realized that this problem isn't that different from dynamic pin control in some ways. https://docs.zephyrproject.org/latest/hardware/pinctrl/index.html#dynamic-pin-control . It could perhaps be modeled more like that. So that custom code will be executed to selected configuration based on whatever criteria you want, including probing. Pin control is something that was very static, that was made dynamic with that feature.
However, I am a bit to new and unfamiliar with the internals of zephyr in this case to provide an exact solution. But I haven't seen anything yet that that I feel would make it (practically) impossible. And I do believe that many people would find it useful and it would add lot of value to have it cover as many use cases as possible.

@teburd can you please take a look?

I don't hate it, but I don't love it either.

I am on the same page here. I wrote this to support a real use-case I had an submitted it upstream in case it was useful.

I guess I'm wondering why a driver can't do this itself by probing the bus for all the possible addresses at init time and choose then.

Of course they could, but as soon as you have more than 2 drivers doing this, looping over the reg = <> fields may as well be in a common helper function.

There's no requirement to use i2c_dt_spec, that's there for convenience. If a driver can take advantage of multiple addresses that seems like a driver specific thing.

A lot of things in Zephyr exist for convenience. If this is a problem that could be solved/made easier for multiple drivers in one place I think that is useful.

Blocking as I do not agree with the design choices made here.

Is it the feature itself that you disagree with or the implementation?


deprecated async_get_registry

Detected integration that uses deprecated `async_get_registry` to access device registry, use async_get instead. Please report issue to the custom component author for ecodevices using this method at custom_components/ecodevices/__init__.py, line 91: device_registry = await dr.async_get_registry(hass)

fix with 4.2.0


collections.Mapping doesn't exist on Python 2.5

Introduced in https://github.com/django-nonrel/django-dbindexer/pull/5 . Apologies folks.

Duplicate of #8.


Setting up environment with docker

I tried to follow the guide written here and encountered some problems: https://medium.com/@ekkis/eos-development-on-docker-3f4eb9b680ec
On Ubuntu 18.04. Steps taken
Setup folders
mkdir eos && cd eos
mkdir contracts

Create docker-compose.yml
version: "3"

services:
  nodeosd:
    image: eosio/eos-dev
    command: /opt/eosio/bin/nodeosd.sh --data-dir /opt/eosio/bin/data-dir -e --http-alias=nodeosd:8888 --http-alias=<IP_ADDRESS>:8888 --http-alias=localhost:8888
    hostname: nodeosd
    ports:
      - 8888:8888
      - 9876:9876
    expose:
      - "8888"
    volumes:
      - nodeos-data-volume:/opt/eosio/bin/data-dir
      - ./contracts:/contracts/usr
    cap_add:
      - IPC_LOCK
    stop_grace_period: 10m

  keosd:
    image: eosio/eos-dev
    command: /opt/eosio/bin/keosd --wallet-dir /opt/eosio/bin/data-dir --http-server-address=<IP_ADDRESS>:8900 --http-alias=keosd:8900 --http-alias=localhost:8900
    hostname: keosd
    links:
      - nodeosd
    volumes:
      - keosd-data-volume:/opt/eosio/bin/data-dir
      - ./contracts:/contracts/usr
    stop_grace_period: 10m

volumes:
  nodeos-data-volume:
  keosd-data-volume:

So your filesystem looks like:
eos/
  docker-compose.yml
  contracts/

Run docker compose:
docker-compose up -d

Alias eosiocpp
eosiocpp() { d=/contracts/usr; docker exec eos_nodeosd_1 /opt/eosio/bin/eosiocpp $1 $d/$2 $d/$3; }

Create smart contract
mkdir contracts/hello
touch contracts/hello/hello.cpp

Smart contract:
#include <eosiolib/eosio.hpp>
#include <eosiolib/print.hpp>
using namespace eosio;

class hello : public eosio::contract {
  public:
      using contract::contract;

      /// @abi action
      void hi( account_name user ) {
         print( "Hello, ", name{user} );
      }
};

EOSIO_ABI( hello, (hi) )

run eosiocpp
eosiocpp -o hello/hello.wast hello/hello.cpp

output:
/contracts/usr/hello/hello.cpp:1:10: fatal error: 'eosiolib/eosio.hpp' file not found
#include <eosiolib/eosio.hpp>
         ^~~~~~~~~~~~~~~~~~~~
1 error generated.

I don't know in which ways I should set up my environment differently. I've tried building locally (using sudo make install with or without aliasing commands) and in almost every situation eosiocpp cannot seem to find the appropriate libs. Either this error or not finding stdint.h. Is there any advice you could give me?

I'm struggling with the same, its very hard to get all of Eos working on my Mac. Even with docker this is a frustrating experience of try and error

Also running into this issue but on Ubuntu 16.04 - any guidance would be greatly appreciated.

So I went ahead ahead and built and installed the eosio.wasmsdk toolchain, and got eosio-cpp working (albeit also had its complication with boost not being found) but through that toolchain as of right now I can't generate an abi. Any advice there @taokayan?

i am also facing same issue ,fatal error: 'eosiolib/eosio.hpp' file not found
any solution?

So I made it work using docker, and it may be helpful for you folks.
First I'm using this docker-compose.yml file:
version: "3"

services:
  builder:
    build:
      context: builder
    image: eosio/builder

  nodeosd:
    container_name: nodeosd
    build:
      context: .
    image: eosio/eos-dev
    command: /opt/eosio/bin/nodeosd.sh --data-dir /opt/eosio/bin/data-dir -e
    hostname: nodeosd
    ports:
      - 8888:8888
      - 9876:9876
    expose:
      - "8888"
    volumes:
      - nodeos-data-volume:/opt/eosio/bin/data-dir
      - ../contracts:/contracts # this is important

  keosd:
    container_name: keosd
    image: eosio/eos:latest
    command: /opt/eosio/bin/keosd --wallet-dir /opt/eosio/bin/data-dir --http-server-address=<IP_ADDRESS>:8900
    hostname: keosd
    links:
      - nodeosd
    volumes:
      - keosd-data-volume:/opt/eosio/bin/data-dir
      - ../contracts:/contracts
    stop_grace_period: 10m

volumes:
  nodeos-data-volume:
    external: true
  keosd-data-volume:
    external: true
  contracts:
    external: true

I'm also using those alias to be able to interact with it:
alias cleos='docker-compose -f /Users/lucca/Development/cpp/eos/Docker/docker-compose.yml exec keosd /opt/eosio/bin/cleos -u http://nodeosd:8888 --wallet-url http://localhost:8900'

alias eosiocpp='docker-compose -f /Users/lucca/Development/cpp/eos/eos/Docker/docker-compose.yml exec nodeosd /opt/eosio/bin/eosiocpp'

For all of that to work out I need to use a docker volume that is mapped to CHANGE_TO_YOUR_EOS_PATH/contracts. It must be the build variation.
Also to use eosiocpp you will have to use the directories from your docker:
$ eosiocpp /contracts/hello
It helped me a lot to do stuff inside docker so everything is liked using
docker-compose -f ../../Docker/docker-compose.yml exec nodeosd bash
It also took me a while to notice that we use cleos from the keos docker but we build from nodeos docker, so be sure to connect/use the right docker when needed
With all of this I could stop getting those eosio.hpp file not found errors

@jpopesculian and rest:
see #5133 for a workaround/fix

try the latest 1.2.0, this should fix your issues (please close this issue if it works for you).

Works thank you! In addition small repository of setup tools for beginners https://github.com/jpopesculian/eos-docker if you want to link anyone @lazaridiscom


Implement SFTPSensorAsync

Addresses #629
Implements a basic, functional asynchronous SFTPSensor using asyncssh.
First time contributor here, so open to feedback on style and technical decisions around how these operators are generally formatted/created.

Will address failures

Hi @tseruga. Thanks for contributing to this project and creating this PR. We will definitely take a look at this PR and share the feedback.

Unsure of how to address the remaining build failures:
build_docs is complaining about my usage of * in my doc-strings. I annotated the line so the static checker locally doesn't complain about it, but I'm not sure if there's another annotation I should use for build-docs to accept it. I can also remove it if it's just easier to link to the fnmatch docs instead of having the info in the doc-string itself.
mypy is complaining about type hints due to class inheritance. The parent SFTP sensor class expects Optional[SFTPHook] but I'm overriding the hook with the new custom async hook SFTPHookAsync, which is a child of SFTPHook.
There also numerous errors from mypy which aren't due to my changes. Not sure what to do about those

For the build docs failure, you need to add the .rst file for sftp sensor in  docs/providers (follow dbt or http sensors)
and you need to make an entry in docs/providers/index.rst as well

@tseruga For docs failure,
You need to add sftp in docs/providers/index.rst and you need to create folder sftp as I mentioned in the earlier comment
For mypy failure, which is not related to your changes , that is covered in one of the PR once it is merged it will cover

Im clearly missing something obvious with sphinx docs. I've added an entry to the providers/index.rst but it still seems to be building the docs incorrectly for sftp. I've looked for an inconsistencies compared to other providers, but can't find it. I'm sure it's something small

Im clearly missing something obvious with sphinx docs. I've added an entry to the providers/index.rst but it still seems to be building the docs incorrectly for sftp. I've looked for an inconsistencies compared to other providers, but can't find it. I'm sure it's something small

Docs build should be working now. mypy will be fixed by https://github.com/astronomer/astronomer-providers/pull/659

Any thoughts on how we will run this in our integration tests? I think we may take this in separate PR, I have created an issue to track it https://github.com/astronomer/astronomer-providers/issues/662

Please Update/rebase your branch.

Ill look through the missed lines and add some tests

Surprised 97.4% coverage still fails the check 😆 I can cover the missing lines

Thanks @tseruga for addressing the comments. Looking great 🚀

@tseruga  can you rebase so we can merge it?

This is awesome, thanks @tseruga  👏 for creating the PR. Appreciate it.

Awesome work @tseruga , congrats on your first merged pull request!

Thanks @pankajastro @rajaths010494 @bharanidharan14 !
Hopefully will be contributing more in the future!


Can I use several images for training?

Hi. Change the init_embedding in embedding_manager.py into an image-independent embedding (instead of CLIP image embedding in InST) to train on several similar concept images.

Hello, can you describe in detail how to modify the code so that each style corresponds to a .pt? @zyxElsa


[Feature]: Use discountCode in PricingPreview

Tell us about your feature request
Pricing preview should allow to apply discount. There is discountId but no way to get discountCode using clientToken.
What problem are you looking to solve?
Additional discountCode property or API to fetch discountId from discountCode using clientToken.
Additional context
No response
How important is this suggestion to you?
Critical

Hi @holtwick,
Thank you for sharing this feedback with us.
This is the first time we are hearing about this as most integrators will be able to map their discountID while building the pricing page.
To help us understand this further, can you please share more details on how you are integrating the pricing preview API with your pricing page?
We could then help determine if there is a better way of achieving what you are trying to do while we take this to the product team for assessment.
Thank you.

Sure. Take this URL for example:
https://pdfify.app/en/buy?coupon=F9AF6FAA
I distribute coupons to my clients and they should be able to apply them. To make it simple, I usually distribute the URL as seen above. But the coupon still should have a self speaking name like SUMMERSALE2024 or the like.
The checkout for Paddle Billing has the ability to  hand over this code, but the preview in the page should also show the effect of the coupon to trigger users to buy. In Paddle Classic this was possible.

Hello 👋 ,
Thank you for sharing the URL.
Unfortunately, we don't have a way of doing this right now. I will raise this to the product team for further analysis.
Meanwhile, I can think of an alternative approach to what you want.

Instead of adding the discount code to the URL, maybe you can add a discount ID and share it with your clients.
When they load the page, you can pass the ID to the price preview API.
The response will include the discount code (data.details.line_items[].discounts[].discount.code) and the percentage (data.details.line_items[].discounts[].discount.amount ). You can then display this information to your clients.

This approach is not ideal, but it could be a middle ground until the feature is implemented.
Please let us know if we can help you with anything else.
Thank you.

Well, for this and a few other reasons, I'm sticking with Paddle Classic for now. The new API doesn't seem to be ready yet... sorry.


add-patient button for no search results

Related Issue or Background Info

resolves #2340

Changes Proposed

add Add new patient link to no search results view

Additional Information
Screenshots / Demos

Checklist for Author and Reviewer
UI

[ ] Any changes to the UI/UX are approved by design
[ ] Any new or updated content (e.g. error messages) are approved by design

Testing

[ ] Includes a summary of what a code reviewer should verify

Changes are Backwards Compatible

[ ] Database changes are submitted as a separate PR

[ ] Any new tables that do not contain PII are accompanied by a GRANT SELECT to the no-PHI user
[ ] Any changes to tables that have custom no-PHI views are accompanied by changes to those views
(including re-granting permission to the no-PHI user if need be)
[ ] Liquibase rollback has been tested locally using ./gradlew liquibaseRollbackSQL or liquibaseRollback

[ ] GraphQL schema changes are backward compatible with older version of the front-end

Security

[ ] Changes with security implications have been approved by a security engineer (changes to  authentication, encryption, handling of PII, etc.)
[ ] Any dependencies introduced have been vetted and discussed

Cloud

[ ] DevOps team has been notified if PR requires ops support
[ ] If there are changes that cannot be tested locally, this has been deployed to our Azure test, dev, or pentest environment for verification

@Rebecca-LM I hear ya on the button. I'll take another look at the design. For now, we'll push the change to have the feature available for users and make any styling changes later.

@Rebecca-LM talked to Kenny and decided to push out this PR and implement the changes in a future PR


Add support for a custom evaluation context that can be inherited and overridden

Allow a custom evaluation context to be defined.

Closed by: https://github.com/galaxyproject/total-perspective-vortex/pull/27


Avoid agent in place_obj method after game start and fix Dynamic-Obstacles bugs

Fixed avoiding agent when placing object after game start. Had to consider start_pos as well because some environments placed objects depending on this variable only (before agent_pos was set). Toggle in place_obj - start_pos / agent_pos while generating grid, based on is_gen_grid variable.
Dynamic-Obstacles env was relying on being able to position obstacle on top of the agent, so I extended place_obj method to be able to this is as well.
Closes: #66
Found what I guess to be an unintentional bug in Dynamic-Obstacles: being able to pick up the obstacles. This was causing also an error because of self.obstacles list not being updated. Fixed this by changing to a ball that cannot be picked up.
Fix 837f5e5

I'd rather not have a new type of ball object. Rejecting the pickup action in this environment ought to be sufficient.
I feel there also should be some way to avoid this: self.is_gen_grid = False :frowning:


Escape 'rank' column in SQL queries since it is a reserverd keyword in mysql 8.0.2

Escape 'rank' column in SQL queries since it is a reserverd keyword in mysql 8.
Fixes issue #242

@mihajul Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@mihajul Thank you for signing the Contributor License Agreement!

Is this pull request will be merged soon?

Merged quickly will be better.


Cleanup CI for documentation

Summary
This PR cleans up the CI for documentation changes.

Tests (including e2e tests) and code linter are not run in CI if the PR only changes documentation
Code Linting does not generate documentation anymore
Remove Make targets:

make docs-<html/pdf/...>: Was broken since v1.2.0 and not used as final documentation webpage is generated separately
make docs-syntax: Was broken since v1.2.0
make docs-htmltest: Was broken since v1.2.0
Meta tags to generate downloadable docs

Removed any dependency other than podman/docker for working with documentation

Auto detects if using docker or podman
Auto detects if go is present on machine. Otherwise uses golang container for auto-generating documentation

Add documentation linting step to CI that runs vale (only if documentation changes)

See https://github.com/k8up-io/k8up/pull/870 for a PR that only touches documentation (and fixes vale linting issues)
Checklist
For Code changes

[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
[x] I have not made any changes in the charts/ directory.

E2E test is flaking again, but as we did not change anything that can effect it, I'm merging.


ssl cert for rabbitmq expired

This is not handled by the current playbook/cronjob

fixed for now, will update the cron job later


Added NuGet set api key aliases

Added aliases for setting api key for a given source. This allows you to authenticate to private feeds using an API key.
Example usage:
NuGetSetApiKey("3f81e328-3ba1-47eb-a92b-363d804bd132", "http://www.privatenugetfeed.com");

I'm a human StyleCop :wink:

@patriksvensson this became a rabbit hole :) Found an verbose logging issue outputting "unsafe" values (true for all tools, but could easily fix in this case)
Added so that tool output is validated and added tests for this.

Merged! :+1:


Check permalinks end in / in diagnostics

This will help catch cases like #732.

Implemented in 2b4907c871c6804c518ebf707ac6f2e826e39745.


Investigate if there is a quick way of autoscaling in Loris

From IIIF outage retro 18 May 2020
Maximum time to be spent investigating: 2-3 hours

I'm going to close this as WONTFIX, because we're going to be decommissioning Loris soon and this isn't worth investigating now.