Use permutation matrices where relevant

We should replace the existing permutation matrix hacks throughout the library with the new PermutationMatrix types. Relevant locations:

[x] LUP decomposition
[x] Parity function in matrix/mod.rs

Just a heads-up in case anyone would want to work on this: please let me know, and we can work together! I'm hoping to be able to come up with a second draft of #94 soon. It will be completely rewritten and rely on the new PermutationMatrix struct.

I think this has been completed now, @Andlon ?

I would agree :)


use external DoH client

Codecov Report

Merging #28 (a7d0a77) into master (7d7ff11) will decrease coverage by 0.73%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
- Coverage   42.67%   41.94%   -0.74%
==========================================
  Files           7        6       -1
  Lines         553      515      -38
==========================================
- Hits          236      216      -20
+ Misses        289      277      -12
+ Partials       28       22       -6

Impacted Files
Coverage Δ

cmd/dnstrace/benchmark.go
68.15% <ø> (ø)

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 7d7ff11...a7d0a77. Read the comment docs.


Does not support array

Tried to generate code but plugin stopped on array.

Array/List supported now in v1.2


Let feature + metadata textures make copies

This change looks a lot more intense than I intended to be, but here's a summary:

Created TextureView base class that FeatureIdTextureView and PropertyTexturePropertyView now inherit from. This is copy pasting the common code from both implementations.
Added TextureViewOptions, which includes the applyKhrTextureTransform flag from a previous PR. But now it includes makeImageCopy, which makes a CPU copy of the input image if true.
Added options parameter to various PropertyTextureView functions so that property views could be constructed with the desired options.
Added unit tests for the new options.

Thanks @kring ! Merging with your approval.


interaction response for synchronous payment methods

Synchronous payment methods can return an InteractionResponse, if the request contained a success URL.
Some small refactorings in ResponseMapper:

introduced the instance variable $transaction
getRedirectUrl: renamed to getSuccessRedirectUrl
getPaymentMethod is called by getSuccessRedirectUrl (instead of passing its result as a parameter)

Coverage decreased (-0.1%) to 99.867% when pulling 0c06ecc1e518112cf2836a5f461d9301394de4d8 on reka:form-interaction-response into b5360351b130b0d419246ee826054d7c71f31249 on wirecard:128-synch-redesign.

Coverage remained the same at 100.0% when pulling a15bb0f438b48c6eb7ceff6c0482d83eb058c2b2 on reka:form-interaction-response into b5360351b130b0d419246ee826054d7c71f31249 on wirecard:128-synch-redesign.


When back to lobby after a game ends, the game start button is enabled by default

The intractable state of game start button should be linked to the readiness states of the players

This issue should be resolved in #99


Update Web Module Examples

Current Situation
The auto-convert utility does not know how to convert usages of exported web modules. As such, some example in the docs need to be manually updated: https://github.com/idom-team/idom/tree/main/docs/source/guides/escape-hatches/_examples
Proposed Actions
Fix them

Is this still open?

nope


How to add click event to marker

Can you help me, thanks

Take a look at this sample
https://www.jmelosegui.com/map/marker/ClientEvents

thank you!


Abstract HTML table parsing into a util function

This is becoming a pattern used in #324, #361, #362, #363, #359, #365, #364. I see no reason it can't be abstracted into a shared util. Pandas has read_html for this purpose, but that's been removed (#345).

(Yes, I'm willing to contribute this.)

Sure. Let's do it.

#438 added an Excel parsing util that could serve as a model/challenge.

@chriszs , I think I'm missing it?


Super cool! Had two questions to better understand how this works...

I was reading through the repo to get a better understanding of contract development in Rust and this all looks really cool! I had two technical questions though, if you didn't mind me asking.

In the typescript client services files, when you call gateway.rpc(address, payload, options), how does the remote node executing your request know which contract function you are calling? I might be missing something huge but it seems like the contract somehow can "magically" infer which contract function you are calling based on the payload you pass in?

Does the current repo actually have Oasis nodes test the submitted models against the secret test data? I saw that there is an evaluation_program field in the Rust contract but I don't see it being used anywhere. If not, do you know how you would instruct a node to run the evaluation script on the submitted models?

how does the remote node executing your request know which contract function you are calling?

Good question! You're actually exactly right about the contract inferring the function from the payload. The "magical" part is that the Oasis Eth/WASI SDK generates the dispatch code for you. Basically what happens is

the contract requests the input (i.e. payload), which is encoded as fn_index || encoded_fn_args
it deserializes the input as a tagged union (the tag is the requested function, the other members are the args)
it matches the tag and dispatches the args to the method you wrote

The client's generated code packs the payload up in the expected format.

Oasis nodes test the submitted models against the secret test data

Yes and no. The current SANDBOXED_EVALUATOR_IMAGE actually bakes in the evaluation program, which isn't ideal because then you'd need to trust the evaluation program (possibly through auditing, possibly through static analysis). Otherwise, you'd take the evaluator image and make that a sandbox in which you run the untrusted evaluation program. This demo was written with the assumption that the target environment is a whole-VM enclave like that offered by AMD SEV(-SNP). If you wanted to use a linked-library enclave, you'd need to retool the sandbox a bit and do some trickery for running the evaluation program (e.g., by embedding a python interpreter).

Ahh ok I see wow. Thanks so much for all of this info. This honestly clears up SO MUCH confusion!

Cool, glad it makes sense! I'll close this issue for now, but you should feel encouraged to reopen it or make a new one if you have any other questions.


Error: ionic run ios

Hello,
I am trying to run ionic 2 application in my device(iphone 5s), but it giving me error:
Error: Error code 65 for command: xcodebuild with args: -xcconfig,/Users/AdityaBatra/documents/ionic/sidemenuapp/platforms/ios/cordova/build-debug.xcconfig,-project,sidemenuapp.xcodeproj,-target,sidemenuapp,-configuration,Debug,-destination,platform=iOS,build,CONFIGURATION_BUILD_DIR=/Users/AdityaBatra/documents/ionic/sidemenuapp/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/AdityaBatra/documents/ionic/sidemenuapp/platforms/ios/build/sharedpch

I have also tried ionic run ios --device but it's not working.

This issue was moved to driftyco/ionic-cli#1336

Hello, thanks for opening an issue with us! Because this issue is an Ionic cli related issue and not an Ionic framework related issue i have moved this issue to the appropriate repo. Thanks for using Ionic!


[enchancement] use GSL to solve radial equations

Major refactoring of the radial solver. Custom RK4 integrator is removed in favour of GSL implementation. Bound state energies for Schroedinger and Dirac equations are in good agreement comparing with analytical results. Other tweaks:

atom utility is refactored
unused files are deleted
generation of radial functions is improved; in particular generation of LAPW basis for high orbital quantum numbers is enchanced
minor refactoring related to Poisson solver

cscs-ci run default

It looks alright to me. Since the code use GSL for RK method, it might be useful to give the user the choice about the method. RK4 is a bit borderline, I would use gsl_odeiv2_step_rk8pd as it has better mathematical properties but it might simply not be relevant for these calculations.

actually, the code does const gsl_odeiv2_step_type* T = gsl_odeiv2_step_rk8pd;. I was thinking to add a flexibility of controlling this, but then decided to fix it to rk8pd

It looks alright to me. Since the code use GSL for RK method, it might be useful to give the user the choice about the method. RK4 is a bit borderline, I would use gsl_odeiv2_step_rk8pd as it has better mathematical properties but it might simply not be relevant for these calculations.

actually, the code does const gsl_odeiv2_step_type* T = gsl_odeiv2_step_rk8pd;. I was thinking to add a flexibility of controlling this, but then decided to fix it to rk8pd

Perfect.

I have no objection to merge this PR. Most of my comments are cosmetics

I have no objection to merge this PR. Most of my comments are cosmetics

I will quickly do the optmisations of the divisions


Added Readme.md

Description
This update introduces a Stress Prediction Model that leverages physiological and behavioral data (e.g., heart rate, sleep patterns) to predict stress levels. It uses machine learning algorithms for accurate predictions, aiming to help individuals and organizations manage stress effectively. Dependencies include Scikit-learn, Pandas, and Flask (optional for web interface).
Fixes # (1562)
Type of change

[x] Added a new machine learning frameworks, libraries or software.
[X] Documentation update

Checklist:

[X] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

@sanjay-kv kindly review my file and assign an appropriate label.


Some Bloqs will not serialize.

This issue was originally discovered by serializing a composite bloq which contains an AND bloq.  The AND bloq fails to serialize and raises this error.  It is likely that there are other bloqs which will have similar problems.
A summary of the path to the error is as follows:
The path to the error is as follows:

Attempts to decompose bloq using bloq.decompose_bloq()

AND does not have this method implemented causing the decomposition to fallback on decompose_from_cirq_style_method().

This leads to it iterating through each of the individual operations.

One of these operations is both classically controlled and is not a gate which causes _extract_bloq_from_op to raise the error.

Please assign me to this issue as I am currently working on a fix.

The serialization code now tries to build a composite bloq; and if a composite bloq doesn't exist / cannot be built (eg: due to classically controlled operations appearing in the decomposition) it gracefully considers the bloq to be a leaf bloq. This issue can now be closed.
In [8]: bloqs_from_proto(bloqs_to_proto(And()))
Out[8]:
[And(cv1=1, cv2=1, uncompute=0),
 Allocate(dtype=QAny(bitsize=1)),
 Hadamard(),
 TGate(is_adjoint=0),
 CNOT(),
 TGate(is_adjoint=1),
 SGate(is_adjoint=0),
 ArbitraryClifford(n=2)]

In [10]: bloqs_from_proto(bloqs_to_proto(And().adjoint()))
Out[10]: [And(cv1=1, cv2=1, uncompute=1), ArbitraryClifford(n=2)]


Request for Documentation: Elastic Search indexing progress bar gets stuck for a long time.

Mattermost user george from https://community-daily.mattermost.com has requested the following be documented:
Another question:

> out of curiosity, why does the ElasticSearch Index fly through the first 95% of indexing then take almost 20 minutes for the last 5%?

The size of the data to be indexed is estimated, and on large databases this can be somewhat inaccurate, leading to the progress bar getting stuck near the end for an extended period. The indexing is still going on behind the scenes, it's just the progress estimate can be quite inaccurate.

See the original post here.
This issue was generated from Mattermost using the Doc Up plugin.

Documentation updated via: https://github.com/mattermost/docs/pull/4338


Add disabled state styling for switch fields

Currently has 1 opacity. Needs 0.5 for default WinterCMS disabled state
Before

After

@AIC-BV @LukeTowers does this also switch the cursor to a "disabled" cursor? If not, I think it should for usability. :)

