NCD clustering accuracy under traditional Settings cannot be reproduced

Thank you so much for sharing the code, it is very helpful for us !
I tried to run the code according to the command you provided in this repo, all the results look normal except for the traditional NCD clustering accuracy.
I assume that running this command line is the result of the UNO + BYOP method:
In the setting of CIFAR10-5 with imbalance ratio 100, in the last epoch, I could only get a clustering accuracy of 44.72:

this is significantly different from 59.3 reported in the paper;
In the setting of CIFAR100-50 with imbalance ratio 100, in the last epoch, I could only get a clustering accuracy of 31.69:

This is also inconsistent with the 35.5 reported in the paper, how do I get normal results?

Hi Zhimao, could you pls share the details of your command and the checkpoint you used to reproduce the results? I have also uploaded the pretrained checkpoints I used for better reproducibility.

For cifar 10-5 with imbalance ratio 100,  the command are as follows:
Pretraining stage: python main_pretrain.py --dataset CIFAR10 --data_dir /home/ubuntu/code/open-set/data --gpus 1 --precision 16 --max_epochs 200 --num_labeled_classes 5 --num_unlabeled_classes 5 --true_prior 100 --comment 5_5_p100 --offline
Discovery stage: python main_byop.py --dataset CIFAR100 --data_dir /home/ubuntu/code/open-set/data --gpus 1 --precision 16 --max_epochs 200 --num_labeled_classes 50 --num_unlabeled_classes 50 --true_prior 100 --pretrained checkpoints/pretrain-resnet18-CIFAR100-50_50_p100.cp --est_epoch 5 --comment run2

Though the commands are respectively for CIFAR10 and 100, they look good to me. Please note that the fluctuation in traditional clustering acc is not a rare issue, which can be sensitive to code environments, computing devices and hyperparameters. Since you mentioned that results under other metrics are normal, you could try multiple runs and see how it goes.

Though the commands are respectively for CIFAR10 and 100, they look good to me. Please note that the fluctuation in traditional clustering acc is not a rare case, which can be sensitive to code environments, computing devices and hyperparameters. Since you mentioned that results under other metrics are normal, you could try multiple runs and see how it goes.

The problem has to be solved.

Though the commands are respectively for CIFAR10 and 100, they look good to me. Please note that the fluctuation in traditional clustering acc is not a rare case, which can be sensitive to code environments, computing devices and hyperparameters. Since you mentioned that results under other metrics are normal, you could try multiple runs and see how it goes.

The problem has to be solved, thanks！

Though the commands are respectively for CIFAR10 and 100, they look good to me. Please note that the fluctuation in traditional clustering acc is not a rare case, which can be sensitive to code environments, computing devices and hyperparameters. Since you mentioned that results under other metrics are normal, you could try multiple runs and see how it goes.

The problem has been solved, thanks！

Though the commands are respectively for CIFAR10 and 100, they look good to me. Please note that the fluctuation in traditional clustering acc is not a rare case, which can be sensitive to code environments, computing devices and hyperparameters. Since you mentioned that results under other metrics are normal, you could try multiple runs and see how it goes.

The results do fluctuate sometimes, but normal results can be obtained, the problem has been solved, thanks！


Why UAA is considering username field instead of email field from uaa users table for sending reset password link ?

Hi All,
while creating user I have not given email address as username  but the user is having email address in email field. when i try to check the forgot password(reset password) functionality it is not sending password reset link to that email address. So again I tried by changing the username to the proper email address  and given that email address (which is username) for sending reset password link  then the password reset link has been sent to the email address which is saved as username filed. Why UAA is considering username field instead of email field from uaa users table? Can anyone please answer to this?

Have you solved this, if not please re-open
Relation of username and email is maybe not known and was changed with https://github.com/cloudfoundry/uaa/commit/3a7749a6d327cacbc7bf93cd50a0e2dee0b935ba but for email there is an email_verified and this could lead to the situation.
code of reset is here
https://github.com/cloudfoundry/uaa/blob/develop/server/src/main/java/org/cloudfoundry/identity/uaa/account/PasswordResetEndpoint.java


Uninstall next-theme and remove all references to dark theme

Description
This PR removes the theme provider library as well as any references to dark theme in tailwind classes. The dark mode config has been removed from tailwind as well.

Issue Ticket Number
Fixes #346

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist:

[x] I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change?
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes needed to the documentation

@josecanhelp Closing your PR as this is already done


spike: propagate parsing errors to controllers

What this PR does / why we need it:
This PR proves that it's possible to propagate translation errors back to controllers. It adds .Status.Conditions to KongPlugin CRD. Programmed condition is populated for the object with values:

Unknown - when the object is seen by the controller for the first time,
True - when the object is successfully translated and sent to the Gateway.
False - when the object fails to be translated.

Both failure and success cases are propagated by means of in-memory events of StatusQueue that are ingested by controllers. KongClient.kubernetesObjectReportsFilter is used to store the last update translation results, including both succeeded and failed objects. It's used by controllers to tell what is the actual status of the object.
Special notes for your reviewer:
This PR serves as a reference prototype and is meant to be thrown away. It's expected that some of the tests won't pass Proper implementation will be done once we create a proper issue and groom it.
Please take a look at my in-line comments to quicker grasp the main points of the changes.

I like this idea as well.
One question I have though, is: is this going to be implemented only for KongPlugin or for other types as well? As far as I understand other types can also fail to validate/translate into kong config because of various reasons, right?

Yes, the goal for the first iteration is to populate the conditions of all objects that we have "error log" validations in place right now (these can be more or less listed with grep -rn continue ./internal/dataplane/parser). Briefly scanning it, there's some in place at the moment; besides KongPlugin there is something for TCPIngress, UDPIngress, TLSRoute, and more.
Implementing new validations  is out of scope for now.

Closing this as it was turned into an issue #3172.


enable package inside module

This PR enables having a an WSGI app in a module below the root where the serverless.yml is (e.g. app/api.py), in order to allow a more flexible structure, specially when having multiple functions in the same service.

Coverage remained the same at 100.0% when pulling 2d7b295f90436d58c557c017b6f68d253920aa5b on lucascosta:package_inside_dir into 8fe2676812c06fddb1b8f0f9fb7723e33b2ed008 on logandk:master.

Coverage remained the same at 100.0% when pulling 4c477945f32b6d7ea1e7cd210d5e73e3c63bfd9c on lucascosta:package_inside_dir into 8fe2676812c06fddb1b8f0f9fb7723e33b2ed008 on logandk:master.

Coverage remained the same at 100.0% when pulling 4c477945f32b6d7ea1e7cd210d5e73e3c63bfd9c on lucascosta:package_inside_dir into 8fe2676812c06fddb1b8f0f9fb7723e33b2ed008 on logandk:master.

Hi Lucas, Thanks a lot for your work on this! I'll test it out later and merge the pull request.


Add Graphql handler

Description
Adding a new handler to send graphql requests, this will be used to communicate with leetcode
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

How Has This Been Tested?
Locally tested using the terminal and added some unit tests as well.
Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works

Current dependencies on/for this PR:

akotadi/setup-migration-db

PR #30

PR #37   👈

This comment was auto-generated by Graphite.

Abandoning in favor of https://github.com/Proyecto-Nutria/otter-welcome-buddy/pull/80


require GPUCompiler 0.14

Codecov Report

Merging #256 (7969320) into main (a873c17) will decrease coverage by 4.83%.
The diff coverage is 52.94%.

@@            Coverage Diff             @@
##             main     #256      +/-   ##
==========================================
- Coverage   81.85%   77.02%   -4.84%
==========================================
  Files          14       14
  Lines        3335     3321      -14
==========================================
- Hits         2730     2558     -172
- Misses        605      763     +158

Impacted Files
Coverage Δ

src/compiler/orcv2.jl
0.00% <0.00%> (-71.43%)
:arrow_down:

src/compiler.jl
82.09% <80.00%> (-1.55%)
:arrow_down:

src/compiler/reflection.jl
93.10% <100.00%> (+0.51%)
:arrow_up:

src/pmap.jl
80.10% <100.00%> (-1.05%)
:arrow_down:

src/compiler/interpreter.jl
31.11% <0.00%> (-60.38%)
:arrow_down:

src/compiler/validation.jl
60.83% <0.00%> (-8.98%)
:arrow_down:

src/logic.jl
75.00% <0.00%> (-5.00%)
:arrow_down:

src/api.jl
48.73% <0.00%> (-1.67%)
:arrow_down:

... and 5 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 a873c17...7969320. Read the comment docs.


Investigate failed Scala Steward PRs

Scala Steward is really fantastic, but I've been doing a terrible job of keeping up with Scala Steward PRs, and there are a lot of failed ones sitting around in Circe projects (#1675 is one example here).
It's not glamorous work, but it would be really helpful for people to go through repos in the Circe org, look for failed Scala Steward PR, and try to figure out why they've failed, and specifically if they have failed because they need changes to code to support the update.

I'm starting with circe-optics.


Potential race condition when generating upstream vs server

Recently, my system was rebooted and came up with VIRTUAL_HOSTs mapped to the wrong upstream definitions, i.e. visiting one domain would render the content of another one on the same server. I was running my custom image fbender/nginx-proxy-custom (last built two days ago) with docker-compose (see config file) and 10-20 containers with VIRTUAL_HOST env. I was able to solve this issue by docker-compose down and docker-compose up again, i.e. restarting the ngnix-proxy-custom container, which – to my understanding – regenerated the configuration file with the set of up and running containers. Unfortunately, I was not able to reproduce this issue with another reboot (as usual with race conditions).
Not understanding what's all going on behind the scenes, my guess is as follows:

Upon reboot, all containers were started automatically (as configured).
At least one VIRTUAL_HOST container was a bit slower to start up than the other ones.
While the container(s) was not fully up, docker-gen ran to generate the configuration file. The remaining containers came to life while the process was going on.
Somewhere in the loops of the template, some entries shifted in their arrays.
And now you have a server definition that points to the wrong upstream.

