Update from 1.1.10 to 1.2.1 loading world crash

Updated only Zenith to the current version
crash-2024-07-08_13.26.18-server.txt
crash-2024-07-08_13.26.19-client.txt

Looks to be a conflict with Extra RPG Attributes.
Basically:

Zenith, to check LootCategories for heavy weapons, creates some dummy entities to check canDisableShield (there really doesn't seem to be a better way to do this) - it equips them with items and calls setItemInHand
This calls onEquipItem, where ExtraRPGAttributes injects to call getAttributeModifiers to check if they should delay reabsorption
Fabric API's ModifyItemAttributeModifiersCallback hooks into getAttributeModifiers
(The change in this update): Zenith uses the ModifyItemAttributeModifiersCallback to add gem modifiers, in which it tries to reevaluate LootCategories to determine how to apply them

I suggested a workaround to the developer of Extra RPG Attributes, but something here is Cursed :tm:

The Extra RPG Attributes dev said they’ll look into implementing the ThreadLocal failsafe
For now, there’s a somewhat serviceable workaround depending on your modlist. Using

Zenith
Zephyr
Extra RPG Attributes
Better Combat
Will prevent this crash, as this original check for heavy weapons is bypassed entirely.


Add Python packaging requirements for v2.4.15.

Hi,
As discussed on the mailing list, these are the changes necessary to build a native python source distribution for v2.4.15.
To build and install a Python package, you should be able to do:
cd bindings/python/pywsman
python setup.py sdist # Make a python source distribution
cd dist
pip install pywsman-2.4.14-0.tar.gz # Build and install the python package

I branched off from the v2.4.15 tag to apply these changes and test the build; however, it seems the VERSION.cmake at this point still has a patch revision of 14 - hence the version being incorrect in the Python package.
There are author and author_email tags we should probably add in setup.py, along with some other optional metadata (documented here: https://packaging.python.org/en/latest/distributing.html#setup-args) - what would you like these set to?
Kind regards,
Ahmad

Merged to master for 2.5.2.
Thanks !


fix(Element): use similar types for displayed texture source comparison

The change introduced in #508 seems to be comparing incompatible types, which is causing an issue where patching in a new texture source is the only thing that triggers a txLoaded event to fire; patching new dimensions does not fire that event.
The issue can be seen here: https://playground.lightningjs.io/#Mhe2FycwzpSt
This fix reverts the check to a previous version where patching in dimensions constitutes as a new texture having loaded, which will fire off the appropriate event.

I think the current behavior is correct, if you look at the docs: https://lightningjs.io/docs/#/lightning-core-reference/Templates/Events?id=events
txLoaded | Fires when a texture is successfully loaded.

That means txLoaded only should fire if a texture is loaded right? Changing the dimensions doesn't update the texture so nothing is (re)loaded thus doesn't provide a txLoaded event.
Might warrant another event, but what's the use case for listening for dimension changes on an Image tag?

One example is that we have an Artwork component -- which handles rendering multiple textures, fallback sources, and effects -- that will scale down an image to a user-defined width and height before checking for and applying various effects, but we need to wait until the texture is fully loaded before we can grab the aspect ratio and scale down that texture.
Previously, we were able to wait until the txLoaded event was fired before checking the values, but if that should only be fired when the texture source changes another event that would signal that the texture has been manipulated in some way would certainly be a viable alternative!

@ImCoolNowRight you should use onAfterUpdate to react to size changes:
https://playground.lightningjs.io/#Vc36DoKlEVFY


rootfs: copy kernel modules to correct location

Commit b8f1a688340c7b1cfe5a1cb1bbe6a792dc97acf8 ("rootfs: Simplify
code") introduced a variable called destdir but accidentally used
dest_dir with cp(1) instead.  This causes kernel modules to be copied to
the wrong location.
Rename the variable to dest_dir to be consistent with module_dir and
rootfs_dir variables used in this function.
Fixes: #94
Signed-off-by: Stefan Hajnoczi<EMAIL_ADDRESS>

lgtm

@jodh-intel @devimc  @bwarden  - please take a look.

Good catch @stefanha!
lgtm


runtime: dieFromSignal should reinstall fwdSig[sig] instead of hard-coding _SIG_DFL

runtime.dieFromSignal is called in a few places in the runtime where we've handled a fatal signal and intend to terminate the process.
At the moment, dieFromSignal unconditionally calls setsig(sig, _SIG_DFL) and re-raises the signal.
That's pretty much always the right thing to do in a pure-Go program.
However, in a mixed-language program there may be some existing signal handler, and that signal handler might want to do something useful — for example, save a core dump, mark an input record as a potential cause of the crash, or write an entry to a crash log.
It seems to me that we could address this use-case pretty easily by making dieFromSignal try to reinstall and raise to the previous handler before it resorts to SIG_DFL.  Perhaps something like:
func dieFromSignal(sig uint32) {
	fwdFn := atomic.Loaduintptr(&fwdSig[sig])
	if fwdFn != _SIG_DFL {
		setsig(sig, fwdFn)
		unblocksig(sig)
		raise(sig)
	}

	// fwdSig[sig] either didn't exist or failed to terminate the process.
	 On some systems, though, raise
	// sends the signal to the whole process rather than to just
	// the current thread, which means that the signal may not yet
	// have been delivered. Give other threads a chance to run and
	// pick up the signal.
	osyield()
	osyield()
	osyield()

	// If we are still somehow running, just exit with the wrong status.
	exit(2)
}

In the typical case — when there are no handlers registered before ours — the behavior would be the same as it is today.  On the off chance that some other language has registered a prior handler, we would instead invoke that handler, and if it isn't well behaved (i.e. doesn't terminate the process), then we fall back to today's behavior anyway.

SGTM
It's only necessary to call unblockSig once.


Update EXO PowerShell module minimum version to 3.2

🗣 Description

Updates minimum EXO PowerShell module version in RequiredVersions.ps1 to 3.2.0
The broken check is the broken Graph Authentication module from #437
💭 Motivation and context

Closes #439
🧪 Testing

Ran Invoke-SCuBA with all products with current EXO PoSH module version 3.1 against G3, G5, E5, and GCCHigh tenants. Still needed basic auth enabled on the client.
Then ran the below commands to upgrade to EXO PoSh module version 3.2

Uninstall-Module ExchangeOnlineManagement
.\SetUp.ps1 # Installs the latest acceptable version of all PowerShell modules including EXO 3.2

After that, tested against G3, G5, E5, and GCCHigh with both interactive auth and service principal auth. No issues found except the one mentioned in the next bullet. Basic auth is NOT needed on the client. WOO!
Defender still doesn't work on GCCHigh while authenticating via SP :( #265 . As noted in that issue and tested again just now, Defender does work for GCCHigh when authenticating interactively.

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[x] All relevant type-of-change labels have been added.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[x] ~All new and existing tests pass.~

✅ Pre-merge checklist

✅ Post-merge checklist

wohooo!


sendfile

Given that NodeJS doesn't seem to have any plans to add support for sendfile. Maybe this is something that could be added to uws for improved performance when transferring files?
Something like:
res
  .readfile(path, {
    start,
    end,
    fd
  })
  .on('finish', onFinish)
  .on('error', onError)

i.e. similar options & params as fs.createReadStream. For platforms that don't properly implement sendfile (OSX & Windows) we could have a fallback.
With this I believe uws could compete with NGINX as a file server.

https://blog.plenz.com/2014-04/so-you-want-to-write-to-a-file-real-fast.html

a similar writefile would also be nice:
req
  .writefile(path, {
    start,
    end,
    fd
  })
  .on('finish', onFinish)
  .on('error', onError)

This is out of scope of this project

@alexhultman: Could we at least get access to the socket descriptor on the response object (if that is not already the case?) so that this can be implemented outside of this project?

It is getHttpSocket().getFd()


How to open local image?

I want to open local image similar to the following:
let images = [{ 			url: require('./../assets/images/myimage.jpg'), 		}];
This produced the following

also tried
let images = [{ 			url:' ./../assets/images/myimage.jpg', 		}];
This produced the following

Nothing's working though. Can anybody help? Thanks.

See #27


failed to reproduce the accuracy of WRN-28-10 on Cifar-10

unable to reproduce the acc on cifar-10 use wrn-28-10. The gap between the reported acc and th actual acc is huge while all hyper parameters are exactly the same.

The problem could be with the 'F.dropout' function in the issue below!
Unfortunately I currently do not have any access to GPUs this semester :(
Will attend to the issue after June!

Hi, i have checked the issues on F.dropout and altered the 'F.dropout' related codes according to https://github.com/xternalz/WideResNet-pytorch/blob/master/wideresnet.py.
It terms out this is not the major problem. Seems to me there exists some implementation errors in the model. I have able to reproduce the result using xternalz git repo.

Hi, i have checked the issues on F.dropout and altered the 'F.dropout' related codes according to https://github.com/xternalz/WideResNet-pytorch/blob/master/wideresnet.py.
It terms out this is not the major problem. Seems to me there exist some implementation errors in the model. I have able to reproduce the result using xternalz git repo.


Updated ACS Rooms CLI to reference 1.0.0b2 SDK

Updated ACS Rooms CLI to reference 1.0.0b2 SDK
Updated Rooms tests and Recorded test files

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

Please update the history file as well (communication/HISTORY.rst).

Also, I believe you need to require a minimum version for the SDK as these changes do not work with previous versions of the rooms python sdk.


✨ Updated BoxtOut AddressSelectionUI

[x] Build the AutoCompleteListItem to match the design
[x] Add the animation to move the "search input" higher when the user focus's on it
[x] Hide the keyboard and auto complete results when user selects a location
[x] Center the floating continue button on the Scaffold
[x] Hide the floating continue button until we have selected a value

@algokun can you please add a screen shot of the UI. The best would be a recording of the user interaction as well so that I can give feedback on how it looks and operates.

Dane, I just made changes accordingly. Thanks for reviewing.
Here's the recording
https://user-images.githubusercontent.com/21126965/120748813-fed61380-c520-11eb-97ab-fc03997232ff.mp4

@algokun When you select the Auto complete it should show in the text field.

@algokun you gonna tackle the changes?

@algokun you gonna tackle the changes?

Sorry Dane, I was busy, will submit PR with the changes today.

Here's the latest recording with updated changes.
https://www.loom.com/share/f8f3cfd349744f6ead2b39f75d56bd07

@algokun please remove the loading indicator under the text field as well. That's not part of the design

Alright, @FilledStacks. I'll update it now

@FilledStacks Here's the updated version
https://www.loom.com/share/712b5d070e704f7a8a87b1d1865e590e


Aggregate numerator breakdown in measures to 3 months worth

See https://openprescribing.net/measure/ace/practice/L83065/ and https://ebmdatalab.slack.com/archives/C31D62X5X/p1510586327000388

Fixed by https://github.com/ebmdatalab/openprescribing/pull/639


Development: Fix flaky ProgrammingExerciseBitbucketBambooIntegrationTest

Checklist
General

[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] I followed the coding and design guidelines.

Motivation and Context

The test ProgrammingExerciseBitbucketBambooIntegrationTest.testArchiveCourseWithProgrammingExercise is flaky with postgres.
Description

The test is similar to the one that was fixed in https://github.com/ls1intum/Artemis/pull/6768. When creating the archive, there is no guarantee when the path of the zip archive is updated in the database. To ensure that this update is persisted immediately, we now flush the data as soon as the archive is created.
Review Progress

Code Review

[ ] Code Review 1
[ ] Code Review 2

Test Coverage

unchanged

Codecov Report

Merging #6822 (8b52a09) into develop (4f38b2d) will decrease coverage by 4.53%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #6822      +/-   ##
=============================================
- Coverage      84.93%   80.40%   -4.53%
+ Complexity     13922    13921       -1
=============================================
  Files           1148     2437    +1289
  Lines          44912    93236   +48324
  Branches        4641    13105    +8464
=============================================
+ Hits           38146    74971   +36825
- Misses          4253    10045    +5792
- Partials        2513     8220    +5707

Impacted Files
Coverage Δ

.../de/tum/in/www1/artemis/service/CourseService.java
86.82% <100.00%> (ø)

... and 1290 files with indirect coverage changes

Flag
Coverage Δ

client
76.20% <ø> (?)

server
84.93% <100.00%> (-0.01%)
:arrow_down:

Continue to review full report in Codecov by Sentry.

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


Can I use this under Ubuntu?

Hi,
Can I use this tool under Ubuntu to convert czi to tiff? I tried running test_bfread.py but failed because of its dependency on win32com. Is Windows required for running this program?
Thanks

Hi,
this is an internal test, which I use to actually alos test the COM interface from Python to the ZEN software (which writes CZI) on my windows machine. So this exact file does only makes sense on windows and where you have a paid version of ZEN Blue.
But all the rest works also on ubuntu.
If you only want to convert CZI to TIFF use:
https://github.com/sebi06/BioFormatsRead/blob/master/convert_czi2tiff.py


Improve and extend Refaster Map rules

Suggested commit message:
Improve and extend Refaster `Map` rules (#337)

Summary of changes:
- Move relevant rules from `AssertJRules` to `AssertJMapRules` and introduce associated tests.
- Extract relevant rules from `AssortedRules` to the new `MapRules` Refaster collection.
- Add a few new rules to both `AssertJMapRules` and `MapRules`.

Note while reviewing, I find that doing some vimdiffs on the test files helps a lot to review the rules introduced :)
vimdiff error-prone-contrib/src/test/resources/tech/picnic/errorprone/refasterrules/AssertJMapRulesTestInput.java error-prone-contrib/src/test/resources/tech/picnic/errorprone/refasterrules/AssertJMapRulesTestOutput.java

vimdiff error-prone-contrib/src/test/resources/tech/picnic/errorprone/refasterrules/MapRulesTestInput.java error-prone-contrib/src/test/resources/tech/picnic/errorprone/refasterrules/MapRulesTestOutput.java

I know what you'll think, and you are right; we should add something for this to automate it stuck_out_tongue.

Exactly :wink:
Changes LGTM!


feat(operator): automatically adopt generated resources

Automatically adopt resources generated by OLM during operator
installation. Any CSV installed via Subscription is adopted by an
operator named after the subscribed package and its install namespace; other resources with
OwnerReferences or OLM-style owner labels referencing component CSVs are
transitively adopted.

/retest

/hold

/hold cancel

/retest

@jianzhangbjz Please take a look at the test cases

/retest

/retest

@kuiwang02 Please have a review, thanks!

/retest

/retest

/retest

/lgtm

/hold
Preventing turn while test failures are being investigated.

/test e2e-aws-olm

/hold cancel
Failures look unrelated. Opening separate PRs to address. In the short term, I'm unholding this.

/lgtm

/hold

/hold cancel

/hold

/hold cancel
Some patches merged that address the blocking tests.

/lgtm


Add flags of instance, endpoint and normal for metrics command

Add flags of instance, endpoint and normal for metrics command
Fix format issue of How-to-release.md
Update README.md

Resolve apache/skywalking#5890

It's weird, failed to build, but I can build it successfully on my pc.

Read this https://github.com/apache/skywalking-cli/pull/74

Codecov Report

Merging #76 (7139429) into master (ec4db3a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #76   +/-   ##
=======================================
  Coverage   51.56%   51.56%
=======================================
  Files           9        9
  Lines         128      128
=======================================
  Hits           66       66
  Misses         54       54
  Partials        8        8

Continue to review full report at Codecov.

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

LGTM, except for the name of multi-line metrics' label.


Continue to address/suppress warnings from unit tests

There are currently still some straggler warnings (14 of them) in our unit tests. Investigate whether any/all of these can be addressed.

It's best to pay attention to the "development version tests" to understand which warnings are still relevant.  For instance, https://github.com/Qiskit/qiskit-terra/pull/10308 fixed a few numpy-related warnings that we were seeing.


Not possible to omit optional fields in Mongo

Bug description
When defining some nested property as optional, TypeScript actually makes you pass null to it, and doesn't allow you to omit it.
How to reproduce
For this prisma.schema:
type Nested {
  something   String?
}

type SomeType {
  nested Nested?
}

it generates TS types that look like
interface Nested {
  something: null | string
}

Expected behavior
I'd expect these types to be generated:
interface Nested {
  something?: null | string
}

Explicitly passing null for optional fields spams db with these nulls, makes the api cumbersome to work with etc.
Prisma information
see above
Environment & setup
Macos, node 20
Prisma Version
5.14.0

I could reproduce issue on 5.16.0-dev with the following schema:
generator client {
  provider        = "prisma-client-js"
  output          = "../node_modules/.prisma/client"
}

datasource db {
  provider = "mongodb"
  url      = env("TEST_MONGO_URI")
}

model Account {
  id String @id @map("_id") @db.ObjectId @default(auto())
  type SomeType
}

type Nested {
  something   String?
}

type SomeType {
  nested Nested?
}

and the code:

import {  Nested } from './node_modules/.prisma/client'

const nested: Nested = {}

Produces following error:
index.ts:4:7 - error TS2741: Property 'something' is missing in type '{}' but required in type '{ something: string | null; }'.

4 const nested: Nested = {}
        ~~~~~~

  node_modules/.prisma/client/index.d.ts:872:7
    872       something: string | null
              ~~~~~~~~~
    'something' is declared here.

Thanks for looking into it @SevInf, hope there's an easy fix!

@SevInf
What is the criterion for using undefined and null in generated models?
According to the tests, only null is used, but this bug is confirmed.
Can you clarify what use you want to give to null and undefined?


Bug with nested tables and arrays

[[fruit.blah]]
  name = "apple"

  [fruit.blah.physical]
    color = "red"
    shape = "round"

[[fruit.blah]]
  name = "banana"

  [fruit.blah.physical]
    color = "yellow"
    shape = "bent"

From my reading of the toml spec, that should work, and give rise to the following JSON:
{
   "fruit":{
      "blah":[
         {
            "name":"apple",
            "physical":{
               "color":"red",
               "shape":"round"
            }
         },
         {
            "name":"banana",
            "physical":{
               "color":"yellow",
               "shape":"bent"
            }
         }
      ]
   }
}

And tomlv accepts it:
$ tomlv -types fruit.toml                                                                                ~
    fruit.blah                         ArrayHash
        fruit.blah.name                String
        fruit.blah.physical            Hash
            fruit.blah.physical.color  String
            fruit.blah.physical.shape  String
    fruit.blah                         ArrayHash
        fruit.blah.name                String
        fruit.blah.physical            Hash
            fruit.blah.physical.color  String
            fruit.blah.physical.shape  String

However attempting to parse with htoml gives Cannot redefine table ('fruit, blah, physical'.

This is a very interesting issue. Thanks for reporting it.

I've made a test case for it: https://github.com/cies/htoml/tree/fix/issue-16
@HuwCampbell This issue will need --as I can see it-- quite serious overhaul of the "implicitness tracking logic"; as we need to keep track of it "per array item". Any thoughts on this?

I don't think it should be that complicated, could be such that sub tables of the table arrays are filtered out of the parser state each time a new table array item is declared.


F1 should open the help page

Please describe the problem you're trying to solve
https://github.com/sxyazi/yazi/issues/736
Would you be willing to contribute this feature?

[ ] Yes, I'll give it a shot

Describe the solution you'd like
F1 is the standard "Help" key, it should open a help page or some documentation menu
Additional context
See also how ranger does it

Hi, Yazi uses ~ instead of F1 to open help because it's more universal. Some keyboards don't have function keys or require pressing them along with the Fn key, so I wanted to avoid using function keys as much as possible.
Closing as not in the plan.

What a strange decision.

F1 is a standard key on PC keyboards, meaning, all PC software ought to assume it is a key that a user might press.
Even if there are "minimal" keyboards which do not have some standard keys, Yazi could still recognize it as an alternative to ~.
F1 is also the standard help key in a lot of software out there, that many people use every day.
I don't know of any other program that uses ~ for a help key.
Having the help key on a key that a user will never think of pressing defeats the point. As it stands, this feature is completely undiscoverable.
If I have to look up an external resource just to discover what key to press to get help, you might as well just put all help text somewhere on the Internet too.

Well, it's your project.

What do you think about, any time the user presses an unbound key, showing a message such as "Press ~ for help"? This should make the keybind discoverable without explicitly binding it to a function key.

Ah I must've misunderstood you - I'm ok with adding a new F1 as an alternative to ~, as long as it's not replacing it. Do you want to raise a PR for it?

Ah, sorry - indeed I proposed it as an alternative, not moving the existing keybind.
https://github.com/sxyazi/yazi/pull/1336


Bug fix/reduce allocations in hashed collect executor

Scope & Purpose
The HashedCollectExecutor uses an unordered_map to gather all groups with their aggregate values. Previously the value type of the map was a std::unique_ptr<std::vector<std::unique_ptr<Aggregator>>>, and every group was initialized with an actual value, even there were no aggregators (i.e., the vector was empty). So without AGGREGATEwe had one allocation per group, with AGGREGATE we had 2 + <NumberOfAggregators> allocations.
The new implementation uses a single allocation for all aggregators using placement new, which should also result in better cache locality. In addition, the unnecessary allocation in case no aggregators are used is also removed. This resulted in a runtime improvement of ~4-8% on my machine.
Tested using this script in the arangod console:
queries = {
  group:    "FOR i IN 1..500 FOR j IN 1..500 COLLECT a = i, b = j RETURN {a,b}",
  count:    "FOR i IN 1..500 FOR j IN 1..500 COLLECT a = i, b = j WITH COUNT INTO cnt RETURN {a,b,cnt}",
  sum:      "FOR i IN 1..500 FOR j IN 1..500 COLLECT AGGREGATE sum = SUM(i), sum2 = SUM(j) RETURN {sum,sum2}",
  groupSum: "FOR i IN 1..500 FOR j IN 1..500 COLLECT a = i, b = j AGGREGATE sum = SUM(i), sum2 = SUM(j) RETURN {sum,sum2}"
}

for (var k in queries) {
  console.log(k);
  let total = 0;
  let rounds = 10;
  for (var i = 0; i < rounds; ++i) {
    let start = new Date().getTime()
    db._query(queries[k], null, {silent: true}).toArray().length;
    let diff = new Date().getTime() - start;
    total += diff;
    console.log(diff);
  }
  console.log(total / rounds);
  console.log("#############");
}

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[x] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[x] No backports required

Testing & Verification

[x] This change is a trivial rework / code cleanup without any test coverage.

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13004/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13032/

Tests blue


Redirect select actors to their Monster Core/Bestiary equivalent

Included in this round
pack_location	                        actor_name
pathfinder-bestiary-2	        Aolaz
pathfinder-monster-core	Aolaz
pathfinder-bestiary-2	        Army Ant Swarm
pathfinder-monster-core	Army Ant Swarm
pathfinder-bestiary          	Awakened Tree
pathfinder-monster-core	Awakened Tree
pathfinder-bestiary         	Axiomite
pathfinder-monster-core	Axiomite
npc-gallery                      	Azarketi Crab Catcher
pathfinder-monster-core	Azarketi Crab Catcher
pathfinder-bestiary         	Banshee
pathfinder-monster-core	Banshee
pathfinder-monster-core	Basilisk
menace-under-otari-bestiary	Basilisk (BB)
pathfinder-bestiary         	Boar
pathfinder-monster-core	Boar
menace-under-otari-bestiary	Boar (BB)
I'm putting this in draft form first so that this list can be reviewed. Once we have final confirmation. I will push the deleted actors to this PR and change it back so it can be merged

Banshee and basilisk have small differences. The rest are identical

This is ready to go.


how can I get the error code of erc error in metamask?

my question is : if I use
await ethereum.request({             method: "wallet_switchEthereumChain",             params: [{ chainId: "0x80" }],  });
maybe the console of my browser will throw a error like:{code:4902},this code indicate the current network is not added in my metamask.
so,now I want to get this code:4902 without use that request method,for example:there is a button,when I click it,the codes in the button I wrote will detect that the current network is in the metamask or not without use 'wallet_switchEthereumChain'  first,   is there any erc error api for me to do that?

please help!

Hello @KBKUN024, thank you for creating this issue. I apologize for the delay. The 4902 error code indicates that the requested chain ID has not been added to MetaMask yet, and you need to request it using wallet_addEthereumChain first. There is no way of checking which chains a user has added except by calling wallet_switchEthereumChain or wallet_addEthereumChain first.
If you have further questions, please create an issue in https://github.com/MetaMask/metamask-extension. This repository is not the right place for this discussion.


copy paste createHashHistory URL does not work

i am using "createHashHistory" style URL which happens to add  some random key at the end, in order to store location state. As i copy URL and try to load in a new browser window i get nothing with following error in console:
Uncaught ReferenceError: joblists is not defined
URL i am trying to copy looks like this:
http://localhost:8080/#/jobs/jobdetail/1?_k=0x501g
My Route:
    <Route path="jobs" component={Jobs}>
         <Route path="jobdetail/:id" component={JobDetail} />
    </Route>

the error is about joblists being undefined probably in your JobDetail component

why pasting URL in new browser does not track STORE state ?
@knowbody In my "JobDetail" component i am getting id from url and doing a lookup in store(flux) to find the record of that particular id and showing it on page. something like this.
componentDidMount: function(){
		var id = this.props.params.id;
		var joblist = JobStore.getJobById(id);
		console.log(joblist);
},

URL i am trying to copy looks like this:
http://localhost:8080/#/jobs/jobdetail/1?_k=0x501g

I guess in my case when i paste url in new browser my program has no idea of state of Store.  So my question was why "joblists" is undefined, isn't whole point of having a key at the end is to preserve "location state".

why pasting URL in new browser does not track STORE state ?

URL is just a URL—an address your app can interpret. It does not magically preserve the state of your application. It is up to you to persist it (for example, to localStorage), and read it when your application boots up to prefill your Stores. This is not something a router could do for you.

thanks Dan!


update repos links examples used in the chatflows

update repos links examples used in the chatflows to the following

wiki : https://github.com/threefoldfoundation/wiki_example
blog : https://github.com/threefoldfoundation/blog_example
website : https://github.com/threefoldfoundation/website_example

branch: development
commit: c8f20dbdc3c98ed1e1622bd3715faf6c5dddd40e


Update codeql-analysis.yml

Trying to run actions on self hosted runner

Closing while sorting out some runner issues, then re-opening.

@tbdk Can u have a look again?

Approved, but I also now just realized, that there might not be any incentive to be running it on the self hosted runner? :slightly_smiling_face: But you can merge if you'd like it to :-)

@mikk5829 må denne merges??


Get tracking number from reference number; or get list of shipments

Can we get the tracking number from a reference number with this library ? or is possible to get a list of all my packages that are not delivered ?
Thanks in advance

@yanpozka this library is basically a thin wrapper around some of the most basic FedEx services. You can extend BaseService to access and use any of the web services documented in the FedEx Developer Guide.


HTTP status code for "NOT READY"

Describe the bug
Today when edge is not considered ready you get a json response explaining it is not ready with a 200 status code. I think it would be more appropriate to use 503 Service Unavailable.
Steps to reproduce the bug

start edge (with invalid url or token)
curl ready endpoint: curl localhost:3063/internal-backstage/ready
inspect response:

HTTP/1.1 200 OK
content-encoding: gzip
content-type: application/json
date: Wed, 08 May 2024 18:21:25 GMT
etag: W/"15-NytVk1xF3R-LK3QpS5Swfg=="
transfer-encoding: chunked
vary: accept-encoding, Origin, Access-Control-Request-Method, Access-Control-Request-Headers

{
    "status": "NOTREADY"
}

Expected behavior
Use status code  503 Service Unavailable instead of "200".
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
No response
Subscription type
None
Hosting type
None
SDK information (language and version)
No response

solved in 19.1.2


Swift example crashed at return self.senderDisplayName()

New issue checklist

[ ] I have read all of the README, documentation, and FAQ.
[ ] I have reviewed the contributing guidelines. Confirmation: ____
[ ] I have searched existing issues and this is not a duplicate.

General information

Library version(s):
iOS version(s): Simulator (iPhone 6s Plus)
Devices/Simulators affected:
Reproducible in the demo project? (Yes/No):
Related issues:

Bug report
Run swift example then try to send a message. Demo crashed on this line:
    override func senderDisplayName() -> String {
        return self.senderDisplayName()
    }

https://github.com/jessesquires/JSQMessagesViewController/blob/develop/SwiftExample/SwiftExample/ChatViewController.swift#L289
Expected behavior
I think what you meant to do is this:
    override func senderId() -> String {
        return User.Wazniak.rawValue
    }

    override func senderDisplayName() -> String {
        return getName(User.Wazniak)
    }

Since  you are also using user Wazniak above.
return self.senderDisplayName() causes dead loop.

/cc: @MacMeDan @GianniCarlo

mmmmm I remember setting it correctly to Wazniak, some commit afterwards must've changed it, I'll add a test about it to avoid future problems

This was introduced on https://github.com/jessesquires/JSQMessagesViewController/commit/003740e8 about showing and hiding senderDisplayName @MacMeDan there's a private var displayName that is not used, was that what you wanted to return on senderDisplayName() ? let me know your thoughts about this issue 👍

I just came across this and I have a fix (it was easy). Diff incoming!

fixed by #1731

JSQMessage is very easy to use. Thanks guys!


Cannot find module 'react-plaid-link'

I'm seeing this error newly within the past 24 hours, in a docker app that has react-plaid-link as a dependency. Changing my package.json to restrict the dep to v1.2.0 fixed the issue. It seems potentially related to commit f48fed5dd0ac4ecae403325edb30c895d53295ab
Error: Cannot find module 'react-plaid-link'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/usr/src/app/dist/server.bundle.js:3998:18)

getting same issue, let me know if you have resolved it, i am using node -v 8

v1.3.1 is working for me, v1.4.0 and greater are not working.
Node v10.16.1
NPM 6.9.0

Thanks for raising this – I've just released v1.5.0 that re-exposes the main as lib/index.js


Set the priority and date added fields for new issues.

This change sets the priority field in the backlog for new issues to 'needs triage'.
This will let us create a view in the project board of new issues.
Also this adds a 'date added' field and automatically sets it for new issues.
While github has dates associated with issues already, there is no way for us to expose
these as fields on the project boards (see https://github.com/github/feedback/discussions/7280 )
Automatically populating a date field ourselves lets us work around this limitation.

rerun tests


Slider: Need prop -> state sync for value prop

Detailed description

Describe in detail the issue you're having.

Slider doesn't update its knob position even if I change value prop

Is this issue related to a specific component?

Yes, <Slider>

What did you expect to happen? What happened instead? What would you like to see changed?

Slider to react to change in value prop to update its internal state (and change knob position)

What browser are you working in?

Chrome

What version of the Carbon Design System are you using?

v6.33.3
Steps to reproduce the issue

Add a Storybook knob for value in a similar manner as min
Change the knob value

Result: No change in knob position.

Fixed by v10 release.


link_to_remove_association _destroy field still 'true' if validation fails

I edit my model and destroy one of the nested models via link_to_remove_assocation.
I have a validation in the model that does not permit this in certain circumstances and adds an error to this nested resource.
The edit page reloads, and I can see the nested resource which I had attempted to destroy with the error message displayed.
I then click update again, thinking not to destroy that nested resource afterall, but it still tries to destroy it.
I looked at the html and found that the ..__destroy hidden input still had a value of true even though I could see the nested resource partial.
So I had to add some javascript to my view like this:
$('document').ready(function(){
    $("div.nested-fields input[id*='__destroy'][value='true']").attr('value', 'false');
});

to reset the _destroy field to false.
Do you think this is peculiar to my situation, or would it be worth making a pull request?

The default rails behaviour will  just send the received form-parameters back to the client, without changing anything. So indeed: deleted items will still be deleted.
What cocoon does, by default, is "hide" the deleted items.
It is a known bug this does not work correctly, when using turbo-links. So that might explain why deleted items are still visible for you. Although your "fix" code uses document-ready and would not be triggered either --so that got me puzzled: are you using the latest version of cocoon?
But undeleting? That is indeed a special case, not abnormal. But imho a clean solution would be to reset the _destroy flag in the controller. In the controller you know why a validation could fail, and reset some
fields.
Also, a specific case: you need at least 3 members is also easily checked at the client-side, and I would generally hide remove-links when items can no longer be removed. It is easier for me (the coder) and also the user (do not allow actions you know will be wrong). But of course, some validations might not be so easy to check at the client-side.

Thanks I'll take a look at changing the _destroy flag. That will be a much better solution if it works. I'll try tomorrow and get back to you. So all I need to do is alter the params[my_nested_object..._destroy] = false ?
I don't think I'm using turbolinks.
The form is re-rendered after the validation fails, so that's why the $('document').ready works.
The validation is a very complicated one that must(nearly must) be done client side.

Thanks for the help, I still went with the original solution as I want to do the validation along with the other ones. However I'm now reconsidering this approach thanks to your comments.
as a side comment: I've been interested in form objects recently, and some are saying that they are a good way to remove 'accepts_nested_attributes_for' in models. However, I have not seen a good implementation for has_many associations, and I would not know where to start replicating the awesome feel that cocoon provides in the GUI with add and remove links. So for the sake of cocoons GUI, I am sticking with nested_attributes_for.

In the controller, when a validation failed, and you want to set the destroy flag, in the controller, you would need to do something like:
 @project.tags[1]._destroy = false

Because you will re-render your @project (as an example).
Yes, I still have to investigate form objects myself, curious how they would replace/handle nested items. Personally I find the accepts_nested_attributes_for acceptable :) but better options might indeed exist. I have used form objects myself, but only for very simple, specific cases. E.g. a person and her address.

@nathanvda I get a " undefined method `_destroy=' " exception when attempting your solution.

I've added attr_accessor to the model. However, when when I set to false in the controller, the nested forms don't show on the view.

Solved using cocoon's callbacks to hide/show delete buttons to prevent actions that would result in failed validations server side


Exception when unfolding cluster

Usecase:
Click on SYTA_Runtme package and select "unfold and show only targets"
Exception:

Applied filters:

Packaging spec:
Plainion_PRISM_packages.txt

seems to be related to SFDP rendering, rendering graphs with DOT did not show this error (yet)

fixed with latest


Security Lake custom source configuration for es-loader

The doc for Security Lake integration says that if the S3 object name doesn't match the current config it has to be reconfigured in user.ini:
[securitylake]
s3_key = [0-9a-f]{32}\.gz\.parquet|[Ss]ecurity[Ll]ake/|file_name_of_parquet

I have set mine as follows:
[securitylake]
s3_key = [0-9a-f]{32}\.gz\.parquet|[Ss]ecurity[Ll]ake/|[a-zA-Z0-9-]+\.gz

in order to match these S3 objects delivered from Security Lake custom sources:
ext/OCSF_LAMBDA/region=us-east-1/accountId=1234567891011/eventday=20230811/dev-sl-ocsf-processing-OcsfLambdaLogsCustomSourceDe-GjVRhffh11x3-2-2023-08-11-22-16-56-f446a497-81b0-3e44-931c-c8fc297abcd1.gz
ext/OCSF_WAF/region=us-east-1/accountId=1234567891011/eventday=20230811/dev-sl-ocsf-processing-OcsfWafLogsCustomSourceDeliv-1ECAj4uSWnt6-2-2023-08-11-22-10-59-3a8d80f4-a649-33dc-a794-ac6d733ed35a.gz
ext/OCSF_WAF/region=us-east-1/accountId=1234567891011/eventday=20230811/dev-sl-ocsf-processing-OcsfWafLogsCustomSourceDeliv-1ECAj4uSWnt6-2-2023-08-11-22-16-02-62d1719f-977a-3422-96a1-61017a777c85.gz
ext/OCSF_WAF/region=us-east-1/accountId=1234567891011/eventday=20230811/dev-sl-ocsf-processing-OcsfWafLogsCustomSourceDeliv-1ECAj4uSWnt6-2-2023-08-11-22-16-42-22b6a235-5e29-3fdc-9e95-aeb8d4aa538c.gz

Does not appear to work because I am not finding the records in the ES. How should I configure user.ini so that es-loader will find these objects and load them to ES?

I have checked the regex by https://regex101.com/ . It seems good.
Can you take a look at the SIEM dashboard in CloudWatch Dashbaord? Maybe you can find the error log or something else. If you still can't figure it out, please let us know the processing message of the parquet file in /aws/lambda/aes-siem-es-loader in CloudWatch Logs.

Does it matter that I'm using gzip JSON from Firehose instead of parquet?

Incidentally, it looks like a separate and probably unrelated issue might be occurring that probably requires it's own issue. Please see this stack trace from the es-loader logs, looks related to Lambda PowerTools:
[ERROR] RuntimeError: No active exception to reraise
Traceback (most recent call last):
  File "/var/task/aws_lambda_powertools/metrics/metrics.py", line 184, in decorate
    response = lambda_handler(event, context)
  File "/var/task/aws_lambda_powertools/logging/logger.py", line 354, in decorate
    return lambda_handler(event, context, *args, **kwargs)
  File "/var/task/index.py", line 397, in decorator
    return func(*args, **kwargs)
  File "/var/task/index.py", line 464, in lambda_handler
    main(event, context)
  File "/var/task/index.py", line 491, in main
    process_record(recs)
  File "/var/task/index.py", line 546, in process_record
    raise

Figured it out, I believe the culprit was not having the custom sources selected under the Security Lake subscription. I can update the documentation and create a pull request for this, but the issue is resolved so I'll close it.


Remove version: Stackers.Stack version 3.18.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://binaries.getstack.app/builds/prod/win/x64/Stack Setup 3.18.1-x64.exe
Response status code does not indicate success: 530 ().
(Automated message - build 896)


Not working on Win10 v20H2 with iTunes 12

Hi,
is this application still working?
Didn't get the itunes status to show up in discord.
Windows 10 20H2
iTunes <IP_ADDRESS>
Discord Stable 71615 (583a822)

Same issue. Attempted to use for the first time tonight, can see the EXE running in Task Manager, opens iTunes, drops memory, suspends, and closes. iTunes remains open and prompts about scripting when closing.

Strange because it works for me

Working correctly here on Windows 10 21H2 LTSC, iTunes <IP_ADDRESS> and Discord stable 165943 (15bdaf0)

Closing due to iTunesRichPresence no longer being maintained.


ENH: Add optional progress reporting for voxel-based extraction

Update base.py to add progress reporting when computing voxel batches. Uses radiomics.getProgressReporter, which should be set to something like tqdm.tqdm to work. Only shows progress bar when logging level is at least INFO (so not when WARNING or higher).

Merging as the error in Travis CI is not due to changes in this PR.


mesh data model

This issue is to discuss the data model for mesh data.
Requirements
To start, some features I think are required:

easy access to vertices and edges (most analysis functions take this as input)
compatibility with spatial indexing (e.g., RTree, kdtree)
can annotate vertices with features (e.g., curvature)
some way to apply measurements to a collection of mesh objects (e.g., classification of objects)
can easily be converted to a Pytorch dataset for GNN (e.g., pytorch geometric)
can be written to a standarized format

Some features that are nice to have:

flexible backend for the arrays (e.g., cupy, numpy, etc.)

Supported workflows
Object classification
This workflow aims to classify objects by their shape

Start with a collection of images
Segment structure of interest
Generate one mesh per object
Classify each object based on the meshes. This may be done with a collection of "engineered features" (e.g., curvature) or some low-dimensional representation learned with CNNs/GNNs.

Mesh feature classification
This workflow aims to identify features of interest on an object (e.g., a particular synapse on a neuron or a functional part of a protein)

Start with a collection of images
Segment structure of interest
Generate one mesh per object
In each mesh, analyze the mesh to identify vertices that correspond with features of interest

Exploration of meshes and features*

Perform one of the analses described above
View the meshes of interest into napari and view objects based on their computed features (e.g., select from UMAP scatter plot)
Annotated objects (i.e., meshes) or parts of object (i.e., vertices on meshes) interactively through the viewer

Possible implementations
Towards this, I think we should have two types of objects:

Mesh contains the mesh and associated annotations
MeshCollection a set of meshes that can be analyzed together

Mesh object ideas
Feature table storage
I propose we store our vertex features in an AnnData table. AnnData tables give a lot of really nice data structures (dense array, sparse array,  DataFrame for categorical annotatinos) and will hopefully be compatible with the OME-NGFF format. Further AnnData is the table model used for many single-cell analysis libraries that have super nice tooling for exploring high dimensional data (e.g., scanpy).
Simple:
One idea is to have a simple Mesh object that holds the vertices and faces in arrays. The table is stored as an AnnData table. The advantage of this approach is that it is very simple and exposes the key data.
class Mesh:

 	# [N x d] array containing coordinates of all vertices
    vertices: np.ndarray

    # [M x 3] array giving the indices of each mesh element vertex
    face : np.ndarray

    # table where each row annotates a vertex (index matched to vertices)
    vertex_features: anndata.AnnData

Using trimesh:
Another idea is to use the trimesh Trimesh object to store the mesh data. We can still have passthroughs that give easy access to the faces and vertices of the mesh. The advantage of using Trimesh is that they do have some nice functionality for common measurements that provide some speedup via caching, etc. We would likely already depend on Trimesh, for the previously-mentioned measurement functions, so it seems reasonable to use Trimesh to store the vertices and faces of the mesh. We likely would still write the mesh to disk as indices and vertices. Trimesh also provides writers for typical mesh formats.
class Mesh:

    # trimesh object which holds the vertices and faces with a bunch of convenience methods
     data : trimesh.Trimesh

     # passthrough from Trimesh.vertices
     vertices: np.ndarray

     # passthrough for Trimesh.faces
     faces: np.ndarray

    # table where each row annotates a vertex (index matched to vertices)
    vertex_features: anndata.AnnData

    # we can expose other

    def __init__(vertices: np.ndarray, faces: np.ndarray, features: Union[pd.DataFrame, AnnData]):
         # the user doesn't need to create the Trimesh and AnnData objects on their own.

MeshCollection ideas
The simplest MeshCollection would be a list, which is appealing since it doesn't require any custom classes. However, I think there is value in grouping the meshes with the table of annotations on the meshes (e.g., what class they are, computed summary statistics, etc). Thus, I propose a simple class to group them together:
class MeshCollection:

    # a list of meshes
    meshes: List[Mesh]

    # table where each row annotates a mesh (index matched to meshes)
    features: anndata.AnnData

    # potentially some functions to convert to Pytorch datasets

    # potentially some functinos to make batch processing easy?

What do you all think, @alisterburt and @bbarad? I am especially curious if there are other workflows you think we should have in mind and if you think MeshCollection is a good idea.

Great summary Kevin!
My immediate questions are

are we being too limiting by not allowing annotations on edges/faces, is there any reason we can't shouldn't include this?
if GUI exploration is a primary usecase do we want to start directly with a SelectableEventedList for the MeshCollection

Overall the MeshCollection seems like a really useful concept - will you end up with lots of mesh collections if you compute lots of things in different ways? That might become unwieldy if serialisation of the whole MeshCollection in a file is the goal so I might rather keep the features separate but again, don't feel strongly :)

Good questions!

are we being too limiting by not allowing annotations on edges/faces, is there any reason we can't shouldn't include this?

I agree we want to include both of these eventually. I think it makes sense to add a Mes.face_features table at the start.
The reason I had punted on the edge annotations is that the way most meshes are defined (i.e., vertices + faces), the unique edges aren't really explicitly defined. For example if you have two triangles sharing an edge, from the faces+vertices, the shared edge would be defined twice and there isn't a clear mapping between the rows of the edge table and the edges.
However, I was just looking and Trimesh does have a unique_edges property that we could use. We would need to look to make sure the ordering is deterministic, but if it is, I think we could use that and have an edge_features at the start as well!
In that case, the class would look like:
class Mesh:

    # trimesh object which holds the vertices and faces with a bunch of convenience methods
     data : trimesh.Trimesh

     # passthrough from Trimesh.vertices
     vertices: np.ndarray

     # passthrough for Trimesh.faces
     faces: np.ndarray

     # passthrough for Trimes.unique_edges
     edges: np.ndarray

    # table where each row annotates a vertex (index matched to vertices)
    vertex_features: anndata.AnnData

    # table where each row annotates a vertex (index matched to vertices)
    face_features: anndata.AnnData

    # table where each row annotates a vertex (index matched to vertices)
    edge_features: anndata.AnnData

    # we can expose other convenience methods as necessary

    def __init__(vertices: np.ndarray, faces: np.ndarray, features: Union[pd.DataFrame, AnnData]):
         # the user doesn't need to create the Trimesh and AnnData objects on their own.

if GUI exploration is a primary usecase do we want to start directly with a SelectableEventedList for the MeshCollection

This is an interesting idea. My intuition is that we should keep the gui code and analysis code as separate as possible, so we wouldn't want to use an EventedList in the MeshCollection, but I am open to discussing if you think this would make things a lot easier down the road.
When I had said GUI exploration is a primary use case, I had more been thinking that we should have performant loading and sampling for speedy viz. For example, in the napari future where we have data loaders, we could make a simple data loader that more or less just wraps the MeshCollection.

https://github.com/kalemaria/pycurv/blob/master/pycurv/surface_graphs.py#L1075
using
https://graph-tool.skewed.de/


cf org-users and space-users shows nothing for cli created users

Not sure #361 is talking about the same but it looks like this happens for both UAA and cli created users.
Issue reproducible against PCF <IP_ADDRESS>, CF cli 6.10.0 and 6.11.0.
sgu-home:~ sgu$ cf create-user sgu-test sgu-test
Creating user sgu-test as admin...
OK
TIP: Assign roles with 'cf set-org-role' and 'cf set-space-role'
sgu-home:~ sgu$
sgu-home:~ sgu$ cf set-org-role sgu-test app OrgManager
Assigning role OrgManager to user sgu-test in org app as admin...
OK
sgu-home:~ sgu$ cf org-users app
Getting users in org app as admin...
ORG MANAGER
BILLING MANAGER
ORG AUDITOR
sgu-home:~ sgu$  cf set-space-role sgu-test app development SpaceManager
Assigning role SpaceManager to user sgu-test in org app / space development as admin...
OK
sgu-home:~ sgu$
sgu-home:~ sgu$ cf space-users app development
Getting users in org app / space development as admin
SPACE MANAGER
SPACE DEVELOPER
SPACE AUDITOR

@wgu I replied in the support ticket.  I cannot reproduce this.

I can't reproduce with:
cf version 6.10.0-a411bc2-2015-04-10T16:20:14+00:00
○ → cf curl /v2/info
{
"name": "vcap",
"build": "2222",
"support": "http://support.cloudfoundry.com",
"version": 2,
"description": "Cloud Foundry sponsored by Pivotal",
"authorization_endpoint": "https://login.a1.cf-app.com",
"token_endpoint": "https://uaa.a1.cf-app.com",
"min_cli_version": null,
"min_recommended_cli_version": null,
"api_version": "2.25.0",
"logging_endpoint": "wss://loggregator.a1.cf-app.com:4443"
}
2.25.0 = cf release 207
○ → cf target -o 1space
API endpoint: https://api.a1.cf-app.com (API version: 2.25.0)
User: admin
Org: 1space
Space: 1space
○ → cf create-user go-test1 go-test1
Creating user go-test1 as admin...
OK
TIP: Assign roles with 'cf set-org-role' and 'cf set-space-role'
○ → cf set-org-role go-test1 1spaace OrgManager
FAILED
Organization 1spaace not found
○ → cf set-org-role go-test1 1space OrgManager
Assigning role OrgManager to user go-test1 in org 1space as admin...
OK
○ → cf org-users 1space
Getting users in org 1space as admin...
ORG MANAGER
go-test1
BILLING MANAGER
ORG AUDITOR
Same thing afterj updating CLI
Previous Version:  cf version 6.10.0-a411bc2-2015-04-10T16:20:14+00:00
New Version:       cf version 6.11.1-4ef66f6-2015-04-20T21:15:38+00:00
|1.9.3-p484| london in ~
○ → cf create-user go-test2 go-test1
Creating user go-test2 as admin...
OK
TIP: Assign roles with 'cf set-org-role' and 'cf set-space-role'
|1.9.3-p484| london in ~
○ → cf set-org-role go-test2 1space OrgManager
Assigning role OrgManager to user go-test2 in org 1space as admin...
OK
|1.9.3-p484| london in ~
○ → cf org-users 1space
Getting users in org 1space as admin...
ORG MANAGER
go-test1
go-test2
BILLING MANAGER
ORG AUDITOR

Hi Greg,
Just in case the zendesk ticket does not send a notification, I have verified the issue does exist for 2.23.0 on vSphere with cf cli v6.11.1, v6.11.0 and v6.10.0. Same env v6.9.0 just worked fine. Since v2.23.0 is the current PCF <IP_ADDRESS> release version, is this explicitly been fixed in v2.25.0?
sgu-home:~ sgu$ cf -v
cf version 6.11.1-4ef66f6-2015-04-20T21:15:38+00:00
sgu-home:~ sgu$ cf org-users sgu-org
Getting users in org sgu-org as admin...

ORG MANAGER

BILLING MANAGER

ORG AUDITOR
sgu-home:~ sgu$ ~/Downloads/cf -v
/Users/sgu/Downloads/cf version 6.9.0-620f841-2015-01-20T18:22:58+00:00
sgu-home:~ sgu$ ~/Downloads/cf org-users sgu-org
Getting users in org sgu-org as admin...

ORG MANAGER
  sgu-test

BILLING MANAGER
  sgu-test

ORG AUDITOR

One thing noticed is that there is a blank line for both org manager and billing manager for v6.11.1.

Please supply the following:

The CF CLI version   (cf -v)
The CloudController API version (cf curl /v2/info)
A trace of the command you are using (CF_TRACE=true cf )

Here is the required output. Seems the missing part is querying for the actual user info after getting the user GUID.
sgu-home:~ sgu$ cf -v
cf version 6.11.1-4ef66f6-2015-04-20T21:15:38+00:00
sgu-home:~ sgu$ cf curl /v2/info
{
   "name": "vcap",
   "build": "2222",
   "support": "http://support.cloudfoundry.com",
   "version": 2,
   "description": "Cloud Foundry sponsored by Pivotal",
   "authorization_endpoint": "https://login.<IP_ADDRESS>.xip.io",
   "token_endpoint": "https://uaa.<IP_ADDRESS>.xip.io",
   "min_cli_version": null,
   "min_recommended_cli_version": null,
   "api_version": "2.23.0",
   "logging_endpoint": "wss://loggregator.<IP_ADDRESS>.xip.io:443",
   "user": "cf5c26b8-f648-473c-8015-cc431fa45911"
}

VERSION:
6.11.1-4ef66f6

REQUEST: [2015-04-30T09:55:00+08:00]
GET /v2/organizations?q=name%3Asgu-org&inline-relations-depth=1 HTTP/1.1
Host: api.<IP_ADDRESS>.xip.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.11.1-4ef66f6 / darwin

RESPONSE: [2015-04-30T09:55:02+08:00]
HTTP/1.1 200 OK
Content-Length: 6283
Content-Type: application/json;charset=utf-8
Date: Thu, 30 Apr 2015 01:55:02 GMT
Server: nginx
X-Cf-Requestid: 902d0f27-4b40-44fb-6265-9486e8092ba1
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 96de2a58-f222-44d1-7b49-b6a86bfbbd0e::a461549a-ba63-444b-a963-d52c0c70a0ac

{
  "total_results": 1,
  "total_pages": 1,
  "prev_url": null,
  "next_url": null,
  "resources": [
    {
      "metadata": {
        "guid": "931ebe92-bdc6-4876-9857-57c578704693",
        "url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693",
        "created_at": "2015-04-22T13:21:01Z",
        "updated_at": null
      },
      "entity": {
        "name": "sgu-org",
        "billing_enabled": false,
        "quota_definition_guid": "aa0fedae-1967-4bea-af4d-81e5d497d53b",
        "status": "active",
        "quota_definition_url": "/v2/quota_definitions/aa0fedae-1967-4bea-af4d-81e5d497d53b",
        "quota_definition": {
          "metadata": {
            "guid": "aa0fedae-1967-4bea-af4d-81e5d497d53b",
            "url": "/v2/quota_definitions/aa0fedae-1967-4bea-af4d-81e5d497d53b",
            "created_at": "2015-04-22T11:36:32Z",
            "updated_at": null
          },
          "entity": {
            "name": "default",
            "non_basic_services_allowed": true,
            "total_services": 100,
            "total_routes": 1000,
            "memory_limit": 10240,
            "trial_db_allowed": false,
            "instance_memory_limit": -1
          }
        },
        "spaces_url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/spaces",
        "spaces": [

        ],
        "domains_url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/domains",
        "domains": [
          {
            "metadata": {
              "guid": "286b44d1-c811-4a82-9ce2-2ed9c9eec331",
              "url": "/v2/domains/286b44d1-c811-4a82-9ce2-2ed9c9eec331",
              "created_at": "2015-04-22T11:36:32Z",
              "updated_at": "2015-04-22T11:36:46Z"
            },
            "entity": {
              "name": "<IP_ADDRESS>.xip.io"
            }
          }
        ],
        "private_domains_url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/private_domains",
        "private_domains": [

        ],
        "users_url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/users",
        "users": [
          {
            "metadata": {
              "guid": "30d38d95-9939-465f-b92d-aa0da67c3642",
              "url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642",
              "created_at": "2015-04-22T12:34:36Z",
              "updated_at": null
            },
            "entity": {
              "admin": false,
              "active": false,
              "default_space_guid": null,
              "spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/spaces",
              "organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/organizations",
              "managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_organizations",
              "billing_managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/billing_managed_organizations",
              "audited_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_organizations",
              "managed_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_spaces",
              "audited_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_spaces"
            }
          }
        ],
        "managers_url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/managers",
        "managers": [
          {
            "metadata": {
              "guid": "30d38d95-9939-465f-b92d-aa0da67c3642",
              "url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642",
              "created_at": "2015-04-22T12:34:36Z",
              "updated_at": null
            },
            "entity": {
              "admin": false,
              "active": false,
              "default_space_guid": null,
              "spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/spaces",
              "organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/organizations",
              "managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_organizations",
              "billing_managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/billing_managed_organizations",
              "audited_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_organizations",
              "managed_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_spaces",
              "audited_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_spaces"
            }
          }
        ],
        "billing_managers_url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/billing_managers",
        "billing_managers": [
          {
            "metadata": {
              "guid": "30d38d95-9939-465f-b92d-aa0da67c3642",
              "url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642",
              "created_at": "2015-04-22T12:34:36Z",
              "updated_at": null
            },
            "entity": {
              "admin": false,
              "active": false,
              "default_space_guid": null,
              "spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/spaces",
              "organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/organizations",
              "managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_organizations",
              "billing_managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/billing_managed_organizations",
              "audited_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_organizations",
              "managed_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_spaces",
              "audited_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_spaces"
            }
          }
        ],
        "auditors_url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/auditors",
        "auditors": [

        ],
        "app_events_url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/app_events",
        "space_quota_definitions_url": "/v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/space_quota_definitions",
        "space_quota_definitions": [

        ]
      }
    }
  ]
}
Getting users in org sgu-org as admin...

REQUEST: [2015-04-30T09:55:02+08:00]
GET /v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/managers HTTP/1.1
Host: api.<IP_ADDRESS>.xip.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.11.1-4ef66f6 / darwin

RESPONSE: [2015-04-30T09:55:03+08:00]
HTTP/1.1 200 OK
Content-Length: 1156
Content-Type: application/json;charset=utf-8
Date: Thu, 30 Apr 2015 01:55:03 GMT
Server: nginx
X-Cf-Requestid: 766262c0-fd5e-413c-5dec-fde981e6051f
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: c829c4cf-1b29-405e-6869-4e5dc211167c::2e05840f-2a09-4b6b-ab4a-4261a5243452

{
  "total_results": 1,
  "total_pages": 1,
  "prev_url": null,
  "next_url": null,
  "resources": [
    {
      "metadata": {
        "guid": "30d38d95-9939-465f-b92d-aa0da67c3642",
        "url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642",
        "created_at": "2015-04-22T12:34:36Z",
        "updated_at": null
      },
      "entity": {
        "admin": false,
        "active": false,
        "default_space_guid": null,
        "spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/spaces",
        "organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/organizations",
        "managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_organizations",
        "billing_managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/billing_managed_organizations",
        "audited_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_organizations",
        "managed_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_spaces",
        "audited_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_spaces"
      }
    }
  ]
}

ORG MANAGER

REQUEST: [2015-04-30T09:55:03+08:00]
GET /v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/billing_managers HTTP/1.1
Host: api.<IP_ADDRESS>.xip.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.11.1-4ef66f6 / darwin

RESPONSE: [2015-04-30T09:55:04+08:00]
HTTP/1.1 200 OK
Content-Length: 1156
Content-Type: application/json;charset=utf-8
Date: Thu, 30 Apr 2015 01:55:04 GMT
Server: nginx
X-Cf-Requestid: d00dadf8-54eb-4d6c-56c3-ebc373a9a2c4
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: bf40802d-8a42-43d9-5070-8bfd0ac78b73::881c4ac4-40b5-489b-b1fa-856e71185ff4

{
  "total_results": 1,
  "total_pages": 1,
  "prev_url": null,
  "next_url": null,
  "resources": [
    {
      "metadata": {
        "guid": "30d38d95-9939-465f-b92d-aa0da67c3642",
        "url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642",
        "created_at": "2015-04-22T12:34:36Z",
        "updated_at": null
      },
      "entity": {
        "admin": false,
        "active": false,
        "default_space_guid": null,
        "spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/spaces",
        "organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/organizations",
        "managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_organizations",
        "billing_managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/billing_managed_organizations",
        "audited_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_organizations",
        "managed_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_spaces",
        "audited_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_spaces"
      }
    }
  ]
}

BILLING MANAGER

REQUEST: [2015-04-30T09:55:04+08:00]
GET /v2/organizations/931ebe92-bdc6-4876-9857-57c578704693/auditors HTTP/1.1
Host: api.<IP_ADDRESS>.xip.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.11.1-4ef66f6 / darwin

RESPONSE: [2015-04-30T09:55:05+08:00]
HTTP/1.1 200 OK
Content-Length: 107
Content-Type: application/json;charset=utf-8
Date: Thu, 30 Apr 2015 01:55:05 GMT
Server: nginx
X-Cf-Requestid: 375b8bf8-c537-4b3e-4019-374a1d1d13cd
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: e4c65fec-ebb8-4db2-50d3-54f1ed304a0a::aaedabc7-2dc8-466e-abc0-0192b09ad3f8

{
  "total_results": 0,
  "total_pages": 1,
  "prev_url": null,
  "next_url": null,
  "resources": [

  ]
}

ORG AUDITOR

I am seeing the same issue. It doesn't appear to be an issue with the cli, but more an issue with the cloudcontroller api response object. The response object doesn't seem to contain the username field in the user.entity object, which the cli depends on.
unless im missing something.
https://github.com/cloudfoundry/cli/blob/master/cf/commands/user/org_users.go#L98
https://github.com/cloudfoundry/cli/blob/master/cf/api/resources/users.go#L11
"users": [
          {
            "metadata": {
              "guid": "30d38d95-9939-465f-b92d-aa0da67c3642",
              "url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642",
              "created_at": "2015-04-22T12:34:36Z",
              "updated_at": null
            },
            "entity": {
              "admin": false,
              "active": false,
              "default_space_guid": null,
              "spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/spaces",
              "organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/organizations",
              "managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_organizations",
              "billing_managed_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/billing_managed_organizations",
              "audited_organizations_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_organizations",
              "managed_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/managed_spaces",
              "audited_spaces_url": "/v2/users/30d38d95-9939-465f-b92d-aa0da67c3642/audited_spaces"
            }
          }
        ],

OK.  So, by default, this view is disabled.  You need to do two things to enable it.  Then you should get the list of usernames when you cf curl v2/users.

Set this property to true: uaa.scim.userids_enabled

uaa:clients should have a client that look like this (The authorities and authorized grant types keys are in addition to what's in there now):
cloud_controller_username_lookup:
authorities: scim.userids
authorized-grant-types: client_credentials
id: cloud_controller_username_lookup
secret: asdfjkl;


mongoose 4.0.1 Error: "Cannot read property 'prototype' of undefined"

Flow the prompt to check the lib/plugin.js, then there is the code
  if (mongoose.Query.prototype.deepPopulate == null) {
    patchMongooseQuery(mongoose)
  }

but, as if there is no mongoose.Query object in mongoose 4.0.1(may be 4.x.x), so it throw error: "Cannot read property 'prototype' of undefined"--as the code, mongoose.Query not be checked if it is null。but the version @1.1.0 is work for mongoose 4.x.x, may be because the dependence is<EMAIL_ADDRESS>but @2.0.0 the is depend on<EMAIL_ADDRESS>so, wish it is help, and expect to fix it , mongoose-deep-populate is awesome work~

Which version of Mongoose and mongoose-deep-populate are you using?

Hi, I am also seeing this problem. I just upgraded mongoose-deep-populate to 2.0.0 and it's having the same problem as above when used with mongoose 4.1.3 (latest as of now).
process.nextTick(function() { throw err; })
^
TypeError: Cannot read property 'prototype' of undefined
Downgrading back to 1.1.0, until there is a fix. I tried to define it in the schema as a plugin, same as in 1.1.0, but I get that error. Please fix

Did you load mongoose-deep-populate correctly per 2.0 breaking change? That is:
var deepPopulate = require('mongoose-deep-populate')(mongoose)

Thanks ---I missed that. Should be in BIG BOLD RED letters! lol ;)

Agreed. I'll highlight that.


add impl for list and tuple getitem

Closes #227

lgtm

This needs to also look for the __index__ method.


Conflict/Can't work with jQuery included in project

You can know more here: https://github.com/Software-js/WS.js/issues/248#issuecomment-215541731

Resolved

You've not referenced a commit to this issue, and/or not referenced the commit on this issue. The two ways are the same and needed on a collaborative community.

You can close an issue directly from a commit, by simple typing title "fixed #4".
"wrapp in iife" and "remove line" are not clear titles for commits and don't explain whats happening, introducting and/or fixing.
Other thing, you're wanting remove my marks in this repository. I've comment my closed issue and pull request, which are closed but currently active. This isn't correct to your contributors.


cn2an library raises exception for season names with Arabic numerals (strict mode)

The current implementation of the cn2an library in strict mode throws a ValueError exception when encountering season names containing Arabic numerals. This issue is observed while processing season name like "第2季".
$ python subtitle_downloader.py https://www.iq.com/play/%E7%84%A1%E8%81%B7%E8%BD%89%E7%94%9F%EF%BD%9E%E5%88%B0%E4%BA%86%E7%95%B0%E4%B8%96%E7%95%8C%E5%B0%B1%E6%8B%BF%E5%87%BA%E7%9C%9F%E6%9C%AC%E4%BA%8B%EF%BD%9E%E7%AC%AC2%E5%AD%A3-1pq3ov9tyy4?lang=zh_tw
Traceback (most recent call last):
  File "/home/user/Subtitle-Downloader/subtitle_downloader.py", line 151, in <module>
    main()
  File "/home/user/Subtitle-Downloader/subtitle_downloader.py", line 140, in main
    service['class'](args).main()
  File "/home/user/Subtitle-Downloader/services/iqiyi/iqiyi.py", line 370, in main
    self.series_subtitle(
  File "/home/user/Subtitle-Downloader/services/iqiyi/iqiyi.py", line 118, in series_subtitle
    season_name = cn2an(
  File "/home/user/.local/lib/python3.10/site-packages/cn2an/cn2an.py", line 58, in cn2an
    sign, integer_data, decimal_data, is_all_num = self.__check_input_data_is_valid(inputs, mode)
  File "/home/user/.local/lib/python3.10/site-packages/cn2an/cn2an.py", line 155, in __check_input_data_is_valid
    raise ValueError(f"当前为{mode}模式，输入的数据不在转化范围内：{data}！")
ValueError: 当前为strict模式，输入的数据不在转化范围内：2！

Seems this will also happen in other platform with the same parsing logic.
https://github.com/wayneclub/Subtitle-Downloader/blob/2c4d4ca45ca2234a9688266648b380585340d260/services/iqiyi/iqiyi.py#L115-L121

The current implementation of the cn2an library in strict mode throws a ValueError exception when encountering season names containing Arabic numerals. This issue is observed while processing season name like "第2季".
$ python subtitle_downloader.py https://www.iq.com/play/%E7%84%A1%E8%81%B7%E8%BD%89%E7%94%9F%EF%BD%9E%E5%88%B0%E4%BA%86%E7%95%B0%E4%B8%96%E7%95%8C%E5%B0%B1%E6%8B%BF%E5%87%BA%E7%9C%9F%E6%9C%AC%E4%BA%8B%EF%BD%9E%E7%AC%AC2%E5%AD%A3-1pq3ov9tyy4?lang=zh_tw
Traceback (most recent call last):
  File "/home/user/Subtitle-Downloader/subtitle_downloader.py", line 151, in <module>
    main()
  File "/home/user/Subtitle-Downloader/subtitle_downloader.py", line 140, in main
    service['class'](args).main()
  File "/home/user/Subtitle-Downloader/services/iqiyi/iqiyi.py", line 370, in main
    self.series_subtitle(
  File "/home/user/Subtitle-Downloader/services/iqiyi/iqiyi.py", line 118, in series_subtitle
    season_name = cn2an(
  File "/home/user/.local/lib/python3.10/site-packages/cn2an/cn2an.py", line 58, in cn2an
    sign, integer_data, decimal_data, is_all_num = self.__check_input_data_is_valid(inputs, mode)
  File "/home/user/.local/lib/python3.10/site-packages/cn2an/cn2an.py", line 155, in __check_input_data_is_valid
    raise ValueError(f"当前为{mode}模式，输入的数据不在转化范围内：{data}！")
ValueError: 当前为strict模式，输入的数据不在转化范围内：2！

Seems this will also happen in other platform with the same parsing logic.
https://github.com/wayneclub/Subtitle-Downloader/blob/2c4d4ca45ca2234a9688266648b380585340d260/services/iqiyi/iqiyi.py#L115-L121

Fixed, please try again.

Confirm fixed, thanks.


Hi, there is a problem with installing the addon.

Blender version 3.6.1
(P.s Thank you in advance)

Sorry, the most recent version of the plugin is broken; you could try an older version.

V 3.6.0
What else could be the problem._.

Oh, sorry, you were talking about the plugin... I'm just sitting through a translator

Thank

Great, let me know if you need anything else.


Reassess annotation cols in default fileview

Isn't the default (local) project fileview for the study project lead? Thus it should be most useful for helping the PL track and organize things. Yet default fileviews created for the project currently specify many columns that are not even in the annotation templates, or only in 1-2 specialized templates, such as consortium, accessTeam, isXenograft, modelOf -- not useful for many projects today. This configuration was probably based on certain projects (e.g. ones with consortia) but don't represent the many of the projects today. (Yes, I should have questioned these columns even more at time of porting the old code.)
The view configuration should be more minimal, and there should be instructions for how the project lead can add extra columns to their view that they may want. Basically, start with what a PL would actually facet on.
Commonly Informative
These should be included by default.

resourceType
assay
dataType
dataSubtype
diagnosis
tumorType
fileFormat
individualID
specimenID
sex
age (we don't include ageUnit because the lead knows what unit they used for measurement)
nf1Genotype
nf2Genotype
species
progressReportNumber
modelSystemName
experimentalCondition

Unclear Information Value

isCellLine
isMultiSpecimen
isMultiIndividual

Low Information Value
These don't actually provide any real information that help with practical data/file management and should be hidden.

fundingAgency:  Unless the data has multiple associations for this property (not the case nowadays), why display this? The project lead already knows what it is and is not going get anything from possible faceting on this.
studyName: Same as above.
studyId: Same as above.
isXenograft: Should only be added if the study does involve transplantation.
transplantationType: Same as above.
compoundName: Should only be added if the study involves drug screens.
modelOf: This is deprecated anyway.
readPair: Should be something that is added back if applies/desired.
accessType: Does any project use this anymore?
accessTeam:  Same as above.
consortium: Same as above.

This configuration was probably based on certain projects (e.g. ones with consortia) but don't represent the many of the projects today.

I think that it's even worse than that - it's probably based on just one project and was propagated from there. I am not entirely sure why the original list was the way it was as these were configured by someone else, but it's definitely been a thing on my mental list to revisit at some point.
I agree with your list - the 'commonly informative' ones are probably the ones that should be there at the outset.
PIs can easily  pull in all of the project-relevant annotations/ additional columns after they annotate files by clicking "add all annotations" in the fileview schema config, so I think a more minimal schema to start makes sense.


The UI of index.html is breaking at the search glass icon

** PLEASE READ THIS BEFORE FILING AN ISSUE **
Feature Requests / Breaking Changes in mdl-1.x
The MDL core team has actively begun work on the next major version of MDL, dubbed MDL v2. Because we are a small team that's hyper-focused on delivering the best Material Design Library possible for the web, it is highly unlikely that we will be actively working on new features or making backwards-incompatible changes for MDL as it currently exists.
If there is a non-breaking feature you would like to see implemented in mdl-1.x and are willing to contribute, we'd be happy to offer assistance with you doing so. But we will not personally be actively working on said features.
While we are just getting started with our next version of MDL, you can see our current progress on master as well as an overview of the direction we're headed in our (WIP) developer guide as well as our initial POC branch for our new architecture.
If you're interested in information for a specific MDL v2 component, check out our v2-component issues to see which v2 milestone it's associated with and feel free to subscribe to that issue for updates.
Bugs
Please include the following information with your bug report:

What MDL Version are you using? (please be specific, e.g. major.minor.patch)

What browser(s) is this bug affecting (including version)?

What OS (and version) are you using?

What are the steps to reproduce the bug? Can you create a plunker/codepen/jsfiddle which reproduces it?

What is the expected behavior?

What is the actual behavior?

Any other information you believe would be useful?

Just assuming from the title (since the bug report info was never provided) this is a duplicate of #4690. If it isn't, please provide the requested bug report information from the template.
Thank you.


Is there a [problem in precision_recall_curve?

Dear sir
Thanks for your excellent work in the scikit-plot. I am confused in the function of precision_recall_curve. As we all know,the PR curve goes through two points:(0,1) and(1,0).But I used the test code to draw the curve and found that the curve does not goes the point of (1,0).I used the below code and get the curve.

import scikitplot as skplt
rf = GaussianNB ()
rf = rf.fit(X_train, y_train)
y_pred = rf.predict(X_test)
skplt.metrics.plot_confusion_matrix(y_test, y_pred, normalize=True)
plt.show()

I'm sorry I can't get your question idea. You want to plot the precision_recall curve, but your code is just using plot_confusion_matrix for confusion matrix. In fact, if you want to use plot_precision_recall_curve, you have to make your prediction probability based on your test data, just like this:
prob = rf.predict_proba(X_test) skplt.metrics.plot_precision_recall_curve(y_test, prob) plt.show()


remove nixpkgs pinning

For a 140 lines script that only depends on 3 dependencies it seems rather an
overkill to pin nipxkgs as it will result in a huge downloads and more
maintainance burdens to keep .nixpkgs-version.json up to date. All libraries
used here are mature and not likely to break across different versions. Also if
they would break it would be better to catch this early in the repository by
having an up to date nixpkgs revision rather than a pinned one.
Signed-off-by: Jörg Thalheim<EMAIL_ADDRESS>

Fair enough!


Add release notes for PR 4617

See #4617.

Since #4617 has been merged in October, it will be part of the Opencast 15 release and this should probably go into r/15.x, not develop. Other than that, this is good to be merged.

Since #4617 has been merged in October, it will be part of the Opencast 15 release and this should probably go into r/15.x, not develop. Other than that, this is good to be merged.

You're right, but since Arne already picked this up in #5433, I can just close this. :D


Minor correction when creating a new  Warehouse

Please change the wording in step 5 from "In the Site field, type a value."  to "In the Site field, select a value from drop down."
Obviously they can not type anything so the sentence gives a false impression that they can think of a site on the fly and AX will create that site.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 67cb777c-3e51-ca6d-10aa-f813f08c99f1
Version Independent ID: 8e7a6426-4a9d-821e-aa46-f4cb0d8bd3c0
Content: Configure locations in a WMS-enabled warehouse - Supply Chain Management | Dynamics 365
Content Source: articles/supply-chain/warehousing/tasks/configure-locations-wms-enabled-warehouse.md
Service: dynamics-365-supply-chain
Product: ****
Technology: ****
GitHub Login: @perlynne
Microsoft Alias: perlynne

@kamaybac, please review.

@Bijan-Ghofranian - Thank you for the feedback. While the field is a drop-down, you can still type in the value for the site if you prefer to do so.


Add text-to-speech

[ ] Find API (Amazon Polly?)
[ ] Implement
[ ] Extra: add caching

Simplest way, without caching:
https://stackoverflow.com/questions/9893175/google-text-to-speech-api/10054006#10054006

var msg = new SpeechSynthesisUtterance("There's an easier way!");
msg.lang = 'en-US';
window.speechSynthesis.speak(msg);

https://caniuse.com/#search=SpeechSynthesisUtterance

So, will we do that on client side? If yes then this is perfect task for someone new from front-end section.


devicetree: make DT_..._REG_SIZE return unsigned

Simiarly to f98fde07b30, make the SIZE macros return unsigned literal values.

Not much drama on this one apparently, should have probably included it with the addr one, ah well...