No it doesn't @bennothommo, good call!


Stay on PokeStop if there is a lure

Expected Behavior
Bot stay on PokeStop that lure has been set and wait for pokemons coming
Actual Behavior
Bot go to next nearest PokeStop and leaving
Steps to Reproduce
Set location on lured pokestop then start Bot
Other Information
OS: Windows 8.1
Git Commit:

Does this fork detect lured pokemon? I know in the original it was introduced a little later.
If so, maybe if a pokemon encounter does occur, it should indicate whether it's a normal or lured pokemon on the console?

I think it can be nice option. I know some places where are pokestops near each other, almost always with lure module. Its nice place to get pokemons.

good question. Is OpenPoGoBot can detect lured by module or incense pokemons?

As far as i'm aware, there is no way to detect if a pokemon has appeared because a lure is present, but we can detect a lure on a pokestop. However, OpenPoGoBot currently does not support this.

Some bots show information like normal/lure/incense on catched pokemons.
I'm asking if its difference between "spawn" methods, becuase sometimes looks like OpenPoGoBot see less pokemons in same area than im seeing on other character.
On place where 6 pokestops are in usable distance, and all have lure modules in fact all the time are pokemons spawned. OpenPoGoBot after login in that area catch 1-2 pokemons and go away. Where i login other char with BlueStacks emu in that area usually i see after login 5-6 pokemons, and new are spawned all the time.

#346 allow the bot to catch lured pokemon. it still don't stop at pokestop.


Ensure Eventwatcher to mark event as handled

What this PR does / why we need it:
Eventwatcher will mark events as handled after pushing the changes. This PR contains exactly:

Add Handled state to the Event model
Add a new rpc ReportEventHandled to PipedAPI
Update eventwatcher to report it to the above API: pkg/app/piped/eventwatcher/eventwatcher.go

Which issue(s) this PR fixes:
Fixes https://github.com/pipe-cd/pipe/issues/2475
Does this PR introduce a user-facing change?:

Prevent Eventwatcher from handling events already handled

@nghialv Thank you for your suggestion. Revised all of them.

Nice update.
/lgtm

Nice
/approve


feat(connectors): generic inbound connector runtime

⚠ depends on https://github.com/camunda/connector-sdk/pull/364

Support of generic inbound connectors in the Runtime.
Minor refactoring of the outbound connector management (to support the changes in the SDK, see https://github.com/camunda/connector-sdk/pull/364)

Webhook Connector needs to be refactored to match the new pattern, but can be done as a separate issue.
related to https://github.com/camunda/team-connectors/issues/331

I'm going to go ahead with merging this PR to unblock further progress. Please reach out if you have any concerns 🙂


v209 not on bosh.io?

Hi
We're pipelining a deployment of Logsearch and Logsearch-for-Cloudfoundry. Yesterday morning our pipeline picked up a new version of the latter (v207) from bosh.io, which is apparently only compatible with v209 of Logsearch. That was published in GitHub at about the same time, but hasn't appeared on bosh.io yet. As such, our pipeline job is failing, as it's still using v208 of Logsearch.
Just wondering if v209 of Logsearch is expected to make it on to bosh.io sometime soon?
Thanks!

Hi @bruxelles86, it should be picked up automatically when new release is available on Github. We don’t do any additional steps to make it available on bosh.io. I will check what is wrong with integration, but at the same time you can use release tarball from releases page to proceed with v209.0.0 deployment.
Sent from my iPhone
On Apr 26, 2018, 11:37 +0300, Will Gant<EMAIL_ADDRESS>wrote:

Hi
We're pipelining a deployment of Logsearch and Logsearch-for-Cloudfoundry. Yesterday morning our pipeline picked up a new version of the latter (v207) from bosh.io, which is apparently only compatible with v209 of Logsearch. That was published in GitHub at about the same time, but hasn't appeared on bosh.io yet. As such, our pipeline job is failing, as it's still using v208 of Logsearch.
Just wondering if v209 of Logsearch is expected to make it on to bosh.io sometime soon?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks. We prefer using bosh.io, but will probably switch over temporarily.

We are having the same issue.  The new version of logsearch-for-cloudfoundry is getting picked up via our concourse pipeline using the bosh-io-release concourse resource, which is creating an issue with incompatibilities.
- name: logsearch-boshrelease
  type: bosh-io-release
  source:
    repository: cloudfoundry-community/logsearch-boshrelease

- name: logsearch-for-cloudfoundry
  type: bosh-io-release
  source:
    repository: cloudfoundry-community/logsearch-for-cloudfoundry

As I can see, now v209 is available on bosh.io


⚠ Bofrost.es has degraded performance

In d9514a3, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1447 ms

Resolved: Bofrost.es performance has improved in 547b0cd after 6 minutes.


To add more detail regions

Hello.
I have a question about the detail region.
If I want to add more genes to exclude or add, should I make the BED file like below?
And read as a dataframe or something?

And what is the meaning of columns? 'score', 'probes_gene', 'probes_promoter'
Thank you!

Hi,
thank you for your patience! You could use a customized BED file, but I recommend to modify the detail_regions GRanges object. You obtain it with:
data("detail_regions") (hg19) or data("detail_regions.hg38") (hg38)


edge vs ie

It's not clear to me how to detect IE vs Edge.
Hint?

Through some unit test, i can confirm that Internet Explorer has IE has family, and Edge has Edge.


Kali Error

] Starting Caffe-Latte attack...
timeout: invalid time interval ‘bash’
Try 'timeout --help' for more information.
Warning: This program is an suid-root program or is being run by the root
user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s
xterm: DISPLAY is not set
/usr/bin/wef: line 1280: kill: (14470) - No such process
[+] Caffe-Latte Attack completed
[] Captures stored in: /opt/wef/main/captures

Thanks for your comment, ensure you are using the latest version because a few days ago I tested in depth the framework in Kali and there were errors so I think that with the latest version will work fine but I'll check it

I have only just installed and that was the error

Hey @Burgess85 the same happened to me when testing attacks that requires to open a new window in my headless installation of Kali Linux in a Rasberry Pi.
Can you specify what's your working platform?

Headless raspberry pi using Kali and screen

I don't have a Raspberry so I can't test it but I can add a command/option inside the framework to headless raspberries to do the AP scanning in the same terminal to avoid using the screen. I think it would be a good option

Yes that should work

I'm working on a new update because if you use airodump-ng with a specific timeout in bash it doesn't run, so the people who use headless systems won't see the scan output until it finishes


[Error]ImportError cannot open shared object file: No such file or directory

First, I compiled Boost.Python in my centos server.
sudo ./bjam toolset=gcc  --build-type=complete --layout=versioned  --with-python install
or
./bootstrap.sh
sudo ./b2 install

then no matter I using pip install or python setup.py install , after installing dlib, I always get following error:

Traceback (most recent call last):
File "avrface.py", line 7, in
import dlib
File "/usr/lib64/python2.7/site-packages/dlib-19.0.99-py2.7-linux-x86_64.egg/dlib/init.py", line 1, in
from .dlib import *
ImportError: libboost_python-gcc48-mt-1_61.so.1.61.0: cannot open shared object file: No such file or directory