So my understanding is that docker-gen must read and filter the list of containers, cache that result and only then generate the result to prevent above issue from happening.
May you please look into the issue and confirm above hypothesis, i.e. potential for a race condition? May you please implement the necessary changes to remedy this issue, either in the template or (likely preferred) in jwilder/docker-gen?

Note: Potentially related to #1144.


Blink

The scoreboard still blinks when it refreshes.

This will be fixed in future updates, please hang on!


Fix to support multiple roles in one condition (or command line arguments)

Fix https://github.com/sonots/ec2-host/pull/9

@SpringMT this should fix your problem

0.6.0 is released.

🙇 👍


day is not defined

Context
Hi, I'm getting the error: ReferenceError: day is not defined.
My code:
$cal.clndr({
    events: [{"date":"2016-07-03","title":"Zohydro ER","class":"pdufa"}],
    template: '

<

>

<%= month %> <%= year %>

                <% _.each(daysOfTheWeek, function(day) { %>

<%= day %>

                <% }); %>

                <% _.each(days, function(day) { %>
                  <div class="<%= day.classes %>" id="<%= day.id %>"><%= day.day %>

                <% }); %>

EVENTS THIS MONTH

              <% _.each(eventsThisMonth, function(event) { %>

<%= event.title %>

<%= event.location %>

                <% }); %>

'
});

Expected Behavior
Should not error and should render the provided template.
Your Environment

Version used: 1.4.4
Browser Name and version: Firefox 48b5
Operating System and version (desktop or mobile): macOS 10.11.5
Link to your project:

@tobz-nz I can't seem to recreate this one. The template you have looks fine and when I run it with a basic CLNDR instantiation it runs ok.
I can tell you though (and this might not be your error) that you can't define a JS string that way, but instead need to suffix each line with "/" or use string concatenation. But everything here looks good.
If you can recreate this in an environment like JSBin or JSFiddle then I can step into it further.

Hi Mike, I got it going by hard-coding the string using backtick's (`) to wrap the template string. So seems it was some issue with loading the template from the DOM. I can't think or figure out why it was breaking. but this solution works, so meh - I'll go with it. :)


Add callback for preload completion.

We have several places in the app where we need to trigger image preloading. We can't do it all at one time, as we load resources along the way.
The issue here is that SDWebImage has a nasty side-effect built into it, it cancels any ongoing prefetch jobs when you call prefetchURLs. There's another variant of the method that has a completion block that returns the progress of the prefetch jobs. Would it be in any way possible to add support for a callback so that we could at least queue the preload calls in our end?
Haven't checked Glide if it supports similar behavior.

+1

+1

Yeah this behavior is not ideal. A callback would be nice too. I'm considering trying out some other native library if there's one offering similar performance with a better API. See: https://github.com/DylanVann/react-native-fast-image/issues/13
SDWebImage handles its core functionality really well though.
I'll add a note in the docs for now, and a link to that issue.

Any update on this? Could def use it in my app... Everything else is working great. Thanks for this awesome component

Any update on this?

updates?

this patch might help I ran into this
react-native-fast-image+8.6.3.patch


bp child job exits with code 13 intermittently

We occasionally observe bp jobs fail with exit code 13. It is worse with headless mode.
{30832} 20170621.083802 [  INFO  ] (BP-4) Running Tests. Attempt Number 1.
{30832} 20170621.083802 [  INFO  ] (BP-4) [Attempt 1] Create Simulator
{30832} 20170621.083802 [  INFO  ] (BP-4) Running in NON-headless mode...
{30832} 20170621.083803 [  INFO  ] (BP-4) Simulator 08B5BC17-8E39-4987-BBE7-BB3D861F2563 achieved the BOOTED state
{30832} 20170621.083803 [  INFO  ] (BP-4) Completed: [Attempt 1] Create Simulator 08B5BC17-8E39-4987-BBE7-BB3D861F2563
{30832} 20170621.083803 [  INFO  ] (BP-4) [Attempt 1] Install Application
{30832} 20170621.083916 [  INFO  ] (BP-4) Completed: [Attempt 1] Install Application
{30832} 20170621.083916 [  INFO  ] (BP-4) [Attempt 1] Launch Application
{30832} 20170621.083916 [  INFO  ] (BP-4) Yay, after the launch async call!!![Attempt 1] Launch Application
{30584} 20170621.083928 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
{30832} 20170621.083928 [  INFO  ] (BP-4) Launch succeeded
{30832} 20170621.083928 [  INFO  ] (BP-4) No error
{30832} 20170621.083928 [  INFO  ] (BP-4) Completion block for launch
{30832} 20170621.083928 [  INFO  ] (BP-4) Calling completion block
{30832} 20170621.083928 [  INFO  ] (BP-4) Completed: [Attempt 1] Launch Application
{30832} 20170621.083941 [  INFO  ] (BP-4) Got proxy channel request from test bundle
{30832} 20170621.083943 [  INFO  ] (BP-4) Daemon connection Disconnected.
{30832} 20170621.083943 [  INFO  ] (BP-4) DTXSocketTransport disconnected
{30832} 20170621.083943 [  INFO  ] (BP-4) Test plan started!
{30584} 20170621.083943 [  INFO  ] Simulator 4 (PID 30832) has finished with exit code 13.
{30584} 20170621.083943 [  INFO  ] PID 30832 exited 13.

A temporary solution would be - add a retry mechanism in Bluepill Runner to detect the exit code 13 and retry on that.

perror 13 is permission denied. I think it's worth investigating whether this is a machine misconfiguration before we add workarounds. If anyone else is seeing this, please comment on this ticket. I'll do some poking around the next time it happens.

close old issues, feel free to reopen


@inspire-platform/sails-hook-auth dependency not public

The @inspire-platform/sails-hook-auth dependency in package.json is not public / not found.
npm install @inspire-platform/sails-hook-permissions --save
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@inspire-platform%2fowasp-password-strength-test - Not found
npm ERR! 404
npm ERR! 404  '<EMAIL_ADDRESS>is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of '@inspire-platform/sails-hook-auth'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR!      /Users/cyupa/.npm/_logs/2019-08-02T08_08_25_433Z-debug.log

This has been fixed, thank you for letting us know!


Build aarch64-apple-darwin binaries on CI

This splits the dist matrix job into four and tries to make xtask dist more principled about target and artifact naming.

I have no idea if this will work, but I couldn't figure how to trigger the action on my fork.

I have no idea if this will work, but I couldn't figure how to trigger the action on my fork.

I guess you could get the action to trigger by merging this change into trigger-nightly on your fork?

I think you can also trigger them manually, but actions don't usually run on forks.

Oh, I had to push it to the master branch, then wait for a while.

@lnicola Looks like it's building on your fork after pushing to trigger-nightly: https://github.com/lnicola/rust-analyzer/runs/1591171874

Hmm, looks like the build failed during linking. I think it's because compilation for aarch64-apple-darwin needs to use the Xcode 12 macosx11.0 SDK, but right now, it's using the macosx10.15 SDK by default.
https://github.com/lnicola/rust-analyzer/runs/1591171874#step:9:477
= note: ld: warning: ignoring file /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/lib/libresolv.tbd, missing required architecture arm64 in file /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/lib/libresolv.tbd

There are two ways around this: you can manually select the macOS 11 SDK, according to shepmaster's instructions:
SDKROOT=$(xcrun -sdk macosx11.0 --show-sdk-path) \
MACOSX_DEPLOYMENT_TARGET=$(xcrun -sdk macosx11.0 --show-sdk-platform-version) \
cargo build --target=aarch64-apple-darwin

Or you can set GitHub Actions to run on the macos-11.0 runner, which is what I did on a simple Rust command-line tool project I contributed to. That should require no extra configuration to cross-compile for aarch64-apple-darwin.
jobs:
  dist:
    name: dist
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
-        os: [ubuntu-16.04, windows-latest, macos-latest]
+        os: [ubuntu-16.04, windows-latest, macos-11.0]

Also, will the necessary code change to code/src/main.ts be in this PR or another PR if this gets merged? platform would need to be set to "mac-arm", I'm guessing.

Thanks for looking it up -- I had to step out for a bit. I do wonder if the macos-11.0 binaries will be compatible with whatever macos-latest works on.

Also, will the necessary code change to code/src/main.ts be in this PR or another PR if this gets merged? platform would need to be set to "mac-arm", I'm guessing.

Yeah, I planned to do it in a different PR, since I'm not sure if this is going to work.

@lnicola Looks like the binaries built on CI: https://github.com/lnicola/rust-analyzer/releases/tag/nightly

I don't think they did, there's no ARM binary. Maybe it used the code from the wrong branch?
Anyway, I suppose it would be better to restructure the workflow to build them in parallel.

I don't think they did, there's no ARM binary. Maybe it used the code from the wrong branch? EDIT: ah, the real nightly kicked in and overwritten the release.
Anyway, I suppose it would be better to restructure the workflow to build them in parallel.

Yep, the real nightly kicked in. I wish there was a way for you to tag it to build as separate. Potentially add an on: push: tags: build-* or something and push a tag, and then have the release action push it that tag.
I don't know if there's a way to build them in parallel in the same job. Wouldn't it take more time to set up another whole macOS runner just to build the additional binary?

@richiksc if you don't mind, can you download a rust-analyzer-mac-arm file from https://github.com/lnicola/rust-analyzer/releases/tag/nightly and give it a spin? If you're having issues with Code, you can run it from the command line, e.g. rust-analyzer-mac-arm analysis-stats . in the RA repo (testing both of the x86-64 and aarch64 versions might be a nice benchmark).

I don't know if there's a way to build them in parallel in the same job. Wouldn't it take more time to set up another whole macOS runner just to build the additional binary?

In separate jobs, I meant. Not sure if it's better to use a single job or two, but it might make sense to have two.

r=me

As a super-minor stylistic changes, I am not a fan of [...]

No problem, I shortened those, maybe even too much. I left get_target unchanged since it was different. Arguably, it could be called pick_target or something else, but I'd rather we passed RA_TARGET explicitly.. actually let me to just that.

I triggered another test run (sorry), to make sure the workflow changes still work.

https://github.com/lnicola/rust-analyzer/releases/tag/nightly :tada:
bors r=matklad

