Test Cases & Scenarios is incorrect

The section of understanding of Test Cases and Scenarios is incorrect:

"Test Cases are clearly written and documented"

Depends on what test technique you are using. Some test techniques don't use written words, they use diagrams instead. Others like combinatorial and domain testing use only values (numbers, words, letters, characters, etc).
Unless you are doing old school, traditional test management, you shouldn't structure test cases as procedures. If you are mainly using exploratory testing your documentation will look a whole lot different than someone doing traditional test management.

"you can cover hire possibilities"

What does this mean?

The section of understanding of Test Cases and Scenarios is incorrect:

Test cases creation is not a mandatory step for each and every single test iteration, however, as a test engineer you should have a basic understanding of it, or else you will be running some random tests without a benchmark and release bugs.
P.S This roadmap is for the whole development community. Some people are not there yet in terms of skills and what is needed to start. Same as you documenting a readme file for a package, you should assume zero understanding.

Unless you are doing old school, traditional test management, you shouldn't structure test cases as procedures. If you are mainly using exploratory testing your documentation will look a whole lot different than someone doing traditional test management.

Old school "AKA" as fundamentals are always and forever required to build the experience you need. I am not sure what a fresher would do if you mentor him
Read the "About" section for this repository
The starting point of your career as a Software Quality Assurance Engineer | Quality Automation Engineer

What does this mean?

typo

Just to be clear, old school doesn't mean fundamentals. Old school means taught in the 80s and in many cases no longer applicable, especially if you want to succeed today. I teach software testing fundamentals, I don't teach this.


1.10

Which Azure service should you use to store certificates?
A. Azure Security Center
B. an Azure Storage account
C. Azure Key Vault
D. Azure Information Protection

C


DOC: Update action commit SHA to the 0.6.0 tag

For stability provide the commit SHA that corresponds to the 0.6.0 tag (ccf29c805b5d0c1dc31fa97fcdb962be074cade3) for users to pin to.

Thanks!


Allow converting mol blocks directly to InChI

The InChI API has a function that allows direct generation of InChI strings from Mol blocks; this PR exposes that function to the RDKit.
Aside from being useful for debugging purposes, there are times when it would be nice to be able to get InChI strings directly without having the RDKit parse the mol block

I just verified this one by running MolBlockToInChI() on all of the mol blocks in ChEMBL_24. With the exception of 9 cases where ChEMBL doesn't have an InChI and the 20 cases where the RDKit won't build a molecule from the mol block (not directly relevant to this test, but part of my validation setup), everything matches.

Very nice!
Envoyé de mon iPhone

Le 13 févr. 2019 à 07:54, Greg Landrum<EMAIL_ADDRESS>a écrit :
I just verified this one by running MolBlockToInChI() on all of the mol blocks in ChEMBL_24. With the exception of 9 cases where ChEMBL doesn't have an InChI and the 20 cases where the RDKit won't build a molecule from the mol block (not directly relevant to this test, but part of my validation setup), everything matches.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Generated duplicate inbound route

Bug description
When debugging, i find there are duplicate route generated
 istioctl pc route httpbin-66cdbdb6c5-rdl2p
NOTE: This output only contains routes loaded via RDS.
NAME                                                          VIRTUAL HOSTS
80                                                            3
istiod.istio-system.svc.cluster.local:853                     1
InboundPassthroughClusterIpv4                                 1
                                                              1
kube-dns.kube-system.svc.cluster.local:9153                   1
istio-ingressgateway.istio-system.svc.cluster.local:15021     1
InboundPassthroughClusterIpv4                                 1
inbound|8000|http|httpbin.default.svc.cluster.local           1
InboundPassthroughClusterIpv6                                 1
InboundPassthroughClusterIpv6                                 1
inbound|8000|http|httpbin.default.svc.cluster.local           1
8000                                                          2
15010                                                         2
15014                                                         2

[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
client version: 1.7.0-alpha.0
control plane version: 1.7.0-alpha.0-37119973c952151e269110170f2fda8c6a34fb5e
data plane version: 1.7.0-alpha.0 (3 proxies)
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)

It may be inline routes for different filter chains

These are inline routes, I think this is intended

I have the same question. All inbound routes are double. I have compared the specific configurations of these routes, and they are all the same. I think it's a bug, or at least needs to be investigated. This problem still exists in version 1.15.


in azure-cli 2.2.0, when add '--output table' option, encounter an error. It doesn't exist in old version 2.0.*

azure-cli : 2.2.0
When run command:
az aks get-upgrades --resource-group  --name  --output table
It reports an error:   Table output unavailable. Use the --query option to specify an appropriate query. Use --debug for more info.
Please refer to the screenshot as below:

aks

I'm not able to reproduce this on 2.3.1
➜  ~ az aks get-upgrades -g contosofin-rg -n contosofinaks --output table
Name     ResourceGroup    MasterVersion    Upgrades
-------  ---------------  ---------------  -----------------------
default  contosofin-rg    1.16.1           1.16.7, 1.17.3(preview)

Could you try an upgrade and repro?

Hello! Please try again with the latest Azure CLI version. Feel free to reopen an issue if it still doesn't work.
https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest


(node:47411) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 pipe listeners added to [Request]. Use emitter.setMaxListeners() to increase limit

The whole code is working but I get this warning very every 2 seconds, '(node:47411) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 pipe listeners added to [Request]. Use emitter.setMaxListeners() to increase limit'. Is there a way to fix this somehow?

Lower the emitters down bruh, Dm me if you cant do that S_waraj#7777

Yom having the same issue, could you hmu on discord Azael#2282, need help with doing that

Yom having the same issue, could you hmu on discord Azael#2282, need help with doing that

Sent a fr req, seems that your dms are closed so i cant dm you

Same code is working but it shows  '(node:47411) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 pipe listeners added to [Request]. Use emitter.setMaxListeners() to increase limit'.

i don't care this is dead


Bug when running  manage.py

Ran installation just like in the documentation and got this error:
This project is amazing, keep up the good work!
Traceback (most recent call last):
File "manage.py", line 4, in
from quantifiedcode.settings import settings
File "/home/meine_joaolucas/quantifiedcode/quantifiedcode/settings/init.py", line 1, in
from .base import * #noqa
File "/home/meine_joaolucas/quantifiedcode/quantifiedcode/settings/base.py", line 12, in
from quantifiedcode.helpers.settings import Settings, load_settings
File "/home/meine_joaolucas/quantifiedcode/quantifiedcode/helpers/settings.py", line 13, in
from checkmate.settings import Settings as CheckmateSettings
ImportError: No module named checkmate.settings

Hey @LukasMeine , thanks for opening this issue! @marcinguy (who recently installed QuantifiedCode and may be able to help you) can you give some pointers here?
From looking at the traceback it seems that checkmate is not properly installed or not on the PYTHONPATH, you can check this by opening python3 and importing the module import checkmate.settings.


Cannot read property 'getSelection' of undefined when unmounting React component

Hi,
first of all great little library! Congrats. We are trying to create a React component that will serve as a wrapper around share-this library. We have an issue when unmounting that component. It says
Cannot read property 'getSelection' of undefined

Here is the codesandbox that you can take a look https://codesandbox.io/s/0pl29v3p5l
Steps to reproduce:

Select a text
Clear selection by clicking outside of the text
Click on toggle button

Expected results

No error is thrown

All right, first of all: sorry if I'm super-late, but I really had to wait for the holidays to look into it! 😕
And second, I currently have a very crappy connection! 😫
Anyway, at a first glance it's not just a React thing, it's more like a general bug caused by the workaround for Safari's selectionchange bug. I'll look into it soon, I might have a solution on hand.
Thank you for reporting this, and happy holidays!


Duplicate errors

Started writing this issue, but in middle of it figured out how to do this. Decided to post it anyway, If anyone else is having similar issues, because I couldn't find too many discussions about this.
I originally had a custom exception_handler and error_handler, that sent all errors/exceptions to an e-mail. After migrating to sentry (which btw is excellent:), I got rid of the email stuff, but I am still using exception handlers for better formatting. Also, to be able to catch php errors, I am turning all errors into exceptions - for example to catch division by zero error.
function sp_error_handler($errno, $errstr, $errfile, $errline)
{
    // @ used
    if (error_reporting() === 0) {
        return false;
    }

    // Throw all the errors as exceptions, so they can be handled as they should
    throw new ErrorException($errstr, 0, $errno, $errfile, $errline);
}

When and error was thrown, we got two entries in sentry:

Which is basically the same error, only second one is from sp_error_handler function. Solved it by creating a custom class SpErrorException that extends ErrorException and throwing it instead of ErrorException and then adding excluded_exceptions parameter to sentry init like this:
    Sentry\init([
        'dsn' => $_ENV['SENTRY_DSN'],
        'release' => Config::$items['git_commit_hash'],
        'environment' => Config::$items['environment'],
        'attach_stacktrace' => true,
        'excluded_exceptions' => [
            '\Core\Models\SpErrorException'
        ]
    ]);

Now, when php "throws" error, sentry catches it, then custom handler also catches it, throws our custom exception, but sentry ignores that exact exception class.

Hey @gintsmurans, thanks for sharing this! I'm sure somebody else might find this useful.
I am going to close this "issue" since otherwise we will keep it open forever (discussions may never end) and you have found (in my eyes the correct) solution to this problem.
Feel free to open up an issue if you think based on this discussion you'd like to propose an enhancement to the SDK.

Nice, thanks for not just deleting it. :)


gh-1266 - getAllGraphIds now returns unmodifiableSet

Codecov Report

Merging #1324 into develop will not change coverage.
The diff coverage is 100%.

@@            Coverage Diff             @@
##             develop    #1324   +/-   ##
==========================================
  Coverage      65.35%   65.35%
  Complexity      1537     1537
==========================================
  Files            690      690
  Lines          22006    22006
  Branches        2734     2734
==========================================
  Hits           14383    14383
  Misses          6502     6502
  Partials        1121     1121

Impacted Files
Coverage Δ
Complexity Δ

...gov/gchq/gaffer/federatedstore/FederatedStore.java
96.53% <100%> (ø)
0 <0> (ø)
:arrow_down:

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 9016c29...22f02e0. Read the comment docs.


Problem with building

Hello,
I really don't know how to solve this problem: ld.lld: error: cannot find entry symbol xecute-only; defaulting to 0x2D824
https://prnt.sc/wnn2ly
Thanks really if you know how to fix it
Yours truly,

