沃兹沃思 is also Wadsworth

沃茲沃思 沃兹沃思 [Wo4 zi1 wo4 si1] /Wordsworth/Wadsworth/
沃茲沃斯 沃兹沃斯 [Wo4 zi1 wo4 si1] /Wordsworth/Wadsworth/

Unfortunately yes.  That's annoying because it's the example I used in the readme and on the HTML and Gemini pages (which, as a simple introduction, could really do with an example name that has only one English meaning, although I picked Wordsworth because I'd written an article about the project in the yearbook of my old college in Cambridge which has a Wordsworth room).  Perhaps it's OK to leave the readme as-is on the assumption that the software could be set to display the first definition only (e.g. the horrible "3-line mode" on my Android apps which I wrote only because people kept asking for it, which requires the English to be as short as possible and generally should not be used without proofreading: it's still an improvement if it displays a name, even if it might be the wrong name, rather than breaking it down into smaller words)


[DOC] Bulk endpoint is not properly documented.

At present bulk endpoint is documented only in [1] and documented only about creating users in bulk. In addition to this updating and deleting in bulk needs to be documented. For more info refer to [2].
Sample bulk delete request:
curl -v -k --user admin:admin --data '{"failOnErrors":2,"schemas":["urn:scim:schemas:core:1.0"],"Operations":[{"path":"/Users/5d4ff8f6-e714-4138-aa6f-fa2443cd09e0","method":"DELETE"},{"path":"/Users/1f9ed88b-d0c2-4fda-af32-54a3a8a73316","method":"DELETE"}]}' --header "Content-Type:application/json" https://localhost:9443/scim2/Bulk
[1] - https://docs.wso2.com/display/IS570/apidocs/SCIM2-endpoints/index.html#!/operations#BulkEndpoint#createBulkUsers
[2] - https://malalanayake.wordpress.com/2013/05/28/scim-bulk-endpoint-operations-in-wso2-identity-server/

related: #4693

Need update the doc related to PATCH and PUT operations as well.
Refer https://github.com/wso2/product-is/issues/6887 to see how PATCH works right now.


Add a welcome bot

Is your feature request related to a problem? Please describe.
github action to add  a message to greet when contributor makes his/her first PR and first issue .
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@avinashkranjan can i work on this ?

Sure Go Ahead @Ankita297


FPFile array empty on onActivityResult

I'm not able to reproduce this issue myself but some users are experiencing it.  Sometimes we get an IndexOutOfBoundsException because the FPFile array is empty when we return from the FilePicker activity.  My onActivityResult() method is pretty much the same as in the getting started guide.
@Override
public void onActivityResult(int requestCode, int resultCode, Intent data) {
    if (requestCode == Filepicker.REQUEST_CODE_GETFILE) {
        if (resultCode != Activity.RESULT_OK) {
            //Result was cancelled by the user or there was an error
            return;
        }

        // Filepicker always returns array of FPFile objects
        ArrayList<FPFile> fpFiles = data.getParcelableArrayListExtra(Filepicker.FPFILES_EXTRA);

        // Get first object (use if multiple option is not set)
        FPFile file = fpFiles.get(0);  // <- java.lang.IndexOutOfBoundsException: Invalid index 0, size is 0

    }
}

This happened on an HTC One running android4.4.2
Thanks

Seeing a similar issue on my Nexus 6.  It happens every time I try to grab an image from the camera or gallery.

interesting.  What kind of phone do you have?  I can't reproduce it on any of our devices.  I only see it in testing.

Looks like they're not working on this.  I just contacted support and got the following response.
Sarajane Stevens (Filestack)
Aug 2, 14:18 CST
Hi Tim,
Unfortunately our resources do not allow us to investigate this further currently. We hope to add an Android Developer to our team who can address these issues in the near future.
Thank you for your patience,
Sarajane

Nexus 5X, running Android 6.0.1.  It's one of the  current Google reference
devices, so I definitely wouldn't expect issues.
Joel
On Aug 2, 2016 3:40 PM, "Tim Hepner"<EMAIL_ADDRESS>wrote:

interesting. What kind of phone do you have? I can't reproduce it on any
of our devices. I only see it in testing.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Ink/filepicker-android/issues/101#issuecomment-237070254,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABrL6PYht0pfh90Qrmtemk_DcxxBbEJ7ks5qb8dngaJpZM4I5967
.

Unfortunately I didn't manage to reproduce this issue. I have tried on Nexus 5X (Android 7.0), Samsung Galaxy S5 (Android 6.0.1) and Samsung Galaxy S4 Mini (Android 4.4.2).
Nevertheless I have posted a fix (087e000b753574f5e21446a62dced84df44d1072) which should help. It makes sure that successful get file(s) operation always returns a non-empty list of the FPFile objects. It will be availabe in the 3.10.0 release.
If you ever enounter this issue again please reopen this and provide all possible details (Android version, device logs with stacktrace, snippet from the code you use to retrieve this list).


Docs linked in README give 404 error

The doc link in the README badge points to https://silvanshade.github.io/lspower/lspower, which gives a 404 error when opening.

I realize that lspower is deprecated now, so I'll close this.


[Function Request] Codeunit 5777 VerifyFieldNotChanged set to global

Dear Microsoft Team,
could you please set the function VerifyFieldNotChanged to a global one?
Otherwise we have to copy the function to our codeunit. I think a lot of developers would need it either because it is a general one.

Hi sharkhpoenix,
This function has already been made external from another request. You should be able to view the change in the preview builds.


Number input

What was changed
Add a new NumberInput component with units and max props.

Why?
For numbers

Looks good, although I'm wondering if we should just extend our existing <Input /> to take a type="number" prop. What do you think?

So I thought about that too but Candace's designs keep it as a normal input (allows string). Generally input type="number" sucks and it's better to use a normal input.


treewide: Fix or comment where fetchFromGitHub fetches a commit which is not on a branch on the specified repo

Motivation for this change
https://github.com/NixOS/nixpkgs/issues/20836#issuecomment-767380571
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110857 run on x86_64-linux 1

2 packages marked as broken and skipped:

linuxPackages_hardkernel_4_14.acpi_call
linuxPackages_hardkernel_latest.acpi_call

2 packages failed to build and are new build failures:

linuxPackages-libre.acpi_call: log was empty
myrica: log https://termbin.com/7qn4

25 packages built:

gr-ais
hdl-dump
libretro.snes9x
linuxPackages.acpi_call (linuxPackages_5_4.acpi_call)
linuxPackages_4_14.acpi_call
linuxPackages_4_19.acpi_call
linuxPackages_4_4.acpi_call
linuxPackages_4_9.acpi_call
linuxPackages_5_10.acpi_call (linuxPackages_latest.acpi_call)
linuxPackages_hardened.acpi_call
linuxPackages_latest-libre.acpi_call
linuxPackages_latest_hardened.acpi_call
linuxPackages_latest_xen_dom0.acpi_call
linuxPackages_latest_xen_dom0_hardened.acpi_call
linuxPackages_lqx.acpi_call
linuxPackages_testing_bcachefs.acpi_call
linuxPackages_xen_dom0.acpi_call
linuxPackages_xen_dom0_hardened.acpi_call
linuxPackages_zen.acpi_call
paperless
python37Packages.nmigen-soc
python38Packages.nmigen-soc
python39Packages.nmigen-soc
snipes
usync

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110857 run on x86_64-linux 1

2 packages marked as broken and skipped:

linuxPackages_hardkernel_4_14.acpi_call
linuxPackages_hardkernel_latest.acpi_call

2 packages failed to build and are new build failures:

linuxPackages-libre.acpi_call: log was empty
myrica: log https://termbin.com/7qn4

25 packages built:

gr-ais
hdl-dump
libretro.snes9x
linuxPackages.acpi_call (linuxPackages_5_4.acpi_call)
linuxPackages_4_14.acpi_call
linuxPackages_4_19.acpi_call
linuxPackages_4_4.acpi_call
linuxPackages_4_9.acpi_call
linuxPackages_5_10.acpi_call (linuxPackages_latest.acpi_call)
linuxPackages_hardened.acpi_call
linuxPackages_latest-libre.acpi_call
linuxPackages_latest_hardened.acpi_call
linuxPackages_latest_xen_dom0.acpi_call
linuxPackages_latest_xen_dom0_hardened.acpi_call
linuxPackages_lqx.acpi_call
linuxPackages_testing_bcachefs.acpi_call
linuxPackages_xen_dom0.acpi_call
linuxPackages_xen_dom0_hardened.acpi_call
linuxPackages_zen.acpi_call
paperless
python37Packages.nmigen-soc
python38Packages.nmigen-soc
python39Packages.nmigen-soc
snipes
usync

@ofborg build linuxPackages-libre.acpi_call

@ofborg build linuxPackages-libre.acpi_call

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110857 run on x86_64-linux 1

1 package failed to build and are new build failure:

linuxPackages-libre.acpi_call: log was empty

26 packages built:

gr-ais (gnuradio-ais)
gnuradio-with-packages
hdl-dump
libretro.snes9x
linuxPackages.acpi_call
linuxPackages_4_14.acpi_call
linuxPackages_4_19.acpi_call
linuxPackages_4_4.acpi_call
linuxPackages_4_9.acpi_call
linuxPackages_5_10.acpi_call
linuxPackages_hardened.acpi_call
linuxPackages_latest-libre.acpi_call
linuxPackages_latest_hardened.acpi_call
linuxPackages_latest_xen_dom0.acpi_call
linuxPackages_latest_xen_dom0_hardened.acpi_call
linuxPackages_lqx.acpi_call
linuxPackages_testing_bcachefs.acpi_call
linuxPackages_xen_dom0.acpi_call
linuxPackages_xen_dom0_hardened.acpi_call
linuxPackages_zen.acpi_call
paperless
python37Packages.nmigen-soc
python38Packages.nmigen-soc
python39Packages.nmigen-soc
snipes
usync

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110857 run on x86_64-linux 1

1 package failed to build and are new build failure:

linuxPackages-libre.acpi_call: log was empty

26 packages built:

gr-ais (gnuradio-ais)
gnuradio-with-packages
hdl-dump
libretro.snes9x
linuxPackages.acpi_call
linuxPackages_4_14.acpi_call
linuxPackages_4_19.acpi_call
linuxPackages_4_4.acpi_call
linuxPackages_4_9.acpi_call
linuxPackages_5_10.acpi_call
linuxPackages_hardened.acpi_call
linuxPackages_latest-libre.acpi_call
linuxPackages_latest_hardened.acpi_call
linuxPackages_latest_xen_dom0.acpi_call
linuxPackages_latest_xen_dom0_hardened.acpi_call
linuxPackages_lqx.acpi_call
linuxPackages_testing_bcachefs.acpi_call
linuxPackages_xen_dom0.acpi_call
linuxPackages_xen_dom0_hardened.acpi_call
linuxPackages_zen.acpi_call
paperless
python37Packages.nmigen-soc
python38Packages.nmigen-soc
python39Packages.nmigen-soc
snipes
usync


Changed NUnit argument prefix from '/' to '-'.

This according to nunit documentation.
http://www.nunit.org/index.php?p=consoleCommandLine&r=2.6
Also renamed file with incorrect capitalization to be able to build on Linux.

@samvik Good catch! :+1:
Since Windows support both hyphen and slash, maybe it would be better to simply change the argument to a hyphen?

That would be the most clean solution. I'm all for that. Just wasn't sure if that would introduce any side effects on windows.

@samvik Good thinking! Just update the PR when you have time and I'll merge it :smile:

Hi @samvik, please when you have the opportunity update PR and rebase against latest and we'll look at merging this.

I should be up to date with develop now.

@samvik merged! Thanks :+1:


Add custom exception type feauture

Summary
We would like to be able to add custom exception types to our errors that are sent to sentry.
Motivation
Our errors have different types and we see these particaular types in sentry like *erros.errorString and *status.statusError.

Frankly, we are not so interested in an underlying error type here. We would like to be able to see the type we provided, for example like Internal error, Timeout error, Batch exceeded error.
Additional Context
These types are determined due to the following code when the exception is constructed itself.
event.Exception = []Exception{{
		Value:      cause.Error(),
		Type:       reflect.TypeOf(cause).String(),
		Stacktrace: stacktrace,
	}}

As you can see from here exception's type is predetermined for us and there is impossible to customise it.
As a straightforward way, that would be great to send error type along with error in sentry.CaptureException(err, errorType) as an option. Or it can be an option func WithErrorType func(err error) string that determines the type depends on the error. It that option func is missing, we can use the default behaviour like reflect.TypeOf(cause).String(). These are just some ideas at the top of my head.
Could we please discuss it?

Hi @mariaefi29!
What version of the SDK are you using? From the code snippet above, reflect.TypeOf(cause).String() suggests v0.5.1 or earlier. We've changed how error chains are reported since them, updating to v0.7.0 may improve your experience.
Could you please provide a code snippet with:

an example of how one of your error types is defined,
what you see in Sentry, and
what you would like to see instead

Hi @rhcarvalho!
Thank you for the provided information!
Yes, you are right, we are using v0.5.1. Let me please explore the new version a bit and I will get back to you!

Hi @rhcarvalho!
I have upgraded sentry to the latest version v0.7.0. However, I have experienced the same issue.

In sentry code your determine exception now like:
event.Exception = append(event.Exception, Exception{
			Value:      err.Error(),
			Type:       reflect.TypeOf(err).String(),
			Stacktrace: ExtractStacktrace(err),
		})

So you predetermine the type for us and there is nothing we can to do to change it.
As you can see on the attached print screen, we see 3 error types:

*errors.errorString type. This happens when we send just usual error from errors.New()
*echo.HTTPError type. This error is from http server echo
*status.statusError. This error occurred from gRPC server.

For us error type is not so important here (we use tags to divide errors from grpc and http servers), but it is highlighted. For example, if we wanted to classify errors yourself, we can't do that.
We would like to see highlighted something more valuable what we can defined ourselves. For example, we encounter "response timing exceeded" error. So highlighted in blue we would like to see Response Timing Error.
Like in your tutorial you can see RestrictedIPAddress err type:

@mariaefi29 the behavior you are describing is how Sentry works in every* platform.
The exception in the example screenshot above is Python code, has type RestrictedIPAddress and was raised in <module-name> in <function-name>.
Similarly, one of your custom Go errors is of type *status.statusError, in <package-name> in <function-name>.
The second line/subtitle has the indicator of severity level and textual description of the error.
This is how the Sentry UI is built (title, subtitle, message): getsentry/sentry:src/sentry/static/sentry/app/utils/events.tsx
And this is how the culprit is built (the subtitle for errors): getsentry/sentry:src/sentry/culprit.py

* There are few platform-specific customizations.
Sentry UI

For us error type is not so important here (we use tags to divide errors from grpc and http servers), but it is highlighted.

I agree with you many times the error type is not the most important info. But sometimes having the error/exception name front and foremost is useful.
See https://github.com/getsentry/sentry/issues/17837. It points out the problem, but, since we can't just change it for everyone, there's no clear solution other than providing some project settings knob to flip the lines or some other design tweak.
If you have specific ideas on what behavior you want, please comment on https://github.com/getsentry/sentry/issues/17837 and/or file a new issue, or contribute a PR. Note that the more general feature of setting your own title etc would involve an addition to the event ingestion API, changes to getsentry/sentry and SDKs.
Workaround

We would like to see highlighted something more valuable what we can defined ourselves. For example, we encounter "response timing exceeded" error. So highlighted in blue we would like to see Response Timing Error.

Until Sentry supports custom title, subtitle and message, one workaround that you can use is to change your events in BeforeSend to change the fields (type, value, etc) to your liking.
https://docs.sentry.io/error-reporting/configuration/filtering/?platform=go
Note that you can do much more than filter events, you can change events to your heart's content :)
Event fingerprinting

For example, if we wanted to classify errors yourself, we can't do that.

If by classify you meant grouping, then that's covered by fingerprints. If you use the SDK to set your own fingerprints you can determine how Sentry groups issues.
https://docs.sentry.io/data-management/event-grouping/
https://pkg.go.dev/github.com/getsentry/sentry-go?tab=doc#Scope.SetFingerprint

I'm going to close this considering that the original request,

We would like to be able to add custom exception types to our errors that are sent to sentry.

can be done with BeforeSend today:
sentry.Init(sentry.ClientOptions{
	BeforeSend: func(event *sentry.Event, hint *sentry.EventHint) *sentry.Event {
		event.Exception[0].Type = "custom type"
		return event
	},
})

Alternatively, for more granular control, the same effect can be achieved with an event processor on the scope:
sentry.WithScope(func(scope *sentry.Scope) {
	scope.AddEventProcessor(func(event *sentry.Event, hint *sentry.EventHint) *sentry.Event {
		event.Exception[0].Type = "custom type"
		return event
	})
	sentry.CaptureException(errors.New("Some Now Error"))
})

@rhcarvalho
Thank you very much for such a detailed and helpful response! We appreciate it so much!
I believe we can work with this for now! Have a good day!

should be in docs or readme

For anyone else coming to this thread: you should be cognizant that the Sentry SDK seems to unroll wrapped errors and as such if you want to manipulate the name that shows up you will want to access the element at the top of the event stack:
e.Exception[len(e.Exception)-1].Type = "custom type"

Referencing e.Exception[0] will update the name on the bottom of the stack which is likely not what you want (and ironically, has a much larger chance now of being a useful error type).

A bit old, but If you implement the Error interface in your type (or you have a custom type for your errors) the name of your type will show as title in the Sentry UI. You'll see something like .
For us was enough, and you just capture and send your custom error type with sentry.CaptureException(err).

Thank you, everybody! I have changed the company and in my team we don't use sentry anymore. But if we do, I know where to go to for valuable advice! Thank you!


Add css gradient to sites

Hey Juho, been a while 👋
Hope survivejs and the webpack work is going well! I just launched a new side project using color joe again. Loved every bit of it :)
Cheers,
Moe

Thanks. Here's my newest project: React Finland. A little design video.

Oh man your design skills have improved a ton!! So well done 👍
Also love the idea of a screen capture. I've never done that before 🤔

@moeamaya We coded the design with a friend. I did the underlying information architecture and structure and then he designed on top of that. There's GraphQL etc. involved. It's a neat stack for building static sites fast. I can connect you if you want.

Ahh I see.
But I'm still a Ruby guy at heart so haven't jumped into js static site world at all. Sticking with Middleman for now. Thanks for offering to connect tho!

@moeamaya Ok, get in touch when it becomes relevant and I'll walk you through my stack. 👍


UI layer needs to be persistent

The UI layer needs to act more like the tilemap cache. It's a place where you can draw pixel data into but also need to explicitly tell it when to clear, unlike the other buffer data which continues be reset on each draw cycle.

The only persistent layer is the Tilemap Cache. This is no longer needed.


update for purescript 0.11

This needs to wait until following packages get new releases:
purescript-node-buffer
purescript-node-path
purescript-node-streams
purescript-js-date

👍 Thanks!


[Spec] Write implementation considerations

Things like republishing optimization, handling scale, integrating with DNS, etc.

A few more:

Without historical resolution, add warning to not rotate off keys that you wish to be verifiable for a long time
Add note on independent verifiability of DID records (no need to trust gateways for anything except types)
PQC risk
Rate limiting and PoW challenge

add node on why '#0 is the first key, talk about being conscious of key id size


Invalid Video Type Error in AutoShorts (Using OllamaAIGen)

Hello,
I encountered an issue when using AutoShorts with the OllamaAIGen AI type. While generating a video script for a "news short" on sport cars, everything works well up until the video generation step, where I receive an error:
F:\AI_Projects3\auto-shorts\node_modules\auto-shorts\dist\index.js:170
            throw Error("Invalid video type!");
                  ^

Error: Invalid video type!
    at genVideo (F:\auto-shorts\node_modules\auto-shorts\dist\index.js:170:19)
    at genVideoWithAI (F:\auto-shorts\node_modules\auto-shorts\dist\index.js:90:18)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async cli (F:\auto-shorts\node_modules\auto-shorts\dist\cli.js:429:18)

Node.js v20.8.1

And when i change to GPTAIGen iget this error:

Invalid JSON data: Unexpected token 'T', "TODO" is not valid JSON
F:\auto-shorts\node_modules\auto-shorts\dist\index.js:140
        throw new Error("Invalid JSON data!");
              ^

Error: Invalid JSON data!
    at genVideo (F:\auto-shorts\node_modules\auto-shorts\dist\index.js:140:15)
    at genVideoWithAI (F:\auto-shorts\node_modules\auto-shorts\dist\index.js:90:18)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async cli (F:\auto-shorts\node_modules\auto-shorts\dist\cli.js:429:18)

I would appreciate any assistance or guidance on how to resolve this issue.
Thanks in advance!

Before I start, I would like to apologize for the late message. I have been working on a new version (tentatively v0.2.0) with solving your issue in mind. This is a known issue and I have experienced it myself.
First of all, the current way the AI works in my code is it expects a specific structured output; however, AI models (LLMs) tend to hallucinate and provide incorrect structured output. I need to improve the way this is handled and I am reworking the AI script generation in v0.2.0 which should, at least, attempt to fix this issue.
What I believe has happened in your case is the LLM model has provided an incorrect type with the incorrect fields for the types. It may have some correct info in the script but the code may not have seen due to the incorrect type (hence the Invalid video type error). I am reworking the way the codes asks AI for the script and reworking how the code handles to invalid JSON.
I know this may not be the answer you were expected. If you want to try the video generation capabilities, you can copy the JSON output of the AI response from the console and put into a separate JSON file. Here you can fix the JSON file with a valid video type. It should be type: 'topic'
You can run this command to read a JSON file instead of asking AI for script: npx auto-shorts --jsonFile [file]
Finally, GPTAIGen failed since I have not implemented the OpenAI API in v0.1.0. I am adding OpenAI API support to v0.2.0.
Thank for your time and interest in this project. Once again I apologize for the late message.

Thanks for the reple @alamshafil
I cant wait for  v0.2.0.
I've tested npx auto-shorts --jsonFile [file] and got another error:
Error: Error: JSON data is missing required "text" field!
    at TopicVideo.checkJson (F:\auto-shorts\node_modules\auto-shorts\dist\types\topicVid.js:21:19)
    at TopicVideo.generateVideo (F:\auto-shorts\node_modules\auto-shorts\dist\types\topicVid.js:28:14)
    at genVideo (F:\auto-shorts\node_modules\auto-shorts\dist\index.js:151:17)
    at genVideoWithJson (F:\auto-shorts\node_modules\auto-shorts\dist\index.js:120:18)
    at cli (F:\auto-shorts\node_modules\auto-shorts\dist\cli.js:423:52)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node.js v20.8.1


bubblewrap build - path not found, even though it exists

Describe the bug
I'm trying to build it, but he says he's not finding his way, but he doesn't talk about what is the Android SDK or the JDK.
And the two paths are right in the settings I tested typing in the CMD the paths exist, I downloaded the files recommended by your README doc.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser chrome

can someone help me?

This looks like another instance of #147. Can you confirm? I've been trying to repro that, but without success. On your case, I wonder if the space in Progream Files is the culprit.

@andreban
It can't be space as it copies these folders to the root of disk C but he still says he didn't find it even without having to go through the program folder.

problem solved for me, conclusion is at: #147


Fix 3 bugs with results

Changes
Okay it's one PR with 3 fixes BUT they are in different commits! And also - this is much more reasonable than my first attempt (https://github.com/tektoncd/pipeline/pull/2465)

Me 🐱: I fixed it! Review my giant PR where I also moved params and results and touched nearly every file!
Vincent 😺: I think you can fix it without all that refactoring, maybe merge that first?
Me 😡: Then I will have to duplicate everything! NOOOOOOOO
Vincent 😺: Sometimes a bit of duplication is worth it
Me 😡:  FINE I WILL TRY IT RELUCTANTLY
tries it
actually needs no additional duplication at all
Me 😳: ... perhaps I should have tried that first

Lesson: try the quicker fix first and THEN refactor
Okay so here are the 3 things I'm trying to address:
(To review separately plz look at the individual commits https://github.com/tektoncd/pipeline/pull/2471/commits 🙏 )
1. Use the same Deps logic in v1alpha1 and v1beta1
Sometimes the PipelineTask that Deps is being executed on is actually
v1beta1 instead of v1alpha1 and the old Deps function, which doesn't
account for Results, is being called.
This PR duplicates the logics so the Deps function is the same.
After #2410 we'll be able to assume we're always using the v1beta1 types
and will not need the logic in both places and can avoid bugs like this.
It also duplicates the DAG test logic which is the closest thing Deps()
currently has to a set of unit tests.
2. Allow results to contain underscores
When results parsing was implemented, the set of allowed characters
wasn't made to match the rest of our substitutions. This duplicates the
set of characters though hopefully we can eventually consolidate this
logic.
I discovered this when trying to use the kaniko task in the catalog
https://github.com/tektoncd/catalog/blob/v1beta1/kaniko/kaniko.yaml
3. Determine correct graph when params and results are mixed 🥄
This was partially addressed in #2387 however the example from the
bug (#2387) was using runAfter, and it should be possible to determine
the correct graph without runAfter. The logic that was determining the
graph was returning an error if any of the substitutions present in a
string along with a result were not results. Now we will instead ignore
these substitutions. We might want to revisit the validation to make
sure that invalid results substitutions are still caught.
Fixes #2464
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[n/a] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Fix 3 bugs with results:
- Determine correct graph when results variable replacement is mixed with other types
- Allow results replacement to work with all valid characters
- Use the same graph logic when using embedded Pipeline specs vs referring to Pipeline CRDs

/lgtm

Fixes #2463


Escape < in unpkg URL

Tools like codepen don't like that non-escaped URL. This converts the < to %3C

Thanks!


ui update: clicking subscribers information toggles Subscribers tab

This pull request impacts the stream_edit.js file in zulip/web/src, updating ui functionality so that clicking a stream subscriber information div toggles the Subscriber tab in the right panel. I did not deviate from the request in the issue documentation.
Fixes: https://github.com/zulip/zulip/issues/32035

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

It looks like this PR adds an accidentally created git submodule called zulip; can you avoid that?

@timabbott I'll look into directly targeting a more semantic CSS class and remediate the submodule issue! Thank you for the input.

Was trying to fix my fork but accidentally closed this, will make a new pull request, sorry if this causes any inconvenience.


Unreleased Resource while using  OkHttpClient.socketFactory()

Among the suggested solution for Untagged socket detected issue , we find the use SocketFactory you coud check the implementation here.
The problem that I faced now is that the created socket didn't seem's to be released by OkHttpClient.
Do this issue create a Security Vulnerabilities ?

The socket won't be released until the connection or client is closed.  See docs on closing a client here http://square.github.io/okhttp/3.x/okhttp/
IF you want further answers please post a question on stackoverflow

@yschimke thanks.
The posted link is just the Okhttp doc home page could you please fix it to point to the right page :].


The first line of my code always has this error, why is that, and I am new to LSP-related and Erlang?

Hi @imLaoYang, by looking at the stacktrace I suspect you are using an outdated version of Erlang/OTP, which has no erl_features:configurable/0 function, which was introduced in OTP 25.1. But I believe we should show a more appropriate message on startup, instead. Thanks for reporting.


Rescue OpenSSL::SSL::SSLError for write and write_multi

While on version 4 of the redis gem, we had a monkey patch to rescue SSL_read: shutdown while in init errors as suggested here: https://github.com/redis/redis-rb/issues/1174#issuecomment-1412993295
This worked fine until we upgrade to redis version 5 and our patch wasn't being applied anymore. We recently have been seeing: SSL_write: shutdown while in init (notice that it's write instead of read). I realized that the redis-client code was rescuing SSL errors for the read: https://github.com/redis-rb/redis-client/blob/master/lib/redis_client/ruby_connection.rb#L102
But it wasn't doing it for write. This PR adds rescuing of OpenSSL::SSL::SSLError to write and write_multi.

I think this has been affecting a small number of Sidekiq users since 7.0. 🙁 but I’m happy we found it.


Restart component if the connection to server was lost

Doesn't look correct, really. The idea behind handling {'EXIT', Pid, _} is keeping track of client session workers. Therefore, we need to handle 'EXIT' from exmpp_component and exmpp_session as different cases.


Verification failed when solving a horn antenna using mesh file created by Gmsh.

i meet some problems when simulation a horn antenna by Gmsh and palace.I can't figure out if it's a problem with the mesh or the model.
The simulation model is composed of a copper horn antenna feeded by a waveport,and airbox outside as an Radiation boundary,see the attachment model.
The error is :
Verification failed: (lambda.real() > 1.0 / (1.0 - 1.0e-2)) is false:
--> Computed wave port mode is or is very close to being evanescent

Hi @keheheke, thanks for sharing your mesh and input file. The first issue is with your model/mesh. The mesh on the wave port face does not conform to the horn boundary, you can see that the triangles discretizing the outer box lie on top of and intersect the triangles for the edge of the horn domain. This needs to be fixed in your CAD model.

Another note is that if you are applying PEC boundary conditions to the surface of the horn, you don't need to mesh the inside. However, it should not hurt to much in this case and so I imagine fixing the above mesh issue should allow your simulation to run.
Finally, I noticed that the version of Palace you are using from Weisim is quite outdated. You would be strongly recommended to use the main branch or most recent release, this includes bug fixes for wave ports specifically. This should build fine on WSL if you are using a Windows machine, or if you need access to a separate Linux machine you could use a public cloud provider like AWS.

Hi @keheheke, thanks for sharing your mesh and input file. The first issue is with your model/mesh. The mesh on the wave port face does not conform to the horn boundary, you can see that the triangles discretizing the outer box lie on top of and intersect the triangles for the edge of the horn domain. This needs to be fixed in your CAD model. Unfortunately I don't have any examples of antennas for you, but you might be able to learn something from the CPW examples with wave ports here. One option is to use the OpenCASCADE kernel in Gmsh and use the Fragment operation in the API (I think this is Coherence or BooleanFragment in the .geo syntax) to ensure the boundary embedding is correct.

Another note is that if you are applying PEC boundary conditions to the surface of the horn, you don't need to mesh the inside. However, it should not hurt to much in this case and so I imagine fixing the above mesh issue should allow your simulation to run.
Finally, I noticed that the version of Palace you are using from Weisim is quite outdated. You would be strongly recommended to use the main branch or most recent release, this includes bug fixes for wave ports specifically. This should build fine on WSL if you are using a Windows machine, or if you need access to a separate Linux machine you could use a public cloud provider like AWS.

Hello, do you have a tutorial on building Palace in Windows?

Hi @keheheke, thanks for sharing your mesh and input file. The first issue is with your model/mesh. The mesh on the wave port face does not conform to the horn boundary, you can see that the triangles discretizing the outer box lie on top of and intersect the triangles for the edge of the horn domain. This needs to be fixed in your CAD model. Unfortunately I don't have any examples of antennas for you, but you might be able to learn something from the CPW examples with wave ports here. One option is to use the OpenCASCADE kernel in Gmsh and use the Fragment operation in the API (I think this is Coherence or BooleanFragment in the .geo syntax) to ensure the boundary embedding is correct.

Another note is that if you are applying PEC boundary conditions to the surface of the horn, you don't need to mesh the inside. However, it should not hurt to much in this case and so I imagine fixing the above mesh issue should allow your simulation to run.
Finally, I noticed that the version of Palace you are using from Weisim is quite outdated. You would be strongly recommended to use the main branch or most recent release, this includes bug fixes for wave ports specifically. This should build fine on WSL if you are using a Windows machine, or if you need access to a separate Linux machine you could use a public cloud provider like AWS.

thanks a lot, i fixed the geometry of my model by the 'Boolean Fragment'， then i can keep the mesh conform on the face and box, finally it can be solved.
also, i used old version of palace integrated by Welsim at the windows system. i will keep learning and figure more about palace.

@keheheke Great to hear! I will close this issue now but feel free to reopen if you have further questions.

@sebastiangrimberg
hello,recently,I have a problem when using Palace to solve a Rectangle waveguide,  I want to get the Insertion loss(S21) .
The cut off frequency of the  waveguide is 15GHz,
if I set the start frequency <15GHz ,such as 10GHz, it will be error like the picture:
if I set the start frequency >15GHz ,such as 16GHz, the simulation will run successfully:
However, i need to get the S21 parameter at from 10GHz to 20GHz ,even the wave energy will be evanescent, is there any solution ？

@sebastiangrimberg
@sebastiangrimberg
hello,recently,I have a problem when using Palace to solve a Rectangle waveguide, I want to get the Insertion loss(S21) .
The cut off frequency of the waveguide is 15GHz,
if I set the start frequency <15GHz ,such as 10GHz, it will be error like that:
<Verification failed: (lambda.real() > 1.0 / (1.0 - 1.0e-2)) is false:
--> Computed wave port mode is or is very close to being evanescent (位 = (9.9999999973809139e-01,0.0000000000000000e+00))!>
if I set the start frequency >15GHz ,such as 16GHz, the simulation will run successfully:
However, i need to get the S21 parameter at from 10GHz to 20GHz ,even the wave energy will be evanescent, is there any solution ？

Hi @keheheke, thanks for your question. In general I'm not sure if it makes sense to try to drive a wave port below the cutoff frequency of the propagating mode, so I do not know what the expected result for S21 is in this case. However, there have been many recent improvements to wave ports which should at least allow your simulation to run below cutoff (< 15 GHz), even as recently as last week with #264. I would suggest as a place to start you build and run Palace from main instead of the outdated version it appears you are using. It appears to me that you are at least using the code from before https://github.com/awslabs/palace/pull/192 (merged Feb. 2024) which included some major upgrades to the wave port boundary mode solver.

Hi @keheheke, thanks for your question. In general I'm not sure if it makes sense to try to drive a wave port below the cutoff frequency of the propagating mode, so I do not know what the expected result for S21 is in this case. However, there have been many recent improvements to wave ports which should at least allow your simulation to run below cutoff (< 15 GHz), even as recently as last week with #264. I would suggest as a place to start you build and run Palace from main instead of the outdated version it appears you are using. It appears to me that you are at least using the code from before #192 (merged Feb. 2024) which included some major upgrades to the wave port boundary mode solver.

@sebastiangrimberg ,Thanks a lot,i will seek help to build the latest version for better features.


CSV upload: send user a confirmation email on successful upload

Problem statement
Users would like to get a confirmation email when a CSV is successfully uploaded.
What you need to know
Our existing daily email setup could probably be repurposed to fire when a user has a successful upload.
Acceptance criteria

[ ] When a user successfully submits a file, they get an email telling them that it was uploaded.
[ ] Uses our standard email template
[ ] Email copy lets a user know the file was a success.
[ ] Email copy tells user the filename of what they uploaded
[ ] Email copy includes top-level RS info about upload: ID, # of results uploaded, ...
[ ] Email copy links to log in/to the submission history

To do

[ ] ...

Closing as Uploader is moving to SimpleReport


Set CXX standard using target properties

This is a better (more cmake way) way of setting the cxx standard that using CXX compiler flags directly

note that there are some places in the CI where the cxx standard is set by hand and I have not modified them in this PR because I was not sure what the CI system does to run the tests, but these should be adjusted to make sure the LIBCDS_CXX_STANDARD flag is set as well before this PR is merged.
build/CI/VASEx-CI-2/cds-libs:gcc-6-cxxflags:       -march=native  -std=c++14
build/CI/VASEx-CI-2/cds-libs:gcc-7-cxxflags:       -march=native  -std=c++1z
build/CI/VASEx-CI-2/cds-libs:gcc-8-cxxflags:       -march=native  -std=c++17 -Wmultistatement-macros
build/CI/VASEx-CI-2/cds-libs:clang-4-cxxflags:       -stdlib=libc++ -Wdocumentation -std=c++14
build/CI/VASEx-CI-2/cds-libs:clang-5-cxxflags:       -stdlib=libc++ -Wdocumentation -std=c++1z
build/CI/VASEx-CI-2/cds-libs:clang-6-cxxflags:       -stdlib=libc++ -Wdocumentation -std=c++17
build/CI/VASEx-CI-2/cds-libs:clang-7-cxxflags:       -stdlib=libc++ -Wdocumentation -std=c++17
build/CI/VASEx-CI/cds-libs:gcc-6-cxxflags:       -march=native -std=c++14
build/CI/VASEx-CI/cds-libs:gcc-7-cxxflags:       -march=native -std=c++1z
build/CI/VASEx-CI/cds-libs:gcc-8-cxxflags:       -march=native  -std=c++17 -Wmultistatement-macros
build/CI/VASEx-CI/cds-libs:clang-4-cxxflags:       -stdlib=libc++ -Wdocumentation -std=c++14
build/CI/VASEx-CI/cds-libs:clang-5-cxxflags:       -stdlib=libc++ -Wdocumentation -std=c++1z
build/CI/VASEx-CI/cds-libs:clang-6-cxxflags:       -stdlib=libc++ -Wdocumentation -std=c++17


Added additional tests

Resolved Add Test Issue by making existing tests more efficient and adding additional tests in commits

Thank you for your PR, definite improvements!


Pug not working

Good day, basically i dont get the template transformed to html.

Im using Parcel, parcel-plugin-svelte, typescript, and pug.

Used a svelte config and is done, maybe parcel took that file, i also installed node-css and node-sass as dev dependencies, which i tend to use in other projects along with this package, I am using vscode, but i dont think that changes anything, thanks for the great work!


Blocked items not showing on the dashboard with "Blocked" field

Describe the bug
The "Blocked" field that comes by default hidden for the work items has been enabled and selected as the way to tag work items that are blocked (we're not using the tags field). Unfortunately blocked items identified this way are not showing up in the blocked tab of the dashboard, but the ones identified with the field tags as "blocked" they do appear.
For the four charts of the Blockers tab of the dashboard I realized:

Current Blocked Items chart: the ones being tagged with Tags and also with the Blocked field, they both appear here.
The ones just tagged with the field "Blocked" don't show up on the Days Lost, Blocked Frequency or MTTU charts.

To Reproduce
Steps to reproduce the behavior:

Set the field "Blocked" as "Yes".
Once the work item has no longer a blocker, set the field "Blocked" as "No".
Continue working on the work item until it reaches the "Closed" state.
Refresh the data and check the blocked tab of the dashboard.

Expected behavior
Blocked items using the "Blocked" field as "yes" and cleared to "no" at some point in the process, should also appear in the dashboard, not only the ones that use the Tags.
Screenshots
Here an example:

The work item is set as a blocked item with the "Blocked" field:

One day later the work item is unblocked and the field "Blocked" is set as "No":

Additional context
Same behavior described as in this other ticket, but unfortunately still getting the same problem as the user described on the ticket: https://github.com/nbrown02/FlowViz/issues/21

Thanks Marcos - let me look into this tonight and get back to you!

Thanks for the quick response Nick, I appreciate it!
Sure, let me capture that info here:

The process template that I'm using is Agile (hope using the Scrum one is not the only way to get it, otherwise I got my answer already haha)

And the field is the standard one, I selected it from the list of available fields:

This is how an user can see it to report a blocker:

Just a side note, we use the "blocked" field instead of the tags because we do have a column in our boards to report blocked issues. And since the only way to tag them is either using tags or this field, we decided to create a rule that is automatically defining the field as "yes" when it is moved into that blocked column (aka state) and it's moving it back to "no" once the work item is moved into another different column. Therefore, it is the system rule who is actually changing the value of the field automatically (I've also try to change it manually myself and still the same result).

Let me know if you'd like to know more info or to test something on my end.

So replicating that setup I still see the same:

Can you share the work item form for User Story and your states?

Sure, here it is the user story form (we do use the same field on bugs as well):

And these are the states we're using:

Sorry - can you show me the states in the process template. I need to mimic as close to your setup as possible...

Sure! Here we go:

Ok so part of the issue I can already see is the states and state categories isn't setup correctly. You shouldn't have a process template that goes out of state categories once work starts. It's going Proposed -> In Progress -> Proposed which isn't how ADO should be setup (and probably why the data is not working).

Thanks for pointing that out. I created a "blocked" state under the "In Progress" state category and kept the same configuration as before. Now the issues are showing up on the charts when using the default field "blocked" as well.

In the MTTU chart I still see a 0 though, but I think that makes sense since I tested all this in less than an hour. I expect longer average blocked times to be reflected on the chart as soon as I start working with real data.

Thanks a lot for you time and support Nick!

Yeah that will be the case with just dummy data to check it works - phew! glad we got there in the end! If you have the time, don't forget to leave a review on the ADO marketplace :)


Revert "remove blas_openblas feature"

This reverts commit 8a342a59db41833e720970e67174d3cb4c4b3500.
it was premature to remove it. The hotfix that required this change has been reverted.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Documentation needs to say that refreshAuthLogic needs to return the axios instance

Thank for you this package. Very useful. First of all, having to use skipWhileRefreshing: false is required for the desired behavior of the package, and I'd urge you to make this the default behavior. Other people seem to have suggested this already, and you have promised to make it so. Thank you for that. Please make it happen. 👍
Secondly, documentation is unclear. It needs to mention that refreshAuthLogic needs to return the axios instance:
const refreshAuthLogic = (failedRequest: any): Promise<any> => {
  return axios.post(...).then(...);
}

The return is missing from the documentation and leads to errors.

Hi @thomergil, thanks for submitting the issue.
Yes I'm aware that skipWhileRefreshing: false is required and I plan to change it as soon as possible in the v3 of the library.
Please, understand this is something I do in my free time while I'm working on other projects/libraries. If you'd like to fast-forward the development process, please consider contributing if that's something you'd be able to do. I'd be more than happy to do a code review & accept any pull requests on this package.
When it comes to the documentation, there's no return statement because of how the arrow functions work. When only one statement is executed and there's no wrapping curly braces {} the statement return type will be returned automatically. Although it's correct, I agree that the function can be written in {} and returned so the people seeing it will actually realise that the return is necessary for the library to work.

I agree with @thomergil because I am faced with the same error. I resolved it only after reading this issue.

@SerhiyRomanov me too

I plan to include this change in v3.0.0 [PR #105].

Done, merged and published in #111.


Problem on Maximize Window

Issue Type: Bug
The Window Chrome should maximize normally but, the bug seems to be like a electrons bug that happens when the frame window is false and you make your own customizable frame (Electron Frameless), i already tried fix this issue in my own application i have developed but i had no success. It would be great if you guys can fix this electrons problem.
 Does that "fix" it?

@bpasero  Yes, it did. Thanks for helping. One last question, why does it happen? Is it a compatibility problem with electron and windows 10 1903? Thanks a lot again

@didiokener sorry, I did not quite follow the bug description. Are you saying the maximize button is just not working?

I think I have the same problem (with dual screens):

Press the maximize button with window in screen 2 (right)
Screen “maximizes” to screen 1 (left)

Maximize button is still there instead of what should be the restore button
I can still drag the window around at this new size; as though it is not maximized but simply resized the the screen size.

Using Window's aero snap (dragging the window to the top of the screen) on screen 2 maximizes it, but it renders over the task bar (I have the taskbar at the bottom with autohide)

Native solves these problems, but I like the look of custom so much better!

@wongjn If this is the same issue, then this is a duplicate of https://github.com/microsoft/vscode/issues/81102
I will close as duplicate but if @didiokener feels these are different, we can re-open

@wongjn That`s it, @wongjn described better than me, but in my case it does the same problem with one screen


Region tags on AWS CDK constructs

Not all services and features are available in all AWS regions. Whether it be community driven or programmatically validated it would be nice to have some insight into whether a construct has been validated to work in a particular region and some sort of grading system for how well it works

Great idea! I think if we were to provide this kind of information, it should probably be surfaced programmatically based on the L1/L2 constructs or top-level CDK modules used in the library. This might require adding some kind of metadata to be included in the JSII assembly, or creating some kind of separate tool that determines this information automatically.
This is probably a good candidate for a RFC!

It may be beneficial to compare against the available CloudFormation resource provider schemas for a good baseline.  I do think that some human verification may be required for 'non CloudFormation' based factors such as code in Lambda functions that calls out to AWS or external APIs.


File to File mounting fails

This mount solution, which actually mounts a file to a file, doesn't work on every filesystem.
Error:
mounting "localpath" to rootfs "dockerpath" caused "not a directory".

Hi @unrl,
According to Docker's documentation, it is correct to mount file as a volume:
https://docs.docker.com/engine/tutorials/dockervolumes/#/mount-a-host-file-as-a-data-volume
Have you checked on other images if mounting file as a volume works for you?

Hi,
I don't know why, but it works now. Btw I'm using a compose.yml. Thanks for your support!
vpn:
image: mobtitude/vpn-pptp
container_name: vpn
ports:
- "1723:1723"
privileged: true
volumes:
- /mnt/docker/vpn/chap-secrets:/etc/ppp/chap-secrets


add consent date field in account creation page for eproms

address these stories:
https://www.pivotaltracker.com/story/show/150119490
https://www.pivotaltracker.com/story/show/150118994
these are changes specific to EPROMs

allow staff to add/edit consent date at account creation
change consent date to study consent date for EPROMs
change display for "withdrawn" consent status
minor bug fix to remove duplicate ID in the footer HTML
NOTE  these changes are dependent on changes in the persistence file. this PR will need to go out with those changes.  persistence file PRs:
https://github.com/uwcirg/ePROMs-site-config/pull/52
https://github.com/uwcirg/TrueNTH-USA-site-config/pull/46

adding the timezone specification.  will re-open this when i am done.


xAxes type time: strange result

Hello,
I try to generate a graph with the option type: 'time' but the result is strange...
See the result
Thanks for your help

The time format is wrong, should be 'YYYY-MM' (not 'YYYY-mm') (fiddle). M is for month, m for minutes (docs).

Thank you very much, it works well now!! Surely a bad habit with php :)


PR feedback follow up for manual install

Follow up to PR feedback that came in after https://github.com/GoogleContainerTools/kpt-config-sync/pull/1455 was merged

/lgtm

/assign @janetkuo


Release 0.4 versions

What is being addressed
Update versions for this release

/test-force-approve


Happy New Year decoration

Happy New Year decoration

website
TG
twitter
posts

https://www.figma.com/file/qhmlIKVNDNUFfdkOZqhvnR/👊🏻-bro_n_bro-team?type=design&node-id=7979-111091&mode=design&t=qSKUhpjhxLBhCL99-4
@prevetal

twitter updated


Left/Right fix

For locale/messages.properties file (the en_US locale), at line 51,

By clicking arrow ⧁ by the left of a Line

Here, "left" should be replaced by "right" to match the layout of lines in the Text Block section.

You're right, thanks. Will be fixed in the next release.


#25 Extends host with additional path eg. /hostPath, example url: you…

#25 Extends host with additional path eg. /hostPath, example url: yourHost:9009/hostPath/v1/endpointName
Fixes https://github.com/CreateAPI/Get/issues/25

I suggest adding a baseURL parameter to replace the existing host, port and isInsecure configuration options:
let baseURL = URL(string: "localhost:9009/yourname")
let absoluteURL = baseURL?.appendingPathComponent("/v1/endpointName")

I think it should cover your scenario and many more.

A new baseURL parameter available in Get 0.7.0.


perf(util): cache regex result for URL path(s)

Made it faster!
hono - org x 708,830 ops/sec ±3.48% (83 runs sampled)
hono - trie-router(default) x 800,532 ops/sec ±4.11% (65 runs sampled)

@yusukebe
I think, this PR would make pathFromURLCache extremely large, is that a problem?

Hi @usualoma !
It's just for better performance. It is related to this issue #282 . I want to make it as fast as possible.
In this pathFromURLCache case, how about "cache only matched path".
diff --git a/src/utils/url.ts b/src/utils/url.ts
index 9753c54..9838d29 100644
--- a/src/utils/url.ts
+++ b/src/utils/url.ts
@@ -59,9 +59,12 @@ export const getPathFromURL = (url: string, params: Params = { strict: true }):
   if (path) return path

   const match = url.match(URL_REGEXP)
-  path = match ? match[1] : ''
-  pathFromURLCache[url] = path
-  return path
+  if (match) {
+    path = match[1]
+    pathFromURLCache[url] = path
+    return path
+  }
+  return ''
 }

 export const isAbsoluteURL = (url: string): boolean => {

@yusukebe
Me too!

I want to make it as fast as possible.
I have confirmed #282. I too think it needs to be optimized.

However, I think that pathFromURLCache would be content with the following.
I think this is not the intention.
{
  "http://example.com/search?q=a": "/search",
  "http://example.com/search?q=b": "/search",
  "http://example.com/search?q=c": "/search",
  "http://example.com/search?q=d": "/search"
}

As for getPathFromURL, could it be optimized in the following way?

RegExpRouter is faster than the master branch with this patch.
TrieRouter is faster than the previous version of getPathFromURL, but a little slower than the master branch.

commit 2e2d4433840cc71b22e9d9001db9c18cecbcdca1
Author: Taku Amano<EMAIL_ADDRESS>Date:   Tue May 31 08:43:49 2022 +0900

    POC: Optimize request.url

diff --git a/src/hono.ts b/src/hono.ts
index 8abbf57..66bdf5b 100644
--- a/src/hono.ts
+++ b/src/hono.ts
@@ -4,7 +4,7 @@ import type { Env } from './context'
 import type { Result, Router } from './router'
 import { METHOD_NAME_ALL, METHOD_NAME_ALL_LOWERCASE } from './router'
 import { TrieRouter } from './router/trie-router' // Default Router
-import { getPathFromURL, mergePath } from './utils/url'
+import { mergePath } from './utils/url'

 declare global {
   interface Request<ParamKeyType extends string = string> {
@@ -181,10 +181,12 @@ export class Hono<E = Env, P extends string = '/'> extends defineDynamicClass()<
   }

   private async dispatch(request: Request, event?: FetchEvent, env?: E): Promise<Response> {
-    const path = getPathFromURL(request.url, { strict: this.strict })
     const method = request.method

-    const result = this.matchRoute(method, path)
+    const result = this.matchRoute(
+      method,
+      this.strict ? request.url : request.url.replace(/\/(?=\?|$)/, '')
+    )

     request.param = ((key?: string): string | Record<string, string> | null => {
       if (result) {
diff --git a/src/router/reg-exp-router/node.ts b/src/router/reg-exp-router/node.ts
index b613927..8729f49 100644
--- a/src/router/reg-exp-router/node.ts
+++ b/src/router/reg-exp-router/node.ts
@@ -67,7 +67,7 @@ export class Node {
           : ['', '', LABEL_REG_EXP_STR]
         : token === '/*'
         ? ['', '', TAIL_WILDCARD_REG_EXP_STR] // '/path/to/*' is /\/path\/to(?:|/.*)$
-        : token.match(/^\:([^\{\}]+)(?:\{(.+)\})?$/)
+        : token.match(/^\:([^\{\}]+)(?:\{(.+)\})?(?:$|\?)/)

     let node
     if (pattern) {
diff --git a/src/router/reg-exp-router/trie.ts b/src/router/reg-exp-router/trie.ts
index 21752fa..7b126d7 100644
--- a/src/router/reg-exp-router/trie.ts
+++ b/src/router/reg-exp-router/trie.ts
@@ -52,6 +52,6 @@ export class Trie {
       return ''
     })

-    return [new RegExp(`^${regexp}`), indexReplacementMap, paramReplacementMap]
+    return [new RegExp(`^https?:\/\/[a-zA-Z0-9\-\.:]+${regexp}`), indexReplacementMap, paramReplacementMap]
   }
 }
diff --git a/src/router/trie-router/node.ts b/src/router/trie-router/node.ts
index 12e47dd..ff0bf94 100644
--- a/src/router/trie-router/node.ts
+++ b/src/router/trie-router/node.ts
@@ -56,7 +56,7 @@ export class Node<T> {

     // eslint-disable-next-line @typescript-eslint/no-this-alias
     let curNode: Node<T> = this
-    const parts = splitPath(path)
+    const parts = splitPath(`https://dummyhostname${path === '*' ? '/*' : path}`)

     const parentPatterns: Pattern[] = []

diff --git a/src/utils/url.ts b/src/utils/url.ts
index 9a112d3..e6a1cb2 100644
--- a/src/utils/url.ts
+++ b/src/utils/url.ts
@@ -3,9 +3,10 @@ const URL_REGEXP = /^https?:\/\/[a-zA-Z0-9\-\.:]+(\/?[^?#]*)/
 export type Pattern = readonly [string, string, RegExp | true] | '*'

 export const splitPath = (path: string): string[] => {
-  const paths = path.split(/\//) // faster than path.split('/')
-  if (paths[0] === '') {
-    paths.shift()
+  const paths = path.match(/^https?:\/\/[a-zA-Z0-9\-\.:]+|(?<=\/)([^/?#]*)|\?.*/g) || []
+  paths.shift()
+  if (paths.length >= 1 && paths[paths.length - 1].startsWith('?')) {
+    paths.pop()
   }
   return paths
 }


java.lang.NullPointerException: Attempt to invoke virtual method 'void android.media.MediaCodec.queueInputBuffer(int, int, int, long, int)' on a null object reference

java.lang.NullPointerException: Attempt to invoke virtual method 'void android.media.MediaCodec.queueInputBuffer(int, int, int, long, int)' on a null object reference
1 | at androidx.camera.core.VideoCapture.a(SourceFile:147)
2 | at androidx.camera.core.VideoCapture$1.run(SourceFile:1)
3 | at android.os.Handler.handleCallback(Handler.java:739)
4 | at android.os.Handler.dispatchMessage(Handler.java:95)
5 | at android.os.Looper.loop(Looper.java:148)
6 | at android.os.HandlerThread.run(HandlerThread.java:61)
I got an error with 1.0.0-alpha06 when take video, I have no idea to resolve ? pls help.

Getting the same error with the same version when the fragment is destroyed during video recording.

Getting the same error with the same version when the fragment is destroyed during video recording.

how to resolve it, i got a lot of errors on my online app....

Unfortunately, could not find any solution

Thanks for opening this issue. A few questions that can help us fix it:

What device are you seeing this in?
What sample are you trying to run?
Did you modify the sample in any way?

Did you modify the sample in any way?
I am modify the demo to take video.
I think, this bug can be reproduced on all devices, start record video, without stopping the video recording, just exit the fragment will appear

This repo is used to track issues with the samples. If you have any questions related to the usage of the library, please use StackOverflow (tag android-camerax) or start a thread in the developer forums.

camera X is not good


fnm: 1.35.0 -> 1.35.1

Description of changes
https://github.com/Schniz/fnm/releases/tag/v1.35.1
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 249477 run on aarch64-darwin 1

1 package built:

fnm


Markdown appearing in code box on "Writing custom shaders" Wiki page

Referring to the tutorial "Writing custom shaders" https://github.com/Microsoft/DirectXTK/wiki/Writing-custom-shaders,  Markdown was inserted into the Html.  It appears in the code box that follows the instruction:
In Game.cpp, add to Render just before the call to Present:
I'd include an example but since it is rendering the raw Markdown, it turns into formatted text here.  I'm sure that you will not have any problem seeing the issue.

Thanks. It was three ticks to open but only two to close :(


getting errors on npm install

getting alot of errors when trying to npm install on v3.0.0-rc.0
you can see complete log of this run :
https://paste.ubuntu.com/p/dVQv3fS9Gz/
i tried with node V12 and V13 on windows 10 and ubuntu

I'm getting the same errors as the OP, here is a shortened version:
Error 1:
npm WARN tar ENOENT: no such file or directory, open '~/coreui-free-bootstrap-admin-template/node_modules/.staging/request-1a2d42e9/index.js'
...
[lots more errors like this]
...
npm WARN tar ENOENT: no such file or directory, open '~/coreui-free-bootstrap-admin-template/node_modules/.staging/lodash-6a94ce82/lodash.min.js'

Error 2:
npm ERR! code E404
npm ERR! 404 Not Found - GET<EMAIL_ADDRESS>npm ERR! 404
npm ERR! 404  '<EMAIL_ADDRESS>is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'coreui-free-bootstrap-admin-template'

Steps I followed:
$ git clone git@github.com:coreui/coreui-free-bootstrap-admin-template.git
$ cd coreui-free-bootstrap-admin-template
$ git checkout v3-next
$ npm run build-clean
$ npm run build

Environment:
MacOS Mojave 10.14.6
$ npm --version
6.13.4
$ npm version
{
  '@coreui/coreui-free-bootstrap-admin-template': '3.0.0-rc.0',
  npm: '6.13.4',
  ares: '1.15.0',
  brotli: '1.0.7',
  cldr: '35.1',
  http_parser: '2.8.0',
  icu: '64.2',
  llhttp: '2.0.1',
  modules: '72',
  napi: '5',
  nghttp2: '1.40.0',
  node: '12.14.1',
  openssl: '1.1.1d',
  tz: '2019c',
  unicode: '12.1',
  uv: '1.33.1',
  v8: '7.7.299.13-node.16',
  zlib: '1.2.11'
}

Upgrading to node 13.7.0 and re-running npm run build  fixed the first errors regarding npm WARN tar ENOENT no such file or directory,  however the second error message is still there.  Additionally there are few deprecation warnings, that should probably be resolved before releasing the 3.0.0 version.
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@coreui%2fchartjs - Not found
npm ERR! 404
npm ERR! 404  '<EMAIL_ADDRESS>is not in the npm registry.

I should clarify, that though the install function didnt have the ENOENT error, the npm run build command did have some issues (see below).  I think basically because of the 404 issue, it prevented continuing to install the rest of the dependencies.
$ npm run build

><EMAIL_ADDRESS>build /Users/jameswilson/App/ProcesoElectronico/coreui-free-bootstrap-admin-template
> npm-run-all build-clean --parallel css js copy --sequential build-vendors

sh: npm-run-all: command not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR<EMAIL_ADDRESS>build: `npm-run-all build-clean --parallel css js copy --sequential build-vendors`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.

@KraToS-zz @jameswilson
<EMAIL_ADDRESS>was set private by mistake. Sorry for the inconvenience.
It should work fine now.

Thanks @xidedix , this fixed it for me. Cheers, have a great week.

thanks for fixing this
but is it possible to have asidebar and sidebar like demo version ?

I'm seeing issue running npm install and npm run build on the current release as well as the downloaded zip
running within a homestead environment but as a plain HTML
`vagrant@homestead:~/code$ npm install
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents/node_modules/rc):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ENOTEMPTY: directory not empty, rmdir '/home/vagrant/code/node_modules/fsevents/node_modules/.rc.DELETE/node_modules'
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path<EMAIL_ADDRESS>npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open<EMAIL_ADDRESS>npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/vagrant/.npm/_logs/2020-08-06T06_21_35_997Z-debug.log
`
and
`vagrant@homestead:~/code$ npm run build

<EMAIL_ADDRESS>build /home/vagrant/code
npm-run-all build-clean --parallel css js copy --sequential build-vendors

sh: 1: npm-run-all: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR<EMAIL_ADDRESS>build: npm-run-all build-clean --parallel css js copy --sequential build-vendors
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/vagrant/.npm/_logs/2020-08-06T06_27_20_863Z-debug.log
`

Same error here... Any solution with the package directly downloaded from the official website?

same problem npm install fail, and --force also
git clone https://github.com/coreui/coreui-free-react-admin-template.git my-project

Cloning into 'my-project'...
remote: Enumerating objects: 125, done.
remote: Counting objects: 100% (125/125), done.
remote: Compressing objects: 100% (71/71), done.
remote: Total 3938 (delta 26), reused 76 (delta 17), pack-reused 3813Receiving objects: 100% (3938/3938), 1.05 MiB | 2.0Receiving objects: 100% (39
38/3938), 2.70 MiB | 3.27 MiB/s, done.
Resolving deltas: 100% (1481/1481), done.

>cd my-project

\my-project>npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/react
npm WARN<EMAIL_ADDRESS>from the root project
npm WARN   9 more (@coreui/icons-react, @coreui/react, react-dom, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>|| 0.14.x || ^15.0.0-0 || ^16.0.0-0" from<EMAIL_ADDRESS>npm WARN node_modules/enzyme-adapter-utils
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/@wojtekmaj/enzyme-adapter-react-17
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@coreui/icons-react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@coreui/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   8 more (@coreui/react, react-dom, react-router-dom, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0-alpha" from<EMAIL_ADDRESS>npm ERR! node_modules/enzyme-adapter-utils/node_modules/airbnb-prop-types
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/enzyme-adapter-utils
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@wojtekmaj/enzyme-adapter-react-17
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\nova\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR!  C:\..\2021-03-30T11_26_38_737Z-debug.log

I'm have an issue when, I run npm run build comman.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/macbook/.npm/_logs/2022-01-12T09_07_30_672Z-debug.log

Check you node version (node -v)
Sometimes newest version of node are not compatible.
I use nvm (node version manager) and I switch to node v 15 or even 14 sometimes to install some repos.
Hope that helps.

@Raheel1258 we fixed those issues in v3.2.2, you should upgrade it.


1.0 changes

I said I'd finish up my changes this weekend, and here they are.
It naturally turned into much more work than expected, mostly because in the process i found unsound trait impls, many inconsistencies, a way to make a const fn for creating AsciiChar from char, and many other small things I felt like changing.
Changelog:

Remove unsound impl From<&mut AsciiStr> for &mut [u8] and for &mut str.
Remove quickcheck.
Rename AsciiStr.trim_left() and AsciiStr.trim_right() to trim_start() and trim_end().
Rename AsciiChar::from{,_unchecked}() to from_ascii{,_unchecked}().
Remove impls of deprecated std::ascii::AsciiExt trait.
Rename some AsciiChar variants, most significantly Null to Nul (for consistency with CStr method names).
Remove AsciiStr::new() (in preparation for making it const sooner or changing it).
Make from_ascii_unchecked() non-generic (in preparation for making it const sooner).
Change Chars iterator returned by AsciiStr::chars() to produce values instead of references.
Change AsciiChar::is_whitespace() to return true for form-feed and vertical tab (for consistency with char::is_whitespace().
Change many AsciiChar methods to take self by reference for maximum compatibility with u8 and char.
Add slice_ascii_str() and get_ascii() to AsAsciiStr and slice_mut_ascii_str() to AsMutAsciiStr.
Hide Lines and Split behind impl Trait.
Change Chars and CharsMut from being typedefs for [AsciiChar] iterators to being newtypes.
Require Rust 1.36 for 1.0.*, and allow later semver-compatible releases to increase it.
Make most AsciiChar methods const fn and add AsciiChar::new().
Implement AsRef<AsciiStr> for AsciiChar and AsciiStr, and AsMut<AsciiStr> for AsciiStr.
Implement ToAsciiChar for i8, u16 and u32.
Implement Clone, Copy and Eq for ToAsciiCharError.
Add many is_xxx() methods to AsciiChar.

The requirement of rustc 1.36 seems a bit high. Debian for example packages 1.34.2 in Buster, which could be our baseline for rustc compatibility I think.

The idea was to allow us to use as many features as possible without increasing MSRV, but aving at least one 1.0 version usable with packaged rustc makes sense.
With 1.36 we could actually use alloc-in-'#![no_std], but we'll still need a "std" feature for ErrorandCStr`, so that can wait until later.
Because I don't want a patch release to break what previously happened to compile, the minimum supported version becomes 1.33.0 as that is the minimum version that compiles.

Thanks for the updates here, I think the PR is ready to be merged and published.

Changelog:
Breaking changes:

* Remove **UNSOUND `impl From<&mut AsciiStr>` for `&mut [u8]` and `&mut str`** (see [#64](https://github.com/tomprogrammer/rust-ascii/issues/64).
* Remove quickcheck feature.
* Remove `AsciiStr::new()`.
* Rename `AsciiChar::from()` and `AsciiChar::from_unchecked()` to `from_ascii()` and `from_ascii_unchecked()`.
* Rename several `AsciiChar.is_xxx()` methods to `is_ascii_xxx()` (for comsistency with std).
* Rename `AsciiChar::Null` to `Nul` (for consistency with eg. `CStr::from_bytes_with_nul()`).
* Rename `AsciiStr.trim_left()` and `AsciiStr.trim_right()` to `trim_start()` and `trim_end()`.
* Remove impls of the deprecated `std::ascii::AsciiExt` trait.
* Change iterators `Chars`, `CharsMut` and `CharsRef` from type aliases to newtypes.
* Return `impl Trait` from `AsciiStr.lines()` and `AsciiStr.split()`, and remove iterator types `Lines` and `Split`.
* Add `slice_ascii_str()`, `get_ascii()` and `unwrap_ascii()` to the `AsAsciiStr` trait.
* Add `slice_mut_ascii_str()` and `unwrap_ascii_mut()` to the `AsMutAsciiStr` trait.
* Require Rust 1.33.0 for 1.0.\*, and allow later semver-compatible 1.y.0 releases to increase it.

Additions:

* Add `const fn` `AsciiChar::new()` which panicks on invalid values.
* Make most `AsciiChar` methods `const fn`.
* Add multiple `AsciiChar::is_[ascii_]xx()` methods.
* Implement `AsRef<AsciiStr>` for `AsciiChar`.
* Make `AsciiString`'s `Extend` and `FromIterator` impl generic over all `AsRef<AsciiStr>`.
* Implement `Clone`, `Copy` and `Eq` for `ToAsciiCharError`.
* Implement `ToAsciiChar` for `u16`, `u32` and `i8`.
* Implement inclusive range indexing for `AsciiStr` (and thereby `AsciiString`).
* Mark `AsciiStr` and `AsciiString` `#[repr(transparent)]` (to `[AsciiChar]` and `Vec<AsciiChar>` respectively).

Also, a README update which I had stashed away:
diff --git a/README.md b/README.md
index 192abf0..e054cf1 100644
--- a/README.md
+++ b/README.md
@@ -11,15 +11,16 @@ dependencies section in `Cargo.toml`:

 ```toml
 [dependencies]
-ascii = "0.9"
+ascii = "1.0"
\`\`\`

 ## Using ascii without libstd

 Most of `AsciiChar` and `AsciiStr` can be used without `std` by disabling the
 default features. The owned string type `AsciiString` and the conversion trait
-`IntoAsciiString` as well as all methods referring to these types are
-unavailable. The `Error` trait is also unavailable, but `description()` is made
+`IntoAsciiString` as well as all methods referring to these types and
+`CStr` and `CString` are unavailable.
+The `Error` trait is also unavailable, but `description()` is made
 available as an inherent method for `ToAsciiCharError` and `AsAsciiStrError`.

 To use the `ascii` crate in `core`-only mode in your cargo project just add the
@@ -27,7 +28,7 @@ following dependency declaration in `Cargo.toml`:

 ```toml
 [dependencies]
-ascii = { version = "0.9", default-features = false }
+ascii = { version = "1.0", default-features = false }
\`\`\`

 ## Minimum supported Rust version
@@ -36,7 +37,7 @@ The minimum Rust version for 1.0.\* releases is 1.33.0.
 Later 1.y.0 releases might require newer Rust versions, but the three most
 recent stable releases at the time of publishing will always be supported.
 For example this means that if the current stable Rust version is 1.38 when
-ascii 1.1.0 is released, then ascii 1.1.* will not require a newer
+ascii 1.1.0 is released, then ascii 1.1.\* will not require a newer
 Rust version than 1.36.

 ## History

(to apply, replace "\`\`\`" with "```" and then run git apply).


Handle robots error messages

When the robot detects an unrecoverable error, you will be sent a message to completely ignore this robot.
To recover from this state, the robot needs a config message.
Please check the update hardware protocol.

How a CONFIG message enables the robot to recover from the error state?
In this situation, we will be out of sync.


ex.4.3.3 module 4 2nd august 2022

Good evening to everyone!
I cannnot understand where I should take the data referring to the passenger age within each passenger class in ex.4.3.3.
Many thanks in advance. Niccolò Ghionzoli

Solved, nothing to be worried


exclude/include in model_dump vs. exclude/include in the Field constructor

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
This may be a bug, but more likely this is a documentation issue. Either way, right now the behavior is confusing/inconsistent with the docs. It is also worth noting that this is not v2 specific. The same can be observed with v1.
The Model- and field-level include and exclude section of the serialization docs state the following:

Explicitly setting exclude/include on model_dump and model_dump_json takes priority over the exclude/include from the field constructor (i.e. Field(..., exclude=True))

The way I understand that is that, if I have a field named b with Field(exclude=True) and later pass include={"b"} to model_dump, that dump should include b. That is not the case though.
Maybe that is the intended behavior, but in that case the documentation is misleading, if not straight up wrong.
Example Code
from pydantic import BaseModel, Field

class Model(BaseModel):
    a: str
    b: str = Field(exclude=True)

obj = Model(a="foo", b="bar")
dumped = obj.model_dump(include={"a", "b"})  # same with `dict` for v1
print(dumped)  # {'a': 'foo'}

Python, Pydantic & OS Version
pydantic version: 2.0.3
        pydantic-core version: 2.3.0 release build profile
                 install path: /path/to/.venv/lib/python3.9/site-packages/pydantic
               python version: 3.9.17 (main, Jun 24 2023, 20:40:40)  [GCC 13.1.1 20230429]
                     platform: Linux-6.4.4-arch1-1-x86_64-with-glibc2.37
     optional deps. installed: ['typing-extensions']

Selected Assignee: @adriangb

Thanks @daniil-berg for reporting this 🙏
Actually, it is intended behavior. when we exclude a field by using Field(exclude=True), Pydantic does not generate a serializer for that field. That's the reason that we can't include it again in model_dump().
If you want this behavior to change, it would be great to make a PR to change it. Otherwise, I will change the documentation.

Thanks @hramezani for explaining this. I guessed something like this, i.e. that this is by design (for now). But I don't know if this is really desirable behavior. The documentation of course indicates the opposite.
So far, I don't have a strong opinion about this either way, just that the documentation needs to reflect the actual behavior.


⚠ Cioos National CKAN has degraded performance

In 9cc23bb, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 5511 ms

Resolved: Cioos National CKAN performance has improved in 2a4aaf4 after 29 minutes.


Support .NET CORE 1.0

Currently not working on .Net CORE 1.0 - netstandard1.4

Duplicate of #237
Support exists (for netstandard1.5, at least) in the master branch, but the owner of this project is the only one who can upload a new NuGet package.


Remove docker

Docker adds a bit of a hurdle for new developers to get dev wallet up and running and often gets out of sync with development. Make it so only npm run dev is needed to run dev wallet.

I mean it was not working with docker, I agree with removal though.


Add role to user

The User model provides a name, email, picture.
I think it would be very useful to add "role" , where role could be any string or we could provide the possible options like "tester", "manager", "architect", etc.

So the semantics would be that this is the primary role they are employed as, right?
In more advanced scenarios I could picture this being a property on a relation instead - "A is-a-member-of B as-a C", where you could have different roles in different groups.

Very true.
Then it becomes more complicated but probably the most flexible improvement would be to make memberOf an object so you can add the role you use for each of the groups you are member of.

The very first version of the relations model will not have support for additional data on relations, but it is something that we intend to add.

Could be very interesting to discover this kind of thing through analyzing contributions too. For example automatically tagging with known languages and technologies and so on.

@Rugvip Could this actually be a label? Employee role, that is

I mean in an output sense it totally could be. But even in an input sense?

Came across this feature request. Are there any plans to take this further?
The method as mentioned by @freben would be ideal as we use Entra (Azure AD) as the source for users, but YAML files to specify relations between user and team.

So the semantics would be that this is the primary role they are employed as, right?
In more advanced scenarios I could picture this being a property on a relation instead - "A is-a-member-of B as-a C", where you could have different roles in different groups.

Having tags/labels to indicate someone's role is limited as one could have a different role in other teams. (e.g. A team member could also be a member of some technology guild or community) Having multiple tags and still provide an overview is almost impossible in my opinion.


Improve Analytics setup documentation

Added instructions to the README for how to get the google services configuration files for analytics. Removed (and ignored in future) the empty config files. Note: empty folders are ignored in git, so added an empty file .exist to the android folder so that it will be there as a place to hold the actual google services file.
Finally added the xCode scheme for the app that you need for newer versions of xCode.

FWIW it looks like the standard spelling of the app is "Xcode"

A few questions

LGTM. Could you change the name of this PR to reflect the fact that it's a collection of small changes to setup? Ideally, we would split changes that aren't related, like the README changes and the gitignore changes and the scheme here, but I think these are all small and it's ok.


Define and use hkdf_extract.

Fix: https://github.com/DMTF/libspdm/issues/1102
Signed-off-by: Jiewen Yao<EMAIL_ADDRESS>

I filed https://github.com/DMTF/Security-TF/issues/2133 on the specification side.


Create an example project for vertx-websocket

Describe the feature here
Might be nice to have an example project for vertx-websocket. Something like a Camel chat server with a basic web UI to show the messages, connection events, maybe even sending 'private' direct messages to a specific peer etc

Hi @jamesnetherton , I and @svkcemk had a discussion internally and we are looking to work on this issue together.
So, just wanted to ask you is that okay?

@spatnity feel free to work on it if you'd like too.

Sure, thankyou!

https://github.com/jamesnetherton/camel-quarkus-examples/tree/camel-quarkus-main/vertx-websocket-chat


Merge new Q-Learning algorithm

Add the assumptions for Q-Learning based on my proposal from a few weeks ago.
At the moment, this involves q-routing and core assignment.

Going to merge and create tests on another branch.


19.09 TeXstudio doesn't start

Describe the bug
Trying to start texstudio led to an abort with this error
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
This happened after the 19.03 to 19.09 update.
To Reproduce
Steps to reproduce the behavior:

Use 19.09 channel
Install texstudio
Try to start it

Expected behavior
The application starts without problems
Metadata
`▶ nix run nixpkgs.nix-info -c nix-info -m

system: "x86_64-linux"
host os: Linux 5.3.2, NixOS, 19.09beta606.3ba0d9f75cc (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3
channels(root): "nixos-19.09beta606.3ba0d9f75cc, nixos1903-19.03.173553.6420e2649fa, nixos1909-19.09beta606.3ba0d9f75cc"
channels(dunklecat): ""
nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos``

cc #65399

I had the same problem, installing qt5Full solved it. You may want try:

nix-shell -p texstudio -p qt5Full --run texstudio

Report:
On 19.03 the package works as expected
On 19.09 the package works as expected if qt5.full is declared, too

This is fixed for master in #73484, but not yet for release-19.09.

Should be fixed now with b926503738cc5b19f3ee66f8a5745c41318a82ff and parent on release-19.09 branch.


Migrate the wiki to gh-pages and add mkdocs

@ipapapa
This is the very first version using mkdocs(http://www.mkdocs.org/)
You can access my fork on: http://diegopacheco.github.io/dynomite/
Once you accept the PR: DM wiki will be here: http://netflix.github.io/dynomite/
On the repo we have the site which was generated by mkdocs via $ mkdocs build. The source code in markdown is on the folder: mkdocs-site.
Cheers,
Diego Pacheco

LGTM, it is just porting the wiki to a website. We probably need to follow up updating our README and related links to point to the website and then delete all content from wiki. @shailesh33 thoughts?

@diegopacheco if we want to update the website, how easy would that be? Moreover, I am looking into the structure and it is not the same as the wiki which makes it hard to parse it. Can we follow the wiki structure?

@ipapapa
Sure. I will try to submit something before Xmas.
Cheers,
Diego Pacheco

@ipapapa
I made the change you requested. I used prefixed numbers so I can grantee the same order as the wiki.

Thanks!


New Helm chart version gets published before the images are pushed

Describe the bug
Whenever we make a new release, the new Helm chart is published before the images get pushed to ghcr.io. Pushing a new Helm chart version should be done after pushing the images.

We have recently only seen this happening when the PR gets manually merged before the release job finishes. However, this ticket could be a good opportunity to add the chart published to the release workflow instead of its own one.


Zero-to-Hero Crossword

The zero-to-hero crossword example is a deliverable for the Dev Platform team for Q3 of 2021. Dev Rel is helping as well. The idea can be understood from resources here:
Resources:

Video: https://drive.google.com/file/d/1Zs9sHyyY6f2H8IBWEjkq--5MHMeQ5vuy/view
Slides: https://docs.google.com/presentation/d/19JISbufR1xUlMqgyiUejeIOrCu-DXhd9qRshRhEmhGc/edit#slide=id.gd8531dd72b_0_7
Modified slides for higher-level view (bootcamp): https://docs.google.com/presentation/d/1DekaQJnjRaS47mo5BBLvJEWBOokJ20oU_ip8PPRKH6I/edit

Phases
Overall, perhaps start with three phases. (akin to beginner, intermediate, advanced) At the end of each phase there's a final "product" they can take with them.
At the end of phase 1, the user walks away with a crossword puzzle and frontend that allows a user to log in and solve the crossword. The player must have an existing account to be able to log in, and would add the solution public key to themself and then call submit_solution. The smart contract checks against the public key but also knows who the predecessor is and that's the account that gets paid the 10 NEAR. This demonstrates the typical way we use function-call access keys.
At the end of phase 2, the product is a crossword puzzle akin to what we have here: https://github.com/near-examples/near-crossword/pull/4. The user playing the crossword puzzle doesn't need to log in. They can create a testnet/mainnet account once they've won. (This differs slightly from the above link as we don't have account creation yet.) This will also involve importing a seed phrase into Wallet. (That PR already stores this info in local storage.) The users walk away understanding callbacks and checking for success/failure.
At the end of phase 3, the user has made optimizations like adding a function that takes Borsh serialized arguments instead of JSON. They also restrict who can call new_puzzle to a designated DAO. Demonstrate the ability of having a DAO controlling this smart contract, how removing all access keys would allow this to be fully controlled by voting only. We could also demonstrate the idea of a "staging area upgrade" that's more advanced.
Thoughts on progressively teaching folks concepts while building

The first contract they write in Rust is super simple. Doesn't pay anything out, doesn't touch access keys, just demonstrates how to pass an argument to a Rust smart contract.

pub fn submit_solution(&mut self, full_answer: String) {
  if full_answer == "sharding subaccount accesskey indexer nonfungible rpc simulation init defi dao" {
    env::log(b"Correct!");
  } else {
    env::log(b"Try again :)");
  }
}

show them logging and how you can see the logs in Explorer, and what Explorer is.

Don't have it check the full answer inside submit_solution but instead store that in a struct's field, and set that on initialization. This demonstrates using state and the deploy-and-init idea.

Don't store the entire seed phrase in state. We could hash the whole seed phrase to make it smaller. Point out that hashing is a one-way process and you can derive a hash from the input, but cannot derive the input once you have the hash. This is essentially a big part of blockchain, provide links for more info.

We could use all sorts of hashing functions, but for instructional purposes, let's create a key pair from the crossword solution, treating it as a seed phrase. We'll show why later.
To create a hash we'll use the public key when we generate a key pair using NEAR CLI. Ask them to install it and run the near generate-key command with the seed phrase.
They'll see that we now have a shorter thing to store on-chain.
Before it was 78 characters (sharding subaccount accesskey indexer nonfungible rpc simulation init defi dao)
Now it is 52 characters (ed25519:J5VxZNQGvgruC1LRqXCnxzBNhwaHmmEoEXFoxdV9cuXB)
What are the ways in which this is helpful? Well, let's talk about storage staking on NEAR, linking to docs about how you pay for data you store on the blockchain. Let's use the near state command to show how much storage was used in both cases, the "hashed" and non-hashed cases. While we're here, let's talk about the "code hash" that is spit out in the result of that command, and how you can tell if a smart contract is deployed to an account.

Next let's introduce the idea of "creating transactions inside a smart contract" because we want to send the winner 10 testnet NEAR if they are correct. But let's go with a little different approach and create a subaccount so we can deploy to that and then call from the parent account and see the transfer of 10 NEAR happened. What are subaccounts… Introduce pattern of deleting and recreating a subaccount when iterating on writing Rust smart contracts.

By the end of it, they call submit_solution on crossword.friend.testnet (giving the public key as the parameter) from friend.testnet. If it's correct, it transfers 10 testnet NEAR to the predecessor, which is friend.near. Go over what predecessor is versus signer versus current account id.

Show people Rust Status Message and how you can "log in" using NEAR Wallet. Go over the access keys, how they're visible in the Wallet UI but also using NEAR CLI's near keys friend.testnet

Be very explicit on which account creates the access key and walk through the process in slow-motion. This is a commonly misunderstood concept, both to new devs and inside NEAR. Show the keys in local storage, use near keys before and after on both the smart contract account and the user account.
Continue on with this pace…

Closing as this has been completed and migrated to https://docs.near.org/tutorials/crosswords/basics/overview.


Table 'XXXX' is missing a matching permission set.

We developed application which works fine in our local environment with no errors but when we are trying to deploy our application on production environment of business central it gives below error.
Package validation failed due to the following error(s): (1,13): error PTE0004: Table '50001' is missing a matching permission set.
(1,13): error PTE0004: Table '50002' is missing a matching permission set.
(1,13): error PTE0004: Table '50003' is missing a matching permission set.
After error we referred git hub issue #1880 , #2977 , #3066 but none are useful.
We are giving permission for table 50001 , 50002 and 50003 as under .
    <Permission>
        <ObjectType>TableData</ObjectType>
        <ObjectID>50001</ObjectID>
        <ReadPermission>Yes</ReadPermission>
        <InsertPermission>Yes</InsertPermission>
        <ModifyPermission>Yes</ModifyPermission>
        <DeletePermission>Yes</DeletePermission>
        <ExecutePermission>0</ExecutePermission>
        <SecurityFilter />
    </Permission>
    <Permission>
        <ObjectType>Table</ObjectType>
        <ObjectID>50001</ObjectID>
        <ReadPermission>1</ReadPermission>
        <InsertPermission>1</InsertPermission>
        <ModifyPermission>1</ModifyPermission>
        <DeletePermission>1</DeletePermission>
        <ExecutePermission>0</ExecutePermission>
        <SecurityFilter />
    </Permission>

We are using AL Language version 0.16.26913.
We want to deploy our app in "CA Dynamics NAV 13.0(24630)" but it gives an error which i mentioned.

Please update to the latest version of AL Language and then try running the new command "Generate permission set containing current extension objects". This will help ensure that all relevant permission sets are created in the right xml format.

TableData: Read,Insert,Modify,Delete
Table: Execute

We have been trying to solve this issue since last two day than we
generated this issue and we got solution after your reply. I would like to
thank you from me and my team.
On Fri, 19 Oct 2018 at 7:11 PM, Stanislaw Stempin<EMAIL_ADDRESS>wrote:

Please update to the latest version of AL Language and then try running
the new command "Generate permission set containing current extension
objects". This will help ensure that all relevant permission sets are
created in the right xml format.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/AL/issues/4089#issuecomment-431367134, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AbeJ_mZ5mkrNvURS5IX1IcLV4ntpqZ3Cks5umdalgaJpZM4XwRjI
.

Please update to the latest version of AL Language and then try running the new command "Generate permission set containing current extension objects". This will help ensure that all relevant permission sets are created in the right xml format.

Thank you so much for your reply on the behalf of my team.


Expires switch doesn't do anything

uptick -d --expires 240 transfer myaccount 1 BTS
uptick -d -e 240 transfer myaccount 1 BTS

Both of these commands generate a transaction that expires in 30 seconds (default value according to docs).

Thanks for the report. The option is passed right to the BitShares constructor which expected expiration instead of expires. I renamed the option and confirmed that it now works ..