Project Start!

Hi
I want to run the project. This error is displayed and I do not know where the problem is and why this error occurred to me.
http://s6.picofile.com/file/8387060150/saleor.png
I did all this work and still have the same problem!
" npm i" "npm i -f" And " Remove node_modules folder and package-lock.json file and reinstall 'npm i' "
Help me please!
Thank you (^_^).

It seems like webpack-dev-server wasn't installed correctly. There are some threads about this issue on the internet, please take a look for example here: https://stackoverflow.com/questions/35810172/webpack-is-not-recognized-as-a-internal-or-external-command-operable-program-or

It seems like webpack-dev-server wasn't installed correctly. There are some threads about this issue on the internet, please take a look for example here: https://stackoverflow.com/questions/35810172/webpack-is-not-recognized-as-a-internal-or-external-command-operable-program-or

I have read and tested your guide but still have the same problem with the program and really do not know where to solve the problem!
This problem is the same for both the " saleor-storefront " project and the " saleor-dashboard " project!

There is some issue with the installation of your dependencies. webpack-dev-server should be present in ./node_modules/.bin/ catalog. Which version of Node and NPM are you using? Are there any errors when you run npm i?

There are 3 files for " webpack-dev-server " in the ( ./node_modules/.bin/ ) folder!
1- webpack-dev-server
2- webpack-dev-server.cmd
3- webpack-dev-server.ps1
My Npm Version: 6.13.6
My Node Version: 12.14.1

When running the npm command i will show no error (^-^)

There is some issue with the installation of your dependencies. webpack-dev-server should be present in ./node_modules/.bin/ catalog. Which version of Node and NPM are you using? Are there any errors when you run npm i?

There are 3 files for " webpack-dev-server " in the ( ./node_modules/.bin/ ) folder!
1- webpack-dev-server
2- webpack-dev-server.cmd
3- webpack-dev-server.ps1
My Npm Version: 6.13.6
My Node Version: 12.14.1

When running the npm command i will show no error (^-^)

Look at the error message - it says "Environment variable API_URI not set". API_URI is the address of the Saleor backend. If you're running the API with the default settings it should be available at localhost:8000. Please read a section about it in our readme: https://github.com/mirumee/saleor-dashboard/#configuration
If you're not familiar, please also read about setting environment variables on Windows.

i have just did what you saied but i didnt solve.
can you help me by the more details guidenence? such as video or screen shots?
I really thanks you for spending time to help me.

Look at the error message - it says "Environment variable API_URI not set". API_URI is the address of the Saleor backend. If you're running the API with the default settings it should be available at localhost:8000. Please read a section about it in our readme: https://github.com/mirumee/saleor-dashboard/#configuration
If you're not familiar, please also read about setting environment variables on Windows.

i have just did what you saied but i didnt solve.
can you help me by the more details guidenence? such as video or screen shots?
I really thanks you for spending time to help me.

Unfortunately, we yet don't have any video tutorials about setting up Saleor. Did you set the API_URI variable? What happens now when you run npm i and npm start?

yes I did . i sent you the screen shot . will you help me if I give you the access of computer with anydesk?

Unfortunately, we yet don't have any video tutorials about setting up Saleor. Did you set the API_URI variable? What happens now when you run npm i and npm start?

yes I did . i sent you the screen shot . will you help me if I give you the access of computer with anydesk?

I see the prompt Terminate batch job (Y/N)? - you shouldn't terminate that process - it takes some time for webpack-dev-server to build and start serving all project files.


bug: incorrect separator color for lualine buffer

Neovim version (nvim -v)
NVIM v0.11.0-dev-315+g46187117c Build type: RelWithDebInfo LuaJIT 2.1.1716656478 Run "nvim -V1 -v" for more info
Terminal / multiplexer
alacritty / zellij
Describe the bug

From repro.lua (test.lua):
$ nvim -u test.lua test.lua README.md aliases -c ":bnext"

Repro
vim.o.packpath = "/tmp/nvim/site"

local plugins = {
  rose_pine = "https://github.com/rose-pine/neovim",
  lualine = "https://github.com/nvim-lualine/lualine.nvim",
}

for name, url in pairs(plugins) do
  local install_path = "/tmp/nvim/site/pack/test/start/" .. name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system({ "git", "clone", "--depth=1", url, install_path })
  end
end

require("rose-pine").setup({
  styles = {
    bold = true,
    italic = false,
    transparency = true,
  },
  highlight_groups = {
    Comment = { italic = true },
  },
})

require("lualine").setup({
  options = {
    icons_enabled = true,
  },
  sections = {
    lualine_a = { "mode" },
    lualine_b = { "branch", "diff", "diagnostics" },
    lualine_c = { { "filename", path = 1 } },
    lualine_x = { "encoding", "fileformat", "filetype" },
    lualine_y = { "progress" },
    lualine_z = { "location" },
  },
  inactive_sections = {
    lualine_a = {},
    lualine_b = {},
    lualine_c = { { "filename", path = 1 } },
    lualine_x = { "location" },
    lualine_y = {},
    lualine_z = {},
  },
  tabline = {
    lualine_a = { { "buffers", show_filename_only = false } },
    lualine_x = {},
    lualine_y = {},
    lualine_z = { "tabs" },
  },
  extensions = {},
})

vim.cmd("colorscheme rose-pine")

@kdheepak
Couple quick questions...

Have you tried another colorscheme such as say Catppuccin? If so, does it also exhibit the same behavior in the tabline in lualine? ie. the tab that is inactive is getting that white separator character?

Does this only happen if you are on say the middle buffer out of 3, or like 2 out of 5? or does it happen on every single buffer no matter which is selected?

Because there is nothing in the way rose-pine configures the highlights for lualine that I can immediately see that would cause this to happen.
If you can provide a bit more information, it would greatly help in triaging this issue. Thanks! 😄

The issue doesn't occur with other colorschemes:

I narrowed the issue down to transparency:
require("rose-pine").setup({
  styles = {
    transparency = false, -- no issue
    -- transparency = true, -- issue occurs
  },
})

I'm not sure if that's an issue with lualine or this repo.

I think #301 should fix this

I tested it out and it fixes it for me! Thanks for the responsive changes!


Timer - Does Not reset

First Issue with Release:  0.94.3
Last working: unknown
Operation environment: HASSIO on Ubuntu 18
Issue with Timer: https://www.home-assistant.io/components/timer/
Home Assistant release with the issue: 0.94.3
|item|value|
arch | x86_64
dev | false
docker | true
hassio | true
os_name | Linux
python_version | 3.7.3
timezone | America/New_York
version | 0.94.3
virtualenv | false
Last working Home Assistant release (if known): unknown
Operating environment (Hass.io/Docker/Windows/etc.): HASSIO
Ubuntu 18.04 on Dell Latitude 5540
Component/platform:
Issue with Timer: https://www.home-assistant.io/components/timer/
Description of problem:
As per the documentation, sending "timer.start" with en entity_id should start with the default duration or restart.
Issue #1:  Sending timer.start a second time with just an entity_id DOES NOT restart the timer to the default (or started) duration
Observation #2:  If you send timer.start a second time, you can specify a new duration.   This duration will be relative to original start time.   So, if you start a 5 min timer and at 4 minutes send a start with 10 minutes, the timer value will continue from 9 minutes, since 1 minute has passed.   Is this the expected behavior?  (documentation on this was not clear)
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
  mbr_fan_cooldown:
    name: "MBR Fan Cooldown"
    duration: '00:05:00'
  motion_countdown_livingroom:
    name: "Living Room Light Timer"
    duration: '00:10:00'

Traceback (if applicable):

Additional information:
Discussed here:
https://community.home-assistant.io/t/timer-reset-restart/57524/6

Sorry, just found:
https://github.com/home-assistant/home-assistant/issues/12013
Closing this


(CREATE_DB) Is the server running on that host and accepting TCP/IP connections?

Hello,
I excuted CREATE_DB, and provided SRID, EPSG code, and srsName. It tried to connet to the database, but error shows:

psql: error: connection to server at "localhost" (::1), port 5432 failed: Connection refused (0x0000274D/10061)
Is the server running on that host and accepting TCP/IP connections?
connection to server at "localhost" (<IP_ADDRESS>), port 5432 failed: Connection refused (0x0000274D/10061)
Is the server running on that host and accepting TCP/IP connections?

What is the problem?

Hey there, this error has nothing to do with the 3DCityDB, it is a PostgreSQL connection problem.
Do what the error message says: Check if you server is running and accepting connections.
These two links are a good starting point to analyze and resolve typical postgres connection issues:

https://stackoverflow.com/questions/20825734/postgresql-connection-refused-check-that-the-hostname-and-port-are-correct-an
https://bobcares.com/blog/postgressql-connection-refused/

Closing. Feel free to reopen if you can't manage to resolve this. In that case we will need much more detailed information on your setup.

Thank you very much, I reinstall with the postgre server and it works not. But in the next step I was asked to provide password, however I am not able to type in. Do you know why?


Consider using the BEAM logger

Hello!
The BEAM has a standard logger, and it has many features such as filters, error handling, multiple backends, dynamic configuration, and back pressure mechanisms to prevent a runaway logging process from causing performance problems.
https://www.erlang.org/doc/apps/kernel/logger_chapter.html
It would be fab to be able to use this library with the standard logger!
Thanks,
Louis