But libboost_python-gcc48-mt-1_61.so.1.61.0 has been successfully installed in /usr/local/lib.
And I also tried export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib, however it dosen`t help.

I don't know why it's not working but you haven't installed it correctly somehow.  From the error, it looks like your LD_LIBRARY_PATH is not set correctly.

when I run my scripts without sudo, it works successfully.
thanks.

@tcz717 did you successfully uninstalled 'sudo installed dlib'? I'm having the same problem, but reinstalling without sudo doesn't solve my problem..


[Bug]: RemoteAPI.DumperVersion = 2022.9.99 OS: Windows 11

All of the following criteria must be met

[X] All Requirements must be installed.
[X] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[ ] Tried reinstalling the Game.
[ ] Tried reinstalling MelonLoader.
[ ] Tried restarting PC.
[ ] Was able to see the Start Screen.

Describe the issue.
[22:18:15.166] Loading MelonStartScreen...
[22:18:15.641] User32::SetTimer original: 0x7FFBF9E55860
[22:18:15.642] Applying USER32.dll::SetTimer Hook at 0x7FFBF9E55860
[22:18:15.642] Creating delegate for original USER32.dll::SetTimer (0x7FFBBA930360)
[22:18:15.642] Applied USER32.dll::SetTimer patch
[22:18:15.714] Loading Il2CppAssemblyGenerator...
[22:18:15.803] Contacting RemoteAPI...
[22:18:17.276] RemoteAPI.DumperVersion = 2022.9.99
[22:18:17.277] RemoteAPI.UnhollowerVersion = <IP_ADDRESS>
[22:18:17.278] RemoteAPI.ObfuscationRegex = ^[^I]\w+
[22:18:17.278] RemoteAPI.MappingURL = ?
[22:18:17.279] RemoteAPI.MappingFileSHA512 = null
[22:18:17.282] Using Dumper Version: 2022.9.99
[22:18:17.282] Using Il2CppAssemblyUnhollower Version = <IP_ADDRESS>
[22:18:17.283] Using Unity Dependencies Version = 2019.4.34
[22:18:17.284] Using Deobfuscation Regex = ^[^I]\w+
[22:18:17.284] Downloading Cpp2IL...
[22:18:17.292] Downloading https://github.com/SamboyCoding/Cpp2IL/releases/download/2022.9.99/Cpp2IL-2022.9.99-Windows-Netframework472.zip to C:\Users\cooky\AppData\Local\Temp\tmp6248184c.tmp
[22:18:18.853] [ERROR] System.Net.WebException: The remote server returned an error: (404) Not Found.
MelonLoader v0.5.2 Open-Beta
OS: Windows 11
Did you attach your log file?

[ ] Yes, I attached my log file to the text box above.
[ ] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

Dont cheat moron


cmd_pgp_gen: explain that the secret key is not exported to gpg

Sorry I was slow on this one...

I think the bug was all mine.


use sbg ekf output for initialization

Description

After fixing height difference and calibration problems , I updated this topic . Now we can use sbg ekf output for initialization. I also updated sbg center and I updated sensor kit descriptions before that.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

since this PR includes this changes: https://github.com/leo-drive/golf_sensor_kit_launch/pull/7 I will close this PR.


computation of MuxLM linear combination seems wrong

The current implementation of MuxLM linear combination appears to compute the linear combination of individual LMs scores only once, at the level of likelihoods returned by each LM on the full input sentence.
The correct implementation should instead compute the linear combination at the level of each ngram in the input sentence, that is: (1) for each ngram in the input sentence, combine linearly the probabilities returned by each LM on such ngram and (2) at the end, multiply all the linearly combined probablities to obtain the final likelihood.
One effect of the current implementation is that hypotheses with the same target string but obtained with different segmentations, may have different MuxLM scores -- this can be verified in the nbest list obtained without the "distinct" option such as in the following simple example:
0 ||| Morgex .  ||| Distortion0= 0 DM0= -0.693147 0 0 0 0 0 0 0 MuxLM= -13.0268 WordPenalty0= -2 PhrasePenalty0= 1 PT0= -0.20557 -0.230983 -0.422988 -2.30259 -2.30259 ||| -1.13522 ||| 0-1=0-1
0 ||| Morgex .  ||| Distortion0= 0 DM0= -0.422349 0 0 0 -0.367725 0 0 0 MuxLM= -13.6894 WordPenalty0= -2 PhrasePenalty0= 2 PT0= -0.20557 -0.230983 -0.63387 -0.520142 -0.55555 ||| -1.24292 ||| 0=0 1=1

To rephase, given a query with the input sentece "w1 | w2 w3" and a MuxLM with two LMs (one is BG and one is ADAPTIVE) with alpha=0.5, the current implementation appears to compute:
log( 0.5 * exp( log_BG(w1) + log_BG(w2|w1) + log_BG(w3|w1 w2) ) + 0.5 * exp( log_AD(w1) + log_AD(w2|w1) + log_AD(w3|w1 w2) ) )
i.e.
log( 0.5 * exp( log_likelyhood_BG(w1 w2 w3) ) + 0.5 * exp( log_likelyhood_AD(w1 w2 w3) ) )
It appears that the correct realization should be the sum of the linear combination of the probabilities of the ngrams:
log( 0.5 * exp( log_BG(w1)) + 0.5 * exp (log_AD(w1))) +
log( 0.5 * exp( log_BG(w2|w1)) + 0.5 * exp (log_AD(w2|w1))) +
log( 0.5 * exp( log_BG(w3|w1 w2)) + 0.5 * exp (log_AD(w3|w1 w2)))

@cidermole from the code point of views, it is quite clear the choice of realizing the linear combination at the level of likelihood instead of ngrams: the former exploits the current sw organizzazion about features. The latter requires either a rather strong code reorganization in the generic LMs case or a specific implementation for KenLM LMs (similar to what Nicola did for the interpolated IRST LMs).

Hi @cattoni @cidermole
So if I understand correctly, this is actually a bug, but fixing it would require a big code refactoring because the right implementation simply cannot be realized with the current architecture of Moses, is it correct?
If yes, what is the extent of the bug? Is there the possibility of a further increase in terms of BLEU score?

after a discussion with @cattoni I understood that practically this could not be a real bug. More precisely the way MuxLM computes the interpolation is a sort of approximation that we are not sure is affecting MMT quality.
Id @cidermole confirm that, I will remove the bug label for now, and just keep this issue as a more generic "discussion".

@cattoni
Roldano, this is exactly the point that Ken was criticising here when I told him how I interpolate LMs. If you run translation experiments, it seems that the "correct" way of linear LM interpolation on the word level in fact performs 0.4 BLEU worse on benchmark-1.1. It also takes more CPU time and is uglier to implement as an abstraction in the LM feature layer (see https://github.com/ModernMT/mosesdecoder/tree/features/verify-interpolation if you like).

I start to get confused, sorry.
@cattoni wrote:
"The current implementation of MuxLM linear combination appears to compute the linear combination of individual LMs scores only once, at the level of likelihoods returned by each LM on the full input sentence."
I guess you cannot perform search by interpolating LMs at the level of the "full input sentence". I prefer to believe instead that we are interpolating at the phrase-level, correct? Even it this is the case,
I don't think it is conceptually wrong. What is missing in the equation by @cattoni
log( 0.5 * exp( log_likelyhood_BG(w1 w2 w3) ) + 0.5 * exp( log_likelyhood_AD(w1 w2 w3) ) )
is that w1 w2 w3 should be conditioned to the same context/history provided by the search state.
I see some advantages in computing the mixture in this way: one assumes that all n-grams inside a phrase are generated by one source with some prior probability. Hence, it is forbidden  that phrases can be generated by switching from one source to another. Actually during search,  different segmentations are tested which actually also allow more alternation among language model sources. It is difficult to tell the effect on the actual probabilities induced by different segmentations. Here is a simple case comparing two segmentation hypotheses:

An alternative form assuming are variables are positive is:

Hence, we can easily see when the inequality holds and when not (hence, the inverse inequality holds)

@cidermole
Thanks, David, for the additional information. So the current implementation, in spite of being an approximation, is faster and perform better than the "correct" one, at least on benchmark-1.1
A good news, I would say :-)


Fixed external link

Issue

worked on the issue #75, although I have not tested it.
Description

am having an issue with npm on my computer
merge it then test it out but I was able to figure out that it is the rel attribute.
Checklist

[ ] Added contributor object in ascending order in contributors.json
[ ] Github action build passing
[ ] No merge conflicts

Great @binismail i will test it and merge it


namedtuple bug in evaluate.py

Rasa NLU version: 0.13.x
Operating system (windows, osx, ...): osx
Content of model configuration file: irrelevant

Issue:
Give the following error
2018-08-08 14:17:35 INFO     __main__  - Intent evaluation results:
Traceback (most recent call last):
  File "/anaconda3/envs/eas/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/anaconda3/envs/eas/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/anaconda3/envs/eas/lib/python3.6/site-packages/rasa_nlu/evaluate.py", line 843, in <module>
    main()
  File "/anaconda3/envs/eas/lib/python3.6/site-packages/rasa_nlu/evaluate.py", line 837, in main
    cmdline_args.histogram)
  File "/anaconda3/envs/eas/lib/python3.6/site-packages/rasa_nlu/evaluate.py", line 630, in run_evaluation
    intent_hist_filename)
  File "/anaconda3/envs/eas/lib/python3.6/site-packages/rasa_nlu/evaluate.py", line 258, in evaluate_intents
    intent_results = remove_empty_intent_examples(intent_results)
  File "/anaconda3/envs/eas/lib/python3.6/site-packages/rasa_nlu/evaluate.py", line 176, in remove_empty_intent_examples
    r.prediction = ""
AttributeError: can't set attribute

substituting line 176 with the line below solves the problem
r = r._replace(prediction="")

Thanks for raising this issue, @JoeyFaulkner will get back to you about it soon.

Hi!
I don't think It's related to the domain. In my understanding, it is the combination of two things that have changed in version 0.13.x: (1) do not predict anything if feature vector contains only zeros in tensorflow embedding classifier and (2) rasa_nlu's evaluate.py using namedtuples and replacing None predictions with empty string for intent predictions in line 176 (r.prediction = ""), which should be (r = r._replace(prediction="")) according to https://docs.python.org/3/library/collections.html#collections.namedtuple, imho.
what I do:

train tensorflow embedding intent classifier (using config_embedding.yml configuration)
evaluate the model on data that contains examples that will yield all-zero embedding vectors, as
The issue does not arise with models trained with different configurations.

To replicate the issue, do the following:

train NLU model using franken_data.json from restaurantbot example of rasa core, as:

python -m rasa_nlu.train -o models -d franken_data.json -c config_embedding.yml

try to evaluate that model on nlu.md data from moodbot example, as:

python -m rasa_nlu.evaluate -d nlu.md -m models/default/model_xxxxxxxx-xxxxxx

I hope I made the issue clearer.

that makes sense! would you like to submit this as a PR? please reference this issue when you do so. Thanks!


JQuery selectors that returs elements by value of attribute contains URL don't work

'@test'['By attr'] = {
    '2.': function () {
        act.click('[href="https://www.google.ru/"]');
    }
};

It's dublicate of https://github.com/DevExpress/testcafe-hammerhead/issues/340


How to regenerate crd

hi，I want to modify the api and add a field. How can I regenerate the crd file after modifying the source code?

./dev/run_code_generator.sh

./dev/run_code_generator.sh

Thanks for your reply，but after I executed this script, crd was not updated.
this is output:

Check this out https://github.com/Altinity/clickhouse-operator/pull/1580#issuecomment-2518016900

@liuxianXX you need manually change CRD in deploy/builder


XLNet support for Reader

Hi,
Currently the reader is operating using a pre trained BERT pytorch model. I am wondering whether you plan on adding support for an XLNet pretrained model once it is released for pytorch?

Indeed having a XLNet reader would be a nice addition to cdQA given its results on the QA tasks.
The @huggingface community is currently implementing XLNet in their transformers repository. See this PR: https://github.com/huggingface/pytorch-pretrained-BERT/pull/711
We are waiting for the official code release to start reverse-engineering the script in order to see if it would be easy to add it to cdQA.
We might need some help though so feel free to comment or PR if you have ideas!

related: https://github.com/renatoviolin/xlnet

@huggingface just released their new update, so we started to explore XLNet for cdQA (PR #205)

Implementation of XLNetForQuestionAnswering is pretty different from BertForQuestionAnswering  and the official HF version does not output the logits for now. (cf. https://github.com/huggingface/pytorch-transformers/issues/838)
XLNetForQuestionAnswering uses Beam Search to find the best (and more probable) span, while BertForQuestionAnswering maximises the start_score and end_score separately.
Due to this limitation, the XLNet support for Reader will take a bit more time than expected.


Fresh installation result in prompt-toolkit ImportError

This is blocking me, and I haven't been able to find a reference to this elsewhere, or a solution. I suspect a version conflict, but even completely cleaning and reinstalling produces the same error every time.
  File "/usr/lib/python3/dist-packages/awsshell/app.py", line 13, in <module>     from prompt_toolkit.shortcuts import create_eventloop ImportError: cannot import name 'create_eventloop' from 'prompt_toolkit.shortcuts' (/usr/lib/python3/dist-packages/prompt_toolkit/shortcuts/__init__.py)
Even digging into the current versions of both aws-shell and prompt-toolkit, there appears to be a wildcard import in the past for the shortcuts/init.py, which was changed to an explicit list, and it no longer includes the create_eventloop that the awsshell/app.py is looking for.
Further puzzling is that on my prior system (Ubuntu 16.10) prompt-toolkit isn't even installed, and aws-shell works perfectly. Removing prompt-toolkit from the current system only moves the error to looking for it.
Possibly relevant system and versions:
Pop_OS 20.10
 $ aws --version
aws-cli/2.0.45 Python/3.7.3 Linux/5.8.0-7625-generic exe/x86_64.pop.20

(note, this was all also failing identically with aws-cli/1.18.170 Python/3.8.6 Linux/5.8.0-7625-generic botocore/1.19.10)
Install -> error sequence
 $ sudo apt-get install aws-shell
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  awscli docutils-common libimagequant0 python3-boto3 python3-botocore python3-configobj python3-dateutil python3-docutils python3-jmespath python3-olefile python3-pil python3-prompt-toolkit
  python3-pyasn1 python3-roman python3-rsa python3-s3transfer python3-wcwidth
Suggested packages:
  python-configobj-doc docutils-doc fonts-linuxlibertine | ttf-linux-libertine texlive-lang-french texlive-latex-base texlive-latex-recommended python-pil-doc python3-pil-dbg
The following NEW packages will be installed:
  aws-shell awscli docutils-common libimagequant0 python3-boto3 python3-botocore python3-configobj python3-dateutil python3-docutils python3-jmespath python3-olefile python3-pil
  python3-prompt-toolkit python3-pyasn1 python3-roman python3-rsa python3-s3transfer python3-wcwidth
0 upgraded, 18 newly installed, 0 to remove and 14 not upgraded.
Need to get 0 B/5,886 kB of archives.
After this operation, 64.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package python3-dateutil.
(Reading database ... 283601 files and directories currently installed.)
Preparing to unpack .../00-python3-dateutil_2.8.1-4_all.deb ...
Unpacking python3-dateutil (2.8.1-4) ...
Selecting previously unselected package docutils-common.
Preparing to unpack .../01-docutils-common_0.16+dfsg-3_all.deb ...
Unpacking docutils-common (0.16+dfsg-3) ...
Selecting previously unselected package python3-roman.
Preparing to unpack .../02-python3-roman_2.0.0-5_all.deb ...
Unpacking python3-roman (2.0.0-5) ...
Selecting previously unselected package python3-docutils.
Preparing to unpack .../03-python3-docutils_0.16+dfsg-3_all.deb ...
Unpacking python3-docutils (0.16+dfsg-3) ...
Selecting previously unselected package python3-jmespath.
Preparing to unpack .../04-python3-jmespath_0.10.0-1_all.deb ...
Unpacking python3-jmespath (0.10.0-1) ...
Selecting previously unselected package python3-botocore.
Preparing to unpack .../05-python3-botocore_1.17.22+repack-1_all.deb ...
Unpacking python3-botocore (1.17.22+repack-1) ...
Selecting previously unselected package python3-pyasn1.
Preparing to unpack .../06-python3-pyasn1_0.4.8-1_all.deb ...
Unpacking python3-pyasn1 (0.4.8-1) ...
Selecting previously unselected package python3-rsa.
Preparing to unpack .../07-python3-rsa_4.0-4_all.deb ...
Unpacking python3-rsa (4.0-4) ...
Selecting previously unselected package python3-s3transfer.
Preparing to unpack .../08-python3-s3transfer_0.3.3-1_all.deb ...
Unpacking python3-s3transfer (0.3.3-1) ...
Selecting previously unselected package awscli.
Preparing to unpack .../09-awscli_1.18.111-1_all.deb ...
Unpacking awscli (1.18.111-1) ...
Selecting previously unselected package python3-boto3.
Preparing to unpack .../10-python3-boto3_1.13.14-1_all.deb ...
Unpacking python3-boto3 (1.13.14-1) ...
Selecting previously unselected package python3-configobj.
Preparing to unpack .../11-python3-configobj_5.0.6-4_all.deb ...
Unpacking python3-configobj (5.0.6-4) ...
Selecting previously unselected package python3-wcwidth.
Preparing to unpack .../12-python3-wcwidth_0.1.9+dfsg1-2_all.deb ...
Unpacking python3-wcwidth (0.1.9+dfsg1-2) ...
Selecting previously unselected package python3-prompt-toolkit.
Preparing to unpack .../13-python3-prompt-toolkit_3.0.6-1_all.deb ...
Unpacking python3-prompt-toolkit (3.0.6-1) ...
Selecting previously unselected package aws-shell.
Preparing to unpack .../14-aws-shell_0.2.1-1_all.deb ...
Unpacking aws-shell (0.2.1-1) ...
Selecting previously unselected package libimagequant0:amd64.
Preparing to unpack .../15-libimagequant0_2.12.2-1.1_amd64.deb ...
Unpacking libimagequant0:amd64 (2.12.2-1.1) ...
Selecting previously unselected package python3-olefile.
Preparing to unpack .../16-python3-olefile_0.46-2_all.deb ...
Unpacking python3-olefile (0.46-2) ...
Selecting previously unselected package python3-pil:amd64.
Preparing to unpack .../17-python3-pil_7.2.0-1_amd64.deb ...
Unpacking python3-pil:amd64 (7.2.0-1) ...
Setting up python3-olefile (0.46-2) ...
Setting up python3-roman (2.0.0-5) ...
Setting up python3-configobj (5.0.6-4) ...
Setting up python3-wcwidth (0.1.9+dfsg1-2) ...
Setting up python3-jmespath (0.10.0-1) ...
Setting up libimagequant0:amd64 (2.12.2-1.1) ...
Setting up docutils-common (0.16+dfsg-3) ...
Setting up python3-pyasn1 (0.4.8-1) ...
Setting up python3-dateutil (2.8.1-4) ...
Setting up python3-prompt-toolkit (3.0.6-1) ...
Setting up python3-pil:amd64 (7.2.0-1) ...
Setting up python3-rsa (4.0-4) ...
Processing triggers for libc-bin (2.32-0ubuntu3) ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for shared-mime-info (2.0-1) ...
Processing triggers for sgml-base (1.30) ...
Setting up python3-docutils (0.16+dfsg-3) ...
update-alternatives: using /usr/share/docutils/scripts/python3/rst-buildhtml to provide /usr/bin/rst-buildhtml (rst-buildhtml) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2html to provide /usr/bin/rst2html (rst2html) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2html4 to provide /usr/bin/rst2html4 (rst2html4) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2html5 to provide /usr/bin/rst2html5 (rst2html5) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2latex to provide /usr/bin/rst2latex (rst2latex) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2man to provide /usr/bin/rst2man (rst2man) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2odt to provide /usr/bin/rst2odt (rst2odt) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2odt_prepstyles to provide /usr/bin/rst2odt_prepstyles (rst2odt_prepstyles) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2pseudoxml to provide /usr/bin/rst2pseudoxml (rst2pseudoxml) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2s5 to provide /usr/bin/rst2s5 (rst2s5) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2xetex to provide /usr/bin/rst2xetex (rst2xetex) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rst2xml to provide /usr/bin/rst2xml (rst2xml) in auto mode
update-alternatives: using /usr/share/docutils/scripts/python3/rstpep2html to provide /usr/bin/rstpep2html (rstpep2html) in auto mode
Setting up python3-botocore (1.17.22+repack-1) ...
Setting up python3-s3transfer (0.3.3-1) ...
Setting up awscli (1.18.111-1) ...
Setting up python3-boto3 (1.13.14-1) ...
Setting up aws-shell (0.2.1-1) ...

 $ aws-shell
Traceback (most recent call last):
  File "/usr/bin/aws-shell", line 11, in <module>
    load_entry_point('aws-shell==0.2.1', 'console_scripts', 'aws-shell')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 488, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2861, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2461, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2467, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/awsshell/__init__.py", line 9, in <module>
    from awsshell import app
  File "/usr/lib/python3/dist-packages/awsshell/app.py", line 13, in <module>
    from prompt_toolkit.shortcuts import create_eventloop
ImportError: cannot import name 'create_eventloop' from 'prompt_toolkit.shortcuts' (/usr/lib/python3/dist-packages/prompt_toolkit/shortcuts/__init__.py)
 $

https://stackoverflow.com/a/52019820 worked for me.

Also same issue for me in Ubuntu 20.04.  Tried all the solutions suggested in stack overflow link, but not worked.

I've managed to get it to work on Ubuntu 20.04 by uninstalling, and reinstalling from scratch with
pip install aws-shell --user
or
sudo pip install aws-shell --user
If you use the latter method, you might have to update your path to also include /root/.local/bin since that's where the scripts are installed.


Offline not centered

Before:

After:

This is caused due to the fact that the Song icon aint present any longer.
The offline text shifts to the left but the clickbox doesnt get updated.
Means the right side from the scrolling offline text is still clickable.

We can try to use the flex layout in that case @kittinan .

@ntsd Could you help to fix this issue?

Not sure what theme is this I think it's a customize one. @zero5enpai I suggest using flex-grow on the name, it will stretch when the cover is not found.

@ntsd I'm not using a custom theme. Using Novatorem theme atm-

@kittinan @zero5enpai Fix by this PR https://github.com/kittinan/spotify-github-profile/pull/67.

tyvm!
The offline scroll is still kinda offset tho- ^^'


Upgrading agent to 7.39.0 breaks SQLServer integration

Additional environment details (Operating System, Cloud provider, etc):
datadog agent from the official docker hub repository: datadog/agent:7.38.2 and datadog/agent:7.39.0
Steps to reproduce the issue:

Have SQLServer integration configured as follows
Use the agent datadog/agent:7.38.2 (see it working)
Update agent to datadog/agent:7.39.0 (see it breaking)

/etc/local/datadog-agent/conf.d/sqlserver.d/conf.yaml

init_config:

instances:
  - host: my-host-name.foo.bar
    port: 1433
    username: %redacted%
    password: %redacted%
    database: 10001_example
    connector: odbc
    driver: /opt/microsoft/msodbcsql17/lib64/libmsodbcsql-17.10.so.1.1
    tags:
      - region:eu-central-1
      - environment:staging
      - dbinstanceclass:sqlserver
      - engine:sqlserver

Describe the results you received:
All monitoring of SQLServer stoped because of an error trying to connect to all DBs, even though the configuration is the same.

Error running check: [{"message": "can only concatenate str (not \"int\") to str", "traceback": "Traceback (most recent call last):
File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py\", line 1116, in run
self.check(instance)
File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/sqlserver.py\", line 624, in check
self.load_static_information()
File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/sqlserver.py\", line 236, in load_static_information
with self.connection.open_managed_default_connection():
File \"/opt/datadog-agent/embedded/lib/python3.8/contextlib.py\", line 113, in __enter__
return next(self.gen)
File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/connection.py\", line 276, in open_managed_default_connection
with self._open_managed_db_connections(self.DEFAULT_DB_KEY, key_prefix=key_prefix):
File \"/opt/datadog-agent/embedded/lib/python3.8/contextlib.py\", line 113, in __enter__
return next(self.gen)
File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/connection.py\", line 281, in _open_managed_db_connections
self.open_db_connections(db_key, db_name, key_prefix=key_prefix)
File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/connection.py\", line 294, in open_db_connections
conn_key = self._conn_key(db_key, db_name, key_prefix)
File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/connection.py\", line 495, in _conn_key
dsn, host, username, password, database, driver = self._get_access_info(db_key, db_name)
File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/connection.py\", line 447, in _get_access_info
host = self._get_host_with_port()
File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/sqlserver/connection.py\", line 491, in _get_host_with_port
return split_host + \",\" + port*TypeError: can only concatenate str (not \"int\") to str*"}]

Describe the results you expected:
Nothing changing to base monitoring checks
Additional information you deem important (e.g. issue happens only occasionally):

The issue took down all environments monitoring (no exceptions)
The mitigation has been to rollback to 7.38.2 at this point
A follow-up support ticket has been opened with a proper flare

The only related change I see in the backlog is:
https://github.com/DataDog/integrations-core/pull/12610
I'm double-checking it against the error stack...

Thanks @EmmaOnThursday, for the quick fix! I'm going to test this as soon as there is a release, but we can close this issue since the patch is already merged.

@marceloboeira feel free to follow up with any additional problems! Thanks again for raising the issue.


Change from BackAndroid to BackHandler

closes #1330
If someone else could double check this that would be awesome, but looks like the completely same syntax, just a different name!

Got a warning too, the replacement would be cool :)
Thanks

so you are going to drop the support for RN < 0.44?

Sorry that was due to prettier. I will fix it
On Tue, May 2, 2017 at 03:23 Neo<EMAIL_ADDRESS>wrote:

so you are going to drop the support for RN < 0.44?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/react-community/react-navigation/pull/1333#issuecomment-298522884,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbacONpTBF6-mbqsqFmyCtcx35Gvfq4ks5r1tnXgaJpZM4NNTJk
.

Any update from the core team on this one? This one is frustrating to have with RN 0.44 since it throws a console.warn which comes up every time you load the app in dev.

As a temporary workaround, you can add this line to your App.js to prevent yellow box messages.
console.ignoredYellowBox = ['Warning: BackAndroid']

@weby Thanks!

I know I totally agree. In fact I have trailing commas turned on in my atom
plugin, don't know how it happened. I'll try to fix the commit tomorrow.
On Thu, May 4, 2017 at 22:50 Kevin Cooper<EMAIL_ADDRESS>wrote:

@cooperka requested changes on this pull request.
In src/createNavigationContainer.js
https://github.com/react-community/react-navigation/pull/1333#discussion_r114925219
:

@@ -19,7 +19,7 @@ type NavigationContainerProps = {
onNavigationStateChange?: (
NavigationState,
NavigationState,

NavigationAction,

NavigationAction

@zackify https://github.com/zackify These trailing commas are
intentional; they help give better diffs when adding/removing/reorganizing
things in a list of items. Please keep them in :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/react-community/react-navigation/pull/1333#pullrequestreview-36428000,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbacGhgpot1Nq4EIA_htw4H1XtWuWHOks5r2o5wgaJpZM4NNTJk
.

 That was being poorly translated.

Okay, I fixed the commas!

Travis is failing because BackHandler is undefined. You also need to update the RN version probably?

I don't think we should merge this until we bump react-native
On May 9, 2017 4:53 PM, "Paul Thompson"<EMAIL_ADDRESS>wrote:

@paritho approved this pull request.
I run this changes locally for each project and they fix the warnings.
Functionality is the same.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/react-community/react-navigation/pull/1333#pullrequestreview-37048450,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATTXSqxkaBix69V0N0Wna8M2w7ItuywEks5r4Hl7gaJpZM4NNTJk
.

How about news?

@dominicrj23 this is currently blocking me from updating my project to .44.
I think its save to assume that people who are upping their react-navigation won't by using an older RN version?

this is currently blocking me

It's a deprecation warning. It shouldn't block you. You can just suppress the warning.

Sorry Zach! I didn't see this one and already reviewed #1520.
Thanks for your work here. Hope to see more contributions from you! :)


make get_all_security_groups filter AND match group ids, not OR them

Currently, if you call get_all_security_groups() with values for group_ids and filters, security groups will be returned if they match the group_ids OR the filters. This patch changes it so that they will be returned if they match the group_ids AND the filters.  A test case is also included so you can confirm the old behavior fails the unit test.

Coverage increased (+0.001%) to 93.409% when pulling 2d359f5883f491e2e2372a8f0eb1e33bd1642e82 on Dawil:fix-get-all-security-groups-filtering into 4eaf5d527ef5d619aedbc48c9e09d3364239b41d on spulec:master.

Thanks!


Support chunk for print media

I admit that this seems to be a rather esoteric configuration, so let me first explain the general idea and use case:

I'd like to support (at least partially) the copying of media files (see issue #482 )
I have made an initial implementation, which executes copy instructions when the function file:copy is available (which is the case, by the way, for users of Oxygen). See PR 483.
Directly executable copy instructions are only possible, if both the source and the destination are known as absolute file paths. That means that i have to resolve every relative URI in ' img/@src` against the base-uri() of the HTML file.
In case of a regular, non-chunked transformation i don't know the destination of the transformations primary result (the HTML file), so i don't know the base-uri for copy instructions.
But chunked output can't be done without knowing the base-uri for HTML files, that's the rationale for $chunk-output-base-uri.
So i am able to generate executable copy instructions only when doing chunked output.
That is fine for online publishing, but what can i do if i am interested in PDF output?
Solution: Doing "fake chunking"  by setting the parameter $chunk-include to the empty list. I will get only one file at the file path that is the combination of $chunk-output-base-uri and $chunk. And i get executable copy instructions since the base-uri in known.

