[ZEPPELIN-799] Add python edit mode.

What is this PR for?
support python edit mode in paragraph.
What type of PR is it?
Improvement
Todos

[x] - support python edit mode.

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-799
How should this be tested?
you can refer to screenshot.
Screenshots (if appropriate)

before

after

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

cool thanks, looks good.

LGTM

Looks great to me! Merging if there is no other discussion.


Save, Save & Close etc... not publishing assets or running on before/AfterWrite etc.

Issue
I've built a site for a client which used the asset uploader within the Member object for "Blog Author Photo". This functionality is actually provided by the official SilverStripe Blog module. However, when your module is installed as well the staff are unable to add photos in this field because they remain in the 'Draft' state on clicking Save, or any of this modules Save buttons.
Replication:

Install silverstripe-blog and this module
Visit your own user profile in SilverStripe add a photo and click Save... that should work as expected.
Now try that same action via the Member LeftAndMain GridField you'll notice any image changes remain in draft.

Other Observations
I initially thought it might've been linked to the the SilverStripe blog not setting ownership on the assets, but it does, as witnessed by the actual user profile saving correctly. I tried to perhaps manually work around this with an onBeforeWrite or an onAfterWrite method call in a DataExtension on the Member object but these don't seem to get invoked in the usual way.
Can you explain how the flow works for this module calling the save actions? I can't seem to work my head around it looking in the source as I'd have tried to patch it and put a pull request in otherwise.

Hey, I made a fresh install and installed the blog module. Then, I created a model admin for the members using the default settings.
As far as I can tell, using the regular "save" works just fine. "save and close" works too, but somehow if you visit page again, it's not refreshing the status of the uploader (so, it's still shown as being "draft" with a little green checkmark showing it's uploaded... but actually, it is published). You can confirm by clicking on the little eye and see the file is indeed published.
So I think it's just the state of the uploader that is somehow cached by silverstripe in between ajax navigation. If you refresh the page, it is displayed properly. Can you confirm this behavior on your end?

That's fair, but if you try and load that asset in a template it won't load. In my case anyway

Mhhh.. since the asset is published (even if the uploader doesn't say so) it should be working. it is for me anyway. could you share like a screen recording or some code that I could have a look at ?

Interesting, I'll check a couple other things over. The browser console is helpful as ever with its reasons.

Is there any way to disable the module for certain parts of the Admin? I just want to ascertain if it's perhaps any other customisations on this particular installation. Thanks for your help with this once again :-)

well it depends. does it fail if you press on the regular "save" button? this is what i would do

if it works with "save" and not with "save and close" => i would look here https://github.com/lekoala/silverstripe-cms-actions/blob/master/src/ActionsGridFieldItemRequest.php#L487
it neither works it means somehow the extension is messing up publishing the asset. i don't see why, since it should not have any side effect other that updating the editform. but you can always return early in https://github.com/lekoala/silverstripe-cms-actions/blob/master/src/ActionsGridFieldItemRequest.php#L487 with somethin like "if controller::curr() instanceof MyMemberController => return null)

I'm closing the issue feel free to reopen if you have more details


Unable to proxy a service

Seeing a strange issue when trying to proxy a service running on GKE, api version v0.21.2
/api/v1/proxy/namespaces/default/services/myservice/index.html
{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "no endpoints available for \"myservice\"",
  "code": 500
}

The service is definitely there and can be seen using
/api/v1/namespaces/default/services/myservice/
If going directly to the pod then it works..
/api/v1/proxy/namespaces/default/pods/myservice-w4l8b/index.html
Is there a configuration that I'm missing on the service to allow it to be proxied or perhaps another reason that it doesn't seem to work?

Can you confirm that your service's selector is selecting any pods?
Run kubectl get services, look for the row of your service, then in the SELECTOR column for something like foo=bar.  This is the selector for your service.  Now see if that selector is selecting any pods, like kubectl get pods -l foo=bar.  If no results from that, then that is your problem.

Thanks but yes that's all working correctly.  I'm able to use the service directly and via a GKE external load balancer. The issue is only when using the proxy.

@rawlingsj If you don't mind sending me (robertbailey [at] google.com) you cluster name / project ID I can take a look and see if there's anything obviously wrong with the proxy on your master.
Can you confirm that the proxy works for pods but not for services?

@roberthbailey sure I'll send the details over now, but yeah the issue is the proxy works for pods but not services.

@rawlingsj when you created your service did you give the port a name?
Try /api/v1/proxy/namespaces/default/services/myservice:portname/index.html

The proxy will only find an address for your service if the port string matches exactly and if one isn't specified in your query it uses the empty string by default. If you create your service with a named port, then your queries through the proxy to that service also need to include the named port.

Ah I see.. no I created it using the CLI and didn't give a port name.
kubectl expose rc myservice --create-external-load-balancer=true --port=80 --target-port=9090
I'll give that a go now.

Hmm, it looks like 'expose' gives unnamed ports a name of "default".  That
seems like a misfeature to me.  Care to open a bug?  Alternately we could
make teh proxy assume that no name means "first port found" which will
handle single-port services transparently.  Or both
On Wed, Jul 15, 2015 at 10:24 AM, James Rawlings<EMAIL_ADDRESS>wrote:

Ah I see.. no I created it using the CLI and didn't give a port name.
kubectl expose rc myservice --create-external-load-balancer=true --port=80
--target-port=9090
I'll give that a go now.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/11296#issuecomment-121685804
.

That's great it is working with default, many thanks both!
/api/v1/proxy/namespaces/default/services/myservice:default/index.html
I'll close this issue and raise one for the misfeature to be discussed.  Thanks again.

Wow I spent 3 hours trying a bunch of things to get to the UI of my cluster service and it never occurred to me that a named port was screwing with the path. Would be great to mentioned this here:
https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/README.md
@roberthbailey @thockin

Why would that go in the addons docs?
http://kubernetes.io/docs/user-guide/accessing-the-cluster/#manually-constructing-apiserver-proxy-urls

@thockin in my case I was creating a cluster-service with a UI and trying to copy the way that the common kubernetes dashboard is deployed. "Kubectl cluster-info" returns the service URL without any ":portname" ending which sends the user to a dead end (from a UX perspective). So after searching and digging the cluster-addon docs and coming up with nothing I ended up here for the answer. Funny enough someone asked about the same thing on Slack the next day I managed to point him in the right direction. It's either a case of me not RTFM or linking the two might save someone else 3 hours ;)


tibber will not load all actual data

Not all Data will load.

I have done a reboot of Fhem and a reboot ot he pc, any the same error, can ypu please check.
regards
simon

Hi Simon,
in my tibber account the price changes at the beginning of a new hour. Therefore, all data except the rt_* data get updated only every new hour. Masterdata e.g. has_production get load only once at FHEM startup. Do you miss any other data or have any other data that needs to be updated more frequently?
bests
Dirk

Thanks for the fix! It is already available in the last release.

@fhempy  dependabot[bot] changed it the dependency back to 0.28.2 ! This breaks again parts of the code.

Thx for reporting! I have fixed the version.


i don't understand char_frequency.py is to do what ?

Check here:
https://github.com/ankush-me/SynthText/blob/874ec5d638393b7a78d0261a98d672ba26b76650/text_utils.py#L432
It is used to get an estimate of the aspect ratio of glyphs of a given font.


Why called "gs" in "automl-gs"?

Grid search, probably

Yes, it's grid search.


Update Meta “tags”

Automatically generated by Netlify CMS

👷 Deploy Preview for benevolent-pika-f5fbe0 processing.

Name
Link

🔨 Latest commit
be3f825e4f997353d9b355809656d3269c4ebd9e

🔍 Latest deploy log
https://app.netlify.com/sites/benevolent-pika-f5fbe0/deploys/62e2e0b8be27d50008eea814


Historical dataset error

On running the pytorch lightning example but swapping in the Historical dataset, the following error is raised:
RuntimeError: Given groups=1, weight of size [64, 3, 9, 9], expected input[1, 1, 256, 256] to have 3 channels, but got 1 channels instead

I assume there is a trivial fix in the dataset?

The Historical dataset is grayscale so it would require changing the number of in_channels on the first conv layer of the model you are using. Looks like I hardcoded it but I can make a fix to define the number of input channels.

Fixed amongst other updates in #3.
You can define input/output channels of a model like
from torch_enhance.models import SRResNet
model = SRResNet(scale_factor=2, channels=3) # channels=1 for grayscale

Although if you train a model on a RGB dataset you won't be able to transfer to grayscale dataset unfortunately unless you do tile the grayscale channel to 3 channels (which will likely give mixed results).

Perfect, thanks for the quick fix!


Connection oracle error

usql oracle://test:test@<IP_ADDRESS>:1521/lzdw
Connected with driver oracle (<unknown, error: oracle: ORA-00942: table or view does not exist>)
Type "help" for help.
or:lzuapp@<IP_ADDRESS>:40011/lzudw=>

What version of Oracle Database are you using?

18c

It should work fine with 18c. Possibly your account doesn't have permission call SELECT version FROM v$instance which is what usql uses to determine the database version.


Add support for documents as CSV string

Pull Request
What does this PR do?
Fixes partially  #182
This one is for the support of CSV string content

bors merge


[Proposal]: Build & Modernize AI Applications Hackathon (Build RAG Pattern apps using Azure OpenAI + AKS + Cosmos DB + Cog Search + Semantic Kernel)

Topic
We have developed a hackathon which is built around the Build & Modernize AI Applications reference solution to demonstrate how to build RAG Pattern applications and services using Azure OpenAI, Azure Cosmos DB, Azure AI Search. and Azure Kubernetes Service. The solution is built using the Semantic Kernel SDK as the AI orchestration layer on .NET 7.
The hackathon contents are fully developed and had multiple customer deliveries. The hackathon consists of 7 challenges and can be delivered in a one day format of 5 challenges. Or a 1.5 - 2 day format with all 7 challenges. The original source for this hackathon is here: Build & Modernize AI Apps Hackathon
We also have a comprehensive Coaches Guide with materials for coaches to prepare for and deliver the hackathon. This includes:

PowerPoint presentations for coaches to present before each challenge.
Written guidance for coaches for each challenge.
Short videos to walk through each challenge to help coaches prepare.
Final solutions for coaches to use to help guide attendees when needed.
a 90-minute video that goes deep into the underlying reference application this hackathon is built on to help them train themselves on this solution.

Abstract/Learning Objectives
Coaches and attendees for this hackathon will learn how to design, build and deploy RAG Pattern applications and services using Azure OpenAI, Azure Cosmos DB, Azure AI Search. and Azure Kubernetes Service. They will learn how to implement these solutions using Semantic Kernel as the orchestration layer.
Attendees will gain knowledge on the following services and concepts:
Services:

Azure Cosmos DB
Azure OpenAI
Azure AI Search

Concepts:

Embeddings
Prompt engineering
Effective system prompts

Below are the learning objectives for each challenges:

Challenge 1: Deploying the service in Azure for this solution and configure the application to debug locally.
Challenge 2: Configuring vector indexes. Data loading and vectorizing. Automating the process to make repeatable.
Challenge 3: Vectorizing user prompts, building system prompts, implementing conversational chat history.
Challenge 4: End to end testing for data loading and vectorizing. Prompt engineering and testing.
Challenge 5: Customizing with new data, entity management, Semantic Kernel memory types.
Challenge 6: Creating new Semantic Kernel Plug-ins and Functions.
Challenge 7: Integrating with Prompt Flow.

Delivery Date
Now
Authors
https://github.com/markjbrown
https://github.com/sandeepsnairms
https://github.com/ciprianjichici
https://github.com/hatboyzero
https://github.com/joelhulen

Other
These contents are fully developed and ready to go. We could use some assistance in getting this content into the WTH format.
Once here our plan is to keep this as the central place to publish this content. The underlying reference app and hackathon will continue be receiving regular updates to reflect changes in the capabilities for the Azure services used in this solution as well as Semantic Kernel SDK.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi folks. the bits on this are coming within the next 7-10 days. CC @joelhulen
Thanks.


[CLOSED] Add missing headers to Path class files.

Issue by Yomodo from Friday Jan 09, 2015 at 10:22 GMT
Originally opened as https://github.com/alphaleonis/AlphaFS/issues/39

Comment by alphaleonis from Friday Jan 09, 2015 at 10:34 GMT

If this is about the copyright comments, see #21. I'll fix that before release.

Comment by Yomodo from Friday Jan 09, 2015 at 11:06 GMT

Uhm, indeed.


Clipboard not working on Linux x11 (i3wm)

Nobody cares about esoteric window managers. It seems that only me is using it, and this bug is on the clipboard library and not notan. So I'll see if I can find some time eventually to check it there. Meanwhile I am closing it.
If anybody thinks that this should be here as reminder, just feel free to leave a comment or open the issue again.


Add 401 to the explicitly defined codes

Changes

/kind

Fixes #108

Release Note

Docs

Add 401 to the explicitly defined codes

PTAL @knative/steering-committee, @knative/technical-oversight-committee

@aliok @dsimansk could you PTAL at this?
/assign @aliok @dsimansk

/assign @pierDipi

@pierDipi could you PTAL?

I have no power to approve here :)

