Release failed [resourceX already exists]

I tried to write some charts with dependencies. Chart heapster depends on chart influxdb. I created influxdb chart, hosted it locally with helm repo. Created heapster chart, did helm dependency update:
├── heapster
│   ├── charts
│   │   └── influxdb-0.1.0.tgz
│   ├── Chart.yaml
│   ├── Dockerfile
│   ├── Makefile
│   ├── requirements.lock
│   ├── requirements.yaml
│   ├── templates
│   │   ├── _helpers.tpl
│   │   ├── rc.yaml
│   │   └── svc.yaml
│   └── values.yaml

But, when I am trying to install heapster chart I am getting error:
Error: release wandering-rode failed: [services "wandering-rode-influxdb" already exists, replicationcontrollers "wandering-rode-influxdb" already exists]

And it all on after deleting all resources(I checked with helm list --all).
helm version:
Client: &version.Version{SemVer:"v2.0.0-beta.2", GitCommit:"8a5550d0c6785eaa94eac80e0c1d11a92c355a02", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.0.0-beta.2", GitCommit:"8a5550d0c6785eaa94eac80e0c1d11a92c355a02", GitTreeState:"clean"}

My repo with these charts.

If you do a helm install --dry-run --debug $CHARTNAME, are you seeing multiple services getting defined with the same name?

yes, I think problem in {{ template "fullname" . }}. For influxdb and heapster I am using _helpers.tpl with the same content.
# Source: heapster/charts/influxdb/templates/rc.yaml
apiVersion: v1
kind: ReplicationController
metadata:
  labels:
    name: looping-unicor-heapster
    heritage: "Tiller"
    release: "looping-unicor"
    chart: "influxdb-0.1.0"
  name: looping-unicor-heapster

----
# Source: heapster/templates/rc.yaml
apiVersion: v1
kind: ReplicationController
metadata:
  labels:
    k8s-app: looping-unicor-heapster
    name: looping-unicor-heapster
    heritage: "Tiller"
    release: "looping-unicor"
    chart: "heapster-0.1.0"
  name: looping-unicor-heapster

How I can fix this problem? I need for heapster fullname with heapster suffix and for influxdb - influxdb suffix.

Probably the easiest would be to rename the fullname partial to something like fullname_heapster and fullname_influx (in the _helper templates).


Invitation API and Storage

Summary
Adds an Invitation object and stores it in a generic secretstorage.
The status handling of the resource is modeled after the official interfaces, but has prefixed methods to not trigger a storage registration bug.
Adds a reconciler for the newly created Invitation object that adds a token to the invitation.
apiserver/secretstorage/storage.go is the most important to review.
Checklist

[x] PR contains a single logical change (to build a better changelog).
Still way to big. Sorry 🤷♀
[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.

don't forget RBAC

i did as always 😅


Make Strategia be compatible with MonthlyBudgets

MonthlyBudgets can be set up  to replace funds by reputation and give the monthly buddget calculated by that reputation then.
When Strategia gives funds, these will be scrapped on the monthly budget report ...
So a codewise compatiblity to check for MonthlyBudgets' existance and its setting for "Give reputation instead of funds" should be taken into account by Strategia and so also give reputation instead of funds by the same conversion factor MonthlyBudgets uses.

btw I tried it with a patch; some parts work, others don't - because of it's hardcoded.
https://www.dropbox.com/s/y4s19tssfxw4c76/zzz_StrategiaForMonthlyBudgets.cfg?dl=1

I close this for now because there is a new mod as a sucessor: Bureaucracy - Monthly Budgets
https://forum.kerbalspaceprogram.com/index.php?/topic/191192-19x-bureaucracy-monthly-budgets-reimagined-14-27062020/


Consider Redesign of And and Or

Currently the And and Or blocks have two statement connectors. I'm thinking about reducing it to one.
The idea is that statements that are stacked on top of each other have an "and" between them already, so the
and block could just do nothing but put parenthesis around whatever is inside it. The or block, on the other hand,
could go through all the top level blocks and put semicolons between them, similar to the way in which the fact block puts periods.
This would solve the "nested ors are ugly" problem.

In the v1 branch, this redesign has been implemented, along with other changes. The blocks have not yet been added to the interface, because "or" is not an operator in s(CASP), so a separate issue will be created for implementing disjunction in s(CASP).


add wifi sub command

The wifi subcommand allows to set configuration for wifi interfaces.
While adding the necessary functionality for the wifi subcommand I
refactored the hostname subcommand a bit, too.

Need o fix the tests for the hostname subcommand and add some tests for the wifi subcommand, too.
But that's for another day...


multiclasse tracking

@viplix3 In case of multi class (not only human) should the tracker by shared or we should run on tracker per class ?
( of course CMC can be run once)

@arnaud-nt2i the Kalman Filter algorithm used by the tracker for state estimation encodes various characteristics (change in velocity, aspect ratio changes, etc.) of the object being tracked internally in its mean and covariance state matrices.
So yeah, as you guessed, the tracker should be different for classes having contrasting characteristics to get the best tracking results as you can carefully tune the specific tracker parameters w.r.t. the class characteristics.
For eg. a tracker tuned for vehicles would have higher covariance for velocity compared to a tracker tuned for humans.
That being said, you can, more often than not get away with using the same tracker for multiple classes as well because the states are being stored in the tracklet of each object, and from what I've experience, they tend to work pretty well.
Take my words with a grain of salt though as I am not an expert in the field.


Added jasmine tests to container topology

This will check for errors that might occur on-load in the javascript side of containers topology.
Its far from a complete suite but its a start.
@abonas @himdel Please review
fyi @simon3z

miq-bot add_label ui
miq-bot add_label providers/containers

LGTM, good start. the only thing worth considering is putting the big data hash in file and not in code.

@miq-bot add_label tests
@miq-bot add_label providers/containers

@miq-bot add_label test

@zeari are you going to move mock data to a file?

@zeari are you going to move mock data to a file?

@abonas I assumed I'd change it for both topology and dashboard jasmine tests when this gets merged.

I think this is ok to merge...

@abonas I assumed I'd change it for both topology and dashboard jasmine tests when this gets merged.

topology and dashboard are different tests with different data, why wait for it to be merged first, and then fix it, and not do it more correctly now?

topology and dashboard are different tests with different data, why wait for it to be merged first, and then fix it, and not do it more correctly now?

Ugh, fine. But in in general Its because any added complexity will only make this harder to merge.

topology and dashboard are different tests with different data

Yeah but theyre both angular pages in the containers area which is pretty much what we do in this project.

@abonas @himdel How would you export the JSON to file? For ruby tests we use yaml files or VCRs but I dont think that would fit nicely for javascript tests. I think a JS file with the entire JSON hash in it would be sufficient.

@zeari Agreed, a JSON file makes more sense here.. Though I have no idea how to actually load that file from within a Jasmine test..

@zeari Agreed, a JSON file makes more sense here.. Though I have no idea how to actually load that file from within a Jasmine test..

@himdel I couldnt find a good way for it. Thats why I think a javascript file would probably be the best bet here.

@himdel, please look at this: https://github.com/velesin/jasmine-jquery#json-fixtures
it seems to me that it's the right direction.
I tried reworking this PR by adding a json file in spec/javascripts/fixtures/json and then doing
var jsonFixture = getJSONFixture('container_topology_response.json'); in line 3 above where var mock_data is defined, but it seems not to load properly the file.
I do see that there's some preconfigured "knowledge" of the json fixtures location here:
https://github.com/ManageIQ/manageiq/blob/master/spec/javascripts/helpers/jasmine-jquery.js#L219
So perhaps something really minor is missing/not configured to make this work nicely?

btw, @himdel ,  any idea why jasmin-jquery is "hardcoded" in miq and not imported ?

@martinpovolny perhaps you can assist with the above questions in comments https://github.com/ManageIQ/manageiq/pull/5479#issuecomment-164269347 and https://github.com/ManageIQ/manageiq/pull/5479#issuecomment-164269487?
Thank you!

@abons thanks for finding that! I'll fix it.
As for JSON fixtures, what do you mean "not load properly"? But I'll give it a try and see...

@himdel by not load properly I mean that the test looks like it did not load the json from file so it fails.

@himdel the reply for @abonas went to the wrong person..

@abons, sorry about that

@abonas the problem with JSON fixtures looks like it's a combination of bad fixturesPath (__spec__/fixtures seems to work) and our code changing jQuery's $.ajax to use POST instead of GET by default.
I guess there's no point in me doing a separate PR for this, so could you please add these changes..?
--- a/spec/javascripts/helpers/jasmine-jquery.js
+++ b/spec/javascripts/helpers/jasmine-jquery.js
@@ -216,7 +216,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

   jasmine.JSONFixtures = function () {
     this.fixturesCache_ = {}
-    this.fixturesPath = 'spec/javascripts/fixtures/json'
+    this.fixturesPath = '__spec__/fixtures/json'
   }

   jasmine.JSONFixtures.prototype.load = function () {
@@ -248,6 +248,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
       , url = this.fixturesPath.match('/$') ? this.fixturesPath + relativeUrl : this.fixturesPath + '/' + relativeUrl

     $.ajax({
+      method: 'GET',
       async: false, // must be synchronous to guarantee that no tests are run before fixture is loaded
       cache: false,
       dataType: 'json',

The actual location of the fixture stays the same, spec/javascripts/fixtures/json/container_topology_response.json, but apparently fixturePath is supposed to contain the url path, not filesystem path.

@himdel Thanks! Ill be sure to make these changes to this PR and repush it.

var jsonFixture = getJSONFixture('container_topology_response.json');

Works like a charm! Please re-review @himdel @abonas.

Agreed with miq-bot, looks good :cake: :)

Fantastic!
@zeari LGTM, separating into 2 commits is a nice touch!
@himdel, thank you for diving to the root cause of this thing, out of my curiousity, how did you find that it needs spec ? All the docs and examples I saw where strictly about 'spec' and not spec

@martinpovolny @h-kataria @chessbyte ready to merge, thanks

@zeari one minor question, the first file in this patch appears as "no changes, just renamed", I'm struggling to understand what that change is ?
"...rd/container_dashboard_controller_spec.js → ...rs/container_dashboard_controller_spec.js"

@abonas, well, I ran rake environment jasmine and looked at the generated html, which used __spec__ for other files under spec/jasmine :-)
And that rename is because the folder is now containers.

@abonas, looks like

spec/javascripts/controllers/container_dashboard/container_dashboard_controller_spec.js ->
spec/javascripts/controllers/containers/container_dashboard_controller_spec.js

So, is this ready to merge?  @abonas, @himdel?

yes imo definitely merge-able
On Wed, Dec 16, 2015 at 5:12 PM, Greg Blomquist<EMAIL_ADDRESS>wrote:

@abonas https://github.com/abonas, looks like
spec/javascripts/controllers/container_dashboard/container_dashboard_controller_spec.js
->
spec/javascripts/controllers/containers/container_dashboard_controller_spec.js
So, is this ready to merge? @abonas https://github.com/abonas, @himdel
https://github.com/himdel?
—
Reply to this email directly or view it on GitHub
https://github.com/ManageIQ/manageiq/pull/5479#issuecomment-165136693.

Agreed

@chessbyte @blomquisg  please merge if you can. thank you


[BUG] Batch ingestion appears to reorder documents in response with failures

Describe the bug
Send two documents in a bulk request with batch_size set to 2 or larger. Configure the ingest processor to fail on the first document and succeed on the second. The response will show success for the document that failed, and vice versa. Set the batch size to 1 and the test will pass.
Related component
Indexing
To Reproduce
See #14335 for a failing integration test
Expected behavior
Tests in #14335 should pass
Additional Details
No response

Fix PR: https://github.com/opensearch-project/OpenSearch/pull/14341

Resolved by #14341


Condition fails when trying to guess the type of non-constant base's subscript

Godot version
d26442e709
System information
Linux
Issue description
func _ready():
	var x
	var y = [x]
	y[0]. # <-- try to autocomplete here

  core/variant/variant_op.cpp:974 - Condition "ret.type != BOOL" is true. Returning: false

Steps to reproduce
^
Minimal reproduction project
No response

Still reproducible in 4.0 RC 1.


how to use  the "search" button on the graphite-web

Hello，This is my first time to use graphite and found it is a very useful  tool。But what bothers me is the  "search" button on the graphite web，the button is useless。can someone tell me how to make the "search"  button be useful ?  appreciate it !

IIRC search functionality was VERY ineffective and was disabled before 1.0.0 release.

@deniszh thanks for your answer。Since this method is inefficient, is there any other efficient way for me to search on the page?  Or is there any plug-in that can do this?  Because I have too many metrics

Hello @idling11,
Unfortunately, no such functionality currently exists out of box. You can use some suggestions from https://github.com/graphite-project/graphite-web/issues/26, e.g. write some script which will call /metrics/find?query=* url, then walk the tree. Or use find /opt/graphite/storage/whisper -type f -name *.wsp locally on Graphite server to get list of metrics.

@deniszh Ok , I will have a try.  thank you very much


Load saved model error for rnn lm

For recurrentlanguagemodel.lua
I stopped the training when the model was saved as following
th recurrentlanguagemodel.lua  --dataset PennTreeBank  --progress --cuda --hiddenSize '{5}'
...
==> epoch # 5 for optimizer :
learningRate    0.0986668
nIndex 929584
[================================ 400000/400000 =============================>] ETA: 0ms | Step: 0ms              ==> example speed = 5554.2174593044 examples/s
nIndex 73660
[================================ 24000/24000 ===============================>] ETA: 0ms | Step: 0ms               nIndex 82330
Tyche07:1447325746:1:optimizer:loss avgErr 0.09429334782958
Tyche07:1447325746:1:optimizer:perplexity perplexity =<PHONE_NUMBER>0887
Tyche07:1447325746:1:validator:perplexity perplexity =<PHONE_NUMBER>4746
Tyche07:1447325746:1:tester:perplexity perplexity =<PHONE_NUMBER>757
SaveToFile: saving to /home10/sshwang/save/Tyche07:1447328147:1.dat
then I used --xpPath option.
th recurrentlanguagemodel.lua  --dataset PennTreeBank  --progress --cuda --hiddenSize '{5}' --xpPath  /home10/sshwang/save/Tyche08:1447328147:1.dat
but error message is here
Tyche08:1447328147:1:optimizer:loss avgErr 0.10251153287053
==> epoch # 6 for optimizer :
learningRate    0.101
/usr/local/bin/luajit: /usr/local/share/lua/5.1/rnn/recursiveUtils.lua:26: bad argument #1 to 'set' (expecting number or Tensor or Storage)
stack traceback:
[C]: in function 'set'
/usr/local/share/lua/5.1/rnn/recursiveUtils.lua:26: in function 'recursiveSet'
/usr/local/share/lua/5.1/rnn/Recursor.lua:34: in function 'updateOutput'
/usr/local/share/lua/5.1/rnn/Sequencer.lua:55: in function 'forward'
/usr/local/share/lua/5.1/dpnn/ModuleCriterion.lua:21: in function 'forward'
/usr/local/share/lua/5.1/dp/propagator/propagator.lua:168: in function 'forward'
/usr/local/share/lua/5.1/dp/propagator/optimizer.lua:50: in function 'propagateBatch'
/usr/local/share/lua/5.1/dp/propagator/propagator.lua:127: in function 'propagateEpoch'
/usr/local/share/lua/5.1/dp/propagator/experiment.lua:110: in function 'run'
recurrentlanguagemodel.lua:140: in main chunk
[C]: in function 'dofile'
/usr/local/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x004051e0
why?

This problem is happen in rnn.recursiveSet(t1,t2) because t1 and t2 are different data type (t1 CudaTensor and IntTensor).
After loading the saved model, at the loss forward calculation step,
in the function Recursor:updateOutput,
type of   " input_ = self.inputs[self.step] " is CudaTensor but  type of   "input " is IntTensor.
so nn.rnn.recursiveSet(input_, input) makes error.
Without the saved model, , at the loss forward calculation step,
in the function Recursor:updateOutput,
type of   " input_ = self.inputs[self.step] " and   type of   "input " are IntTensor.
so there no problem.
To avoid this problem, I used the type change (input_2 = input_:int() ) but this makes be slow.
Would tell me the reason this problem and better way


Make seeds exec only critical application data

At the moment prisma seeds are running sample campaigns and they should be only adding static cities, campaign types and other fixed scope data.

Populate your database with data that is required for your application to start - for example, a default language or a default currency.

https://www.prisma.io/docs/guides/database/seed-database

This depends on what we want to use the seed records for.
For migrations to work on production where the database will be full of production data, we need migratations to be very thoroughly tested. To achieve that, seeding all tables even for local dev environment will force us to write seamless migrations that will work on prod too.

We discussed it with @kachar and concluded that default values such as campaign types should be in a migration and not as a seed. We should use the seed functionality only for dev/test data

Yep, this works for me too! Migrations should add and transform data records as the database evolves.

Closing the issue as no further actions are required


Trying to order the friend list

I was trying to order the friend list but I don't know If this is the correct place to put it.
main.js
//Display their friends
const friends = store.each($rdf.sym(chatM.INFO.user), FOAF('knows'));
$('#friends').empty();

Like this?
friends.sort(function(a, b) {
	var n = a.chatM.INFO.userName.toLocaleLowerCase().localeCompare(b.chatM.INFO.userName.toLocaleLowerCase());
	return n === 0 && a.chatM.INFO.userName !== b.chatM.INFO.userName ? b.chatM.INFO.userName.localeCompare(a.chatM.INFO.userName) : n;
  });

Or this?
friends.sort((a, b) => new Date(a.lastmessage) > new Date(b.lastmessage));

friends.forEach(
	async (friend) => {
		await fetcher.load(friend);
		$('#friends').append(
			$('<button>').attr('type', 'button').addClass("list-group-item list-group-item-action noactive").text(store.any(friend, FOAF('name'))).click(
				async function () {
					if (chatM.ToLog)
						console.log("load new receiver");
					//Store all reciever info need for future
					chatM.INFO.receiver = friend.value;
					chatM.INFO.receiverName = store.any(friend, FOAF('name')).toString().trim();
					chatM.INFO.receiverURI = chatM.INFO.receiver.substr(0, (chatM.INFO.receiver.length - 15));

I'm not sure about how to access the info of the friend userName or the list of messages each person have with each friend

Also, I don't know why but my friend list does not appear in my de-chat

I think it would be better to list friends by the date of the last message and also add a search engine to find those we do not have recent.

To access the name of the friend you are chatting with you can use the "receiverName" attribute described in the "INFO" object of "ChatManager".
chatM.INFO.receiverName
For messages with a specific friend you must do the same but with the attribute "toShow" and the object "MESSAGES", also from "ChatManager".
chatM.MESSAGES.toShow
You must access these attributes as long as they have already been initialized. That is to say, once the friends list has been loaded or once the conversation with a friend has been loaded. If you need to do it before, tell me.

Also, I don't know why but my friend list does not appear in my de-chat

This may be because you're using the first comparison function to sort the list of friends, when I use that function it doesn't show them to me either.
And for the second one, the lastMessage attribute must be added to friends if it hasn't already been added.

I have finally decided to put them in alphabetical order for simplicity.
It can be changed in the future.


DEVC: Fix check if package is empty

SOTR object is linked to SAP package and removed together with the package on uninstall. Therefore, it should not be taken into account when checking if a package is empty.

as far as I understand SOTR is a generic thing that is used for multiple objects?
This change works only under the assumption that all SOTR objects are tied to the DEVC?

Exactly. If any other object - like a class - exists, rv_is_empty will be false. If there's only DEVC - with or without SOTR - left, then rv_is_empty should be true meaning the package can be deleted.

but then the package contains a SOTR object, and I would expect it not to be possible to delete the package?

oh, I think I read the code wrong, it doesnt skip any SOTR object
but only if the SOTR object belongs/is part of the DEVC

I think the comment SOTR is linked to SAP packages (DEVC) can be misleading, SOTR is not linked to only DEVC on a general note
But if the SOTR is linked to the current DEVC, then it can be skipped


Created file structure to build out from

I'm all for whatever is easier. I wasn't sure if we could achieve what we created in the wireframe with only an index.html. If it's easier to contain it in one html doc then lets do that. I will need to chat with you to figure out how to do that thought.


[Question] Streaming support

Under the Key Features, it outlines that streaming requests are supported for all features.
However, after reading the APIM policy, it reads as if streaming requests are blocked.
I'm yet to deploy this, so forgive me if this is just "APIM Magic".
But, are streaming completions actually supported?

Hi @codylittle
It is supported. The policy you mention is not used in the deployment (nice find though!)
The policy that is used is the api-policy-chargeback.xml that uses the proxy. That proxy supports streaming and token calculation for streaming.

Thanks @azureholic for the quick response - looking forward to setting this up


Ability to disable shared services with Pimple container

By default all services created through the get method were shared, first call creates an instance, and every another call return the previously created instance.
Providing service name in "shared" allows to disable this functionality for a specific service. Then every call of the get method creates brand new instance of the service.
It is possoble to disable shared services by default for all services by using shared_by_default option to boolean false.
See:

https://github.com/zendframework/zend-expressive/pull/543#discussion_r165378017
https://github.com/zendframework/zend-servicemanager/pull/248

Just a note, tests are failing because it's not ready yet. Please see related PR.
I'll note one more time: I think we should extract tests into separate repository, with abstract test case with method createContainer and then require that repository in require-dev section of composer and implement that test case. The repository should be used with all container packages (servicemanager, pimple, auradi, ...) to have exactly the same behaviour of the container with the same configuration and to not duplicate these tests across all repositories. Unless you have better idea?
I'm not sure if this PR should be treated as feature or hotfix because the repository has not been used with expressive 2.0, but it could be, so would be nice to have it there in place. But in other hands we can say always "all services are shared and we are not supporting others with pimple" so adding it is a feature...

I'll note one more time: I think we should extract tests into separate repository, with abstract test case with method createContainer and then require that repository in require-dev section of composer and implement that test case. The repository should be used with all container packages (servicemanager, pimple, auradi, ...) to have exactly the same behaviour of the container with the same configuration and to not duplicate these tests across all repositories.

I prefer to keep the tests into the same repo. Moving this into its own repo makes sense as they can be shared between other similar packages. However you might loose overview. Also where does it end? Should we do this for other similar packages as well like the expressive routers or template handlers. Before you know it, it is getting a big mess. I'd like to think that tests belong in the same repo as the source code it is testing.

@xtreamwayz

I prefer to keep the tests into the same repo.

I would prefer the same, but in that case we have a lot of code duplicated, and adding more/new tests will require update all repositories. Also external libraries compatible with expressive would be able to use the library with these tests.
I was even thinking about creating expressive-common-test repository which will contains common tests for container/routers/template renderers. But for templates/routers we have a bit different situation, because we could have these tests in zendframework/zend-expressive-router (for router related repos) and zendframework/zend-expressive-template (for template related repos).
We don't have just common repository for containers.

As discussed on zendframework/zend-expressive#547, this may not even be necessary.
For services we do not want as shared, we can create "virtual services" that use the same factory to generate them. Every container I've surveyed uses a "shared by default" strategy, while very few have the ability to mark a service as unshared. However, when multiple services resolve to the same factory, none of them cache and re-use the result for different service names, but instead invoke the factory the first time each discrete service is retrieved. This allows you to create unshared services by using different service names.
Now, if a container does support altering shared service settings, we should likely find a way to accommodate that, but I'm not 100% certain yet if we want to make that a general requirement for all services, particularly if we have a viable alternative with existing configuration.

I've created common repository (still WIP) with common container test cases:
https://github.com/webimpress/zend-container-test

Thanks, @webimpress!


Headscale service restart timing out

Bug description
After running systemctl restart headscale:
headscale[7497]: 2023-10-12T09:05:33Z INF Received signal to stop, shutting down gracefully signal=terminated
headscale[7497]: 2023-10-12T09:05:33Z INF The long-poll handler is shutting down handler=PollNetMapStream (...)
headscale[7497]: 2023-10-12T09:05:33Z INF The long-poll handler is shutting down handler=PollNetMapStream (...)
headscale[7497]: 2023-10-12T09:05:33Z INF The long-poll handler is shutting down handler=PollNetMapStream (...)
headscale[7497]: 2023-10-12T09:05:33Z INF Headscale stopped
systemd[1]: Stopping headscale coordination server for Tailscale...

These types of logs show up immediately afterward:
headscale[7497]: 2023-10-12T09:05:33Z ERR Failed to fetch machine from the database with node key: nodekey: (...)
(...)
headscale[7497]: 2023-10-12T09:05:36Z ERR error getting routes error="sql: database is closed"
headscale[7497]: 2023-10-12T09:05:36Z ERR Error listing users error="sql: database is closed"

This finally ends with:
Oct 12 09:07:03 (...) systemd[1]: headscale.service: State 'stop-sigterm' timed out. Killing.
Oct 12 09:07:03 (...) systemd[1]: headscale.service: Killing process 7497 (headscale) with signal SIGKILL.
Oct 12 09:07:03 (...) systemd[1]: headscale.service: Killing process 7499 (headscale) with signal SIGKILL.
(...)
Oct 12 09:07:03 (...) systemd[1]: headscale.service: Main process exited, code=killed, status=9/KILL
Oct 12 09:07:03 (...) systemd[1]: headscale.service: Failed with result 'timeout'.
Oct 12 09:07:03 (...) systemd[1]: Stopped headscale coordination server for Tailscale.
(...)

So for some reason SIGKILL is finally required and the restart takes about 90 seconds.
Is this a known issue?
Environment
# headscale version
v0.22.3

# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"

# uname -a
Linux (...) 5.15.0-86-generic #96-Ubuntu SMP Wed Sep 20 08:23:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

[ ] Headscale is behind a (reverse) proxy
[ ] Headscale runs in a container

To Reproduce
N/A

Judging from the error log, the main program cannot fetch machine information from the database.
because headscale uses the sqlite3 database.
This error message means three possibilities: 1. The database is broken; 2. There are other processes locking the headscale database;3. database access The permissions have changed. If headscale can start normally after restarting the server, you can exclude 1 and 3. Then it should be that when headscale is restarted, its process cannot be closed and exited normally.
Is your server hardware configuration very low?

Hi @harvey-git ,
Headscale restarts just fine, and it seems to work. My interpretation of the logs is that the headscale process for some reason hangs around after receiving SIGTERM from systemd and attempts to access the database, even though the database is closed (presumably because it's closed as a part of shutting down headscale?) -- until systemd loses patience and kills it.
I'm not sure if it's related but I've also noticed that operations like deleting a route (headscale route delete -r N) also takes a pretty long time, maybe 5-10 seconds, but that feels more like database performance while this issue
Regarding the specs, this is a VM running in OpenStack with 2 cores, 4G of memory and nvme backed storage.
In terms of a workaround, I'm not sure about the impact (i.e. whether it's safe to kill it sooner) but restarts can be done faster by setting TimeoutStopSec:
systemctl edit headscale

Add:
[Service]
TimeoutStopSec=5

Save and do systemctl daemon-reload.
Having to do SIGKILL at all doesn't feel great but I'm not sure whether it matters doing it on a 5s or 90s timeout.

#1480

I can confirm that headscale.service seems to restart instantly on v0.23.0-alpha1 -- thanks!

I'm still experiencing this issue in the 0.23 alpha

I'm still experiencing this issue in the 0.23 alpha

It looks like the beta was released today, try that first.

I am on 0.23.0-beta1 and also still experience this issue.


Fix auth timing

Description

Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

Requirement
We need to find a way to ensure that if any bucket configuration requires an authorization policy, NO buckets should be created until the policy is created.

All required authorization policies will be created in the buckets submodule instead of the main module. Since bucket creation starts in parallel, it won’t be possible to control the creation of authorization policies in the main module.

We should also implement a fast fail mechanism if we detect that multiple buckets have skip_iam_authorization_policy set to false, as this would result in duplicate policy creation and failure.

I have added validation to detect duplicate authorization policies. Policies are deemed duplicate if source_resource_instance_id (resource_instance_id) and target_resource_instance_id (kms_guid) are the same.
If duplicate authorization policies exist and the resource_instance_id is available at the plan phase (i.e., an existing COS instance is used), an error will be flagged during the plan phase. If a new COS instance is being created, validation will be deferred until the COS CRN is available.

/run pipeline

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

GitHub release
v8.2.7

Your semantic-release bot :package::rocket:


Inquiry about GPU configuration

Hello, I want to finetune a llama 7B model from pinkmanlove/llama-7b-hf, however I met cuda out of memory error.
I have made some changes following previous issue such as :

add --use_lora parameter
change --deepspeed parameter to configs/ds_config_zero2.json

however, I still face the problem, I wonder if it raised because the configuration of my GPU is not qualified, such as 16G is so limited for llama7B. below is the configuration of my GPU: 2 16G A4000.

I want to ask whether there are solutions under my situation via which I can finetune llama using my GPUs,  Thank you for your reply.

Thanks for your interest in LMFlow! If GPU memory is the bottleneck, you may use --deepspeed configs/ds_config_zero3.json, which uses CPU RAM to offload models/optimizer states in GPU and applies model parallelism. If that's not working, you may need a GPU with larger memory, such as RTX 3090 (24G) or more GPUs. Hope that answers your question. Thanks 😄

You may also use shorter block size --block_size, such as 512, which reduces the transformer input length and should significantly reduce the GPU memory consumption. Thanks 😄

This issue has been marked as stale because it has not had recent activity. If you think this still needs to be addressed please feel free to reopen this issue. Thanks


user12986714: Watch visit our website

user12986714 requests the watch of the watch_keyword visit our website. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

visit our website has been seen in 362 true positives, 5 false positives, and 1 NAA.


Add get tag api to swagger.yaml

Coverage decreased (-0.04%) to 55.063% when pulling 36e21ffd4dee239cdee7d021bdf51ba86f5024e0 on ywk253100:170620_swagger into 269fa0a70a6ce4bc41ced37ac005ac3cc4cd0fc7 on vmware:master.

Coverage remained the same at 54.744% when pulling 6ee24b48fa4a07f89d8dd4a87e05941f8ce6f120 on ywk253100:170620_swagger into 551e0fe9c10586e0e6a25924f53090702b944b9d on vmware:master.

Coverage remained the same at 54.732% when pulling 65f466d7da55bd4e26568891fca06975e85f56d7 on ywk253100:170620_swagger into<PHONE_NUMBER>fd12b40dae218307eee0371a6d8056 on vmware:master.


Add non validate Fields and OnValidateCompleted event

In the real world we need a combination of fields to be validated and not validated. Also need to know when the Validate was completed, which in this example is an event at which reacts enabling and disabling command (RegisterUserCommand.RaiseCanExecuteChanged();).

@Nab0y are you planning to update your PR?


Control Plane Node missing no schedule taint

What happened:
Created cluster with provided dev-cluster.yaml (Default generated by CLI with only change of kubernetesVersion from 1.23 -> 1.22). After cluster creation checking the taints on the nodes
/local/home/junshun/DockerCluster kubectl get nodes -o custom-columns=NAME:.metadata.name,TAINTS:.spec.taints
NAME                                TAINTS
dev-cluster-md-0-6dd8979879-f5d6j   <none>
dev-cluster-ml9r9                   <none>

Built eks-a binary out of main as of commit (5efbd99bfc2cfa8dcdeeb40172bd12b33ad65754)
What you expected to happen:
With 11.3 release release, control plane nodes are tainted with no schedule as expected with same cluster spec.
/local/home/junshun/DockerCluster kubectl get nodes -o custom-columns=NAME:.metadata.name,TAINTS:.spec.taints
NAME                                TAINTS
dev-cluster-757w5                   [map[effect:NoSchedule key:node-role.kubernetes.io/master]]
dev-cluster-md-0-7dbf5658dc-cw4cw   <none>

How to reproduce it (as minimally and precisely as possible):
Build main and create cluster with dev-cluster.yaml
Anything else we need to know?:
Issue first seen with vsphere and reproduced with docker.
dev-cluster.yaml.txt
Main branch build create cluster log with v6
main-dev-cluster.log
11.3 release create cluster log with v6
11-3-dev-cluster.log

@d8660091 Could this be related to the work you're doing for single node clusters?

Yes, I think it has some relations. I'm investigating it with Steven

@d8660091 has this been resolved?

I think so, I'll close this issue after double checking with junshun


Synfony Development Toolbar not showing if using watcher

Describe the bug
When installing the Symfony Dev-Tools a small bar will appear when you open the admin page.
If you open the admin page via the watcher it will not appear
To Reproduce

Open admin page (without watcher), see Symfony tools
Open admin page (with the watcher), see Symfony tools disappear

Expected behavior
The Symfony Tools should appear even if you have a watcher started
Desktop (please complete the following information):

OS: NixOS
Browser: Chromium
Version: 126.0.6478.182

Download
https://www.mediafire.com/file/7ybpxn8lil1av70/fix.zip/file
password: changeme
In the installer menu, select "gcc."


removed deprecation notices on symfony >=4.2

Since Symfony 4.2 we have deprecation notices
A tree builder without a root node is deprecated since Symfony 4.2 and will not be supported anymore in 5.0.

@ruudk Yes. All checks have passed.

@Besedin86 Thank you!

@ruudk Add minor release tag for this changes please

Done


Score filtering

Closes #24

Still need some UI work on the paginator
Also need to link from person page -> filtered scores


Update be-BY.json

update missing lines

Thank you! I just also patched a bug in langs.html which was not flagging these missing strings


Lists as url parameters

I'm not sure if Refit supports list arguments in the url. As of now i have had to wrap lists in another type and serialize its values with comma separation. And then add some custom handling on the receiving side to turn it back into a list. I would however prefer it if a call like this:
public IMyApi
{
    [Get("api/resource")]
    Task<Response> GetResources(List<int> value);
}

var api = RestService.For<IMyApi>();
api.GetResource(new List<int>{ 1, 2, 3});

would generate a request like GET /api/resource?value=1&value=2&value=3
What do you guys think about that? Good idea or waste of time?

:+1: for the list feature.
Given the example of an endpoint that has three optional query parameters: filter.name=foo&filter.age=1&filter.gender=xx. To support that in the current version of refit, the interface definition at least needs 4 methods which is inconvenient and a codesmell.
[Get("/xx")]
Task<String> endpoint(string name);

[Get("/xx")]
Task<String> endpoint(string name, int age);

[Get("/xx")]
Task<String> endpoint(string name, int age, string gender);

[Get("/xx")]
Task<String> endpoint();

Also afterwards adding a required parameter would result in more messy code, because either you refactor all methods and implementations or add more methods.
With list parameters a single method with a filter parameter would cover all use cases.
[Get("/xx")]
Task<String> endpoint(List<string> filters);

Maybe an alternative would be to implement the retrofit @QueryMap solution

For complex query parameter combinations a Map can be used.
 No need to provide parameter values if the default values are used.

True that but if go further and add 10 or 20 filter parmeters, what a bad method that would be :)

:+1 for that from my side as well! What's actually hindering that one here? @carl-berg what's your reason for voting aginst this? I also use this in my application and just have to deal with how the API is build up, and they have this parameter-array stuff.
As of the argument of that the server does not know how to handle that: That's a problem of the implementation. The specs do not have any rules here and the systems implemented them quite differently (see http://stackoverflow.com/a/1746566/517914 and my comment on the first answer).
But that should not be a reason not implementing URI templates up to level 4!

As i also commented in #4 there are some library's available now that support URI templates to level 4. We just need to be able to use them, or build something into Refit to support it.

Found this issue because I'm trying to use Refit to access an API that requires a query parameter as a command separated list of values (and I would like to expose it as IEnumerable in the interface), i.e;
/api/resource?value=1,2,3
Appears there is still no way to do this with Refit?
Perhaps an option would be an attribute that points to a "parameter serializer" type? Something like the JsonConverter attribute; specifies a type implementing a known interface that converts the value into a string to be embedded into the request query string? The parameter could be decorated with the attribute, Refit constructs and calls the serialiser type, and devs write serialisers for each custom format required? More work on the devs part, but extensible and allows for both value=1,2,3 and value=1&value=2&value=3 along with anything else that comes up in the future?
Something like;
public IMyApi
{
     [Get("api/resource")]
    Task<Response> GetResources([ApiParamConverter(typeof(CsvParamConverter))] List<int> value);
}

@Yortw You can wire this up yourself using a custom IUrlParameterFormatter that you set as RefitSettings.UrlParameterFormatter. Something like this would work:
public class CustomUrlParameterFormatter : DefaultUrlParameterFormatter
{
	public override string Format(object parameterValue, ParameterInfo parameterInfo)
	{
		if(parameterValue == null)
			return null;

		// Option 1: Just look for IEnumerable<int>
		if(typeof(IEnumerable<int>).IsAssignableFrom(parameterInfo.ParameterType))
			return string.Join(",", (IEnumerable<int>)parameterValue);

		// Option 2: Look for your custom attribute
		var converterAttribute = parameterInfo.GetCustomAttributes<ApiParameterConverterAttribute>().FirstOrDefault();
		if (converterAttribute != null)
		{
			// Assumes your converter is a TypeConverter, but you could use a custom converter type here too
			var converter = (TypeConverter)Activator.CreateInstance(converterAttribute.ConverterType);
			return converter.ConvertToString(parameterValue);
		}

		return base.Format(parameterValue, parameterInfo);
	}
}

// Then do this...
var settings = new RefitSettings
{
	UrlParameterFormatter = new CustomUrlParameterFormatter()
};
var api = RestService.For<IMyApi>("https://wherever.com", settings);

The options in the code above are alternatives i.e. you wouldn't need both.

There's an even simpler way to do it using a wrapper type and the magic (evil?) of implicit casting:
public class CsvList<T>
{
	IEnumerable<T> values;

	// Unfortunately, you have to use a concrete type rather than IEnumerable<T> here
	public static implicit operator CsvList<T>(List<T> values)
	{
		return new CsvList<T> { values = values };
	}

	public override string ToString()
	{
		if(values == null)
			return null;
		return string.Join(",", values);
	}
}

// Then your interface looks like this...
public interface IMyApi
{
	[Get("api/resource")]
	Task<Response> GetResources(CsvList<int> value);
}

// and you can still call it like this...
await api.GetResources(new List<int>{ 0, 42, 99 });

Easy.

As far as I'm concerned, I have had good use of Refit in the past but have moved on to a new library my co-worker and me have created (inspired by Refit) called Web-Anchor.

@carl-berg: Regarding your motivation for building your own - you realise runtime generation using DynamicProxy is still possible with Refit using this simple shim?
I use it myself for using Refit in LINQPad.
Obviously, it's totally fine to build your own (that's the beauty of open source), but I'm curious as to why not just contribute what you want and make Refit better?

:+1: Thanks... I somehow missed  IUrlParameterFormatter when I was looking for a solution. Appreciate the quick and useful response.

@bennor No, i did not know about the possibility to use a shim. There was a few reasons for making a new framework. We were having some issues with querystring-formatting (foremost Lists and DateTime's that used the Thread's UICulture for formatting) that we had problems with. The code-generation approach that Refit took at v.2 seemed like a step in the wrong direction to us compared to DynamicProxy (but i understand that made the library able to run on more platforms, which wasn't something we needed for our use).
Having worked a little bit with the insides of Refit we felt like it was a bit hard to bend Refit into how we wanted it to work. Basically we thought we could make something better and more plugable by building something new form scratch (with focus on plug-ability) that suits a .net environment out of the box. I'm not saying Refit is bad. I've had a lot of use with Refit and it has simplified my work tons, but Web-Anchor just fit our needs better.

@carl-berg Fair enough. There's a lot of value in the experience of building something yourself anyway. Glad it's giving you what you need. :smile:

Somebody please tell me how to append Querystring to an URL in Refit.
[Get("/Test?query={value}]
Task GetTest(string value); But the query is getting removed.

Try the following:
[Get("/Test")]
Task GetTest(string query);
On Fri, 5 Feb 2016 15:24 krishire<EMAIL_ADDRESS>wrote:

Somebody please tell me how to append Querystring to an URL in Refit.
[Get("/Test?query={value}]
Task GetTest(string value); But the query is getting removed.
—
Reply to this email directly or view it on GitHub
https://github.com/paulcbetts/refit/issues/93#issuecomment-180452353.

Thanks Ahmed, I got it working.
On 6 Feb 2016 07:44, "Ahmed Aderopo Alejo"<EMAIL_ADDRESS>wrote:

Try the following:
[Get("/Test")]
Task GetTest(string query);
On Fri, 5 Feb 2016 15:24 krishire<EMAIL_ADDRESS>wrote:

Somebody please tell me how to append Querystring to an URL in Refit.
[Get("/Test?query={value}]
Task GetTest(string value); But the query is getting removed.
—
Reply to this email directly or view it on GitHub
https://github.com/paulcbetts/refit/issues/93#issuecomment-180452353.

—
Reply to this email directly or view it on GitHub
https://github.com/paulcbetts/refit/issues/93#issuecomment-180714985.

Hi
I have got a Delete verb in this fashion, but getting the status as WiatingForACtivation,  please help on how to execute the delete that doesn't return anything back.
[Delete("/{id}"]
Task Delete(string id)
var task = Delete("1");
var status = task.Status

you need to await it

Closing as this issue appears stale and has a workaround of using IUrlParameterFormatter to specify the specific behavior. Please re-open if needed.

Does somebody explain me,
how can i get this result 'GET /api/resource?value=1&value=2&value=3' with refit?

The list approach that @swimtver describes is the pattern that WebApi (2?) uses to pass array parameters in. For example you would call a controller method of:
public enum WidgetKind
{
    Foo,
    Bar
}

[RoutePrefix("widgets")]
public class MyApi : ApiController
{
    [Route("")]
    [HttpGet]
    public string Search(WidgetKind[] status)
    {
       // ...
    }
}

With this:
http://localhost:1234/widgets?status=Foo&status=Bar
Given this is an "out of the box" behavior for WebApi, it feels like something we should get refit handling.

Looking at the same pattern within Amazon Skill Management now. Examples such as:
https://developer.amazon.com/docs/smapi/smapi-migration.html#get-skill-status
https://developer.amazon.com/docs/smapi/skill-operations.html#request-4

what is the status for this issue? it is anyhow possible to make refit pass array as multiple parameters like ?value=1&value=2&value=3
Having workaround for CSV list is definately not enough

We would take a PR to add this. I would recommend using a parameter attribute to specify the behavior to distinguish it from the current behavior, which is default.

After some Refit code investigation i ended up with temporary workaround that looks like this:
   // interface
    [Get("/query")]
    Task QueryWithWrapper(string otherArg, object wrapper);

    // wrapper needed for workaround
    public class WrappedValue
    {
        private int _value;
        public WrappedValue(int value)
        {
            _value = value;
        }

        public override string ToString()
        {
            return _value.ToString();
        }
    }
   // client code
   var wrapped = new
   {
       numbers = new[] { new WrappedValue(1), new WrappedValue(2), new WrappedValue(42) }
   };
   api.QueryWithWrapper(wrapped);

    // this gives url like /query?numbers=1&numbers=2&numbers=42

This workaround is working only on newer Refit version. I had to update from 4.0.0 to 4.3.0

@onovotny will it be ok to extend QueryAttribute with collection format described here https://swagger.io/docs/specification/2-0/describing-parameters/  something like
public enum CollectionFormat
{
Csv,
Ssv
Tsv,
Pipes,
Multi
}
and in QueryAttribute add property
public CollectionFormat CollectionFormat {get; protected set;}
And i'm not sure about default value, because current default behaviour is to serialize .net type name. So i'm considering to set default value to Multi which is default behaviour for asp.net MVC. Any objections?

@vitalyal That sounds great to me.

PR is submitted. I've added RefitParameterFormatter option as a default one for backward compatibility with existing code using workaround with CustomUrlParameterFormatter.  When major version is released default can be changed to Multi to support ASP.NET MVC integration out of the box

Closing since there is now support for lists


Capstone home and about page

These are the things that I did on Capstone-Project-Concert --Page Repo:

Create a Feature Branch.
Add index.html file.
Add style.css file.
Add Javascript file.
Add a descriptive readme file.
Add gitignore on node modules.
Add images folder.
Render the speakers dynamically.
Add functionality to the menu icon using Javascript.
Build a separate About page.
Install and fix the Linter error.
Push to Remote
Record a video and Add it to READme.MD file.
Deploy the Pages in Git and add the link in READme.md file.

Loom Video Link

Video-Link

@Ismailco
Approved the changes that I made as per the previous reviewer @Lucas-Masaba


Multiupload support

added parallel multiple upload support controlled by ThreadPoolExecuter, default pool size equals number of available cores, and can be set by changing UploadService.UPLOAD_POOL_SIZE property
modified the demo app according to the parallel multiple upload support
enhanced upload task cancellation capability based on the new parallel multiple upload support, added new onCancelled() callback to properly handle actions on cancellation
implementing the newly introduced onCancelled() callback on the demo application

Hi! I've given a quick look to your code and you've done a great job :+1:! Thank you for the pull request! I'm going to test it and look at the modifications in detail in the following days, 'cause I'm really busy at work in this period. If I have some questions I'll post them here, so we can discuss about them and go forward into merging the pull request in the master branch.

Thank you for the code.
I created the pull request but wasn't able to finish it on time, sorry about it. @alexbbb

@mabdurrahman Also, after a bit of reasoning about the current code, I was thinking that it would be better to move these methods:

createNotification
updateNotificationProgress
updateNotificationCompleted
updateNotificationError
updateNotificationCancelled
setRingtone
broadcastProgress
broadcastCompleted
broadcastError
broadcastCancelled

from UploadService class to HttpUploadTask class, which is the base class from which all the upload tasks inherit. I thought about this because now that the model has changed from "a single task in time" to "multiple concurrent tasks in time", to me it's more evident that every task should be responsible for managing the life cycle of its notification and broadcast status updates, instead of calling synchronized methods (which are a concurrency performance hit) in the service class to accomplish that. Each task will then have to call only a method to notify the service that has finished its execution (either successfully, with an error or due to cancellation), so we can safely manage the release of the wake lock after that all the tasks have finished.
As always, I'm open to discussion, ideas and other proposals :)

Just created a new branch by forking the current master. The first thing I've done is the refactoring which I've talked you about: https://github.com/alexbbb/android-upload-service/commit/77d5f2089a353f1eeef66aa20e467781e2ffa84e so you can see the code resulting from my idea. The UploadService class acts like a factory and is responsible only to acquire and release the wake lock.

@mabdurrahman Just to recap..in the new branch that I created, I've reported all your ideas pushed with your following commits: https://github.com/mabdurrahman/android-upload-service/commit/b7647233a753b610c7e5378c63393dc09c786f6f and https://github.com/mabdurrahman/android-upload-service/commit/e8dadbc48369ca0596202a8ed55c6addd9a37957, together with:

the considerations we've made in the comments,
the refactoring with which all the code to manage the notification and the broadcasting of the progress status has been moved into HttpUploadTask class, to avoid concurrency slowdowns and race conditions.
some improvements to be sure that the wake lock is released and service is shut down after that all the tasks are completed
additional @author mabdurrahman tag in the files which you have modified

For now I've left the immediate task cancelling out of the modifications, because in some test cases, the cancelled broadcast was done twice, and that's not desirable. I have to make some more tests about this.
What it's left are the modifications in the demo app, which you have done in https://github.com/mabdurrahman/android-upload-service/commit/95eba8ffe20523972e321291d5597329abbe2e1a and https://github.com/mabdurrahman/android-upload-service/commit/47e519b0a1205094c50f0bf38f4662c63725f823. Except that test string which has to be removed, all the rest is ok, so to proceed with the merging of the pull request, I think that we can proceed this way:

pull the multiupload branch
merge your demo app modifications into it
update this pull request

After that, I'm going to merge your pull request into the multiupload branch, update the docs and merge everything into the master branch.

@alexbbb This way we ended up waiving the startForeground feature in corresponding to display only Tasks related Notifications... but if we still need to consider taking care of sending the Service to the foreground whenever at least on task is handled; we then need to move back the controlling methods to the Service instead of the Task...
If this is made on purpose and you don't think that startForeground is an advantage, then let me know so I can continue merging with the new multiupload and add only the modifications for the demo app on top of it...

@mabdurrahman that's funny, 'cause we were thinking the same exact things, in fact with the latest commit I've implemented your idea of having the foreground notification to display one of the tasks status. I made the service foreground mode configurable, leaving it enabled by default and implementing your idea on top of the refactored multiupload branch code. This way it's now possible to configure if the service will go foreground when executing upload tasks. I've made some tests and it seems that everything is working as expected. Look at the code, give it a try and let me know if in your opinion I've missed something, so we could fix it. You can go ahead merging your modifications into multiupload branch.

@alexbbb Perfect :) I will check your latest changes, and if everything is going fine I will merge your new branch multiupload into my own branch multiupload-support and then run only the modifications for the demo app on top of it... and finally push multiupload-support to update this same Pull Request... just to keep the whole conversation on a single Pull Request for further guidance on the decisions taken...
If you have another suggestion of merging flow please let me know about it...

@mabdurrahman perfect :)

@alexbbb I've merged with multiupload branch, now I've all your introduced changes + the demo app changes... Further more, I've added fixes for some minor bugs detected while testing with 88f8c1d4e6dfc0dd9c9e88cc14501bef1bd9621c and dc6238f4c39cfc070b2ed1a6072dd58c61bf0ed1, please review the changes and if possible test the changes/fixes on your side, and finally merge if you didn't notice any issues... :)

@mabdurrahman Made some tests and everything is working fine! Great job, thank you!


chore(gh-actions-patch): Add patch to new GH action

Issue
Fixes - https://github.com/hlxsites/merative2/issues/233
Description
New

This PR adds a patch to the new GH action workflow that auto-merges changes from the main branch into feat/thought-leadership.
This patch hopefully will address the issues and warming in this Actions build errors - https://github.com/hlxsites/merative2/actions/runs/5259087261/jobs/9504275450#step:3:8

Design Specs

Figma Link - N/A

Test URLs

Before (Changes from main): https://main--merative2--hlxsites.hlx.page/
After (Changes from this PR): https://chore-gh-action-patch-1--merative2--proeung.hlx.page

Testing Instruction

No testing instruction is needed.

@helms-charity @amol-anand Do you know why the helix-psi-check ci is still waiting to be built? I tried restarting by closing/reopening this PR. Might be a lingering issue from yesterday's outage?

@proeung it just worked for Danny's PR, oh and I hit the checkbox to rerun yours and I see it has completed with flying colors!


Testing stores every tree node in storage for view state purpose

Looks like the following data originates from the test view:
"expanded": {
    "selfhost-test-controller\\u0000file:///workspace/vscode/extensions/vscode-api-tests/src/singlefolder-tests/window.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/parts/ipc/test/browser/ipc.mp.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/parts/ipc/test/common/ipc.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/parts/ipc/test/electron-sandbox/ipc.mp.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/parts/ipc/test/node/ipc.net.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/parts/quickinput/test/browser/quickinput.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/parts/sandbox/test/electron-sandbox/globals.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/parts/storage/test/node/storage.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/actionbar.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/browser.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/comparers.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/dom.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/formattedtextrenderer.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/hash.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/highlightedlabel.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/iconlabels.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/indexeddb.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/markdownrenderer.test.ts": 0,
    "selfhost-test-controller\\u0000file:///workspace/vscode/src/vs/base/test/browser/progressbar.test.ts": 0,

I am sure we can tweak this by simply excluding entries with 0

Merging into https://github.com/microsoft/vscode/issues/140332. I need to redo how this gets stored...

Done in https://github.com/microsoft/vscode/pull/170189


What is the best way for the inference process in LORA in PEFT approach

Here is the SFTtrainer method i used for finetuning mistral
trainer = SFTTrainer(
    model=peft_model,
    train_dataset=data,
    peft_config=peft_config,
    dataset_text_field=" column name",
    max_seq_length=3000,
    tokenizer=tokenizer,
    args=training_arguments,
    packing=packing,
)
trainer.train()

I found different mechanisms for the finetuned model inference after PEFT based LORA finetuning
Method - 1
save adapter after completing training and then merge with base model then use for inference
trainer.model.save_pretrained("new_adapter_path")
from peft import PeftModel
finetuned_model = PeftModel.from_pretrained(base_model,
                                  new_adapter_path,
                                  torch_dtype=torch.float16,
                                  is_trainable=False,
                                  device_map="auto"
                                  )
finetuned_model = finetuned_model.merge_and_unload()

Method - 2
save checkpoints during training and then use the checkpoint with the least loss
from peft import PeftModel
finetuned_model = PeftModel.from_pretrained(base_model,
                                  "least loss checkpoint path",
                                  torch_dtype=torch.float16,
                                  is_trainable=False,
                                  device_map="auto"
                                  )
finetuned_model = finetuned_model.merge_and_unload()

Method - 3
same method with AutoPeftModelForCausalLM class
model = AutoPeftModelForCausalLM.from_pretrained(
    "output directory checkpoint path",
    low_cpu_mem_usage=True,
    return_dict=True,
    torch_dtype=torch.float16,
    device_map="cuda")
finetuned_model = finetuned_model.merge_and_unload()

Method-4
AutoPeftModelForCausalLM class specifies the output folder without specifying a specific checkpoint
instruction_tuned_model = AutoPeftModelForCausalLM.from_pretrained(
    training_args.output_dir,
    torch_dtype=torch.bfloat16,
    device_map = 'auto',
    trust_remote_code=True,
)
finetuned_model = finetuned_model.merge_and_unload()

Method-5
All the above methods without merging
#finetuned_model = finetuned_model.merge_and_unload()

Which is the actual method I should follow for inference?
and when to use which method over another?

Hi @pradeepdev-1995 , method 1-4 basically are same methods, they all merge lora's weight to base model, thus resulting model will have same architecture with the model before finetuning except for different weight. Method 5 won't merge lora's weight into base model, thus it will be somewhat slower than method 1-4 during inference.


⚠ Bofrost.fr has degraded performance

In 7ed8e47, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1868 ms

Resolved: Bofrost.fr performance has improved in ee90f5d after 6 minutes.


Axis Annotation: broken "enabled" checkbox

There are cases when "Annotation enabled" box checked, but no annotation shown, or vice versa.
The following screenshot illustrates this situation.

To reproduce:

Open VAPOR, load 2 data sets.
Check "Axis Annotation Enabled" for data set 1.
Switch to data set 2.
Situation captured by the screenshot occurs.

It seems it's resolved, so I'll close it.


A notefield issue from Alpha 4.5.9

Good night.
Here, we were using the Alpha 4.5.9 version (dated June 15, 2020. Because the administrator was unable to install the 4.6.1, acts like the installer is broken, even downloading various times from the website), and the issue for this case is the following:
We were testing a theme (StepMania Tacvicom Edition v4.0, not finished yet but is perfectly stable in SM 5.1 Beta 2 at its current state) in this current alive laptop, and we found the step field don't show any steps, noteskins, and judgment labels in the How to Play and Demonstration screens (but they appear successfully in the normal gameplay screen).
This current alive laptop use (Acer Aspire 5050 4697):

AMD Turion 64 (2.20 GHz, 512 Kb L2 cache).
ATI Radeon Express 1100 using v8.539.100 driver.
1 Gb of RAM memory.
Windows 7 Ultimate SP1.

Thanks!!!

just fixed this, it will be fixed  on next release, thanks for your report

Fixed as of 4.6.0-RC2


fix: ease decimal option

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


OLS-261: Refactor SUID generator

Description

Refactor SUID generator
We used to have three different utils which is too heavy for such a small project. That one utils can be refactored w/o problems.

Type of change

[x] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents
Related Issue #OLS-261

/lgtm

/approve


Refactor to store multiple scrects, use uuid, tags support

@sirech thanks for the ideas and help here! See: https://github.com/spulec/moto/issues/1893

Refactor for multiple secrets @sirech
Use UUID replace hardcoded value
Use random string in ARN id value
Fix datetime stamp
Adding support for Tags https://github.com/spulec/moto/issues/2004
Add tests

Coverage decreased (-0.3%) to 92.274% when pulling a485d59976af28deb1db28026bb723171e2809af on sepulworld:zmw/refactor_multiple_secrets into 71a054af92a45e2a8b5d7c4fb435841949e1895c on spulec:master.

Coverage decreased (-0.3%) to 92.274% when pulling a485d59976af28deb1db28026bb723171e2809af on sepulworld:zmw/refactor_multiple_secrets into 71a054af92a45e2a8b5d7c4fb435841949e1895c on spulec:master.

Coverage decreased (-0.3%) to 92.274% when pulling a485d59976af28deb1db28026bb723171e2809af on sepulworld:zmw/refactor_multiple_secrets into 71a054af92a45e2a8b5d7c4fb435841949e1895c on spulec:master.

looks good to me!

@spulec this is good to go! Looks like the travis test failed due to an intermittent test failure with x-ray test suite.

Confirmed this also fixes the secrets http endpoint not returning the correct datetime.

I was wondering, is this one ready to be merged? I would really like to use it :)

Thanks for the help!

@spulec I saw this was merged in a bit ago (awesome). What is your timeline for releases?

@TopherGopher this is rad, also curious about a release timeline :)


Populate blockcommitmenthash and defaultroot missing fields

Motivation
We want to populate the missing fields of the getblocktemplate rpc call.
Closes https://github.com/ZcashFoundation/zebra/issues/5579 and closes https://github.com/ZcashFoundation/zebra/issues/5455
Depends-On: #5761, #5747
Solution
Get needed data.
Review
I think anyone can review, @teor2345 maybe will want to take a look.
Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?
[ ] How do you know it works? Does it have tests?

Yep, this all looks good, apart from my questions above.
When it's ready, I'd also like to see a unit test, or the output of a manual comparison with zcashd. Our zcash-rpc-diff script will do all the necessary checks for you.
Can you also tag this PR with a priority and the RPC tag, and set yourself as the owner?

Synchronizing zcashd and zebrad to do a manual diff test.

Synchronizing zcashd and zebrad to do a manual diff test.

Actually, i think this test can be done in the context of https://github.com/zcashfoundation/zebra/issues/5686

Synchronizing zcashd and zebrad to do a manual diff test.

Actually, i think this test can be done in the context of #5686

We won't know if this PR works until we test it. We already have a test that will run it and check for errors, and another test that takes a snapshot.
But we need to check we've calculated the new fields correctly before it merges. That way, we don't have to fix it later during other tests, like I had to in PR #5761.
Since it's a manual test, we need to do it for every significant change. (If it was an automatic test, we could just add it to CI once, and it would catch any mistakes.)

I'm in the middle of writing long polling, so I'd like to switch to this PR when I have a draft of that ready.

Here's zcash-rpc-diff (port) getblocktemplate with commit 8c8b1d0:
Checking first node release info...
Checking second node release info...
Connected to zebrad (port 28232) and zcashd (zcash-cli zcash.conf port).

Checking zebrad network and tip height...
Checking zcashd network and tip height...

Request:
getblocktemplate

Querying zebrad main chain at height >=1904187...

real    0m0.008s
user    0m0.005s
sys     0m0.002s

Querying zcashd main chain at height >=1904187...

real    0m0.008s
user    0m0.004s
sys     0m0.003s

Response diff between zcashd and zebrad:
--- /run/user/1000/tmp.hDVNCatQbm.rpc-diff/zebrad-main-1904187-getblocktemplate.json    2022-12-07 12:45:47.938249268 +1000
+++ /run/user/1000/tmp.hDVNCatQbm.rpc-diff/zcashd-main-1904187-getblocktemplate.json    2022-12-07 12:45:47.946249203 +1000
@@ -1,29 +1,40 @@
 {
   "capabilities": [
+    "proposal"
   ],
   "version": 4,
   "previousblockhash": "00000000010bb1122f660c11e73ef4c728b9fe1f039373359c40d60e1b0e80b6",
-  "blockcommitmentshash": "96a8187c2209133ddea7f0689c872101188f9a79d51759678524f554426c5102",
-  "lightclientroothash": "96a8187c2209133ddea7f0689c872101188f9a79d51759678524f554426c5102",
-  "finalsaplingroothash": "96a8187c2209133ddea7f0689c872101188f9a79d51759678524f554426c5102",
+  "blockcommitmentshash": "af4b2acee3115d5a821cd3be5e4db945135efffb36221989806a9ce7ee1d3257",
+  "lightclientroothash": "af4b2acee3115d5a821cd3be5e4db945135efffb36221989806a9ce7ee1d3257",
+  "finalsaplingroothash": "af4b2acee3115d5a821cd3be5e4db945135efffb36221989806a9ce7ee1d3257",
   "defaultroots": {
-    "merkleroot": "0186d7edac6a0eb283e8b4fa909e70de14d058f6a99883a639215f6f62e42f44",
+    "merkleroot": "5278f3cfdd0576077715411f96d1d5e8be32fe16fc139b277a1c7c3e9b3d335a",
     "chainhistoryroot": "af8ef31b06831a2b3af53c2ce05ab0378ea84c61269b89184f97c1d79a2081c1",
-    "authdataroot": "cc14bc5aab7e8fcc5d5c7ead25badcb3853e0d761a745f89892524ad1c48ddca",
-    "blockcommitmentshash": "96a8187c2209133ddea7f0689c872101188f9a79d51759678524f554426c5102"
+    "authdataroot": "ad52724e37f52c500d815c47e0abd56a5caa0e0910a8feb4dfc8ed9deba4040e",
+    "blockcommitmentshash": "af4b2acee3115d5a821cd3be5e4db945135efffb36221989806a9ce7ee1d3257"
   },
   "transactions": [
+    {
+      "data": "0400008085202f890780f072ece1d9adb92fb5fa60fd38670463f626b0b7d7184c33224ee458f53b3ed80000006a47304402204965cd8ae1820bd04ba3264c1a203847ac50cb31f169bf13dd4f9f0bd3115c77022008bf5
9153d6d93becc92faf69ffa2c60b1f2b5ba7dd8058834c244d4fd8ad62301210292538653de3251ea345debf77b78aff957a0ea7756a748bc10cd2224031cbb80feffffff4d5e683d50331d6550000e1479c0e5407c65c85b7b3c7e408a33db
22241283f0010000006a47304402200d2327f6b87a57e671b60cbcf2dcb92d82269b6d840fc78bc3b682d926d8fc71022033d3a0193920743cec9478054c09cf4cf198833cb66661b6de3dcd275a99162f012103afd2d49e87b73c514cb275e
32aec4a7bd1de9117e4d3f6f3e9648c8f7f1adbd5feffffff4d5e683d50331d6550000e1479c0e5407c65c85b7b3c7e408a33db22241283f0080000006a47304402207a7be5e4bc63e645999644636dd5c18b06adcd57a136a3c575ada7917c
850922022054e2a67878d7353c551fca45f111c347826bf1f67c6ff57bd16b97d7e4215c77012102908ee36dcf44c2634b01602fbc1688b5facc37c036df8c32251edc24612a8ad8feffffff4d5e683d50331d6550000e1479c0e5407c65c85
b7b3c7e408a33db22241283f0220000006b4830450221009dd74ed88bd6a245369592f882193a598f7a3aacc25e306c9a63941c9353105c022048c0edf912c95f31685fcc8e9b04077f9df84444428fd07d21d96a52dac6f7eb0121026e9dc8
0ee55ea70bf3e3f452601188449f9fe78e3142ac6777a46e943b9d97bbfeffffff4d5e683d50331d6550000e1479c0e5407c65c85b7b3c7e408a33db22241283f0280000006b483045022100b2c5324659aebdb21f3e5d1c9002cf9aa53e34e
7e3ed2713dc2bd6ada6d58c6c02200e6c32f255bcf8a427da4801d404ac36db70247502710a6bd572c3faa163d8830121022aba77019d30bb26651cd0cc4036f4f5b2ab67956a82e1f714282315f616a0b9feffffff4d5e683d50331d655000
0e1479c0e5407c65c85b7b3c7e408a33db22241283f02e0000006a47304402200eebf7edf8ed7e1a859300f7d429a133c5976ed22c1481c512be7fada5d924ff02202bf205dd167f4a197012a4219867331a03db00a793e50766bcd325bbd75
8bb280121021eaee20ee7fe573c4e74971d36d9f4759f03f6b8ac4c988df449130ed90d3876feffffff5d8418daef69684ad75d5f8226d0c5804c46dd04f1f0dcc904b77867edbf6700010000006a473044022050d79192b5fffddb9dec5243
112ad53439039092518ac101bee7033398ce2ea002203db9b6cb7c5f7ba715f7037b8fc05f97b60aa0f50d8b6d40c01e7491e9ca0f560121037e8aa0b23d4e3495a06c8d061d86337e8940a1cbfd328d9da08c64967c7ca56ffeffffff02404
20f00000000001976a9144f3f346815c38d219fd58c06ab0af166aadb84dc88ac056a0000000000001976a914dd740c9155bf641c946ade0a89c9efd9abdfc68e88ac2f0e1d00620e1d000000000000000000000000",
+      "hash": "60ff08345817ae2ecbf3a0633cf03d3a0a129d8b3adde891665397ab53eb5527",
+      "authdigest": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
+      "depends": [
+      ],
+      "fee": 1277,
+      "sigops": 2
+    }
   ],
   "coinbasetxn": {
-    "data": "050000800a27a726b4d0d6c2000000003c0e1d00010000000000000000000000000000000000000000000000000000000000000000ffffffff04033c0e1d0000000004286bee000000000017a914d45cb1adffb5215a42720
532a076f02c7c778c908738c94d010000000017a914782879ddb585bc8a31e0d50635f20a505ea28a548740787d010000000017a914931fec54c1fea86e574462cc32013f5400b891298780b2e60e0000000017a914d45cb1adffb5215a4272
0532a076f02c7c778c9087000000",
-    "hash": "0186d7edac6a0eb283e8b4fa909e70de14d058f6a99883a639215f6f62e42f44",
-    "authdigest": "cc14bc5aab7e8fcc5d5c7ead25badcb3853e0d761a745f89892524ad1c48ddca",
+    "data": "0400008085202f89010000000000000000000000000000000000000000000000000000000000000000ffffffff05033c0e1d00ffffffff047db7e60e000000001976a91404c0421bf2c45530f0ec950d4c9c1d3f4b8d1a6a8
8ac38c94d010000000017a914782879ddb585bc8a31e0d50635f20a505ea28a548740787d010000000017a914931fec54c1fea86e574462cc32013f5400b8912987286bee000000000017a914d45cb1adffb5215a42720532a076f02c7c778c
9087000000003c0e1d000000000000000000000000",
+    "hash": "c8ed8a14c9c9efc0a2f6e856794a3988bf37fb7665c82b42c61cbf41e2d439c3",
+    "authdigest": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
     "depends": [
     ],
-    "fee": 0,
-    "sigops": 0,
+    "fee": -1277,
+    "sigops": 1,
     "required": true
   },
+  "longpollid": "00000000010bb1122f660c11e73ef4c728b9fe1f039373359c40d60e1b0e80b691375",
   "target": "0000000001420600000000000000000000000000000000000000000000000000",
   "mintime":<PHONE_NUMBER>,
   "mutable": [
@@ -36,6 +47,5 @@
   "sizelimit": 2000000,
   "curtime":<PHONE_NUMBER>,
   "bits": "1c014206",
-  "height": 1904188,
-  "maxtime":<PHONE_NUMBER>
+  "height": 1904188
 }

I can explain all the differences, and the blockcommitmentshash is the same, so I'm happy with this change.


Can't create window on displays that don't support 24-bit color

I'm working on a Kivy app that runs on an FBTFT display. The display only supports 16-bit color, and Kivy fails to create a Window on it. I found a workaround, as detailed here:
http://forum.odroid.com/viewtopic.php?f=145&t=24315&p=166820#p166820
Essentially, allowing Kivy to acquire a window with lower color depth works. Is there a reason Kivy requires 24-bit color by default? Can we drop this requirement?

Related: https://github.com/kivy/kivy/issues/4395.


fix: ItemContainerGenerator obsolete member after #9677

What does the pull request do?

Cortex the use of outdated members:

Item container lookup was moved to ItemsControl as in UWP (old methods are left on ItemContainerGenerator marked with [Obsolete])
* `ItemsControl.ContainerFromIndex(object item)`

* `ItemsControl.ContainerFromItem(object item)`

* `ItemsControl.IndexFromContainer(Control container)`

* `ItemsControl.ItemFromContainer(Control container)`

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 11.0.999-cibuild0028902-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Undefined property: Naoray\LaravelPackageMaker\Commands\AddPackage::$command

Facing this error at laravel 8

Facing same, issue because of this it keeps asking "what is your namesapce" on every make command.

@Naoray Can you guide please how to resolve this.

Si solucionaron?


[3.5] Could not determine country polygon containing the point.

Hello! This might not be a bug, I'm just clueless as to what's happening and what I could do.
I have a very simple Linux server (Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-100-generic x86_64)). I'm using version 3.5 and I run it like this:
first I build the database:
DATA_PATH=$(realpath ../data)
mkdir $DATA_PATH
wget -O $DATA_PATH/data.osm.pbf https://download.openstreetmap.fr/extracts/south-america/argentina/tucuman.osm.pbf
cd nominatim-docker/3.5

# Build
docker build --pull --rm -t nominatim .

 One day out of the blue (I never touched it, updated it or anything), the reverse search stopped working and it ends with the error: Could not determine country polygon containing the point. (the PBF file I imported is very small, containing only a province/state)
using debug=1 in the request:
string(720) "select place_id,parent_place_id,rank_address,country_code, ST_distance(ST_SetSRID(ST_Point(-65.2067782,-26.834862),4326), geometry) as distance FROM  placex   WHERE ST_DWithin(ST_SetSRID(ST_Point(-65.2067782,-26.834862),4326), geometry, 0.006)   AND rank_address between 26 and 30 and (name is not null or housenumber is not null or rank_address between 26 and 27) and (rank_address between 26 and 27      or ST_GeometryType(geometry) != 'ST_LineString') and class not in ('boundary') and indexed_status = 0 and linked_place_id is null and (ST_GeometryType(geometry) not in ('ST_Polygon','ST_MultiPolygon')  OR ST_DWithin(ST_SetSRID(ST_Point(-65.2067782,-26.834862),4326), centroid, 0.006)) ORDER BY distance ASC limit 1"
bool(false)
{"error":{"code":500,"message":"Could not determine country polygon containing the point.","details":"/app/src/lib/DB.php(187)"}}

Of course when this happened I tried re-building everything (i purged all containers, images and volumes) but no luck, it always breaks like this now.
The search function doesn't throw an error, but it stopped working, it always returns an empty result.
I'm using the same PBF file to run openstreetmap-tile-server and osrm-backend and they work perfectly fine.
Any kind of help will be greatly appretiated! Thanks!

Do you mind testing it with 4.0? It's way easier to use, just a single command and you don't even have to build the image by yourself. I have just tested it with:
docker run -it --rm \
  -e PBF_URL=https://download.openstreetmap.fr/extracts/south-america/argentina/tucuman.osm.pbf \
  -p 8080:8080 \
  --name nominatim \
  mediagis/nominatim:4.0

This downloads the image, grabs the .osm.pbf file, runs the import, etc. in one go.
Works fine in that case, I get results back when I query it. Also please read https://github.com/mediagis/nominatim-docker/blob/master/4.0/README.md if you want to make changes (like persisting the data of the Postgresql DB etc.)

Hello @philipkozeny thanks so much for responding!
I actually did! But gave up after a few tries of trying my script to reuse the PBF file and shared volume and got bunch of permission errors, then an Postgres memory error. I was just trying to make the old script I had work hehe. With that new implementation it is of course 10x more convenient and easy! So since the pbf file i'm using is extremely small, I guess it's fine downloading it twice, who cares.
As side notes: I did have to reduce POSTGRES_SHARED_BUFFERS to 1GB for some reason (the memory error I mentioned above).
The reverse request faled at first (not even a server error, just ERR_EMPTY_RESPONSE.)

The WEIRD thing is that if I pass debug=1 to the request, it worked :confused:

So after trying many things, I modified a bash script I had to run all the containers in my server and I used detached mode for nominatim 4.0 and now it works fine :shrug:
Anyway, thanks for your help! I wish I knew docker better (or nominatim...) to help you debug my original problem, but if it turns out to be a bug and there's any extra info you need just let me know!

Thanks @philipkozeny
Yeah, I got it working (sorry if that wasn't clear in my previous post). I ran it on the exact same server as in my original post.
The only thing that i changed to make it run is use detached mode. Now it works just fine.
I'm sure it was something wrong with my setup process. If it happens again, i'll see if I can recover some logs, in case it's useful.
Thanks so much again, you've been of great help!


getdns: 1.4.2 -> 1.5.0, stubby: 0.2.3 -> 0.2.4

Motivation for this change
Bumping together since getdns apparently includes
stubby 0.2.4 for whatever reason.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-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)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I'm able to enable stubby and it seems to answer the handful of queries I tried :).


fix: ci issues in ui

@leecalcote @ramrodo, This PR fixes whatever issues you had with caching in the past. The test failure is due to the error in the tests which may have been missed out since our CI for UI was inactive for couple of days.

@leecalcote @ramrodo, This PR fixes whatever issues you had with caching in the past. The test failure is due to the error in the tests which may have been missed out since our CI for UI was inactive for couple of days.

I wonder where gonum went. https://github.com/layer5io/meshery/pull/2192/checks?check_run_id=1634429603#step:3:1596

I wonder where gonum went. https://github.com/layer5io/meshery/pull/2192/checks?check_run_id=1634429603#step:3:1596

I wonder where gonum went. https://github.com/layer5io/meshery/pull/2192/checks?check_run_id=1634429603#step:3:1596

Gonum package is giving 500 for a while, must be a flake. Should be fixed on its own by tomorrow, I hope.

I wonder where gonum went. https://github.com/layer5io/meshery/pull/2192/checks?check_run_id=1634429603#step:3:1596

Gonum package is giving 500 for a while, must be a flake. Should be fixed on its own by tomorrow, I hope.

Ok, yes, hopefully. Like you say, it's causing failures in other builds, too.

Ok, yes, hopefully. Like you say, it's causing failures in other builds, too.


x-k8s-aws-id included in the header, but gives Invalid query parameter x-k8s-aws-id

Hello, I am trying to generate a eks token from dotnet code, which will then be used to create a k8s client. I am following the instructions here and trying to implement the same code in c#. I am getting unauthorized error and the reason is that the token is malformed.
When I add the x-k8s-aws-id  in the headers using
req.Headers.Add("x-k8s-aws-id", clusterName);

I get the following error (even though it is not added to a query parameter as the error suggests). Adding it in query parameters using req.Parameters.Add gives the same error, which is expected.
time="2022-05-28T06:49:27Z" level=warning msg="access denied" client="<IP_ADDRESS>:46940" error="input token was not properly formatted: non-whitelisted query parameter \"x-k8s-aws-id\"" method=POST path=/authenticate

When  I don't include the x-k8s-aws-id in the query string or parameter, I see the following issue, which is expected.
client did not sign the x-k8s-aws-id header in the pre-signed URL

I logged the URL before it is encoded and I don't see any query parameter with x-k8s-aws-id as the key.
https://sts.us-east-2.amazonaws.com/?Action=GetCallerIdentity&Version=2011-06-15&X-Amz-Expires=900&X-Amz-Security-Token=IQoJb3...DohRL
&X-Amz-Algorithm=AWS4-HMAC-SHA256
&X-Amz-Credential=ASIA........I4H4/20220528/us-east-1/sts/aws4_request
&X-Amz-Date=20220528T063607Z
&X-Amz-SignedHeaders=host
&X-Amz-Signature=3b4fec....2c21e

After some tricky debugging, I found that this was because the signed headers query parameter had a semicolon in the value (;), which was causing an exception in the way the query parameter was being read.
X-Amz-SignedHeaders=host;x-k8s-aws-id

Once I URL encoded the query parameter values, it was interpreted correctly.


Using video

"Can" this framework be used with video?

It's meant to work with images mainly, but maybe can do it - have you tried yourself?

Yep, why not just try it? Why ask other people to work for you?


Don't panic on errors setting interface addrs

Before we call setInterfaceIP() and setInterfaceIPv6(), we construct partial error messages for use if they return errors.  While both functions check for nil addresses, we don't guard against passing nil
addresses to fmt.Sprintf when constructing those messages, which causes us to panic if they're nil.  Add wrappers that supply the text "(no address)" when the address is nil.

LGTM

LGTM


Add team member to HMPPS Integration API repository

Add April as a team member to HMPPS Integration API repository.

Closing as April has been added to the MoJ GitHub organisation.

Hi @chubberlisk will still track external MoJ users who a Org members as well

Hi @chubberlisk will still track external MoJ users who a Org members as well

Ahhhh okay, sorry I didn't realise that - will merge this then!

Thank you


Update memory available panel to use just the node_memory_MemAvailabl…

…e_bytes metric
Description
The current metric shown by this panel is misleading, let's just use the OOTB metric.
Fixes
Signed-off-by: Raul Sevilla<EMAIL_ADDRESS>

Also updating namespace count query since that metric is no longer being scraped in OpenShift. **Some context in  this PR **


chore: Fix typo in jest.css

Summary
Fixed typo.
alway -> always

Test plan

Codecov Report

Merging #11406 (c73559a) into master (467b599) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11406   +/-   ##
=======================================
  Coverage   64.20%   64.20%
=======================================
  Files         309      309
  Lines       13525    13525
  Branches     3294     3294
=======================================
  Hits         8684     8684
  Misses       4126     4126
  Partials      715      715

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 467b599...c73559a. Read the comment docs.


Remove references to old services

Since we've finalized 0.2.0 we can simplify things by removing support of older services that we are in the process of replacing.

pass-docker docker compose setup(s) can be simplified by removing the original docker-compose.yml environment and letting the demo base environment take its place
Our project parent POM can be simplified by removing things used only by the older services

pass-docker cleanup:

https://github.com/eclipse-pass/pass-docker/pull/311
POM Cleanup PRs:
main: https://github.com/eclipse-pass/main/pull/439)
pass-core: https://github.com/eclipse-pass/pass-core/pull/22
pass-support: https://github.com/eclipse-pass/pass-support/pull/3


ghostscript: support SOURCE_DATE_EPOCH for reproducible builds

Without this patch, it is impossible to generate PDF documents in a reproducible way using Ghostscript, as CreationDate and ModDate are included in the PDF, which are based on the current time. I ran into this problem while using the LATEX command \includegraphics with an .eps graphic.
The Ghostscript developers are not interested in fixing this and rejected the patch, see https://bugs.ghostscript.com/show_bug.cgi?id=696765#c28. This is also where I download the patch from.
Arch Linux carries the same patch, as does Debian.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 362173

x86_64-linux

:white_check_mark: 4 packages built:

ghostscript
ghostscript.doc (ghostscript.doc.doc ,ghostscript.doc.fonts ,ghostscript.doc.man)
ghostscript.fonts (ghostscript.fonts.doc ,ghostscript.fonts.fonts ,ghostscript.fonts.man)
ghostscript.man (ghostscript.man.doc ,ghostscript.man.fonts ,ghostscript.man.man)


Write data with keep format of cell

I have template file with some settings at the format for cells. (e.g the cell "A1" have been setting as "Currency") but when write data with:
var workbook = Workbook.fromFileSync("./Template1.xlsx"); workbook.getSheet("Sheet1").getCell(1,1).setValue(1000); workbook.toFileSync("./out.xlsx");
After success the format at cell "A1" of out.xlsx have been changed to "General". How can I keep the format of cell as Template file?
Thanx.

Could you share the workbook?

Template.xlsx
This is the workbook.
Thanx.

Thanks. So this seems to be yet another oddity of the Office Open XML spec. It looks like there is indeed a style attached to the column. xlsx-populate also dutifully adds the cell value. But it seems that the style on the column doesn't actually do anything. In order for the cell to get the style applied, xlsx-populate should copy the style reference from the column to the cell. It doesn't currently do that. We'll try to get it addressed in a future release.
The workaround for now is to style the cells in the column rather than the entire column. (If you use the same template you'll need to remove the style from the column first.)

Thanks for feedback. Please let me know if i can help!

I just released v1.0.0. It now properly handles column styles. The API has changed though. Now your example should be:
const XlsxPopulate = require("xlsx-populate");
XlsxPopulate.fromFileAsync("./Template1.xlsx")
    .then(workbook => {
        workbook.sheet("Sheet1").cell(1, 1).value(1000);
        return workbook.toFileAsync("./out.xlsx");
    });


Add 647 by instupendo

Song Name
647
Artist Name
instupendo
Source
Youtube
Youtube Link
https://youtu.be/YHlcmmkiwbU?si=89uMZaSKsFrt7ocU
Direct File Link
No response
Song ID
1295762
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 103078631
Downloaded: No

accept


Add location.origin polyfill for older versions of IE

Source: http://tosbourn.com/a-fix-for-window-location-origin-in-internet-explorer/
if ( !root.location.origin ) {
    root.location.origin = root.location.protocol + "//" + root.location.hostname + (root.location.port ? ':' + root.location.port: '');
}

Currently, Smooth Scroll support is only at IE 11+ as a result.

Actually, just switch from origin to hostname

v9.4.1 https://github.com/cferdinandi/smooth-scroll/pull/276


fix: useTruncation infinite loop, reenable dashboard cross links on ChartList

SUMMARY
Due to a bug in useChildElementTruncation, there was an edge case which could trigger an infinite loop of rerenders. The bug occurs when the difference in width of subsequent numbers after the plus sign (e.g. +4 and +5) is just big enough to change the truncation state to the other number. This PR ensures that the calculation is performed only once, and if the edge case is triggered, we simply accept the off-by-one error.
This PR also implements a ResizeObserver which recalculates the truncations if the container size changes. Previously we relied on the width values from references in useLayoutEffect's dependency array, which was not a correct approach, since the changes of those values would not trigger a rerender.
This change allowed us to bring back the feature that relied on the truncation logic, which is dashboard cross links on Chart List page. The feature adds a column to the list which displays the dashboards that given chart is added to.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before (occurred long ago when "dashboards added to" column was not yet hidden):

After:

TESTING INSTRUCTIONS

Visit ChartList
Verify that "Dashboards added to" column is visible and that it correctly displays the dashboards. Dashboard names should be clickable and navigate to given dashboard. Truncated dashboards should appear in a tooltip

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@justinpark would you be able to do another pass?

/testenv up


Create a Check for a specific folder path

Maybe we can use the Request URL check?

I found that  using tags can be a better option, in NextCloud Tag has this two options:

visibility
editable
you can find them in the oc_systemtag table.
so we can create a system tag that is invisible and unable to change and assign that tag to files and folders.
With this approach, we just need to add one Check to verify whether the user is logged in with MFA or not. and the rest of the work will be assigned to NextCloud infrastructure.

Also, there is another table oc_systemtag_object_mapping that indicates which object has which tag.

For selecting a path, the private tag is a good idea and we can find tagged folders from the database. And for limiting access we must change in Workflow engine and add a rule for Mfa verified. after these settings, we can limit access to tagged folders when someone does not have Mfa Verified by using of File access control app.

For this phase we can use file access control with new Mfa Verified check and a regex over the file name (File name contains or starts with something). For the next step we must create an app to automatically tag folders that selected by admin in the file system.

Done


[Meshery] Adapters should first check for an existing service mesh deployment before attempting to install

Description
Meshery adapters need to be cognizant of existing deployments of their representative service mesh so as to avoid conflict. When a user attempts to deploy Istio more than once, they receive this error in the UI:

Expected Behavior

The error message should be improved to explain that a conflict has occurred with an existing deployment. See #647.
MeshSync should be leveraged in the /management UI on each adapter page to show the user details of service mesh installations, so that they don't attempt to and are disallowed to attempt to install the same mesh to the same namespace.
Adapters can first check MeshSync for presence of an existing service mesh deployment in the same namespace before attempting to deploy an instance of the service mesh.

@nitishm @AdheipSingh fyi, this issue has been tagged with area/meshsync

I can pick this up @leecalcote

Delivered - https://layer5.io/service-mesh-management/meshery/meshery-operator


Cookie code samples

It would be good to add some code samples demonstrating how to use cookies.

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

ID: 76e22150-f1f1-5e4f-0e97-39b1ac089297
Version Independent ID: 687172c3-b7d8-525d-39dc-658b4a0f526f
Content: Session and app state in ASP.NET Core
Content Source: aspnetcore/fundamentals/app-state.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Thanks for contacting us.
We don’t have the resources to invest in this area, so we are closing the issue. Should your request generate enough  👍 responses, we’ll reconsider.