In the scenario text file, when I use landuse+ but do not use biomass-harvest, I get a stack trace error (error below)

Reported by Matthew Duveneck
It looks like the updates that were made in the last couple weeks to Biomass Harvest 3.0 and PnET-Succession have fixed both the partial harvesting problem in biomass harvest that I found AND the partial harvesting problem in landuse+. I have tested this and show partial harvest removal successful in both disturbance extensions.
There is a problem though

In the scenario text file, when I use landuse+ but do not use biomass-harvest, I get a stack trace error (error below).  When I run biomass harvest AND landuse+, I don't get an error and everything seems to run. As a hack, I can run biomass Harvest with zero biomass removed and then turn on landuse+ successfully.

2015-10-13 13:53:00,973 - LANDIS-II 6.1 (official release)
2015-10-13 13:53:00,990 -
2015-10-13 13:53:01,118 - Loading scenario from file "HEM_scenario_pnet_orig.txt" ...
2015-10-13 13:53:01,222 - Initialized random number generator with user-supplied seed = 4,357
2015-10-13 13:53:01,222 - Loading species data from file "NE_species.txt" ...
2015-10-13 13:53:01,256 - Loading ecoregions from file "HEM_ecoregions.txt" ...
2015-10-13 13:53:01,283 - Initializing landscape from ecoregions map "HEM_314_single_cell_eco.img" ...
2015-10-13 13:53:01,309 - Cell length = 100 m, cell area = 1 ha
2015-10-13 13:53:01,311 - Map dimensions: 1 row by 1 column = 1 cell
2015-10-13 13:53:01,323 - Sites: 1 active (100.0 %), 0 inactive (0.0 %)
2015-10-13 13:53:01,337 - Loading PnET-Succession extension ...
2015-10-13 13:53:01,394 - OutputSite (1, 1) ecoregion eco314
2015-10-13 13:53:01,405 - Initializing PnET-Succession version <IP_ADDRESS>
2015-10-13 13:53:01,478 - Eco SoiltWiltPntFieldCap(mm)FC-WPPorosity
2015-10-13 13:53:01,479 - eco314 SALO65.12118150.858685.73742360.9474
2015-10-13 13:53:01,498 -    Registering Data:  TimeOfLastSuccession.
2015-10-13 13:53:01,499 -    Registering Data:  Shade.
2015-10-13 13:53:01,501 -    Creating Dispersal Neighborhood List.
2015-10-13 13:53:01,502 -    Dispersal:  NeighborRadius=5050, CellLength=100, numCellRadius=50
2015-10-13 13:53:01,509 - Spinning up biomass
2015-10-13 13:53:01,511 -    Loading initial communities from file "HEM_initial_community.txt" ...
2015-10-13 13:53:01,526 -    Reading initial communities map "single_cell_IC_val10.img" ...
2015-10-13 13:53:01,699 -    Registering Data:  Succession.BiomassCohorts.
2015-10-13 13:53:01,699 -    Registering Data:  Succession.WoodyDebris.
2015-10-13 13:53:01,699 -    Registering Data:  Succession.Litter.
2015-10-13 13:53:01,700 -    Registering Data:  Succession.AgeCohorts.
2015-10-13 13:53:01,700 -    Registering Data:  Succession.CohortsPnET.
2015-10-13 13:53:01,703 - Loading Land Use 1.0 extension ...
2015-10-13 13:53:01,715 -   Loading parameters from landuse_plus_single_cell.txt
2015-10-13 13:53:01,768 - Initializing Land Use...
2015-10-13 13:53:01,769 -    Registering Data:  LandUse.AllowHarvest.
2015-10-13 13:53:01,771 -   Opening log file "land-use/site-log.csv"...
2015-10-13 13:53:01,779 -   Reading map "land-use8S_0.img"...
2015-10-13 13:53:01,797 -     Forest (1)
2015-10-13 13:53:01,797 - Loading Output-PnET extension ...
2015-10-13 13:53:01,813 - Running Output-PnET ...
2015-10-13 13:53:01,843 - Current time: 1
2015-10-13 13:53:01,844 - Running PnET-Succession ...
2015-10-13 13:53:01,892 - Current time: 2
2015-10-13 13:53:01,892 - Running PnET-Succession ...
2015-10-13 13:53:01,909 - Current time: 3
2015-10-13 13:53:01,909 - Running PnET-Succession ...
2015-10-13 13:53:01,924 - Current time: 4
2015-10-13 13:53:01,925 - Running PnET-Succession ...
2015-10-13 13:53:01,941 - Current time: 5
2015-10-13 13:53:01,941 - Running PnET-Succession ...
2015-10-13 13:53:01,956 - Running Output-PnET ...
2015-10-13 13:53:01,957 - Current time: 6
2015-10-13 13:53:01,957 - Running PnET-Succession ...
2015-10-13 13:53:01,973 - Current time: 7
2015-10-13 13:53:01,973 - Running PnET-Succession ...
2015-10-13 13:53:01,989 - Current time: 8
2015-10-13 13:53:01,989 - Running PnET-Succession ...
2015-10-13 13:53:02,006 - Current time: 9
2015-10-13 13:53:02,007 - Running PnET-Succession ...
2015-10-13 13:53:02,021 - Current time: 10
2015-10-13 13:53:02,022 - Running Land Use ...
2015-10-13 13:53:02,023 -   Reading map "land-use8S_10.img"...
2015-10-13 13:53:02,045 - Internal error occurred within the program:
2015-10-13 13:53:02,046 -   Object reference not set to an instance of an object.
2015-10-13 13:53:02,046 -
2015-10-13 13:53:02,047 - Stack trace:
2015-10-13 13:53:02,050 -    at Landis.Library.BiomassHarvest.PartialCohortCutter.Cut(ActiveSite site, CohortCounts cohortCounts)
at Landis.Extension.LandUse.LandCover.RemoveTrees.ApplyTo(ActiveSite site)
at Landis.Extension.LandUse.Main.b__2(Site site, LandUse newLandUse)
at Landis.Extension.LandUse.Main.ProcessInputMap(ProcessLandUseAt processLandUseAt)
at Landis.Extension.LandUse.Main.Run()
at Landis.Model.Run(ExtensionMain extension)
at Landis.Model.Run(String scenarioPath, IUserInterface ui)
at Landis.App.Main(String[] args)

Version 1.1 appears to have resolved this issue.  Simulations run with Land Use, but not Biomass Harvest do not throw any errors.


Name wrong in the error code

Highlighted in Red..Should be DEVELPOER Instead of EVELOPER
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3f3073d5-376e-44af-6057-79019456b3f5
Version Independent ID: bf455a28-2792-e1ce-ba03-e86ded9947cc
Content: ADAL to MSAL migration guide for Android - Microsoft identity platform
Content Source: articles/active-directory/develop/migrate-android-adal-msal.md
Service: active-directory
Sub-service: develop
GitHub Login: @mmacy
Microsoft Alias: marsma

@AyushKumar85 Thank you for your inputs . We will engage with the backend team to get this reviewed and update the same. It may take some time though  .

@AyushKumar85 Thanks for the feedback. We have engaged the content development team for further investigation, they will verify and perform necessary changes in the document as needed.

#label:"doc-bug"
Hi @shashishailaj and @vipulsparsh, can one of you remove the doc-enhancement label from this issue? It is a bug.

@AyushKumar85 Thanks for the notification on this! The typo has been fixed in https://github.com/MicrosoftDocs/azure-docs-pr/commit/320f206c07f52b4d476f7b2617e97fb829d0e154.


Org creation using new command not updating orgs.yml

CF-MGMT version:
Version: [1.0.31], Commit: [eb65902ff6615bf2181f921abd132570bc0d3061]
OS:
Windows 10 Enterprise  64 bit OS
Issue:
When I ran the below command, It is creating org but failing to update "orgs.yml" with the new org name.
cf-mgmt-config.exe org /config-dir:testdir /org:test_org
Work Around:
I was able to use the deprecated command option and was able to create and org and found orgs.yml is updating.
cf-mgmt-config.exe add-org --config-dir=testdir --org=test_org

Fixed with - https://github.com/pivotalservices/cf-mgmt/releases/tag/v1.0.34


Multi-Stream Consumption

Currently one realtime Pinot table only consumes from one stream. For use cases in which multiple existing streams are the input source for one Pinot table, the workaround is to use stream processors to read from different streams, perform necessary transformations, and write the output of all transformed events into another stream. Then one realtime pinot table can be set up to consume from that output stream. This requires maintaining two systems: the stream processor jobs and also pinot realtime tables. It would be nice to add capabilities to pinot realtime tables to consume from multiple topics.

I'm working on a design doc for this and will share it here soon.

@sajjad-moradi this is a great idea. Lemme know if you had any update on this issue.


getting an error while building opensycl

I was installing opensycl using llvm version 15.0.7 on x86 and after make install command , it shows the error below mentioned.
Please help to rectify the same.
make install
[  2%] Built target opensycl-common
[ 31%] Built target opensycl-clang
[ 32%] Linking CXX shared library libllvm-to-backend.so
/bin/ld: cannot find -lLLVM
clang-15: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [src/compiler/llvm-to-backend/libllvm-to-backend.so] Error 1
make[1]: *** [src/compiler/llvm-to-backend/CMakeFiles/llvm-to-backend.dir/all] Error 2
make: *** [all] Error 2

Hi,
If you are building with the SSCP compiler enabled (this is the case by default) you need an LLVM that provides dynamic libraries, i.e. an libLLVM.so or libLLVM-<version>.so. Do you have such a file?
If not, you can either:

build LLVM in the way described here: https://github.com/OpenSYCL/OpenSYCL/blob/develop/doc/install-llvm.md#only-if-you-wish-to-compile-llvm-from-source-not-recommended
Disable the SSCP compiler using -DWITH_SSCP_COMPILER=OFF.