Hello!
It's a good point to support what is already standard in the BEAM in order to tap into already proven concepts. I will give it a try to fit this to the current architecture of Glimt. Some of the features are a bit overlapping (but of course the BEAM logger has a lot more features) but perhaps there is a good way of map the Glimt features onto the BEAM logger.
Thanks for your input!
/
John


Update !== to (apparently) intended ===

Just an oversight I'm sure.

yup, thanks

@petkaantonov doc rebuild needed


feat(cli): set query timeout value via CLI argument

What was wrong?
When a beacon trin node request a light client content (while keeping in sync with the latest header), the query can take more time than the beacon slot duration (12 sec), because the default query timeout duration is set to 60 sec.
For beacon, we want to set this timeout to no more than 12 sec, so we can always request the light client content for the next slot and not miss slots.
How was it fixed?
Set the query timeout via CLI argument.
To-Do

[ ] Clean up commit history and use conventional commits.

I didn't add a 12s timeout for specific beacon queries, but #1566 should do most of the heavy lifting. On top of that, it should just be a line or two to drop into light-client/src/consensus/rpc/portal_rpc.rs. (Is it just the optimistic updates that should have a custom limit?)
Anyway, I figured just having the refactor available would be helpful for you to do whatever kind of testing you want to do with a 12s limit while running beacon, @ogenev . So I think we can merge the refactor without it, if the approach looks good enough to everyone.

Wouldn't setting this flag to 12 seconds (I assume desired when beacon is enabled), change behavior for other networks as well?

This is a good point, we may want different timeouts per network and content. I'm closing this in favor of https://github.com/ethereum/trin/pull/1566.


Add support to export scene to add light map

Just to review

The demo is nice. How did you go about specifying the light source in the scene before exporting it?
We will need input from Vittal on this one as he is working on the lights support.

I think you could separate completely out the export part as we could merge that sooner. Maybe put the export in the GVRContext as it is the usual dumping ground for stuff like that.

Hi @liaxim, it is exporting just the Mesh information already.  After that you can add the lights' source at the Beast application that I have sent by email with the steps to test.

I was referring to the lightMap flag in addition to the export functionality. Not too big of a deal.

Looks good.
Regarding lights -- I have an initial version of multiple lights using the shaders present in the Texture Shader class under https://github.com/Vittalbabu/GearVRf/commits/light. This is work in progress (not a pull request yet) and has incomplete implementation (plus lots of debug code) of some of the multiple lights functionality. When this is complete, we should be able to query from the Scene all the lights that are defined. Currently the implementation takes the same parameters as the existing GVRLight class but we are now able to attach multiple lights. All shader types  get access to all the lights in the Scene and only LightShader uses these lights. Goal is to fully flesh out the interfaces in Scene that handle Light, look at updating the shader in LightShader class (create multiple shaders if required), complete further definition of Light types.
Finally, we have to address one question. Do we force all shaders to use the available lights in the Scene or do we allow some of the shader types to ignore lights in their rendering. If we allow shaders to ignore lights, we will end up with some objects in the scene lit up while other are not.

@Vittalbabu As far as I can see, this patch does not directly handle light types corresponding shaders. It mainly adds an exporter to export the scene for offline lightmap backing (with Beast). The question may be a bit off topic in this thread. In my opinion, in our current architecture, we allow users to select shaders including custom shaders for each scene object, so there is no systematic guarantee that all lights are rendered. The developer needs to take care of consistency.

@ragner Thanks for the patch for review. It can be used now for static lights and static scene objects. Since it is offline baking, it doesn't need to support moveable lights and scene objects. Moveable things need to be handled in another way.
So the difficult issue is to design some way of coordinating Beast and dynamic lighting. Do you have any plan for that?
I think on GVRf side, maybe we can add a flag "moveable" to Scene Objects and Lights, and only export the non-moveable scene objects and lights for Beast.
Further versions of GVRf will ideally export lights (types, position, etc.), so offline baking of these lights, and online rendering can be coordinated.
What do others think?

@danke-sra Movable lights will be implemented by the new Light class holding a SceneObject* (to get the position,direction from the SceneObject). If this pointer is NULL, light is static. We can provide Scene::getLights() and Scene::getStaticLights() methods or Scene::getLights(bool staticLightsOnly = false)

@ragner A minor issue with the exporter: when I export to "A.obj", it creates two files A.obj and A.obj.mtl. It would be better to use the file name "A.mtl" for the material file. Is it possible?

Hi all,
Thank you for your review.
How there is no visual editor to the scene of GVRf framework, the only way I have found to integrate it with Beast was exporting the scene.
I have made this patch just for you to see something working and to prove that it is possible.
If you agree with this I will implement some "final version".
I am not sure if .obj is the best format to export the scene, I am using it just because there a sample of beast that imports .obj file.
Maybe the best solution could be export at collada format.
Thank you all.

@ragner Thanks for keeping us in the loop. Please go ahead to implement the final version. Please keep in mind a couple of things while you design / implement it:

We need to make sure both static scene objects / lights, and moveable scene objects / lights work. Since Beast only handles static things, we can make sure we can easily exclude moveable scene objects / lights from the exporter.

The Visual Studio project for generating the lightmap would also be part of GVRf. So please make that tool generic as well. For instance, it can process the exported lights. Since dependency on Visual Studio may be some extra burden for Android developers, if possible, could we implement it in Lua, since Beast SDK also provides a Lua binding? If not, Visual Studio is fine. We just need to support multiple platforms, such as Windows, Mac and ideally Ubuntu as well.

I understand GVRf doesn't currently have complete light information, we can use standard Collada format to import those lights.
These are just some suggestions. Look forward to seeing the next version. Thanks for this contribution. It is amazing work!

Hi @danke-sra,

I haven't found any docs about Lua binding to Beast. What I have found is that Beast offers just a Lua render pass,  which allows users to customise the baking.
I am not sure if Beast is multi platform, its evaluation SDK is just for Windows platforms. I may need help about it. What I know is that Unity3d is multi platform and has support to Beast.

Hi @ragner,
I checked again and found Lua support quite difficult. Yeah, you are right there is a Lua interface is for render pass scripting but non-C programming API is difficult -- it only supports C# and Python. So let's stick with Visual Studio and C++. Thanks.


Starting Taint for simple register operands

Test source code:
void fun(int* ptr, int a)
{
    *ptr = a;
}

int main(){
  int *p = 0;
  fun(p,4);
  return 0;
}

Compiled with:
$ clang -g -O0 m.c -o m
Consider following MIR instruction, which is at the crash point in the presented test.
crash-start MOV32mr $rax, 1, $noreg, 0, $noreg, $ecx
Currently, in the startTaint(), we try to insert to the Taint List all of the tree possible locations:

Memory location at the address $rax + 0 (destination operand) - inserted
Register $rax (destination operand base register) - not inserted, since it is treated equal to the location 1.
Simple register location $ecx (source operand) - inserted

Is it valid to taint a simple register location, if it is not a base register of a memory operand?
This is done in TaintAnalysis::startTaint().
In the presented case, the MIR level data flow graph looks like:

From the DFG, is it obvious that path, which starts from register location $ecx leads to the wrong blame instruction.
Based on the constructed DFG, llvm-crash-analyzer cannot decide which leaf node is the blame one.

In my opinion, the initial taint list should include the destination memory operand. By the semantics of the crashing instruction and SEGV violation, it is clear that the memory operand is tainted. The path on the right hand side in above DFG is not needed.

In my opinion, the initial taint list should include the destination memory operand. By the semantics of the crashing instruction and SEGV violation, it is clear that the memory operand is tainted. The path on the right hand side in above DFG is not needed.

To my understanding, source operand of the crash instruction should be in the taint list if it is a memory operand.
For example, in $rax = MOV $rbx, 8, invalid value of $rbx + 8 could cause crash in general case. In most cases, I've seen, the value of the base register $rbx is responsible for the crash. Anyways, any memory operand could cause crash and I don't think it matters if it is a destination or a source.
On the other hand, I think that simple register location, like $rax in the example above, cannot cause crash in any case, so we should not add it to the Taint List.
Thanks,
Nikola


Adding SSTD'S does not show up in game

When I use the status menu and add a sstd it adds it as a status but when I load the save in game and try to progress the sstd never shows up as an infection.  I also have a suggestion for the Furpies infection, maybe you could choose what type you get?

Alright, I had some time to look into this. Yes, the status effect is present but the issue is the editor doesn't currently support editing status effect duration, which is what the game depends on when dealing with this. If you know how to, you can set the minutesLeft property equal to 17280 and it should work as intended.
I'm planning on finishing up status effects either today or tomorrow

I also have a suggestion for the Furpies infection, maybe you could choose what type you get?

No clue how that works but it's most likely also something to do with status effects not being 100% supported yet


Fix self.max_tokens in anthropic_llms.py

Fix bug where self.max_tokens was not set.
The AnthropicChatLM uses everywhere self.max_tokens while in constructor is sets self.max_token. It doesn't call issues on smaller responses but I caught it while asking for bigger (>1000tokens) response.

As far as I can see the tests are broken in main, not caused by my patch


get-spcontentdatabase change

Docs Build status updates of commit 307b72b:
:clock10: Full build: the average full build time is 13 min(s) 49 sec(s), this is based on the last 465 build(s) for this repository.

Docs Build status updates of commit 307b72b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDatabase.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Update-SPProfileSync.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 0b51a03:
:clock10: Full build: the average full build time is 13 min(s) 49 sec(s), this is based on the last 466 build(s) for this repository.