bors seems stuck again (I think I've seen it merge workflows changes once), I'll merge manually.

@richiksc if you don't mind, can you download a rust-analyzer-mac-arm file from https://github.com/lnicola/rust-analyzer/releases/tag/nightly and give it a spin? If you're having issues with Code, you can run it from the command line, e.g. rust-analyzer-mac-arm analysis-stats . in the RA repo (testing both of the x86-64 and aarch64 versions might be a nice benchmark).

@lnicola I wasn't able to test this earlier due to my timezone. I'd love to test the binary today but I can't see a release on your fork anymore - was it deleted for some reason? I can definitely run the benchmark in the rust-analyzer repo if necessary.

Oof, I deleted the branch and they're gone. I triggered a new build, but they don't seem to have a lot of macos-11.0 runners, so it's gonna take a while to run. I'll ping you.

I can definitely run the benchmark in the rust-analyzer repo if necessary.

It's not necessary, of course :-).

@richiksc I think it's ready

@lnicola Hmm, the release seems to have both binaries with the old naming scheme ("rust-analyzer-mac") and the new naming scheme ("rust-analyzer-x86_64-apple-darwin") - are you building it twice?

both names are essential, to give time for non-vs-code clients to migrate
to new names
On Tue, 22 Dec 2020 at 23:10, Richik SC<EMAIL_ADDRESS>wrote:

@lnicola https://github.com/lnicola Hmm, the release seems to have both
binaries with the old naming scheme ("rust-analyzer-mac") and the new
naming scheme ("rust-analyzer-x86_64-apple-darwin") - are you building it
twice?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-analyzer/rust-analyzer/pull/6989#issuecomment-749753246,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANB3M2IR2EO7ECPLYA2X6DSWD4NFANCNFSM4VETS3JA
.

are you building it twice

No, it's just making a copy.

@lnicola Ok, I've ran the benchmark.
Here's the results (13" MacBook Pro, M1, Late 2020, 16GB RAM):
rust-analyzer-aarch64-apple-darwin (ARM Native)
% ./rust-analyzer-aarch64-apple-darwin analysis-stats .
Database loaded 641.27ms
Crates in this dir: 36
Total modules found: 572
Total declarations: 11043
Total functions: 8630
Item Collection: 7.37s
30/8630 100% processing: logger::flushTotal expressions: 236758                nExpressions of unknown type: 2669 (1%)
Expressions of partially unknown type: 2053 (0%)
Type mismatches: 857
Inference: 14.35s
Total: 21.72s

rust-analyzer-x86_64-apple-darwin (Rosetta 2)
% ./rust-analyzer-x86_64-apple-darwin analysis-stats .
Database loaded 913.53ms
Crates in this dir: 36
Total modules found: 572
Total declarations: 11043
Total functions: 8630
Item Collection: 11.22s
30/8630 100% processing: logger::flushTotal expressions: 236758                nExpressions of unknown type: 2669 (1%)
Expressions of partially unknown type: 2053 (0%)
Type mismatches: 857
Inference: 22.46s
Total: 33.68s

As you can see, a significant 35% reduction in analysis time just by being ARM native.
This is the second run of the x86_64 binary, as the first time, it just hung. I'm guessing it was because Rosetta 2 was performing AOT translation of it. It reported Database loaded 22s after killing it with ^C.

Then it works! Can you also use it with Code? You can set the server path in the settings.

Then it works! Can you also use it with Code? You can set the server path in the settings.

@lnicola Yep, works great on the arm64 native Insiders build of VSCode!


How Can Set RTL?

How Can Set RTL?

Hi,
you can reverse the array of options with reverse() method; if you expect the order of the buttons to change in RTL mode.


SPFx CommandSets and FieldCustomizer not working in new view UI

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

Browser Version: Edge 121.0.2277.112
SPFx version: 1.18.1
Node.js version v18.18.2

Describe the bug / error
A few hours ago, the views in one of our lists changed to the new Lists UI and all the CommandSets and FieldCustomizer that are registered on this list are gone.
Here is a screenshot:

Usually we have a few commands visible if one or multiple items are selected. Also some columns have FieldCustomizers registered to change the rendering, but they all show the default way. Looks like all the customizations are gone. Looks like ApplicationCustomizers are working.
Steps to reproduce

Add a SharePoint Framework app to a SharePoint website that has command sets registered on lists
Make sure the list already has the new experience with the views showing up as tabs (see the screenshot above). Our tenant is set to Target Release, but some views still show the old experience (which is working fine).
The command sets will not show in the new UI
The same happens for FieldExtensions

Expected behavior
CommandSets and FieldCustomizer should also show in the new UI.

@florianwachter - thank you for submitting the issue!
Unfortunately, I can't repro the issue - is it still happening for you?
Could you please a few things?

are you seeing any error in the console?
if you open Network tab in Dev Tools and refresh the page:

are you seeing request for https://res-1.cdn.office.net/files/sp-client/listview-host-assembly_en-us_<hash-code>.js?
if you open the aspx response and search for ClientSideComponentId - are you seeing your SPFx solution in there?

@AJIXuMuK - thanks for your assistance.
Please find my answers below:

No, I don't see any errors in the console related to this.
Yes, I see the request to the listview-host-assemly js and the entire URL is https://res-1.cdn.office.net/files/sp-client/listview-host-assembly_en-us_5061854e0c9eb8062748cd2905c95f86.js
Yes, I can see the commandSet componentIds in g_clientComponents and I can see the componentIds of the fieldcustomizers in window._spClientSideComponentIds.

I hope this helps. Please let me know if you need further details.
Thanks!

I have one more question regarding this issue. The message center entry MC709979 that announced this change mentiones that these improvements will NOT reach Lists that have been configured with SharePoint Framework extensions (see below).
"Users in affected tenants will see Lists feature updates as described in Microsoft Lists: Easier, Better, Faster, Stronger - Microsoft Community Hub when browsing to lists in SharePoint sites, the Lists progressive web app (PWA), and Lists in Teams. All Lists in SharePoint sites will maintain the SharePoint site's chrome, theming, and navigation. **These improvements will NOT reach Lists that have been configured with these features:
SharePoint Framework extensions**
PowerApps forms
Approvals
The Playlist template"
Does anyone know what this means exactly? Does it mean if there is a commandset configured for the list, or any field with a fieldcustomizer registered, the list will remain in the old UI. At least for now.
@AJIXuMuK : You mentioned that you cannot repro the issue. Does it mean that you see the old list experience or that you have the new experience with your custom actions, etc.?
Thanks!

The new experience should not appear if there are SPFx command sets or field customizers. And that is the behavior I'm observing.
I believe you are in touch with the owning team to solve the issue as it seems to be scoped to some unique situations.

@AJIXuMuK - Thanks for your answer!

I can confirm, that I've been seeing the "new" Lists UX in SharePoint Lists as well ... and also for Lists that have SPFx Extensions deployed that provide custom commandsets and other customizations.
These commandsets are not visible any more and the customizations don't work as expected either. For example: I have a solution, which is supposed to open a panel from the right (as the add-new-item action would do from the commandbar). This is now opening a new tab with my page, instead of a panel. Just as one example.
I would argue, that this is a bug we're seing. This new UI is not yet ready for sites with SPFx extensions, but somehow this is being applied to these sites as well.
Also: not everyone on our tenant is receiving this experience. I have this behaviour, a colleague new room still has the "old" UX.
BTW: yes, my tenant is first-release 😉

@henningeiben - I am in contact with an engineer from the Lists/SharePoint team who is looking into this and I'll keep you posted about the result.

@florianwachter please use this issue for the updates so the others could find the results too

Thank you for reporting! It looks like we have a bug specific to personal views. The workaround for now while we work on a fix would be to use a public view and not a personal view.
If that's not sufficient, please send me a message.

@natalieethell: I cannot confirm this. I also see this "new" list UX in public views!
At first I had the impression, that this UX would only show up when I'm accessing the allitems.aspx and I would still get the old UX when I'm accessing views by their aspx-pages (like archive.aspx). I figured when I'm accessing the archive-view (a public view an a list) using allitems.aspx?viewid=[id of the archive-view] this would trigger the new UX, while just archive.aspx would still show the old UX.
But that was on Wednesday. Since yesterday I'm getting the new UX on most lists/views (however - not on all of them!).
To make it even more confusing (if that is possible): today I get for some (public) views again the old UX, where I got Tuesday and Wednesday the new UX. 🤯

@florianwachter please use this issue for the updates so the others could find the results too

I'm pretty sure it's not the job of your customers to let others know about your product's ongoing issue status. I know your answer will be that some other team @ Microsoft caused this issue so don't bother.

Huge thanks everyone for your input on this. We do apologize the delay here and are currently actively looking on solving this issue.
We are also curious on understanding how widely this issue is visible worldwide, so if this is an active issue for you, please add a comment with small description, so that we can see the impact.
At the same time we are now actively working on solving this internally.

I can confirm that this is an issue still at least for command sets. If it's not supposed to be enabled if a command set/field customizer is present that is not happening in all cases, further, is it the intent that if you want to add a field customizer or command set later that it would revert? I have found that I'm able to fall back to "Standard Release" wait for the UI to switch back, add the field customizer... then if I switch back to "Targeted release for everyone" the command set doesn't show up but the console shows that it was loaded.
Standard Release

Targeted Release

I have the same problem here with a command set extension that is targeting multiple list (using RegistrationId in elements.xml and ListTemplateId in ClientSideInstance.xml).
It looks like some lists created earlier stays in the "classic modern experience" and the command set extension is active, but if I create a new list it shows in the "Microsoft lists modern experience" and the command set is not loaded (the strings files from the solution is loaded, but not the script files).
I hope this can be resolved quickly because I have many customers relying on this command set extension to use my Modern DFFS solution.
Alexander

@SPJS @juliemturner I've made a configuration change that should take effect in the next 15-30 minutes which should put you back in the state of loading "classic modern" (as Alexander puts it) when SPFX command sets are present.  If you're still seeing the problem in an hour from now, please let me know.
One of us will also reach out to you later to get more details on your scenario so we can figure out why your scenarios were not working in the "new modern".

@reedpamsft - It appears to me that it's already taken affect for my dev tenant. After a few (empty cache and hard refresh) browser refreshes, in targeted release for everyone, the site collection with the list command set now is showing the lists in the old style and the command sets work whereas a site collection without any customizations has lists that show with the new list experience.

@juliemturner thanks for confirming!

@reedpamsft - I can confirm that it works now - the lists in the site collection where the command set it active (installed in a site collection app catalog) shows in the "classic modern style" and the command set extension is loaded as expected.
Thanks for the quick turnaround!
Alexander

And looking forward, SPFx will be supported in the new modern as well, right? Or is this a slow walkback on some types of customizations?

@heinrich-ulbricht "new modern" currently supports App-level SPFX customizers, and we are working on supporting command set customizers right now (a bug in that work is what caused this recent issue).

Is there an update on the issue? Recently some of our customers reported this issue in personal views. Command sets and field customizers are suddenlty gone.

Any news on this? More and more customers are reporting that they can see the new views and all the command sets and field customizers are gone.

@florianwachter do you have more details?  Is this something you're able to reproduce yourself, or could you help us get in touch with someone who is seeing the issue?  I ask because in our testing, views are falling back to the existing UI as expected when command set customizers are present.

Hi @Thomas-Fir , thanks for the details!  Unfortunately, it seems that github no longer allows private messages, so we'll have to get a little creative in gathering your feedback.
Can you go to a view that is showing the issue and use the "Provide feedback to Microsoft" -> "Report a problem" button in the top right corner to tell me a bit more about the details?  That should help me identify why the code decided to show the new UI despite the presence of command set customizers.  If you could include a screenshot and your email, that would be very helpful!  Please make sure to mention my github username in the "What went wrong?" box so I can find it.

@florianwachter do you have more details? Is this something you're able to reproduce yourself, or could you help us get in touch with someone who is seeing the issue? I ask because in our testing, views are falling back to the existing UI as expected when command set customizers are present.

@reedpamsft
Yes, I can reproduce it. These are the steps:

Create a personal view in alist where command sets are registered
Open any public view -> the command sets are visible
Use the view selector to switch to the personal view -> the command sets are visible
Reload the current page in the browser or copy the URL to a new tab -> the new list UX is visible and the command sets are no longer visible

If you are unable to reproduce it following the steps above, please let me know and I'll share a screen recording.

Thanks @florianwachter !  I am not able to reproduce the issue with those steps, so a screen recording would be very helpful!  In order for us to have a look at our logs, it would also be great to get the list URL and an exact date/time/time zone when you reproduced the issue.

@reedpamsft
Here is a screen recording showing the issue. This time I had to create two personal view to reproduce the issue.
https://github.com/SharePoint/sp-dev-docs/assets/5690610/7bf74b53-5fef-464c-a496-67894d1f8399

Hi @reedpamsft,
I was able to reproduce the same behavior as shown by @florianwachter after refreshing page.

Thanks @florianwachter  and @aaclage  , I am able to reproduce the issue consistently now with the additional detail of "multiple personal views".

I experience the same behavior as @florianwachter regarding the new UX view on personal-views when these are called directly via the URL.
Also: when I then switch to a public view using the view selector, I'll stay on the new UX view and of course the custom commands are not available.
In addition: I have custom-forms registered in my list, and in the "old modern view" this form would be loaded for displaying an item. In the "new UX view" these forms are ignored when there is no custom commandbar entry. When a custom commandbarentry exists the custom form will be loaded (even in the "new UX view").

As an FYI, I've fixed the issue with multiple personal views and it will be rolling out soon.  In tandem, we're finishing up support in the new UI for command customizers, which might or might not arrive before the fix to properly detect command set customizers when making the decision which version of the UI to use.
Anyway, @henningeiben , do you have a few more details on this form issue you're seeing?  What kind of custom form?  Which specific command are you using in the new UI that's acting differently from the old one?

It's unclear for me if the fix should also restore field customizer from teams files tab. Can we expect this to work?

@stevebeauge the Files tab is totally unrelated to any of this.  We're not currently pushing any new UI framework for the files tab.  Let me check around about that, though.

@reedpamsft: Thanks for the update about the fix. You also mentioned that your team is finishing up support in the new UI for command customizers. Can you please confirm that field customizers will also work in the new UI/UX and can you please tell me if there is a way to test the new functionalities before it's rolled out globally to target release tenants? Is there some kind of program where we can get early access to new feature.
Thanks, Florian

@reedpamsft ; how about Form Customizer extensions? As of last week we're seeing this same issue with a list that has a Form Customizer extension active; in the previous UI, a click on the Title field would redirect to the custom form page as expected, but after the list switched to the new Lists UI, it shows the popup window instead.
I've managed to work around this limitation for now by adding a JSON formatter on the column that adds a link to the custom form with the item ID, but until they're supported in the Lists experience I'd expect form customizer extensions to be among the criteria that stop a list from getting the new UI.

I am a developer and made spfx buttons (command sets) in the list navigation. We have created multiple sites with these buttons that are all the same. Yesterday for one user and for a couple of the sites, not all, the look and feel will switch to the new one and it will not load our custom buttons. The user did change the view but not yesterday, weeks before. The user did not have personal views on that list. After testing out a couple of things, like removing all the fields in a new view and creating new views I noticed that it suddenly jumped back.
and that was after ?sw=bypass&bypassReason=abandoned was put after the .aspx. It reloads the page into the old look and feel.
So I would like to pitch in and say that we also experience this problem for one user but for now we have a temporary solution but I hope this will not be an issue for more of our users.
How is the rollout going of the support for command sets in the new UI? @reedpamsft

Strange, I stopped getting notifications about this thread...
Anyway, @florianwachter , we don't have a current timeline for field customizers.
@oppie85 we recently added a fix for the scenario you mentioned.  It should be available to all users by next Wednesday (July 17).
@JonEOffice command sets should now work in the new UI, so that's surprising!  Can you share more details about your customizer?  Is there a way I can test with it?

@reedpamsft the solution is from last year I think it is running these versions
"tslib": "2.3.1",
"@microsoft/sp-core-library": "1.15.2",
"@microsoft/decorators": "1.15.2",
"@microsoft/sp-listview-extensibility": "1.15.2",
"@microsoft/sp-dialog": "1.15.2"
I can share it, but it depends on certain lists and security groups to be there in the site, this takes setting up before you can get it to work.
For me and other users the list is still being pushed back to the old modern look, so if you say it works at this time, that means that for us this change is not implemented yet, but for this one user it is?
In the console log of this user it seems like the entire extension is not being loaded since we have things we write in the console log when it is being loaded.

Thanks @JonEOffice !  If you could share it, that would be great.  The original genesis of this thread was a point at which we had thought we had tested all applicable scenarios for command set customizers, but a class of them weren't working, so there's a possibility that something in your customizer puts it in a new class we haven't fully explored.

@reedpamsft https://duwboot-my.sharepoint.com/:u:/g/personal/jon_van_rij_e-office_com/EZhIssmx5ixNgWXi0UoxkfIBOg-TtROHAkMhg5HiIFepVg?e=kd9959
Pass RejectGithub1
let me know when you have it

@JonEOffice got it, thanks!!

@JonEOffice thanks for sharing! I'm an engineer on @reedpamsft 's team. Taking a look at the code you shared, it looks like there's an incomplete if/else in updateListItem.

Is this the most up-to-date code?

@natalieethell I gave you guys a version of the script where I removed and changed a few lines that contained customer information. So this is the most up to date code that is deployed. but a few lines are different where I didn't think would stop this script from deploying. for instance the indexof contains the tenant name

Other thing that is changed is in the serve.json. Fill in your own URLs there.

We are experiencing this issue as well. As of yesterday, we got the new UI and now our custom functionality (CommandSet) isn't working. Is there a way to revert the UI until this is fixed (since I don't have the know-how to troubleshoot this and the ones that do, are on vacation)? @natalieethell @reedpamsft