I was installing opensycl using llvm version 15.0.7 on x86 and after make install command , it shows the error below mentioned.My previous error has been resolved but now getting new error.
Please help to rectify the same.
Building CXX object src/runtime/CMakeFiles/rt-backend-cuda.dir/cuda/cuda_allocator.cpp.o
/aniket/prakash/garade/OpenSYCL/src/runtime/cuda/cuda_allocator.cpp:143:15: error: no member named 'type' in 'cudaPointerAttributes'
if (attribs.type == cudaMemoryTypeUnregistered) {
~~~~~~~ ^
/aniket/prakash/garade/OpenSYCL/src/runtime/cuda/cuda_allocator.cpp:143:23: error: use of undeclared identifier 'cudaMemoryTypeUnregistered'; did you mean 'cudaMemoryTypeDevice'?
if (attribs.type == cudaMemoryTypeUnregistered) {
^~~~~~~~~~~~~~~~~~~~~~~~~~
cudaMemoryTypeDevice
/usr/local/cuda/include/driver_types.h:833:5: note: 'cudaMemoryTypeDevice' declared here
cudaMemoryTypeDevice = 2  /< Device memory */
^
/aniket/prakash/garade/OpenSYCL/src/runtime/cuda/cuda_allocator.cpp:153:35: error: no member named 'type' in 'cudaPointerAttributes'
out.is_optimized_host = attribs.type == cudaMemoryTypeHost;
~~~~~~~ ^
/aniket/prakash/garade/OpenSYCL/src/runtime/cuda/cuda_allocator.cpp:154:24: error: no member named 'type' in 'cudaPointerAttributes'
out.is_usm = attribs.type == cudaMemoryTypeManaged;
~~~~~~~ ^
/aniket/prakash/garade/OpenSYCL/src/runtime/cuda/cuda_allocator.cpp:154:32: error: use of undeclared identifier 'cudaMemoryTypeManaged'; did you mean 'cudaMemoryTypeDevice'?
out.is_usm = attribs.type == cudaMemoryTypeManaged;
^~~~~~~~~~~~~~~~~~~~~
cudaMemoryTypeDevice
/usr/local/cuda/include/driver_types.h:833:5: note: 'cudaMemoryTypeDevice' declared here
cudaMemoryTypeDevice = 2  /< Device memory */
^
5 errors generated.
make[2]: *** [src/runtime/CMakeFiles/rt-backend-cuda.dir/cuda/cuda_allocator.cpp.o] Error 1
make[1]: *** [src/runtime/CMakeFiles/rt-backend-cuda.dir/all] Error 2
make: *** [all] Error 2

Which CUDA version are you using? You might have to update your CUDA SDK.

we dont have cuda , ROCm. we have to install it only on x86 architecture and we are also  skipping cuda dependencies during cmake during installation and  still we are getting this error. Please guide for installation on x86 without cuda , ROCm.

Please provide the commands you use to configure and compile the project. The error is triggered in the CUDA backend, so the CUDA backend was enabled. cmake must have found some CUDA installation (or remnants of one?) on your system.

cmake -DCMAKE_INSTALL_PREFIX=/path/to/OpenSYCL/build -DCLANG_EXECUTABLE_PATH=/path/to/bin/clang++ -DCLANG_INCLUDE_PATH=/path/to/include/clang/ -DCMAKE_CXX_COMPILER=/path/to/bin/clang++ -DBOOST_ROOT=/path/to/build
This was the command used and cmake does find a CUDA installation but while building CUDA dependencies were ignored

Given the lack of feedback I assume that this issue was resolved with the argument in the last comment. If not, please reopen the issue.


[move-prover] Report: updating introduction (3)

Motivation
Updating the introduction  content as it was still based on the Nov '20 state of affairs.
Closes: #8852
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Existing CI testcases

/canary

:sunny: Canary successful

/land


Use Hash of Song Byte Data

hash data from byte array using SHA256 and then convert ensuing byte array into string of designated length

Can you remove any bits of unused code (including commented code, for loops that do not do anything, unused methods, etc)? Also try extracting methods. Otherwise, LGTM.

Also this article on git commit messages might be worth a read.


Pure Domain Layer

@Andrusha26 commented on Tue Apr 28 2020
Is it okay to inherit from INotification, which cause dependency on MediatR lib? How we can avoid it?

Сведения о документе
⚠ Не вносите правки в этот раздел. Это необходимо для связывания страницы сайта docs.microsoft.com с вопросом на GitHub.

ID: d432d5bb-24a7-3bec-1e17-910c8129226e
Version Independent ID: e41af96d-f015-a8e0-4449-7a508d7bccc8
Content: События предметной области. Проектирование и реализация
Content Source: docs/architecture/microservices/microservice-ddd-cqrs-patterns/domain-events-design-implementation.md
Product: dotnet-architecture
Technology: microservices
GitHub Login: @nishanil
Microsoft Alias: nanil

@srvbpigh commented on Tue Apr 28 2020
Hello, @Andrusha26
Thank you for your feedback.
We are actively reviewing your comments and will get back to you soon.
Kind regards,
Microsoft DOCS International Team

Hi @CeciAc,
Well, as usual, that's an absolute "it depends" 😉.
It might be a requirement in some context or just an opinionated decision, so there's no black and white here, IMHO.
How to avoid it? The only way I can think of would be to create your own abstraction, which means more complexity or, at the very least, more code you have to write.
I see MediatR as just another library that I like and use a lot, BTW, because it makes my life as a developer much easier.
For this kind of decisions I compare the business value I have to deliver, with the cost of:

Developing my own abstraction.
Developing my own implementation.
Developing and maintaining the related test cases.
Discovering and handling the corner cases.
Fixing bugs and adding features (and tests).
The opportunity cost of fixing bugs and adding features, That is, what you'd be doing if you weren't fixing bugs and adding features to you library.
Document all of the above for the developers that will come after me.

Of course you can create your own abstraction and have an absolutely pure domain layer, you just have to consider the associated costs and risks. If that makes sense, then go for it, the customer will understand the hours dedicated to develop that as a feature.
Hope this helps.

thank you so much, for the response, make sense

Closing this issue as @mvelosop has addressed this. Please feel free to reopen if you have more questions.


Fix volume binding name bug (#1561)

#1561
Before this fix, Acorn was expecting the user to use the name of the PersistentVolume in Kubernetes when binding an existing volume into a new app, for example:
acorn run -n myApp -v pvc-447f1f93-5b81-417c-a938-918d6f68e7ed:vol .

PV names in k8s are very long and we don't even expose them to the user, so this needed to change.
With this fix, the user must now use the public volume name when binding an existing volume. For example:
❯ acorn volume
NAME           APP-NAME       BOUND-VOLUME   CAPACITY   VOLUME-CLASS   STATUS     ACCESS-MODES   CREATED
voltest.data   voltest.data   data           1G         local-path     released   RWO            32m ago

❯ acorn run -n myapp -v voltest.data:vol .

Acorn will use labels to find the corresponding PersistentVolume and then reassign it to the new app. As that happens, the public name of the existing PV gets changed (along with the other labels).
One other change from this PR is that cross-project volume binding is no longer possible. It probably never should have been possible in the first place.
Checklist

[x] The title of this PR would make a good line in Acorn's Release Note's Changelog
[x] The title of this PR ends with a link to the main issue being address in parentheses, like: This is a title (#1216). Here's an example
[x] All relevant issues are referenced in the PR description. NOTE: don't use GitHub keywords that auto-close issues
[x] Commits follow contributing guidance
[x] Automated tests added to cover the changes. If tests couldn't be added, an explanation is provided in the Verification and Testing section
[x] Changes to user-facing functionality, API, CLI, and upgrade impacts are clearly called out in PR description
[ ] PR has at least two approvals before merging (or a reasonable exception, like it's just a docs change)

The logic should be good now. Going to work on adding more test cases though.

No context comments:
A user should only be able to bind a PV that has the acorn managed label.
Cross project binding should definitely not be supported right now.
If the volume name changes after binding that’s weird. Can it just always have the original name?

If the volume name changes after binding that’s weird. Can it just always have the original name?

It's not the name of the PV that changes, but the value of the acorn.io/public-name label on the PV. This value becomes the same thing that is shown to the user when they list volumes by running acorn volume.

Ready for review again. Changed the logic based on our discussion earlier today, so that all apps can only bind volumes that are managed by Acorn and part of the same project as the app - no way to "adopt" a volume from the outside until we add that as a different subcommand (unless you manually throw labels onto the PV).

Converting to draft and unassigning all reviewers. I just remembered that I still need to make sure that binding volumes inside of the Acornfile is properly locked down. My top priority issue changed so I will need to come back to this later.

From talking with Darren, it looks like there isn't any other way to bind volumes currently besides using -v. So I believe that all these changes are sufficient.


Feature/extend localization

String localization using Calendar locale property added to the calendarView. Also it is possible to localize menuView using the same calendar object.

Hey @elsesiy thanks for your comments.
I've changed them and pushed now. Would you take a look?
Thanks

Looks good now, thanks!


Adds ability to customize resizing of images across platform

Closes #1453

Now we are able to minimize the code at one place.
Admin is able to choose different size of images across platform.

@istride can we consider getting this into the build which upgrades to Wagtail 2.15?

@cbunicef The Wagtail upgrade is ready to be deployed, so it is too late. It is important to get this feature correct because it affects all images across the site. When this feature is ready, we will merge it and then schedule a release.

Thanks @istride, this is the type of feedback I was looking for. Let's please be sure that this is in the next build after the upgrade.

I would recommend not working on this until a couple of issues are resolved:

Image width options: I'm not sure whether these are guesses which might need to change as soon as the app is deployed - I would like us to be certain.
Is this feature the best way to solve the problem or would use of <picture> be better? I don't think we should do both.

@sheralim012 This has been merged without my approval. I would have appreciated the chance to verify that the changes I asked for have been made correctly. It was important to me that the values for the IMAGE_SIZE_PRESET setting be a name rather than a number, to make it very clear that there is a very limited range of valid values - clearer than a single comment in 'base.py'.
I'm not going to insist on more changes at this time.


Update MaskResult.kt

Fixed the selection that was leading to crash if the selection was higher than the length of the text.
Fixes #27

@santalu is this fix going to get in a version?


Expand on items.dat Header

Hi,
I like this project, however I've noticed you're missing some bytes on the header of items.dat here: https://github.com/H-pun/growtopia-docs/blob/74ad222389ec9d509f9dbdd9e75f6a28a75efdc2/items_dat/README.md?plain=1#L9-L14
The order goes:
items.dat version (1 byte)
1 unknown byte
item count (2 bytes) (byte + byte << 8 to read count)
2 unknown byte
I could open a PR to fix this if you'd like, just let me know.

Ahhh yes I didn't know that, I'm currently completing types, there are lots of em. As for this PR are welcome


gccgo: bogus index out of bounds

gccgo rejects to compile the following program:
package a
var a = ""[:]

go.go:2:11: error: string index out of bounds

gcc version 6.0.0 20150702 (experimental) (GCC)

@paranoiacblack


Figures fail to render

Description
Figures render partially, and 'leak' their content into the rest of the HTML. Shown below with screenshot.
(Optional:) Please add any files, screenshots, or other information here.

(Required) What is this issue most closely related to? Select one.
Figures
Internal issue ID
37d71e89-60f0-4681-8ac2-cce2dc0fcf4d
Paper URL
https://arxiv.org/html/2404.00344v1
Browser
Firefox/132.0
Device Type
MacOS

see also issue #2729, similar issue there


Use default Commanders Act logging

As a developer I would like to initialize Commanders Act with the least amount of setup code. Currently some debugging must be disabled but really shouldn't.
Acceptance criteria

TCDebug configuration has been removed.

Tasks

[x] Check whether the linked issue has been fixed.
[x] Remove TCDebug logging level setup. Check that no events are logged to the console.

The issue has been addressed. We should be able to implement this task starting with the next Commanders Act SDK release.

SDK updated in #487. We can now remove the Commanders Act logging setup entirely and use the default behavior.


Try linear regression and MLP on PCs instead of raw inputs for FOCI data

Find no improvement in performance: Both models can handle multi-collinearity in input data.

Solves #6


Drop node 4,6 add node 12

FWIW, there's no specific code changes that actually eliminate node 4 or 6 compatibility at the moment, but I don't see a point in testing on unsupported versions.


how can I get pbtxt file from binarypb file

Hello
how can I get pbtxt graph file from binarypb

Hi @mostafamdy, Could you please share your use case with respect to the above request. Thanks!

I have code from github for android  solution and I want to use Visualizer mediapipe tool    to know what happen inside the graph but the visualizer don't support binary graph so can I convert binary graph to pbtxt format

This can be done but that need more work. There is an opensource protobuf printing tool.
protobuf API: protobuf::TextFormat, you need to build you own converter with that API.
(https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.text_format)
(https://medium.com/@nathantnorth/protocol-buffers-text-format-14e0584f70a5)

hi,
is it possible to reopen this issue?
I'd like to visualize a binarypb file and i cannot convert it in pbtxt.
@mostafamdy how did you write your own converter?
thank you

Hi @elYeodeol ,
Did you get a chance to check this closed issue https://github.com/google/mediapipe/issues/885.

Hi @elYeodeol ,
Did you get a chance to check this closed issue https://github.com/google/mediapipe/issues/885.

I checked this issue. I tried to recreate the 'pose_web.binarypb' (file loaded when you launch the pose solution page of mediapipe). I want to recreate it bc I want to change the subgraph to modify options. But ive got the wasm error "SolutionWasm$loadGraph" when i used my custom pose_web.binarypb file instead of the original one. So maybe i didn't recreate it perfectly..

Hi @elYeodeol ,
Do you still have error?

Any help with #885 will be appreciated, just posted more info about how models look after conversion

Hey,
I am still trying to get a .pbtxt file from a binarypb file.
Specifically, I would like to convert the graph pose_web.binarypb into pose_web.pbtxt
Any help would be appreciated,
Thank you


I can't install react-native.  Unknown command: "init$1$1"

Description
I copied the installation command from the official website. I have previously set up the environment, everything is fine. But the installation command gives an error.
npx @react-native-community/cli@latest init AwesomeProject

I understand that probably react-native is not to blame here, but I no longer know where to go for help. The error is not even Googled!
Steps to reproduce
npx @react-native-community/cli@latest init AwesomeProject
React Native Version
0.76.1
Affected Platforms
Build - Windows
Output of npx react-native info
no react-native

Stacktrace or Logs
⠹ Downloading template

error An unexpected error occurred: Command failed with exit code 1: npm init -y
Unknown command: "init$1$1"

To see a list of supported npm commands, run:
  npm help.

$ node -v
v22.11.0
$ npm -v
10.9.0
$ npx -v
10.9.0

I had same problem.
I reinstalled NPM, Nodejs. Then I tried this one in the C: folder, It worked for me.
npx @react-native-community/cli@latest init SampleApp --version 0.76.0

I advice you to restart your device after doing the reinstallation phase

I had same problem.
I reinstalled NPM, Nodejs. Then I tried this one in the C: folder, It worked for me.
npx @react-native-community/cli@latest init SampleApp --version 0.76.0

Yup this sounds like the right solution @valery-lavrik
If that doesn't help, could you open your same issue here:
https://github.com/react-native-community/cli/issues
The code where the failure happens is inside the Community CLI so if there is a bug there, it should be fixed inside the Community CLI code

I found the reason.   The problem was that during the installation I was distributing Internet from my mobile phone. As soon as I switched to normal wi-fi, everything worked immediately. I don't understand how this is connected....

@valery-lavrik I advice you to connect both your phone and your computer to the same WiFi network during development


--watch option works strangely with .only()

After adding .only() and removing it, --watch doesn't work correctly. After removing .only from a test case, I expected mocha should test all test cases, but it did not test any case at all.
steps to reproduce

mocha test.js --watch  with following code.

// test.js
// Sample code to reproduce
describe('test with --watch', () => {
  it('should be ok', () => {
    //
  });
  it('should be ok too', () => {
    //
  });
});

// output
  test with --watch
    ✓ should be ok
    ✓ should be ok too

  2 passing (8ms)

Add .only to the first test.

// output
  test with --watch
    ✓ should be ok too

  1 passing (2ms)

Remove .only from the first test.

// output
  0 passing (1ms)

Expected Behavior
After removing .only, all tests should be tested again.
Environmet

OS: windows 10 / Ubuntu 16.04.1
node : 6.3.0
mocha : 3.0.2

#2327

Same problem here, glad its already reported.
mocha 3.0.2, node 6.2.1

Would accept a PR to fix this if it's not too complicated.  We don't really have the resources to maintain --watch.
Suggested workaround: use a third-party package to watch files and re-execute mocha

I don't have enough knowledge of mocha internal to fix this problem, but I want to share what I have checked.
I changed bin/_mocha as followed to check runner's state.
// https://github.com/mochajs/mocha/blob/master/bin/_mocha
// line: 355
  function loadAndRun() {
    try {
      mocha.files = files;
      runAgain = false;
      runner = mocha.run(function(){
        runner = null;
        if (runAgain) {
          rerun();
        }
      });
      // ADDED for testing
      console.log('in loadAndRun():', runner.total);
    } catch(e) {
      console.log(e.stack);
    }
  }

When I run test with mocha 2.5.3, .only affected runner.total. Without .only, runner.total was 2 and with .only runner.total changed to 1. But, on mocha 3.0.2. .only didn't affect runner.total and it was always 2.
I think runner.total means the total number of test cases, and it should be changed when .only is used, but it is not. So the problem is not from --watch, but from .only's incorrect internal behaviors.

@boneskull About 3rd party tools you're suggesting. Can you please point me some tool which might work with mocha.opts? Because all examples i see on the internet imply using some task runners like gulp-mocha which do not accept mocha.opts.

@dobryanskyy Maybe watch? It has also a handy little CLI tool. 🤓

@boneskull you don't have the resources to maintain watch, yet you update the rest of mocha without removing it? i'd rather remove a neglected feature when it's broken than leave it as is.

@gurdiga thanks a lot, watch did work for me.

However, it's a bit slower than using --watch switch from mocha

I've just run into this as well, but I'm using Mocha's api programmatically, so this issue is not limited only to the --watch option.
In my case I've written a little test runner script that uses Mocha's api specifically to work around problems with --watch. The script uses chokidar to watch files and is calling mocha.addFile() and mocha.run() when files change. So far it's working, picking up moved/added/deleted files (--watch doesn't work in these cases). But I've realized this issue with .only is still present.
In looking through the codebase, I noticed interfaces/common.js sets mocha.options.hasOnly = true in a few places. But nowhere in the codebase is it ever set to false. If one calls mocha.run() a second time after removing .only from tests, this option will still be true, and so no tests will be run. I think mocha.options must be global to Mocha itself. Even creating a new instance (with new Mocha()) does not seem to change anything.
A fix here may be to initialize mocha.options.hasOnly to false, perhaps when a new Mocha instance is initialized? I think I've managed to work around this problem in my script by doing new Mocha({hasOnly: false}), and passing it in with mocha options. However, this feels a little hacky since hasOnly seems more like an internal state variable, rather than an option that should be passed into the Mocha constructor.

I suspect that some of the issues experienced with --watch may actually be problems with Mocha breaking in various ways on multiple calls to .run(). Mocha seems to be relying on the process exiting to do its cleanup. Running tests multiple times in the same process (exactly what you'd want to do for good file watch functionality) causes problems. For example, another issue I needed to work around was clearing the require cache in order to get tests to run a second time (see #1938).
I guess the question is whether running tests multiple times in the same process is something that should be supported by the api. Sane file watch functionality is a prime example where this is useful. The suggestion given to replace --watch by re-running the mocha command each time a file changes is not ideal due to it being pretty slow, especially when using something like babel.

@bartels I also noticed that hasOnly is never updated to false. In my pullrequest https://github.com/mochajs/mocha/pull/2544 I detach the outdated state of hasOnly and evaluate on each iteration if there is any test or suite with only.
I just wonder if we should fix the hasOnly state of the rootSuite. However we could also try to remove the hasOnly of the rootSuite. What are your opinions?

@davidspinat Your pull request does seem like the best way to fix this. I'm testing it out and seems to work well in my case. Might be good for @boneskull to take a look too. I'm not all that familiar with mocha internals.
Looking at this a bit more, your pull request seems to have removed the need for setting options.hasOnly at all since the check is now handled on each run by looking at the tests & suites themselves. I think the hasOnly option was only being set globally so it would then be passed along to the runner, which your pull request removes the need for, as far as I can tell.
I tried removing all instances of options.hasOnly from lib/interfaces/common.js and lib/mocha.js. All tests are passing, and I haven't noticed any problems. I would say cleaning up the obsolete hasOnly option entirely make sense.

Whether that particular PR makes the cut or not, let's make sure we get one source of truth on only-ness. Something similar was done with whether a given test or suite is skipped/pending, if I recall correct.

@bartels @ScottFreeCode thank you for having a look.
@bartels I agree that it would make most sense to just remove the hasOnly state. When it comes to maintainability holding and updating states like that is just too dangerous as they might get out of sync quite easy.
@ScottFreeCode from my point of view these kind of states are very hard to maintain and should be avoided. However I tried to evaluate the situation and agree, that only-ness should be handled the same way as skipping and pending. Since thats more an architecture discussion, I would rather stick to my proposal https://github.com/mochajs/mocha/pull/2544 which seems to be a clean fix for the reported bug. Maybe we could have further on a separate discussion about how we could improve holding and updating the suite/test state in mocha.
Should I extend my PR to also remove all related hasOnly? What are your opinions?

I have no strong opinions one way or the other on separating the fix into immediate and underlying/architecture phases, or into "eliminate use of .hasOnly as an extra property" and "remove the now-unused property" phases. Well, I would like them in separate commits at least so we can look at the two steps in the history, but if they're separate commits I'd be fine having them in the same PR. Others might think differently, however; /cc @mochajs/core
That being said, ideally if we could both fix the immediate issue and set up some kind of test for it so we know if the issue comes back (preferably using the programmatic API in a manner similar to --watch as regards this issue, rather than using --watch directly*), that would help ensure that when we do review the architecture we don't break anything with further attempts to improve it. @bartels Do you think you could adapt some of your --watch-replacing code, minus the workaround for the .hasOnly problem (since that should be fixed), to create a test case?
*The more tests we get using the programmatic API, especially for --watch-like behavior, the closer we get to being able to use the programmatic API with third-party watcher tools so --watch isn't needed!

If d22cae831ee3684e6556651763c142174d72eb80 fixes this, I would love to see this merged!


(MAINT) Bump puppet-agent to 112d479 and puppet submodule

This commit bumps our puppet-agent dependency for CI to 112d479, latest
full OS matrix build that passed puppet-agent CI.  The prior build,
6e35df8, only included a partial OS matrix and so was not suitable for
the full OS matrix puppet-server nightly job runs.
This commit also bumps our puppet submodule dependency to 2256ed8 in
order to pick up a fix for the cached_catalog_remediate_local_drift.rb
test for ubuntu-1404.

Do we need to merge this down to stable too ?

@KevinCorcoran We will, yeah.  How soon are you thinking we'll be able to get #928 merged?  I'd definitely prefer to start targeting some of these PRs that we know we'll want in for the 2.3.X releases to the "stable" branch but we'll obviously need that other PR to land first.


Occasional NotFoundException when attempting to pull messages from subscription immediately after creation.

I am utilizing this library as part of an effort to build out a test automation framework. The basic aim is to create a wrapper class around the already existing Subscriber functionality to abstract out the lower level details and make creating, polling, and deleting subscriptions as easy as possible. A plausible test scenario is as follows:

Create a pull subscription on a preexisting topic and project
Create an instance of the subscriber and start
Trigger some workflow/task that should publish to subscribed topic
Pull messages from the subscriber and validate the response
Delete the subscription and cleanup

Java version: 1.8.0_201
google-cloud-pubsub version: 1.102.1
With my implementation, I am able to create the pull subscription, start the subscription, receive x incoming messages, stop, and delete the subscription. However, it seems like something is off because occasionally I will receive a NotFoundException due to the resource (projects/{project}/subscriptions/{subscription}) not being found. My immediate thought was that the resource is sometimes unavailable because I am not giving it any time in between creating and starting the subscription, and thus it's possible the subscription had not completed the creation process before I started polling. However, it seems like this issue is linked more to the repetition of the workflow, rather than the time between calls. In other words, I am more likely to see this error every other execution, as opposed to it being related to the amount of time I wait after creating the subscription to begin polling. I'm not a java expert and have referenced a lot of examples to implement my wrapper class so I'm afraid that I'm doing things against the general paradigms that this library was built upon.
Code example
Things to note about my naive PubSubSubscriber implementation

One instance of PubSubSubscriber per subscription. Allow for multiple instances to be running asynchronously
Each instance of PubSubSubscriber has its own Subscriber attribute, and a queue (I'm using LinkedBlockingDeque). I've read that it's important to use a queue that is thread safe but I'm not exactly sure how much this matters if I'm creating a new instance of it per instance of the PubSubSubscriber. Is it simply incorrect to be creating an instance of LinkedBlockingDeque per PubSubSubscriber if the queue is already designed to be thread-safe?
I have implemented a static method in this class called createPullSubscription(). Since it is static, it doesn't require an instance to be created in order to call this method; does that cause issues if I create an instance after creating the pull subscription so that I can subscribe and pull from the newly created subscription?

Basic constructor looks something like this:
  public PubSubSubscriber(String projectId, String subscriptionId)  {
    this.PROJECT_ID = projectId;
    this.SUBSCRIPTION_ID = subscriptionId;
    this.messages = new LinkedBlockingDeque<>();
      ProjectSubscriptionName subscriptionName = ProjectSubscriptionName
          .of(this.PROJECT_ID, this.SUBSCRIPTION_ID);

    this.subscriber = Subscriber.newBuilder(subscriptionName,
          ((PubsubMessage message, AckReplyConsumer consumer) -> {
            this.messages.offer(message);
            consumer.ack();
            })
          )
        .build();

The createPullSubscription method (which resides in the same class) looks like:
  public static void createPullSubscription(String projectId, String topicId, String subscriptionId)
      throws IOException {

    ProjectTopicName topicName = ProjectTopicName.of(projectId, topicId);
    ProjectSubscriptionName subscriptionName = ProjectSubscriptionName.of(
        projectId, subscriptionId);

    try (SubscriptionAdminClient subscriptionAdminClient = SubscriptionAdminClient.create()) {
      Subscription subscription = subscriptionAdminClient.createSubscription(subscriptionName, topicName,
          PushConfig.getDefaultInstance(), 0);
    } catch (ApiException e) {
      System.out.println(e.getStatusCode().getCode());
      System.out.println(e.isRetryable());
    }

Test code in main method:
public static void main(String... args) {
  PubSubSubscriber.createPullSubscription("my-project", "my-topic", "my-test-sub");
  PubSubSubscriber ps = new PubSubSubscriber("my-project", "my-test-sub");

  // this simply calls ps.subscriber.startAsync().awaitRunning();
  ps.start();

  // Receive Messages on the subscription based on a key and value to look for (my own method that uses poll())
  JsonArray messages = ps.getMessages("id", testId);

  // this simply calls ps.subscriber.stopAsync().awaitTerminated();
  ps.stop();

  // also my own static method to delete
  PubSubSubscriber.deleteSubscription("my-project", "my-test-sub");
}

Stack trace
Feb 03, 2020 4:40:02 PM com.google.cloud.pubsub.v1.StreamingSubscriberConnection$1 onFailure
SEVERE: terminated streaming with exception
com.google.api.gax.rpc.NotFoundException: com.google.api.gax.rpc.NotFoundException: io.grpc.StatusRuntimeException: NOT_FOUND: Resource not found (resource=projects/my-project/subscriptions/my-test-sub).
	at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:45)
	at com.google.cloud.pubsub.v1.StreamingSubscriberConnection$1.onFailure(StreamingSubscriberConnection.java:238)
	at com.google.api.core.ApiFutures$1.onFailure(ApiFutures.java:68)
	at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1039)
	at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
	at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1165)
	at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:958)
	at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:749)
	at com.google.api.core.AbstractApiFuture$InternalSettableFuture.setException(AbstractApiFuture.java:95)
	at com.google.api.core.AbstractApiFuture.setException(AbstractApiFuture.java:77)
	at com.google.api.core.SettableApiFuture.setException(SettableApiFuture.java:52)
	at com.google.cloud.pubsub.v1.StreamingSubscriberConnection$StreamingPullResponseObserver.onError(StreamingSubscriberConnection.java:174)
	at com.google.api.gax.tracing.TracedResponseObserver.onError(TracedResponseObserver.java:103)
	at com.google.api.gax.grpc.ExceptionResponseObserver.onErrorImpl(ExceptionResponseObserver.java:84)
	at com.google.api.gax.rpc.StateCheckingResponseObserver.onError(StateCheckingResponseObserver.java:86)
	at com.google.api.gax.grpc.GrpcDirectStreamController$ResponseObserverAdapter.onClose(GrpcDirectStreamController.java:149)
	at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
	at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
	at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
	at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:700)
	at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
	at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
	at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
	at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:399)
	at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:521)
	at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:66)
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:641)
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$700(ClientCallImpl.java:529)
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:703)
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:692)
	at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
	at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: com.google.api.gax.rpc.NotFoundException: io.grpc.StatusRuntimeException: NOT_FOUND: Resource not found (resource=projects/my-project/subscriptions/my-test-sub).
	at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:45)
	at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:72)
	at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:60)
	at com.google.api.gax.grpc.ExceptionResponseObserver.onErrorImpl(ExceptionResponseObserver.java:82)
	... 25 more