Docs Build status updates of commit 0b51a03:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Get-SPContentDatabase.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Update-SPProfileSync.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix markdown links

Prior to this commit several directory links in DEVELOPER.md were incorrectly formatted to render as links. This commit removes the errant )s to resolve this.

Thank you @jeffweiss — sorry so slow in merging!


Add versioned Image alias names and remove image aliases whose images do not exist

Related command
az vm image list
Resource Provider
Microsoft.Compute/compute
Description of Feature or Work Requested
As discussed with several PMs and Xing Zhou from the CLI team, we had to update the Image aliases in PS. We want CLI to be change in parallel to this.
The PS image updates: https://github.com/Azure/azure-powershell/pull/21012/files#diff-2b55a7c7b9a159041f1adb1ba967b55a8840ddc6e88df099b70a50c17331f6e2L9
There is also a breaking change warning being added to New-AzVM to help amplify the communications and future changes in the Oct 2023 breaking change. We plan to update the CLI docs, https://learn.microsoft.com/en-us/azure/virtual-machines/linux/cli-ps-findimage#list-popular-images , that we know that refer to these image aliases. We want to include a link to these docs in the breaking change warning.
Minimum API Version Required
2022-11-01
Swagger PR link / SDK link
N/A , should only be client side changes.
Request Example
No response
Target Date
2023-04-01
Additional context
We want this released in the next available CLI release. There may be some updates to the PS breaking change warning we would want mirrored in the CLI codebase too.

add versioned image alias names

@Sandido This is the configuration file for image alias aliases.json used by the CLI, since it is currently maintained by the service team, could you help submit a PR to modify this configuration file?
And then we will review it and add some warning log to notify the possible breaking changes in advance

I need to make some edits to the PS work, so I will do that first before raising the CLI PR.

@Sandido Thanks for creating the PR for CLI alias.json

I don't know if there are any tests to update/create, or where to add the upcoming breaking change warning in New-AzVM and New-AzVmss like in PS.

We will do the rest of the work ourselves, and then let you help review the related PR


Add documentation to git

Hey,
I find most of the documentation that is on par is updated through their users by being able to submit a PR to a repo where the documentation for the site relies.
much like this site:
https://www.graphile.org/postgraphile/introduction/
suggest improvements on the page:
https://github.com/graphile/graphile.github.io/edit/develop/src/pages/postgraphile/introduction.md

The docs are already in the repository and accepting contributions: https://github.com/onivim/oni2/tree/master/docs/docs
I'm sure they could be easier to find though, and that would be a good contribution opportunity in itself, I'd say!

This was resolved by #2483, no?

@glennsl yes


Chapter number is 'Chapter 1' instead of '1', include cover art in mp3

Thanks for the excellent package, it works like a charm. I tweaked it a little bit to serve my goals (Audible --> Google Play to be able to stream to Sonos) better. After the extracted mp3 is created, I changed the code to first create the cover art. Next, in the creation of the per-chapter files, I have added the chapter number to the title, fixed the chapter metadata, and added the cover art:
debug "Created ${full_file_path}."

cover_path="${output_directory}/cover.jpg"
debug "Extracting cover into ${cover_path}..."
</dev/null ffmpeg -loglevel error -activation_bytes "${auth_code}" -i "${path}" -an -codec:v copy "${cover_path}"

if [ "${mode}" == "chaptered" ]; then
    debug "Extracting chapter files from ${full_file_path}..."

    while read -r -u9 first _ _ start _ end
    do
        if [[ "${first}" = "Chapter" ]]
        then
            read -r -u9 _
            read -r -u9 _ _ chapter
            chapterarray=($chapter)
            echo "${chapter} :: ${chapterarray[0]} :: ${chapterarray[1]}"
            chapter_padding
            chapter_file="${output_directory}/${title} - ${chapter}.${extension}"
            chapter_file_with_cover="${output_directory}/${title} - ${chapter} - cover.${extension}"
            </dev/null ffmpeg -loglevel error -stats -i "${full_file_path}" -ss "${start%?}" -to "${end}" -codec:a copy -metadata track="${chapterarray[1]}" -metadata title="${title} - ${chapter}" "${chapter_file}"
	</dev/null ffmpeg -loglevel error -nostats -i "${chapter_file}" -i "${cover_path}" -c copy -map 0:0 -map 1:0 -id3v2_version 3 -metadata:s:v title="Album cover" -metadata:s:v comment="Cover (Front)" "${chapter_file_with_cover}"
        fi
    done 9< "$metadata_file"
    rm "${full_file_path}"
    debug "Done creating chapters. Chaptered files contained in ${output_directory}."
fi

debug "Done."

Let me know if you want me to push this to github. Maybe the 'include cover' should be a command-line option.

I don't even think that it needs to be a command line option. It was something that I originally wanted to add to the script, but never got around to figuring out how to embed the cover into the output mp3 file using ffmpeg.
I just merged some code that should hopefully help with non-english chapter regex output. I would recommend looking through that for any changes that affect this, and if possible add the cover to each output chapter file directly.


Update sbt-scoverage to 1.7.2

Updates org.scoverage:sbt-scoverage from 1.5.1 to 1.7.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.5.1).
You might want to review and update them manually.
README.md
build.sbt
project/plugins.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, semver-minor, old-version-remains

Superseded by #20.


feat: Add additional compute types for CodeBuild

Description of changes:

Adds additional compute types for codeseeder codebuild jobs.

Relates: #456
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing per #456


3.13.2

Fixes: https://github.com/conda-forge/json_tricks-feedstock/pulls
And asked upstream to include license file in their distribution: https://github.com/mverleg/pyjson_tricks/pull/61
Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

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

@conda-forge/json_tricks this is ready for review.

Not really, I just wanted an updated version

@hmaarrfk sounds good, I'll bump it to 3.13.4 and merge it in about an hour and a half (once I get out of meeting).

Bot