Looks like this may be an incompatibility with the latest NDK (r22). Could you test if using the previous version (LTS r21d) fixes this issue?

Looks like this may be an incompatibility with the latest NDK (r22). Could you test if using the previous version (LTS r21d) fixes this issue?

Ohhh thank you so much, I hadn't thought of that.
Compilation ok,
thank you so much

Ohhh thank you so much, I hadn't thought of that.
Compilation ok,
thank you so much

This also worked for me. I had the same issue.


GraphQL mutation for complete shipment flow

Implement createShipment mutation
Turn former crud test into an endpoint test
Move retrieval of agreement bases into dedicated function
Extend test data for bases
Validate that bases for new shipment are part of transfer agreement
Add test data for unidirectional agreement
Validate that shipment-creating user is source org member for unidirectional agreement
Use convenience function for verifying erroneous request
Implement cancelShipment mutation
Extend test data with canceled shipment
Add base class for invalid resource state exceptions
Validate that shipment state is Preparing when about to cancel
Implement sendShipment mutation incl. shipment state validation
Make signature for update_shipment function more explicit
Make fields for ShipmentUpdateInput nullable
Implement updateShipment mutation for source/target base
Use separate function for validating bases as part of agreement
Validate bases as part of agreement when updating shipment
Specify boxes by label identifier in ShipmentUpdateInput
Add endpoint test for updating shipment with prepared boxes
Remove crud test
Use convenience function for shipment-update tests
Extend test data with another box
Discard boxes for shipment update if not located in source base
Validate that shipment state is Preparing when about to update
Extend shipment test data
Validate that user is member of shipment-creating org when about to send
Extend box test data
Validate box state when about to be updated for shipment preparation
Use dedicated function to update shipment with prepared boxes
Implement returning of prepared boxes into stock
Validate box state before removing box from shipment
Extend test data
Implement updating of target location/product when receiving box
Move assert_bad_user_input function to test.utils module
Validate that checking-in user is member of target base organisation
Extend shipment detail test data
Validate shipment state before updating shipment detail
Remove updating of shipment source base
Validate that user is member of source organisation when updating shipment
Remove two boxes from shipment in test
Extend box test data
Prevent removing arbitrary MarkedForShipment box from shipment
Introduce convenience assert function
Validate that location is in target base when updating shipment detail
Validate that product is in target base when updating shipment detail

 Implement GraphQL mutations for update-shipment flow, part II


Images in docs need recolored

Expected Behavior
The images at https://docs.gradle.org/7.6-rc-1/userguide/userguide.html should not be color scaled to meet their brand guidelines.
Current Behavior
They are in our colors.

This has been fixed and will be public in 8.3: https://docs.gradle.org/nightly/userguide/userguide.html


Add redirect functionality for once upload is complete

This change redirects the user to the 'processing your records' placeholder page once the s3 upload has completed. It is done using a second hidden form on the upload page, the action of which is to render the page that the user is redirected to. This hidden form is only submitted once the upload has completed.
This change still needs tests to be added to it.

Accidentally made a new branch rather than using the one I was using originally due to working on a different computer. Have now amended this.


KeyError: 'data'

Hi
I meet issue when deploying wazuh agent as daemonset, and here the error from the pod
Traceback (most recent call last):
  File "/var/ossec/./register_agent.py", line 289, in <module>
    agent_id, agent_key = add_agent(node_name)
  File "/var/ossec/./register_agent.py", line 174, in add_agent
    status_code, response = wazuh_api(
  File "/var/ossec/./register_agent.py", line 91, in wazuh_api
    token = json.loads(response.content.decode())["data"]["token"]
KeyError: 'data'

can you help  me on this ?
thank you

hi @pyToshka thanks for your feedback, there was a typo when I create the secret file
thank you


Enforce correct type for ValidatorScript

i.e. toValidatorScript :: CompiledCode(Data -> Data -> PendingTx -> Bool) -> ValidatorScript, as opposed to the current thing which just takes any old opaque Script.

Done.


BUG - Scroll anchors are set to top option rather than header

BUG: Quick scrolling using the alphabetical scroll, jumps the list to the top option rather that the header of that selected option
DESCRIPTION
When using the alphabetical quick scroll, the first item of the selected group is used as the anchor and jumps to the top of the page. This butts the first item up to the top of the page creating an odd UX. The group header should be used as the anchor when scrolling through groups.
Pages this affects:

/editsnack
/slackname

Steps to reproduce:

Navigate through the image recognition steps to reach the /editsnack page
Click and hold on the alphabetical scroll bar and begin scrolling to any particular group (eg 'G')
BUG - List jumps the first item of that group to the top, rather than using the group header ('G' in this example)

The same issue can be found on the /slackname page when scrolling through the slack handles
Expected behaviour:

The group header should be used as the anchor, meaning selecting a group will jump the group header to the top of the page rather than the first item.

Observed behaviour:

The first item is used as the anchor, meaning selecting a group will jump the first item to the top of the page rather than the group header

There should be some margin to the top of the anchor when you scroll to it. Otherwise it becomes pressed up against the header. The top of the list is a good example to follow. See screenshots.
Edit item - needs padding example

Edit item - top of list (good)

Slack name - needs padding example

Slack name - top of list (good)


Adjust to nf-core template

To make it more portable.

Notes :
There are some aspects of the nf-core template that I'd like to avoid, such as defining variables in the config file in such a way that they can not be overridden on the command line.
Other things can be adopted. For example, https://github.com/UPHL-BioNGS/Cecret/pull/221 uses the same process labels.

Guide for how to do this : https://github.com/apetkau/nf-core-assemblyexample


check to see if in a string before skipping a quote

Fixes #4287

I initially tried fixing it like this, but figured it wasn't quite optimal for typing (different) quotes within a string, so I ended up with edd8e6180a520

cool thanks for this :)


Authentication credentials on some APIs

Currently on some APIs that is oftenly accessed, such as nss we're authenticating with personal access token.
Should we refactor it so that it also allows registered api resources with their access key to access nss API?
Because personal token tied to user, while nss APIs are accessed by external services

Actually NSS APIs now use host based token - those are issued when host gets registered.

Some are still not, for example this one on nss
...
def groups_list
    token = AccessToken.valid_token params[:token]
if token
...

that API is used by 3rd party services, such as portal to fetch a user groups


Add SPID to toolbar

Adds the SPID of the current connection/editor to the bottom right bar, similar to SSMS, added as part of the connection status (in it's own section though):
Images:
Default connection SPID:

Query Editor (showing editor SPID):

Fixes: https://github.com/microsoft/azuredatastudio/issues/229
Companion PRs:
https://github.com/microsoft/sqltoolsservice/pull/2269
https://github.com/microsoft/sqlops-dataprotocolclient/pull/97

please make sure this is only displayed when the spid is available, other providers won't have this information at the beginning. also it would be nice to adjust comments to make it more generic and allow extensions to provider their own preferred display name instead of hardcoding it to spid.

for example: in Postgres it is called PID.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 11 (36.36%)  changed or added relevant lines in 4 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.006%) to 41.581%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/services/query/common/queryManagement.ts
0
2
0.0%

src/sql/workbench/services/query/common/queryRunner.ts
2
4
50.0%

src/sql/workbench/services/query/common/queryModelService.ts
1
4
25.0%

Files with Coverage Reduction
New Missed Lines
%

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

src/sql/workbench/services/query/common/queryManagement.ts
1
1.74%

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

Totals

Change from base Build<PHONE_NUMBER>:
-0.006%

Covered Lines:
30778

Relevant Lines:
69328

💛  - Coveralls

@Charles-Gagnon for now, yes

@smartguest

do we show tooltip for the PID toolbar item?
please add screenshot to show how it works with Posgtres

@alanrenmsft it is now part of the connection status where supported (currently only with MSSQL for queries), so the tooltip is a part of the connection status tooltip now with whatever name the provider uses.
For Postgres it is not implemented yet, so the connection status should remain the same for now (I will run a test on it later today)

@smartguest Could you update the screenshots in the initial description? Those appear to have the separate status item for the SPID, but looking at this it seems like we only display it as part of the tooltip of the connection info currently

@Charles-Gagnon Screenshots have been updated.

@smartguest Please make sure that you're showing the tooltips in the screenshots, not all of them have that (and since we only show the SPID there we need to see them to validate everything looks good)

Something to think about though @cheenamalhotra @kisantia is that with this kind of functionality added I think we should strongly consider removing the "global connection" functionality for the status bar item and only have it display for the current editor.
Not knowing what connection is "active" makes it very confusing - especially if there's an active editor but the connection is for some random connection in OE...

@cheenamalhotra Can you take a look and make sure all the latest changes look good to you?

@smartguest, @cheenamalhotra   How can I integrate this solution into my ADS Program?

If you're working with MSSQL provider, and you're listening to onConnectionComplete or onQueryComplete events you can read property serverConnectionId (available in azdata.proposed.d.ts) to get SPID for the connection in use.


Updated Mesos patches to extra/patches directory.

High-level description
This is similar to the changes made to the master branch via #2824.
Corresponding DC/OS tickets (obligatory)
Related tickets (optional)
Other tickets related to this change:
Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review):
[ ] Test Results:
[ ] Code Coverage (if available):

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

This repo has @mesosphere-mergebot integration. You can interact with the following commands.
@mesosphere-mergebot override-status
@mesosphere-mergebot merge-it
@mesosphere-mergebot label [Ready For Review |Holding |Request For Comment |Ship It |Work In Progress]
@mesosphere-mergebot bump-ee

PR creators can apply one of  [Ready For Review |Work In Progress]. Owners can apply any label.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review

@karya0 Can you please update https://github.com/dcos/dcos/blob/1.10/CHANGES.md as well? In a separate PR is fine.

@rukletsov : As with the corresponding 1.11 PR, I don't think we need changelog entry as there are no code changes as such.

Applying the ship-it label. The EE failure is on teamcity/dcos/test/aws/onprem/static/strict which is no longer marked required.

@mesosphere-mergebot label ship-it


feat: migrate runner to async db

Signed-off-by: Alex Chi<EMAIL_ADDRESS>finish remaining works of https://github.com/singularity-data/sqllogictest-rs/pull/2

Note that this patch results in API change &self -> &mut self, so the next version should be tagged as v0.3.