Caused by: io.grpc.StatusRuntimeException: NOT_FOUND: Resource not found (resource=projects/my-project/subscriptions/my-test-sub).
	at io.grpc.Status.asRuntimeException(Status.java:533)
	... 24 more

Any additional information below

The error doesn't occur during instantiation of the class for a new subscription. It occurs when I attempt to pull messages. (this.messages.poll())
I've tried modifying flow control settings, parallel pull counts, making state checks, etc. Nothing seems to change the outcome.
The only "pattern" I've been able to identify is that it rarely happens twice in a row, and it's pretty common for it to happen every other run, but sometimes it will work 2-3 times consecutively before crashing with that error. The resource and project names for the generated subscription have remained unchanged for each run.

Is there something obvious I'm missing here? Is it possible I'm not shutting down threads somehow? I'm using startAsync() and stopAsync() to start and stop and have even tried awaiting for Running/Terminated states. Is there anything else regarding the resource status that I can continuously check for before attempting to connect to a resource to ensure that the resource is available? Any and all help (including ripping apart my naive implementation) is appreciated.
Thanks!

@jtanningbed, thanks for reaching out about this issue - I will attempt to reproduce the same error and get back to you

@jtanningbed, I have looked into the issue that you are seeing.   It is likely that you need to wait for a longer period of time before you delete a subscription and immediately try to re-create that subscription.  Here are a couple of things that you can try:

Wait a few minutes between calls to your createPullSubscription method (~3 minutes)
Use a different subscription name every time.  The base name can be the same "my-test-sub", but you can then append a unique identifier onto the end of the subscription name each run (timestamp, number that increases on each call, etc.)


seems hs.hotkey.bind has changed.

hi, thx for your config.
I upgrade harmmerspoon recently.  and Find cursor will move twice for each press.
I  make a little change, the problem was fixed.
hs.hotkey.bind(mods, key, pressFn, nil, pressFn)	=> hs.hotkey.bind(mods, key, pressFn, nil, nil)

== my bad.


[PE-D][Tester B] DG: Error in the ModelClassDiagram

A doctor doesn’t have a DOB, Gender field, but the diagram suggests they do. Likewise for patient and Specialty field.
Instead of adding these fields to the Person class and leaving them nullable, ensure they remain unique to the specific subclasses.

The Person class includes only common fields (name, phone, email, address, tags).
The Doctor and Patient classes each inherit from Person.
The Doctor class has a dedicated association with Speciality, while the Patient class has associations with DateOfBirth and Gender

However, based on the code, since Person class already has all fields and creating a Doctor simply sets the DOB and Gender fields to be null, the Person part is correct. Then, the Doctor and Patient should just have the inheritance arrow to Person, without any extra arrows to Specialty, DOB and gender since this is already implied by the inheritance.