We are experiencing this issue as well. As of yesterday, we got the new UI and now our custom functionality (CommandSet) isn't working. Is there a way to revert the UI until this is fixed (since I don't have the know-how to troubleshoot this and the ones that do, are on vacation)? @natalieethell @reedpamsft

@MissHerku as I stated in the reply above. Put this behind the .aspfx ?sw=bypass&bypassReason=abandoned
Like so https://tenantname.sharepoint.com/sites/sitename/listname/viewname.aspx?sw=bypass&bypassReason=abandoned

@JonEOffice unfortunately adding that didn't do anything for me. It just removes it from the url (I tried in Safari and Edge, on PC and Macbook). Is it supposed to return to the old UI?

@MissHerku For when I tested it with the user, it reloads the page, removing the extension (?sw=bypass&bypassReason=abandoned) and displaying the list in the old look and feel. I got this extension after testing it out with adding new views for this user and removing the views, suddenly it displayed the old look and feel and I saw this in the URL.
Because one of the cases futher up this thread was in regards with personal views being a problem, so I checked that.
Do you have it for all users and for all lists? For my user it became active this monday (8th july). But not for other users.

@JonEOffice I've tried just about anything. Over the last months I have seen the new UI for only a handfull of users in all of my Customer's domains, so it's been clear that they have been testing the new features with a soft launch (which honestly has been a communicative nightmare). But now it seems as if they have made a larger enrollment, since all of my customers now have the new UI.
Perhaps that means that you can no longer bypass it in the url, like you mention? I have tried adding the bypass url to public views, personal views, on the url of the view itself as well as the url with a view GUID. I have created new views and tested old ones. Nothing seems to work and I have testet on 3 different domains now.
However back to the issue of CommandSets not working with the new layout, @reedpamsft seemed to think that these should be working by now, so I am very interested in getting some sort of status on the matter from Microsoft

Are there any updates on this issue? I work a for an ISV that uses SPFx list view command sets extensively and customers are reporting that our extensions do not work in this experience. Do we have to create our SPFx package with a particular version of SPFx? Are there any workarounds? Does anyone have any idea when this issue will be taken care of?
This is a little troublesome that Microsoft would soft launch features that don't fully support SPFx