Support arrow.LIST in data frame.Collect()

What changes were proposed in this pull request?
This is a simple change to add support for arrow.LIST in dataframe.Collect()

Why are the changes needed?
Currently get unsupported message in a LIST is used unsupported arrow data type LIST in column %d

Does this PR introduce any user-facing change?
No

How was this patch tested?
make test plus have tested with lists of integers and strings

This doesn't work and I can't find a way to make it work.  (arrow is too obscure for me to work out)
What I want is an array of structs from a dataframe.  Using a work around to encode lists in records as json,  the following allows me to achieve what I want.  Closing.
func collectStruct[T interface{}](ctx context.Context, df sql.DataFrame) ([]T, error) {
	rows, err := df.Collect(ctx)
	if err != nil {
		return []T{}, err
	}

	schema, err := df.Schema(ctx)
	if err != nil {
		return []T{}, err
	}

	res := make([]T, len(rows))
	for i, row := range rows {
		vals, _ := row.Values()
		u := map[string]interface{}{}
		a := []interface{}{}
		for ci, v := range vals {
			// embedded lists don't work with spark-connect.  encode as json
			err = json.Unmarshal([]byte(fmt.Sprint(v)), &a)
			if err == nil {
				v = a
			}
			u[schema.Fields[ci].Name] = v
		}
		dbByte, _ := json.Marshal(u)
		_ = json.Unmarshal(dbByte, &res[i])

	}

	return res, nil

}


Streamline policyJSON Section

Split each potential step out into a separate variable that can be added
Centralized these variables in one section
Simplified how to change what gets deployed in Required, Recommended, and Complete
Reduced duplicate code, which reduces future modifications people need to make
This also helps streamline adding future steps for programs not currently included.

Sorry for all the PRs!  Sometimes I gotta get an idea out before I forget it.

Thanks, @rougegoat.
(I'll take a look once 1.10.0 is released.)

@rougegoat: Please give me some time to counsel with others on how best to proceed with this PR. Thanks.

Understandable.  I should note the main goal here was less rewriting it for à la carte style app installs and more reducing duplicate code.  That way, going forward if you have to update the Rosetta or Recon (for example) json snippets, you only have to adjust it in one place instead of four.  It's just that when this is done, it kind of opens the door to that functionality should that route be needed down the line.

I like the core concept of this idea a lot.


Add Normal-inverse-gamma distribution

Right now the Normal-inverse-gamma distribution is missing in scipy.stats. I think it qualifies as useful addition since it is the conjugate prior of the normal distribution in case mean and variance are unknown. Therefore the Normal-inverse-gamma distribution is important for Bayesian inference which has been for years and still is a trending topic in the domain of data science.

I agree, it would be great to have it.  In fact, there is already a (stalled) pull request for it that was started three years ago, https://github.com/scipy/scipy/pull/2648, so I'm closing this issue.
If you are interested in reviving that pull request, add your comments there.

@WarrenWeckesser You are linking the normal Normal-inverse Gaussian which is not equal to the Normal-inverse Gamma distribution or do I miss something here?

... or do I miss something here?

No, I'm the one who missed something.  Sorry about that!

@FlorianWilhelm  What methods and use cases do you have in mind for it?
Given that it is a bivariate distribution it would have to go with the multivariate distributions.  There is no strict pattern for those, AFAIK, and not much that can be inherited. So the features and implementation are mostly distribution specific. (in contrast to univariate models that has an elaborate "framework" and inherited methods, and have a more rigid structure).
scipy has a good collection of distribution, and I think it would be useful to keep expanding it also to new kinds of distributions. However, there is no established pattern and it would need some thoughts about what and how this should be implemented and what the API should be.

@josef-pkt I actually learned about that distribution when I was looking for the conjugate prior of a normal distribution with unknown mean μ and precision τ, check Wikipedia. Since I haven't found the Normal-inverse-Gamma distribution I started to think about if the conjugate prior of a normal distribution with known precision would also do it and in my bayesian inference related to user profiling and I think it does.
This means I am not working on the implementation of the Normal-inverse-Gamma right now but I still think it would be a valuable addition to Scipy.

Isn't normal-inverse-wishart the multivariate one, and normal-inverse-gamma for the univariate. And i am interested in adding it's implementation to Scipy, but what all methods need to be added for this.
I guess PDF, CDF and random variate generation are the necessary ones, so apart from them what more would be required?

I think that mode and some moments mean, variance, median and some conditional or marginal distribution properties would be useful. What's easily feasible depends on which distribution.
E,g, the univariate case the conditional and marginal distributions method could return the corresponding univariate distribution instance.
cdf in the general multivariate case will be difficult, rvs might be useful for users also to use MonteCarlo integration directly.
In general: IMO, it would be in the scope of scipy to provide the basic distribution facilities for basic Bayesian natural conjugates. I'm not a Bayesian anymore, but using the normal-normal conjugate pair assuming known variance is quite simple and useful (e.g. it's generalized Ridge regression or L2 penalized linear model.) Last week we had a question on the statsmodels mailing list on posterior from beta-binomial especially for the posterior confidence interval.
https://groups.google.com/d/msg/pystatsmodels/QaQc88bX718/7hONQuuADQAJ
There might be some license compatible packages in python or julia where some ideas for the implementation are available.

There's a julia implementation https://github.com/JuliaStats/ConjugatePriors.jl/blob/master/src/normalinversegamma.jl to refer. But I need some help in adding it to scipy, like under which module would this go in stats?

@ev-br and @rgommers  are now essentially the main maintainers for stats.
If it's just this distribution to be added, then I would suggest continuing with https://github.com/scipy/scipy/blob/master/scipy/stats/_multivariate.py
But given that the module is already getting a bit large, and if there is the possibility to add more conjugate priors like in the julia package, then I would start a new module, maybe a variation on conjugate

Hi!
Any update on this?

Any update on this?

Open PR is gh-6739, so that's the place to ask and where I will comment.

This was requested again in gh-13644. Seems like it would be a valuable addition.