Labels: severity.Low type.DocumentationBug
original: EthanLoww/ped#9

Closing this issue as this was how it was actually implemented in the code.


add a couple of minor changes to 134

This pull request just adds a period to the end of a sentence that's missing one, and adds some words to fix grammatical errors, in 134. How can we invoke sum in sum.js from index.js?.

Closing due to inactivity


Some stack variables can't be renamed

In the example below I was able to rename rbp - 0x90 to input, but I can't rename rbp - 0xd0. Additionally, the names don't match up with the stack offsets. For instance, one line reads mov dword [rbp-0xa0 {var_a8}], 0xf0f082be.

The binary is here. I'm using Binary Ninja Version 1.1.922 Personal (Build ID 4d40ebb7).

Duplicate of #797

You're right. Closing.


Figure texts and small plot bugs

Figure texts placeholders added for all the graphs as well as fixing a bug connected to the haplotype graph that made it possible to insert invalid individual id and breakiing the system.

This should probably be merged before we do the UI testing


Add missing measurements units

:scroll: Description
Not as nice as SentryMeasurementUnit.duration.milliSecond as some other languages, but it's a limitation of the enum type in Dart in the current min. supported version, we can refactor that in the future.
Changing it to a plain String would be a breaking change and would have a poor UX because we'd need to document all the possible values.
The current limitation is that you can only set the unit with one of the enum values, which is well covered for most of the cases.
In case somebody wants to use their own metric unit, it's currently not supported, we can refactor this and bump the Dart version if needed.
:bulb: Motivation and Context
Reason: https://github.com/getsentry/sentry-java/pull/2260#discussion_r984387110
:green_heart: How did you test it?
:pencil: Checklist

[X] I reviewed submitted code
[X] I added tests to verify changes
[ ] I updated the docs if needed
[X] All tests passing
[X] No breaking changes

:crystal_ball: Next steps

Codecov Report
Base: 90.26% // Head: 95.55% // Increases project coverage by +5.28% :tada:

Coverage data is based on head (fad9d52) compared to base (812d379).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1033      +/-   ##
==========================================
+ Coverage   90.26%   95.55%   +5.28%
==========================================
  Files         114        2     -112
  Lines        3556       45    -3511
==========================================
- Hits         3210       43    -3167
+ Misses        346        2     -344

Impacted Files
Coverage Δ

dart/lib/src/sentry_measurement_unit.dart

dart/lib/src/sentry_envelope_header.dart

dart/lib/src/transport/noop_transport.dart

dart/lib/src/client_reports/client_report.dart

...lib/src/invalid_sentry_trace_header_exception.dart

dart/lib/src/diagnostic_logger.dart

...event_processor/deduplication_event_processor.dart

dart/lib/src/sentry_envelope.dart

dart/lib/src/protocol/mechanism.dart

dart/lib/src/protocol/sentry_trace_header.dart

... and 102 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Message view improvements (smooth text stream, autocorrect, etc.)

Creating this initial issue for myself. Going to see if I can find some time this week (or next) to submit some PRs.
Really appreciate the product!

Smooth text stream (smooth animate on scroll up)
Autocorrect for message TextField
Optional haptics on message receive? (similar to ChatGPT for iOS)

Update on this, it seems that scrolling doesn't work when the cursor is hovering over rendered markdown

Hi guys, thanks for reporting

Fixed scrolling on markdown code
Autocorrect on iOS

These fixes will be available later today or tomorrow!
Smoothness issue seems to be problem with SwiftUI framework. I will see if there's any workarounds, but in different issue.


tb.write does not allow for negative values

This is not a deal breaker, but it would be nice to have a way to write on -10, 2 for example.
I was trying to write just half of a box, something like this:
(0,0)
`

|12345678|
|12345678|

12345678

`

Becomes something like this at (-4,0):

`

45678|
45678|

45678

`

I might take a look sometime, seems easy enough. You could also give it a go and raise a PR if you like 😄


fix BodyFilter.replaceJsonStringProperty issue with empty values

Description

BodyFilter BodyFilters#replaceJsonStringProperty corrupts json.
Motivation and Context

When BodyFilters#replaceJsonStringProperty filters json containing empty properties to replace it corrupt json. Example:
Filter:
final BodyFilter unit = BodyFilters.replaceJsonStringProperty(Collections.singleton("foo"), "XXX");

Input:
{"foo":"","bar":"public"}

Output:
{"foo":"XXX"bar":"public"}

Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.

Thanks for your pull request :tada:! I released the fix as 1.9.1 to central.


[bn] Localization of ephemeral-container.md

[bn] Localization of ephemeral-container.md
Fixes: #45729
Resolves : #44993
Resolves : #45729

/lgtm


KOB Email

To raise a new Pull Request, the following prerequisites need to be met. Please tick before proceeding:

[ ] a conversation was held in the appropriate media hyperledgerkochi channel.
[ ] a Github Issue was opened for this feature / bug.

This addresses Issue #XXX-Link-to-Approved-Issue-XXX

@sweta-dotcom Please do address the review comments. Let us know if you have any queries.


[BUG] Add repo description

Coming from opensearch-project/opensearch-plugins#92.
Each plugin has a short descriptive text blurb that says what it does: this appears in plugin-descriptor.properties (OpenSearch plugins) or package.json (OpenSearch Dashboards plugins), as well as on the project website's "source" page and in the "About" section of every repo. These were created one-by-one over the years as plugins were created, so looking at them all together now it would be hard for somebody new to the project to use these to understand what the plugins do.

Updated description with "Provides OpenSearch geospatial features"  Please reopen if you have something else you think would be better :)


Lacking Minute Issue

First off, wonderful tool you've made here, and thank you for it.
I'm finding that when my start- and end-time are all zeros and in the PM, only dates and no times are produced in the resulting ICS file.
Example:
cal_single.addEvent( 'Title', 'Description and such...', '4/20/2014 6:00 pm', '4/20/2014 7:00 pm');

Results in...
DTSTART;VALUE=DATE:20140420
DTEND;VALUE=DATE:20140420

Whereas...
cal_single.addEvent( 'Title', 'Description and such...', '4/20/2014 6:01 pm', '4/20/2014 7:01 pm');

Results in...
DTSTART;VALUE=DATE:20140420T180101
DTEND;VALUE=DATE:20140420T190101

Hitting a deadline right now, so I'm defaulting end times to 30 minutes after the start times.  Once I'm done with this, I'll try to go in and isolate exactly where this is occurring in the code.  I'll let you know what I find.
Testing done in Chrome 34.0.1847.116 m.

I have the same problem - and an related strange issue:
cal.addEvent("title", "", "", new Date(2017,0,1,14,30,0), new Date(2017,0,1,15,0,0))
will create
DTSTART;VALUE=DATE:20170101T143030

Why 14:30:30 - where do the 30 seconds come from?
BR Matthias
(using: https://rawgithub.com/nwcell/ics.js/master/ics.deps.min.js)

Hi ,
I am facing the same Issue.
Any idea how to fix this.

Sadly this repo seems to be not maintained anymore. Last commit 2014.
You could look at it's forks - maybe someone fixed it already.
Fork it yourself and fix it ;)
Or use an other better maintained repo. :/

I've applied some PRs recently.  I believe some of them fixed this issue.


use config hash for dependent configs

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@hzxuzhonghu @howardjohn @sschepens WDYT about this?

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
7e22c3eb16e4831fe348a15ef9d42dbcc97c2d24
link
true
/test lint_istio

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.

https://www.avira.com/en/blog/md5-the-broken-algorithm#:~:text=MD5%3A The fastest and shortest,%3A 1.47*10-29.
MD5: The fastest and shortest generated hash (16 bytes). The probability of just two hashes accidentally colliding is approximately: 1.47*10-29.
/lgtm

MD5 is 16bytes but we're storing it in a uint64 which is only 8bytes so we're actually increasing the possibilities of collision.

MD5 is 16bytes but we're storing it in a uint64 which is only 8bytes so we're actually increasing the possibilities of collision

I do not think that is big issue given how rare the collisions can be but we change easily change the type if we agree on the direction.

Why not use the pointer option another PR had? That is simpler, cheaper (no need to hash), and no collision, and same size?
I would really really like to see concrete numbers on this PRs so we don't just have to guess about performance

We all agree that current model is not scalable. I do not have strong opinion on this vs. other PR. My motivation for choosing this approach is sidecar config dependencies is similar to this and it worked there (there are more computations in sidecar code compared to xds cache Add). To have similar pattern for same problem.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
144222125e22b25726d1e94a846741de2c7534d0
link
true
/test unit-tests_istio

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.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
144222125e22b25726d1e94a846741de2c7534d0
link
true
/test unit-tests_istio

lint_istio
144222125e22b25726d1e94a846741de2c7534d0
link
true
/test lint_istio

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.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f39651e6edd535f25662b36d0cf32596708b8791
link
true
/test unit-tests_istio

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.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f39651e6edd535f25662b36d0cf32596708b8791
link
true
/test unit-tests_istio

lint_istio
f39651e6edd535f25662b36d0cf32596708b8791
link
true
/test lint_istio

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.


Declare Plugin

What Jenkins plugin enables the functionality in the Manage System> Cloud setting?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: da0d4345-e27a-8fa8-7d26-9c0c8920a4e8
Version Independent ID: 1287b94b-5240-5d8e-cde8-741e6a6ea561
Content: Use Azure Container Instances as a Jenkins build agent
Content Source: articles/container-instances/container-instances-jenkins.md
Service: container-instances
GitHub Login: @neilpeterson
Microsoft Alias: nepeters

@bearrito - I believe the plugin is named Azure Container Agents. Can you try that out and let me know.
Thanks

This is correct.

@bearrito We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


New release (v0.6.0)

I am in the process of implementing the changes for the PDS Migrator in our PHP code.
There were some minor issues for which I'll open an MR.
I noticed we are a bit behind in creating a new release. The latest tag is v0.5.1 from November last year.
In the meantime, 117 commits have been made to main, mostly fixes from December to February.
The same goes for pdsinterop/php-solid-auth#v0.6.1. Both pdsinterop/php-solid-crud#v0.3.0 and pdsinterop/flysystem-rdf#v0.3.0 are already up-to-date.
I was thinking of tagging a new release as v0.6.0. I'd like to include a fix for #43 and #46 (as they are trivial to add).
Any/All changes after that, for the Migrator, would then be tagged as v0.7.0.
Questions