@JonEOffice we are taking a look at your customizers to see what could be going wrong, thank you!
@MissHerku @vieirak79 would you be able to share your customizers? That would be super helpful to debug the specific issue and get this figured out.

@natalieethell The timing is really unfortunate, since our developer(s) are on vacation. Until they're back and we can share more details, is there really no way to exclude a domain/site/list from getting the new layout?
For the last two days we had the new layout. This morning, the old one was back on and our functionality was working again. Now a few hours later (and after I sent out news about our solution working again) the new layout is back on. It's really difficult to communicate anything of value to my end users, when the layout changes by the hour.

@natalieethell You can use the default "helloworld" command set extension created by the SPFx framework or use this example:
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api
I used the latest version of SPFx to create the example extension. If the list doesn't switch to the "new modern view UI", the command set functions as expected. Once the the list switches to the new modern view UI, the command set extension JavaScript files are loaded, but the constructor and onInit events for the command set are never called.

@MissHerku @vieirak79 @JonEOffice  as a note, we've identified at least one bug that could be causing this class of issues, and as a result have suspended the new UI for lists with command customizers.  You should see the old UI in any case where command customizers are present again, but note that there is a lot of caching layers between us setting that and users getting the experience.  Refreshing the browser a few times, or doing a "hard refresh" with ctrl + f5 should clear out those caches and give affected users the old UI back until we've solved this set of bugs.

@reedpamsft that's great to hear and I do look forward to getting the new layout, once it works as expected.
So perhaps the re-enrollment of the new layout, we saw momentarily today, was merely a caching issue(?) Makes sense!

@vieirak79 We've tested out basic command set extensions like the "helloworld" one, and that is rendering as expected in the Modern experience, so I'm surprised to hear that some methods aren't being called in your extension. Could you provide some of the differences between the sample "helloworld" extension and yours?

@natalieethell list view command sets work fine in the standard/original modern experience. When the list renders in the "new modern view UI", no command set extensions work.
For example, when the lists renders like this, there are no extensions loaded.

If list view renders in the "standard/original" modern experience, the extensions are loaded.

This happens for any extension, including the hello world example. I even tried re-deploying the hello world example extension and these are the results.
Original standard/modern view:
No items selected:

One item selected:

In the new UI, the extensions never appear.

And I never know which experience will be the one displayed to the user. The new experience appears at random. All these screenshots are from the same list. I just repeatedly refresh the page until I the modern experience I want to take screenshots of is rendered.

@vieirak79 Sorry, by "Modern", I meant the new UI experience that you're talking about. Since we suspended the new UI, as Reed mentioned there are a lot of caching layers between us setting that and users getting the experience. Does a "hard refresh" with ctrl + f5 to clear out those caches work for you?

@natalieethell we have investigated this further, and found out the culprit is the service worker.
Affected users (not everyone is affected by this) will get the following console error messages when the extension does not load:
Refused to get unsafe header "SPClientServiceRequestDuration"
Refused to get unsafe header "SPRequestGuid"
Refused to get unsafe header "SPRequestGuid"
Refused to get unsafe header "X-SERVICEWORKER-DATA-SOURCE"

This seems to have been reported and resolved in the past, over a year ago, and now is coming back for some users.
We have tried to unregister the service worker, it does install itself as expected with the same version as on other unaffected users. We also cleared all browser cache, including all cache storage but the affected users can consistently reproduce it now.
Hope this helps, we are happy to help diagnose this if needed.

@natalieethell Clearing out the cache will work temporarily. As @shaipetel stated, for some users on some sites the command sets are not loaded (the oninit is never called and the buttons do not render in the command bar). Again, we tested this with our custom list view command sets and the "HelloWorld" example directly from Microsoft.
Here is the what happens on a completely cached site:

These are the errors that @shaipetel mentioned

Now, if I completely clear the cache and do a hard reload, everything works fine:

Soon as I perform a standard refresh, the command set buttons disappear.
The other thing I'd like to mention is that if the service worker fails with this error:

Everything works fine.
It is almost as if on a hard reload the service work fails and the command sets load normally, but on subsequent refreshes (where everything is cached), the service worker doesn't fail, and the command sets don't load.

Any updates on this issue? The fact that list view command sets don't load in the new experience, and don't load on some lists in the previous modern experience is concerning. This is going to start impacting more and more customers.

I see the same behavior where the commandset is sometimes not loaded in the "old modern UI", and if I then refresh the page using F5 the "new modern UI" is loaded. The command set extension is not loaded there either.
Subsequent refreshes keeps loading the "new modern UI" until I do a hard refresh using Ctrl + Shift + r.
I also see this in the console (as noted by others earlier):
plt.odsp-common.js:138 Refused to get unsafe header "X-SERVICEWORKER-DATA-SOURCE"
plt.odsp-common.js:138 Refused to get unsafe header "X-ServiceWorkerFetchInfo"
plt.odsp-common.js:138 Refused to get unsafe header "SPSQLQueryCount"
plt.odsp-common.js:138 Refused to get unsafe header "X-SERVICEWORKER-DATA-SOURCE"

It looks like lists created a while back in the same site is still rendered using the "old modern UI" with the commandset, but there is a short flash of the "new modern UI" before it reverts back to the "old modern UI".
Please fix!
Alexander

Hey @SPJS so far we were able to learn a bit more about the cause and how to bypass it in the meanwhile while waiting for a fix.
I've discussed possible cause and workarounds here
Options 2 or 3 would work for you: either taking the list off the sync, or disabling Microsoft List Sync on your computer.
Hopefully this gets resolved soon.

@shaipetel  - Thanks! - disabling list sync in Microsoft Lists seems to have fixed the issue where it loaded in the "new modern UI" with no commandset buttons.
Alexander

Sorry, by "Modern", I meant the new UI experience that you're talking about. Since we suspended the new UI, as @reedpamsft mentioned there are a lot of caching layers between us setting that and users getting the experience. Does a "hard refresh" with ctrl + f5 to clear out those caches work for you?

Hi @natalieethell - Some additional feedback: Ever since MS fixed the issue with the "new Modern" UI, causing the new Modern UI not to appear when there are CommandSets present on the list, that has been working well for us. That is, our customers are seeing the "old modern" UI, with our CommandSets as well as your new Forms button - which is fine. But just within the past couple of weeks, we have received some reports of our CommandSets not being displayed on the "old modern" UI. Ctrl-F5 does indeed clear the caches and make them appear, at least for that session. But it's a nuisance because it doesn't seem to happen all the time, and is causing quite a few support tickets as people have gotten used to it working well until recently.

@SandyLT Yes, sorry about that. Disabling "Sync" on your affected lists should fix that issue as well. You can do this by going to the Microsoft Lists app, opening the "..." menu of an affected list, and selecting "Stop syncing".

The Sync team is working on a fix for this bug, thanks for your patience!

If the above doesn't work, a second option would be, as Shai mentioned, to disable Sync on your device.

Is there a similar workaround for Document Libraries (not Lists) to prevent loading the "new Modern" UI where command set customizers (SPFx list view commands) are in place? - except disabling offline sync approach...
Disabling "Offline Client Availability" sync isn't an option for our clients/users on libraries since obviously the business relevant OneDrive's Sync to Explorer stops working in that setting.

So OneDrive's Sync to Explorer is different than the Sync in Lists. Document Libraries will not see this new Modern UI yet, but once they do, this issue should not impact them.

So glad I have found this thread, have had a similar issue for a while now and it has been driving me mad. I have noticed similar behaviour when simply filtering by a Managed Metadata (MMD) column (both with a formatted list view and a non-formatted list view).
When the list is being synced offline filtering on a MMD column by the tag display name does not work and results are only returned when the guid of the tag is included (i.e. Italy|46b134fa-4dac-41b1-8822-cd89c3cb06f4). When syncing is disabled as advised above the list filters as expected, using just the tag display name.
Very frustrating bug but glad the workaround of disabling the offline sync seems to sort it for now. Looking forward to hopefully soon getting a fix from the Sync team 👍

Hey @SharePointJim , thanks for reporting the issue.  That sounds completely different from what's being discussed, so I'll pass it along to the sync team as a new issue.

When we place a list component on the modern page and disable "Offline Client Availability", the list is displayed in the new modern UI.
After a couple of days, the second issue occurs: only Init() is executed and when I select an item or multiple items, then onListViewUpdated(event: IListViewCommandSetListViewUpdatedParameters) is not fired for a custom commandset when the list component is on the modern page.
I checked on tenants with early releases enabled.
Has anyone experienced the same issue?

We have the same problem related to this issue.
We have a command set for document libraries. If library uses "New Modern UI", the command set isn't loaded at all. We've tried disabling "Offline Client Availability", but seems it doesn't work for document libraries. Currently, the problem hit one customer, but looks like it will grow.
Are there any additional info about this problem? I'ts the end of August and seems people struggle with it for a few months already.

We are experiencing the exact same as @s-KaiNet currently and also hoping for some good news as consistent Command Sets are vital for our business.

@yur-st @s-KaiNet @MortenGuldbaek Thanks for reporting. We've identified the issue specific to the document libraries webpart and have reverted to the "old" UI. You should be seeing your SPFx command customizers in your document libraries webparts again in the "old" UI.
We are ensuring that the SPFx command customizers issue in the webpart is fixed before we push the "modern" UI again.

Hey folks - this thread is getting too long and reference a few different issues, although all of them are related to new UI for lists and document libraries.
To summarize, there is still an issue with offline mode for the lists.
And here is the workaround for it: https://github.com/SharePoint/sp-dev-docs/issues/9514#issuecomment-2285006188
For web part you should see "old" UI being enabled.
The team is ensuring that the new UI will not break SPFx extensions when enabled.
I will close this one as it's getting hard to track.
Please, create new issues and reference this one if needed.
Also, provide information like:

type of extension
document library or list
full page or web part

I would also encourage you to name the issue with SPFx in lists (same as label for this issue) to be able to triage it faster
The team will be monitoring new items in the repo while rolling out the new experience.
Thanks!

Thanks @natalieethell for the fast response and the fix. I can confirm, that on two of our tenants, where we previously observed the issue, now document library web parts use "old UI" and all command sets work as expected.