Any update? : ( Im looking for this conjugate prior

From https://github.com/scipy/scipy/pull/18109#issuecomment-1458993415:

It looks like the distribution is an oddball - it doesn't fit our univariate distribution infrastructure or the multivariate distribution infrastructure.
To summarize (from #6739 and #6528), here's where we stand on the issue:

From https://github.com/scipy/scipy/pull/6739#issuecomment-261706648: Julia's ConjugatePriors.jl package considers both x and sig2 as random variates while R's PIGShift package considers only x as the random variate. Should SciPy follow the former or the latter convention?
From https://github.com/scipy/scipy/pull/6739#issuecomment-344051109: Would the implementation of the distribution be useful? The marginal distributions for x and sig2 are already implemented in SciPy and it's easy to compute the full distribution using those.
From https://github.com/scipy/scipy/pull/6739#issuecomment-344051109: The CDF on Wikipedia seems incorrect. Probably best to avoid implementing it before confirming the closed form is correct.

To start, I am leaning more towards considering this a multivariate distribution with x and sig2 themselves being univariate random variates. We can iterate over it to allow multivariate sig2. As far as the usefulness of the distribution is concerned, I think it has gotten more user requests and attention than most other distributions. So, usefulness seems justified. But it would be nice to get some more opinions on these points.
I think that covers the major points discussed on the issue and on the PR. Feel free to add to the above list if I missed anything.

I've played around with the PDF a bit, and it seems to only integrate to 1 if you integrate across both variables (there's also a large imaginary component, but I assume that's because of mpmath). That confirms that x and sig2 both have to be treated as random variates, and it also means some of the formulas need to be reworked. That being said, I'm not sure if returning a random sample of sig2 as well as x in the rvs method is the right way to go, since the sig2 can be obtained from the invgamma rvs method. Anyways, I'm getting ahead of myself. I know a lot of Scipy maintainers also work on Numpy, which is busy preparing for a 2.0 release. I don't want to overload them with work, so I'm not going to work on this until Numpy 2.0 comes out. In the meantime, discussion here is dead, so we should move the conversation over to the mailing list. @tirthasheshpatel, sound good to you?


Boardwalk beta 1.1 crashes on launch

Version of Boardwalk: Beta 1.1
Version of Android: 4.3
Device model: Samsung Galaxy Tab 4
Description of the problem: Whenever I try to load a Minecraft version by clicking launch, boardwalk will load the game for 1 second and then crash. This happens when running every version of Minecraft, and only  crashes on the beta releases, not the google play version. Unfortunately there is no crash log.

I got the same error

Try http://zhuoweizhang.net/Boardwalk/Boardwalk-release.apk, which should fix this.
The multiplayer fix crashes on Android versions below 4.4.4; I test on 5.0 only so didn't catch this.


can't CreateDirectory

FTP OS: CentOs
FTP Server: Vsftpd
Computer OS:  win7
My ftp path: /home/myftp/
error:
client.CreateDirectory("/eee");
ok:
client.CreateDirectory(" /home/myftp/eee");
why?

Maybe the FTP server is configured to disable clients modifying the root directories. If it's your server, check the config file.


Make components headless for Tag component

Description
Migrate styles from components to themes.
Since component styles in themes inherit styles from other components using mergeStyle etc., duplicate styles should be removed.
Problem Statement/Justification

Move static styles from component to theme.
Remove unnecessary fallback() calls.

Proposed Solution or API
No response
Alternatives
No response
Are you willing to participate in implementing this feature and create a pull request include the implementation?
None
Additional Information
No response

Duplication

https://github.com/yamada-ui/yamada-ui/issues/3940


unhandled rejection (?)

I'm confused how we're supposed to prevent an unhandled rejection:
export const signIn = ({email, password}) => ({
  type: 'SIGN_IN',
  payload: http.post('signin', {email, password})
});

const initialState = {inProgress: false, isLoggedIn: false};

export default (state=initialState, action) => {
  switch (action.type) {
    case 'SIGN_IN_FULFILLED': {
      return {...initialState, isLoggedIn: true};
    }

    case 'SIGN_IN_PENDING': {
      return {...initialState, inProgress: true};
    }

    case 'SIGN_IN_REJECTED': {
        const error = action.payload;
        alert(`${error.name}: ${error.message}`);
    }

    default: return state;
  }
};

According to https://github.com/pburtchaell/redux-promise-middleware/blob/master/docs/guides/rejected-promises.md, we now need to depend on redux-thunk? I switched to this lib to get away from that cruft.

I ended up with:
import isPromise from 'is-promise';
import ValidationError from '../util/ValidationError';

// From https://github.com/pburtchaell/redux-promise-middleware/blob/4.3.0/examples/complex/middleware/error.js
export default () => next => action => {
  if (!isPromise(action.payload)) {
    return next(action);
  }

  // Dispatch initial pending promise, but catch any errors
  return next(action).catch(error => {
    if (!(error instanceof ValidationError)) {
      // TODO :: use some kind of flash messaging
      alert(`${error.name}: ${error.message}`);
    }
  });
};

…but my build would be better with #169 patched.

I switched to this lib to get away from that cruft.

I would recommend using Redux Thunk so you can access the promise. It's a matter of opinion, but the Redux Thunk + this middleware is a very effective combination.
What exactly is your issue? #169 has been delayed, but a patch is in the works.

My issue was that I needed to write a custom middleware as a result of the v4 changes, to which #168 would be a big improvement. I also don't need thunks as everything is promise/async/await-based.

I also don't need thunks as everything is promise/async/await-based.

From your example,() => next => action => { ... } is effectively a thunk.
A thunk is a function that returns another function. Redux Thunk keeps your action creators dry by eliminating what you're writing, but if you prefer to write it, that's your preference.
Closing this issue to focus on #168.


updated warning in docs

++ added warning message in welcome page

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[credit card journey] Pool / seller listing design flows to pay with credit card

Need to have figma updated to show the full user journey flow for credit card.
Credit card as a payment method is supported for RETIRE of a pool or seller listing.

[ ] The user journey would start by selecting Credit Card from the Pay with: dropdown. The design should show this option activated (not coming soon anymore)

[ ] When credit card is selected, will want to update the icon on the form from USDC symbol to whatever icon we are using for Credit Card.

[ ] When credit card is selected, we need to indicate on the Total cost that the maximum allowed is $2000. Example below from the retirement aggregator:

[ ] On the strip checkout screen, need to swap out the Klima Infinity logo for a Carbonmark logo.

[ ] Next, on the Transaction complete screen, need to update Klima references again.

Return to klimadao.finance should be carbonmark.com/projects

swap out the Klima Infinity logo for a Carbonmark logo

Here are the updated wireframes: https://www.figma.com/file/5GewbdVaM1Q06CwHmF7d3F?node-id=890:29468&mode=design#480130483
Please note the following

I don't have access to the stripe account so I can't change the assets mentioned on the checkout screen or the transaction complete screen, that will have to be @Atmosfearful

we must update the help text under the "pay with" dropdown. the text is reflected in the wireframes.

we cannot process credit card payments exceeding $2,000, so there's a new use case in the user journey that displays this possible error state.

the dynamic price cards will have to change to show new units. instead of the usdc icon, we'll need to insert dollar signs. the wireframes show this change.

the approve modal changes to notify the user of our third party payment provider.

I don't have access to the stripe account so I can't change the assets mentioned on the checkout screen or the transaction complete screen, that will have to be @Atmosfearful

@theprofessora yup, understood that atmos will need to change those but is it still possible to mock those up using a screen shot current and swapping out the images?
This will be helpful as a design reference for the dev but also Liam is looking for design screen shots for his sales pitch deck

done


main: support generate declarative workflows

Versioned
https://github.com/user-attachments/assets/62257eef-d020-41e8-9766-92cb772c736c

Created yml file:
name: Atlas
on:
  push:
    branches:
      - main
    paths:
      - .github/workflows/ci-atlas.yaml
      - 'migrations/*'
  pull_request:
    paths:
      - 'migrations/*'
# Permissions to write comments on the pull request.
permissions:
  contents: read
  pull-requests: write
jobs:
  atlas:
    runs-on: ubuntu-latest
    env:
      GITHUB_TOKEN: ${{ github.token }}
    steps:
      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - uses: ariga/setup-atlas@v0
        with:
          cloud-token: ${{ secrets.ATLAS_CLOUD_TOKEN_8PVPLZ }}
      - uses: ariga/atlas-action/migrate/lint@v1
        with:
          dir: 'file://migrations'
          dir-name: 'admin'
          config: 'file://atlas.hcl'
          env: 'test'
      - uses: ariga/atlas-action/migrate/push@v1
        if: github.ref == 'refs/heads/main'
        with:
          dir: 'file://migrations'
          dir-name: 'admin'
          config: 'file://atlas.hcl'
          env: 'test'

Declarative
https://github.com/user-attachments/assets/5617fb35-07a7-4ea8-b4fd-47a9b16bbeba

Created yml file:
name: Atlas
on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]
  workflow_dispatch:
# Permissions to write comments on the pull request.
permissions:
  contents: read
  pull-requests: write
jobs:
  plan:
    if: ${{ github.event_name == 'pull_request' }}
    runs-on: ubuntu-latest
    env:
      GITHUB_TOKEN: ${{ github.token }}
    steps:
      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - uses: ariga/setup-atlas@v0
        with:
          cloud-token: ${{ secrets.ATLAS_CLOUD_TOKEN_EI1OPC }}
      - uses: ariga/atlas-action/schema/plan@master
        with:
          from: env://url
          schema-name: a8m-app
          config: 'file://atlas.hcl'
          env: 'test'
  apply:
    if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
    runs-on: ubuntu-latest
    env:
      GITHUB_TOKEN: ${{ github.token }}
    steps:
      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - uses: ariga/setup-atlas@v0
        with:
          cloud-token: ${{ secrets.ATLAS_CLOUD_TOKEN_EI1OPC }}
      - uses: ariga/atlas-action/schema/push@master
        with:
          schema-name: a8m-app
          config: 'file://atlas.hcl'
          env: 'test'
      - uses: ariga/atlas-action/schema/plan/approve@master
        id: plan-approve
        with:
          from: env://url
          to: ${{ steps.schema-push.outputs.url }}
          schema-name: a8m-app
          config: 'file://atlas.hcl'
          env: 'test'
      - uses: ariga/atlas-action/schema/apply@master
        if: ${{ steps.plan-approve.outputs.status == 'APPROVED' }}
        with:
          config: 'file://atlas.hcl'
          env: 'test'
          plan: ${{ steps.plan-approve.outputs.plan }}

waiting for nebula release

Videos added for better review

Thanks guys. 🚀🚀🚀🚀


Deploy role also deploys role members

I have a model created in Visual Studio with roles and RLS set up. Members are added to the roles. However, the new Power BI Premium XMLA endpoint doesn't support role members at the moment. When I try to deploy and check "Deploy Roles" but not "Deploy Role Members" Tabular Editor still tries to deploy the members resulting in an error. If I export a TMSL script I can see the role members. If I remove the members manually and run the script the deploy is working.

When you check "Deploy Roles" but uncheck "Deploy Role Members", Tabular Editor populates the TMSL script with the members already defined in the destination database, instead of those that may have been defined within Tabular Editor. If we send an empty array of role members for any given role in the TMSL, Analysis Services would remove any existing members from that role upon deployment.
Now, this functionality was created for Analysis Services where it works well, and we know that adding role members through XMLA is not yet supported on the Power BI XMLA endpoint. But I'm confused about the role members that showed up in your TMSL script? To my knowledge, if you've added members through the Power BI Service UI, these members would not show up in XMLA. Indeed - they don't show up in SSMS either.
So with "Deploy Role Members" unchecked, I don't understand why you're seeing role members in the TMSL script - these must have come from the Power BI service somehow.
Even if I change the behaviour of Tabular Editor, to not include existing role members from the destination dataset when deploying to Power BI XMLA, I would have to change it back at a later point in time, once the XMLA endpoint supports adding role members. So you can probably understand why I'm a little hesitant to change this.
Could a workaround in the mean time be, that you manually remove the role members within Tabular Editor before deploying?
To make this a little easier, here's a script you can use, which will clear all roles of their members in one go:
foreach(var role in Model.Roles)
    role.ClearMembers();

First of all - thank you Daniel for looking into the problem and for all your great work on Tabular Editor!
I agree to everything in your comment, and hopefully the XMLA endpoint will soon fully support roles and the problem goes away... But there is still one thing I find strange - I get members in the roles in the script even when deploying to an empty workspace with no model deployed before. Are the members from the bim file added if it's not possible to fetch them from the server? This is a part of the generated script:
        "roles": [           {             "name": "Chefer",             "description": "AAD.PowerBI.Chef - Dynamisk säkerhet baserad på chefsskap i MasterData",             "modelPermission": "read",             "members": [               {                 "memberName"<EMAIL_ADDRESS>                "memberId"<EMAIL_ADDRESS>                "identityProvider": "AzureAD"               }             ],             "tablePermissions": [               {                 "name": "Behörighet Organisation chef",                 "filterExpression": "'Behörighet Organisation chef'[Emailadress]=USERNAME()"               }             ]           }

Aha - that's a bug in the script generated when deploying a model as a new dataset (when writing my previous comment, I had only tested deployment with overwriting an existing dataset, which is a different code path). Thanks! I'll make sure this is fixed in next release.

Great! Thank's again!

Fixed in 2.12.0.

@otykier , Hey Daniel - any future plans to deploy the role members data as well from tabular editor with XMLA endpoint to Power BI dataset ?

@saurbshnde if your model metadata contains role members, they should already get deployed, when checking both "Deploy roles" and "Deploy role members".

@otykier Hey Daniel, thanks with some tweaks we were able to deploy role members data too. Thanks again for prompt response.

@otykier Hey Daniel, As we were able to succesfully convert a SSAS tabular cube to a Power BI dataset through XMLA endpoint on Tabular editor along with Role member data too.
I wanted to know does this mean that DAX logics we had written for RLS on the SSAS side will also get migrated to Power BI service and doesn't need any further tweaks ? Appreciate your support, thanks!

@saurbshnde if your deployment included the roles (you can verify this by opening the Power BI dataset in Tabular Editor through XMLA), then your RLS expressions should be intact. However, I still suggest you test that the security works as expected, by impersonating a user in the Power BI service.

@otykier Thanks Daniel, I will check this out! and keep you posted :)

@otykier Hey Daniel, I could see that the DAX rules got deployed onto the PowerBI dataset. However on the Power BI side, I cannot see the RLS getting applied. May be an issue or some configuration miss at the POwer BI side from us.


cleanHTML replaceOldTags doesn't seem to do anything

Jodit Version:  3.8.5
Browser:  FF
OS:  Windows
Is React App:  False
Code
var editor = new Jodit('#editor', {
    "cleanHTML": {
        "replaceOldTags": {
            'i':'em',
            'b':'strong',
            'h1':'p',
         },
     }
});

Expected behavior:
Any < i> tags will get converted to < em> tags, < b> to < strong> and < h1> to < p> when pasting in HTML
Actual behavior:
Nothing seems to happen to any of the existing tags. allowTags works fine for completely removing a tag.

ldlçskd
kdlsdksldks]lçsldl
kldskdlskd
kdlsdks