[ ] #43
[ ] #46
[ ] #52
[ ] @ylebre Should #45 also be merged in? Or better to leave that for later?
[x] @michielbdejong Should #50 be merged in?
[ ] Is there anything else that needs to be included in this release?

Maybe #16 ?

Better to leave that for later, that code is on proof-of-concept level at best and probably insecure.


How to change return url after authentication and get token from youtube

I find in the documentation:
"Assuming you were not presented with any errors during authentication, you will be redirected back to your application root. (/)."
Can that change to go to route where is placed form to upload video, other route that is not root?

Is not part of the configs but you can do it manually on this file <path_to_your_project>/vendor/dawson/youtube/routes/web.php on
Route::get(config('youtube.routes.redirect_uri'), function(Illuminate\Http\Request $request)
	{
		$code = $request->get('code');

		if(is_null($code)) {
			throw new Exception('$_GET[\'code\'] is not set.');
		} else {
			$token = Youtube::authenticate($code);
			Youtube::saveAccessTokenToDB($token);
		}

		return redirect('/');
	});

Ok. TNX. I made a pull request for that to be in config.


Restructure code and test generation

I've rewritten some of the code today to make it easier to test and extend in the future.
Among other things, I've

Moved the code files into a wavenet package
Defined all variables in Wavenet up front so that they can be shared between training and generation methods
Renamed WaveNet to WaveNetModel because I want to introduce another class WaveNet that manages all the TensorFlow stuff around WaveNetModel so that the train.py and generate.py scripts should become very simple.
Added tests for generation (including a passing test that compares the old and new generation methods)
Fixed a bug in how we handled the boolean argument in generate.py

Add bias support to fast generation

Holy crap that was fast.

@ibab, I pulled this branch and trained with it. Error dropped rapidly all the way to zero. Then I generated from it and got white noise. I think the only way error could drop to zero is if the net had access to future values, i.e. not causal.

@jyegerlehner: Okay, thanks for finding that out. I'll start looking for bugs.

 I can confirm it.
Makes me wonder what the problem might be, though.
The causal convolution hasn't been changed, and the input/output shift also hasn't been touched.
Those are the only two places where I would suspect a problem.

There was a redundant reshape that seems to have something to do with the problem.
If I remove it, everything seems to work again, but I'm not sure why it makes a difference :/

Switched to Restructure branch and still seeing immediate drop to 0.
Training currently seems to work on Master, but generation hits the problems of https://github.com/ibab/tensorflow-wavenet/pull/88/commits/3261ae0095e5bc7e2e3c156e1bb52cd67915ba66
Running python3 / tensorflow 0.10 / cuda 8.
New in these woods so possible I'm doing something off.!

@paperkettle: If the loss is dropping to 0 for you, that's a pretty sure sign that something is still wrong. It's likely that I made a mistake somewhere.

I've rebased on master and added the changes from #76.

Hey is this branch getting close to landing? Anything I can do to help / any bugs to track down?

Just found the origin of the bug:
I've used filter_width as the first dimension for the 1x1 convolutions inside the dilated block instead of 1.
This meant that they allowed the network to look into future.
The loss now drops at a regular pace.
@maxhodak: It would be great if you could take a look at the code to see whether anything can be expressed in a cleaner way. I'll also go through it.
Next, I'm planning to write a separate WaveNet class that manages all the TensorFlow stuff in the background so we can neatly encapsulate a lot of the functionality that's currently in the train.py and generate.py scripts.
(And this would allow users to use WaveNet more easily for their custom applications)


Yank aoc subscribe

This is now safe to merge
Depends on #971, where the initial implementation is.
Relevant Issues

Partially closes #970
Description

Yanked the aoc subscribe commands. See #971 for how this works.
Did you:

[x] Join the Python Discord Community?
[x] Read all the comments in this template?
[x] Ensure there is an issue open, or link relevant discord discussions?
[x] Read and agree to the contributing guidelines?

Rebased onto main to remove the implementation commit, as that was added with #971

There were merge conflicts, so merged with main.


fix(Usage Reports): change BillingMonth field to match new response from the API

PR summary
See #213 for details of the issue
PR Checklist
Please make sure that your PR fulfills the following requirements:

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

Current vs new behavior
BillingMonth changes to Month and uses the JSON key month instead of billing_month
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


update projects

👷 Deploy Preview for fancy-puffpuff-df775f processing.

Name
Link

🔨 Latest commit
47de7a0de98ea9b3e6df7897c2fb7e0e93951acf

🔍 Latest deploy log
https://app.netlify.com/sites/fancy-puffpuff-df775f/deploys/64df86d1b7d92300082b7154


API reduction

Discussion bits are scattered about, but mostly in #120 (which was growing beyond scope).

Will do, I probably can review it after my lunch and then add ruleset to main

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (d852751) 71.53% compared to head (6db3875) 71.28%.

Files
Patch %
Lines

src/edn/utils/index.rs
50.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #121      +/-   ##
==========================================
- Coverage   71.53%   71.28%   -0.26%
==========================================
  Files           8        8
  Lines         938      867      -71
==========================================
- Hits          671      618      -53
+ Misses        267      249      -18

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I sneaked in test refactoring here because it was causing noise for #120.
I'm guessing for historical reasons it made it easier to work with, but it was testing internal structures that I intend to rewrite, so I converted them to integration tests in https://github.com/naomijub/edn-rs/pull/121/commits/78bdf1cbc201b0295a44c04ff6633e73a6b827bb
If it's ok, I'll continue doing this as I run into things like in https://github.com/naomijub/edn-rs/pull/121/commits/6db3875a4b4afe1ecc2588ff328c301ad2c6c396. A lot of the tests are actually using only public interfaces so can live in tests/. As you probably noticed, there's a lot less #[cfg(feature = "sets")] scattered all over too.
I think going forward cut/paste. I'll keep them in separate commits so it's easy to track.

I sneaked in test refactoring here because it was causing noise for #120.
I'm guessing for historical reasons it made it easier to work with, but it was testing internal structures that I intend to rewrite, so I converted them to integration tests in 78bdf1c
If it's ok, I'll continue doing this as I run into things like in 6db3875. A lot of the tests are actually using only public interfaces so can live in tests/. As you probably noticed, there's a lot less #[cfg(feature = "sets")] scattered all over too.
I think going forward cut/paste. I'll keep them in separate commits so it's easy to track.

I'll probably take a couple of days to review the changes and test them


Export multiple PDFs (one per language) ?

Hi,
Considering the separate directory per locale:  https://vitepress.dev/guide/i18n#separate-directory-for-each-locale
What would be the best approach to generate one PDF for each locale at once (since a single PDF containing all languages makes less sense)?
Thank you.

When generating the PDFs, make sure that the configuration file config.ts has only one language to solve the problem.
For example:
export default defineConfig({
  ...shared,
  locales: {
    root: { label: 'English', ...en },
    // zh: { label: '简体中文', ...zh },
    // pt: { label: 'Português', ...pt }
  }
})

@condorheroblog
Thank you for the quick reply !


Add untested/unintegrated nomad-substrate crate

Motivation
Enable Nomad agents to run against substrate chains. Must add nomad-substrate crate to implement contract traits.

Solution
Major High Level Changes

Adds nomad-substrate crate to rust/chains but does NOT integrate into rest of codebase (i.e. nomad-base and agents)
Moves nomad_core::ChainCommunicationError to nomad-base and makes it a wrapper across chain-specific error types defined in `chains

Note that this solves the issue of having chain-specific errors leak into nomad-core
Note this is also consistent with having nomad-base draw on chain-specific crates and serve as chain-agnostic wrapper

Changes nomad_core::{Common, Home, ConnectionManager} to return associated type error (Self::Error), having chain-specific crates define/return their own chain-specific error types (e.g. EthereumError, SubstrateError)

Details

nomad-substrate

Adds SubstrateHome and SubstrateHomeIndexer objects and implements necessary nomad_core traits
Adds SubstrateError type which wraps all subxt and scale-value deserialization errors (substrate-specific)

nomad-core

Removes ChainCommunicationError (changed/moved to nomad-base)
Has contract traits return associated type errors instead of the old ChainCommunicationError

nomad-base

Adds new ChainCommunicationError which wraps nomad_ethereum::EthereumError and nomad_substrate::SubstrateError

nomad-ethereum

Adds EthereumError error enum to wrapper ethers and gelato errors (ethereum-specific)
Has existing contract methods return Results<_, EthereumError> now instead of using old ChainCommunicationError

accumulator

Adds deserialization for LightMerkle (nomad-substrate needs this to decode tree object)

PR Checklist

[ ] Added Tests
[x] Updated Documentation
[x] Updated CHANGELOG.md for the appropriate package
[ ] Ran PR in local/dev/staging

Closing in favor of #232


Mod brakes jei visibility of hover biom list from industrial-foregoing

Installed Mods
emi-1.0.22+1.19.2+forge.jar
jei-1.19.2-forge-<IP_ADDRESS>8.jar
industrial-foregoing-1.19.2-<IP_ADDRESS>-5.jar
titanium-1.19.2-3.7.4-28.jar
Mod brakes the jei ability to show biom list from industrial-foregoing.
When emi is removed, it's visible. With emi the hover list is not visible.
Shown in usage of laser base fluid or ore. Hover over the tree.
How it should be:

Fixed in 1.0.23


Mark R_austria tutorial test as xfail on macos-latest-py3.8

This PR marks test message_ix/tests/test_tutorials.py::test_tutorial[R_austria] as xfail due to flakiness. Merging this PR will close issue #507.
How to review

Read the diff and note that the CI checks all pass.

PR checklist

[x] Continuous integration checks all ✅
[x] Add or expand tests; coverage checks both ✅

I pushed a change here. Briefly:

The tutorial variable in this file is a list which is passed to pytest.mark.parametrize().
Per the Pytest docs (1, 2), this list already used pytest.param(…, marks=…) for some of the cases, to apply marks to individual tests, e.g. the R tutorials.
So we can (a) add a new mark object, stored as a variable (mark1), and then (b) add that to the existing marks= argument for the test(s) to which it applies.

This avoids having the logic about which tests to run/outcomes to expect in the body of the test itself.


Show notification when path is invalid

Currently there's an error in devtools only

Updated errors in version v1.0.0


Update client to use BearerTokenFile when needed

With this PR we should be able to lunch the client with different Options or none, it tries to resemble https://github.com/zalando/skipper/pull/2590 so requests could be authorized with tokens outside clusters.
Without this PR I get 2023/10/04 17:55:21 Failed to get Ingress list: Unauthorized in the example, could hack around and try to use /var/run/secrets/kubernetes.io/serviceaccount/token but this also didn't work

Closing this since it could be resolved by using the right $KUBECONFIG and
loadingRules := clientcmd.NewDefaultClientConfigLoadingRules()
configOverrides := &clientcmd.ConfigOverrides{}
kubeConfig := clientcmd.NewNonInteractiveDeferredLoadingClientConfig(loadingRules, configOverrides)
config, err := kubeConfig.ClientConfig()
# error handling
client, err := rgclient.NewClientset(kubeConfig)
# error handling


Chef14:  Poise tests broke

Failures:
  1) Poise::Helpers::LWRPPolyfill Poise::Helpers::LWRPPolyfill::Provider load_current_resource override with no new_resource
     Failure/Error: subject { provider(:poise_test).new(nil, nil).load_current_resource }
     NoMethodError:
       undefined method `name' for nil:NilClass
     # /home/travis/.rvm/gems/ruby-2.5.1/gems/chef-14.0.190/lib/chef/provider.rb:97:in `initialize'
     # ./test/spec/helpers/lwrp_polyfill_spec.rb:148:in `new'
     # ./test/spec/helpers/lwrp_polyfill_spec.rb:148:in `block (5 levels) in <top (required)>'
     # ./test/spec/helpers/lwrp_polyfill_spec.rb:149:in `block (5 levels) in <top (required)>'
  2) Poise::Helpers::LWRPPolyfill Poise::Helpers::LWRPPolyfill::Provider load_current_resource override with no new_resource
     Failure/Error: subject { provider(:poise_test).new(nil, nil).load_current_resource }
     NoMethodError:
       undefined method `name' for nil:NilClass
     # /home/travis/.rvm/gems/ruby-2.5.1/gems/chef-14.0.190/lib/chef/provider.rb:97:in `initialize'
     # ./test/spec/helpers/lwrp_polyfill_spec.rb:148:in `new'
     # ./test/spec/helpers/lwrp_polyfill_spec.rb:148:in `block (5 levels) in <top (required)>'
     # ./test/spec/helpers/lwrp_polyfill_spec.rb:150:in `block (5 levels) in <top (required)>'
  3) Poise::Helpers::DefinedIn#poise_defined_in_cookbook
     Failure/Error: subject { resource(:poise_test).new('test', run_context) }
       #<Double "run context"> received unexpected message :logger with (no args)
     # /home/travis/.rvm/gems/ruby-2.5.1/gems/chef-14.0.190/lib/chef/resource.rb:136:in `initialize'
     # /home/travis/.rvm/gems/ruby-2.5.1/gems/chefspec-7.1.2/lib/chefspec/extensions/chef/resource.rb:42:in `initialize'
     # ./test/spec/helpers/defined_in_spec.rb:56:in `new'
     # ./test/spec/helpers/defined_in_spec.rb:56:in `block (3 levels) in <top (required)>'
     # ./test/spec/helpers/defined_in_spec.rb:58:in `block (3 levels) in <top (required)>'