This works well when i use docbook.xsl for transformation. It does not, however, when i use print.xsl for paged media. The Error message is
Error at char 56 in expression in xsl:variable/@select on line 437 column 45 of chunk-cleanup.xsl:
  FORG0002  Base URI {} is not an absolute URI. Found while atomizing the value of parameter
  $adjusted-uri in {supplied} on line 647. Found while atomizing the value of variable
  $adjusted-uri in {xsl:apply-templates} on line 621

This error is independent of the value of the parameter $chunk-include, it also happens with the default value. I think the reason is that print.xsl has never been tested with the chunk mechanism.
I don't know how to use the XSpec based test mechanism  for this special case, so i made a test case in the attached archive. The included shell script should explain how it is to be used.
testcase.zip
Greetings, Frank

The whole idea of chunk support for print media is based on the conviction, that there is no other way to find out the base uri of the primary output document than to use the $chunk-output-base-uri parameter. I never wanted print files to be chunked. I just wanted the current outpu URI.
Today i have learned that there is a fn:current-output-uri standard function in XSLT 3. Sigh.


Error when im trying to run Wiom 1.3.4

I was trying to run Wiom on my OS ( debian based ) and i had a problem beacuse when i typed "wiom -w" it appeared an error that you can see in the image below.
I look into the code and i saw that there are a few lines that are comments that are not commented i think. How i can fix that?
Thank you : )