ARVR needs much tighter integration: bugs and performance woes with current setup!

The Problem:
When rendering an AR/VR frame in Godot, VisualServerViewport "draw_viewports" checks to see if the current viewport has "use_arvr" enabled. If it does then it calls "_draw_viewport" once for each eye. This causes the current viewport to then behave as two separate viewport/cameras pairs, one for each eye.
However, for each _draw_viewport call Godot performs a bit of setup before actually rendering the scene. This is a result of "render_camera" being called which performs scene culling, light visibility determination, reflection/GI probe updates, shadow updates, etc.. All of this work could (and should) be done once and used between both eye renders.
Not only is it slower to perform this pre-frame setup individually for each eye, but one problem that manifests as a result of the current implementation involves the way directional light PSSM shadows are generated per rendered viewport, producing a visible difference along the edges of shadows that shouldn't be there. Both eyes should invariably be seeing the same shadows cast across surfaces visible to both. This visible difference on shadows leads to a stereoscopic dissonance that is bothersome to look at and makes a scene look 'glitchy' in VR. If Godot were to use the same directional light shadowmaps for both eyes, by performing all pre-frame setup once and using the results across both eyes, then not only would this problem be solved but everything would run faster too.
VisualServerViewport treating each eye as an entirely separate viewport/camera also means iterating the scenetree twice per ARVR frame. When each mesh in the scene needs to be drawn it requires binding all the appropriate textures, shaders, vertex buffers, etc.. and then issues a draw call. With Godot's current ARVR implementation this means performing twice as much state change, and all of that state change adds up, eating away at performance. In an ideal ARVR implementation the GL state needed for each mesh in the scene is instantiated once and used to render it for all eyes, via multiple draw calls. In some instances even a single draw call can be used to render to multiple eyes (i.e. OVR_multiview extension in GLES3.2/GL4.6), but I don't suspect there's an equivalent across all ARVR capable platforms. Maybe with Vulkan running, perhaps.
The Solution:
Godot closely associates a viewport and camera in VisualServer, which at first-glance makes it appear a bit trickier to integrate proper ARVR rendering into, but I think that it can be done with minimal work.
The key is that all the setup (culling, shadows, reflection probes, etc) should occur once for a single ARVR enabled viewport and its associated ARVRCamera - regardless of the number of eyes it has. This means that the ARVR render case should be treated the same as the conventional case - with one viewport/FBO/camera, etc. The number of eyes of the current viewport/camera and corresponding view/projection transforms should be passed all the way down from VisualServerViewport::draw_viewports() to RasterizerScene::_render_list() so that when it instantiates the render state for each list item it can then make multiple geometry draw calls using each eye's view/projection transforms, rendering to each eye's corresponding glViewport subrect2d of the current viewport's FBO. Post processing and any other viewport-specific activities will also need to loop through the current viewport's eye's and glViewport between them across the FBO to perform whatever work entailed.
Here's a diagram to make better sense of the madness I describe:

Treating ARVR viewports as any other viewport will solve all of the inconsistency problems between eyes by naturally re-using generated culling/shadow data between them, as well as speed up rendering by reducing state change by nearly half, leaving Godot's ARVR rendering performance to conform more closely to the scene complexity and raw triangle/fragment processing capability of the underlying hardware itself, instead of the current approach of performing an entire two frames' worth of work for a single frame.
The resulting single texture containing both eyes' views can be blitted to the swapchain textures of the current ARVR interface. Whether or not this is performant on mobile is a different story, and perhaps the existing dual-camera render setup could be left as a fallback/option as mobile VR has significantly less memory bandwidth and is quite a bit more sensitive to moving around a lot of memory (such as when rendering to FBO and using the resulting texture to continue rendering the current frame), and may perform better if directly rendering to the swapchain textures provided by mobile VR API. Perhaps some kind of re-use flag can be set so that after rendering the first eye the second eye can re-use the culling/shadows of the first eye. Or, some means of decoupling the viewport/camera from eachother so that pre-frame setup can be performed for the ARVRCamera, and then two separate renders can be generated using the culling/shadows from that.
Different combinations of the above can be offered as multiple variants of which Godot users can select from as the means by which rendering for ARVR should be performed. Surely games with different levels of scene complexity on different devices will perform differently depending on the multi-view rendering strategy used. At the very least the situation with setting up twice to render from a single ARVRCamera, nearly the same vantage point, absolutely must be resolved, for all instances of ARVR rendering.
I'm sure VR is low on the priorities list, but it's not going anywhere, and we're long overdue for an alternative to the 'other' engines, especially one designed as cleanly and capably to its core as Godot. I could take a stab at setting up Godot to render ARVR optimally, and make a pull request, but I'm not sure how well that's going to work with all the existing work that's going on to integrate Vulkan in there, among other things. At some point someone's likely going to have to do some surgical merging one way or the other. I suppose at the very least I could fandangle a proof-of-concept with my own 'customized' Godot to use as a reference for you guys working more intimately with the guts. Or this could wait until whatever changes to Godot have been made on the rendering side.

You can join forces with @BastiaanOlij (main ar/vr dev) at IRC, godotengine-vr to coordinate the work and fixes.

@DEF7 indeed, this is something we've discussed in length in the past. The current solution was the one that was fastest to get up and running after which we could start looking at improvements. The focus was on getting 3.0 released with the new renderer working for everyone, not adding a few months of redesign just to make the handful of people wanting to use Godot for VR happy (sad for me but true 😃 ).
I've done a few experiments with doubling the viewport size and treating each half for each eye but there are a lot of technical hoops to jump through. Keep in mind that you can't simply double your draw calls, continuously switching between rendering left and right eye has overheads in itself that will mitigate any improvements. When looking for instance at Nvidia's 3dvision drivers that do this behind the scenes to turn a non-stereoscopic game into a stereoscopic game they will batch draw calls to minimize switching between left and right rendering. It requires enhancements in both the API and the hardware to make this a win-win situation.
In that respect i'm putting my money in waiting for this enhancement to become mainstream:
https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview.txt
That would basically allow us to do stereoscopic rendering with very few changes in the current rendering pipeline and indeed, we could still fall back on the left eye/right eye slower approach on older hardware that doesn't support it or that has memory constraints making it illogical to double the sizes of all render buffers especially as they are already at 4x the resolution to accommodate the lens distortion (VR is incredibly wasteful at this point in time).
As far as left eye/right eye separate rendering is concerned.
The pipeline if multiview is not available should really become:

figure out a combined view frustum for left and right eye combined
doing your lighting and shadow calculation and shadow buffer updates based on that frustum so they can be used for both eyes
do your culling based on that frustum to create your render list
render left eye
render right eye

While there will be some overhead in processing the objects to be rendered twice, all the stuff that really is doubled up will now only be done once.
And this is an approach that really only suits the current generation of headsets where you have two forward looking "cameras" with view frustums that overlap for 90%, you look at something like StarVR and that goes out the door as an optimization.
Another thing in this that we need to further investigate is whether we can at the very least keep the left eye and right eye color buffer separated even if we reuse all of the effect buffers, this will still prevent the memory usage from blowing up but it will allow us to create stereo buffers that we can then use during rendering.
@reduz at this point in time knows the render pipeline better then I do, I've been meaning to find time to dive into it more and possibly break up the render scene function into individual parts so we can change the render loop as sketched above.
Btw, I'm in Sydney Australia so timezones (hence not being on #godotengine-vr when you said hi, check out riot.im so you can stay on persistently and I can leave reactions :)

How does the upcoming switch to Vulkan affect this proposal? Are there APIs or new techniques available in Vulkan that can improve VR support?

It supports multiview rendering. Just like what bastiaan described above. With multiview rendering you can render to both eyes simultaneously.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


Bug/exchange rates

Fix exchange rates on swap for synths that have futures markets (sEUR)
Description

change the rates object in state to include synth and asset names (sEUR and EUR)
Update the ETH address for swap pricing to the WETH contract on Optimism

Trying ETH -> sUSD swap clicking "Max" on ETH results in 0 instead of expected max ETH balance of connected wallet

@platschi the issue is because we "buffer" ETH swaps by 0.1 ETH which seems really extreme. Since the balance is 0.017 it will default to 0, but if you had .2 ETH it would display .1 ETH

https://github.com/Kwenta/kwenta/blob/150de1163e8e97ae7597400f95a75094d6937638/hooks/useExchange.ts#L1117


Bugfix for negative spaces in space(field::Symbol)