I'm assuming based on the discussion in https://github.com/knative/community/issues/1399 that @knative/technical-oversight-committee owns changes to the spec now.
And we probably should vote on spec changes... we can probably do that async, but I'll add it to the TOC backlog too just in case.
+1 from me

+1 from me

+1

/approve


docs(behavior_path_planner): update pull out docs

Description

update pull_out docs related  to https://github.com/autowarefoundation/autoware.universe/pull/1438
please see

https://github.com/tier4/autoware.universe/blob/docs/update_pull_out_docs/planning/behavior_path_planner/README.md
https://autowarefoundation.github.io/autoware.universe/pr-1587/planning/behavior_path_planner/

Related links

https://github.com/autowarefoundation/autoware.universe/pull/1438
Tests performed
not tested because changing only docs

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[x] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

[ ] write the reason why vehicle_info's max_steer is not used.


getOneOfs() oneofs cardinality not known!

Error: getOneOfs() oneofs cardinality not known!
at getOneOfs (/root/gencode/node_modules/.pnpm/@cosmology+ast@1.8.1/node_modules/@cosmology/ast/main/encoding/proto/types.js:162:15)
at createProtoType (/root/gencode/node_modules/.pnpm/@cosmology+ast@1.8.1/node_modules/@cosmology/ast/main/encoding/proto/interface/proto.js:59:42)
at buildBaseTypeScriptInterface (/root/gencode/node_modules/.pnpm/@cosmology+telescope@1.8.3/node_modules/@cosmology/telescope/main/build.js:41:49)
at /root/gencode/node_modules/.pnpm/@cosmology+telescope@1.8.3/node_modules/@cosmology/telescope/main/build.js:118:58
at Array.forEach ()
at TelescopeParseContext.buildBase (/root/gencode/node_modules/.pnpm/@cosmology+telescope@1.8.3/node_modules/@cosmology/telescope/main/build.js:115:20)
at /root/gencode/node_modules/.pnpm/@cosmology+telescope@1.8.3/node_modules/@cosmology/telescope/main/generators/create-types.js:46:17
at Array.map ()
at plugin (/root/gencode/node_modules/.pnpm/@cosmology+telescope@1.8.3/node_modules/@cosmology/telescope/main/generators/create-types.js:43:35)
at /root/gencode/node_modules/.pnpm/@cosmology+telescope@1.8.3/node_modules/@cosmology/telescope/main/builder.js:106:39
https://github.com/sunriselayer/sunrise/tree/main/proto/sunrise
https://github.com/sunriselayer/sunrise/blob/effea572e0b2661fca71a8bb88b8af530681ae57/proto/sunrise/swap/route.proto#L40
https://github.com/sunriselayer/sunrise/blob/effea572e0b2661fca71a8bb88b8af530681ae57/proto/sunrise/swap/metadata.proto#L51
https://github.com/sunriselayer/sunrise/blob/effea572e0b2661fca71a8bb88b8af530681ae57/proto/sunrise/swap/in_flight_packet.proto#L39
https://github.com/sunriselayer/sunrise/blob/effea572e0b2661fca71a8bb88b8af530681ae57/proto/sunrise/swap/in_flight_packet.proto#L43

https://github.com/sunriselayer/sunrise/tree/main/proto/sunrise

Hi, thanks for the feedback!
I think we can improve the error msg to make it more clear.
About this issue, I believe there maybe a message which has multiple oneofs like:
message TestRequest {
uint32 test_num = 1;
oneof test_oneof {
string id = 2;
string name = 3;
}
oneof test_oneof1 {
string id = 4;
string name = 5;
}
}
If there's a place like this, they have to combine into one.

message IncomingInFlightPacket {
PacketIndex index = 1 [
(gogoproto.nullable)   = false,
(amino.dont_omitempty) = true
];
bytes data = 2;
string src_port_id = 3;
string src_channel_id = 4;
string timeout_height = 5;
uint64 timeout_timestamp = 6;
bytes ack = 7;
RouteResult result = 8 [
(gogoproto.nullable)   = false,
(amino.dont_omitempty) = true
];
string interface_fee = 9 [
(cosmos_proto.scalar) = "cosmos.Int",
(gogoproto.customtype) = "cosmossdk.io/math.Int",
(gogoproto.nullable) = false,
(amino.dont_omitempty) = true
];
oneof change {
PacketIndex outgoing_index_change = 10;
bytes ack_change = 11;
}
oneof forward {
PacketIndex outgoing_index_forward = 12;
bytes ack_forward = 13;
}
}


reports zero values on startup

When gosdm starts but has not read out all values from the modbus yet, the JSON entities corresponding to the unread values are zero. This can be confusing because zero might be a valid value. A better choice might be to leave out these entities, or give them a JSON value of null.

This is correct. I changed the behaviour:
{"UniqueId":"Instrument23","Timestamp":"2017-06-22T16:32:13.217469202+02:00","Unix":1498141933,"ModbusDeviceId":23,"Power":{"L1":0,"L2":0,"L3":0},"Voltage":{"L1":235.1999969482422,"L2":0,"L3":0},"Current":{"L1":0,"L2":0,"L3":0},"Cosphi":{"L1":1,"L2":0,"L3":null},"Import":{"L1":null,"L2":null,"L3":null},"TotalImport":null,"Export":{"L1":null,"L2":null,"L3":null},"TotalExport":null,"THD":{"VoltageNeutral":{"L1":null,"L2":null,"L3":null},"AvgVoltageNeutral":null}}

In this example, all values up to Cosphi.L2" are already read from the smart meter and therefore initialized. The other values are null``.


Issue #42

updated the format of the cheatsheet

Great work @bubblecode76 !!
Will merge it in a while after solving the merge conflicts!


Supported device addition for Wiki

I can't submit a edit to the wiki page for supported devices.
Just wanted to add one:

Apple

iPhone 13 Pro, iOS 17.0.1

I've got the iPhone connected to a Windows 11 machine, shared over IP to a Server 2019 machine. I was able to interact with the iPhone using iMazing, approve trusting the device, pull a backup and view data on the phone.
Server 2019: usbip-win2 UDE <IP_ADDRESS>
Windows 11: usbipd-win 3.2.0

Thank you very much for the feedback! I've added iPhone 13 Pro to the list.


Cannot use +Layout.svelte in svelte kit

Check that this is really a bug

[X] I confirm

Reproduction link
/
Bug description
Using a layout is required if you want to build this with sveltekit and have anything useful. When I do so, the slots don't load, and you just get a blank screen.
Expected Behavior
No response
Actual Behavior
No response
Konsta UI version
3.0.1
Platform/Target and Browser Versions
All
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Konsta UI issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

I am using sveltekit 1.5.0, konsta ^3.0.0 and I'm using +layout.svelte with only KonstaUI and everything works fine, the following is an example of one of the layouts, using <slot />:
<script>
	import '$lib/style/app.css';
	import { Notification } from 'konsta/svelte';
	import { App } from 'konsta/svelte';
	import { toastContent, toast } from '$lib/stores/global';
</script>

<App safeAreas theme="ios">
	<slot />

	<Notification
		colors={{ bgIos: $toastContent.color || 'bg-white' }}
		opened={$toastContent}
		title="C-Square"
		subtitle={$toastContent.title}
		text={$toastContent.text}
		class="mt-10"
		onClick={() => toast.hide()}
	/>