I'm so sorry about that, the reason is that I screwed up git merge... Surely you can comment on the parts that report invalid syntax. I thought I had uploaded the fixed version to Github... Where and when did you download it - what version is it?
Alternatively, try cloning the repository and installing it directly from there.
PS: I found more bugs in the code, I'm planning an update for early June.

Hi, sorry for the late respond.
I tried to comment those "strange" lines but i couldn´t run it anyway.  That error occurs to me in version 1.3.4.  So i decided to try with version 1.3.3. I did the git clone and i ran it, it was everything okey, you can run this version without any problem. But what i saw is when you try to run for example "sudo wiom -w" ,it nothing happens  and i try that with every option of the manual.

I've published a new release (version 1.3.5) in which I fixed a few bugs. Now everything should work properly.
Please let me know if your problem was solved by installing the new version so we can close the issue.
Thank you.

Hi, i have tried again with the newest version and now it works perfect.
Thank you so much.


Chat fails when using a trustStore

I need to make HTTPS calls to my server using a trustStore and when I add -Djava.net.ssl.trustStore=trustStore.jks to my application launch command, my calls to Slack fail with the error 'unable to find valid certification path to requested target'.
Is there a certificate I need to import into my trustStore so I can access both my application and Slack?
Thanks,

I'm not an expert on this matter yet but it seems that okhttp doesn't support the JVM option. Instead, we can call OkHttpClient.Builder#sslSocketFactory(..) in Java code to set up the configuration.

https://square.github.io/okhttp/3.x/okhttp/okhttp3/OkHttpClient.Builder.html#sslSocketFactory-javax.net.ssl.SSLSocketFactory-javax.net.ssl.X509TrustManager-
https://stackoverflow.com/questions/23103174/does-okhttp-support-accepting-self-signed-ssl-certs
https://gist.github.com/swankjesse/b8c289c8cf527d7e556b

@maury33308 Do you have any further comments? Otherwise, let me close this issue with a few days.

Allow me to close this issue. If you have more comments in the future, feel free to reopen.

Yes thanks. We have resolved the problem.Envoyé depuis mon smartphone Samsung Galaxy.
-------- Message d'origine --------De : Kazuhiro Sera<EMAIL_ADDRESS>Date : 01/07/2019  23:49  (GMT-05:00) À : seratch/jslack<EMAIL_ADDRESS>Cc : maury33308<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Objet : Re: [seratch/jslack] Chat fails when using a trustStore (#143) Allow me to close this issue. If you have more comments in the future, feel free to reopen.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/seratch/jslack/issues/143?email_source=notifications\u0026email_token=AHLQ4NIPMDRY67MXAVESDJTP5LF27A5CNFSM4HJT55W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY77DII#issuecomment-507507105",
"url": "https://github.com/seratch/jslack/issues/143?email_source=notifications\u0026email_token=AHLQ4NIPMDRY67MXAVESDJTP5LF27A5CNFSM4HJT55W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY77DII#issuecomment-507507105",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]


degenerate obsolescence/deprecation patterns