Love Bibliography.jl, thanks for these packages!
I have bibtex files with some extra-long fields, for example
    @inproceedings{farassat_theoretical_analysis_linearized_acoustics_supersonic_propellers_1985,
     organization  = {NASA Langley Research Center},
     pages         = {15 p},
     distributionlimits = {Unclassified; Publicly available; Unlimited},
     booktitle     = {AGARD Aerodyn. and Acoustics of Propellers},
     author        = {Farassat, F.},
     month         = {02},
     source        = {NASA STI Program - NTRS},
     title         = {Theoretical analysis of linearized acoustics and aerodynamics of advanced supersonic propellers},
     doctype       = {Conference Paper},
     link          = {https://ntrs.nasa.gov/search.jsp?R=19860001689},
     ntrsdocid     = {19860001689},
     year          = {1985},
     rights        = {Copyright; Distribution within the U.S. granted by agreement},
     file          = {AGARDCP366:fulltext/farassat_theoretical_analysis_linearized_acoustics_supersonic_propellers_1985-AGARDCP366.pdf:application/pdf}
    }

When I try to parse that, I get an error:
ERROR: ArgumentError: can't repeat a string -5 times
Stacktrace:
 [1] repeat(s::String, r::Int64)
   @ Base ./strings/substring.jl:226
 [2] int_to_spaces
   @ ~/projects/LitMan.jl-dev/spaces_bug/dev/Bibliography/src/bibtex.jl:15 [inlined]
 [3] field_to_bibtex(key::String, value::String)
   @ Bibliography ~/projects/LitMan.jl-dev/spaces_bug/dev/Bibliography/src/bibtex.jl:27
 [4] export_bibtex(e::BibInternal.Entry)
   @ Bibliography ~/projects/LitMan.jl-dev/spaces_bug/dev/Bibliography/src/bibtex.jl:135
 [5] export_bibtex(bibliography::OrderedCollections.OrderedDict{String, BibInternal.Entry})
   @ Bibliography ~/projects/LitMan.jl-dev/spaces_bug/dev/Bibliography/src/bibtex.jl:149
 [6] doit()
   @ Main.Test1 ~/projects/LitMan.jl-dev/spaces_bug/test1.jl:29
 [7] top-level scope
   @ REPL[7]:1

The problem is that the distributionlimits field is longer than any of the standard fields in the BibTeX file format. This messes up the space offset calculation when writing out the file.
Here's the script I used to test this:
module Test1

using Bibliography
using BibParser

function doit()

    bibtex_str = """
    @inproceedings{farassat_theoretical_analysis_linearized_acoustics_supersonic_propellers_1985,
     organization  = {NASA Langley Research Center},
     pages         = {15 p},
     distributionlimits = {Unclassified; Publicly available; Unlimited},
     booktitle     = {AGARD Aerodyn. and Acoustics of Propellers},
     author        = {Farassat, F.},
     month         = {02},
     source        = {NASA STI Program - NTRS},
     title         = {Theoretical analysis of linearized acoustics and aerodynamics of advanced supersonic propellers},
     doctype       = {Conference Paper},
     link          = {https://ntrs.nasa.gov/search.jsp?R=19860001689},
     ntrsdocid     = {19860001689},
     year          = {1985},
     rights        = {Copyright; Distribution within the U.S. granted by agreement},
     file          = {AGARDCP366:fulltext/farassat_theoretical_analysis_linearized_acoustics_supersonic_propellers_1985-AGARDCP366.pdf:application/pdf},
     abstract      = {The derivation of a formula for prediction of the noise of supersonic propellers using time domain analysis is presented. This formula is a solution of the Ffowcs Williams-Hawkings equation and does not have the Doppler singularity of some other formulations. The result presented involves some surface integrals over the blade and line integrals over the leading and trailing edges. The blade geometry, motion and surface pressure are needed for noise calculation. To obtain the blade surface pressure, the observer is moved onto the blade surface and a linear singular integral equation is derived which can be solved numerically. Two examples of acoustic calculations using a computer program are currently under development.}
    }
    """

    db = BibParser.parse_entry(bibtex_str)
    export_bibtex(db)
end

end # module

Nice catch, thanks! I will merge it and tag a new version.
Is that okay if I also add your example in the test of Bibliography.jl? (I can make another dummy test, but it is nice to have real example)
I will also open an issue in Bibliography.jl to make the spaces relative to the fields in an entry. Eventually ...

Is that okay if I also add your example in the test of Bibliography.jl? (I can make another dummy test, but it is nice to have real example)

Go for it! Thanks again!


In Node 10.x + Typescript using ts-node fuzzy-search fails when new'd

The output from ts-node REPL after importing the Parser and calling the search routine.
 var searcher = new fuzzy_search_1.default(this.registrations, ['name', 'realName', 'email', 'previousEmails', 'regCode'], {
                       ^

TypeError: fuzzy_search_1.default is not a constructor

The actual code is:
    searchRegistrations(needle: string) {
        const searcher = new FuzzySearch(this.registrations, ['name', 'realName', 'email', 'previousEmails', 'regCode'], {
            caseSensitive: false,
          });

          return searcher.search(needle)
    }

I dug around a bit and I can't find anything that I missed... this project looks amazing and was excited to find it. Hope its something simple we missed.
Thanks for the awesome project and the help!

Turns out switching from:
import FuzzySearch from 'fuzzy-search'
to
const FuzzySearch = require('fuzzy-search');

worked.
I will leave this open just in case there is something meaningful to this failure.
Thanks again!

Apparently https://github.com/wouter2203/fuzzy-search/pull/52 also fixes this issue. It's working for me, so I'm closing it.
Feel free to reopen it if the problem persist for you!


a little confuse about chapter5/blackjack.py

hi,As the following algorithm,I didn't see the corresponding sentence in the code "Unless the pair S t , A t appears in S 0 , A 0 , S 1 , A 1 . . . , S t 1 , A t 1 :"
Initialize:
pi(s)  belongs to   A(s) (arbitrarily), for all s  belongs to  S
Q(s, a)  belongs to  R (arbitrarily), for all s  belongs to S, a belongs to A(s)
Returns(s, a)<-empty list, for all s belongs to S, a belongs to A(s)
Loop forever (for each episode):
Choose S 0 2 S, A 0 2 A(S 0 ) randomly such that all pairs have probability > 0
Generate an episode from S 0 , A 0 , following pi: S 0 , A 0 , R 1 , . . . , S T 1 , A T 1 , R T
G<-0
Loop for each step of episode, t = T 1, T 2, . . . , 0:
G=lambda*G + R t+1
Unless the pair S t , A t appears in S 0 , A 0 , S 1 , A 1 . . . , S t 1 , A t 1 :
Append G to Returns(S t , A t )
Q(S t , A t ) = average(Returns(S t , A t ))
pi(S t )=argmax a Q(S t , a)

Thanks for pointing this out.  It looks an issue with every visit MC and first visit MC.
By ignoring that sentence, every visit MC is implemented instead of first visit MC.
Maybe fix it in the future.

Fixed, thanks!


Update cluster template definition

probably not, where do you see this sorry?

Hmm, seems only to be present on alt-1.


Add a -t option for specifying custom number of threads per process

Is your feature request related to a problem? Please describe.
Adding a cli -t option will user to customize and scale the download speed as per their needs
Describe the solution you'd like
We can add a cli option -t that on invokation will look like m3u8-dl <url-of-playlist> -t 8 this would mean starting the download processes with 8 threads per process, so if there are 4 download processes there will be a total of 32 threads.

I'm gonna take a look at this.


[Sage Discussion]: Mixture Data Selection

Mixture Data Selection: We currently have ThermoML as our source of mixture data. What mixtures should be emphasized in the training data? What solvents other than water that we should be focusing on?

Parsley Benchmark Set: https://github.com/openforcefield/release-1-benchmarking/blob/master/physical_properties/release_1_benchmark_set.pdf


Make unicodeAccents.js ES6 module

Use babel-register in unicodeMake.js to require ES6 module.

This reduces bundling overhead since non-ES6 module didn't support module concatenation and tree shaking.

Another option is passing the --harmony flag to node, but I don't know which versions support ES6 modules with that flag.

@kevinbarabash Node 8.5+ supports ES modules with experimental-modules flag, but the file extension needs to be .mjs.


Cannot replicate

I trained the model as specified in the readme but cannot replicate the results. The following is what I get.

Input: you must have girlfriend
Output: than than than than than than than than than than

Is this because of the training/dataset?

hi @braindead  i have problem in training
it show error
batched_corrective_tokens = tf.pack(
AttributeError: 'module' object has no attribute 'pack'

in file

text_corrector_models.py   line 91

tensorflow V 1.0.0

@braindead I also get this kind of results. Have you solved it?
@essamgoda You should use stack instead of pack.

another error show
@xushenkun
ValueError: Shape must be rank 2 but is rank 1 for 'model_with_buckets/sequence_loss/sequence_loss_by_example/sampled_softmax_loss/LogUniformCandidateSampler' (op: 'LogUniformCandidateSampler') with input shapes: [?]

@essamgoda Maybe change labels and inputs, as in in API https://www.tensorflow.org/versions/r1.1/api_docs/python/tf/nn/sampled_softmax_loss
            def sampled_loss(labels, inputs):                 labels = tf.reshape(labels, [-1, 1])                 return tf.nn.sampled_softmax_loss(w_t, b, labels, inputs,                                                   num_samples,                                                   self.target_vocab_size)
another error "Ran out of memory"
File "correct_text.py", line 434, in main
   train(data_reader, FLAGS.train_path, FLAGS.val_path, FLAGS.model_path)
 File "correct_text.py", line 181, in train
   target_weights, bucket_id, False)
 File "text_corrector_models.py", line 297, in step
   outputs = session.run(output_feed, input_feed)

Command used:
python correct_text.py --train_path "./data/movie_dialog_train.txt" --val_path "./data/movie_dialog_val.txt" --config DefaultMovieDialogConfig --data_reader_type MovieDialogReader --model_path "./movie_dialog_model"
Used data and source code:
https://www.dropbox.com/s/oo7e9vg5hcrnjke/deep-text-corrector-master.rar?dl=0

@derofim thanks alot it's worked
your code worked too (take a long time)
try to reduce number of layer and size if your resource is limited i use gpu ( Nvidia 940 mx 4 gb)

@braindead @xushenkun the same error did you solve it ?

@essamgoda hi, how much steps have you trained? when I run 20000 times in half an hour, it showed....
 Did you eventually solve it? Or is it unsolvable?

Problem fixed. Please see my fork.

how to get expected results, and which parameters should change?
output:  what what what what what what what what what

Problem fixed. Please see my fork.

Hi, which problem did you fix? problem 'cannot replicate the results'? I tried your fork with my pertained model but still get the same kind of results.


Add checkbox to hide/show offline instances for a particular user

Currently user might have multiple instances and we can only distinguish them by description which is often not set up. Also it's kinda useless to show offline instances, we only need it when we want to modify consent. So maybe it would be better if we had a checkbox "show offline instances" or something like that which would be off by default.

Closing as this is not a priority right now


Error while reading library

Hi, app crashed with this message :
 Reading library...Error: The "path" argument must be of type string. Received undefined
Running on MacOS v10.15.7, nodejs  v18.2.0, quiver v3.2.7
Thx.

@cocoaway Sorry for replying late. Can you tell me which command parameters you input?


[Storage] Deprecate BlobProperties as blob or name parameter input

As title states 😄

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-blob


[BUILD] fvdb not installable

Environment
Windows 11, python 3.11.9, miniconda3 (conda 24.7.1)
Describe the problem
In openvdb/fvdb/README.md there is an incomplete instruction:

fVDB is provided as an installable python package from [todo: insert package distributor].

In addition, the conda install command given in the README does not appear to be working.
To Reproduce
Steps to reproduce the behavior:

As per the README, run conda install -c jswartz fvdb
See the PackagesNotFoundError for fvdb

Additional context
I am really looking forward to using fVDB!

I corresponded with James offline and advised that building for Windows is currently not supported.  I've also unfortunately left instructions for a test build of fVDB up on the docs which I'll remove.

Hi, I tried the same command conda install -c jswartz fvdb on Linux and got the same issue PackagesNotFoundError: The following packages are not available from current channels:- fvdb

Hi @OasisYang, at the moment we don't have packaged builds distributed for fvdb.  The build instructions should still be relevant and work but the conda command in the README is an instruction from an old test package.  This conda command information will be removed shortly, sorry for the confusion.


New slim-skeleton not working on nginx getting 403 message

Hi I just created a new project with composer   composer create-project slim/slim-skeleton
and in my nginx.conf I have this settings.
location ~ ^/slim-skeleton{
try_files $uri $uri/ /slim-skeleton/public/index.php$is_args$args;
}
but my output I get as this

403 Forbidden

403 Forbidden

nginx

This seems like a configuration issue with Nginx. Please show logs and configuration file.

I'm closing this as resolved, feel free to re-open with more insights.

Hi,
Which logs will you prefer then I post it here?

Any logs. From either Nginx or PHP

@learnme2019 Are you sure that you install project into the root folder /slim-skeleton/public/index.php?

I'm closing this as no further user feedback has been provided


Fix multiple run models exception for API

The exception should not be raised, as we are getting project event from the project objects such as PR/branch push/release/issues and for these, there can be multiple project events (e.g. PR with multiple pushes). Fixes #2153
TODO:

[ ] Write new tests or update the old ones to cover new functionality.

RELEASE NOTES BEGIN
TODO
RELEASE NOTES END

recheck

recheck

recheck


master => live - 2020-04-27

new tagline for advocates
adding advocates to the listing
updating toc/map/index

Docs Build status updates of commit 0a70253:
:clock10: Pending: waiting for processors (11 builds ahead of you)
:warning: Docs Build is busy, currently there are 11 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 0a70253:
:warning: Validation status: warnings

File
Status
Preview URL
Details

advocates/index.html.yml
:warning:Warning
View
Details

advocates/april-speight.yml
:white_check_mark:Succeeded
View

advocates/aysegul-yonet.yml
:white_check_mark:Succeeded
View

advocates/em-lazerwalker.yml
:white_check_mark:Succeeded
View

advocates/madoka-chiyoda.yml
:white_check_mark:Succeeded
View

advocates/map.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/aysegul-yonet.jpg
:white_check_mark:Succeeded
View

advocates/media/profiles/thomas-lewis.png
:white_check_mark:Succeeded
View

advocates/thomas-lewis.yml
:white_check_mark:Succeeded
View

advocates/toc.yml
:white_check_mark:Succeeded
View

advocates/index.html.yml

Line 0: [Warning] Invalid file link:(~/tweets).
Line 0: [Warning] Invalid file link:(~/map).

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


The information of 'min threads' and 'max threads' do not shown in the Job stats panel.

Hello Snakemake Team,
I've encountered an issue with job stats in versions of Snakemake later than 7.30.1 and would like to report it for your review.
Snakemake version: Any version latter than 7.30.1
Python version: 3.11.6
Describe the bug:
In Snakemake version 7.30.1 and earlier, executing a workflow with the -n (dry run) option provided detailed job stats, including:

job
count
min threads
max threads

However, starting from versions later than 7.30.1, the 'min threads' and 'max threads' information is no longer displayed in the job stats. The output now only includes the job name and count. For example:
$ snakemake  -c8   -p  -n
Building DAG of jobs...
Job stats:
job             count
------------  -------
all                 1
run_workflow        2
total               3

Execute 2 jobs...

[Wed Jan 31 17:33:22 2024]
localrule run_workflow:
    output: 1.done
    jobid: 1
    reason: Missing output files: 1.done
    wildcards: i=1
    threads: 3
    resources: tmpdir=<TBD>

touch 1.done

[Wed Jan 31 17:33:22 2024]
localrule run_workflow:
    output: 2.done
    jobid: 2
    reason: Missing output files: 2.done
    wildcards: i=2
    threads: 3
    resources: tmpdir=<TBD>

touch 2.done
Execute 1 jobs...

[Wed Jan 31 17:33:22 2024]
localrule all:
    input: 1.done, 2.done
    jobid: 0
    reason: Input files updated by another job: 2.done, 1.done
    threads: 2
    resources: tmpdir=<TBD>

Job stats:
job             count
------------  -------
all                 1
run_workflow        2
total               3

Reasons:
    (check individual jobs above for details)
    input files updated by another job:
        all
    missing output files:
        run_workflow

This was a dry-run (flag -n). The order of jobs does not reflect the order of execution.

The result is produced with Snakemake version 8.4.2
This change in behaviour results in less detailed information about thread usage in the workflow summary, which is crucial for understanding and optimizing resource allocation.
Minimal example:
samples = [1,2]
rule all:
    input:
        expand("{i}.done", i=samples)
    threads: 2

rule run_workflow:
    output:
        "{i}.done"
    threads: 3
    shell: "touch {output}"

Command Used:
snakemake  -c8   -p  -n
Additional context:
The job stats should include 'min threads' and 'max threads' for each rule, as was the case in version 7.30.1 and earlier.
Best,
Jie

It is mentioned in the here 'https://github.com/snakemake/snakemake/commit/4c591b72b31d6c6c36b43f1d7773d8317352fbc9'


Vickel: Watch ghonay.com

Vickel requests the watch of the watch_keyword ghonay\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

ghonay\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jesse in Charcoal HQ


Added webhook event listener.

To donavanbecker,
If this PR doesn't agree to the strategy/policy of plug-in and/or target user, reject it immediately. I guess there are any reasons for the absence of this function.
To developers,
This PR implements webhook event listener to deliver them to the handler of each device, as a basis of future development.
Config keyword 'webhookURL' in 'options' is added to specify webhook URL which needs to be public server address where the plug-in is running.
{
  "name": "SwitchBot",
  "credentials": {...},
  "options": {
    "webhookURL": "http://${FQDN}:${PORT}/${PATH}",
  }
  ...
}

To implement the webhook event handler, look constructor() in meter.ts as an example. The template code structure is as follows.
if (this.device.webhook) {
  this.infoLog(`${this.device.deviceType}: ${this.accessory.displayName} is listening webhook.`);
  this.platform.webhookEventHandler[this.device.deviceId] = async (context) => {
    try {
      this.debugLog(`${this.device.deviceType}: ${this.accessory.displayName} received Webhook: ${JSON.stringify(context)}`);
      //
      // event processing in here.
      //
    } catch (e: any) {
      this.errorLog(`${this.device.deviceType}: ${this.accessory.displayName} failed to handle webhook. Received: ${JSON.stringify(context)} Error: ${e}`);
    }
  }
}

and the device handler is enabled by config kwyword 'webhook' of device in 'devices' section.
"devices":[
  {
    "deviceId": "...",
    "webhook": true,
    ...
  },
  ...
]

I will add development tips, if approved.

Thank you so much for this PR!!!
I am going to merge this, but if we are going to release this in a new version, a lot of documentation would need to be created so that it is easy for users to setup.

@banboobee, by chance can you add documentation?

I added all I did and found I originally planed.

Do you have this working?

Yes, working every days.

Okay what are you using for the webhook capturing, what is an example of a webhook url you are using, etc?

My understanding of webhooks is that there is a server that gets the webhooks from SwitchBot and then would have to push it to the plugin, for the plugin to recognize. Or am I wrong?

There is no 'server that gets the webhooks from SwitchBot', so this PR creates the server inside of plugin. Thus the url is an IP address of the server itself. Since this is a super personal information rather than credentials, I can't disclose it to you.

@banboobee Are you on the Homebridge Discord server?


WIP shortcuts

Not for merging, yet.

I'm :-1: on the Escape-based shortcuts.

As much as I like emacs (and I really do love it), I'm with Chris on this one: -1 on escape-based shortcuts.

This thing seem to need rebase.

Please reopen this against https://github.com/jupyter/jupyterlab if it is still applicable.


⚠ SceneTime has degraded performance

In 0f30471, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3065 ms

Resolved: SceneTime performance has improved in 5175702 after 8 minutes.


Add notice about fixed firmware v3, TRA01E18 (#28)

Do you agree to be mentioned here? @rmettes

Sure, no problem


Reset account settings during setup progression

Fixes #5088 (Port isn't changed when switching account types)
As per my comment on that issue I've made it so that all settings are reset when you navigate to the incoming/outgoing screen.
Doesn't change what the default settings are when first navigating to those screens just resets back to those same defaults each time you go to the incoming/outgoing screens.

I squashed the commits, rebased the branch, and fixed a couple of minor issues.

I squashed the commits, rebased the branch, and fixed a couple of minor issues.

Thanks :+1:

Thanks :+1:

I squashed the commits, rebased the branch, and fixed a couple of minor issues.
Legend thanks for doing that cketti

I squashed the commits, rebased the branch, and fixed a couple of minor issues.
Legend thanks for doing that cketti


Run compile check on vanilla as well

Btw @GeckoEidechse assuming this doesn't explode everything you might want to merge this pretty quick, I may have accidentally made the new parameter required and not bumped the version number at the same time :)

Cannot check rn but I'll just you with it ^^"


RegexCorsConfiguration - always calls the super class method

I'm trying to use your RegexCorsConfiguration I have kind of the same implementation as you except I expose CorsFilter using a FilterRegistrationBean and via @Bean annotation.
        @Bean
        FilterRegistrationBean corsFilter() {
          UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
          CorsConfiguration config = new RegexCorsConfiguration();
          config.setAllowCredentials(true);

          this.corsSettings.getAllowedHeaders().forEach(config::addAllowedHeader);
          this.corsSettings.getAllowedMethods().forEach(config::addAllowedMethod);
          this.corsSettings.getAllowedOrigins().forEach(config::addAllowedOrigin);

          source.registerCorsConfiguration("/**", config);
          FilterRegistrationBean bean = new FilterRegistrationBean<>(new CorsFilter(source));
          bean.setOrder(Ordered.HIGHEST_PRECEDENCE);
          return bean;
        }

But for some reason, it always calls the superclass implementation of the checkOrigin method. Do you have any idea about this? Appreciate your feedback

Hi @RockyRx ,
RegexCorsConfiguration redefines checkOrigin like this:
https://github.com/looorent/spring-security-jwt/blob/bf0dac14736db062fd43862c58eebf0d4aadd0b2/src/main/java/be/looorent/security/jwt/RegexCorsConfiguration.java#L48-L52
This means before checking the origin based on a regular expression, it initially checks whether the origin already meets some basic CORS checks (for instance, if you allow "*" in your CORS configuration, your regex won't be used).
If you actually want to avoid this basic CORS check, you could extend RegexCorsConfiguration.checkOrigin to not call super.checkOrigin in checkOrigin.

@looorent
Thanks for the quick response.
I tried commenting off the super.checkOrigin in checkOrigin, but still, it calls the superclass method. I think I have done something fundamentally wrong here but still could not figure it out.
  @Nullable
  public String checkOrigin(String requestOrigin) {
//    String result = super.checkOrigin(requestOrigin);
    return checkOriginWithRegularExpression(requestOrigin);
  }

Would you have a repository with a working example? So I could debug it by myself and identifies why there is a unexpected check.


refactor: switch Logo.vue to use UIcon, however there is no nuxters icon on ico…

…nify
@Atinux #39

We can use the UIcon component from https://ui.nuxt.com actually to improve this

I switched Logo.vue to show how it could work, but theres no nuxters icon on iconify, is this something that can be changed?

I don't think it's possible then

I don't think it's possible then
Should I close the PR then?


Fix issue #452

If main run-lisav2 script will call these scripts, it will conflict in using the $LogFileName variable.
This is to fix that behavior if the scripts are ran independently of lisav2
Test Results :
Azure :
ARM Image Under Test  : Canonical : UbuntuServer : 18.04-DAILY-LTS : latest
Total Test Cases      : 2 (2 Pass, 0 Fail, 0 Abort)
Total Time (dd:hh:mm) : 0:0:9
ID TestCaseName                                                 TestResult TestDuration(in minutes)
1 CAPTURE-VHD-BEFORE-TEST                                            PASS                 4.78
2 VERIFY-DEPLOYMENT-PROVISION                                        PASS                 4.61
FirstBoot : PASS
FirstBoot : Call Trace Verification : PASS
Reboot : PASS
Reboot : Call Trace Verification : PASS
Logfiles :

Hyper-V:
VHD Under Test        : ubuntu_18.04.1.vhdx
Total Test Cases      : 1 (1 Pass, 0 Fail, 0 Abort)
Total Time (dd:hh:mm) : 0:0:4
ID TestCaseName                                                 TestResult TestDuration(in minutes)
1 VERIFY-DEPLOYMENT-PROVISION                                        PASS                 4.26
FirstBoot : PASS
FirstBoot : Call Trace Verification : PASS
Reboot : PASS
Reboot : Call Trace Verification : PASS
Logfiles:

@chvalean @asofron Please provide test results for future PR, make sure not break case against HyperV and Azure.

@LiliDeng  Update with relevant tests


fix exp overflow when updating lse

Fix the exp overflow when updating LSE
#new_lse = lse + torch.log(1 + torch.exp(block_lse - lse))
new_lse = lse - _logSigmoid(lse - block_lse)

This is great! Could you use the
import torch.nn.functional as F

F.logsigmoid(...)

so that we don't need to have a global var? Thank you!

This is great! Could you use the
import torch.nn.functional as F

F.logsigmoid(...)

so that we don't need to have a global var? Thank you!

yeah, done


[Completion] Add a test case for CaseIterable enum in other file

Make sure 'allCases' is suggested even if the enum decl is in a different file.
rdar://problem/57489427

@swift-ci Please smoke test


[Monitor] Support GA MetricAlerts API

Fold new functionality into existing monitor alert commands.

PR merged.


Tab navigation improvements

"I strongly feel that the multiple jobs feature can be done away with in first version. If not, the tab navigation needs to be improved. A “run all job” button is also essential as the user will not find it convenient to go to each tab to start the process. Can Ctrl + Tab be assigned for tab navigation?  "
cc @prashantverma2014

A “run all job” button is also essential as the user will not find it convenient to go to each tab to start the process.

I'm not sure I understand why such a button is essential. In a normal workflow, the user will fill out a job form and then submit it. The most common use case will then be that the user waits for the job to finish. The other use case is that the user will go on submitting more jobs forms while other jobs are still running, so it is indeed important that he can navigate between jobs. But I don't see such a benefit in being able to submit several jobs at once.

I strongly feel that the multiple jobs feature can be done away with in first version.

Personally I also think it might have been better to have no tab interface initially, but provide a way to have multiple windows (one for each job). This way navigation between jobs would have been a OS native thing.
I'm all for the tab interface if it works well though.
Ideal would be a combination of tabs and multiple windows, I think, like in browsers. That would give the user the flexibility to arrange and navigate jobs the way he prefers.

I was told that users may like to leave the system running as they go out of office with jobs that take time i.e. those using TTS.
IN such a case, they can add several jobs and then start them all together.
Starting such jobs and also creating new jobs in parallel may make the system slow, or users may have that apprehension.
The other Pipeline   has run all jobs option.
From: Bert Frees @.>
Sent: Monday, December 12, 2022 4:03 PM
To: daisy/pipeline-ui @.>
Cc: Prashant Ranjan Verma @.>; Mention @.>
Subject: Re: [daisy/pipeline-ui] Tab navigation improvements (Issue #21)
A “run all job” button is also essential as the user will not find it convenient to go to each tab to start the process.
I'm not sure I understand why such a button is essential. In a normal workflow, the user will fill out a job form and then submit it. The most common use case will then be that the user waits for the job to finish. The other use case is that the user will go on submitting more jobs forms while other jobs are still running, so it is indeed important that he can navigate between jobs. But I don't see such a benefit in being able to submit several jobs at once.
I strongly feel that the multiple jobs feature can be done away with in first version.
Personally I also think it might have been better to have no tab interface initially, but provide a way to have multiple windows (one for each job). This way navigation between jobs would have been a OS native thing.
I'm all for the tab interface if it works well though.
Ideal would be a combination of tabs and multiple windows, I think, like in browsers. That would give the user the flexibility to arrange and navigate jobs the way he prefers.
—
Reply to this email directly, view it on GitHub https://github.com/daisy/pipeline-ui/issues/21#issuecomment-1346455604 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYXNO3JXAIKPYADDC5GO7TWM4PATANCNFSM6AAAAAASXG4FSE .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/ABYXNO3WK567LNLPPMTB5ADWM4PATA5CNFSM6AAAAAASXG4FSGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSQIFEDI.gif Message ID: @.*** @.***> >

This issue has been split into 3 issues so I am closing it here but please continue the discussions.


Blog App: validations and model specs

In this pull request the following tasks were implemented:

Add the following validations:

For the User model:

Name must not be blank.
PostsCounter must be an integer greater than or equal to zero.

For the Post model:

Title must not be blank.
Title must not exceed 250 characters.
CommentsCounter must be an integer greater than or equal to zero.
LikesCounter must be an integer greater than or equal to zero.

Add unit specs for all of your models' methods and validations.

Hi @Danieldotcomcoder,
I wanted to express my gratitude for your review of my project.


How to switch front-back camera in CameraCaptureActivity ?

I want to switch the front or back camera in CameraCaptureActivity(src/com/android/grafika/CameraCaptureActivity.java), as the following:
public boolean switchCamera() {
        releaseCamera();
        mGLView.onPause();
        if (mReqCameraId == Camera.CameraInfo.CAMERA_FACING_BACK) {
            mReqCameraId = Camera.CameraInfo.CAMERA_FACING_FRONT;
        } else {
            mReqCameraId = Camera.CameraInfo.CAMERA_FACING_BACK;
        }
        openCamera(mReqCameraId);

        mGLView.onResume();
        mGLView.queueEvent(new Runnable() {
            @Override
            public void run() {
                mRenderer.setCameraPreviewSize(mCameraPreviewWidth, mCameraPreviewHeight);
            }
        });
        return true;
    }

It works, but the FOV has been changed when I back to the camera which first time launched. It seems the frame has been clipped.
So where did i miss when switch the front-back camera?
Thanks.

Someone recently discovered that calling setRecordingHint() would alter the FOV. Read about it here:
http://stackoverflow.com/questions/31114191/field-of-camera-preview-is-smaller-if-i-use-the-way-of-preview-in-grifikas-cont
If that doesn't lead you to the solution, you should post a question on http://stackoverflow.com/, using the [android-camera] tag.

OK. Thanks.


"Use of uninitialized value" error when starting daemon

Hi, I just freshly installed convos, and I get the following error when I try to start the daemon using the magic incantation offered in the manual:
$ ./vendor/bin/carton exec script/convos daemon --listen http://*:8080
Use of uninitialized value in -f at /home/harry/convos/local/lib/perl5/Daemon/Control.pm line 313.
Use of uninitialized value in open at /home/harry/convos/local/lib/perl5/Daemon/Control.pm line 299.
Use of uninitialized value in concatenation (.) or string at /home/harry/convos/local/lib/perl5/Daemon/Control.pm line 299.
Failed to write : No such file or directory at /home/harry/convos/local/lib/perl5/Daemon/Control.pm line 299.

Running this on a pretty bare-bones Ubuntu 14.04 VM btw.
Any ideas what could have gone wrong here? Cheers!
-harry

This should be fixed by d4292fff9ea2394c091106add5066e73b4448df2.
Please re-open if I am wrong.


Fix addEventCallback input parameter type

Fixes input parameter type for addEventCallback which broke when moving from v2 to v3
Addresses #6309

Can we add tests to match the type?

Generally speaking testing types is done by the TypeScript compiler, you can't really write unit tests against non-primitive types because types are stripped at runtime. Functionally nothing changes here, this is purely a TypeScript change.
We do have tests for the addEventCallback API, however, they continued to pass because PCA was expecting a less specific type. Now that we've restored the expectation for a more specific type attempts to pass in a less specific type would fail at the TypeScript level.