</App>

Can you check that +layout.svelte has a lower "L" and in case post your code?


Examples could use const/let instead of var

The documentation uses var, e.g. for cond.
var fn = R.cond([
  [R.equals(0),   R.always('water freezes at 0°C')],
  [R.equals(100), R.always('water boils at 100°C')],
  [R.T,           temp => 'nothing special happens at ' + temp + '°C']
]);

I'd prefer using const and it should be better practice. Is there a cause why var is used instead? Or an opinion against?

No, there is no good reason not to switch that I see.  Since the examples have moved to fat arrows from function expressions, it would make sense to switch these too.  The library still mostly works with ES3, a restriction we intend to relax as soon as we hit 1.0.  But the examples should be more modern.
Feel like creating a PR?


fix(learn): changed test to be different from the video

the array on the test and it's solution were same as the video explanation, replaced the test with one suggested in #39097
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #39097

Problem: Numpy - Initialize Array Problem (link)
Before fix:
Question:
What is another way to produce the following array?
[[1. 1. 1. 1. 1.]
[1. 0. 0. 0. 1.]
[1. 0. 9. 0. 1.]
[1. 0. 0. 0. 1.]
[1. 1. 1. 1. 1.]]

Solution:
output = np.ones((5, 5))
z = np.zeros((3, 3))
z[1, 1] = 9
output[1:-1, 1:-1] = z

After fix:
Question:
What is another way to produce the following array?
[[0. 0. 0. 0. 0. 0. 0.]
[0. 1. 1. 1. 1. 1. 0.]
[0. 1. 1. 1. 1. 1. 0.]
[0. 1. 1. 5. 1. 1. 0.]
[0. 1. 1. 1. 1. 1. 0.]
[0. 1. 1. 1. 1. 1. 0.]
[0. 0. 0. 0. 0. 0. 0.]]

Solution:
output = np.ones((7, 7))
z = np.zeros((5, 5))
z[2, 2] = 5
output[1:-1, 1:-1] = z

@ojeytonwilliams and @Twaha-Rahman The Cyprus test for ShowCertification.js failed. Does this just mean this branch needs a rebase? Or, is there something else going on?

@Sky020 The fix for the Cypress test is in #39754.
A rebase after that PR gets merged should be enough.

@Twaha-Rahman Right. Thank you. I just saw the message from Oliver on the contributors channel.

Closing this PR due to not being able to push back to user's master branch.  I have created PR #39773 as a replacement with the user's changes.
@nitnjain In the future, please take a look at the docs to learn about creating a branch off your master for creating PRs.  You also should revert the changes made on this PR from your master branch.


svelte(kit)+postgresql, postgrest starter template

introduction talk coming in svelte fall summit 2021!

@guyromm, can you run rebase your branch on staging and run npm run format.
The formatting of src/routes/templates/templates.json is not correct


Add new relevancy evaluators

Description

Adds new relevancy evaluators AnswerRelevancyEvaluator and ContextRelevancyEvaluator for measuring relevancy of answer and contexts, respectively, to the query.
Separating out these evaluators allows for finer grain evaluation

Fixes # (issue)
Type of Change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Does this mean the existing relevancy evaluator is deprecated?

Does this mean the existing relevancy evaluator is deprecated?

It's a good question. The existing relevancy evaluator could be kept I think, as that one tries to get an evaluation of whether both answer and context are relevant to the query in the same prompt. Though, we undertook this work in order to improve that one due to the lack of feedback we get on the evaluation — we just get a YES or NO result.
The new evaluators handle answer and context relevancy separately.

Does this mean the existing relevancy evaluator is deprecated?

It's a good question. The existing relevancy evaluator could be kept I think, as that one tries to get an evaluation of whether both answer and context are relevant to the query in the same prompt. Though, we undertook this work in order to improve that one due to the lack of feedback we get on the evaluation — we just get a YES or NO result.
The new evaluators handle answer and context relevancy separately.


// $ExpectError tests can never fail

// $ExpectError
const x: number = 3;

That should fail, but doesn't.

This commit from flow changed the behaviour: https://github.com/facebook/flow/commit/c62d5ebac2ef7881192b760b023ce54bb57140e6
And there is an issue open about it: https://github.com/facebook/flow/issues/5009
Seems rather serious!

Agreed, quite serious. I'd hate to be the one to try and reenable it on this repo. I'd guess the only way to reenable it now would be to grep for warning in the output of flow since it won't exit w/ a non-zero status code :/

Flow recently made unused suppression comments warnings instead of errors. Warnings are not included by default. (You need include_warnings=true in the .flowconfig). I'll look into how this affects running specs on travis.

Made a naive fix for the problem: https://github.com/flowtype/flow-typed/pull/1407 at least it should point to right direction.

@GAntoine it might make sense to run the test suite for all the PRs open at the moment now when the fix is merged.

Yeah that makes sense, though they'll need to rebase first. I'll go through the active ones and let people know.

@gantoine this is still not working: a lot of tests are not failing even though $ExpectError fails to catch an error... See the tests for react-redux_v5 as an example: they should clearly fail but currently they don't.

Ok, actually this works, but because in travis tests are only run on differences, we haven't seen these errors.

yeah would not be fair to fail tests on non-related libdefs.


Change crypto dictionary

Change crypto dictionary in the glossary
from: https://blockspot.io/crypto-dictionary/
to: https://coinmarketcap.com/alexandria/glossary

opened a PR to close this one! https://github.com/yearn/yearn-devdocs/pull/130


Helping the user bring the right things based on the weather

If it's raining, bring an umbrella
If it's sunny, bring suncream
If it's cold, bring a coat

I would like to work on this issue.


Download icon missing from Stories

As of today the download icon no longer appears in Stories, meaning that pics and videos can't be downloaded.

The icon appears for me, but it does nothing.

If you Stories open and use Duplicate Tab, it works in the new tab, so that's a workaround.

I have update the addon yesterday. You can try the latest version to see whether the problem still exists.

Unfortunately the problem is still there.

Unfortunately the problem is still there.

Can you give me a link to reproduce the problem? I can't reproduce it on my end.

Can you give me a link to reproduce the problem? I can't reproduce it on my end.

Here's an example: if you go to https://www.instagram.com/thewarningargentina/ and click on their Stories link, the download icon doesn't appear. If you can't reproduce this, there must be something weird in my Firefox settings that's causing it.
Something has changed, though — I've now found that if I do that and then press Refresh, the icon shows up! So if it's not fixable, I guess I can live with that.

I have the icons without refreshing the tab. If the Firefox add-on version your are using is the latest(1.3.7), I don't know the exact cause of the problem at the moment...

I have the icons without refreshing the tab.

Check the stories, not the highlights. Maybe it's somehow related to the fact that when you open the stories from the account page, the story link looks like this: https://instagram.com/stories/%username%. However, when you open it from your feed, it also shows the numerical ID of the story in the link, like this:

I just checked version 1.3.7, and both the "download" and "open in a new tab" buttons don't work if the link doesn't contain that ID.

@sn3akyb3ar  Oh, I thought there would always be an id. Because even if I open the stories from the account page, there is an id in the link address.  Also, when I click the prev or next button to switch stories, the id changes at the same time. Actually I don't use Instagram very often, so there are a few I may not have come across.

Also, when I click the prev or next button to switch stories, the id changes at the same time

Yes, it does change when you switch stories. But buttons don't appear until you reload the page. Maybe Instagram tests it for different users.

I've updated a new version. Hope it can fix the problem.

That seems to have fixed it. Good job!

Closing this.


bazel-snapshots fails when run with Bazel remote execution

+ bazel run snaptool --config=remote -- diff --out snapshot.json --format=json --stderr-pretty deployed
WARNING: Option 'javabase' is deprecated
WARNING: Option 'java_toolchain' is deprecated
WARNING: Option 'host_javabase' is deprecated
WARNING: Option 'host_java_toolchain' is deprecated
INFO: Invocation ID: 79704985-d849-4078-8faa-b8f991152287
INFO: Streaming build results to: https://foo.bar/invocation/79704985-d849-4078-8faa-b8f991152287
Loading:
Loading: 0 packages loaded
Analyzing: target //:snaptool (0 packages loaded, 0 targets configured)
INFO: Analyzed target //:snaptool (0 packages loaded, 3 targets configured).
INFO: Found 1 target...
[0 / 4] [Prepa] BazelWorkspaceStatusAction stable-status.txt
Target //:snaptool up-to-date:
  bazel-bin/snaptool-runner.bash
  bazel-bin/snaptool
INFO: Elapsed time: 1.910s, Critical Path: 0.79s
INFO: 137 processes: 133 remote cache hit, 4 internal.
INFO: Build completed successfully, 137 total actions
INFO: Running command line: bazel-bin/snaptool diff --out snapshot.json '--format=json' --stderr-pretty deployed
INFO: Streaming build results to: https://foo.bar/invocation/79704985-d849-4078-8faa-b8f991152287
INFO: Build completed successfully, 137 total actions
INFO: Build completed successfully, 137 total actions
/bazel-cache/infrastructure/execroot/infrastructure/bazel-out/k8-fastbuild/bin/snaptool: line 16: ../com_cognitedata_bazel_snapshots/snapshots/go/cmd/snapshots/snapshots_/snapshots: No such file or directory
script returned exit code 127

SNAPSHOTS on line https://github.com/cognitedata/bazel-snapshots/blob/main/snapshots/runner.tmpl.sh#L6 expands to ../com_cognitedata_bazel_snapshots/snapshots/go/cmd/snapshots/snapshots_/snapshots, and seems to be where the problem originates.

This problem only occurs if we run with from_source = True. Running from the latest release, and setting from_source = False provides a workaround.

Closed by #103


Stripe refund handling

Handle refunds issued for Stripe payments in pages/api/webhooks/saleor/transaction-action-request.ts

Hi! Is this feature under development? If not, I'd like to work on it.


l10nized all strings hopefully :-)

Should close #117
Please check @v1r0x
Please use l10n files in future commits!

Very nice! :penguin:
I fixed the two TODOs and translated the context menu. Fixed some minor bugs/missing translations as well.