Finished in 4 minutes 27.8 seconds (files took 22.88 seconds to load)
427 examples, 3 failures
Failed examples:
rspec ./test/spec/helpers/lwrp_polyfill_spec.rb:149 # Poise::Helpers::LWRPPolyfill Poise::Helpers::LWRPPolyfill::Provider load_current_resource override with no new_resource
rspec ./test/spec/helpers/lwrp_polyfill_spec.rb:150 # Poise::Helpers::LWRPPolyfill Poise::Helpers::LWRPPolyfill::Provider load_current_resource override with no new_resource
rspec ./test/spec/helpers/defined_in_spec.rb:57 # Poise::Helpers::DefinedIn#poise_defined_in_cookbook

Welp.


Rename .Components.Browser -> Components.Web

This is part of API review for Blazor. We're renaming these projects to
reflect the fact that they are for Blazor using web technologies (html
+css).
The old naming of .Browser was a little unclear of whether it meant browser-technologies or meant client-side (in the browser).

Note: I didn't rename BrowserRenderer in the .ts code.

We can deal with moving extra contents across to this package (and maybe changing more namespaces) after.

Yup. Exactly what I had in mind.

Note: I didn't rename BrowserRenderer in the .ts code.

That sounds fine. Longer term we should reconside the .ts-side distinction between Renderer and BrowserRenderer (it's not clear the layering represents anything useful), but it's purely an internal implementation detail so we wouldn't prioritise it soon. I wouldn't worry about renaming any of that presently.


Asymmetrical treatment of '+' in Object.toQueryString() and Object.fromQueryString()

Object.fromQueryString('foo=bar&broken=wear+a') -> {"foo":"bar","broken":"wear+a"}
Object.toQueryString({"foo":"bar","broken":"wear a"}) -> "foo=bar&broken=wear+a"
Object.fromQueryString(Object.toQueryString({"foo":"bar","broken":"wear a"})) -> {foo: "bar", broken: "wear+a"} != {"foo":"bar","broken":"wear a"}
In some of my use cases of sugar, a form class has difficulty in initializing properly from its serialized URL due to this asymmetrical treatment of converting space to '+' in toQueryString, but not '+' to space in fromQueryString.

Duplicate of #457


New Contributor

team:  Marketing
title: Project Manager
isLead: FALSE
display_name: Bagy
github_username: BagyPo
profile_image: https://ibb.co/C2b3f82
slack_username: Bagy
account_number: 7e095dc5825ca517c42a6e6074dfbf939d37ab983df9d951437a40d482333501

shall we close this issue @Chrisha1212


move to shortened, compliant names

Change to match ssl values

Although prod service name is not finalised, we can go with this for now.  LGTM


go-openapi/runtime introduces backwards incompatible API change

Problem statement
The go-openapi/runtime library has introduced a backwards incompatible API change, where a new interface, Authorizer, is required to be implemented and causes the following error:
service\http\restapi\operations\my_api.go:344:46: cannot use o (type *MyAPI) as type middleware.RoutableAPI in argument to middleware.NewRoutableContext:
        *MyAPI does not implement middleware.RoutableAPI (missing Authorizer method)

Swagger specification
v2.0
Steps to reproduce
swagger generate server -f ./swagger/swagger.yml -t ./service/http
go get github.com/go-openapi/runtime
go get github.com/tylerb/graceful
go get github.com/jessevdk/go-flags

Environment
swagger version: 2
go version: 1.8.3/1.9.0
OS: Windows 10/Alpine Linux

I believe #1162 has become victim of this as well.
For now, we are pinning the run time to the hash before the specific commit. We use Glide internally for dependency management. For those affected, add this into your glide.yaml file:
- package: github.com/go-openapi/runtime
  version: f1447ecfd160e50218589d4db3fb28bd24b8dec8

Hi all! how can I solve it with govendor?
Many thanks

Having a quick look at the govendor readme, I think: govendor fetch github.com/go-openapi/runtime@f1447ecfd160e50218589d4db3fb28bd24b8dec8 should do the trick.

Hi @MatthewHartstonge,
Setting the revision to f1447ecfd160e50218589d4db3fb28bd24b8dec8 I get another error: undefined: runtime.Authorizer.
Do you have any idea how to solve it?

I'll cut a new release today

pushed a new release

This issue seems to be reintroduced in the latest image.

Same issue here. Generated server code won't run because runtime.Authorizer is not defined.

Is this project still active?  I am having this same problem and it does not seem to be being addressed, rolling back version fixes it, but breaks stuff elsewhere.

you have to update your vendor and the swagger binary tool.
The 2 advance in lock-step, it's only an issue with the docker container.

if the runtime.Authorizer is not defined that means that the runtime project or the swagger binary (templates) are not updated to reflect that.

same issue:
runtime.Authorizer is not defined.
modified the runtime version, but doesnot work.
swagger version: 0.13

fixed:
update pckage:
go-openapi/runtime
go-openapi/analysis
go-openapi/spec

Having same issue, with swagger version
version: 0.7.3
commit: 01d9ee15ff01cdbfdc735d21949a7cc66ab6ab56
go build ./server/cmd/a-sample-service-server/main.go
gangtao/go-service/server/restapi/operations
server/restapi/operations/a_sample_service_api.go:188:46: cannot use o (type *ASampleServiceAPI) as type middleware.RoutableAPI in argument to middleware.NewRoutableContext:
*ASampleServiceAPI does not implement middleware.RoutableAPI (missing Authorizer method)
server/restapi/operations/get_time.go:41:11: assignment mismatch: 2 variables but 3 values
server/restapi/operations/post_time.go:41:11: assignment mismatch: 2 variables but 3 values


change status to stable

After testing JourneyAI score schemas for some time, we want to make it as stable now.

@mjasrotia Hi Manik, this PR is to update the meta:status to "stable". Please let me know if there's any comment.
Thanks,

@mjasrotia Hi Manik, this PR is to update the meta:status to "stable". Please let me know if there's any comment.
Thanks,

@daiadobe , This is good.

@daiadobe , This is good.

@prabhum2, Hi Prabhakar, I've tried to create branches but encountered permission denial.  So I still used my fork for PR. The build seems stuck again. Please let me know if I there's anything I can do.
Thanks,

@prabhum2, Hi Prabhakar, I've tried to create branches but encountered permission denial.  So I still used my fork for PR. The build seems stuck again. Please let me know if I there's anything I can do.
Thanks,


Issues with playintegrityfix

I tried release and debug, both of them causing issues to playintegrityfix.
Same case with kernelsu

Please try this build https://github.com/snake-4/Zygisk-Assistant/actions/runs/8713369999/artifacts/1420029812

It should be fixed in 2.1.0


Test on Windows

We should build it on Windows

I tried to build it on Windows without success yet. These are the things I installed so far:

MinGW 64

GCC
G++
Openssl
put bin directory in PATH

CMake
Curl

Put include and bin it in PATH

I used the Rust installer with MinGW ABI. I'm not sure if the MSVC version is suitable for our case because we depend on Make, OpenSSL and friends.


[DOC] Nebari Troubleshooting page

PR for the Nebari troubleshooting page ( Fixes #83 ).
Currently I am simply moving existing documentation over while also making grammatical and stylistic changes to the original source:

https://github.com/Quansight/qhub/blob/main/docs/source/user_guide/troubleshooting.md
https://github.com/Quansight/qhub/blob/main/docs/source/admin_guide/troubleshooting.md

(I removed the "Theming" section since this does not seem to be related to Troubleshooting, but am happy to add it back if so desired)
Once we're happy with the content, I will be reformatting the Troubleshooting page as much as possible to be closer to the layout seen in the JupyterHub and Docker Stacks troubleshooting pages.
Suggestions are welcome.

Image paths aren't rendering properly for some reason.

Checklist for content in the current page that will need to be revisited: https://github.com/nebari-dev/nebari-docs/issues/83#issuecomment-1212111241

I think I'd like this page organized a bit differently, but I'm not sure exactly what would be best. Did you have any other ideas for organization?

I was essentially mimicking the JupyterHub troubleshooting page https://jupyterhub.readthedocs.io/en/stable/troubleshooting.html
I guess it depends on what kinds of topics we want to capture, going forward. Is this mainly for common errors? And/or for non-error behavior that seems confusing or counterintuitive? I think there's room for the latter but we have to be careful it doesn't simply become an extension of the FAQ.

separate FAQ from troubleshooting
Each point needs

name of issue
explain the issue
explain why it might be happening
explain some things to try

debugging section ?
tabs for cloud provider section

PR should now include tabbed table, and exclude the question on /tmp, which is now in a separate FAQ (#132).

@kcpevey Still two open items from your previous review that need feedback, but otherwise I think this addresses everything we've discussed so far.

@kcpevey For fixing the broken link: https://github.com/nebari-dev/nebari-docs/issues/134
Latest commit includes fix for the sidebar link.

This PR is what causes that issue... why not just fix it here before merging?

@kcpevey My (flawed) rationale last week was that it was outside the troubleshooting page. Apologies, I've committed the fix here and will close the other PR.


Issue with certain complex forward declarations

Please look at the following compile error:
https://gcc.godbolt.org/z/Ulejks
Seems to be consistent on all compilers.
Apparently this is due to the usage of the following typedef:
       typedef remove_reference_t<decltype(*_VSTD::declval<_Tp&>())> element_type;

Interestingly enough - replacing it with more complex typedef where we're using T::element_type if it exists (otherwise the same logic), makes compilation successful.
I do think that being able to forward declare things is essential so it's really regretful to lose it when wrapping pointer in propagate_const.
Personally I don't see why usage of this typedef requires type definition but major compilers seem to agree on this so maybe it happens according to the standard for some reason.

I will look into this.

For reference, a Stack Overflow discussion of this issue: https://stackoverflow.com/questions/54787606/propagate-const-and-forward-declaration

Fix outlines in the stack overflow post.


[Feature] implement tzip26

to adapt tzip26

type of proposal_id is change to bytes
Resolve_proposal is renamed to Proof_of_event_challenge
emit event proof_of_event when resolve a proposal

other

fix test cases for upgrading the version of ligo compiler

close, and open the other PR: https://github.com/marigold-dev/tzsafe/pull/29


Fix NavigationObstacle 2D/3D (re)parent issues

Fixes (re)parent issues with NavigationObstacle 2D and 3D (same as NavigationAgents).
Also adds the option from NavigationAgents to override the default navigation map.

Thanks!


Server closes connection for files > ~23K, when trying to upload via JsRuntime.InvokeAsync(

Describe the bug
While implementing a test program to upload files using server side Razor Components, any file that is greater than about 23K closes the server connection. The connection does not restart and requires restart of the program.
To Reproduce
Steps to reproduce the behavior:

Using
ASP.NET Core Blazor Language Services   0.8.0-preview-19104-04
Visual Studio 2019 Preview 2

Razor Component source
UploadFileTest.cshtml
@page "/UploadFileTest"

@using Microsoft.JSInterop;
@inject IJSRuntime JsRuntime;

@Filename

Data length = @dataLength

@data

<input type="file" onchange="@FileSelected" id="fileUpload" />

@if (fileIsSelected)
{
    <button class="btn btn-primary" onclick="@UploadFile">Upload File</button>
}

@functions
{
    bool fileIsSelected = false;
    int dataLength = 0;
    string Filename = "Blank";
    string data;

    async Task FileSelected()
    {
        string text = await JsRuntime.InvokeAsync<string>("GetFileName");
        Filename = text;
        fileIsSelected = true;
        StateHasChanged();
    }
    async Task UploadFile()
    {
        data = await JsRuntime.InvokeAsync<string>("readFileToUpload");
        if (data != null)
        {
            dataLength = data.Length;
            StateHasChanged();
        }
    }

Index.html
<!DOCTYPE html>

    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width" />
    <title>Standards</title>
    <base href="/" />
    <link href="css/bootstrap/bootstrap.min.css" rel="stylesheet" />
    <link href="css/site.css" rel="stylesheet" />

    <app>Loading...</app>

Expected behavior
===================
Base 64 encoded data is created by the browser and can be seen in the console via the
console.log(fileContents);
The file contents are successfully transferred for files that are smaller than about 23K bytes as sized on the disk.
Error
System.InvalidOperationException: Advancing examined to the end would cause pipe to deadlock because FlushAsync is waiting.
at System.IO.Pipelines.ThrowHelper.ThrowInvalidOperationException_BackpressureDeadlock()
at System.IO.Pipelines.Pipe.AdvanceReader(BufferSegment consumedSegment, Int32 consumedIndex, BufferSegment examinedSegment, Int32 examinedIndex)
at System.IO.Pipelines.Pipe.AdvanceReader(SequencePosition& consumed, SequencePosition& examined)
at System.IO.Pipelines.Pipe.DefaultPipeReader.AdvanceTo(SequencePosition consumed, SequencePosition examined)
at Microsoft.AspNetCore.SignalR.HubConnectionHandler1.DispatchMessagesAsync(HubConnectionContext connection)    at Microsoft.AspNetCore.SignalR.HubConnectionHandler1.RunHubAsync(HubConnectionContext connection)
Information: Close message received from server.
Microsoft.AspNetCore.Hosting.Internal.GenericWebHostService: Information: Request finished in 58219.6816ms 101
Error: Connection disconnected with error 'Error: Server returned an error on close: Connection closed with an error.'.

Perhaps the following can help you:
https://github.com/aspnet/Blazor/issues/1614#issuecomment-433983017
https://github.com/aspnet/AspNetCore/issues/5623

Thanks, the information in that discussion explains the problem, and the error message that is not that helpful


Nice work

Looking forward to seeing this get built out further. I'd be interested to help. FWIW, you might be interested in looking at some of the UX and architecture of https://github.com/tosher/Redlime, a similar plugin for Sublime Text.

I'ld like to share my usage of redmine/your plugin.
In my organisation, the people that have issues assigned to will mark them as resolved (most of the time), then another people will verify and closed the issue (or mark as unresolved).
In that workflow, my list of issues contain all not closed, it would be nice to have a settings to filter the list by issue statuses (for me opened but not resolved).
What did you think about that ?

I think I'll make configurable queries. One will be able to create own version on query based on needs. So, in your settings, you would be able to define list of queries, which will be listed in QuickPick (for example, action named "Custom queries" will contain all of customly defined queries).


Redundancy/mis-hierarchi in data saving folder structure

In the current config, data are saved into the following 5 subfolders:
SessionFolder/EphysFolder
SessionFolder/HarpFolder
SessionFolder/PhotometryFolder
SessionFolder/TrainingFolder
SessionFolder/VideoFolder
This is great. However, actual Photometry and Video data are currently saved into
SessionFolder/HarpFolder/PhotometryFolder
SessionFolder/HarpFolder/VideoFolder
while leaving the following two empty:
SessionFolder/PhotometryFolder
SessionFolder/VideoFolder

This is because the GUI code is sending the HarpFolder as the RootPath to Bonsai via OSC.
Can @alexpiet @hanhou fix the GUI part? I can take care of fixing the Bonsai part.
I wanted to fix this before working on data streaming to s3. (which likely requires functional metadata anyways beforehand...)

@hagikent Where do you want the Photometry and Video data saved? into SessionFolder/PhotometryFolder?

This issue is a continuation of: https://github.com/AllenNeuralDynamics/aind-behavior-blog/issues/49
@XX-Yin Can you clarify what needs to be updated in MyFunctions._GetLicks() in order to save the Photometry data in the right folder?

I don't think we need to update MyFunctions._GetLicks().
The rootpath sent from the python through OSC message is SessionFolder/HarpFolder/. Then, we concatenate the rootpath with PhotometryFolder or VideoFolder in bonsai. We can solve this by directly connecting the SessionFolder with the PhotometryFolder or VideoFolder in Bonsai.

@hagikent Where do you want the Photometry and Video data saved? into SessionFolder/PhotometryFolder?

Photometry data to  SessionFolder/PhotometryFolder
Video data to SessionFolder/VideoFolder

Just to be extra clear, is this issue still active now that the fiber photometry workflow has been separated?

Still relevant. Although I haven't implemented yet (because of the quick fix last night), the idea is to receive the same OSC  from GUI (BonsaiOSC:4002) by the photometry-bonsai and to save the data into the same session folder, with the organisation described above.

thanks for catching this old issue; yes, orthogonality solved as a byproduct of #299


Update tests for python3.10

Be less strict about subversions

@m3nu pinning a python 3.10 subversion was too strict.
Can you update the repo settings one more time?

Done.


lack of partials support for handlebars

The way the --hbs options currently works doesnt support partials, i suspect that it might be possible to change that without the use of an additional package, but there was a package designed specifically with this in mind, so i figured id use that instead.
In #161 I jumped the gun on the discussion phase and already submitted a replacement of the handlebars package which DG also maintains, and coded up the rest of the suggestions he laid out there. My plan is to resubmit a PR next week taking into account any feedback i get here, and also see if i can figure out how to get DG's handlebars package to support partials the way the package i found does.

Was there any progress on this?

short answer no
The issue was that the only considered reliable packages are those in the purview of the expressjs github organization which @dougwilson also manages, and he raises valid concerns about the huge matrix of supported platforms and versioning that come inherently as adding a node package into the mix from outside.
I didn't feel comfortable rewriting or augmenting existing package at the time, but for now I'd suggest installing the branch with the external package, running it to see the output it contains, copy/pasting the output to a github gist, reinstalling the generator from npm and just copy and pasting from the gist.

Got it, thanks!
On Thu, Nov 30, 2017 at 5:21 PM David Ankin<EMAIL_ADDRESS>wrote:

short answer no
The issue was that the only considered reliable packages are those in the
purview of the expressjs github organization which @dougwilson
https://github.com/dougwilson also manages, and he raises valid
concerns about the huge matrix of supported platforms and versioning that
come inherently as adding a node package into the mix from outside.
I didn't feel comfortable rewriting or augmenting existing package at the
time, but for now I'd suggest installing the branch with the external
package, running it to see the output it contains, copy/pasting the output
to a github gist, reinstalling the generator from npm and just copy and
pasting from the gist.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/expressjs/generator/issues/162#issuecomment-348339746,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARj5GeJNvYOP_PdAQc43EliSDzf1oQbsks5s7ypggaJpZM4N6sXz
.