Missing build.xml

Readme.md says there is an example of running Spock using Ant but it seems that the Ant example was deleted in a PR earlier. May you please add the example again or let us know the reason behind deleting the example.

Honestly, I consider ANT to be outdated and didn't want to maintain the build.xml anymore, that is why I deleted it. And apparently I missed a mention of it in that commit.
If you are still using ANT, take a look at https://github.com/junit-team/junit5-samples/blob/r5.9.1/junit5-jupiter-starter-ant/build.xml, since Spock 2.x is a JUnit Platform engine, this combined to the old build.xml should give you the necessary building blocks to get it to work.
What is the reason for still using ANT?

Thank you @leonard84 . I was just curious that there is no example of ANT even though README mentions it.


Dependabot doesn't create PR

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
docker
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
https://github.com/pizzafactory-contorno/piatto/blob/main/debian-10.1/Dockerfile
dependabot.yml content
version: 2
updates:
- package-ecosystem: docker
  directory: /alpine-3.10
  ignore:
  - dependency-name: alpine
    versions:
    - "!= 3.10"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /alpine-3.15.0
  ignore:
  - dependency-name: alpine
    versions:
    - "!= 3.15.0"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /alpine-3.16
  ignore:
  - dependency-name: alpine
    versions:
    - "!= 3.16"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /alpine-3.17
  ignore:
  - dependency-name: alpine
    versions:
    - "!= 3.17"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /alpine-3.18
  ignore:
  - dependency-name: alpine
    versions:
    - "!= 3.18"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /debian-10
  ignore:
  - dependency-name: debian
    versions:
    - "!= 10.pre.slim"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /debian-10.1
  ignore:
  - dependency-name: debian
    versions:
    - "!= 10.1.pre.slim"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /debian-10.2
  ignore:
  - dependency-name: debian
    versions:
    - "!= 10.2.pre.slim"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /debian-11.1
  ignore:
  - dependency-name: debian
    versions:
    - "!= 11.1.pre.slim"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /debian-9.11
  ignore:
  - dependency-name: debian
    versions:
    - "!= 9.11.pre.slim"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /ubuntu-16.04
  ignore:
  - dependency-name: ubuntu
    versions:
    - "!= 16.04"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /ubuntu-18.04
  ignore:
  - dependency-name: ubuntu
    versions:
    - "!= 18.04"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /ubuntu-20.04
  ignore:
  - dependency-name: ubuntu
    versions:
    - "!= 20.04"
  schedule:
    interval: daily
- package-ecosystem: docker
  directory: /ubuntu-22.04
  ignore:
  - dependency-name: ubuntu
    versions:
    - "!= 22.04"
  schedule:
    interval: daily

Updated dependency
Update logs in Dependency-graph
updater | 2023/07/08 10:38:14 INFO <job_690289655> Finished job processing
updater | 2023/07/08 10:38:14 INFO Results:
updater | +--------------------------------------------------+
updater | |       Changes to Dependabot Pull Requests        |
updater | +---------+----------------------------------------+
updater | | created | debian ( from `a893719` to `1125379` ) |
updater | +---------+----------------------------------------+
updater | time="2023-07-08T10:38:15Z" level=info msg="task complete" container_id=job-690289655-updater exit_code=0 job_id=690289655 step=updater

What you expected to see, versus what you actually saw
I expect a pull request is created.
I see no pull requests.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Additional info:
Dependabot creates some PRs for another Dockerfile in the same repository. e.g. https://github.com/pizzafactory-contorno/piatto/pull/59
I guess Dependabot fails to create PR if the image tag contains -.

FROM ubuntu:22.04@sha256:... is acceptable.
FROM debian:10.1-slim@sha256:... may not be acceptable.

I think I am experiencing the same issue. In my case, I am using the npm environment.
The result of the logs indicate that it should create a PR:
updater | 2023/08/03 15:50:19 INFO Results:
updater | +------------------------------------------------------------------------------------------------------------------------------------+
updater | |                                                Changes to Dependabot Pull Requests                                                 |
updater | +---------+--------------------------------------------------------------------------------------------------------------------------+
updater | | created | @storybook/addon-essentials ( from 7.1.1 to 7.2.1 ), @storybook/addon-interactions ( from 7.1.1 to 7.2.1 ), @storyboo... |
updater | +---------+--------------------------------------------------------------------------------------------------------------------------+
updater | time="2023-08-03T15:50:19Z" level=info msg="task complete" container_id=job-704710861-updater exit_code=0 job_id=704710861 step=updater

However, no PR is actually created.
Interestingly, in my case the name of the package to update also contains a dash (-). I am using the experimental Groups feature, but it has been working fine for this same group less than a week ago.
The relevan

The issue which i had was with the schedule.time: "16:17"... after setting it to 09:00 it worked.. not sure what is the time format it supports.. 12 or 24 hours ?

I think I am experiencing the same issue. In my case, I am using the npm environment.
The result of the logs indicate that it should create a PR:
updater | 2023/08/03 15:50:19 INFO Results:
updater | +------------------------------------------------------------------------------------------------------------------------------------+
updater | |                                                Changes to Dependabot Pull Requests                                                 |
updater | +---------+--------------------------------------------------------------------------------------------------------------------------+
updater | | created | @storybook/addon-essentials ( from 7.1.1 to 7.2.1 ), @storybook/addon-interactions ( from 7.1.1 to 7.2.1 ), @storyboo... |
updater | +---------+--------------------------------------------------------------------------------------------------------------------------+
updater | time="2023-08-03T15:50:19Z" level=info msg="task complete" container_id=job-704710861-updater exit_code=0 job_id=704710861 step=updater

However, no PR is actually created.

Whatever issue was causing this might have been fixed. Finally received a grouped Storybook bump yesterday.

It does seem to work for me again as well... might have been a hickup, but certainly not something caused by misconfiguration.

Not sure what fixed this, but let's close this since it seems indeed fixed! :)


Allow own messages in NonNull annotations

Migrated from Google Code (issue 833)

Features always have a cost associated with them; we have to maintain and document them, and even if that was 'free', so to speak, our users have to read it.
We discussed it and @rspilker and I do not feel like this clears the bar.
TL;DR: That's not boilerplate.


indicator also to UIImage

Please add the function of the indicator also to UIImage

you can add to UIImageView

I was able to do it
Thank you!!


[WIP] Adds cluster_name parameter to listRecommendations API

This PR fixes #940

Enhancement of /listRecommendations API by adding cluster_name query parameter to retrieve recommendations for a specific cluster based on its name

@khansaad - I have incorporated review comments and rebased branch 'add_clusterName_parameter' onto 'mvp_demo'.
Can you please review the updated PR?

Closing stale PRs


feat: renovate folder icon

closes #374
I ran the pnpm icons -a command before committing, I'm not sure if the updated previews are desired?

I ran the pnpm icons -a command before committing, I'm not sure if the updated previews are desired?

https://github.com/catppuccin/vscode-icons/pull/309 does it for you, you can remove them to avoid conflicts and that PR will update them for all new icons later.

After a bit of rebasing/pushing misery I've cleaned up the branch :) Thanks for the input @uncenter!

Apologies for the ping @prazdevs, but is there anything that I should/can do to progress this PR?


Clean code: delete commented code

What this PR does / why we need it: #5584
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

ping @reddydinesh427, any updated on this?

@hickeyma updated it

@hickeyma updated.


8 feat add about page

Each of us should update the config with the appropriate details.

I will do it now :)

@Stefan-Radu you forgot to add your line lol.

@Costinteo to link your github xD

I added my part, I think @SecioreanuStefanita  you are the last one and then we can merge the PR.


Doesn't compile

$ rustc --version
rustc 1.57.0 (f1edd0429 2021-11-29)

error[E0308]: mismatched types
   --> /Users/darrien/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.18.1/src/platform/macos/view.rs:208:9
    |