The team will be monitoring new items in the repo while rolling out the new experience.

Why weren't you doing that to begin with?

Why is this issue closed?

@silentmark -- please read the comment above https://github.com/SharePoint/sp-dev-docs/issues/9514#issuecomment-2318550547

Why is this issue closed?

Because it is getting "hard to track" the mess they made.

I just discovered that command sets are still functional in the new UI! The only thing that has changed is the handling of event.selectedRows. To make your code work again, simply replace it with this.context.listView.selectedRows.

@BlazeOfFeathers : Thank you very much, confirming it`s working. Solving the issue reported here: https://github.com/SharePoint/sp-dev-docs/issues/9898#issuecomment-2328801335

@BlazeOfFeathers Thanks very much! This solution is working for me!

I just discovered that command sets are still functional in the new UI! The only thing that has changed is the handling of event.selectedRows. To make your code work again, simply replace it with this.context.listView.selectedRows.

What version of SPFx do I need to use for that workaround ? Version 1.12.1 gives me "Property 'selectedRows' does not exist on type 'ListViewAccessor'" error.

I'm also surprised and confused, why close this issue if the fix for the original issue is still not resolved... It is even harder to track if you close this one and asking people to report the same issue in duplicates, so I'm not sure what's the point?

As of this morning, we have reverted to the previous UI in our tenant, without any info from MS.

does anyone know (@BlazeOfFeathers) if this.context.listView.selectedRows is just a workaround or is this the expected way to access this information in the future? Is there any official notice on this "change"?

@henningeiben  - no official statement has been made about that change, until it is I would consider it a hack to get things working and would either wait or inform my clients that making that change could break at any time. That said, per @adriangoszczynski comment I would suggest that the amount of noise that is being made is helping raise visibility and they have decided to revert changes so that things can be better handled. At least I hope that will be the case. Again, sadly, nothing official.

@juliemturner: in the meantime I addressed this also in issue #9896 - maybe this helps as well

+1000 to what @juliemturner said... the way Microsoft is handling this issue leaves A LOT TO BE DESIRED.
If you encounter this issue, there's no one place that says what the issue is or what the resolution or current status is. The fact it was closed & marked as completed by @AJIXuMuK makes it seem like the issue has been resolved when it clearly hasn't.
As @shaipetel said in his comment, the approach of creating fragmenting this to multiple issues is making it even harder to follow.
Sure seems to me the new List UX wasn't ready to ship because it didn't account for SPFx customizations, breaking established practices. Regardless if it's one issue or 50 issues, it's one feature that's getting reverted & seems like one issue should be used to track it.
Hoping Microsoft makes an official statement either here in the issue list, or in the docs... but it's something we can point customers to, because it sure isn't being well received by customers.
Dear @VesaJuvonen ... #help

@andrewconnell  the other thread was closed because the specific bugs it was discussing had been fixed and confirmed as fixed by the folks who reported the issue.

@reedpamsft is there a place you would like us to submit bugs with the new lists experience that aren't related to SharePoint Framework?

@reedpamsft said:

@andrewconnell the other thread was closed because the specific bugs it was discussing had been fixed and confirmed as fixed by the folks who reported the issue.

Which "other thread" are you referring to? The issues linked in this one are all open... sorry, just asking for a single link we can share with customers who are still confused who want to hear it from Microsoft.

@juliemturner maybe create a new thread and at-mention me?  Github seems to have removed the ability to send private messages.

@andrewconnell I'm referring to the thread that Florian had created and which was marked as closed.  I understand that having multiple threads can be confusing in some ways, but having a single thread where different issues are piled on makes it difficult to differentiate which are still active and which are resolved.

@reedpamsft  seems like MSFT are now dropping updates directly to production, targeted release no longer getting a heads up with the new new new list experience...
I just reported an issue that started happening last Friday and tagged you, and this release also broke many of our forms based solutions due to now opening forms in a dialog.
Is MSFT not following the targeted release anymore? is there another way for us to be able to taste/test the drops before they hit production?


lm_info target 'device' omits devices in SDT

SUMMARY
Devices in SDT (maintenance) are not listed in the output of module lm_info, target 'device'.
ISSUE TYPE

Bug Report

COMPONENT NAME
module logicmonitor.integration.lm_info
ANSIBLE VERSION

ansible 2.9.27
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/lm/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/lm/PycharmProjects/lm_experiments/venv/lib/python3.10/site-packages/ansible
  executable location = /home/lm/PycharmProjects/lm_experiments/venv/bin/ansible
  python version = 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0]

COLLECTION VERSION

Installing 'logicmonitor.integration:1.3.0'  (list option does not exist in this version of ansible-galaxy)

CONFIGURATION

DEFAULT_BECOME(/etc/ansible/ansible.cfg) = True
DEFAULT_BECOME_METHOD(/etc/ansible/ansible.cfg) = sudo
DEFAULT_BECOME_USER(/etc/ansible/ansible.cfg) = root
DEFAULT_CALLBACK_PLUGIN_PATH(/etc/ansible/ansible.cfg) = ['/etc/ansible/plugins/callback', '/home/****/.ansible/plugins/callback', '/usr/share/ansible/plugins/callback']
DEFAULT_EXECUTABLE(/etc/ansible/ansible.cfg) = /bin/bash
DEFAULT_GATHERING(/etc/ansible/ansible.cfg) = explicit
DEFAULT_HOST_LIST(/etc/ansible/ansible.cfg) = ['/etc/ansible/****']
DEFAULT_REMOTE_USER(/etc/ansible/ansible.cfg) = ansible
DEFAULT_STDOUT_CALLBACK(/etc/ansible/ansible.cfg) = ****
DEFAULT_VAULT_PASSWORD_FILE(/etc/ansible/ansible.cfg) = /etc/ansible/****
DISPLAY_SKIPPED_HOSTS(/etc/ansible/ansible.cfg) = False
TAGS_SKIP(/etc/ansible/ansible.cfg) = ['*****']

OS / ENVIRONMENT

$ cat /etc/os-release
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
STEPS TO REPRODUCE

Run a playbook with the two tasks specified below. No errors happen.

    - name: Look up all devices
      lm_info:
        company: "{{ lm_company }}"
        access_id: "{{ lm_id }}"
        access_key: "{{ lm_key }}"
        target: device
      register: all_devices

    - name: "Dump info into /tmp/lm_devices.yml"
      copy:
        content: "{{ all_devices | to_nice_yaml }}"
        dest: /tmp/lm_devices.yml

EXPECTED RESULTS

A list of all devices, including those currently in SDT.
ACTUAL RESULTS

A list of devices, without those currently in SDT.

@JG127 please submit any bug or feature request to LogicMonitor support
https://support.logicmonitor.com/hc/en-us/requests/new


Prevent empty tags; duplicate tags cause error

Just testing tag management behaviour... a couple of simple issues:
1.
Creating or editing with ", " at the end generates a false empty category that doesn't link back to the post.
2.
setting the categories as this:
"foo,bar, ,   "
gives "something went wrong on the server" and this in the log:
Error <IP_ADDRESS> cloudscribe.SimpleContent.Web.Controllers.BlogController /Blog/AjaxPost
ajax post failed with exception The instance of entity type 'PostCategory' cannot be tracked because another instance of this type with the same key is already being tracked. When adding new entities, for most key types a unique temporary key value will be created if no key is set (i.e. if the key property is assigned the default value for its type). If you are explicitly setting key values for new entities, ensure they do not collide with existing entities or temporary values generated for other new entities. When attaching existing entities, ensure that only one entity instance with a given key value is attached to the context.
This gives a similar error:
"foo,bar, Foo ,"
So does this
"foo,bar, Foo"
( I think this just require de-duplicating the list).

thanks as always for the bug report! this is fixed now


get/set_named_weights and save/load_weights support for more meaningful weights objects in Graphs

I was dissatisfied with the way Graph serialized weights to an opaque, flat format when getting/saving, since it made transferring weights between different achitectures a pain. Motiviated by this use case, I have:

added get_named_weights and set_named_weights to containers.Graph
this returns the weights in a dictionary structure with keys the same as node names
it recurses into subgraphs to produce nested dictionaries
when encountering a Layer/container not supporting get_named_weights, it calls that object's plain get_weights method
set_named_weights takes such a dictionary and inverts the process
added the boolean named kwarg to graph.save_weights, which produces hdf5 files using the graph's node names as keys and reproducing any hierarchical structure. It sets an attr on the file, so that load_weights can handle these transparently.
added fairly comprehensive tests.

There was a killer typo in the tests which made me miss a slew of errors: working on it.

I was dissatisfied with the way Graph serialized weights to an opaque, flat format when getting/saving, since it made transferring weights between different achitectures a pain

I never had any issues with transferring weights. The canonical way to do this is to load your weights into the previous Keras model (you don't need to compile it, so it's instant) and use that model as a query-able datastructure to access the weights. The deep dream example scripts show how to do it.
Would your changes break weight loading/saving recursivity (with nested containers)? Are you aware that layer name unicity is not globally enforced?

These methods were written with recursive containers in mind and should work correctly, assuming that the original get/set_weights methods do. I have tested them with nested Graphs.
Similarly, they are compatible with non-unique layer names between nested structures, since the nesting structure itself provides a natural disambiguation, and is carried forward in the resulting weights dictionary.
These changes do not tamper with the existing get/set_weights code

I was not aware of the deep_dreams example, but I believe that my code provides a more intuitive and user-friendly weights object, as well as better-structured hdf5 files, than the current implementation for Graph: in contrast with Sequential, which provides a natural segmentation into layer_{} and param_{}, Graph currently compresses all of the weights in the model into a flat list of param_{}s. I felt it's very natural that instead it should carry forward the named-node tree structure in weight representation.

Definitely interested in merging this, thanks for working on it. Mostly I think:

let's not add more weight setting / getting methods beyond the existing ones. Can we just extend the existing methods?
can we unify the weight formats for Sequential and Graph?

Let's come up with a unified, tree-based, name-based (where non-unique names from a single container are postfixed with an index) weight file format for Keras, for both Sequential and Graph models. Support for previous will of course continue, but I believe we can afford to redesign something from scratch then route the parsing of the files to a different function based on the presence/absence of a file format version indicator in the file.

(To start, I will mention here in passing my idea in #1764 to subsume Sequential into Graph, which would allow conceptual and development work - with named weights code, and other code in the future - to concern itself only with Graph)
My dominant intuition is that weight objects should be as transparent, interoperable and future-proof as possible. I feel this is especially important in light of pushing to make Keras a more "ready-to-use solution for applied machine learning", where users might be concerned with data traceability and long-term interpretability. Some ideas to this end:

writing more information to hdf5 attrs is desirable, such as:
Keras version information
layer type in Group nodes
basic container information in file-level attrs
parameter name (W, b, etc.)
depending on feasibility, interlayer-connectivity information
Sequential should be treated like a Graph with a linear node structure, with some generic name for nodes like layer_{} (this is similar to how it is already implemented). Perhaps being able to optionally name Sequential layers could be an ancillary addition (once more reminiscent of #1764).

Keras version information

Sure. And weight format version.

layer type in Group nodes

Sure

basic container information in file-level attrs

Note sure what you mean by that.

parameter name (W, b, etc.)

This is useful but won't be easy to achieve. It would require layer-level modifications.

depending on feasibility, interlayer-connectivity information

I don't think that's feasible.
What we can do for Sequential:

more file-level info: version numbers
more info in groups: layer type
group (layer) names match layer names, with a prefix that allows alphanumeric sorting. Typically, I'm thinking of "01:my_layer_name". The number of leading zeros would be determined by the number of layers in the container.

parameter name (W, b, etc.)

This is useful but won't be easy to achieve. It would require layer-level modifications.

As an intermediate step, we should start modifying layers so that the underlying weight tensors have a name (in TF space or Theano space). I wonder if name unicity will turn out to be an issue.

Rather than layer types, wouldn't it make sense to just store model.to_json() output as part of the hdf5 file? It should be pretty tiny compared to the parameters, right? And it'd allow working with easily redistributable, self-contained, single-file models, it could be pretty convenient.

wouldn't it make sense to just store model.to_json() output as part of the hdf5 file? It should be pretty tiny compared to the parameters, right? And it'd allow working with easily redistributable, self-contained, single-file models, it could be pretty convenient.

I second this...

Obsolete PR, closing.


Update README.md

Changed the yaml code from tibber_custom to tibber_data since this is the new name.

This is Tibber data
https://github.com/Danielhiversen/home_assistant_tibber_data


[FEATURE] Unix binaries that can be used to bypass local security restrictions in misconfigured systems like GTFO Bins, {branch: dev}.

Detailed description
We can add Unix binaries like
Context
This change will be very helpful for pentesters
Possible implementation
No response
Additional information
No response
Code of Conduct

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

[ ] give data files more informative names
[ ] check if there are some improvements to do in design or leave as it is.


Split responsibilities to Mode, Method, activate() and activate_using() (v. 0.8.0)

This is basically a ticket to myself, and is continuation of work in the PR #51, which left the main branch in an unfinished and bit messy state.
Tasks
Modes

[x] Clean up code for Mode. The purpose of Mode is to simply provide the main API and context manager for the user. Everything else should be handled elsewhere. (PR #70)
[x] Remove creation of DBusAdapter instances from Modes. Pass the DBusAdapter class to a ModeActivationManager -> ModeActivator -> Caller and create an instance of the adapter there (in separate thread)   (PR #70)
[x] Remove prioritization of methods from Modes. Prioritization should be done in ModeActivator.  (PR #70)
[x] Implement Mode.__exit__ and add ModeExit exception which can be used to exit the mode with statement block.  (PR #72)
[x] The callables for Modes like keep.running and keep.presenting should be functions which return instances of Modes. Calling keep.running() should call return a fresh instance of Mode (for supporting running wakepy in multiple threads) (PR #71)
[x] Create tests for Mode  (PR #71)

ModeActivationManager

[x] Create a ModeActivationManager class. (PR #76)

This is running in the main thread, and an instance of it is accessible at `mode.manager'.
Purpose of ModeActivationManager is to manage activation of modes.
It creates a separate thread for the activation process, two queues, and communicates with the ModeActivatorProcess using the queues.
It returns an ActivationResult from some .activate() call.