I consider "true"^^xsd:boolean to be the only acceptable value for owl:deprecated but I don't have any citation for that yet. It does make up 99.95% of the deprecation values that appear in Ubergraph.
FoodOn has one xsd:string triple
FOODON:00004474  owl:deprecated "A cutting process which outputs sliced material."@en .

and multiple "true"@en triples

FOODON:00002123
FOODON:00002136
FOODON:03302410
FOODON:03310661
FOODON:03315285
FOODON:03315561
FOODON:03317365

    <owl:Class rdf:about="&obo;FOODON_00004474">
        <rdfs:subClassOf rdf:resource="&obo;FOODON_00000071"/>
        <dcterms:contributor rdf:resource="https://orcid.org/0000-0002-8844-9165"/>
        <dcterms:date rdf:datatype="&xsd;dateTime">2023-08-01T23:32:07Z</dcterms:date>
        <rdfs:label xml:lang="en">slicing process</rdfs:label>
        <owl:deprecated xml:lang="en">A cutting process which outputs sliced material.</owl:deprecated>
    </owl:Class>

    <owl:Class rdf:about="&obo;FOODON_00002123">
        <rdfs:subClassOf rdf:resource="&owl;Thing"/>
        <obo:IAO_0000231>Redundant entry, already have 'alcoholic beverage' and both have the parent class 'plant derived fermented beverage'</obo:IAO_0000231>
        <obo:IAO_0100001 rdf:resource="&obo;FOODON_00001579"/>
        <rdfs:label xml:lang="en">obsolete: plant based alcoholic beverage</rdfs:label>
        <owl:deprecated xml:lang="en">true</owl:deprecated>
    </owl:Class>

@turbomam By definition of (one of) the spec, it should be a boolean. Comically, OWL1 defines it as:
owl:deprecated a owl:AnnotationProperty ;
     rdfs:label "deprecated" ;
     rdfs:comment "The annotation property that indicates that a given entity has been deprecated." ;
     rdfs:domain rdfs:Resource ;
     rdfs:isDefinedBy <http://www.w3.org/2002/07/owl#> ;
     rdfs:range rdfs:Resource .

I can't find a formal definition for the owl2 version of this, but owl:deprecated is an axiom that is generated by owl:DeprecatedClass or owl:DeprecatedProperty according to the OWL2 Quick Reference Guide.
I personally do both and add the owl:equivalentClass to link to the new version as per the recommendation.
An older well known but undocumented standard is the use of <vs:term_status xml:lang="en"> deprecated </vs:term_status> for document generators.
My short answer, let's switch it to a owl:DeprecatedClass, add owl:equivalentClass to point to new class and use something like ...skos:changeNote?

Thanks for the fast reply. Do you do Slack? There's been some good deprecation discussion here today: https://app.slack.com/client/T01BAB621JR/C01BDKWDS91

Anything in FoodOn except "true"^^xsd:boolean is an accident, so I'll fix those asap!  All our deprecations are in a separate file so shouldn't be hard to fix.

Deprecations now fixed and will be updated with new release shortly.
I'd like to stick to the OBO Foundry deprecation set of recommendations.  obo:IAO_0000231 is the "has obsolescence reason" which occasionally gets entered.  But in the case of a replacement I haven't bothered, since the replacement itself seems the obvious reason.  It seems to me owl:deprecated is the only signal structure needed, and the DeprecatedClass and DeprecatedProperty were some kind of attempt to isolate a deprecated item without having to change the relationships connecting that term?  But I'm willing to do whatever OBO Foundry deems best!
For cases of obo:IAO_0100001 “term replaced by” deprecations in theory I can see why one might add an equivalence to facilitate merging with old data; however this seems to break  the “no direct equivalencies allowed” ontology validation rule ODK runs.

DeprecatedClass and DeprecatedProperty are an attempt at providing some signal at the reasoner level that allows alternate behaviour with deprecated data which otherwise might not be possible through the owl:deprecated property. That might not be a problem within OBO where the data is kept updated but in external datasets, or archived datasets, the data might still point to the old classes.
I've been trying to locate the “no direct equivalencies allowed" rule, do you have a reference?
owl:equivalentClass (unlike owl:sameAs) is defined as a simple property within the spec and only means that the instances of A are also in the instances of B, therefore providing a path forward to updating datasets through an automated process. The alternatives are dcterms:isReplacedBy (actual usage unclear),  IAO_0100001 “term replaced by” is marked as "pending final vetting"  and  prov:wasInvalidatedBy, which is the ideal way to do things but a very heavy hammer.
I have been meaning to write some of this up along with ontology versioning, but I would prefer owl:equivalentClass myself since it is arguably authoritative and communicates changes outside non-OBO spaces.

@oldskeptic https://robot.obolibrary.org/reason.html#equivalent-class-axioms
IAO_0100001 “term replaced by” has probably been marked "pending final vetting" for a decade, c'est la vie.  I've seen it be the OBO foundry convention, and in active use.

I'm going to close this now.  If new requirements come up via OBO Foundry deprecation then we can implement then.

@ddooley I'm following up to this ticket because of the consequence to other projects.
You've pointed to the robot FAQ: "in many cases, inferring equivalence between two classes is usually a sign that something has gone wrong." Fair enough within a monolithic ontology that the Robot tool is creating, but that's not OBO policy and I'm not sure they had deprecation in mind for that statement.
So what is the way forward for the mouthfeel classes? I'm pushing them to the beer ontology and the OBO, so what ontological equivalency mechanism are your proposing for the reasoner? The alternative is owl:sameAs which is a bit of a can of worms.

@oldskeptic The robot reasoning/validation doesn't just apply to monolithic ontologies, nor just ones it creates, but rather any suitably formatted OWL file.  About OBO policy its #10 commitment to collaborate that mentions orthogonal term reuse, but references to that and MIEROT and how that relates to deprecation/replacement are not really emphasized in rest of docs admittedly though papers back to 2011 do talk about that.
The cleanup of old overlapping terms within OBO Foundry is a prime use case, though there are other cases.
Other thoughts: The use of owl:equivalentTo across ontology communities is a good quest to test logical satisfiability in the face of an ideal conversion from one community's vocabulary to another's.  A proposal this coming year aims to do just that for BFO/DOLCE/UFO with respect to food ontologies. That ideally paves way for knowledge graph conversion of entities including relationships.  It gets challenging if we're asking people to use terms/relations from two different ontology communities in one graph though, so I imagine wherever owlEquivalentTo is encountered between two ontology communities, its a stepping stone to term replacement by one community trying to take advantage of another's knowledge graphs.  If we drop logical stringency, accepting that ontologies may never attain logically equivalency, then a skos:exact/broad/narrow match is probably the way to go to keep track of term semantic closeness.


Cross-project flows

This adds the ability for a project to include other projects from external sources (so far just github) and make use of tasks and flows from the included project.
Example: Creating an org with NPSP from the V4S repo
Include NPSP in V4S's cumulusci.yml:
sources:
    npsp:
        github: https://github.com/SalesforceFoundation/Cumulus

Now run cci flow run npsp:install_beta. You should see a line saying the Cumulus source was fetched, and end up with an org with NPSP including the full trial config.
Details
A github source can specify a specific commit, tag, or branch. If none is specified, CumulusCI will try to find the tag from the latest release. If there's no release, it'll use master.
The external source is fetched into .cci/projects/[repo name]/[commit hash]. This means that repeated runs do not need to re-fetch the source each time if the commit is the same. (However this cache is not currently shared between multiple CumulusCI projects; maybe it should be.)
Task configs and Flow configs now get a project_config attached to them so we can keep track of which project they came from. Tasks now explicitly change directories to their project's repository root while executing, so that all our tasks which were written assuming the current directory is the repo root still work.
To do

[ ] Tests
[ ] Add support for freezing source info and sending it to MetaDeploy
[ ] Indicate sources when printing a flow summary
[ ] See other xxx comments in code

In my testing, if there was no release and no commit, github.py throws an exception
https://api.github.com/repos/SFDO-Tooling/core-sfdo-performance-tests/releases/latest
Traceback (most recent call last):
  File "/Users/pprescod/code/envs/cumulusci-py3/bin/cci", line 11, in <module>
    load_entry_point('cumulusci', 'console_scripts', 'cci')()
  File "/Users/pprescod/code/envs/cumulusci-py3/lib/python3.7/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/Users/pprescod/code/envs/cumulusci-py3/lib/python3.7/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/Users/pprescod/code/envs/cumulusci-py3/lib/python3.7/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/pprescod/code/envs/cumulusci-py3/lib/python3.7/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/pprescod/code/envs/cumulusci-py3/lib/python3.7/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/pprescod/code/envs/cumulusci-py3/lib/python3.7/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/Users/pprescod/code/CumulusCI/cumulusci/cli/cci.py", line 208, in new_func
    func(config, *args, **kw)
  File "/Users/pprescod/code/CumulusCI/cumulusci/cli/cci.py", line 1336, in flow_run
    handle_exception_debug(config, debug, no_prompt=no_prompt)
  File "/Users/pprescod/code/CumulusCI/cumulusci/cli/cci.py", line 1327, in flow_run
    coordinator = config.get_flow(flow_name, options=options)
  File "/Users/pprescod/code/CumulusCI/cumulusci/core/runtime.py", line 96, in get_flow
    flow_config = self.project_config.get_flow(name)
  File "/Users/pprescod/code/CumulusCI/cumulusci/core/config/BaseProjectConfig.py", line 753, in get_flow
    other_config = self.get_namespace(ns)
  File "/Users/pprescod/code/CumulusCI/cumulusci/core/config/BaseProjectConfig.py", line 769, in get_namespace
    project_config = self.include_source(spec)
  File "/Users/pprescod/code/CumulusCI/cumulusci/core/config/BaseProjectConfig.py", line 775, in include_source
    source = GitHubSource(self, spec)
  File "/Users/pprescod/code/CumulusCI/cumulusci/core/config/BaseProjectConfig.py", line 804, in __init__
    self.resolve()
  File "/Users/pprescod/code/CumulusCI/cumulusci/core/config/BaseProjectConfig.py", line 846, in resolve
    release = _find_latest_release(self.repo, include_beta=False)
  File "/Users/pprescod/code/CumulusCI/cumulusci/core/config/BaseProjectConfig.py", line 884, in _find_latest_release
    return repo.latest_release()
  File "/Users/pprescod/code/envs/cumulusci-py3/lib/python3.7/site-packages/github3/repos/repo.py", line 2104, in latest_release
    json = self._json(self._get(url), 200)
  File "/Users/pprescod/code/envs/cumulusci-py3/lib/python3.7/site-packages/github3/models.py", line 156, in _json
    raise exceptions.error_for(response)