204 | extern fn has_marked_text(this: &Object, _sel: Sel) -> BOOL {
    |                                                        ---- expected `bool` because of return type
...
208 |         (marked_text.length() > 0) as i8
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `bool`, found `i8`

error[E0308]: mismatched types
   --> /Users/darrien/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.18.1/src/platform/macos/window.rs:102:26
    |
102 |             is_zoomed != 0
    |                          ^ expected `bool`, found integer

error[E0308]: mismatched types
   --> /Users/darrien/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.18.1/src/platform/macos/window.rs:174:57
    |
174 |                 self.window.setFrame_display_(new_rect, 0);
    |                                                         ^ expected `bool`, found integer

error[E0308]: mismatched types
    --> /Users/darrien/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.18.1/src/platform/macos/window.rs:1277:48
     |
1277 |         window.setFrame_display_(current_rect, 0)
     |                                                ^ expected `bool`, found integer

error[E0308]: mismatched types
    --> /Users/darrien/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.18.1/src/platform/macos/window.rs:1284:48
     |
1284 |         window.setFrame_display_(current_rect, 0)
     |                                                ^ expected `bool`, found integer

error[E0308]: mismatched types
    --> /Users/darrien/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.18.1/src/platform/macos/window.rs:1301:48
     |
1301 |         window.setFrame_display_(current_rect, 0)
     |                                                ^ expected `bool`, found integer

error[E0308]: mismatched types
    --> /Users/darrien/.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.18.1/src/platform/macos/window.rs:1308:48
     |
1308 |         window.setFrame_display_(current_rect, 0)
     |                                                ^ expected `bool`, found integer

It looks like there may have been an incompatible update in one of the later winit releases.

Updating to the latest piston_window is step sort of handles this.
piston_window = "0.121.0"

I'm guessing this has to do with rust's dependency resolver. Afterwards we just need to add a trait for rand. I'll make a PR.

Thanks for the PR mate ✌


Is the mediaType field necessary in the artifact manifest?

The mediaType field is present in the artifact manifest spec, presumably copied over from the OCI image manifest or image index specs. According to those specs, it's a field that is kept around for backwards compatibility / reserved for use. I'm not sure that reasoning applies here, so I wonder if we should either:

remove it.
better explain its purpose in the new artifact manifest.

ref: https://github.com/oras-project/artifacts-spec/blob/main/artifact-manifest.md#oras-artifact-manifest-properties

Thanks Michael, this does warrant some more clarifications. The updated PR removes the copied "reserved" wording, and focuses on the usage.
The argument against including the mediaType was it's stored externally to the storage of the manifest. Before attempting to parse the document, the mediaType is known. The mediaType is pushed in the header when posting to a registry.
However, this doesn't solve the standalone evaluation of the manifest as an offline document. For most container runtime scenarios, the manifest is generated on the fly, as part of registry push, and not kept around, or built offline.
The notary v2 work clarified the need for offline, ephemeral clients where all the content is built and validated before being pushed to a registry.
The new graph of linked artifacts (through the subject property) changed those needs.
To create the following offline graph, you need local manifests. Having them in the document assures the values are preserved when you post the documents to the registry.
image
┣signature
┣sbom
┣─sbom-signature
┣gitbom
┣─gitbom-signature
┣scan-reusult
┕─scan-result-signature

The concern wasn't that it's invalid to have the mediaType in the document, rather it's duplicative.
You could make a similar argument that a digest and size are redundant. But, they're used for verification purposes. We could add detail to a new artifact-authors.md document that explains the mediaType must match (header and content) or the manifest is invalid.
I had several conversations with Stephen Day and Mike Brown about this topic, and we agreed to keep mediaType. But, you might notice schemaVersion was removed, which was also part of that same conversation.
So, the text should read the mediaType should reflect this double verification. If the mediaType stored externally doesn't match what's in the document, that's an error, just as the size and digest should match.

The concern wasn't that it's invalid to have the mediaType in the document, rather it's duplicative.

There isn't a concern about being duplicative, but inconsistent: https://github.com/opencontainers/image-spec/pull/411#issuecomment-261106466

So, the text should read the mediaType should reflect this double verification. If the mediaType stored externally doesn't match what's in the document, that's an error, just as the size and digest should match.

Folks involved seem to think it was a mistake to include, so I would recommend against this.

You could make a similar argument that a digest and size are redundant.

This doesn't make sense. How are they redundant?

If we navigate from a descriptor down to the actual manifest is makes sense to remove the mediaType. For e.g. in an index if the descriptor does have the mediaType of the manifest then definitely its redundant.
The scenarios called out in the opencontainers/image-spec#411 of out-of-band transfer of mediaTypes is also valid concern. I remember having a conversation with @vbatts about self describing artifacts and if we needed these fields The artifactType was was the interesting bit and if we removed that then validation tools wouldn't know if its should handle that manifest if it was given an array of descriptors and then we end up back into annotation land.
For a CAS engine also makes sense since we navigate from a ref ->descriptor either from the /referrers or get-manifest and request with ACCEPT which is the known mediaType.
Before we go down this path of removing the media type - I would like to understand how the manifest handler will disambiguate between different types of PUT. We need to specify what the content-type would be even if it isn't present in the manifest itself
https://github.com/distribution/distribution/blob/677772e08d6465bcdd09070d664bcd3ed64964a6/registry/handlers/manifests.go#L305
	mediaType := r.Header.Get("Content-Type")
	manifest, desc, err := distribution.UnmarshalManifest(mediaType, jsonBuf.Bytes())
	if err != nil {
		imh.Errors = append(imh.Errors, v2.ErrorCodeManifestInvalid.WithDetail(err))
		return
	}

So if remove the mediaType from the body we should call out the mediaType that would be used by distribution so that this new type of manifest can be put and handled.
Does that sound reasonable?

So if we remove the mediaType from the body we should call out the mediaType that would be used by distribution so that this new type of manifest can be put and handled.
Does that sound reasonable?

This seems reasonable to me. Other than examples in READMEs, there aren't really any contexts where you would encounter a document without sufficient metadata to interpret it. E.g., registries and clients currently communicate this information via the Content-Type header, and the on-disk OCI Image Layout representation solves this by hard-coding the type of index.json, which contains descriptors for the rest of the content in the image layout.
FWIW, I agree that self-describing artifacts have some nice properties, but I don't think it's reasonable to overturn a decision without at least understanding why it was made and the pros/cons of that decision. If in doubt, I'd bias towards consistency.

Seems reasonable to me, as well. I certainly didn't mean to imply that the mediaType should be removed entirely... My goal was to try and figure out why we have a field that seems to only exist for backwards compatibility reasons related to the Docker => OCI manifest spec process.
+1 to @jonjohnsonjr's point on index.json. I imagine that clients that need a local representation of an image and its related artifacts would use something similar to the Image Layout representation to do so.
Given that I believe both points are addressed, are there other concerns that we should discuss or should we go ahead and remove the field?

/cc @shizhMSFT - do you have any inputs here since this might affect client tooling.

The manifest upgrade scenario, where pulling a v1 manifest can be pushed as a v2 manifest is the most compelling scenario to remove it.
Scenario:
Pull a v1 based manifest:
{
  "mediaType": "application/vnd.cncf.oras.artifact.manifest.v1+json",
  "artifactType": "org.cncf.notary.v2",
  "blobs": [],
  "subject": {
    "mediaType": "application/vnd.oci.image.manifest.v1+json",
    "digest": "sha256:73c803930ea3ba1e54bc25c2bdc53edd0284c62ed651fe7b00369da519a3c333",
    "size": 16724
  },
  "annotations": {
    "foo": "bar"
  }
}

The above manifest has a digest and size based on the content, which includes: "mediaType": "application/vnd.cncf.oras.artifact.manifest.v1+json"
If a client understands a v2 version of the manifest, and the registry supports a v2 manifest, the client would/should/could attempt to upgrade.
However, changing the value of the mediaType would change the digest and size and all references (subject pointers) to the original manifest, and those references would no longer be valid.  😞
I've been mostly concerned around offline scenarios, where we shouldn't need to construct a "store" that knows how to store different mediaTypes. A client should be able to store the files in a single directory and know how to parse them.
While it's possible to infer, based on the schema, I was hoping to avoid this requirement.
The upgrade/conversion is far more interesting, and with more digging into the code (registry, oras, notation), even for references, this doesn't look like it's a problem.
So, I'm ok removing mediaType from the persistence.
The only question I have is whether we remove it before cutting draft1, or make this change in draft2.

/cc @shizhMSFT - do you have any inputs here since this might affect client tooling.

Clients should be fine with the mediaType removal. As in Docker Registry HTTP API V2 #Manifest, GET Manifest always returns the media type of the manifest through the Content-Type HTTP response header.
Servers using distribution are impacted with mediaType removal since the media type is not persisted alongside the manifest blob. As shown in the code, the implemention cannot get the media type from the blob storage, and it is a guesswork to determine the media type of the manifest. For instance, there is no effective way to determine whether a manifest is an OCI Index or an OCI Manifest. It is possible to push an OCI Manifest but server thinks it is an OCI Index, and it is possible to push an OCI Index but server thinks it is an OCI Manifest.
To improve the server implementation, it is necessary to refine the blob store interface and update its implementation accordingly.

LGTM to remove the mediaType field.

Artifacts that are not self-describing would introduce some challenges in the GET handler: https://github.com/distribution/distribution/blob/main/registry/storage/manifeststore.go#L74
One possible solution would be to use artifactType before deserializing to the type. Any other suggestions?

Resolved with #44


no support for loading 70B models via llamacpp

System Info
LangChain 0.0.242
Who can help?
No response
Information

[ ] The official example notebooks/scripts
[X] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[X] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
tried to load https://huggingface.co/TheBloke/StableBeluga2-70B-GGML model to work with lanchain's Llamacpp :
llm = LlamaCpp(model_path="./stablebeluga2-70b.ggmlv3.q4_0.bin", n_gpu_layers=n_gpu_layers,  n_batch=n_batch, n_ctx=8192, input={"temperature": 0.01},n_threads=8) llm_chain = LLMChain(llm=llm, prompt=prompt)
i see that there is no support in passing  n_gqa=8 parameter that according to https://github.com/abetlen/llama-cpp-python should be used for 70B models
the error i get is :
error loading model: llama.cpp: tensor 'layers.0.attention.wk.weight' has wrong shape; expected  8192 x  8192, got  8192 x  1024
Expected behavior
model should be loaded successfuly

+1 I'm having the same issue, the n_gqa arg is not working in LlamaCpp

This was merged 5 hours ago: https://github.com/ggerganov/llama.cpp/pull/2459

embeddings = LlamaCppEmbeddings(model_path="..../llama-2-70b.ggmlv3.q4_0.bin", n_gqa=8)
Support for n_gqa added in : https://github.com/abetlen/llama-cpp-python/issues/539


fix loading links on unsaved object

after auto links loading added, calling .add/.addAll for IsarLinks on unsaved objects throws ** Containing object needs to be managed by Isar to use this method.**

Codecov Report

Merging #490 (16bc080) into main (eaa99f3) will decrease coverage by 62.54%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main     #490       +/-   ##
===========================================
- Coverage   75.15%   12.61%   -62.55%
===========================================
  Files          32       32
  Lines        2483     2252      -231
===========================================
- Hits         1866      284     -1582
- Misses        617     1968     +1351

Impacted Files
Coverage Δ

packages/isar/lib/src/common/isar_link_common.dart
0.00% <0.00%> (-65.04%)
:arrow_down:

packages/isar/lib/src/version.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

packages/isar/lib/src/native/open.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

packages/isar/lib/src/annotations/name.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

packages/isar/lib/src/native/split_words.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

packages/isar/lib/src/annotations/backlink.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

packages/isar/lib/src/annotations/collection.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

...kages/isar/lib/src/annotations/type_converter.dart
0.00% <0.00%> (-100.00%)
:arrow_down:

packages/isar/lib/src/native/bindings.dart
0.00% <0.00%> (-91.84%)
:arrow_down:

packages/isar/lib/src/native/query_build.dart
0.00% <0.00%> (-84.98%)
:arrow_down:

... and 21 more

Continue to review full report at Codecov.

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


feat(#1264): add goa-calendar and goa-datepicker components

[ ] Issue-1: add examples in React App and Angular App
[ ] Issue-2: Date focus is not working
[ ] Issue-3: selecting unavailable date, month should change ? if yes, then selected date should move to available date
[ ] Issue-4: month dropdown scroll not working
[ ] Issue-5: opening dropdown, selected month should appear in dropdown list
[ ] Issue-6: Home Key, End Key, PageUp, PageDown, Shift+pageUp, Shift+PageDown Key are not working as expected
[ ] Issue-7: Mobile [ IOS-safari ]: improper selected date padding
[ ] Issue-8: IOS-Safari : blue border absent on Today's date
[ ] Issue-9:  see the steps to reproduce: [ https://www.loom.com/share/d5c81806cc13422fbb25b8d5de608653?sid=b614ee5a-7265-4610-a830-ae2894703383 ]

Steps to Reproduce [ Issue-9 ]:

Open Date picker with date attribute set as today's date.
Move selected date with arrow keys
move selected date to right (towards 31st August)
move that to 1st September [ NOTE: user won't be able to see selected date ]
click on any date from September [NOTE: month will change to October]

Issue-2:

Issue-7:

Issue-8:

[ ] Move to July by selecting unavailable date from August month. [No unavailable dates after 30 July]

Steps to Reproduce:

open Today's Date
Click on 31st July [This will be unavailable date]
31st July date will be selected. [ Issue: No Unavailable dates after 30 July. ]

[ ] Above issue also exist for 31st December 2023 and March 2024 and June 2024

Issue-1: PageUp not working properly

Steps to Reproduce:

Go to September 4th, 2023
Press PageUp

Current Output: 5th August 2023
Expected Output: 4th August 2023
Similar Dates with Issue:  5th July 2023
Issue-2: Shift + page Up Not working as expected

Steps to Reproduce:

Go to September 2nd, 2021
Press Shift + PageUp

Current Output: 1st September 2020
Expected Output: 2nd September 2020
Similar Dates with Issue: 3rd September 2020
Issue-3: Angular: [ https://www.loom.com/share/6569fcacdca04382b6d0ee4fc2615fcb?sid=228bfd0d-c201-4427-9b83-da7731c526f8 ]

Open Date picker
press Tab to shift focus to month dropdown
press shift+Tab to shift focus to previous element [ focus will move to last day of month, it should move to selected date]

Issue-4: Selecting date from date picker, input focus state should be active [just like date and time]( @Tom can you confirm this is a bug or not ?)

[ ] Issue-1: space key : opens the date picker but scrolls the DOM page as well
[ ] Issue-2: In Min/Max : year dropdown has only current year
[ ] Issue-3: month/year dropdown should close, if we close the date picker
[ ] Issue-4: dropdown should open/close by pressing enter
[ ] Issue-5: Shift+PageDown goes till 2027, it should go till 2028 (up to 5 years forward)
[ ] Issue-6: there should be white underline border on the today's date,selected
[ ] Issue-7: extra double quotation below min/max date picker input

Issue-6

Issue-7:

[ ] Issue-1: Accessibility: selecting the date, it should announce date including month and year
[ ] Issue-2: Accessibility: unable to select date with arrow keys
[ ] Issue-3: not able to update date when NVDA is active.
[ ] Issue-4: once date is updated with keyboard, month and year value gets cleared

https://www.loom.com/share/2aa2da6a7e3442c7863116ba7f1c0448?sid=8d49d5c4-9c61-445f-9963-24d6bec8bd76
Steps to Reproduce: [ NOTE: use only keyboard ]

Open date picker.
select any date from date picker.
reopen the date picker again [ Issue-4: month & year dropdown is cleared ]

:tada: This PR is included in version 4.15.0-alpha.7 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.15.0-alpha.7 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.6.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


chore(main): release svelte-fluent 0.6.2

:robot: I have created a release beep boop
0.6.2 (2023-06-16)
Bug Fixes

prevent exception in svelte-devtools (f3259d0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/nubolab-ffwd/svelte-fluent/releases/tag/svelte-fluent-v0.6.2 :sunflower:


Forward merge/zl/2.0 into 2.1

@JeetKunDoug... @macintux and I did some archaeology and the changes made in 2.1 were right on. Mostly around the previous work done in https://github.com/basho/riak_kv/commit/95a8c310a01b7ddaff50662ff48cb42c2a27f0a2. So... just them copyrights is all.

:+1: eec608f

@borshop merge


Missing Reduction: addi

created from #7.
A reduction sequence not yet supported: integral sum
repros.zip
triton-shared-opt -triton-to-linalg 30.mlir
triton-shared-opt -triton-to-linalg 86.mlir
Error output:
+++/home/ianb/test/ttirs_linalg_failed/30.mlir
/home/ianb/test/ttirs_linalg_failed/30.mlir:24:11: error: Only support lowering reduction with body containing 1 max(i/f) or addf.
    %13 = "tt.reduce"(%12) <{axis = 1 : i32}> ({
          ^
/home/ianb/test/ttirs_linalg_failed/30.mlir:24:11: note: see current operation:
%76 = "tt.reduce"(%75) <{axis = 1 : i32}> ({
^bb0(%arg12: i64, %arg13: i64):
  %84 = "arith.addi"(%arg12, %arg13) : (i64, i64) -> i64
  "tt.reduce.return"(%84) : (i64) -> ()
}) : (tensor<1x2xi64>) -> tensor<1xi64>
/home/ianb/test/ttirs_linalg_failed/30.mlir:24:11: error: failed to legalize operation 'tt.reduce'
    %13 = "tt.reduce"(%12) <{axis = 1 : i32}> ({
          ^
/home/ianb/test/ttirs_linalg_failed/30.mlir:24:11: note: see current operation:
%76 = "tt.reduce"(%75) <{axis = 1 : i32}> ({
^bb0(%arg12: i64, %arg13: i64):
  %84 = "arith.addi"(%arg12, %arg13) : (i64, i64) -> i64
  "tt.reduce.return"(%84) : (i64) -> ()
}) : (tensor<1x2xi64>) -> tensor<1xi64>

The repros here I think intersect with some slightly more complex patterns; E.g., with the natural addition (see https://github.com/microsoft/triton-shared/pull/20) 86.mlir still fails due to
86.mlir:33:11: error: failed to legalize operation 'tt.splat' marked as erased
    %18 = tt.splat %17 : (!tt.ptr<f32, 1>) -> tensor<1x1x!tt.ptr<f32, 1>>
          ^
86.mlir:33:11: note: see current operation: %93 = "tt.splat"(%92) {MetaUse} : (!tt.ptr<f32, 1>) -> tensor<1x1x!tt.ptr<f32, 1>>
86.mlir:34:5: note: found live user of result #0: "memref.tensor_store"(%88, %93) : (tensor<1x1xf32>, tensor<1x1x!tt.ptr<f32, 1>>) -> ()
    tt.store %18, %16 {cache = 1 : i32, evict = 1 : i32} : tensor<1x1xf32>
    ^

Happy to keep pushing to make the repros pass in totum but would appreciate a hint, since it seems in other tests "tt.splat"(%92) : (!tt.ptr<f32, 1>) lowers fine.


Go v1.7+ seems to be a requirement

On Windows 10 using cygwin:
$ go version
go version go1.6.3 windows/amd64
$ go get -u github.com/golang/dep/...
# github.com/golang/dep
..\github.com\golang\dep\lock.go:130: enc.SetIndent undefined (type *json.Encoder has no field or method SetIndent)
..\github.com\golang\dep\lock.go:131: enc.SetEscapeHTML undefined (type *json.Encoder has no field or method SetEscapeHTML)
..\github.com\golang\dep\manifest.go:129: enc.SetIndent undefined (type *json.Encoder has no field or method SetIndent)
..\github.com\golang\dep\manifest.go:130: enc.SetEscapeHTML undefined (type *json.Encoder has no field or method SetEscapeHTML)

According to this https://golang.org/doc/go1.7#minor_library_changes that enc.SetIndent has been introduced in go v 1.7.
I am not 100% sure about this issue as I am quite new to go, however if this is true then it could be mentioned in the docs, perhaps in the README.md near go get -u github.com/golang/dep/....
I can not find anywhere this information and I got stuck while trying to install go dep.

I don't think that was intentional, but we also haven't established that we plan to support any older versions of Go, either. In any case, thanks, and good suggestion - I'll update the README.


first pr

I have created a login page. And made some small additions related to it.

This is the login page.

Good work!! Merging it.

This is the login page.

Good work!! Merging it.


Fixes #332. Bug fix for GCC 10 and DRHOS0

This PR fixes a bug (#332) with GCC 10 and DRHOS0.
The problem was that in StieglitzSnow.F90, drho0 is initialized too late. In the code, at the top is an if-test:
https://github.com/GEOS-ESM/GEOSgcm_GridComp/blob/2590c4fdaece1901b6bef6132177eb67126f408b/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/Shared/StieglitzSnow.F90#L394
with a return built-in:
https://github.com/GEOS-ESM/GEOSgcm_GridComp/blob/2590c4fdaece1901b6bef6132177eb67126f408b/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/Shared/StieglitzSnow.F90#L441-L443
But, drho0 was initialized too far down:
https://github.com/GEOS-ESM/GEOSgcm_GridComp/blob/2590c4fdaece1901b6bef6132177eb67126f408b/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/Shared/StieglitzSnow.F90#L830
Thus, the code could return without drho0 being set to anything and apparently with GCC 10, that could be a denormal number (or even NaN as seen on macOS).
This PR initializes ALL the intent(out) members of the routine that are not in the initial set of "set to 0" at the top:
       rmelt = 0.0
       mltwtr = 0.0
       drho0 = 0.0
       tksno = 0.0

as a safety.

Currently going to do two tests:

Fully rebuild GCC 10 and make sure it still is consistent
Run this code within Intel and make sure it's zero-diff (🤞 )

If these pass, I'll ping @zhaobin74 to try it out in his code base(s) and make sure it works for him.

I suppose I might have to ping @gmao-rreichle as well. Make sure this doesn't do anything untoward to GEOSldas...if they use this code?

Okay. I am going to pull this out of draft. It seems zero-diff with Intel (as if Intel was flushing-to-zero denormals, it would be).
But, I'm not sure how to label this. The state of the model doesn't care about DRHOS0 as it's just diagnostic, but there is a chance on Intel and a guarantee on GCC 10 that the geosgcm_snowlayer collection (or any other collection that has it) could change a few values at the odd points where this was triggered.
I also don't know if DRHOS0 is a state variable for GEOSldas. I'll take a look, but I might need @gmao-rreichle to confirm/deny.

I also don't know if DRHOS0 is a state variable for GEOSldas. I'll take a look, but I might need @gmao-rreichle to confirm/deny.

I just took a look through GEOSldas and apparently it doesn't care about DRHOS0 (no reference to it) or even the drho0 from StieglitzSnow. It can be garbage and the GEOSldas will not mind one way or the other from my reading. drho0 is just an array that comes and goes. 😄

@zhaobin74 @gmao-rreichle  I guess I didn't do that because there are other places things happen in twos a la:
https://github.com/GEOS-ESM/GEOSgcm_GridComp/blob/2590c4fdaece1901b6bef6132177eb67126f408b/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/Shared/StieglitzSnow.F90#L373
https://github.com/GEOS-ESM/GEOSgcm_GridComp/blob/2590c4fdaece1901b6bef6132177eb67126f408b/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSsurface_GridComp/Shared/StieglitzSnow.F90#L827
I was going for the smallest change. But I can remove the other init-to-zero for drho0 if you like

Thanks for the clarification, @mathomp4 .  I see where you're coming from...
For reference, here are lines ~825-830 in the bugfix branch:
!**** Update snow density by compaction (Pitman et al. 1991)

       excs = 0.
       mass = 0.
       w    = 0.
       drho0 = 0.

A quick check suggests that the init of "excs" is the same as that of "drho0", ie., the 2nd init could/should be removed.
The init of "mass" should probably also be moved up, similar to that of "drho0".
But good luck with searching for "w"...
In a nutshell, the code is messy, and the question is simply how much cleanup we want to do at this time.
Perhaps the best course of action would be to clean up the init of "drho0", "excs" and "mass" because that seems to be low-hanging fruit, and add a comment about this cleanup into the code where "w" is initialized (for future reference).
Alternatively, the "w" init could also be moved up along with the others and then subjected to a full 0-diff testing.   Weiyuan could test GEOSldas if that's what you decide to do.
cc: @zhaobin74

Thanks for the clarification, @mathomp4 . I see where you're coming from...
For reference, here are lines ~825-830 in the bugfix branch:
!**** Update snow density by compaction (Pitman et al. 1991)

       excs = 0.
       mass = 0.
       w    = 0.
       drho0 = 0.

A quick check suggests that the init of "excs" is the same as that of "drho0", ie., the 2nd init could/should be removed.
The init of "mass" should probably also be moved up, similar to that of "drho0".
But good luck with searching for "w"...
In a nutshell, the code is messy, and the question is simply how much cleanup we want to do at this time.
Perhaps the best course of action would be to clean up the init of "drho0", "excs" and "mass" because that seems to be low-hanging fruit, and add a comment about this cleanup into the code where "w" is initialized (for future reference).
Alternatively, the "w" init could also be moved up along with the others and then subjected to a full 0-diff testing. Weiyuan could test GEOSldas if that's what you decide to do.
cc: @zhaobin74

I agree, now is the right time to make this right. excs, mass and drho0  should be fixed.

I pushed a commit that removes the redundant excs and drho0 set-to-zeros. The mass and w look fine to me as they are local to the routine and only ever referenced inside the if-block that uses them. excs and drho0 are actual outputs of snowrt and so should be initialized as soon as possible.


ActiveMerchantGrid UI improvements

Added horizontal seperators between each merchant. Also added auto-sort on active merchants so the highest voted merchant is always on top, merchants with negative votes are greyed out depending on the number of votes (#37).
Zones are now clickable and open the image in a new tab (#40), Only clickable in merchants table, not in UpdateMerchants page to avoid confusion.
A star icon now appears before notified cards and rapports (#43).

So just to be clear how this works, it greys out only the 2nd/3rd/etc row?
Looks good though, other than the extra comment I marked above. I'm assuming it can be removed since the sorting still appears to be working.
Related I should really add some dummy test images for the fake zones...

Yes it only greys out additional merchants. I found it looks really odd if the first merchant is greyed out aswell. On that note: I chose not to completely hide/remove merchants over the downvote threshold, since it might be confusing to see merchants disappear (and users can't suggest them again, they will be blocked in MerchantHub), and I didn't want to add logic to completely remove a merchant server-side.
Oh yeah, the marked line can be removed, the actual sorting happens in the view, not the list. That's from testing, I forgot to remove that.


Missing columnName description

I have provided the documentation with a short description of the columnName annotation.
I hope it is accurate enough!
M

Thanks for the PR


Stripped Bamboo Sign crashes - 1.19 Beta 7 & 8

Game crashes when rendering in Stripped Bamboo Sign, both when trying to place it or if it's already placed and you're loading in the chunks on 1.19.
Tried with both beta 7 and beta 8.
Attached is crash log using beta 8

How to recreate:

Use Twigs 1.19 beta 7 or 8
Load up a world
Place down a sign
Crash

crash-2022-08-19_01.38.35-client.txt

I've just released a beta 9 with official 1.19.2 support, could you try that out?
Frame API is also updated to 0.26

Updated both Twigs and Frame API, still crashes. normal and crash log attached
latest.log
crash-2022-08-20_17.25.00-client.txt

I disabled all unnecessary mods (Something I admittedly should've done before as it is standard bug testing), and it doesn't crash. I will check which mod is having issues, report it here, and see about opening an issue about it on that mod's page as well

Looks like the offending mod is Expanded Storage, I already opened a issue there (as Github so helpfully tells us)

Please see this, not sure why this happens exactly but I don't think it's necessarily the fault of bad code but rather how fabric/quilt mods are written in general:
https://github.com/devs-immortal/Paradise-Lost/issues/587

.

Is this still an issue?

Yep, just tried with newest versions of Twigs (2.0.0 beta 9), Frame (0.26.1), Ellemes' Container Library (2.1.0 alpha 10) and Expanded Storage (8.1.0 alpha 2), and the game still crashes when rendering a bamboo sign

opened a pull request which fixes the issue on the Frame library: https://github.com/moddingplayground/frame-fabric/pull/5


Multiple IF EXISTS in one statement. EG: modifying multiple columns.

Which version and edition of Flyway are you using?
$ flyway -v
Flyway Community Edition 6.4.2 by Redgate

If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin): CLI
Which database are you using (type & version)?
$ mysql --version
mysql  Ver 15.1 Distrib 10.3.23-MariaDB, for Linux (x86_64) using readline 5.1

Which operating system are you using?
CentOS 7

What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
migration 1: created schema and select it...
CREATE SCHEMA IF NOT EXISTS `example`;

USE `example`;

Apply a migration wherein multiple columns on a table are modified or created in one command leveraging IF [NOT] EXISTS to ensure a clean application of the migration.
SET NAMES 'utf8';

CREATE TABLE IF NOT EXISTS example.example_table_5 (
  `id` INT(11) DEFAULT NULL AUTO_INCREMENT PRIMARY KEY
);

-- This throws a warning: `WARNING: DB: Unknown column 'col_1' in 'example_table_5' (SQL State: 42S22 - Error Code: 1054)` but does exit 0.
ALTER TABLE example.example_table_5
  MODIFY COLUMN IF EXISTS `col_1` CHAR(1) DEFAULT NULL,
  ADD COLUMN `col_2` TINYINT DEFAULT NULL,
  ADD COLUMN `col_3` TINYINT DEFAULT NULL;

-- This does not work
-- `ERROR: Unable to parse statement in ../sql/example_release_version/example_schema_name/V202005221115__example_migratino_5.sql at line 13 col 1. See https://flywaydb.org/documentation/knownparserlimitations for more information: Incomplete statement at line 13 col 1: ALTER TABLE IF EXISTS example.example_table_5`
-- ALTER TABLE IF EXISTS example.example_table_5
--   MODIFY COLUMN IF EXISTS `col_1` CHAR(1) DEFAULT NULL,
--   ADD COLUMN `col_2` TINYINT DEFAULT NULL,
--   ADD COLUMN `col_3` TINYINT DEFAULT NULL;

-- This does not work
-- `ERROR: Unable to parse statement in ../sql/example_release_version/example_schema_name/V202005221115__example_migratino_5.sql at line 13 col 1. See https://flywaydb.org/documentation/knownparserlimitations for more information: Incomplete statement at line 13 col 1: ALTER TABLE IF EXISTS example.example_table_5`
-- ALTER TABLE example.example_table_5
--   MODIFY COLUMN IF EXISTS `col_1` CHAR(1) DEFAULT NULL,
--   ADD COLUMN IF NOT EXISTS `col_2` TINYINT DEFAULT NULL,
--   ADD COLUMN `col_3` TINYINT DEFAULT NULL;

-- This does not work
-- ERROR: Unable to parse statement in ../sql/example_release_version/example_schema_name/V202005221115__example_migratino_5.sql at line 27 col 1. See https://flywaydb.org/documentation/knownparserlimitations for more information: Incomplete statement at line 27...
-- ALTER TABLE example.example_table_5
--   MODIFY COLUMN `col_1` CHAR(1) DEFAULT NULL,
--   ADD COLUMN IF NOT EXISTS `col_2` TINYINT DEFAULT NULL,
--   ADD COLUMN IF NOT EXISTS`col_3` TINYINT DEFAULT NULL;

-- This does not work
-- Error `ERROR: Unable to parse statement in ../sql/example_release_version/example_schema_name/V202005221115__example_migratino_5.sql at line 13 col 1. See https://flywaydb.org/documentation/knownparserlimitations for more information: Incomplete statement at line 13 col 1: ALTER TABLE IF EXISTS example.example_table_5`
-- ALTER TABLE IF EXISTS example.example_table_5
--   MODIFY COLUMN `col_1` CHAR(1) DEFAULT NULL,
--   ADD COLUMN `col_2` TINYINT DEFAULT NULL,
--   ADD COLUMN `col_3` TINYINT DEFAULT NULL;

What did you expect to see?
Successful execution of the SQL logic. MariaDB support [IF [NOT] EXISTS] on most of the commands. Yet Flyway fails if more than one is encountered in a statement.
What did you see instead?
Failed migrations. :(

Did I mention the Flyway team is awesome? @MikielAgutu @Lyeeedar Thank you very much.


Any reason this shouldn't work with Grails3 on Tomcat8

http://stackoverflow.com/questions/35081392/using-aws-dynamodb-ro-save-session-inormation-in-grails-3

This looks like a bug. ExpiredSessionReaper should occasionally be polling for thread status and abort in a timely fashion.
"I'm hoping that once I have dynamodb backing the httpsession that I can spin up as many instances of my web app as possible and still have user sessions work across different servers without relying on 'sticky' sessions etc."
Not sure if you're the same poster as the StackOverflow question but this implementation of session manager still requires sticky sessions unfortunately. It is similar to the JDBC and File session stores and only persists idle sessions and acts as a session backup rather then realtime persistence.

is there any way of getting around stickyness or is it generally used ? or do most apps these days always just use oauth2 for a completly stateless model

"is there any way of getting around stickyness or is it generally used?"
Unfortunately due to the design of the session manager it is not possible to use non-sticky sessions. There is a memcached session manager that supports non-sticky sessions. https://github.com/magro/memcached-session-manager
"Or do most apps these days always just use oauth2 for a completly stateless mode?"
I'm not sure, I am not familiar with oauth2.

Assuming this Issue is actually about the memory leak on un-deployment caused by the "ExpiredSessionReaper," here's some more information:
SEVERE: The web application [] appears to have started a thread named [dynamo-session-manager-expired-sesion-reaper] but has failed to stop it. This is very likely to create a memory leak.

The ExecutorService associated with ExpiredSessionReaperExecutor is never shutdown():
https://github.com/aws/aws-dynamodb-session-tomcat/blob/master/src/main/java/com/amazonaws/services/dynamodb/sessionmanager/DynamoDBSessionManager.java#L143
For example, on PersistentManagerBase.stopInternal(), something like this:
scheduledThreadPoolExecutor.shutdown();

try{
	if(!scheduledThreadPoolExecutor.awaitTermination(1, TimeUnit.MINUTES)){
		scheduledThreadPoolExecutor.shutdownNow();
	}
}
catch(InterruptedException e){
	scheduledThreadPoolExecutor.shutdownNow();
}

https://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/session/PersistentManagerBase.html

Is this likely to be fixed any time?

This project has been archived. Please see the README.md for more detail on alternative projects.


OpenSSL License still applied instead of the Apache 2 license

Found in OpenSSL 3.2.1 and master branch.
The following files
include/openssl/hpke.h
crypto/hpke/hpke.c
crypto/ec/asm/ecp_sm2p256-armv8.pl
crypto/chacha/asm/chacha-loongarch64.pl
still seem to be released under the OpenSSL License instead of the Apache 2 license.
Fixes #23570

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

A thank you is still due.  Thanks for noticing these license discrepancies...  but, could this PR fix only that, please?

Do not change the dates on any of these files.. It indicates when they were created/updated

Done. Addressed.
It was copy paste mistake. Thanks!

A thank you is still due. Thanks for trying to fix these license discrepancies... but, could this PR fix only that, please?

Done.

This pull request is ready to merge

Merged to the master and 3.2 branches. Thank you for the contribution.


power loss on teleport require block replacement (1.10.2)

While playing on my 1.10 server using refined storage we encounter a bug where teleporting back to your base often cause the refined storage system blocks to no longer receive power, usually requiring breaking and replacing of the blocks inorder for them to properly work again, if RS blocks are connected to the controller directly they will need broken and replaced as well however if you have RS cables running from the controller down to the rest of your blocks its typically only the controller which needs broken and replaced, while not a major bug it is a hassle, and in 1 such case so far someone lost items they had in the crafting grid inside their grid when they broke and replaced it to get it connected to the network again. edit (i also noticed this occuring sometimes when you log into the server as well)
Ideally the blocks should update their status and start receiving power again immediately when they are loaded.
Steps to reproduce:

leave the area far enough for it to unload, the bug typically occurs when you travel back from another dimension.
teleport home via any available method.
while this does not seam to occur every time it its well over half in my experience, and as i said usually more frequent when returning from another dimension.
edit-(3. log into the server at your base and it will also often be unpowered)

Version (make sure you are on the latest version before reporting):

Minecraft:1.10.2
Forge:-1.10.2-<IP_ADDRESS>2
Refined Storage: 1.2.26]
spongeforge-1.10.2-2281-5.2.0-BETA-2464

1.10 is unsupported.


Enter-pssession closing issue

I am having a great difficulty getting the following working.
Have tried with and without remotemode, and it seems that i need it with otherwise each call takes the maxWait amount of time to finish.
I also need 2 exit statements otherwise the powershell.Close throws a TimeOut.
So it seems that my commands somehow open 2 extra powershell shells? I understand 1 extra as the enter-pssession start a new shell remotely.
The first powerShell.configuration(config).executeCommand("exit"); always takes the maxWait time to finish.
	@Test
	public void testConcreteExecute_Remote() {
		PowerShell powerShell = null;
		PowerShellResponse response = null;
		Map<String, String> config = new HashMap<String, String>();
		config.put("remoteMode", "true");
		config.put("maxWait", "50000");
		try {
			powerShell = PowerShell.openSession();

			response = powerShell.configuration(config).executeCommand("$password = ConvertTo-SecureString \"password\" -AsPlainText -Force");
			response = powerShell.configuration(config).executeCommand("$cred= New-Object System.Management.Automation.PSCredential (\"Administrator\", $password)");
			response = powerShell.configuration(config).executeCommand("Enter-pssession <IP_ADDRESS> -Credential $cred");
			System.out.println("PSsession:" + response.getCommandOutput());
			//Execute another command in the same PowerShell session
			response = powerShell.configuration(config).executeCommand("Get-WmiObject Win32_BIOS");

			powerShell.configuration(config).executeCommand("exit");
			powerShell.configuration(config).executeCommand("exit");
			System.out.println("BIOS information:" + response.getCommandOutput());
			Assert.assertEquals(false, response.isError());
		} catch (PowerShellNotAvailableException ex) {
			System.err.println("PowerShell not running on remote system" + ex);
		} finally {
			if (powerShell != null) {
				powerShell.close();
			}
		}
	}

Hello,
Your use case is quite in the edge!
You have no need to force the configuration each time. It should be ok if you perform a:
powerShell = PowerShell.config(config).openSession();

In your example you mix remote and non remote calls which I think it is not a good idea. Do you have the same problem if you call the Get-WmiObject Win32_BIOS with remoteMode=false?
The double exit is really weird, but I do not have right now the means to reproduce it. Could you debug it to see what is happening?
Best regards

I am currently trying without opensession but with only direct Invoke-commands .This seems to be much more stable. As in no extra exit statements are needed. Currently i use executeScript with a small fix which i will upload later (handling of output from script without newline ). I am able to execute remotely with arguments and/or parameters. One bug i need to solve though which is remotemode not handling errors correctly. The normal stream exits before the error stream but the errorstream does give output.


Implemented fc on grid layout which applies min-width to the card inside, hence no need to add explicit width

Modified Layout file to map fc to min-width
Added a Test case
Ran tests
Ran pre-commit
Tested Locally with a python script with the proposed code provided in issue

@quest-bot loot #1780

@arcanaxion

Tx @HatimZ I like your solution, it is simple and neat. We would need a bit of documentation and also an example in doc/gui/examples. 👍

Okay sure!

@HatimZ Indeed this is short and effective.
In order for us to integrate this, as @FredLL-Avaiga said, we would like a little something to expose it to users:

A short and relevant application that demonstrates the feature.
There are a few such examples in [taipy]/doc/gui/examples/[controls|blocks] that you can get inspiration from.
So far we have no example for the layout block, and we need to work on it.
We can certainly be in charge of fitting your proposal there, with code conventions and formatting constraints.

A paragraph or two explaining, beside the code comments, what's going on.
We will transform this input into a Usage section in the documentation, pointing to the code example we would have integrated.
Thanks!

#2039
Thankyou for the feedback, will wrap it up today.

Are you still working on this PR @HatimZ  ?
If you are, please update your branch and answer the questions
If you are not, please close the PR

layout columns property already supports standard css : we're not inventing new keywords
Tx for your time and efforts @HatimZ
We should have better analyzed the issue at first

hey @HatimZ  congratulations on the merged PR.
could you please contact me at<EMAIL_ADDRESS>to ship your swag? :)


TC-DA-1.5: Try using a random discriminator (WIP, just testing)

https://github.com/CHIP-Specifications/chip-test-scripts/issues/596

test was unsuccessful, this is an avahi problem. Closing.


Doesn't work on "wholesale" pages

When I search for something I get something like this:
https://www.aliexpress.com/wholesale?catId=0&initiative_id=SB_20210223111350&SearchText=printer
Which the script doesn't detect and even if I include it in the regex it still doesn't clean the urls in the results. Can you make it compatible?
btw, it also doesn't work on these pages which are suggested searchs:
https://www.aliexpress.com/w/wholesale-impresora-termica.html
Thanks.

Hey sorry. Entirely missed this. Almost two years later here I am tho 😅
What would a clean url of that look like? The idea of this script is to strip unnecessary data from the URL


is there any docs about register_pattern, register_compute, register_schedule?

hi,
Is there any docs about pattern, compute and schedule for help developers to understand the design?
Thanks

They are packed functions which allows user to define operator attribute("TOpPattern", "FTVMCompute", "FTVMSchedule") in python.
Some basic concepts about packed func: http://docs.tvmlang.org/dev/runtime.html#packedfunc
It would be better if we have more documentations about this part.

@kevinthesun
what's the relationship about leaky_relu in python/nnvm/top/nn.py and leaky_relu in tvm/topi/python/topi/nn/elemwise.py?
Thanks

Operator implementation(how to do actual computation) is defined in tvm. Operator prototype, such as number of inputs/outputs and parameters, is defined in nnvm. To compile the whole graph, we need to register compute(implementation) and schedule(strategy to optimize) for each operator in nnvm. This is done by register_compute and register_schedule. These two functions add "FTVMCompute" and "FTVMSchedule" attributes to operator to call the implementation function in tvm.
Actually these register can be directly done in C++: https://github.com/dmlc/nnvm/blob/master/src/top/nn/nn.cc#L391
With python, it would be easier if you want to customize compute or schedule for your operator.

@kevinthesun
leaky_relu in tvm/topi/python/topi/nn/elemwise.py is decorated by tvm.tag_scope, and leaky_relu in src/top/nn/nn.cc#L391 is also for compute, what's the difference between these two leaky_relu implementation?
Thanks


Reset password proposal #2

Hi, this is a mayor update. Everything works except one : how to hash and salt new password ? Maybe need different issue

[x] Require email to register
[x] Create reset password at login page
[x] Generate random string as new password
[x] Send reset password link and new password via e-mail
[ ] How to hash and salt new password?

And one more, maybe user can change password after login due to random password generated by this issue is hard to remember. I will wait your review about this. Thanks

@wildan3105 going to check this out now! Will get back to you soon!

@wildan3105 I am getting an error when attempting to send a reset email

smtp: '454 4.7.0 Too many login attempts, please try again later

Are you seeing this as well? As for the hashing and salting a new password, I will have to look into it more. I somewhat am regretting using the passport stack for auth, as it has caused me some trouble as well.

No, try this configuration (in my case I use gmail) :
server = email.server.connect({
    user<EMAIL_ADDRESS>    password: 'password',
    host: 'smtp.gmail.com',
    ssl: true
});

I am getting an error when attempting to send a reset email

Yeah, you better do that. I myself used simply-encryptor to encrypt user's password.

I will have to look into it more. I somewhat am regretting using the passport stack for auth, as it has caused me some trouble as well.

Please notify me if anything wrong, so far everything works except the hash and salt

Yes I am looking into the salt/hash issue, but your PR looks great and I will merge it once I solve the other issue!

@wildan3105 I'm sorry I am just getting to this in depth. Classwork has been very heavy since midterms are approaching. Could you explain the flow of the reset link and reset pass, or what they are meant to do exactly?


Add support for configurable node groups

This PR makes it possible to specify node group information when running cluster-autoscaler:
./cluster-autoscaler-amd64 --cloud-provider=juju --nodes 3:10:kubernetes-worker

where 3 is the min size, 10 is the max size, and kubernetes-worker is the application name. The --nodes option can be specified multiple time to support multiple node groups.
This needs further work. The application name is ignored for now, and there are still some hard-coded assumptions that there is only 1 node group. I'm working on it.

This is ready for review. To run the cluster-autoscaler with these changes, include the --nodes 1:3:<model>,<application> option specified one or more times. For example:
./cluster-autoscaler-amd64 -v=5 --kubeconfig=/home/gkk/.kube/config --cloud-provider=juju --max-node-provision-time 30m0s --scale-down-unneeded-time=5m0s --nodes 1:3:test,kubernetes-worker

I've split this up into two commits. The first commit is just reformatting with gofmt -w *. The second commit has the functional changes. Consider reading the second commit specifically if you want to understand the functional changes without all the reformatting noise.

This is ready for review. To run the cluster-autoscaler with these changes, include the --nodes 1:3:<model>,<application> option specified one or more times. For example:
./cluster-autoscaler-amd64 -v=5 --kubeconfig=$HOME/.kube/config --cloud-provider=juju --max-node-provision-time 30m0s --scale-down-unneeded-time=5m0s --nodes 1:3:test,kubernetes-worker

I've split this up into two commits. The first commit is just reformatting with gofmt -w *. The second commit has the functional changes. Consider reading the second commit specifically if you want to understand the functional changes without all the reformatting noise.

@Cynerva just confirming this isn't a typo:
1:3:test,kubernetes-worker not 1:3:test:kubernetes-worker.  I'd expected colon separators for everything here -- and designed the charm around colon separators.  should i update or can you?
secondarily.  does this have to be a "name" or can it be model uuid?
juju status -m 3523dd89-c23e-4a7b-84f1-9d8f807b0c09

works just fine for me.

@Cynerva just confirming this isn't a typo:
1:3:test,kubernetes-worker not 1:3:test:kubernetes-worker. I'd expected colon separators for everything here -- and designed the charm around colon separators. should i update or can you?

Yup, not a typo. I split on , because while the SpecFromString function does allow for more than 3 :-separated fields, it wasn't clear to me that this is intentional behavior.
That said, I just searched and I see there is precedent in the Hetzner cloud provider code for using more than 3 :-separated fields. See the Hetzner cloud provider README. So we may as well do the same. I'll update this PR to separate on : instead.

secondarily. does this have to be a "name" or can it be model uuid?

UUID should work too


Improved responsiveness of Showcase form & removed empty ruleset.

Hello, I noticed that the submission form select and fields were not responsive for a device with a maximum width of 400px.
Before:

After I fixed it, ensuring the rest of the responsive elements are in place:

Also eliminated a single unneeded ruleset.

Thank you for this, wow! I will test this soon and hopefully merge! @dipamsen or @fturmel feel free to take a look too if you have a minute!

I like it! Could we try using 100% instead of arbitrary pixel values, and apply them to the --small (600px) breakpoint instead? That way the fields will fill up the width more consistently and we'll get rid of the remaining broken state between 400px and ~525px browser width.
As for removing the empty root css class in the tracks Header component, it wasn't bothering me since most components are structured with a root class and roughly 5 of them are empty.
If we do want to remove the empty class properly though, the reference to it in the component should also be deleted:
https://github.com/CodingTrain/thecodingtrain.com/blob/fcddb57a2b684a908e5231c114c4dfe9df7cee32/src/components/tracks/Header.js#L14

Hi @Zack-Dx did you mean to close this? I would like to incorporate it! Apologies for not following up about it sooner.

Hi @Zack-Dx did you mean to close this? I would like to incorporate it! Apologies for not following up about it sooner.

No issues Shiffman, I'll create a new pr fixing this I'm just busy these days a bit due to my exams, I'll fix by upcoming weekend. Thanks love you.


Model readiness check in hpc load balancer

Ensure a model instance is only called after it has completed its setup phase (i.e. left the model instance constructor). Some models may have considerable setup cost, and calls to them during setup may cause errors or (at the very least) avoidable delays. In kubernetes we can achieve a readiness check by checking if the server's /Info endpoint is reachable.

Is --worker-start-cmd blocking? If so, maybe spawn our model server independently, but put a blocking loop until /Info is reachable in the cmd?

Now part of job launching script, which happens to be blocking now, so does the trick.


install neovim on github workers to make tests work

#12 moment on windows, it seems, @noib3

alright, I will look at mlua tests later, since im going to sleep now, but right now it seems that i found a weird solution that will probably work. i basically ignore every unresolved external symbol error in linker

i will push it to this branch if it will work

hmmm

good news: it fixed the issue, but now there's another error

good news: it fixed the issue, but now there's another error

That's an easy fix, I thought Windows would behave like macOS and Linux when building a library in that in prepends a lib to the name of the compiled artifact, but apparently it doesn't. Will fix it later, for now you can just rename oxi_tests.dll to liboxi_tests.dll.
Btw, the contents of /.cargo/config should probably be appended to /oxi-tests/.cargo/config. A cargo build at the root of the repo is expected to fail, what matters is that the oxi-tests crate (which depends on nvim-oxi) builds.


UI customisation from legacy UI

Check the supported list of configurations (https://github.com/apache/cloudstack-primate/blob/master/src/config/settings.js#L29) against the legacy UI config file: https://github.com/apache/cloudstack/pull/3258/files

PR merged


fix: Handling 2022_03 breaking changes

2022_03 bundle changes the following behaviour:

Share NAME column in accounts using the new org naming is returned as ORG.ACCOUNT.SHARE, instead of the old ACCOUNT.SHARE
Task PREDECESSORS column is now always returned as a JSON array (even when it's empty)
File format VALIDATE_UTF8 option is obsoleted, attempting to set it to false now fails

Note that the existing task implementation only handles one task root and this change continues that. While you can only specify one AFTER in CREATE TASK, you can add more with ALTER TASK ... ADD AFTER. Supporting this would require a breaking change to make the after parameter a list and handle state for multiple roots, this should be done in a separate contribution.
Test Plan

[x] acceptance tests

References

2022_03 changes
SHOW TASKS Command & TASK_DEPENDENTS Function: PREDECESSORS / PREDECESSOR Column
SHOW SHARES Command & Data Sharing UI: Changes to Output
VALIDATE_UTF8 File Format Option

/ok-to-test sha=9babf75

Tests should be fixed now, ready for another run 🤞

/ok-to-test sha=8d02816

/ok-to-test sha=3b95c53

@sfc-gh-swinkler do you know when the release will be available ? it's quite urgent for us regarding the synchronization of share names between terraform and snowflake


array column names are sorted

Hi,
Should the behavior be changed, so the json follows the ABAP structure? Or add an option to keep the columns/structure fields in the same order?

Hmm, you mean for table serialization?

Hmm, you mean for table serialization?

yes

yes

Name/value pairs in json are unordered. If you want ordered lists in json, it needs to be in an array.

Name/value pairs in json are unordered. If you want ordered lists in json, it needs to be in an array.

{"foo": 2, "bar": 1} and {"bar": 1, "foo": 2} is the same in json, but when serializing ABAP structures they are ordered, and it would be easier to compare the json vs ABAP if they have the same ordering

{"foo": 2, "bar": 1} and {"bar": 1, "foo": 2} is the same in json, but when serializing ABAP structures they are ordered, and it would be easier to compare the json vs ABAP if they have the same ordering

The purpose is clear. I think it might be a parameter. But not sure how to implement it from the frst glance.
The fields can be added freely or as a structure. And somehow the latter has to memoise the order. While the first does not need too ... hmmm. Might be crutchy... i'll think about it. Ideas also welcomed :)

The purpose is clear. I think it might be a parameter. But not sure how to implement it from the frst glance.
The fields can be added freely or as a structure. And somehow the latter has to memoise the order. While the first does not need too ... hmmm. Might be crutchy... i'll think about it. Ideas also welcomed :)

Some kind of additional force_order field ...

Some kind of additional force_order field ...

imho, it should be { "structure_name": [ "foo": 2, "bar": 1 ] }. this will keep the order

imho, it should be { "structure_name": [ "foo": 2, "bar": 1 ] }. this will keep the order

So, the concept:

Instance flag keep_field_order (or keep_field_order_for_struc), set via create_empty or (maybe???) by another method set_keep_order
add a field order to ty_node.
on adding of a structure, if the flag is set, convert_struc should fill the order with sy-tabix
stringify: probably a third sorted mkey for mt_json_tree and key selection in stringify_set will do the job

So, the concept:

Instance flag keep_field_order (or keep_field_order_for_struc), set via create_empty or (maybe???) by another method set_keep_order
add a field order to ty_node.
on adding of a structure, if the flag is set, convert_struc should fill the order with sy-tabix
stringify: probably a third sorted mkey for mt_json_tree and key selection in stringify_set will do the job

@larshp should work, pls try. Docs are here: https://github.com/sbcgua/ajson#keep-item-order

@larshp should work, pls try. Docs are here: https://github.com/sbcgua/ajson#keep-item-order

cool, I'll try it out tomorrow

cool, I'll try it out tomorrow

working,
https://github.com/abapGit-tests/data1/pull/2/commits/441e2d0a6e809d5456b4832d9cc513827218d61b
https://github.com/abapGit/abapGit/pull/4399
closing

working,
https://github.com/abapGit-tests/data1/pull/2/commits/441e2d0a6e809d5456b4832d9cc513827218d61b
https://github.com/abapGit/abapGit/pull/4399
closing


setup email and dns

i bought the following domains

gitevents.org
gitevents.com
gitevents.co.uk

@PatrickHeneise which to use? org or com?  others are for redirects

You think it's necessary? We can just create a gh-page and be github.io/gitevents.

its for a support email address
eg contact@gitevents
also for redirects and to prevent type squatters..

id rather have them before promoting :-)

Since we're git-driven, shouldn't be support be through GitHub issues? :P

I have the same doubt than @PatrickHeneise
However with a domain the gh-page may be more attractive as some projects do (e.g. mocha)

no rush, we have them bagged for a future date..


Stripe Signature header key not matching documentation

Describe the bug
The key that identifies the Stripe Signature header in requests originating from my Stripe App doesn't match
the value specified in Server Side logic doc
To Reproduce
Steps to reproduce the behavior:

Check code snippet in Server side logic doc
Trigger request to external server
Examine Header values in request to external server

Expected behavior
I would expect the header keys to match the values provided in the docs.  At the least this failure can cause all requests to appear unverified.  Where code relies on the key as an index for header retrieval this can cause the external server to crash.
Screenshot

s
Desktop (please complete the following information):

OS: macOS 12.4
Browser Chrome
Version 103.0.5060.53

Hi @rmanzer-stripe, is this a request that you're initiating from your app to your backend? Something like this?
return fetch(`https://example.com/${endpoint}/`, {
      method: 'POST',
      headers: {
        'Stripe-Signature': await fetchStripeSignature(),
        'Content-Type': 'application/json',
      },

If so, can you double check the spelling of Stripe-Signature in your code? If not, can you help me understand where the misspelled Stripe-Sgnature is coming from?

:facepalm:


[iOS] Fabric: Add font variant support

Summary:
Fixes #44064
Changelog:
[IOS] [FIXED] - [iOS] Fabric: Add font variant support
Test Plan:
Demo in #44064 .

Awesome! Thank you


Append Endpoint suffix to storage blob connection string

Fixes publish issues due to missing endpoint suffix.
Verified connection string from Azure Portal for storage account, validated with local testing.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.002%) to 41.674%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-bindings/src/common/azureFunctionsUtils.ts
1
80.65%

extensions/sql-database-projects/src/common/httpClient.ts
1
66.18%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
2
50.74%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
30328

Relevant Lines:
67383

💛  - Coveralls

Did something change recently to require this?

Yep we recently migrated from old azure-storage npm package in PR #22664


is it possible to put the calendar as an element in page?

is it possible to put the calendar as an element in page?

With this component you can use it either as a modal or as a popup. But you can still use it in a page if you can do some modifications in the source code.


Please update it to React Native new version

I am unable to update my project because of this library.
Please update it to React Native version 0.70.6

Hi @nnrohu , we regualary update this library, so we'll push an update soon. If you'd like to contribute, you can open a pull request.

We've upgraded @bugfender/rn-bugfender to RN 0.70.6. Check the lates version: 2.1.2.


Branch checkout fails in repo menu

Describe the bug
Branch switching is not working from Repository section drop down
To Reproduce

Go to 'http://localhost:9001/dashboard/repository'
Click on 'Branch dropdown list'

Expected behavior
To checkout to the changed branch
Screenshots

Command Line Logs
Gitconvex displays logs in the command line. Please paste the error logs below
{"errors":[{"message":"Cannot query field \"setBranch\" on type \"Mutation\". Did you mean \"addBranch\", \"deleteBranch\", or \"checkoutBranch\"?","locations":[{"line":3,"column":13}],"extensions":{"code":"GRAPHQL_VALIDATION_FAILED"}}],"data":null}

Desktop (please complete the following information):

OS: [Windows]
Browser [Chrome]
Version [2.0.0]

Issue Type

mark with [x] to select the check box

[x] UI Issue
[ ] Performance Issue
[x] Feature Breaking Issue
[ ] Security Issue

Severity

mark with [x] to select the check box

[ ] Critical (The application crashes / breaks completely)
[x] High (Blocks you from performing an critical operation)
[ ] Moderate (Bearable or Manageable issue)
[ ] Low (Something is not right, but the impact is minimal)

@Nageswari-droid fix delivered, please test and update


the support tab/picture looks clickable and changes to a clickable cursor, but isn't clickable making for minor user confusion

i want to click it

                <div class="square support onclick="nav('mailto:

contact@openconnecto.me')"">
failed.
fix it?
On Thu, Jun 18, 2015 at 12:21 PM, ron boger<EMAIL_ADDRESS>wrote:

i want to click it
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/openconnectome.github.io/issues/8.

--
the glass is all full:  half water, half air.
openconnecto.me, jovo.me, office hours
https://www.google.com/calendar/embed?src=e2ktu4lrgul8anp8hclrcminp8%40group.calendar.google.com&ctz=America/New_York

Ah, didn't see the change of assignment. I'll take care of it then

I don't think this matters anymore
On Sunday, June 21, 2015, Jordan Matelsky<EMAIL_ADDRESS>wrote:

Ah, didn't see the change of assignment. I'll take care of it then
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/openconnectome.github.io/issues/8#issuecomment-114004510
.

--
the glass is all full:  half water, half air.
openconnecto.me, jovo.me, office hours
https://www.google.com/calendar/embed?src=e2ktu4lrgul8anp8hclrcminp8%40group.calendar.google.com&ctz=America/New_York


Cleanup and Reimplement Checks

Some tests had FormData which was not handled properly with current MSW version, Pete created a workaround that implements a basic .formData() on MSW request which allows us to recheck tests.
Originally posted by @petebacondarwin in https://github.com/cloudflare/wrangler2/pull/2440#discussion_r1054066757

https://github.com/cloudflare/workers-sdk/blob/4abc759b6f87ad768a31a8b7d72b3dbd3a747a8a/packages/wrangler/src/__tests__/kv.test.ts#L325-L335

This is no longer relevant—we upgraded MSW to a newer version which properly supports FormData in #5887


remove is_bootstrap parameter

remove is_bootstrap parameter from rabit api
implicit use signature and loadcheckpoint flag instead

@hcho3 @trivialfis @CodingCat this is minor pr remove is_bootstrap parameter from rabit api to make it more user friendly.  https://github.com/dmlc/xgboost/pull/4808 would benefit by having a smaller code change.

could you complete the description about when we load bootstrap cache now?

goog catch, let me update documentation as well.

@CodingCat done


Version flag

This is a feature request: could you add a --version flag, to check which version one is currently running? Or is there a better way to check the version?

It has --version and -v flags.

Ah, I see, on dev-master it has a --version and -v flag indeed. Returns unversioned for now, looking forward to the next release. :D

Now works always in 2.0.14 version.

@wapmorgan Thanks a lot, works like a charm!


fix: Adjusted color of bracket highlight in light theme

close #331
Starting from version 2.1.0, the contrast ratio of bracket highlights in light mode was lowered. We have adjusted this to match the display style of version 2.0.2.

version
screenshot

ver 2.0.2

ver 2.1.0

My suggestion

Someone else mentioned this to me- I'll look into it soon

Actually, a little confused by your post above- in your suggestion screenshot, it looks the same as 2.1.0? What am I missing?

@sdras Apologies for the confusion.
As you can see in the enlarged image below, it seems that the brackets have become almost invisible in version 2.1.0.

version
screenshot

ver 2.0.2

ver 2.1.0

My suggestion

I have the same issue. Almost invisible for me too..

Ah I see, thank you! I may revert the change from the last version rather than taking the PR because I've heard dark mode broke too, I'll get this in today

Thank you for reply. It would be better to revert the commit.
So, I will close this PR.
Have a great New Year✨

Thank you so much for this! This should be resolved now- I just published, might take an hour or two.


Question: UIView supported?

Does is support adding a custom UIView?
Bests!

Hey! Hope this code is helping you 😃
Like any other UIView, you can manually addSubview, but I have no plans on making it support inline UIViews. The reason being that this is just a thin wrapper around a UIWebView, and I'm not really sure how you'd embed a UIView inside the HTML being displayed inside.
Sorry!


[Question] how to customize the replace range when completion item was selected?

Description
follow the image, the 'next' completion item actually is '->next', so when i pick the 'next' completion, it would be the second image

and i try to use
range: {      insert: range,      replace: range }
but not working, can anyone tell me how to cusomize the replace position to resolve that problem like the follow expected image?

How do you solve this problem now? I have the same problem. I also tried to use range to implement it. However, it is found that the effect is not consistent with the understanding of the document description, and the effect is very strange.

hi, I finally solved it through additionalTextEdits,

but I only did this special treatment for c++ and c, and i hope this could help you.


Variable in Platformer project hanging for a bit before beginning to update.

Tying to script an action that lets you perform an action while in the air. Using the Player Fields plug-in but reporting the bug here on recommendation of the Discord server, incase th issue is with GB Studio itself.
Currently have a test project set up to fire a bullet when the player is in the air, as well as report the status of the "onGound" Bool when start is pressed. As you can see in the attached gif, for the first minute or so, the variable doesn't update, constantly reporting 0 when start is pressed regardless of player status, and fires bullets constantly.
After ~ a minute, it suddenly starts working as expected, the variable updates when checked, and bullets only fire in the air.
On 3.02, on macOS Monterey.

From the Discord conversation you're using an On Update script to store the is on ground variable

Is the actor that contains this on update script pinned?  otherwise it'll be out of the screen the moment you scroll to the right. Out of the screen actors are disabled and don't run their on update script.

From the Discord conversation you're using an On Update script to store the is on ground variable

Is the actor that contains this on update script pinned? otherwise it'll be out of the screen the moment you scroll to the right. Out of the screen actors are disabled and don't run their on update script.

I’m using a pinned hidden actor as a Game Manager, yes. Would it help to link the project file?

Yes, please, include a zip of the project.

Pinned sprite in the corner is in the top left corner with the variable update. Scene has the Attach to button script.
test.zip

Another observation: It seems the variable starts working not after a set amount of time, but after moving off and then back on the first platform. I tired jumping back on the first platform from each side, and as soon as the Player lands on that one in particular, the variable starts working as expected.

Another observation: It seems the variable starts working not after a set amount of time, but after moving off and then back on the first platform. I tired jumping back on the first platform from each side, and as soon as the Player lands on that one in particular, the variable starts working as expected.

Okay, it has to do with the hidden Game Manager sprite that's updating the variable. If you disable the On Init Hide Actor action, everything works as expected immediately.
Maybe the reason jumping on that first platform was triggering it working, was that the hidden game manager actor's location was back on screen. It's pinned so it should be moving, but jumping back on that first platform would have where it's initial location in the Scene is (I'm not a programmer so I'm just spitballing haha)

Indeed. Hidden actors aren't suppose to be running the on update script, except when #884 happens.

Indeed. Hidden actors aren't suppose to be running the on update script, except when #884 happens.

Huh... okay. It looks like I've run into the same issue as #884 then, except in my case, it made it work how I intended, because I was using the On Update function incorrectly.
The only odd thing is the hidden sprite was pinned to the screen, so it should never have left and come back to the viewport. I'd assume pinning an actor is essentially in the On Update function under the hood?


rFOX address updated confirmation modal spelling mistake

Overview
THORChain is written as THORCHain in the address updated confirmation modal
References and additional details

Acceptance Criteria
Should be THORChain
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

Claim modal says cooldown finished in 9 minutes when it should say "finishes in 9 minutes"


Recommended way to include API keys in requests

Once issued an API key, what is the recommended way to include it in requests, specifically with the PyPi package? We could just tack it on as a URL parameter (though I don't know the name of the parameter), but it would be nice if this was supported in the PyPi package somehow.

Most of the API functions in our Python libs(1.4) supports an api option parameter as a way to provide your API key. E.g.
https://github.com/blockchain/api-v1-client-python/blob/master/blockchain/blockexplorer.py#L11
The URL parameter is 'api_code' if you are using the HTTP endpoint directly.


Swift has been updated to 4.0

Swift has been updated to 4.0，This is still 3.1，If you have time you want to update it.Thank you very much.

@VineFiner the new version of this repo has been moved to https://github.com/gotranseo/template

Thank you


simple usage / run issue

Hi, sorry for a trivial question, I am evaluating a migration of a rather large index (4mio fulltext indexed documents) from 4.3.x to 8.x
Been bumping around some minor issues up to now, but nothing that could not be tuned or solved.
But I have a rather simple usage question. Let's say I launch the simplest converter pattern as in
import org.trypticon.luceneupgrader.*;
import java.nio.file.*;

public class Main
{
  public static void main(String[] args) {
    System.out.println("Launching indexupdater");
    Path path = Paths.get(args[0]);
    System.out.println(path);
    try{
      System.out.println("guessing version");
      LuceneVersion guessed = new VersionGuesser().guess(path);
      System.out.println(guessed);

      System.out.println("setting up indexupgrader");
      IndexUpgrader upgrader = new IndexUpgrader(path);
      upgrader.upgradeTo(LuceneVersion.VERSION_8);
    }
    catch(Exception e)
    {
      System.out.println(e.getMessage());
      e.printStackTrace();
    }
  }
}

the question is:
what libraries/jars is the tool expecting me to have in the classpath?
currently I put - by try-and-error and not by really knowing it for sure - these in the classpath:
lucene-backward-codecs-5.0.0.jar
lucene-backward-codecs-6.0.0.jar
lucene-backward-codecs-7.0.0.jar
lucene-backward-codecs-8.0.0.jar
lucene-codecs-4.3.0.jar
lucene-codecs-5.0.0.jar
lucene-codecs-6.0.0.jar
lucene-codecs-7.0.0.jar
lucene-codecs-8.0.0.jar
lucene-core-4.3.0.jar
lucene-core-5.0.0.jar
lucene-core-6.0.0.jar
lucene-core-7.0.0.jar
lucene-core-8.0.0.jar
luceneupgrader-0.5.2-SNAPSHOT.jar

but I might as well be completely wrong on this, and the only jars you expect me to put in could be, as from the .m2 build directory, the
{...}
./.m2/repository/org/apache/lucene/lucene-core/8.5.1/lucene-core-8.5.1.jar
./.m2/repository/org/apache/lucene/lucene-backward-codecs/8.5.1/lucene-backward-codecs-8.5.1.jar
{...}

Sorry if this is such a brain-dead-question, but I am new to gradlew and the USAGE part on your documentation indicates only the quick "dependencies" info
dependencies {
    implementation("org.trypticon.luceneupgrader:luceneupgrader:VERSION")
}

which, probably, points to the .m2 files above?
thanks ahead for clarification

The luceneupgrader jar bundles all the earlier versions of Lucene necessary to run, except for the current version it depends on (8.5.1) which it gets as a dependency, so you don't need the earlier versions on the classpath at all.
And actually, having the older versions on the classpath would probably break classloading because they contain largely the same class files. The copies inside luceneupgrader have been bumped to a different package name to avoid that.

thanks for clarification - I hadn't looked so much inside as to understand you had copies inside luceneupgrader yet. I'll switch to the 8.5.1 jars only then, makes of course sense.


Features/detect headphones

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Test the code

What to Check
Verify that the following are valid

...

Other Information

Adam, noticed few bugs:

on fresh install if bluetooth is connected before, in audio device selection device is not displayed

Audio device list displays device name but button says bluetooth

@iaulakh

Added check for permission approval to init bluetooth (for android 12 Runtime permissions for bluetooth).
Fixed SetupControlBarView (Shows device name & Headset when plugged)
Removed Comment from last PR (from merge commit)
getAdapter() instead of getDefaultAdapter() (deprecated update)

@iaulakh I think good now (no memory leak) small fix for that.


Update examples_test.go

Same change but for version 7

I will merge this once I create a branch for v7

closing this, changes were merged in from v6 into v7 before creating v7 branch
P.S. @ardan-bkennedy v7 has been released! see notes here: https://github.com/bluesuncorp/validator/releases/tag/v7 according to the code I saw in your training material, this should be a drop in replacement.


BGP issue with IPV6 and multipath/ecmp

On a cluster with IPV6 only connectivity, i'm trying to enable BGP with nodeToNodeMeshEnabled: true.
We have two routers in our datacenter that distribute the default gateway via router advertisements (RA) for redundancy.
By default, linux accepts both gateways and uses ecmp. The network works well, etc ...
However, there is an issue with Calico, see screenshot below :

Calico fail to parse the default route.
Steps to Reproduce (for bugs)

Enable BGP in an IPV6 network with two routers.

Your Environment
Kubernetes RKE2 v1.27.12 +rke2r1
IPV6 only
Calico v3.27.2
All nodes are on Debian 12
Thanks for your help !

This error seems to be coming from the "CalicoNodeStatus" controller, here: https://github.com/projectcalico/calico/blob/e5923877435c699200777047795d68b77ff0fc93/node/pkg/status/populators/route.go#L153-L156
I think this means it shouldn't be impacting actual networking, which seems to match what you're describing, and can be circumvented by deleting and CalicoNodeStatus resources (https://docs.tigera.io/calico/latest/reference/resources/caliconodestatus)
This does seem like a bug though - that status logic likely isn't expecing the ECMP routes and doesn't have logic to parse them.


README improvements:

Clarify the who/what/when of some of the setup and development steps.
Provide additional links to external resources.

@deidyomega
Give this and https://github.com/CodeForFoco/CERP-backend/pull/25 a skim when you have a chance  and let me know if it's accurate and easy to determine which steps are needed and when.

Coverage remained the same at 4.688% when pulling 0f0cecd6dd02c2c334c209dd1082e89460800486 on abettermap:readme-clarify into c07ca9ea4894f82d6105ffd64f090b713ad30f6d on CodeForFoco:master.

Change Set the Database Source --> Set the API Source
Other than that it looks great, make the change, resubmit, and I'll merge :smile:

Alrighty, all set.

Coverage remained the same at 4.688% when pulling 3ca7943f19a26fd7dd861d4e500b5e38e2c90e1b on abettermap:readme-clarify into c07ca9ea4894f82d6105ffd64f090b713ad30f6d on CodeForFoco:master.


Update db-query-builder.md

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
no

Merged. Thanks!


Add ability to discard reordering

This PR do not break BC.

This looks ok to me :). Does that make sense to you @docteurklein ?

Closing as outdated


Page not loading in experience editor after implementing in Sitecore JSS App(React)

I have implementation this OIDC Client in Sitecore JSS App(React). Looks like working fine in connected and disconnected mode. But when we load the in page in Sitecore experience editor it is throwing below error.
Server Error in '/' Application.
Cannot read property 'getItem' of undefined
TypeError: Cannot read property 'getItem' of undefined
at t [as get] (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:2067:14912)
at e.t [as _loadUser] (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:2113:46495)
at e.t [as getUser] (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:2113:32492)
at new t (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:2067:41166)
at new e (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:2113:32004)
at new AuthService (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:28825:22)
at new AuthProvider (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:28893:25)
at c (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:11787:325)
at Ua (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:11790:16)
at a.render (C:\inetpub\wwwroot\samplesite\dist\sample-jss-app\server.bundle.js:11796:48)
Is there any workaround to fix this issue?

No idea, sorry.

Hi Brock Allen,
Is it possible to use Cookie as store in this client? I'm suspecting since the application doesn't have access to use sessionStore/localStorage as store.
Thanks.

That's been discussed elsewhere. Also, if you are using a cookie, that means you have a backend? If that's the case, then perhaps it doesn't make sense to do OIDC/OAuth2 from the client-side (and thus you might not need this library at all).


Refactor/state prs

This resorts to checking GitHub on every page reload to verify the state of the PR. It is sub optimal because it queries GitHub frequently, but is the only solution for now as we are not using webhooks.


Implement more taskbar customization features with FalconX as a PowerToy

Summary of the new feature/enhancement
This feature would help users to have more customization options for their taskbars without any dangerous registry editing tools etc. It allows users to position their taskbar icons in the center of the taskbar similar to the dock approach on other OS.
It also allows the user to customize the look and feel of the taskbar's background with options like transparent background, blurred background or acrylic background.
This will bring a lot of joy to some group of users who always look for more ways to customize their desktop experience.
See here:

Direct link: https://chrisandriessen.nl/web/FalconX.html
Store link: https://www.microsoft.com/en-us/p/falconx-center-taskbar/9pcmz6bxk8gh?activetab=pivot:overviewtab

I don't know how big of a problem the paid Store release is since the actual tool is open source.
Thanks a lot already
Examples:

This would be amazing! Using it on my Machine.

More taskbar control in general would also be useful.

Have a two-line clock on my second status bar (time on primary monitor, time+date on secondary); DisplayFusion allows this
ability to pin different icons to different taskbars. (DisplayFusion has this)
Move icons pinned on secondary taskbar monitor to the opposite end (ie, left-pinned on primary, right-pinned on secondary)
Resize/reshape the tray overflow menu (make it short and wide, not square)
Make the tray overflow menu ALWAYS show up on top of other items. Yes, I mean that notifications/toasts from other windows should not be able to pop up on top of it, especially not when it has mouse focus.
Reduce the width of icons pinned to the taskbar when the corresponding application is closed

opened applications are wide like usual, but closed applications should be as close together as tray icons currently are

I like the idea and I use two another open-source plugin to custom my taskbar now.

One is CenterTaskbar. The project is here https://github.com/mdhiggins/CenterTaskbar, the project is a .net framework project. I really hope this function can be added into the powertoys
I don't know anything about .net or I will try to make a PR :)
Another one is taskbar translucent, here
https://github.com/TranslucentTB/TranslucentTB
it still a opensource project.

THIS! Also, I would vote for adding an option to open pinned item with a  double click instead one (to avoid accidental clicks)

See https://github.com/microsoft/PowerToys/issues/6433#issuecomment-689183842

Hey all, just popping in a (admittingly general) comment here. Just came across a video of Thio Joe where he quickly shows a number of apps, regarding tweaking Windows: https://www.youtube.com/watch?v=n7lykL7ZELQ
Not promising everything for this issue, but the Stardock app is interesting! :)


fix(slideer): show the tooltip after dragging the Slider component(#1…

…077)
PR
PR Checklist
Please check if your PR fulfills the following requirements:

[√] The commit message follows our Commit Message Guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[√] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #1077
What is the new behavior?
Behavior as expected. Maintain the tooltip showing after dragging, and hide it after mouse out.
Does this PR introduce a breaking change?

[ ] Yes
[√] No

Other information

PR的标题参考一下 https://github.com/opentiny/tiny-vue/blob/dev/CONTRIBUTING.zh-CN.md

@all-contributors please add @wNing50 for code