[ ] Update ModeActivationManager (this task needs some refinement)

ModeActivatorProcess

[ ] ModeActivatorProcess: Replaces the current ModeWorkerThread. Runs in a separate thread and communicates with ModeActivationManager using queues. Is split in method selection, method prioritization and mode activation. Uses a Caller to process different types of Calls, like DBusMethodCall, ExecutableCall, PythonCall, SharedLibraryCall.
[ ] ModeSelector class
[ ] Prioritization of methods in ModePrioritizer
[ ] Activation of mode in ModeActivator
[ ] DBusAdapters in ModeActivator (get a default one if user did not provide one)

ActivationResult

[ ] Update ActivationResult to have reference to the ModeActivationManager (self.manager).

Talks only to manager directly.
Contains only results from mode activation.
Has list of active methods, etc, but all(?) lists of methods are simply stings, not instances of Methods. The Method instances live only in the ModeActivator, in separate thread.

I wrote some initial ideas in https://github.com/fohrloop/wakepy/issues/75 about renaming ModeActivator to ModeActivationProcess and splitting the responsibilities in three: MethodSelector, MethodPrioritizer and ModeActivator.
I could try to implement the classes next. Modifying the list above to reflect the changes.

As mentioned in https://github.com/fohrloop/wakepy/discussions/100, wakepy Mode activation process will be a blocking operation. This makes it possible to do everything, except heartbeat, in the main thread, which in turn makes things a lot easier. I've already written some documentation to the 0.8.0dev ("main") docs about how this all will work. The plan is roughly:

Have Mode class as the context manager
Have activate(methods, ...) function which can activate a "mode" (list of method classes)
Have activate_using(method, ...) function which may activate a "mode" using a single Method.
Have Method class for sole purpose of defining subclasses Method
Have a Heartbeat class which runs a heartbeat in separate thread.

Rough implementation of activate():
def activate(methods: list[MethodCls], ...) -> tuple[ActivationResult, HeartBeat|None]:
    prioritized_methods = prioritize_methods(methods)
    result = ActivationResult()

    for method in prioritized_methods:
        methodresult, heartbeat = activate_using(method, ...)
        result.add(methodresult)
        if result.success:
            break
    return result, heartbeat

The idea behind activate() function is that you don't need to have Mode instance in order to activate a "mode" defined by a list of Methods.

Rough implementation of activate_using() (pseudocode):
def activate_using(methodcls: MethodCls, ...):
    method = methodcls()
    if check_platform_support(method) is False:
         return MethodUsageResult(failure_stage=PLATFORM_SUPPORT), None
    if check_requirements(method) is False:
        return MethodUsageResult(failure_stage=REQUIREMENTS), None
    entered = try_enter_mode(method)
    heartbeat_started = try_heartbeat(method)
    if not entered or not heartbeat_started:
        return MethodUsageResult(failure_stage=ACTIVATION), None
    if heartbeat_started:
        heartbeat = Heartbeat(method)
        heartbeat.start()
    return MethodUsageResult(), heartbeat

The rest of the work on this ticket has been split into multiple tickets. This one is done and can be closed.


Add "feedback" link to Autotune dashboard

Link it to a Google form TK from Lauren

gimme a form and I'll make a link in the nav for it.

https://docs.google.com/a/voxmedia.com/forms/d/1FZGfxov-3BcclKUMa0LkpaYL_4SOmCGGvuATBgNbzdg/viewform


added support for the Switch Enum Instruction

Added support for switch enum instruction

@mmroz could you please resolve the merge conflicts on this PR?

@mmroz it seems that merging #41 caused a conflict in this one. Could you please resolve before I review it?

@mmroz it looks like reverting this PR will create a new PR rather than reverting the merge. Therefore I just suggest you create a new PR with the fix to re-add the missing method header (i.e.,  visitSelectValueInst(SelectValueInst *SVI))


Standalone build and Runtime only build

What problem does this feature solve?
Hi,
 How to choose 'Standalone build' or 'Runtime only build' on Vue-CLI 3.

Thx.
What does the proposed API look like?
select

Hi, GitHub issues are only for bug reports and feature requests. If you need help, please ask on the forums or the discord.


Bootstrap 5 page scrolls smoothly on desktop browsers, but ABRUPTLY jumps to anchor points on iOS

Bootstrap 5 appears to have issues smoothly scrolling to anchor points on all iOS browsers that I've tried, including Safari, Chrome, Brave, and Firefox.
The same page scrolls smoothly on all desktop browsers.
Try https://brad-barnes.github.io/portfolio with both iOS and desktop browsers to see the contrast between smooth scrolling and abrupt changing to anchor points pointed to in the navbar.

Smooth scrolling is enabled via CSS, and not every browser supports it. When the browser doesn't, you get the jump to effect.


Unable to upload entire file content to ADLS GEN2 using Python SDK

DatalakeSerivceClient:
12.4.0:
Windows 11:
3.12.3 64-bit:

Describe the bug
While uploading file to ADLS2 using Python SDK DatalakeServiceClient , complete file contents are not uploaded on the ADLS2 container. There is no error in the output. When printed file content I can see full data there, but the last 2 rows from the file are not loaded to the target ADLS2. Small file is getting uploaded properly. Not sure if there's any limitation to content length here. Checked append_data and flush_data methods but not able to understand what's the root cause.
Content length: 359254
File type that is expected to be loaded:  csv
To Reproduce
Steps to reproduce the behavior:

Generate a file with content length more than 359254
Upload using append_data and flush_data methods with default parameters.

Expected behavior
Entire file content should be uploaded to the container / folder.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
When uploaded same file content using BlobClient it's working fine.

Hi @nupoor01nawathey Nupoor, thanks for reaching out. Could you please share a code snippet showing how you are constructing your client and how you are uploading your data? It is difficult for us to reproduce without a code sample. Thanks.

Sorry for the delay. PFA for the sample code. There is no error in the upload process but somehow 2 last rows from the source file are not getting uploaded to the target file.