:+1: (I gotta figure out why PR notifications aren't coming through for this repo...)


Xdebug error on Laravel Artisan Commands

Description:
When run any artisan command there is an xdebug related issue.
Clear laradock installation with XDEBUG on workspace and php-fpm enabled
php artisan migrate
Xdebug: [Step Debug] Could not connect to debugging client. Tried: host.docker.internal:9003 (through xdebug.client_host/xdebug.client_port) :-(
Nothing to migrate.
Xdebug: [Step Debug] Could not connect to debugging client. Tried: host.docker.internal:9003 (through xdebug.client_host/xdebug.client_port) :-(
Xdebug: [Step Debug] Could not connect to debugging client. Tried: host.docker.internal:9003 (through xdebug.client_host/xdebug.client_port) :-(

If you are not using XDebug in your workspace - edit xdebug.ini (use php --ini to find where it is) and set "xdebug.mode=off" instead of "xdebug.mode=debug". You can switch it back on temporarily the the env var XDEBUG_MODE which overrides this setting.
In addition if you are using Xdebug you need to remove some lines from docker-compose.yml. For the php-fpm container there is a "ports" section, forwarding php-fpm:9003 to the host. This is not correct, as it's your debugging program (e.g. PHPStorm) that opens port 9003 and listens on it for php to connect.

@merlinblack
Is there a reason why the "ports" section was added. It was not there previously.

@merlinblack Is there a reason why the "ports" section was added. It was not there previously.

You would have to ask the author - having the 9003 port there is incorrect, hence why it should be removed.

please merge this fix as its related to #797 #3083 and others

@merlinblack removeing the ports section it's not solve the problem :(

@merlinblack removeing the ports section it's not solve the problem :(

Unfortunately, Xdebug is a quirky beast - I can only suggest to make sure Xdebug can contact the port it is configured for on your localhost. You can use Netcat, or start up a temporary HTTP server on port 9003 for example and try to use curl or similar. Look in the logs for Xdebug.

I think there is also a version problem. For example with version 3.1.3 xdebug works fine but with version 3.1.2 no.  And the problems starts when the php 8 was added. Before everything just woks fine. Hard to understand why this problem is not solved and every month a new not wide used service is added to laradock.

There was a problem with a  laradock dependency dragging in another version of php and causing havok too. Something to check for
Sent from BlueMail
On 9 Mar 2022, 5:23 am, at 5:23 am, Lorand Gombos @.***> wrote:

I think there is also a version problem. For example with version 3.1.3
xdebug works fine but with version 3.1.2 no.  And the problems starts
when the php 8 was added. Before everything just woks fine. Hard to
understand why this problem is not solved and every month a new not
wide used service is added to laradock.
--
Reply to this email directly or view it on GitHub:
https://github.com/laradock/laradock/issues/3064#issuecomment-1062073623
You are receiving this because you were mentioned.
Message ID: @.***>

My 2 cents. If you are running with Laravel Sail you can put in your .env file:
SAIL_XDEBUG_CONFIG="log_level=0"
to get rid these messages
remember to rerun containers (sail down then sail up -d) after change


Manually create datablock

Hey there!
I have been trying to use this library for some days now to read and write from and on cif files, and I was wondering if it was possible to manually create and insert data into datablocks.
In my use case, I need to write a datablock to a file, but I need to modify the elements in the atom_site tag before actually writing the data with an updated version of those atoms i receive from elsewhere in a different format.
I have been taking a look at the source files, but I haven't quite figured out yet a way to do that.
Would it be possible to add an new file to the examples that manually creates a datablock based on a small (can be hardcoded, it doesn't matter) atom dataset?
Thanks!

The documentation for libcifpp is a bit lacking at the moment, I agree.
What you want to accomplish is certainly possible. The classes in libcifpp try to implement common C++ interface for manipulating data. cif::file e.g. inherits from std::list and thus offers all the methods from that class, so you can insert, delete and iterate datatblocks among others.
cif::datablock is also a std::list. Of cif::categories in this case.
cif::category tries to implement the Container requirements as well as the SequenceContainer requirements. That means it looks a bit like a std::vector.
Inserting is done most effectively using the emplace methods.
You could have a look at the file test/unit-v2-test.cpp. This unit test contains many small functions that test various ways you can create and manipulate data objects in cif files. You can also look at the other projects in the PDB-REDO space. All of them are using libcifpp to read and or write cif data.
I will try to create proper documentation. Once I find the time to do so.


Decide On Testing Framework

Now since rawcodeio is now open-source we should probably roll out a testing framework.
This will allow us to not only make sure PRs won't cause crashing, but will also allow us to make sure we don't introduce potentially bad bugs in a release.
Perhaps something widely used like Karma, w/ Jasmine. Or one of the many others.

I have to admit, I'm a complete noob when it comes to testing!
Last test I wrote was about 5 years ago unit-testing something in Java :blush: from there it was just EP with small functions to immediately test expected results of rather small modules.
I'll do my best to get up to speed with this! Karma w/ mocha or jasmine look alright to me. Should we set up something like TravisCI (not that I'd ever done that..)?

Haha it's alright,
I'd be more than happy to sort of bring the initial PR to implementing this, and getting the framework around testing setup so then you can start writing unit tests, and getting it all ready.
Yes I think we should setup it with something like TravisCI (quite an easy process, one config file really).


Variableized Log4J2 Configuration for ES 5.x

Pull request acceptance prerequisites:

[x] Signed the CLA (if not already signed)
[x] Rebased/up-to-date with base branch
[x] Tests pass
[ ] Updated CHANGELOG.md with patch notes (if necessary)
[ ] Updated CONTRIBUTORS (if attribution is requested)

Tested this in our environment (ES 5.2) for a few weeks now and works great!  Looking to get rid of my fork and go back to master, but with the currently hard-coded values in this configuration file that is just not feasible.  Hopefully this sets you guys ahead and keeps your puppet offering working smoothly :-)

Thanks for the contribution @hikerspath, this looks like a useful change. Two notes:

The CLA checks failed and I couldn't find your information in our database, can you confirmed you signed the CLA?
The Travis tests are failing due to the syntax of the ERB changes - take a look at the failure output; it looks like some of the syntax may be wrong (there's at least one place where =%> should be -%>, for example)

My apologies for the tardiness here, the CLA was signed but didn't realize that I had to also confirm it in email.  Confirmation is completed.
Looking into statement issue now.

Thanks @hikerspath, the rest of those errors are unrelated to your changeset so I think we're good to go here. Thanks for you contribution!


Message from debugger: Terminated due to memory issue

I got the this while using implementing the controller, and finally, my app crashed.
Here i got the logs
Cannot find executable for CFBundle 0x101382580 </var/containers/Bundle/Application/4FFA28BA-874C-4E92-9A66-0831843BFB01/Test .app/Frameworks/VeeContactPicker.framework/VeeContactPicker.bundle> (not loaded)

This should be solved in v1


No lane changes at toll boothes

Regular and emergency vehicles do not change lanes at toll booths anymore.
The old erroneous solution (checking for lanes with "Merge" flag) was removed.
The new solution checks whether the transit node belongs to a toll booth. If that's the case lane transitions that involve lane changes are not generated anymore.

Fixes #225

I've not had time to do extensive testing but as far as I can tell vehicles no longer lane change at the toll booth.
I did see a taxi do a u-turn at the end of a toll booth road however; it arrived via the 2-lane road, and then u-turned in the transition between that road and the 4-lane toll road, the node depicted in the image below:

Not sure if it was just already on its route and pathfinding got recalculated due to me slapping a toll booth in it's path, but seeing as the U-turn for that node is disabled it was bit odd. Also, should we disable u-turn features (including in UI) for all nodes that are part of a toll booth?
Also, not sure if I need to wait longer, but so far the toll booth isn't reporting any revenue from vehicles. Vehicles aren't stopping at the booth (the 'Automated Toll' policy is not enabled). Maybe it's just too soon as all vehicles were already on the map when toll booth placed. I'll wait a bit longer.

Update: Vehicles are now stopping at the toll booth; I assume only vehicles spawned after the booth is placed will stop at it?

All vehicles should stop at the tollbooth. It may require some seconds for the vehicles to "see" the new toll booth.

I had "Customisations come in to effect instantly" enabled on General tab in mod options. It took about 10 mins before (non-service) vehicles started stopping at the toll booth. To me it seemed that anything already spawned just drove straight through without stopping.


Main Window shows up offscreen when Monitor is unplugged or screen size changes

When I open up brackets after having an external monitor connected and close it after the monitor has been disconnected, the next time I open Brackets, I can't get to the window, even after plugging the same monitor in again.
Should always open on my main desktop window.

Nominating for 1.2 -- this was in the 1.1 milestone originally but was dropped from that milestone without comment.  Seems like it should be an easy fix though.

Looks like I tried to fix this in brackets-shell PR 144 (which was so long ago I forgot about it). Issue #2180 is also related.

@redmunds it looks like your change may have gotten lost when the dark shell changes were merged.
It may be as easy as reintroducing that change to CefMainWindow::RestoreWindowPlacement()

Confirmed. Closing.


[Team 5] Enhancing existing UI and Engineer Controller

Description
Feature: Enhancing existing UI and Engineer Controller (#195)
This task deals with enhancing existing UI components including the current Turret Selection (more visually appealing), and current Turret placement mechanics. An "Engineer Controller" will also be implemented, where the user can move engineers and repair turrets with engineers. With this functionality, the game will feel more interactive for the user as they have now engineers to move around the map.
Example

Engineer Movement: Engineers will be able to move around the map.
Turret Placement: The player can buy turrets and place them on the map in exchange for currency
Turret Selection: The boss mobs will now be larger, spanning multiple lanes which allows them to be targeted by towers from multiple lanes, adding a new layer of strategy and excitement to the gameplay.

Dependencies
This ticket relies on the completion of all subfeatures (task tickets):

Turret Upgrades UI (#188)
Turret Selection Development (#187)
Engineer Controller (#184)
Turret Placement (#xx)

Milestones
Goal 1 (Sep 19): Planning and Scaffolding

[ ] Engineer Controller
[ ] Turret select screen
[ ] Turret placement

Goal 2 (Sep 30) Code Implementation and Test Design (JUnit)

[ ] Engineer Controller
[ ] Turret select screen
[ ] Turret placement

Goal 3 (Oct 2) Testing and Debugging; Integration

[ ] Engineer Controller
[ ] Turret select screen
[ ] Turret placement

Goal 4 (Oct 2) Documentation

[ ] Engineer Controller
[ ] Turret select screen
[ ] Turret placement

Completion Deadline: Oct 3
Documentation
TBA
Members
Ryan (@ryandmcneilly) (Ryan McNeilly)
Sonja (@SonjaMcNeilly) (Sonja)
Nawal (@nawal-0) (Nawal)
Jackie (@FattyHope) (Jackie)
Kevin (@Hasakev) (Kevin Luo)

In-Game build menu has been implemented, see #205 which should be merged into main soon. JUnit tests and Documentation to follow


Add support for isExpired in configuration store to gate CDN requests…

… (FF-2048)

labels: mergeable
Fixes: #issue
Motivation and Context
Customers with very short sessions (for example, chrome extensions) experience many more CDN requests than those with longer sessions. It is their interest to have more control over the rate of refreshes and balance that against being tolerant against stale flags.
For example, an owner of a chrome extension may know that during the lifetime of a financial transaction on a website where the extension is used repeatedly, a cool down period of 2 minutes will allow for a CDN request on the first open of the chrome extension to get the latest flags, while pausing CDN requests for subsequent requests in that period whenever the extension is re-opened.
We will provide an isExpired API to the ConfigurationStore and only perform CDN requests when the store declares itself as expired.
The default case will likely be that isExpired returns true always and the SDK behavior will be unchanged.
Upstream clients will implement isExpired using the available APIs on their platforms and the desired policies. Paired with these changes will be support for a cooldown period which will be a user provided SDK init parameter that governs how often a client should be stale, even when the poller executes its callback.
chrome extension
class ChromeStorage {

  constructor(private cooldownSeconds: number) {}

  setEntries(..) {

     await chrome.storage.local.set('lastUpdated', new Date())
  }

  isExpired():Promise<boolean> {
    await lastUpdated = chrome.storage.local.get('lastUpdated')

    const currentTime = new Date();
    const timeSinceLastUpdate = currentTime.getTime() - lastUpdated.getTime();
    const cooldownMilliseconds = cooldownPeriodSeconds * 1000; // Convert cooldown to milliseconds

    return timeSinceLastUpdate >= cooldownMilliseconds;
  }

}

The other classes will implement the functions in similar ways, or choose to return whatever else is appropriate.
Description
Upstream clients will implement isExpired using the available APIs on their platforms.
How has this been tested?
New unit tests
Questions for reviewers

There are several ways to "block" CDN requests and all of them have trade-offs

Ultimately the "cooldown period" upstream clients will implement is not exact.
This approach continues running the poller and it acts as the clock - cool down periods significantly shorter than the period of the poller don't make much sense. However they will still be useful for stopping the initial request from happening during repeated short sessions - such as with the use case of the chrome extension.

No new SDK parameters are added to commons

The cooldown period will be implemented in the JS SDK for the configuration stores that need it.

Does the word isExpired convey the correct meaning?

It's important to get it right so users who implement their own persistent store have an understanding of its role in the SDK's operation.

Btw don't forget to bump the version, I guess 3.1.0 is appropriate given the new functionality


TypeScript Preset 1.2.0 not working w/ HTML framework

After upgrading the TypeScript Preset from 1.1.0 to 1.2.0, we got a lot of errors (unexpected token). The TypeScript code cannot be parsed anymore. You can reproduce by cloning this repository:

Current version uses 1.1.0 => it works.
Try to upgrade to 1.2.0 => it fails.

Note that if I uses the 1.1.0 version with the new beta version of Storybook (5.3), it fails as well.
Something is missing from my configuration?

@karolisgrinkevicius Would you mind looking into this? The difference between 1.1 and 1.2 is the fork-ts-checker-webpack-plugin you added: https://github.com/storybookjs/presets/pull/56

@shilman sure, I will look into this.

So the bug actually lies in this recent commit: https://github.com/storybookjs/presets/commit/f71637c0385d6cdd452792e07bb85afb25967561. Specifically include init. Without it being initialized to an empty array it works just fine.

@darondel-yoobic thanks for providing the test repo and thanks @karolisgrinkevicius for identifying the issue. I propose instead of overwriting the existing includes (that may have come from webpack config) to append them, like it's done with other options using rest parameter.
https://github.com/storybookjs/presets/compare/master...T0MASD:append_includes

@shilman Is there any update on this issue?

@darondel-yoobic merged the fix ie #106 and released as 1.2.1. Also released 2.0.0 which includes the fix to https://github.com/storybookjs/storybook/issues/8337

@shilman Works like a charm, thanks!


DevTools: Change component properties

Description

I wanted something cool to show off on Altinn Kaffe, this allows you to modify component properties and see how it affects your layout. I think this makes the developer experience much better since you normally would have to refresh the entire page to try out small changes. Additionally, you don't have to make changes to your actual layout file and risk forgetting to change them back.
https://user-images.githubusercontent.com/47412359/232710147-9eb9ea75-4a5f-4afe-b7e0-df9ee5188e87.mov

Da mangler det bare å skrive endringene tilbake til json filene, så har vi erstattet altinn-studio.


[wip] Add Bash completion support to ReFrame

Closes #725

So far this is a bit of a poc. On Daint this can be tested with
module load reframe
. ac-reframe.sh

Currently, this supports completion of command line options:
$> reframe [TAB][TAB]
-c               --help                    --module-mappings         -R                        -t
-C               --ignore-check-conflicts  --module-path             --recursive               --tag
--checkpath      -J                        -n                        --report-file             --timestamp
--config-file    --job-option              --name                    --restore-session         -u
--cpu-only       --keep-stage-files        --nocolor                 --run                     --unload-module
(...)

files and directories for -c, --checkpath, -C and --config-file:
$> reframe -r -c cscs-checks/[TAB][TAB]
analytics/           apps/            compile/         libraries/       mch/
microbenchmarks/     prgenv/          system/          tools/

and test names given a directory or file through the -c option
$> reframe -r -c cscs-checks/apps/quantumespresso/ -n  [TAB][TAB] QuantumESPRESSO
$> reframe -r -c cscs-checks/apps/quantumespresso/ -n QuantumESPRESSO[TAB][TAB]
QuantumESPRESSOCpuCheck_large_maint  QuantumESPRESSOCpuCheck_small_maint
QuantumESPRESSOGpuCheck_large_maint  QuantumESPRESSOGpuCheck_small_maint
QuantumESPRESSOCpuCheck_large_prod   QuantumESPRESSOCpuCheck_small_prod
QuantumESPRESSOGpuCheck_large_prod   QuantumESPRESSOGpuCheck_small_prod

So far this is a bit of a poc. On Daint this can be tested with
module load reframe
. ac-reframe.sh

Currently, this supports completion of command line options:
$> reframe [TAB][TAB]
-c               --help                    --module-mappings         -R                        -t
-C               --ignore-check-conflicts  --module-path             --recursive               --tag
--checkpath      -J                        -n                        --report-file             --timestamp
--config-file    --job-option              --name                    --restore-session         -u
--cpu-only       --keep-stage-files        --nocolor                 --run                     --unload-module
(...)

files and directories for -c, --checkpath, -C and --config-file:
$> reframe -r -c cscs-checks/[TAB][TAB]
analytics/           apps/            compile/         libraries/       mch/
microbenchmarks/     prgenv/          system/          tools/

and test names given a directory or file through the -c option
$> reframe -r -c cscs-checks/apps/quantumespresso/ -n  [TAB][TAB] QuantumESPRESSO
$> reframe -r -c cscs-checks/apps/quantumespresso/ -n QuantumESPRESSO[TAB][TAB]
QuantumESPRESSOCpuCheck_large_maint  QuantumESPRESSOCpuCheck_small_maint
QuantumESPRESSOGpuCheck_large_maint  QuantumESPRESSOGpuCheck_small_maint
QuantumESPRESSOCpuCheck_large_prod   QuantumESPRESSOCpuCheck_small_prod
QuantumESPRESSOGpuCheck_large_prod   QuantumESPRESSOGpuCheck_small_prod

Codecov Report

Merging #1685 (463e981) into master (f2efc3c) will increase coverage by 0.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1685      +/-   ##
==========================================
+ Coverage   87.21%   87.31%   +0.10%
==========================================
  Files          45       46       +1
  Lines        7546     7639      +93
==========================================
+ Hits         6581     6670      +89
- Misses        965      969       +4

Impacted Files
Coverage Δ

reframe/core/fields.py
98.71% <0.00%> (-0.28%)
:arrow_down:

reframe/core/exceptions.py
94.07% <0.00%> (-0.09%)
:arrow_down:

reframe/core/runtime.py
89.63% <0.00%> (-0.07%)
:arrow_down:

reframe/core/schedulers/local.py
95.86% <0.00%> (-0.04%)
:arrow_down:

reframe/frontend/statistics.py
96.72% <0.00%> (-0.02%)
:arrow_down:

reframe/core/meta.py
100.00% <0.00%> (ø)

reframe/core/modules.py
56.62% <0.00%> (ø)

reframe/core/containers.py
100.00% <0.00%> (ø)

reframe/core/schedulers/slurm.py
53.78% <0.00%> (ø)

reframe/frontend/executors/policies.py
99.33% <0.00%> (ø)

... 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 f2efc3c...463e981. Read the comment docs.

Codecov Report

Merging #1685 (463e981) into master (f2efc3c) will increase coverage by 0.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1685      +/-   ##
==========================================
+ Coverage   87.21%   87.31%   +0.10%
==========================================
  Files          45       46       +1
  Lines        7546     7639      +93
==========================================
+ Hits         6581     6670      +89
- Misses        965      969       +4

Impacted Files
Coverage Δ

reframe/core/fields.py
98.71% <0.00%> (-0.28%)
:arrow_down:

reframe/core/exceptions.py
94.07% <0.00%> (-0.09%)
:arrow_down:

reframe/core/runtime.py
89.63% <0.00%> (-0.07%)
:arrow_down:

reframe/core/schedulers/local.py
95.86% <0.00%> (-0.04%)
:arrow_down:

reframe/frontend/statistics.py
96.72% <0.00%> (-0.02%)
:arrow_down:

reframe/core/meta.py
100.00% <0.00%> (ø)

reframe/core/modules.py
56.62% <0.00%> (ø)

reframe/core/containers.py
100.00% <0.00%> (ø)

reframe/core/schedulers/slurm.py
53.78% <0.00%> (ø)

reframe/frontend/executors/policies.py
99.33% <0.00%> (ø)

... 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 f2efc3c...463e981. Read the comment docs.

@vkarak in which terminal did you try?

@rsarm I tried on my Mac's bash. But then I started playing with argcomplete and tried to understand why it doesn't work in our case. Actually, it seems that it can work with our setup, but there is something that we still need to figure out. If you run the following Python script (using our ArgParser, slightly modified (see below)) it works:
#!/usr/bin/env python
# PYTHON_ARGCOMPLETE_OK

import argcomplete
from argcomplete.completers import EnvironCompleter

import reframe.frontend.argparse as argparse

def main():
    parser = argparse.ArgumentParser()
    parser.add_argument("--env-var1").completer = EnvironCompleter
    parser.add_argument("--env-var2").completer = EnvironCompleter
    parser.add_argument("--env-var3").completer = EnvironCompleter
    options = parser.parse_args()

if __name__ == '__main__':
    main()

And I added the following two lines in our ArgParser:
@@ -257,6 +257,9 @@ class ArgumentParser(_ArgumentHolder):
         `add_argument()` call. If no default value was specified either, the
         attribute will be set to `None`.'''

+        import argcomplete
+        argcomplete.autocomplete(self._holder)
+
         # We always pass an empty namespace to our internal argparser and we do
         # the namespace resolution ourselves. We do this, because we want the
         # newly parsed options to completely override any options defined in

Now if I try to run ./bin/reframe (with PYTHON_ARGCOMPLETE_OK), which uses the exact same parser it doesn't work. I think we need to replicate the file structure of ./bin/reframe and cli.py with completely stripped down versions and see why it can't pick the autocompletion in that case, because in principle the trick above can make it work. So it must be something in-between that is happening.


Correlation failed :: Cookie not found

if i try to open a client(for example MVCHybridBackChannel) and open up multiple tab and try to login in both tab. The first tab works fine but in case of second tab i get the following error.

Please Note:: i haven't made any change in the sample app, if you want to replicate this issue u can use the same code.
Please let me know what is the best approach in fixing this thing.

@ravi22saini, what do you mean by "try to login"? wait until it redirects to login in each tab and only after that log in each? so what you see is the normal behavior of oidc handler in asp.net. nothing specific for identity server. if that matter, it must be easy to handle in OnAuthenticationFailed client side.

@dfrunet I mean when you try to access the url of client(for example MVCHybridBackChannel), you will be redirected to login page of IDP (Till this point everything works and this i know is normal behaviour) but when i provide my credentials in first tab it works fine and i am redirected by to the main page of the client. but in second tab i get this error.
to easily replicate this scenario you can try the sample code of identity server and run any client from code, once running open the login page and duplicate the tab(you will have 2 login tabs).
Now when you try to login in first it will work and you will be redirected back normally but in second tab you will get this error.

This is the expected behavior with the Microsoft OIDC client library.

Thank you for the revert @leastprivilege. But i want to how can we avoid this behavior, we can have multiple clients(eg MVCHybridBackChannel , MvcHybridAutomaticRefresh and so on) which might be pointing to same IDP and our user can try to access all these clients together, then they will see this error which is not what anyone would expected.
Please let me know how can we handle?

It is by design - it's a security feature.

Is there a way we can solve it or override it??

Ask Microsoft what they would suggest. It is their librariy.


Add WAF sustainability guidance in FAQ

Sustainability guidance and recommendations were added to the Azure Well-Architected Framework (WAF) in the latter half of last year. As users of the Emissions Impact Dashboard are likely looking for ways to further optimise and reduce the carbon impact of their cloud workloads, I think it makes sense to link to the guidance in the FAQ.

@andreabichsel
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Test data compression for all backends

This PR enables the test data compression available in JMeter for all other backends. This is achieved by compressing testdata prior to storing LoadTest objects outside of the backend (i.e. should work for all future backends). It also externalizes the CSV splitting behaviour found in JMeter. To achieve that a new  UsesCSVTestData  property has been added to the backend interface.
Since the data is now gzipped, all testdata-using backends now need init containers to inflate back the data and make it available for the main container.
Caveat 1: Generated mock
I couldn't figure out the right mockgen  incantation that would generate a conforming mock.go  and ended up changing it manually. Just point me in the right direction and I'll fix that.
Caveat 2: CSV splitting
One may notice that I started assuming that k6 also used CSV test data and progressed to port CSV splitting for it. I later realised that JMeter is currently the only backend that support CSV test data exclusively. K6 and locust also support it, but just because they support any file type opaquely.
Maybe CSV splitting is just making the common code more complex. Just let me know if you think it really belongs inside the JMeter backend and I'll patch the PR accordingly.
Fixes #229

By the way, shoutout to @amandahla, author of the original gzip PR for the JMeter backend. Most of the code here was shamelessly copy-pasted from her.


[release-1.4] Add protocol detection timeout to mesh config

This is an automated cherry-pick of #589

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

noauth_installer_release-1.4
10d7421414f4c8bfe20e18d9b0d5177566383d73
link
/test noauth_installer_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


[Tab] Implement onClick

Description
Currently <Tabs /> accepts on onChange prop that is called when the active tab is changed.
To my knowledge (someone please tell me if I got this wrong!), there is no way to handle the case of performing an action when the user clicks on the currently active tab.
I can't find any mention to how this should behave in Tabs - Components - Material design guidelines, so I guess it's open for interpretation.
Proposal
I'd like to add an onClick prop to <Tab />. The prop accepts a function with the following signature: function onClick (event, tabIndex) { ... }. onClick should be called before onChange if the user clicks on any tab except the active tab. The event should not bubble up if event.stopPropagation() is called.
Happy to submit a PR for this if there is support.
Thoughts?
J

@brwr Can't you use the onActive property? Check the first example here
If this is not the case, could you explain it in more detail? An example might help.

@mccraveiro Right you are! Thanks :)


TIP when scheduling on Windows via Task Scheduler.

If you copy and rename the script to the .pyw extension instead of the py, you can set it up in Windows Task Scheduler and it will run silent, without opening a console window, unlike regular . py files. Windows will use PYTHONW. EXE instead of PYTHON. EXE.

Interesting. I didn't know this. Are you able to file a PR?

I've never done a PR before and will need to review how to do it.

OK, that's fine. I'll have a look at adding this to the README.

@p37307 I've just added a sentence. Can you check that is correct? I'm not familiar with Windows, so would appreciate confirmation.

Yes, that looks fine. The only other thing, that could be mentioned, is the .pyw file can be used anytime you want the script to run windowless, not just in Task Scheduler. I don't know why in my original post I tied it so strongly to task scheduler.

Great. Thanks @p37307


Separating ”Pick_Info“ Generation from the Main Rendering Pipeline

Based on our discussion in #740, I am trying to separate the generation of ”pick_info“ from the main rendering pipeline.
In my conception, the generation of ”pick_info“ should be very simple and inexpensive, and it should only be related to the geometric information of the objects. We can handle it with very simple shaders. However, during the implementation process, I found that this is not the case. For certain objects, the ”pick_info“ is strongly related to the shader logic (fragment shader) of the object.
The biggest issue is that I noticed many objects' ”pick_info“ contains fields similar to face_coord (f32).
Are they used together with face_index to calculate vertex_index? If so, there should be a simpler implementation.
Apart from object_id and vertex_id, what other information do we expect to be included in the "pick_info"?

As a user story: We use the "color" of the object to report certain properties of the object. For example after shading and lighting, what is the  object unaffected by any other overlays.
One aspect where we hit a hiccup, was in trying to pick a fully transparent object (i know, strange, but think if you have something "hidden" that you want to reveal on hover)
https://github.com/pygfx/pygfx/blob/dfa74246e5c9e7ec813c33649ba2af4e9be62e79/pygfx/renderers/wgpu/engine/blender.py#L150
The logic here is useful when you want to avoid expensive computation for objects that are "probably really transparent", but it "hurt" our application (we ended up setting the opacity really low, and the alpha of the color of the line really low, so eventually it appears effectively transparent but tricked the pick logic in rendering the object we wanted to click on).

In mature game engines, picking, collisions, etc use proxy geometry instead of the visual scene. Scene objects are approximated with simple convex shapes (boxes, spheres, hulls) and picking is performed by intersecting a ray with these proxy shapes. That way you can resolve picking without depending on rendering at all. Unfortunately that is a whole different ball game and not implemented here.


Add zypper plugin

Provides the artifact-registry zypper plugin for resolving URLs to repositories hosted in GCP Artifact Registry.
To use this plugin, zypper repository URIs must be specified as plugin:artifact-registry?project=PROJECT&location=LOCATION1&repository=REPOSITORY&service_account_json=PATH.
To test on Apple M2 Max MacBook Pro (running Sonoma 14.0) against a repository containing x86_64 RPMs:

Cross-compile ar-token for linux/amd64:
$ env GOOS=linux GOARCH=amd64 go build -o ar-token cmd/ar-token/main.go

Initialize docker environment via colima:
$ colima start -a x86_64 -t vz --vz-rosetta

Run an opensuse/tumbleweed container with working tree mounted at /data:
$ docker run -ti --rm -v $(pwd):/data opensuse/tumbleweed /bin/bash
Unable to find image 'opensuse/tumbleweed:latest' locally
latest: Pulling from opensuse/tumbleweed
fc18dad756fe: Pull complete
Digest: sha256:f65e67248adef8ead6f238befc878f4680b0f82bf952e4022360623062f4f366
Status: Downloaded newer image for opensuse/tumbleweed:latest
85670253b6f3:/ # cd /data
85670253b6f3:/data #

Install ar-token to /usr/libexec:
85670253b6f3:/data # install -p -m 0755 ar-token /usr/libexec/

Verify service account key works:
85670253b6f3:/data # /usr/libexec/ar-token --service_account_json=/data/service-account.json >/dev/null
DEBUG: Obtain credentials using service account JSON
DEBUG: Got a token

Install python311-zypp-plugin (the plugin uses python3):
85670253b6f3:/data # zypper in python311-zypp-plugin

Install the plugin:
85670253b6f3:/data # install -p -m 0755 zypper/artifact-registry.py /lib/zypp/plugins/urlresolver/artifact-registry

Add repository:
85670253b6f3:/data # zypper ar 'plugin:artifact-registry?project=stellar-code-398917&location=us-central1&repository=devops-dev-rpm&service_account_json=/data/service-account.json' devops-dev

Verify by listing repository packages:
85670253b6f3:/data # zypper pa -r devops-dev
Loading repository data...
Reading installed packages...
S | Repository | Name  | Version          | Arch
--+------------+-------+------------------+-------
  | devops-dev | gedit | 40.1-150400.2.15 | x86_64
  | devops-dev | nano  | 7.2-1.4          | x86_64

Plugin works for tumbleweed (15.5 base) but does not work with Leap 15.4 due to the use of functools cache, which is not available in Python 3.6 (system python version for 15.4).

I built RPM version e.g. 20231010.00 in an opensuse/leap:15.4 container as follows:

docker run -ti --rm -v $(shell pwd):/data opensuse/leap:15.4 /bin/bash
zypper in -y rpmbuild 'go>=1.17' golang-packaging
cd /data && rpmbuild --define "_topdir $(pwd)" --build-in-place --define "_version $(date '+%Y%m%d').00" -bb packaging/zypper-artifact-registry-plugin.spec

Resulting RPM installs and works in opensuse/tumbleweed and opensuse/leap:15.4, opensuse/leap:15.3, opensuse/leap:15.2, opensuse/leap:15.1, and opensuse/leap:15.0. E.g.:

docker run -ti --rm -v $(pwd):/data opensuse/leap:15.1 /bin/bash
zypper in -y --allow-unsigned-rpm /data/RPMS/x86_64/zypper-artifact-registry-plugin-20231010.00-g1.x86_64.rpm
zypper ar -cf 'plugin:artifact-registry?project=stellar-code-398917&location=us-central1&repository=devops-dev-rpm&service_account_json=/data/service-account.json' devops-dev
zypper pa -r devops-dev

I confirmed the code changes work on Leap 15.4 after resetting my python environment back to the system 3.6 install. I was able to build and install the plugin rpm, refresh zypper repos, and access a test registry in GCP using a service account key.


Consulting call in call transfer has no audio

In a setup with a sip bridge, there is no audio on the consulting call leg within a call transfer
Steps to reproduce the behavior:

The element iOS client is active in foreground
A call from a PSTN number<PHONE_NUMBER>) via sip bridge is coming in and is accepted
This call has good audio
The user now presses the transfer button, putting the PSTN user on hold (hears hold music)
The user dials a second PSTN number on the transfer dial pad and connects with “consult first” active
The second PSTN user gets and accepts the call
This consulting call has no audio at all

https://github.com/matrix-org/matrix-ios-sdk/pull/1738 offers a way to fix it for matrix applications that need it.


Frnic contact create

Hello,
I'm working on the frnic extension. This merge request is mostly to gather guidance: am I doing it right or not?
Also, is this something that would be included in instant-epp or would I better keep it in my private branch.
Thanks for reading this.

I think this part, the contact create part, is ok.

Thanks, this is looking great!


Service?

Why do you have \Service\Datatables; in the imports header of UsersDataTable.php it is not doing anything but throwing errors

@phillipmadsen, You should use yajra\Datatables\Services\DataTable; and not  \Service\Datatables;. The service approach is still under development but it is working as intended. Have you seen this tutorial on how to use it?

Going thru the tutorial should fixed the issue.


fn: applications should be aware of reserved writable space

Similar to FN_MEMORY, we pass FN_TMPSIZE to function config.

@kmjohansen For time being, it's not configurable. Hardcoded to /tmp.

I understand that this approach here is limited, but this is consistent with FN_MEMORY, FN_CPU. These are passed in as part of call configuration structure, for example, for json:
https://github.com/fnproject/fn/blob/master/api/agent/protocol/json.go#L27
TMPFSSIZE is part of Route API and it's a single entity. When volumes are implemented, we'd need to extend/supplement this. Right now, TMPFSSIZE is either unlimited (0), or set to a specific limit.
I'm ok with holding off on this until we decide on a better strategy as well.

My major concerns here are two-fold.  The first is the vast proliferation of environment variables.  It seems like it might be easier to encode configuration information into a runtime neutral format that any FDK can parse and return to the application.  The second is the set of issues around providing static definitions for resources that are dynamically available.  If, for example, we provided an interface that allowed the caller to get both the max and available transient storage in a single call, that would satisfy me.  The concern here is that any caller that depends upon the environment variable when the availability of the resource is dynamic is broken by definition.

@kmjohansen These are actually properly/formally formatted in json/cloud-events protocol as function-config. (They only have to be env variables in cold-functions, which has no structured protocol. Because of this, I keep calling these env variables and I've accidentally caused some confusion.) FDKs actually parse these and offer them as config data.
I also agree with dynamic nature of the resource. But these are to be treated as "function configuration" not as a way to dynamically determine how much memory or /tmp space a function has at a given time. In other words, these tell the function which "shape" it is currently running on. We expose FN_CPU, FN_MEMORY along with configuration set in that route, which is also merged with the application configuration. In other words, we communicate almost all configuration params in a route to the function:
https://github.com/fnproject/fn/blob/master/api/agent/call.go#L142

Based on ongoing discussion:
https://github.com/fnproject/fn/issues/1106
we might eventually hide these: cpu/tmpsize from users. But in case we don't, I'd like to keep the triplet: cpu/mem/tmpfs consistent & merged in & exposed.


An error during nucmer running

When i used nucmer to make self-alignments of genome sequences,  the program was terminated after a error reported:
terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
################
I do not know what happened to these analyses. But some of them ran well. Can anyone fix this above problem?
By the way, I found the nucmer failed to call multiple threads sometimes when I used the option -t 10, although there are 128 threads of 64 cores in my server.
Thanks.
Shuai

It seems that there is not enough memory?
128 threads of 64 cores is a big server,  but there was other task/process used a lot of memory?

Same problem. How did you guys manage it?
Thanks
F


Update library_generation.sh

The relative path for the "Fix permission" section has been modified. There were additional nested directory (libmicroros directory) in the address which has been removed. Also the name of "include" directory has been changed to the "microros_include" according to the line 64.

@mergify backport main foxy


Basic native push

cc @vivangkumar @zimbatm
TODO:

[ ] tests
[ ] validations

Did you have a look at vivan's implementation in the ruby lib?

Yep. Thats my guideline. Todos yet to be done though
Sent from my iPhone

On 6 Jul 2016, at 09:29, zimbatm<EMAIL_ADDRESS>wrote:
Did you have a look at vivan's implementation in the ruby lib?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Does it mean you'll make a separate class and the hostname configurable too?

Yeah I will
Sent from my iPhone

On 6 Jul 2016, at 09:33, zimbatm<EMAIL_ADDRESS>wrote:
Does it mean you'll make a separate class and the hostname configurable too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


change line21 '燒毀vs燒毀圖表' to '燃尽vs燃尽图表'

[ x] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[ x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@fedelico
Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍 We're happy to accept these changes and look forward to future contributions.


your current branch does not have any commits yet

Version
0.4.0
Details
Should prevent git exception In a clean new repo, when there are no commits.
Steps to reproduce

Step 1: Create a new repo git init
Step 2: Install Husky dotnet husky install
Step 3: Add pre-commit hook dotnet husky add pre-commit -c "dotnet husky run"
Step 4: Add dotnet-format staged task

{
   "tasks": [
      {
         "command": "dotnet",
         "group": "pre-commit",
         "args": [ "dotnet-format", "--include", "${staged}" ],
         "include": [ "**/*.cs", "**/*.vb" ]
      }
   ]
}

Temporary workaround
Adding an empty commit before Step 3 can solve the problem. git commit --allow-empty -m "first commit"

Should be fixed via PR #34, in v0.4.1


Renew of the documentation

I had some difficulties with getting started and had to search re-read large parts of the documentation to understand how some things are working.
That's why I sat down and thought about how to improve the documentation and here are the changes:

Restructures the docs into more categories, splits 'making games' into multiple documents
Use Grunt to compile all assets and moves them into new directory
Styles are now handled by Sass
Update to Bootstrap 4
Replace Prettify.js with highlight.js
Updates the base templates

Previews

Frontpage
Making Games page

Precompiled assets
At the moment some of the assets like styles.css and JS dependencies are removed from version control. If it's necessary to have them available in the repo, we can commit them again.

I really hope that all changes are fine. If not, just leave a comment and I will correct. 😃

It's amazing that you're putting so much work into this. Is there any way you and break this into multiple PRs? There's too much to look at here.
Examples:

a pr to move the assets
a pr to use scss
a pr to update .md files
a pr to replace prettify.js with highlight.js

etc...
Also a few things

I don't build the docs. In other words if you're updating .md files please only update those. Don't update the corresponding html files.

Please stick to the style as is. Do not remove blank lines, don't add or remove spaces, don't go changing coding styles please. Thanks.

Yeah I really like this project, it's astonishing how well the system works and I know how important help is.
I will try to split this up into multiple PRs tomorrow.
If HTML files should not be updates would it make sense to completely remove them from the repository?
Also, do you have an example where the code style was changed? Can't remember all changes..

It's hard to read the diffs and I didn't go searching for all places but for example in changelist.md the diff appears to show all blank lines removed and a few other files. In writing-games.md moved from makinggames.md the controller.js section has been refomatted similarly in other places. In Gruntfile.js spaces have been added after function. Names have been changed to have under_scores etc...

Ok I will look into this.

What about the HTML files? Should they be removed from the repo if they should not be commited anyway?


Plugin broken in Obsidian version 0.15.0

Before Submitting: Double-check that you are running the latest version of the plugin. The bug might have already been fixed 😄

Describe the bug
In version 0.15.0 of Obsidian, released today, the way links are opened from within a sidebar has changed.  Instead of opening the link in the main pane, it now opens the link in the sidebar.
Unfortunately, this affects the calendar plugin -- clicking on a date now replaces the calendar widget with the daily note.  And because the sidebar is narrow, the daily note is opened in far too narrow a pane, making it very hard to read.
Steps to reproduce

Make sure you're using Obsidian version 0.15.0 with the Calendar plugin installed.
Show the calendar in the right sidebar
Click on a date in the calendar with an existing daily note.
See that the daily note is opened in the right sidebar, replacing the calendar view.

Expected behavior
The Calendar plugin should open the daily note in the centre panel rather than in the right sidebar.
Screenshots
n/a
Environment (please specify)
n/a
OS
Mac OS X.
Obsidian Version (e.g. v0.10.6)
0.15.0
Theme (if applicable):
n/a

same question

Yeah I ran into same issue. The only solution is to click on the main editor to switch the focus there, then click on the date in Calendar Plug-in for it to work.

Ditto. I noticed the same behavior.

Yup, same for me.

Same here 😔 !
I couldn't find a way to go around this new buggy behavior 😞 ...

Yeah I ran into same issue. The only solution is to click on the main editor to switch the focus there, then click on the date in Calendar Plug-in for it to work.

That works for switching between existing daily notes ... Not creating new ones (from what I can see) 😞

Yeah I ran into same issue. The only solution is to click on the main editor to switch the focus there, then click on the date in Calendar Plug-in for it to work.

That works for switching between existing daily notes ... Not creating new ones (from what I can see) 😞

Thanks for the report! This will be fixed by Obsidian in the upcoming 0.15.1 version.

Is it possible to back rev obsidian to get notes working again? I depend on it and am not sure how quickly this will get fixed by Obsidian.

@OogieM : Obsidian v.0.15.1 has been released few hours ago 😊 ... I didn't had the time to test properly everything but this specific calendar bug seems to be fixed 😊

The incompatibilities with v.0.15.0 should be fixed in the newest version of Obsidian. If not, please let me know.

Not fixed as of Obsidian v.0.15.1 or at least I'm not seeing what I expect.  The pane (I'm using Sliding panes) where the notes open up seems random. It's not always the one that is currently open, sometimes it's the one before that. I haven't been able to replicate the set of things I do for when it fails so I'm not much help for debugging at the moment. But it's not every time and it very well could be a user error but it never did that before.

I'm using Sliding panes

Sliding Panes might be the culprit here 🤔 ... Have you tried to disable it and use calendar to see if it works normally @OogieM ? 🤔
I mean, the brand new "focus on side pane" feature which came with Obsidian 0.15+ seems to have impacted other plugins too (I just reported a bug with Templater and there's another one with Breadcrumbs)... and each time, it seems like the "buggy" plugins doesn't know where to do what needs to be done anymore (it doesn't know where to focus)... At least, this is how my non-dev' mind interpret the troubles I've encountered with Obsidian v.0.15+ 😇 .
But still, without using Sliding Panes and after the release of Obsidian v.0.15.1, Calendar seems to work as it used to 😊 .

OK More info here. I'm using periodic notes. If I have 2 panes available and click in the right most pane then click on yesterdays date in the calendar in the right sidebar the note properly shows up in the rightmost pane. Then click in the leftmost pane and click to create the new note for today. The new note is created in the rightmost pane. Before this update it would create it in the left pane.
Once that happens even clicking in the left pane does not move the display slider so that I see the whole note. It's still set with the right note having the focus and the whole display. So not sliding ike they used to do. I have already sent theinfo to  the developer of Sliding Panes but tam reporting here sicne it may be a conflickt between the 2 plug-ins.


Default project/rendermanger requires textures-power-2 none

At the moment, the default rendermanger requires the "textures-power-2" PRC variable to be set to "none" to avoid viewport issues. This should either be set in the default main.py, or handled somehow in the default rendermanger.py. At the very least, this should be documented since it is very confusing to new users.

Fixed by ea4a0ade6a7eec94c6c5a23cbabeb44019973fb9


chore(demo) add file used in demos

The original file; https://bit.ly/echo-server is no longer valid, hence creating one of our own, next to the already existing httpbin example file

What this PR does / why we need it:
In several demos the file we used is invalid and an extrenal gist, here we can own and control the file appropriately, such that attendees can properly replay the demo's themselves

The original file; https://bit.ly/echo-server is no longer valid

Can you elaborate on what you mean by no longer valid?
It worked fine for me right now.

apiVersion: apps/v1beta1 no longer works, the beta1 was dropped, so should now be: apiVersion: apps/v1

We already have this in the master branch:
https://github.com/Kong/kubernetes-ingress-controller/blob/master/deploy/manifests/dummy-application.yaml

Closing this. Please re-open if needed.


Support projects that want to ban @NullUnmarked in some way

We view @NullUnmarked as being a transitional step. I doubt any new codebase would have cause to use it, nor would a codebase that already got itself migrated want to face backsliding.
So, I think that banning @NullUnmarked whenever possible will be a practice we heartily recommend. Yet it seems we're leaving everyone on their own to rig up some ad-hoc way to ban it on their own.
(Admittedly this is only half of the puzzle: such projects would equally wish for a way to ensure @NullMarked IS always used on every new (module/package/class, their preference). So what I list below are only partial solutions.)
One pretty severe idea is to banish @NullUnmarked and future others like it to a separate artifact! The package might be something like org.jspecify.migration.*. This of course lets the build configuration control whether to let it in or not.
Another idea is @NullMarked(overridable = false). (If we wanted that to be the default behavior (?), we'd have to do this by 1.0; that's the only reason I conservatively set this issue as milestone=1.0.)
Since we're listing ideas, I guess I'll add @BanWithinThisScope(NullUnmarked.class)...

My assumption had been that support for this wouldn't come from JSpecify per se. I tend to think of something like a presubmit or pre-commit hook or, if there's support from a checker, support that's more configurable than we'd be able to offer. Let me see if I can figure out what was underlying that assumption....
First, the separate artifact is quite interesting! I probably wouldn't go that far, perhaps partially because "Add these two dependencies for the full set of nullness annotations" sounds like an easy thing to make fun of, even if one of the artifacts won't be necessary for some projects :) Oh, and then it has to go in a separate package... and maybe we'd want a separate artifact for the "legacy" annotation for each of our other domains besides nullness.... Plus, there are build tools that don't enforce "strict deps," so, as soon as you have a dependency that uses @NullUnmarked, then everyone else can use it. Put all together, that's worse than I expected when I started writing this paragraph. The thing I'm actually planning to harp more on is the configurability argument.
One sort of configurability argument is this: @NullMarked(overridable = false) and @BanWithinThisScope(NullUnmarked.class) work if you can put those on every package (#34, #30, #221, sigh) or on every module (and my understanding is that module adoption isn't quite there yet). If you want to rely on that, you're probably going to want a way to enforce that people include those annotations. That means writing external configuration to your checker or the other "enforcers" in your development environment. And if you're willing to do that, then you can just as well use those same tools to straight-up ban @NullUnmarked.
Then there's the main sort of configurability argument: How many people will be sure that they'll never use @NullUnmarked? I'm sure there will eventually be a good number of people in that position, but I would expect a common other need to be "no @NullUnmarked except in this set of locations that Team X has audited." That's not something that a JSpecify annotation is likely to support well.
Another possibility is that some people will want warnings for @NullUnmarked and others will want errors. That is of course the kind of configuration that a checker can offer for @NullMarked(overridable = false) and @BanWithinThisScope(NullUnmarked.class). But it's another reason to feel that JSpecify could solve only a portion of this problem, likely having to answer a number of questions about potential features along the way. So we could end up with @NullMarked(overridable = false, butAllowSuppressionOfThat = true), and then our rules need to specify what to do with @NullMarked(overridable = false, butAllowSuppressionOfThat = false) inside that scope, and... it's probably all manageable, but it doesn't feel worth pursuing to me unless I'm being overly pessimistic about the usefulness of the feature.

I personally don't think we have a strong need for this in the JSpecify spec.  I agree with @cpovirk that users will want configurability of these bans, and needing to implement such configurability within JSpecify-compliant checkers will add complexity.  IMO, clear documentation about the intent of @NullUnmarked is good enough, and bans can be enforced by other linters / checkers.

I think we can rule out the separate migration-support artifact:

It won't play well; will make JSpecify look more like a "pain" in general.
When people hit a snag in migration, we want it to be easy to reach for @NullUnmarked.

I think we can rule out @NullMarked(overridable = <boolean>):

It's only a partial solution anyway.
It doesn't actually communicate information about the code, which is JSpecify's purpose.
It seems to have no good choice for default value.

I think we can rule out @BanWithinThisScope(NullUnmarked.class):

It's only a partial solution anyway.
It doesn't actually communicate information about the code, which is JSpecify's purpose.
It lacks release pressure: it could always be added compatibly later. In such cases there is little sense in trying to predict its value.

In general, any scheme for how projects can enforce annotation usage policies:

Can't logically be purely annotation-based
Doesn't need to be married to JSpecify in any way

This issue was a bit of a time-waster, but if the arguments above seem valid then I at least see some potentially reusable principles here.

Current decision: This feature is not required for JSpecify 1.0.
Proposal for 1.0: Finalize the current decision. If you agree, please add a thumbs-up emoji (👍) to this comment. If you disagree, please add a thumbs-down emoji (👎) to this comment and briefly explain your disagreement. Please only add a thumbs-down if you feel you can make a strong case why this decision will be materially worse for users or tool providers than an alternative.