github3.exceptions.NotFoundError: 404 Not Found

After I added a branch, it seemed to work well for my use-case!

@prescod Thanks for trying it. I added a fix for that case.


Update values.yaml

changed halyard image

We have done these changes in another PR https://github.com/OpsMx/enterprise-spinnaker/pull/589


[5.2] Fix missing makeHidden method in Model.php

The documentation references this method but it doesn't seem to exist (https://laravel.com/docs/5.2/eloquent-serialization#hiding-attributes-from-json)
Tested and implemented this in my current project.
I hope this is useful and i am not missing something.
If i am please let me know :)

Needs tests.


[SMALLFIX]Replace anonymous type with lambda

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/19204/
Test PASSed.

Merged build finished. Test PASSed.


Added PropertyListEncoder/Decoder from Darwin SDK Overlay

Can this process binary plist?! It's still crashing on me when I extract an .ipa on Linux :(

@rafiki270 A cursory look at the code indicates that it should support binary plists, if you could file a bug on https://bugs.swift.org with a reproducible example that would be very helpful and avoid the issue being forgotten about, thanks.


Expand kubelet's clientset to support multiple tenant partitions

Initial code change to expand kubelet to support multiple Tenant partitions and separation of Resource and Tenant partition clientsets.
make and run:
run it with new args:
/kubelet --kubeconfig=/testconfig/kubeconfig1 --tenant-servers="http://<IP_ADDRESS>:8080,http://<IP_ADDRESS>:8080" > kubelet.log 2>&1 &
OR to set up the resource cluster with:
export KUBELET_FLAGS="--tenant-servers=http://<IP_ADDRESS>:8080,http://<IP_ADDRESS>:8080" && export SCALE_OUT_PROXY_ENDPOINT="http://<IP_ADDRESS>:8888" && LOG_LEVEL=3 KUBE_CONTROLLERS=nodelifecycle IS_RESOURCE_PARTITION=true ./hack/arktos-up-scale-out-poc.sh
Noted that it uses a new cmdline args for now. add new entries to kubecofig will involved in the client-go config update which currently i incline to not change.

/assign @chenqianfzh

I took this and run with just one apiserver setup like this:

And pod is schedule but not running:
root@goose-t:~/code/src/k8s.io/arktos# kubectl get pods -o wide
NAME                     HASHKEY               READY   STATUS    RESTARTS   AGE   IP       NODE      NOMINATED NODE   READINESS GATES
nginx-7fc6c5979b-dczfq<PHONE_NUMBER>362607514   0/1     Pending   0          68s   <none>   goose-r   <none>           <none>

In kublet log I'm seeing
E1113 01:14:13.006435   19696 reflector.go:407] k8s.io/kubernetes/pkg/kubelet/kubelet.go:454: Failed to watch *v1.Node: Get http://<IP_ADDRESS>:8888/api/v1/nodes?fieldSelector=metadata.name%3Dgoose-r&resourceVersion=841602838005547008&timeout=10s&timeoutSeconds=557&watch=true: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

I think we want to fix this before merging.

@yb01 can you also make the script change in this? say taking the tenant partition ip addresses from an environment. otherwise it may cause regression.

please make the arktos-up script change too
just pushed a change to the arktos-up-scale-out.sh to set the defualt for the --tenant-services parameters, to not break the existing cluster set up.

/approve

/lgtm


[IA-4137]  Add types to desired and existing runtime config

Are you able to add some tests of the new logic that builds the existing runtime config/the desired runtime config from the existing runtime config?

it took a lot of lines to test it.. def was a good idea

Left a couple questions + small thing I found when testing, the running compute cost is showing unknown specifically for the Standard VM compute type

Fixed the cost, thanks! The gpu type was garbled.

Are you able to add some tests of the new logic that builds the existing runtime config/the desired runtime config from the existing runtime config?

it took a lot of lines to test it.. def was a good idea

thank you, the tests look great!


Testing the feedback mechanism

I'm just testing whether md.reviewer gets this feedback. Ignore me :)

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

ID: aca0ec03-776b-fb48-3c1d-82dc11916534
Version Independent ID: 030f5f5d-992a-1ead-ec17-39faba84cef1
Content: DCsv2-series - Azure Virtual Machines
Content Source: articles/virtual-machines/dcv2-series.md
Service: virtual-machines
Sub-service: sizes
GitHub Login: @linuxelf001
Microsoft Alias: raginjup

@cynthn Closing this as test.


Update BLE HAL doxygen

Update BLE HAL doxygen
Description
Update BLE HAL doxygen
Remove unnecessary extern in front of function prototype
Checklist:

[ ] I have tested my changes. No regression in existing tests.
[x] My code is Linted.

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

/bot run checks

/bot run checks

/bot run checks

/bot run checks


Style component should take an object, not an array

Right now, the Style component takes an array of rules, which is technically correct but doesn't line up with the way we handle any of our other styles objects, which are all objects.
Should update Style so that it doesn't require such a verbose syntax.

+1 for that, I'm currently getting around this by using assign/merge, otherwise dynamic styles are not getting rendered server-side. (when using the array syntax)

@mrtnbroder is this a separate bug you are reporting?


added linux, open source, devrel and devops files

Ahoy matey!
Thank ye for considering to contribute to our book project. Before ye submit your pull request, please make sure to check the following:

[x] Your changes follow the book's style and conventions
[ ] Your changes have been thoroughly reviewed and do not introduce any errors
[ ] You have added appropriate documentation for your changes (if necessary)

Description of changes:
I added the Linux, open source, DevRel and devops files
Issue(s) closed:
[List the issue(s) that this pull request resolves, if applicable]
Thanks for your contribution! We'll review your changes as soon as we can.
Yarrrr!

I have created the Content directory in which all the field files will be present and index.md file will contain the links of them. If you find the DevOps, DevRel, Open Source, and Linux, you will find those links.


Improved Money.repr

Closes #66.
I xfailed the normalization of decimal places, since this feature is not implemented (localization.py:L69)

uh, bump

The test fails in a fairly obvious way:
    def test_repr(self):
>       assert repr(self.one_million_bucks) == '1000000.00 USD'
E       assert '<Money: 1000000 USD>' == '1000000.00 USD'
E         - <Money: 1000000 USD>
E         + 1000000.00 USD

Also, it would be better not to add the additional failing test, it's not clear at this point whether that should be implemented.

Fixed. Sorry to cause trouble with the tests :sob:


Bug 1859594: fix(resolver): Exclude all installed packages in dependency search

Description of the change:
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

/lgtm
/approve

/bugzilla refresh

/lgtm

/retest

/retest

/retest


Suggest changing logging  to  tag

The output tag is more semantic for what we're trying to achieve here and it will allow me to write more general and reusable css.

LOL @scriswell
Thank you for contributing this pull request! We're truly excited and honored to have you as a member of our community. We look forward to working together with you to further build the Aurelia platform.
We noticed that you haven't yet signed our CLA. We would appreciate it if you would consider doing that for us. Before signing, please take a few minutes to read our contributing guidelines. These guidelines will help get you up to speed on how our community likes to operate and how the pull request process works. Once you have read that, assuming you are in agreement, simply sign our online CLA.
After you've signed, please ping this issue to let us know and we'll get your improvements merged in.
Thank you again!
The Aurelia Team

Give me a few more minutes and I'll have this released and then update the hub data.

Great
Sent with Unibox


[AutoPR imagebuilder/resource-manager] [Hub Generated] Review request for Microsoft.VirtualMachineImages to add version preview/2019-05-01-preview

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5723

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/4935


Feature: Add Stable Diffusion with ComfyUI to ujust

We currently have things like Ollama and InvokeAI available in ujust. It would be really awesome to include a ujust command for creating a quadlet to run Stable Diffusion and ComfyUI.

@castrojo found this: https://github.com/AbdBarho/stable-diffusion-webui-docker?tab=readme-ov-file
We likely could just create a quadlet from this and go from there.

@noelmiller Here is my repo here. I think it would be more suitable for Podman environment like we have in bluefin.

Oh yeah, that's looking really dope!

What does work great as well, is installing SwarmUI, which uses ComfyUI as a backend locally onto the machine as ROCm is installed anyway. This saves around 60GB of ROCm Containers. Only caveat: One needs to do a brew install dotnet to make swarmui function on Bluefin.


Instructions on how to update in the README

@asaadmahmood can you add instructions on how to update in the README so people, myself included, can update text ahead of announce?

Done @it33


Warning showing up in production

I am getting this warning in my browser console even for the minified version of the angular-translate lib dist/angular-translate.min.js
pascalprecht.translate.$translateSanitization: No sanitization strategy has been configured. This can have serious security implications. See http://angular-translate.github.io/docs/#/guide/19_security for details.

IMHO error/warnings should be suppressed in production environments.

Well, the security concern is so important, we should enforce it actually. But on the other side we do not want to break things (think semver), so this is the only way let the people (developers) to care of and deal with it.
At the moment we have no "production mode"; we only have a minified version which is.. well.. minified source.
I understand your intent opening this issue, but the security aspect is definitely no optional bullet point while configuring angular-translate.

I am 100% with you on this. I understand security is super important. But in our use case all the translated strings are static and live in the codebase, and we trust them.
Also I understand your point -

At the moment we have no "production mode"; we only have a minified version which is.. well.. minified source.

Is there anyway this could be added to new/future feature requests?

I am 100% with you on this. I understand security is super important. But in our use case all the translated strings are static and live in the codebase, and we trust them.

Perhaps the message and the document behind the link is not clear enough: it is full okay to trust the messages -- but you have to opt-in the old default mode (null) manually. Sounds a bit weird, but this is the only way to ensure semver with the little noisy message.

Is there anyway this could be added to new/future feature requests?

In general: yes. Personally, I have the feeling people will not read the documentation, will only include the minified version and will not care of it. Again: I fully understand your aspect of noisy warnings. But I do not like to reduce effective security (not everyone knows "RTFM" :))  just because of one warning.

Thanks for your thoughts. I'll opt-in for the old default mode then. 👍


Ability to hide unknown section

unknown files are loose files that have been opened that are not recognised as part of any project.
I have almost 2000 of them.
from
https://github.com/muety/wakapi/discussions/617#discussioncomment-8731914