Hi @nupoor01nawathey Nupoor, thanks for sharing the code. Here are several suggestions to try and address the issue. If none of these work, we can look more closely.

Firstly, you mentioned you are using version 12.4.0? That is a pretty old version and so I would recommend updating to the latest.
I would try opening your files in bytes mode rather than text and providing the append_data API a bytes. You are providing us a string where we will attempt some encoding. It is better to provide the raw bytes to upload. Additionally, I would recommend using a context manager with your file operations to ensure the file is closed and all contents are flushed. Another thing you could try is passing the SDK the file stream directly. Here are some examples of both of these:

# Open and read the file into memory
with open(local_file_path, 'rb') as local_file:
    file_contents: bytes = local_file.read()

# Pass file handle directly
file_client = dir_client.create_file(file_name)
with open(local_file_path, 'rb') as local_file:
    file_client.append_data(local_file, 0, len(local_file))
    file_client.flush(len(local_file))

Yet another thing you could try, if you just want to upload a file, is using the upload_data API which will create the file and upload the files contents fully. If you are file is large, this can prevent having o read the whole file into memory and even offers parallelism.

with open(local_file_path, 'rb') as local_file:
    # You need to pass overwrite=True to create the file.
    file_client.upload_data(local_file, overwrite=True)

Hopefully one of these suggestions can help but please let us know if not, thanks.

@pvaneck  Thanks for the quick response, the 3rd solution you provided is working fine.
with open(local_file_path, 'rb') as local_file:     # You need to pass overwrite=True to create the file.     file_client.upload_data(local_file, overwrite=True)


Chore: Use GitHub license template

In order to be able to identify the main license of all managed repositories centrally, the SAP Open Source Program Office (OSPO) asks all teams to have an identifiable license in their repositories. While you are properly using the REUSE tool (thanks for that!), a license file that specifies the main license of your project is missing. As a consequence, the license of this repository is not detected properly by GitHub. This PR includes text from a GitHub license template that should facilitate the automated license detection.

Hi Sebastian,
There is already https://github.com/SAP/grunt-openui5/blob/master/LICENSE.txt. I think GitHub has trouble with the formatting of the LICENSE files downloaded by the REUSE tool and therefore fails to detect the license. IMHO this should be fixed by either the REUSE tool or GitHub.
Anyways, we would rather like to replace the content of LICENCE.txt instead of adding a new LICENSE file as proposed in this PR. Would that be possible? We have several other projects facing the same issue.
Thanks!

Well, my bad. I thought, I replaced the original file with the template...
And yes, the problem with the formatting is known - the reason that GitHub obviously fails to detect things properly one the one side and the need on our side to get the licenses easily retrieved via an API leads us to such actions. We will create PRs for the other projects as well. I'll close this PR and do the replacement in another.


Documentation and packages out of synch

Pip package is not in sync with github and documentation.  For example documentation has response_format and pip package MistralClient does not support it.

Add version numbers to clients so easier to track and debug
Update pip packages frequently along with releases of documentation and push to github.

Thanks for the issue report! This should be fixed now. Please let us know if you see more issues. Thanks!


Sentry unable to scrub sensitive infomation in in case of raw body

I have mentioned the password as a sensitive field in the configuration. But In case of invalid JSON, the sentry is sending the password as plain-text to server.
ActionDispatch::Http::Parameters::ParseError: 822: unexpected token at '{
"username":"abc.pqr",
"role": "admin"
"password": "Abc@123"
}'

Any news on this issue? I'm having the same problem

thanks for reporting this issue, I've opened https://github.com/getsentry/raven-ruby/pull/984 for solving it. would you mind using
gem 'sentry-raven', github: "getsentry/raven-ruby", branch: "fix-#948"

to give it a try?


chore: remove use of dispatchError in RuntimeAPI

The use of DispatchError as error type is only required for the extrinsics. For the RuntimeAPI we can use whatever type we want (as long as it implements scale and type-info).
Using such a custom type allow us to return richer information and participate into our will to move away from substrate

@tdelabro I can incorporate most of these changes into my PR as I am refactoring the error messaging in the rpc in #1555

superseeded by #1555


Create Outbound OML ORC Segment

Story
As a public health lab, to be able to make use of received electronic NBS orders, I need the OML ORC segment included with the order.
Pre-conditions

[x] The required fields are already included in the incoming FHIR.

Acceptance Criteria

[x] TheORC segment shows up in the outbound OML and has all the required fields.

Tasks
Research

[x] Identify required fields.

Engineering

[x] Convert ORC segments

[x] ORC-1 Order Control
[x] ORC-2 Placer Order Number

[x] ORC-2.1 Entity Identifier
[x] ORC-2.2 Namespace ID
[x] ORC-2.3 Universal ID
[x] ORC-2.4 Universal ID Type

[x] ORC-9 Date/Time of Transaction
[x] ORC-21 Ordering Facility Name

[x] ORC-21.1 Organization Name
[x] ORC-21.6 Assigning Authority
[x] ORC-21.7 Identifier Type Code
[x] ORC-21.10 Organization Identifier

Definition of Done

[x] Documentation tasks completed

[x] Documentation and diagrams created or updated

[x] Implementation guide (/ig folder)

[x]  Add ig provenance (changelog) updates for this story specifically (if applicable)

[x] ADRs (/adr folder)
[x] Main README.md
[x] Other READMEs in the repo
[x] If applicable, update the ReportStream Setup section in README.md

[x] Threat model updated
[x] API documentation updated
[x] Source code documentation created when the code is not self-documenting

[x] Code quality tasks completed

[x] Logging added where useful
[x] Code refactored for clarity and no design/technical debt
[x] Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies
[x] Code is reviewed or developed by pair; 1 approval is needed but consider requiring an outside-the-pair reviewer
[x] Code quality checks passed

[x] Security & Privacy tasks completed

[x] Security & privacy gates passed

[x] Testing tasks completed

[x] Load tests passed
[x] Unit test coverage of our code >= 90%

[x] Build & Deploy tasks completed

[x] Build process updated
[x] API(s) are versioned
[x] Feature toggles created and/or deleted.  Document the feature toggle
[x] Source code is merged to the main branch

Research Questions

Optional: Any initial questions for research

Decisions

Optional: Any decisions we've made while working on this story

Notes

RS fhir -> hl7vs KS video

This Story helps complete the requirement:
MVP-REQ-08 - Each intermediary will support at least one format for outbound orders


sometimes I see Windows ugly scrollbars

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS:  Windows 10 1703

Issue

List your plugins please

@Stanzilla hyperterm-panda, hyperline, gitrocket and hyperpower. Scrolls exist both with/without this plugs. It's not significant, but better to remove them, no? Appears and disappears

Thank you for your feedback and your screencast but please use our issue template.
Without that, we are forced to spend time to ask you all the tings are mentioned in our issue template.
We need to know if you can reproduce without any plugin...
We need to know your Hyper version..
Please reopen an issue with all issue template informations filled.

Oh sorry, I misread :)

Can you try to reproduce on our canary version (v2.0.4)?

@chabou yea. just wait

@chabou nice!  😊

Yes!
Thank you for your feedback


[vcpkg baseline] Retrigger failed port qscintilla

Related to https://github.com/microsoft/vcpkg/pull/11815 and many PRs.
QScintilla:86-windows failed to download source on CI, we can't repro this locally.
Retrigger this port.
-- Downloading https://www.riverbankcomputing.com/static/Downloads/QScintilla/2.11.4/QScintilla-2.11.4.tar.gz...
-- Downloading https://www.riverbankcomputing.com/static/Downloads/QScintilla/2.11.4/QScintilla-2.11.4.tar.gz... Failed. Status: 52;"Server returned nothing (no headers, no data)"
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:175 (message):
  Failed to download file.
  If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY environment
  variables to "https://user:password@your-proxy-ip-address:port/".
  Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
ports/qscintilla/portfile.cmake:1 (vcpkg_download_distfile)
scripts/ports.cmake:76 (include)

Since the tombstone has been removed, and x86-windows is clean, so close this PR.


apply on a Matrix returns a Vector

mwe:
using Proj, GeometryBasics
import GeometryOps as GO
point_grid = Point2d.(-180:180, (-90:90)') # matrix
GO.reproject(point_grid, source_crs="+proj=longlat +type=crs", target_crs="+proj=wintri +type=crs") # vector

One thing we could do here is to explicitly document that one should use broadcasting on vectors of geometries when you want shape preservation.  Broadcasting semantics like similar may also help here.

We could maintain shape fairly easily.


(notepadplusplus) How to force install Release Candidate

I have installed Notepad++ v<IP_ADDRESS> with choco, however wish to install Release Candidate for <IP_ADDRESS>, which is not available over chocolatey How can I "upgrade" manually using choco command line? This is meant to fix important issues.
https://github.com/notepad-plus-plus/notepad-plus-plus/issues/10968

As this is phrased as a question, and no template is being used I will be moving this over to Discussions.


Spacing in test_delayed_feature_transformer.py

The spacing in test_delayed_feature_transformer.py: L307-321 is a little messed up.  The indenting of the dictionary components seems to be off by 1.
    if logical_type in [Integer, Double, Categorical]:
            assert transformed.ww.logical_types == {0: logical_type,
                                                    '0_delay_1': Double,
                                                    'target_delay_0': Integer,
                                                    'target_delay_1': Double}
        elif logical_type == Boolean:
            assert transformed.ww.logical_types == {0: logical_type,
                                                    '0_delay_1': Categorical,
                                                    'target_delay_0': Integer,
                                                    'target_delay_1': Double}
        else:
            assert transformed.ww.logical_types == {0: logical_type,
                                                    '0_delay_1': logical_type,
                                                    'target_delay_0': Integer,
                                                    'target_delay_1': Double}

This isn't real


Raygui

Hi
How do we get setup to use the bindings for RayGUI?
Missing a binary for raygui.dll?

I would like to know this as well

Initially raygui tried to load bindings from raylib but this required a custom build of raylib to include it as it is not built into raylib by default. This caused issues so I changed it to look for its own library raygui instead so on windows that would be raygui.dll etc.
There is a similar issue on raygui here with more details. I will look into improving the documentation to make this clearer to new users.