alignPieces rewritten to be clearer and correct

Investigation of convolution bug suggested an error in the function alignPieces. Rewriting this to be more compact and clearer has fixed the bug.
Also a small bug in convolvePolyDeltas turned up, which this PR fixes.

This fixes issue #13


Use locality_id on locality

To match with backend.

:-/ some reason this has to be merged so quickly? It'd be great to have a chance to ask questions / make suggestions. Also helps learn about the front-end more. I find PRs do that much more than issues tend to.


Improve importing log_step

Instead of importing log_step as in
from brixy import brixy

@brixy.log_step
def step_1():
  pass

it would be nicer to import it like:
from brixy import log_step

@log_step
def step_1():
  pass

released with version 0.2.0


Lenaic/improve e2e

What does this PR do?

When the e2e tests are failing, in order to help diagnosing what’s wrong,

the logs of the failed steps is printed
some additional “diagnostic” steps are run to collect agent status, agent config, etc.
But as the “diagonstic” steps were successful, the collected data was not printed !

With this change, the CI will print the logs of both:

the failed steps and
the “diagostic” steps.

Motivation

Provide more clues to investigate e2e tests failures.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Look at the GitLab logs of a failed e2e job.
It should now contain the output of all the diagnostic “steps” in addition to the output of the failed steps.
Reviewer's Checklist

[X] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[X] The appropriate team/.. label has been applied, if known.
[X] A release note
has been added or the changelog/no-changelog label has been applied.
[X] Changed code has automated tests for its functionality.
[X] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[X] If applicable, docs team has been notified or
an issue has been opened on the documentation repo.
[X] If applicable, the need-change/operator and need-change/helm labels have been applied.
[X] If applicable, the config template
has been updated.

Here is an execution of the e2e tests for this PR: https://gitlab.ddbuild.io/DataDog/datadog-agent/-/jobs/97489537
Unfortunately, as the tests were successful, we cannot see the added logs.


Visual defect when scrolling across text that is longer than a screen width (macOS)

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.87.0 (but this has been happening for a few weeks)
OS Version: macOS Sonoma 14.3

Steps to Reproduce:

Scroll off the edge of the screen
Scroll back to the first column (at a reasonable speed - this doesn't work if you scroll back at snails pace)
The first few columns of text are not visible and only become visible if you click or scroll vertically.

See attached video:
https://github.com/microsoft/vscode/assets/639983/40bd2b18-cac0-474f-a71b-86b81007d17e

Does this reproduce when launching code --disable-gpu ?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Instructions do not mention that git-lfs is required for the KTX-Software submodule

I am just attempting to build cesium-native out for the first time, I cloned the repo onto my machine (Kubuntu 22.04)  but as I initialize the submodules during the clone I had to run:
git submodule update --init --recursive
I got two errors reported on the first pass, but on running again just get the following error:
Aborting
fatal: Unable to checkout 'b84886590e91f850a32334216322d6a43ba37ca6' in submodule path 'extern/KTX-Software'

Thanks @robertosfield, I updated the title of this issue to reflect the need for a doc change. We'd welcome a pull request if you're up for it!

KTX requiring git-lfs is the real problem, the actual library build itself doesn't need it, perhaps KTX-Software team can be pursued to restructure the repo so the software is easier to pull down.

I have created an Issue on the KTX-Software github Issue tracker:
https://github.com/KhronosGroup/KTX-Software/issues/668
Hopefully they will respond positively and create a small libktx repo that doesn't have the crazy footprint and dependency on git LFS.  If they do this then there will be no need to complicate cesium-native clone/build instructions or add a dependency on something that isn't needed for anything other a dependency project having made a poor choice.


Use size_t instead of int where appropriate

Thanks, but we don't want to touch these lines for such cleanup changes.


chore: add format workflow

Codecov Report
Patch and project coverage have no change.

Comparison is base (0b50079) 100.00% compared to head (51d3e19) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##              main      #441   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           25        25
  Lines          649       649
  Branches       250       250
=========================================
  Hits           649       649

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


fix too depth bug

上下限を設けました

Codecov Report

Merging #117 into master will decrease coverage by 0.92%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #117      +/-   ##
==========================================
- Coverage   44.68%   43.76%   -0.93%
==========================================
  Files          39       41       +2
  Lines        3845     4440     +595
  Branches      774      986     +212
==========================================
+ Hits         1718     1943     +225
- Misses       1681     1917     +236
- Partials      446      580     +134

Impacted Files
Coverage Δ

ricochet-robots/index.js
38.8% <0%> (-0.59%)
:arrow_down:

tahoiya/index.js
14.54% <0%> (-1.96%)
:arrow_down:

prime/index.js
17.04% <0%> (-0.86%)
:arrow_down:

achievements/achievements.ts
100% <0%> (ø)
:arrow_up:

tashibot/index.js
62.16% <0%> (ø)

tashibot/prices.js
100% <0%> (ø)

shogi/index.js
19.86% <0%> (+0.71%)
:arrow_up:

achievements/index.ts
59.2% <0%> (+5.69%)
:arrow_up:

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 fe84e19...05a2f27. Read the comment docs.


Bugfix: buffer missing segments

@markqvist This hopefully resolves the issues you were experiencing. I was able to reproduce similar issues and I think they are retry-related. As part of the fix, I added a protected variable to LocalInterface to allow tests to simulate links with constrained bandwidth. It was my first and ignorant crack at it, do feel free to push back if you don't like it.
I am not certain that the problem was just that the retry timer was too short. It could be additional complications due to half duplex or actual lost packets from the physical channel. I'll need to set up a proper LoRa test rig to really see what's going on with that.
In this update

StreamDataMessage now packed by struct rather than umsgpack for a more predictable size
Added protected variable on LocalInterface to allow tests to simulate a low bandwidth connection
Retry timer now has exponential backoff and a more sane starting value
Link proves packet before sending contents to Channel; this should help prevent spurious retries especially on half-duplex links
Transport packet filter no longer filters out duplicate packets for Channel. Duplicates are handled in Channel to ensure the duplicate packet is reproven (in case the original proof packet was lost)
Fixed up tests broken by these changes
Added a low bandwidth buffer test. Since it takes ~2 min to finish, the test is skipped unless RUN_SLOW_TESTS=1 is specified on the command line.

@markqvist I set up a pair of RNodes with separate configs and tested this changeset and I did not have any issues with dropped segments. I'd like to find the root cause, but I'm not sure the juice is worth the squeeze. I suspect something was funky with the umsgpacked message body and trying to maximize MDU utilization.
I tried using 62.5/10/6 to get that 410 bps on-air rate, but for some reason the link would not establish. I am noticing a surprising amount of dropped/not received packets. The lights act as expected, but the packet is not received. This seems to be what happens when the link fails. I guess it's mostly surprising because the radios are sitting less than a foot apart.
At 0.7 Kbps, I was able to establish a link. There were still a few retries each direction, but I guess since I was testing the behavior of Channel and Buffer, that was okay. The initial retry timer wait seemed reasonable and the exponential backoff worked. I used the same test text that you did and it was transferred in its entirety both directions.
As bitrates climb above 1 or 2 Kbps, I no longer notice packets failing to receive. I'm using a pair of genuine Unsigned RNodes (gen 2, 900MHz) and I tried a couple different antennas.

Perfect, that sounds good. 410 bps is absolutely pushing it, since the minimum supported bitrate is actually 500 bps. I temporarily changed DEFAULT_PER_HOP_TIMEOUT to 6 in https://github.com/markqvist/Reticulum/blob/master/RNS/Reticulum.py#L120, and if you haven't pulled that change, I don't even think link establishment will work, since it will time out before they have physically had the time to finish the establishment procedure.
I'm going to merge it now and try it out as well.

Ok, I'm still seeing some strange bevaviour at 410 bps over the air, but I honestly don't know exactly what is going on, and it needs further investigation, since it could even be located elsewhere. At any of the bitrates that are actually supported by Reticulum, things work smoothly, so I don't think we should spend more time on this now.
I will look into it in more depth when I have a chance. Might even be a misconfiguration of CSMA parameters in the RNode firmware at those low bitrates.

From looking at the packet flow, I think something that would help a lot on performance and retries, would be to keep out-of-order packets instead of dropping them, and then trying to fit them into the total sequence, once other packets arrive, since there's a good chance that the actual packet sequences will arrive out of order. Is my understanding correct, that this doesn't happen currently?

I've seen a few of those pop up, but based on the way the protocol currently works, I think the out of order packets are all older packets that the other end resent because because it didn't receive the proof. It would probably be helpful to print the sequence numbers in that message.
The sliding window logic will accommodate out of order packets. Much of the groundwork is laid already--incoming and outgoing packets are sequenced into ring buffers for reassembly and resending, but currently only one packet is allowed at a time and the reassembly logic hasn't been written yet.
But just the same, I am fairly certain that the out of order packets received now are resent packets. I should improve the logging to help make more sense of that.

Ah, that makes total sense then! Just didn't catch that. Thanks for explaining!


Fix OCI build re. psutil package

Problem
psutil failed to install when building the OCI image.
References

https://github.com/crate-workbench/mlflow-cratedb/actions/runs/6766177123/job/18386922080#step:10:855

Ah. It was apparently only happening on aarch64.
#20 112.7       building 'psutil._psutil_linux' extension
#20 112.7       creating build/temp.linux-aarch64-cpython-310
#20 112.7       creating build/temp.linux-aarch64-cpython-310/psutil
#20 112.7       gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DPSUTIL_POSIX=1 -DPSUTIL_SIZEOF_PID_T=4 -DPSUTIL_VERSION=596 -DPy_LIMITED_API=0x03060000 -DPSUTIL_ETHTOOL_MISSING_TYPES=1 -DPSUTIL_LINUX=1 -I/usr/local/include/python3.10 -c psutil/_psutil_common.c -o build/temp.linux-aarch64-cpython-310/psutil/_psutil_common.o
#20 112.7       psutil could not be installed from sources because gcc is not installed. Try running:
#20 112.7         sudo apt-get install gcc python3-dev
#20 112.7       error: command 'gcc' failed: No such file or directory


Need exempla use call Node pleas

Good afternoon, I wanted to clarify, I need an example of calling a node in the timeline, I want to call a scene with animation in the dialog, but for some reason I can't, and unfortunately there are no such examples in the documentation. Thank you in advance.

Hey this discussion might help. Alternatively using signals is always a good way to achieve things.
More documentation will hopefully come once we approach 2.0.


[FEATURE] Map display total results

Description
Display the total amount of users on the map with/without filters, for example

if there were 100 people and with no filters, it would show 100/100
with a filter that only showed 60 people, it could display 60/100

https://linkfree.eddiehub.io/map
Screenshots
No response
Additional information
No response

Hello! Could I be assigned this one? I'd love to work on it 🤩

I've been taking a look at this. A few questions:

I haven't touched anything to do with the map but every time I make a change locally on the map page, I am getting the following error Error: Map container is already initialized.. Seems like a dev only issue but was wondering if you already knew about it. The error goes away if I refresh the page, but it's just a bit annoying when developing.

I had a go at using the component you suggested but I can't find a good place for the component with the current design. I was thinking to create something like this, but I think that I'd need to fix an extra bug as part of this PR:

At the moment, when you deselect a tag, it has no effect on the map. You have to click the Clear/Reset Filters button in order for the map to update. With the above design, I think it would be a bit confusing so I'm suggesting that I should fix this bug as part of this PR. This would mean that when you deselect the tag, it would update the users on the map straight away. We would still have a Clear Filters button on the right hand side in case the user selects all the tags and wants to remove them easily.
What do you think?

Thanks Lucy for the detailed reply 👍

I think this is due to the SSR, maybe @amandamartin-dev knows more?
Maybe for now we can keep it simpler and use the Badge component on the clear filters button? https://github.com/EddieHubCommunity/LinkFree/blob/main/components/Badge.js
Do not worry about the de-toggle (un-toggle?) bug it is being worked on here https://github.com/EddieHubCommunity/LinkFree/issues/5420

@eddiejaoude and @lmac-1  Hey! Thanks for the tag - yup, this will happen only during dev because of the way the updates push the code while you work.  You can just refresh and it will be fine.
One thing to note with the tags is that those counts are inaccurate.  I noted this in the PR when I created v1 of the tags but when you pull the data from the tags API it already comes with counts that are based on all of LF profiles whereas the map data will only pull folks with a location.
I was not sure how to remedy this at that time without an adjustment to the underlying API or some other method.

Thanks @amandamartin-dev - just wanted to check it wasn't a new error.
Good point about tag counts! But we aren't actually using them to calculate the total number of selected users on this page. We are calculating everything from users which is returned from getServerSideProps. This is returning the users that have a location set:
data.users = data.users.filter(
    (user) =>
      user.location &&
      user.location.provided &&
      user.location.provided !== "unknown" &&
      user.location.name !== "unknown" &&
      user.location.provided.toLowerCase() !== "remote"
  );

And thanks @eddiejaoude! I am taking a look at the Badge component and will report back.

Thanks @amandamartin-dev - just wanted to check it wasn't a new error.
Good point about tag counts! But we aren't actually using them to calculate the total number of selected users on this page. We are calculating everything from users which is returned from getServerSideProps. This is returning the users that have a location set:
data.users = data.users.filter(
    (user) =>
      user.location &&
      user.location.provided &&
      user.location.provided !== "unknown" &&
      user.location.name !== "unknown" &&
      user.location.provided.toLowerCase() !== "remote"
  );

True! But perhaps after this issue we should create one to handle the tag counts since with the map user count now visible it might become confusing that the tag counts don't add up to the map count?  Not critical at all and can definitely be handled separately

I was not sure how to remedy this at that time without an adjustment to the underlying API or some other method.

But perhaps after this issue we should create one to handle the tag counts since with the map user count now visible it might become confusing that the tag counts don't add up to the map count? Not critical at all and can definitely be handled separately

yep we can have a separate issue to fix this, I have an idea on how this could be solved - but I don't think it is a blocker for this issue

Yeah I hadn't paid attention so much to this because I didn't have all of the users in my local db. I was just assuming it would total up correctly when all the users were there, but looking into the code a bit more, it looks like it won't.
Definitely interested in the best practice to solve this problem, so will be keeping an eye out on the other issue 😁. Is it #5281?

Is it #5281?

Oh! I just looked at that issue, I'm not sure if it's the same or not, but basically the tag counts would need to not be tied to total profiles for the map to be accurate.  So unclear whether it could be solved in the scope of that issue or would still be handled separately.  Good catch!

Yeah I am wondering if we need a separate issue for the tag issue on the maps page but perhaps there's another one lurking around that I missed!

I think you are good creating it, I know I forgot to make one for it after I noticed and am not seeing one specific to the map either

Definitely interested in the best practice to solve this problem, so will be keeping an eye out on the other issue 😁. Is it https://github.com/EddieHubCommunity/LinkFree/issues/5281?

This one is different. Feel free to raise an issue if you like for the new issue

PR and issue raised 🎉 thanks everyone!

Great collab 🚀


open-completion: version bump to v1.0.3

Bump version to v1.0.3, fixes file splitting bug

Thanks @moshen! :tada:

:beers:


Check location permissions before searching places

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
#1873
✅ Checklist

[x] Github issue details are up to date for people to QA.
[x] I have tested all my changes.

🕵♂ Notes for Code Reviewer
The bug cause that search results do not appear.. It turns out that the autocomplete service (the one that returns the results) is passed a location (in this case the user's) to show the closest results. And then when trying to get the location and it gives an error, the service is not performed.
👯♀ Paired with
"nobody"

PD: We need test this on iOS.

code looks good.
ill let others who run it approve it.

@RaulUrtecho Just tried it on iOS, still seeing the same issue (no search results if location permission is denied):
https://user-images.githubusercontent.com/1284706/172680714-2c6bcf91-f383-4260-8704-3c949f5f51d1.mp4
Logs:

flutter: OnQueryTextChange { query: b }
flutter: OnQueryTextChange { query: ba }
flutter: OnQueryTextChange { query: bal }
flutter: Transition { currentState: SearchPlacesState(PageState.initial, [], false, null), event: OnQueryTextChange { query: bal }, nextState: SearchPlacesState(PageState.success, [], true, null) }
flutter: OnQueryTextChange { query: bali }
flutter: Error getting user location
flutter: Transition { currentState: SearchPlacesState(PageState.success, [], true, null), event: OnQueryTextChange { query: bal }, nextState: SearchPlacesState(PageState.failure, [], true, null) }
flutter: Transition { currentState: SearchPlacesState(PageState.failure, [], true, null), event: OnQueryTextChange { query: bali }, nextState: SearchPlacesState(PageState.success, [], true, null) }
flutter: Error getting user location
flutter: Transition { currentState: SearchPlacesState(PageState.success, [], true, null), event: OnQueryTextChange { query: bali }, nextState: SearchPlacesState(PageState.failure, [], true, null) }

@RaulUrtecho Just tried it on iOS, still seeing the same issue (no search results if location permission is denied):
1877.mp4
Logs:

flutter: OnQueryTextChange { query: b }
flutter: OnQueryTextChange { query: ba }
flutter: OnQueryTextChange { query: bal }
flutter: Transition { currentState: SearchPlacesState(PageState.initial, [], false, null), event: OnQueryTextChange { query: bal }, nextState: SearchPlacesState(PageState.success, [], true, null) }
flutter: OnQueryTextChange { query: bali }
flutter: Error getting user location
flutter: Transition { currentState: SearchPlacesState(PageState.success, [], true, null), event: OnQueryTextChange { query: bal }, nextState: SearchPlacesState(PageState.failure, [], true, null) }
flutter: Transition { currentState: SearchPlacesState(PageState.failure, [], true, null), event: OnQueryTextChange { query: bali }, nextState: SearchPlacesState(PageState.success, [], true, null) }
flutter: Error getting user location
flutter: Transition { currentState: SearchPlacesState(PageState.success, [], true, null), event: OnQueryTextChange { query: bali }, nextState: SearchPlacesState(PageState.failure, [], true, null) }

Yeah unfortunately I have no way to test in iOS. Does it works for you on Android?

@gguij004 could you check the iOS side? I think could be related to the package installation.

Does it works for you on Android?

Yes! I see search results on Android when location permission is set to Deny.

Does it works for you on Android?

Yes! I see search results on Android when location permission is set to Deny.

@buildc0de  can you check again, I added a fix and check on my emulator and it works.

@buildc0de can you check again, I added a fix and check on my emulator and it works.

Yes! It now works on iOS as well 🥳


[MH] rejection-free proposal for the multivariate normal case

This blog post shows how to sample from a truncated (univariate) gaussian proposal for Metropolis-Hasting, so as to avoid rejecting a MH step because the proposed value does not lie on the distribution's support.
This is currently implemented in Turing.
Can we extend this idea to the normal multivariate case ?

Yes, we can extend to the multivariate case. But the kinds of constraints possible is much richer. This is why, even thought Distributions.jl has a truncated Gaussian, it doesn't have a truncated Multivariate gaussian (see https://github.com/JuliaStats/Distributions.jl/issues/480). They couldn't agree what a 'typical' constraint was.
For our case, rectangular constraints are the simplest. It's just a product of many univariate interval constraints. The correction factor would then be the product of the correction factors for each dimension.
A linear constraint that doesn't align with the univariate distributions is also fine. (A constraint of the form a <= X.r <= b.) This is again easy because X.r is univariate Gaussian so the correction factors are again made up of Normal cdf values.
A third constraint type you might be interested in is ||X|| <= a. Again, it is possible to calculate the correction factor though you need to do the eigendecomposition of the covariance matrix. (See https://mathoverflow.net/questions/155829/euclidian-norm-of-gaussian-vectors).
So basically, what kinds of constraints are we interested in supporting?

I think there is a misunderstanding, the issue is not in sampling from a truncated gaussian (even if that's interesting to know how to do that without sampling until constraints are satisfied) but to know how to correct the acceptance ratio of the Metropolis-Hasting algorithm.

Yes @emilemathieu , but the correction factors depend on the type of constraint!

Let me slow down. Suppose we have general constraint set C.  We may or may not be able to compute that probability analytically. It all depends upon the shape of C

True ! For instance, the constraint could be the set of positive semi-definite matrix, for a MH step on a covariance matrix with a Normal proposal.

So you draw the matrix components from a multivariate Gaussian and subsequently constraint the resulting matrix to be positive definite?

Hum I think I said a mistake. But we could have a simplex constraint for instance.

Sure, we could have many constraints! I guess I'm asking which are the important ones? Which ones are so common that we cannot tolerate regular rejection?

That's a good point, I'm trying to think of common constraint on vector random variable.

I'm not sure it's worth spending too much time on this, maybe we should just close it.

Ok let's close this. What we should do is this. If we constantly find ourselves doing MH with variables on a simplex (say) and we notice that proposals keep getting rejected, then we open a new issue asking for the correction factors for that type of constraint. Until then, we might be optimizing prematurely by writing a corrected proposer which never gets used.


README errors

Hi, thanks for your package.
Here are some issues I hit in the README.
I installed with pip install e ..

If I try to use the files in ExampleFiles following the template in the README I get some errors:
import QuantumTomography as qKLib

path = <path/to/ExampleFiles>
t = qKLib.Tomography()
t.importConf(path + "conf.txt')
[rho, intens, fval] = t.importData(path + "data.txt')

I am able to resolve these errors by using the example "conf.txt" and "data.txt" files provided in the README and adding the following to conf.txt:
conf["method"] = "MLE"

It would be nice if using the ExampleFiles ran without errors, and if the issue could resolved as to whether conf["method"] is required in the conf.txt.

If I run:
qKLib.entanglement(rho)

I get:
AttributeError: module 'QuantumTomography' has no attribute 'entanglement'

I can submit a PR if you give me permissions.


Pressing esc key won't close the modal if the shouldCloseOnOverlayClick is set to false

Summary:
It potentially might be a bug or just a question, I have a modal that the shouldCloseOnOverlayClick={false}, obviously clicking on overlay will not close the modal, but pressing on an esc key after that will not close the modal as well. But, opening a modal and pressing the esc key alone without clicking on overlay will close the modal as expected.
Steps to reproduce:

Creates a new react-modal component.
Set component option of shouldCloseOnOverlayClick={false}.
Run server, open the modal, and clicking on the overlay layer.
Press the esc button.

Expected behavior:
The modal should close.

@antonhalim I'm sorry for the delay on this.  The reason this behaves this way is that the keydown handler is associated with the content of the modal rather than the overlay.  Thus if focus isn't on the content, then this handler doesn't fire.
I think we can rethink this, but probably not until version 2.  Moving it to the overlay instead seems to be a better option.  I'll put it on our roadmap for v2.


python311Packages.svg-py: init at 1.4.2, python311Packages.deebot-client: init at 5.0.0

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

6 packages built:

python311Packages.deebot-client
python311Packages.deebot-client.dist
python311Packages.svg-py
python311Packages.svg-py.dist
python312Packages.svg-py
python312Packages.svg-py.dist


Scrolling gesture only works on the edge

I'm noticing that on chat interactions with a long chat post you can't scroll by swiping over chat bubbles. See screenshot from my app.
I've also reproduced this in the Quickstart example.

IMO the expected behavior is that the entire chat canvas is supports the scrolling gesture.

@JoeCotellese
✨Thanks for letting me know the issue!
🎯I'm going to resolve this issue from the upcoming version: 1.0.0-beta.8.
🔔After the release, I'll remind you!

Any updates on this beta 8?

Any updates on this beta 8?

Sorry for the delay on the deployment.
https://github.com/jaesung-0o0/ChatUI/discussions/27
As I announced here, I pause my work until the end of April because of personal issue!
If you use it by forking, you might resolve the issue by 2 ways:

set up frame size of scroll view to fit in the screen.
modify tap gesture or long tap gesture on Message list body

Hi, @JoeCotellese
✨ Thank you for waiting patiently.
🚀 The bug you reported has been fixed and the 8th beta version (1.0.0-beta.8) has been released.


Add /s

@CircuitSacul For the next time please make your commit messages more descriptive.

@CircuitSacul For the next time please make your commit messages more descriptive.

Sorry, I always use squash merging so I don't have to worry about commit messages in branches.


Update couchdb_peruser package for CouchDB 2.0

I tried to set up CouchDB 2.0 with couchdb_peruser enabled. I saw (in
previous email in the user-archive) that it haven't been tested with 2.0. At the
same time, tests are passing but when using CouchDB normally user creation
does not trigger a database creation.
I investigated the logic behind and the mechanisms is only working when
users are added to the node-only _users database. Users added to the
cluster are not watched for systematic database creation.
The previous set up is relatively strange, as user databases (userdb-xxxx)
are added to the cluster but not to the local node (they are sharded).
Previously, couch_peruser relies on couch_changes:handle_db_changes which is
local-node specific and I do not find an equivalent for the cluster.
I hack together an updated version of couch_peruser that spawn_opt an
couch_changes:handle_db_changes for each local shard of the cluster
authentication_db.
Would that approach be ok ?
It there any point in keeping the previous logic working ? (Local users but
clustered user dbs.)
I am pretty new at CouchDB and at Erlang so pardon my basic understanding
of the different mechanisms.

following..

LGFM.
@iilyak, @rnewson, @nickva, could you check this please?

Do not merge this PR just yet.
I need to reproduce and mitigate/fix some issues I had (from memory, crash on initial start-up before cluster set-up) and check that everything is in line on subsequent start-ups.
I will push updates ASAP (probably later today).

@guillett
Thanks for follow up! No worries, leave a note when it will be ready for final testing and merge then.

@kxepal
Thanks, I had another look and I would like some feedback from knowledgable people. I confirm, if the instance is started with peruser enabled and without the underlying user table, it crashes.

I thought that I could watch _all_dbs via couch_changes:handle_db_changes but I can't (at least, I didn't manage).
I wanted to use the same strategy as chttpd_auth_cache  (that is to ping the system every 5 seconds to check if it is ready) but I don't think a plugin like peruser is a place to have such logic.

That is why, I finally simply I amended the logic to disable the plugin when the user database is missing, it generates a [warning] and the configuration change [notice] also contains the reason (_users is missing).

@guillett thank you for stepping up and contributing this! I ran into this recently and was wondering how anyone actually used CouchDB 2.0 without per-user document read authorization.

I am having trouble getting this to work. I've tried replacing the src/couch_peruser directory in the apache-couchdb-2.0.0.tar.gz release with this branch, and compiled couchdb with make release and enabled couch_peruser in Couch's etc/local.ini and restarted my server, but am still not seeing per-user databases being created.

@jacksonrayhamilton Thanks for your message and sorry to hear that you have trouble using the branch.
I haven't tested with the package on CouchDB but only from github master.
Here is what I have done and that seems to work (I have no idea why it is not working with the package):
set -e
set -v
git clone git@github.com:guillett/couchdb-peruser.git
cd couchdb-peruser
git clone https://github.com/apache/couchdb
cd couchdb
./configure --disable-docs --disable-fauxton
cp -R ../src ./src/couch_peruser && cp -R ../test ./src/couch_peruser
make release
./rel/couchdb/bin/couch

In a different shell (sorry that one is a bit dirty):
#!/bin/sh
set -e
set -v
# Should return full config
res=`curl -sX GET http://localhost:5984/_node/couchdb@localhost/_config`
if [[ $res == '{"error":"unauthorized","reason":"You are not a server admin."}' ]]; then
  res=`curl -sX DELETE http://localhost:5984/_node/couchdb@localhost/_config/admins/tom -H "Authorization: Basic dG9tOnRvbQ=="`
  [[ `echo $res|wc -c` -gt 50 ]]
  res=`curl -sX GET http://localhost:5984/_node/couchdb@localhost/_config`
fi
[[ `echo $res|wc -c` -gt 1000 ]]
[[ `curl -sX GET http://localhost:5984/_cluster_setup` == '{"state":"cluster_disabled"}' ]]
[[ `curl -sX POST http://localhost:5984/_cluster_setup \
  -d '{"action":"enable_cluster","username":"tom","password":"tom","bind_address":"<IP_ADDRESS>","port":5984}' \
  -H 'Content-Type: application/json'` == '{"ok":true}' ]]
[[ `curl -sX POST http://localhost:5984/_cluster_setup \
  -d '{"action":"finish_cluster"}' \
  -H 'Content-Type: application/json' \
  -H "Authorization: Basic dG9tOnRvbQ=="` == '{"ok":true}' ]]

curl -X PUT http://localhost:5984/_node/couchdb@localhost/_config/couch_peruser/enable \
   --data '"true"' \
  -H 'Content-Type: application/json' \
  -H "Authorization: Basic dG9tOnRvbQ=="

 curl -X PUT http://localhost:5984/_users/org.couchdb.user:alice -H 'Content-Type: application/json' \
 -d '{"_id": "org.couchdb.user:alice", "name":"alice", "password":"alice", "type":"user", "roles":[]}'

curl http://localhost:5984/_users/_all_docs -H "Authorization: Basic dG9tOnRvbQ=="
curl http://localhost:5984/_all_dbs

I get the expected DB userdb-616c696365.
Can you confirm it is not working for you or send some logs. I will try to give the official 2.0 package a try tomorrow.

Whoops! I forgot to checkout the test branch on your fork. After I did that and recompiled I'm now seeing per-user databases being created.

@jacksonrayhamilton Good to know, I am glad to read that you fixed your issue and than the fix is working for someone else than me.

@guillett
I merged your testbranch
git clone -b test https://github.com/guillett/couchdb-peruser.git
But with this my couchdb service is restart every few seconds. You know why?
eb 21 13:30:58 server.ets.com couchdb[14957]: [info] 2017-02-21T13:30:58.242987Z couchdb@localhost <0.209.0> -------- open_result error {error,eacces} for _users
Feb 21 13:30:58 server.ets.com couchdb[14957]: [error] 2017-02-21T13:30:58.243394Z couchdb@localhost <0.246.0> -------- CRASH REPORT Process  (<0.246.0>) with 1 neighbors exited with reason: no match of right hand value {err
Feb 21 13:30:58 server.ets.com couchdb[14957]: [error] 2017-02-21T13:30:58.244675Z couchdb@localhost <0.203.0> -------- Error starting Apache CouchDB:
Feb 21 13:30:58 server.ets.com couchdb[14957]:     {error,{shutdown,{failed_to_start_child,couch_secondary_services,{shutdown,{failed_to_start_child,auth_cache,{{badmatch,{error,eacces}},[{couch_auth_cache,ensure_users_db_ex
Feb 21 13:30:58 server.ets.com couchdb[14957]: [error] 2017-02-21T13:30:58.246090Z couchdb@localhost <0.212.0> -------- Supervisor couch_secondary_services had child auth_cache started with couch_auth_cache:start_link() at u
Feb 21 13:30:58 server.ets.com couchdb[14957]: [error] 2017-02-21T13:30:58.246350Z couchdb@localhost <0.204.0> -------- Supervisor couch_sup had child couch_secondary_services started with couch_secondary_sup:start_link() at
Feb 21 13:30:58 server.ets.com couchdb[14957]: [error] 2017-02-21T13:30:58.246570Z couchdb@localhost <0.202.0> -------- CRASH REPORT Process  (<0.202.0>) with 0 neighbors exited with reason: {{shutdown,{failed_to_start_child
Feb 21 13:30:58 server.ets.com couchdb[14957]: [info] 2017-02-21T13:30:58.246751Z couchdb@localhost <0.7.0> -------- Application couch exited with reason: {{shutdown,{failed_to_start_child,couch_secondary_services,{shutdown,
Feb 21 13:30:58 server.ets.com couchdb[14957]: [os_mon] memory supervisor port (memsup): Erlang has closed
Feb 21 13:30:58 server.ets.com couchdb[14957]: [os_mon] cpu supervisor port (cpu_sup): Erlang has closed

@katche70 No ideas. Can you dump your config here? What is your cluster setup? Do you have anything fancy set up?

i delete all couchdb files and did a new fresh install. now couchdb service is running fine.
I acticate
[couch_peruser] enable = true
and restarted service. After adding a new user with pouchdb no new db was created.
is ist nessesary to configure cluster or single node?

@katche70 You need to have a cluster set up (I tested with single node cluster and that works).
You can either set up your cluster via Fauxton or use a similar strategy I used in https://github.com/apache/couchdb-peruser/pull/3#issuecomment-279244728 (I replicated what Fauxton send to the server using curl calls).
Currently your console should be spammed by couch_auth_cache every 5 seconds or so.
Once your cluster is ready the spam should stop and you should be able to enable the _peruser module.
If that is still not working:
What is your remote DB with PouchDB ? The local node port or the single cluster port ?
Can you see your added user in the user DB ? What is the full URL of your user document ?

@guillett - thanks for this branch. Can confirm I've got this working too (with PouchDB).
@jacksonrayhamilton - thanks for your input, especially that Debian script - made setting this up much quicker!
I had one weird thing - when I was trying to modify 'local.ini' to set 'couch_peruser' to true it wasn't working. I'd save the file, restart the server and check the config. It would be showing 'false' through Fauxton. I'd go back into the 'local.ini' file and... sure enough the setting was changed back to 'false'. I went through this a few times to make sure I was actually saving the file correctly.
Changing 'default.ini' didn't work either. (Note that any other changes I made to the files would stick - just the couch_peruser flag that was being reset each time).
Anyway, in the end, I manually created a '_users' table, made the settings change in 'local.ini', restarted and the change held correctly. Just leaving this note here in case anyone else comes across the same thing!

Hi @guillett I followed your instructions. but since I need Fauxton, I used the ./configure instead of ./configure --disable-docs --disable-fauxton. Upon make release the build fails. Can you please enlighten me what the problem can be?

@guillett I also tried your instructions But it doesn't seem to work for me. No errors, but no per user databases created either.
I tried both with copying the newly compiled couchdb_peruser plugin (folder name: couch_peruser-2.0.0-RC4-4381-ga9d709714) into my system wide installed stable couchdb instance, and also simply running the newly compiled couchdb. Per user databases won't be created when making new users with either instance of couchdb.
I'm really just a beginner with couchdb, and I don't really understand how it can happen, that such a seemingly simple and basic thing like this (ie. storing data for users that only they can see and modify)  doesn't work.

@emoryy Did you try enabling the plugin only after your _users database was created?
Making it possible to enable this plugin without the _users database seems like it would make it much easier to use.  After or despite that, we should get this merged, as this feature is so important for any application in need of basic security.

@jacksonrayhamilton Yes, I think I already had the _users database.
Now I actually redid the instructions of @guillett to the letter, and it seems to work - but only on that build of couchdb.
What I don't know is how to get it work with the system installed couchdb. Reinstalling it, and simply copying the newly built plugin into its lib folder (/usr/lib/couchdb/lib/) doesn't seem to work.

I managed to run couchdb built with peruser from the test branch as a system service. At first it seemed to work quite well, but then after an hour of not touching it, I noticed that couchdb is using up one of the CPU cores entirely. It also became unresponsive.
I tried to stop and restart the service, but without success. Couchdb doesn't start up anymore. Here is the error log.
The following info may be irrelevant regarding the problem, but this is how I got couchdb work as a system service:
I use Arch Linux, so I downloaded the build files for the official couchdb Arch package.
Then I modified the PKGBUILD according to the instructions of @guillett, and then simply built and installed the package replacing the official one.

👍

Hi, awesome work! I’ve opened a PR of this on couchdb.git since the couch_peruser.git repo was since moved into couchdb.git: https://github.com/apache/couchdb/pull/570

Merged into the new monorepo!
@guillett Please close this PR, as I'm unable to do so.

🚀 Great ! Thanks !


Unable to extract title for reference pages

There are about 20 files for which we cannot find the title.  These do seem to have the div/h2 pattern, but the id="title" identifier is missing.
I think we're correct to start off by looking for the div/h2 element with the known ID.  But, if it isn't found, I think we should fall back on getting any div/h2 element that has absolute positioning.

Fixed in #433

Update: There are some pages that don't have the div > h2 construct.  As another fallback, several of those I inspected do have a  that equates to the title.  I suggest we take the contents of the first h1, and push out a warning if more than one h1 is found.

Fixed in #440.


Add tensor quantization

Checklist

[x] Confirmed that run-checks all script has been executed.
[x] Made sure the book is up to date with changes in this PR.

Related Issues/PRs
Progress towards #464
Changes
Support for static per-tensor quantization.

Added new DType::QFloat
Added backend trait associative type QuantizedTensorPrimitive
Added QTensorOps for quantize/dequantize ops
Added TensorPrimitive enum for float tensors to include float and qfloat (quantized type)

All existing float ops now automatically retrieve the .tensor() (dequantized) before calling the backend implementation on the FloatTensorPrimitive

Added QuantizationStrategy enum with per-tensor affine and symmetric int8 quantization

Note: QAT support should be added in a future PR
Testing
Added unit tests for affine and symmetric per-tensor quantization

Not sure what's up with the wgpu tests, they seem to be failing intermittently even on main
error: test failed, to rerun pass `-p burn-wgpu --lib`

  Caused by:
    process didn't exit successfully: `/home/runner/work/burn/burn/target/debug/deps/burn_wgpu-c73d9b81b38abf9c --color=always` (signal: 11, SIGSEGV: invalid memory reference)

Not sure what's up with the wgpu tests, they seem to be failing intermittently even on main
error: test failed, to rerun pass `-p burn-wgpu --lib`

  Caused by:
    process didn't exit successfully: `/home/runner/work/burn/burn/target/debug/deps/burn_wgpu-c73d9b81b38abf9c --color=always` (signal: 11, SIGSEGV: invalid memory reference)

Working on it


[Bug]: Button Icon End doesn't show on Buttons if it's a multi line button

🕵 Is there an existing issue for this?

[X] I have searched the existing issues

What version of spark are you using?
1.0.0
🐛 What happened?
A bug happened!

Relevant logcat output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@elisa-hery You can verify it by using the button configurator before the fix and check that it doesn't happen anymore after it

Perfect, thank ! I'm moving it to done


Use LDFLAGS to set the default locations in docker

Too many docker users are caught out by the default location for the
app.ini file being environment dependent so that when they docker exec
into the container the gitea commands do not work properly and require
additional -c arguments to correctly pick up the configuration.
This PR simply builds the default locations into the build.
Fix #14468
Reference #17497
Reference #12082
Reference #8941
... amongst others ...
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

It makes the docker gitea binary differ from other build.
Can we just use a wrapper to bypass the config problem? eg, we put gitea binary to /usr/local/bin/gitea-real, and make /usr/local/bin/gitea or /app/gitea/gitea a script:
#!/bin/sh
export GITEA_WORK_DIR=/data/gitea
export GITEA_CUSTOM=/data/gitea/custom
exec /usr/local/bin/gitea-real "$@"

You mean a script like:
https://github.com/go-gitea/gitea/blob/main/contrib/fhs-compliant-script/gitea

Yep, it is more clear, and keeps all Gitea build consistency. My thought is re-design out directory layout inside docker (Maybe both root-docker and rootless-docker).
For example:
We save gitea binary to /usr/libexec/gitea/gitea, and make a wrapper /usr/local/bin/gitea.
Users can only use the wrapper and they always use the correct environment.

It makes the docker gitea binary differ from other build.

This is already the case.
The binaries in the dockers are built specifically for the docker - they're not copied from the "release" binaries that are made by make release. In particular they have an additional build tag that is not provided to the release binaries. They're built with a different version of go on a different os. They're not even static builds.
Docker
https://github.com/go-gitea/gitea/blob/4e8a81780ed4ff0423e3a2ac7f75265e362ca46d/Dockerfile#L10-L11
https://github.com/go-gitea/gitea/blob/4e8a81780ed4ff0423e3a2ac7f75265e362ca46d/Dockerfile#L23
bash-5.1# gitea -v
Gitea version 1.16.0+dev-446-g4e8a81780 built with GNU Make 4.3, go1.17.2 : bindata, timetzdata, sqlite, sqlite_unlock_notify
bash-5.1# ldd $(which gitea)
	/lib/ld-musl-x86_64.so.1 (0x7f76e01db000)
	libc.musl-x86_64.so.1 => /lib/ld-musl-x86_64.so.1 (0x7f76e01db000)

Release Binaries
https://github.com/go-gitea/gitea/blob/4e8a81780ed4ff0423e3a2ac7f75265e362ca46d/Makefile#L634-L638
$ ~/Downloads/gitea-main-linux-amd64 -v
Gitea version 1.16.0+dev-446-g4e8a81780 built with GNU Make 4.1, go1.16.9 : bindata, sqlite, sqlite_unlock_notify
$ ldd ~/Downloads/gitea-main-linux-amd64
	not a dynamic executable

Then what about the snap and other builds?

what about snap and other builds

This change only affects the LDFLAGS for the docker build, in snap and others the binary remains the same (ex, here is snap being built: https://github.com/go-gitea/gitea/blob/main/snap/snapcraft.yaml#L70)

what about snap and other builds

This change only affects the LDFLAGS for the docker build, in snap and others the binary remains the same (ex, here is snap being built: https://github.com/go-gitea/gitea/blob/main/snap/snapcraft.yaml#L70)

I mean, do snap or other builds have similar problems? I know many snap users also meet path & environment problems.
My preference is to make a stable build system, eliminate the differences between builds as much as possible, and never surprise users, if they run gitea xxx they should be always use the correct app.ini.

The wrapping script would need to be different for each variant - I'm not sure that is really much different from just compiling things in correctly.
(This reminds me though that the FHS script could benefit from a very small improvement...)

Another related issue. Adding LDFLAGS doesn't resolve the design problem fundamentally

https://github.com/go-gitea/gitea/issues/17521

Another related issue. Adding LDFLAGS doesn't resolve the design problem fundamentally

 delete a user from command line ignores the -c switch with config file #17521

I think this one is unrelated and is more a problem with: setFlagsAndBeforeOnSubcommands in main.go.

Another related issue. Adding LDFLAGS doesn't resolve the design problem fundamentally

 delete a user from command line ignores the -c switch with config file #17521

I think this one is unrelated and is more a problem with: setFlagsAndBeforeOnSubcommands in main.go.

If we can warn users correctly when they try to use a wrong app.ini, then the problem can be resolved by user them-selves. We can show a friendly guide message to users to teach them how to find the correct app.ini.
The real problem now is: we never warn users, instead gitea tries to do some automatic and "magic" operations for users. This is the fundamental problem in my mind.

The real problem now is: we never warn users, instead gitea tries to do some automatic and "magic" operations for users, which leads to a bigger mistake. This is the fundamental problem in my mind.

Yes, you're preaching to the choir here. I am fully aware that our default paths are not correct for the ways that people use Gitea today.
Gitea was never designed to be dumped in /usr/bin or /usr/local/bin as it is currently compiled. It is currently compiled to do the correct thing if you were to download Gitea and run it from where you downloaded.
We can't change that default because it would be massively breaking for a number of people.
The reality is that no binary you just download from the web would normally be considered to obey the FHS. Things that are meant to obey the FHS usually have to have their source code downloaded and compiled or be in a package.
To that end, I spent a long time creating two options:

The FHS-compliant script
The ability to compile Gitea setting LDFLAGS to compile in the default flags.

Neither of these gained much acceptance - although I understand that Arch uses LDFLAGS.

1. The Filesystem Hierarchy Standard Script
Reasons to use the script:

It's simple and any one can adjust the script to get their defaults as needed
It's clear as to what's happening and the script can remain the same as the binary changes.

Reasons against the script:

You'll need multiple different copies of the script per particular thing to use.
People JUST DON'T USE IT despite it being there for 3 years
If we were to use it on docker we'd have still have to adjust the script.
It may be possible to get out of the exec -a hole to end up writing refs to the actual executable instead of script.
It requires bash.
The user complaints about having to use a script...

It's notable that firefox (at least it used to) required a script like this.
2. LDFLAGS and compiling in the defaults
Reasons to compile things in:

No weird script getting in the way.
The binary is right and looks like any other packaged binary.

Reasons against compiling in:

Each binary is different. Downloading from the website might not work for you anymore.
Each situation we compile for would require a slightly different set of flags and packagers would have to get things correct for their situation.

These two negatives are just the same as any packaged binary though.

My personal suggestion would be that we use LDFLAGS over the script as the script is just not being used. We could provide two different sets of binaries for linux - one obeying the FHS and one with the standard defaults. The docker version would just get the right locations built in.
Snap and other downstream packagers would need to build in the correct paths or use the script as per their own choice.

If you would prefer to use the scripted route then we need to come up with some way to make people use the script.

Maybe we can just improve the gitea's behavior of choosing the app.ini:

Define app.ini candidates: /etc/gitea/app.ini, env defined app.ini, cli defined app.ini

if more than one of these candidates co-exist, do fatal message to tell user to remove wrong app.ini

Only use FHS wrapper inside docker or snap build for cli

Pros: The problem seems to be resolved. For advanced users, they still can control the behavior. For junior users, no surprise to them, if accident occurs (more candidates), they still get enough message to learn how to resolve it.
Cons: (I can not find a bad case now)

It's not just the app.ini it's the workpath too.

It's not just the app.ini it's the workpath too.

If we can get the correct app.ini, we get the correct work path.

For existing instances we can't get correct app.ini anymore except for breaking everything for them by changing behavior. So I agree with @zeripath that using LDFLAGS for docker image gitea binary build  would be best solution here

For existing instances we can't get correct app.ini anymore except for breaking everything for them by changing behavior. So I agree with @zeripath that using LDFLAGS for docker image gitea binary build would be best solution here

Why we can't ? I think we can get the app.ini correctly according the sequence:

get from flag -c
from ENV $GITEA_CUSTOM/conf/app.ini
/etc/gitea/app.ini if it's UNIX like system
current work directory custom/conf/app.ini

For existing instances we can't get correct app.ini anymore except for breaking everything for them by changing behavior. So I agree with @zeripath that using LDFLAGS for docker image gitea binary build would be best solution here

Why do you think can't we break behaviors? We are releasing new versions, we should fix  all strange behaviors.
How do you resolve the problem  (including all non-docker cases) fundamentally?

@lafriks @zeripath
What about my proposal 2: Only use FHS wrapper inside docker or snap build for cli
For example, we put gitea binary in /usr/libexec/gitea-exec, and use a FHS script for /app/gitea/gitea and /usr/local/bin/gitea, the script just do exec /usr/libexec/gitea-exec -c /the-real-app.ini
This solution is simple, and doesn't break existing system, and can be used for snap/apt/deb builds.

About concerns:

You'll need multiple different copies of the script per particular thing to use.
That's the same to multiple builds. It doesn't make things worse. That's gitea's problem.

People JUST DON'T USE IT despite it being there for 3 years
Because no one knows it and most people do not know how to use it. For example, I didn't know it before you told me. But we can use it since it works.

If we were to use it on docker we'd have still have to adjust the script.
Yes, as Q1, gitea's strange behavior forces us to make a choice, split the builds, or introduce scripts.

It may be possible to get out of the exec -a hole to end up writing refs to the actual executable instead of script.
Well, I don't what the real problem is .... some examples for bad cases?

It requires bash.
Not bash, sh is enough. And we already have it, every POSIX system has it.

The user complaints about having to use a script...
They won't know it is a script ..... many Linux programs work this way.

Codecov Report

Merging #17501 (388307a) into main (9defddb) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #17501      +/-   ##
==========================================
+ Coverage   45.54%   45.56%   +0.01%
==========================================
  Files         809      809
  Lines       90059    90059
==========================================
+ Hits        41019    41035      +16
+ Misses      42484    42473      -11
+ Partials     6556     6551       -5

Impacted Files
Coverage Δ

models/unit/unit.go
41.09% <0.00%> (-2.74%)
:arrow_down:

modules/queue/queue_channel.go
95.00% <0.00%> (-1.67%)
:arrow_down:

models/issue_comment.go
52.69% <0.00%> (+0.28%)
:arrow_up:

models/notification.go
65.65% <0.00%> (+0.86%)
:arrow_up:

modules/notification/ui/ui.go
62.31% <0.00%> (+1.44%)
:arrow_up:

modules/queue/workerpool.go
53.05% <0.00%> (+1.90%)
:arrow_up:

modules/notification/mail/mail.go
38.23% <0.00%> (+2.94%)
:arrow_up:

models/gpg_key_common.go
64.51% <0.00%> (+4.83%)
:arrow_up:

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 9defddb...388307a. Read the comment docs.

Closed in preference of #17846


Formatting time of 'statistic taken'

I tried to make the time more readable.

I'll hope I got it right. I'm new to GitHub...


How to train with non-square images without resizing

I'm looking for a way to train the model on rectangle images. Any advice appreciated!

I think it's possible as a model for this project


Fix element append for group in CustomConfigEntires

This is fixing an issue where credentials for pipeline inputs are not showing on the "execute pipeline" dialog.


Add integer From/TryFrom impls for Month

Closes #345.

Forgot to update the required status checks when I bumped the MSRV. I'll do that in a bit.

All suggestions addressed. Please let me know if you want me to squash the PR into a single commit.

Actually just thought of the fact that the only time the error part of map_or_else is when the value is zero. I can handle that myself.
Right now I'm trying to figure out how to run the CI. Apparently it's disabled by default for first-time contributors, but I don't see a way to explicitly run it.

No idea how to get CI to run, since the button that GitHub docs say should be there isn't. Regardless I've tested this locally in a few ways and am confident enough to merge it.


M3U Initial setup issue

Hello,
I'm going through my initial setup on the server and copy and pasted my M3u address. I hit next and it's spinning, but not loading properly. I've waited about 30 mins now.
Server (please complete the following information):

OS [Windows
Arch [Intel 64 bit
-V2 binary

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [Windows
Browser [Chrome
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Please post the xTeVe Log (Console) and the first 5 lines of the M3U. Please remove the URLs.

Hi there,
I am having the exact same issue. Not sure how to view the xTeVe log. Here's my m3u URL:
http://mystreamingwebsitehere.xyz:80/get.php?username=xxxxxxxx&password=xxxxxxxx&type=m3u_plus&ouput=hls

Something is wrong with the contents of the M3U.