Note to myself: this would either require to pre-compute two different summaries, one with unknown projects included and one without them (heartbeat's project column being NULL or "") or be always computed on the fly (analogously to when applying filters), which would result in poor performance, though. As simple as it sounds, this is not as straightforward from a technical perspective.

Yeah, I ideally it would be excluded everywhere. It a thorn in my side, out of sight out of mind.

Had another thought about this. If we made this a global per-user setting (which would require to re-compute all summaries once initially), implementing this would actually be quite straightforward. Could be implemented in a way similar to how #156 will be realized. Will look into this soon!

Thanks so much, working a treat! My sanity is restored (somewhat) :)


puppet lookup error when key's value has leading colon

Describe the Bug
puppet lookup gives error when key's value is ::ff:<IP_ADDRESS>
Expected Behavior
no error expected
Steps to Reproduce
Steps to reproduce the behavior:

create file /tmp/puppet/hieradata/system.yaml

platform::dns::resolv::servers:
 - fd01::1
 - ::ff:<IP_ADDRESS>

create file /etc/puppet/hiera.yaml

---
version: 5
hierarchy:
  - name: "yaml"
    datadir: /tmp/puppet/hieradata
    data_hash: yaml_data
    paths:
      - system.yaml

/opt/puppetlabs/bin/puppet lookup --hiera_config /etc/puppet/hiera.yaml platform::dns::resolv::servers

Environment

puppet --version [8.4.0]
Platform [Debian 5.10]

wget https://apt.puppet.com/puppet8-release-bulleye.deb
dpkg -i puppet8-release-bulleye.deb
apt-get update
apt-get install puppet-agent
/opt/puppetlabs/bin/puppet --version
8.4.0
Additional Context
Error: Could not run: Lookup of key 'platform::dns::resolv::servers' failed: Value for key 'platform::dns::resolv::servers', in hash returned from data_hash function 'yaml_data', when using location '/tmp/puppet/hieradata/system.yaml', has wrong type, expects Puppet::LookupValue, got Array[Any, 2, 2]

This is not a puppet problem. That IPv6 address needs to be quoted for YAML to interpret it as a regular string.
platform::dns::resolv::servers:
 - fd01::1
 - '::ff:<IP_ADDRESS>'

For posterity, search for "yaml sexagesimal" which can be seen:
$ ruby -ryaml -e "puts YAML.load('11:00')"
39600

Going to close this.

Does this mean this is ruby issue ?
Python parses this correctly:
python3.9 -c 'import yaml; a=yaml.safe_load("servers: ::ffff:<IP_ADDRESS>"); print(a); print(a["servers"]);'
{'servers': '::ffff:<IP_ADDRESS>'}
::ffff:<IP_ADDRESS>

Ruby parses correctly for ffff::1 but has problem with leading colon (::ffff:<IP_ADDRESS>).
ruby --version
ruby 2.7.0p0
ruby -ryaml -e "puts YAML.load('servers: ffff::1')"
{"servers"=>"ffff::1"}

ruby -ryaml -e "a = YAML.load('servers: ::ffff:<IP_ADDRESS>'); puts a; puts a['servers']"
{"servers"=>:":ffff:<IP_ADDRESS>"}
:ffff:<IP_ADDRESS>

In ruby it depends on the version of the yaml library that ruby uses and (I believe) whether the library conforms to YAML 1.1 or 1.2  https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell#sexagesimal-numbers

gem list yaml
yaml (0.3.0)

ruby -ryaml -e "puts YAML.load('59:59')"
215940

Even with latest yaml library and the above result  for sexagesimal, means it is YAML 1.1. Looks like this library does not comply with leading :: value. I do not see YAML 1.2 compliance yaml library for ruby to test.
Thank you for all your inputs.


Bumping webhook image to v0.4.3

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Bumps webhook version to v0.4.3 in preparation for release.
Does this PR introduce a user-facing change?:
NONE

/lgtm


Publish wasi-nn Rust bindings here?

I would like to publish Rust bindings for wasi-nn that were generated with the witx-bindgen tool in this repo (the Rust bindings currently live in a Wasmtime example). It would be helpful to me to have the bindings in one place--i.e., most likely this repository--so that changes to WITX, the tools, etc., can be tested against bindings from several modules. This would simplify creating and maintaining WASI proposals and there are other WASI proposals (e.g. wasi-crypto, wasi-sockets, etc.) that might benefit from this same idea.
The first question is "should this be done?" and I am interested in opinions here. Then, "how?": I think this repository (and accompanying CI tasks) could be slightly refactored to generate and publish multiple crates, one per proposal. Thoughts?

cc: @pchickey, @sunfishcode, @alexcrichton, @jedisct1

The AssemblyScript/Zig bindings and documentation for wasi-crypto and other APIs were all generated with as-witx. The Rust bindings were generated with witx-generate-raw.
But none of these code generators support the recent changes made to the witx format yet.
I don't know what tools other proposals have used to generate their bindings. Some of them (ex: experimental-http) are manually written.
Before centralizing these bindings, maybe we really need code generators (not only for Rust) that we could all use.

I'm not personally sure where best the bindings for all the proposals to wasi would live, but here seems as best a place as any while we figure that out?

Agreed with Alex that the long term isnt clear, but for now we should start by getting the Rust code generator in this crate working for all proposals. I don't have an opinion on where code generators for other languages should live.

maybe we really need code generators (not only for Rust) that we could all use

@jedisct1, is https://github.com/jedisct1/witx-codegen an attempt to fix this problem? I haven't tried it out yet, but I like the idea of being able to generate bindings for a bunch of different languages! How do you see that tool relating to the current Rust code generator in this repo--should it replace it? Live alongside?

@abrown Yes. witx-codegen was made to solve this problem, which also affected other non-rust projects as changes to witx were made. It merges existing code and doc generators into a single tool, which is way easier to maintain than all these different forks of as-witx.
witx-codegen is currently being updated to use the BindGen trait in order to support the next ABI, and for the Rust backend, the code from this repository can easily be ported to it instead of exposing a different interface.


Make setting constitution more flexible

Motivation
In order to test #240, we would like to test adding members both when they are immediately accepted and when voting is required and current methods of setting the constitution don't allow different resolve functions.
This change makes it easy to set a constitution made up of different pieces, for example we can set a resolve function for testing which just auto accepts every proposal, but for specific use cases we can easily use a majority vote, the structure also makes it trivial to add new options for example we might want a majority vote of certain members, or allow any member to veto proposals.
Changes

[x] Structure the governance/constitution directory to have separate scripts for the bits of the CCF constitution, with options where appropriate (e.g. type of resolve function)
[x] Re-write constitution_set.sh to allow the user to specify where to get the parts of the constitution
[x] Update usage of this script to maintain existing behaviour (i.e. auto accept proposals and use kms specific actions)
[x] Rename endpoint tests to just system test (singular) because we now test more than just endpoints
[x] Add a test_constitution.py test which tests the different resolve options we have

I suggest to avoid copying the default constitution files and  just have the delta;s to avoid having to maintain these files.

https://github.com/microsoft/azure-privacy-sandbox-kms/pull/242#issuecomment-2536153691
I suggest to avoid copying the default constitution files and just have the delta;s to avoid having to maintain these files.

Can you explain how to specify a delta of a resolve function which isn't just a patch against the default one? A patch has the same maintenance overhead as the actual code but with the code it refers to being invisible.


Day View Resolution

How do I get the calendar day view resolution to 15 minutes instead of 30? Any  ideas on where to start.
I usually schedule in 15 minute blocks.

Did make this work as i have same issue here. Can share some code if you happened solve the problem

Comment below line and 15 min blocks will be added.
eventHeight = MAX(roundf(VERTICAL_DIFF/2), eventHeight);


My bot didn't run after all settings

Hello!
Thank you for your great app, but due to really poor documentation I can't understand why my bot didn't run.
This is my settings:
DISCORD_BOT_PLUGINS = ''
DISCORD_BOT_RECONNECT = ''
DISCORD_PY_BOT_TOKEN = 'MyToken'

INSTALLED_APPS = [
    'daphne',
    'channels',
........
    'django_discord.py.bot',
]

ASGI_APPLICATION = 'core.asgi.application'

CHANNEL_LAYERS = {
    "default": {
        "BACKEND": "channels_redis.core.RedisChannelLayer",
        "CONFIG": {
            "hosts": [("<IP_ADDRESS>", 6379)],
        },
    },
}

This is my ASGI config, full:
import os
import importlib

from channels.routing import ChannelNameRouter, ProtocolTypeRouter
from django.core.asgi import get_asgi_application
os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'core.settings')

django_asgi_app = get_asgi_application()

consumers_module = importlib.import_module('django_discord.py.bot.consumers')

application = ProtocolTypeRouter(
    {
        "http": django_asgi_app,
        "channel": ChannelNameRouter(
            {
                "discord_bot": consumers_module.BaseDiscordConsumer.as_asgi(),
            }
        ),
    }
)

And this is my bot.py:
import discord
from discord.ext import commands

intents = discord.Intents.all()
intents.message_content = True
intents.members = True
bot = commands.Bot(command_prefix='>', intents=intents)

@bot.event
async def on_member_join(member):
    print("id", member.guild.id)
    print("id_type", type(member.guild.id))
    embed = discord.Embed(title="Welcome to my server!", description=None, color = discord.Color.magenta())
    embed.add_field(name="To get started:", value="•Invite some friends!\n•Check out some of the channels and get engaged with the community!\n•Have fun!", inline=True)
    channel = discord.utils.get(member.guild.channels, name="welcome")
    channel_id = channel.id
    channel = bot.get_channel(channel_id)
    await channel.send(embed=embed)

@bot.command()
async def hi(ctx):
    await ctx.send('Hello!!')

@bot.command()
async def test_join(member: discord.Member):
    await on_member_join(member)

After I run python manage.py runserver I have this
2024-02-14 15:30:34.839 | INFO     | django_discord.py.bot.apps:ready:14 - Sending start signal
2024-02-14 15:30:34.841 | INFO     | django_discord.py.bot.apps:ready:37 - Start signal sent
2024-02-14 15:30:35.081 | INFO     | django_discord.py.bot.apps:ready:14 - Sending start signal
2024-02-14 15:30:35.082 | INFO     | django_discord.py.bot.apps:ready:37 - Start signal sent
Watching for file changes with StatReloader
Performing system checks...

System check identified no issues (0 silenced).
February 14, 2024 - 15:30:35
Django version 5.0.2, using settings 'core.settings'
Starting ASGI/Daphne version 4.1.0 development server at http://<IP_ADDRESS>:8000/
Quit the server with CONTROL-C.

It seems like consumer didn't run properly or didn't run at all.

Thank you for your fast reply!
I'll check it later, but at this point close this issue.
All the best, cheers!