relabel:'connective tissue disorder due to lysyl hydroxylase-3 deficiency'

Mondo term (ID and Label):
'connective tissue disorder due to lysyl hydroxylase-3 deficiency'
Suggested new label:
use OMIM:
https://omim.org/entry/612394
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here
Optional: Any additional information (like supporting evidence, PubMed ID, etc.)

part of #3155

I would like to double check if ClinGen is using this term before we relabel it, because they are interested in relabeling. I assigned this to the Nov release, hopefully we'll get a list of terms that ClinGen is using soon.


Fixes for minor spelling and grammar issues

I just encountered these while reading through, and figured a PR was the best thing to do :)

Thanks a lot!
I had to merge and wasn't sure if I could push to your branch. So I created https://github.com/luebken/container-patterns/pull/5


Script halts

Bot is fine on selecting a deck but after it select the deck and game starts it just stops here, it was working fine before though.
PS C:\LoR-Bot> python .\LOR_Bot.py
PvP Mode
SELECTING DECK NOW!
SELECTING DECK NOW!
Unknown mana...
Unknown mana...
Unknown mana...
Exception in thread Thread-1 (run):
Traceback (most recent call last):
  File "C:\Python311\Lib\threading.py", line 1038, in _bootstrap_inner
    self.run()
  File "C:\Python311\Lib\threading.py", line 975, in run
    self._target(*self._args, **self._kwargs)
  File "C:\LoR-Bot\Bot.py", line 52, in run
    self.game_state, self.cards_on_board, self.deck_type, self.n_games, self.games_won = self.state_machine.get_game_info()
                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\LoR-Bot\StateMachine.py", line 78, in get_game_info
    self.game_state = self._get_game_state(self.frames, image)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\LoR-Bot\StateMachine.py", line 151, in _get_game_state
    self._get_deck_type()
  File "C:\LoR-Bot\StateMachine.py", line 204, in _get_deck_type
    self.deck = tuple(self.all_cards[cardCode] for cardCode, num_cards in self.cards_data["CardsInDeck"].items()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\LoR-Bot\StateMachine.py", line 204, in <genexpr>
    self.deck = tuple(self.all_cards[cardCode] for cardCode, num_cards in self.cards_data["CardsInDeck"].items()
                      ~~~~~~~~~~~~~~^^^^^^^^^^
KeyError: '06PZ007'

I see, you are getting a KeyError: '06PZ007', which should be fixed. KeyError means there is a card with a key that bot could not recognize ('06PZ007' in this case). This is strange, because I moved all KeyErrors to warnings.
I suggest you to delete the card_sets folder and run the program again, it will download all the card sets again, like it says in the notes section.
If that still does not work, I'm guessing Riot decided to make a bigger change as to how they handle keys and I will have to look at it thoroughly.

No luck, same issue after it downloaded the cards.

SELECTING DECK NOW!
SELECTING DECK NOW!
Unknown mana...
Exception in thread Thread-1 (run):
Traceback (most recent call last):
  File "C:\Python311\Lib\threading.py", line 1038, in _bootstrap_inner
    self.run()
  File "C:\Python311\Lib\threading.py", line 975, in run
    self._target(*self._args, **self._kwargs)
  File "C:\LoR-Bot\Bot.py", line 52, in run
    self.game_state, self.cards_on_board, self.deck_type, self.n_games, self.games_won = self.state_machine.get_game_info()
                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\LoR-Bot\StateMachine.py", line 78, in get_game_info
    self.game_state = self._get_game_state(self.frames, image)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\LoR-Bot\StateMachine.py", line 151, in _get_game_state
    self._get_deck_type()
  File "C:\LoR-Bot\StateMachine.py", line 204, in _get_deck_type
    self.deck = tuple(self.all_cards[cardCode] for cardCode, num_cards in self.cards_data["CardsInDeck"].items()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\LoR-Bot\StateMachine.py", line 204, in <genexpr>
    self.deck = tuple(self.all_cards[cardCode] for cardCode, num_cards in self.cards_data["CardsInDeck"].items()
                      ~~~~~~~~~~~~~~^^^^^^^^^^
KeyError: '06PZ007'

Ok. After checking the Developer portal I saw there is another card set called https://dd.b.pvp.net/latest/set6cde-en_us.zip which the bot does not download.
I suggest downloading it either manually or through code and see if it works.

That fixes the issue, looks like it was just missing the set.

Fixed here
https://github.com/MOj0/LoR-Bot/commit/eacd3f07a69e511f02c4b1e5e4442293e91597d1


bump webassembly and few fixes

What kind of change does this PR introduce?

Did you add tests for your changes?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

Addresses comments in https://github.com/webpack/webpack/pull/7275

Thanks


Add default area on space creation.

what is the name of this space ? empty string or ?

The name of the root area is the same as that of the space, @maxandersen .

okey, I hope our ui and queries will equate me typing "/" to mean the root space rather than having to type it out every time ;)

Another concern i have here is once we have queries expressed by strings/expressions - if I have to state the area root name I can't easily share queries between projects.


i18n(fr): add guides/deploy/clever-cloud.mdx

Description (required)

Translate guides/deploy/clever-cloud.mdx in French (see #9030)

[!NOTE]
I translated the UI strings because Clever Cloud seems to be available in French, but I didn't check if the translation is the same as the UI because we need an account...

Related issues & labels (optional)

Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
guides/deploy/clever-cloud.mdx
Localization added, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Created Italian translation for the Contribution Guidelines.

Created Italian translation for the Contribution Guidelines.

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

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

@lindakovacs It's great to see you here after our many discussions on Twitter. Thanks for taking the time to translate this! Congrats on your first merged PR!

Thank you @QuincyLarson.


error cant create file already exists

Everytime I try to load a local PDF, it answers the first question, but after that it errors out with "cant create file that already exists".

could you please try now. I had added a temporary embeddings file which was causing this error. Now I am able to run it correctly:

Did you fix the source code also so I could try it locally?

yes, please get the latest code

Please use this file https://huggingface.co/spaces/bhaskartripathi/pdfChatter/blob/main/app.py

Thank you. I just tried and still have the same error.

The error you are getting is because the earlier code was checking if the embedding is created and save temporarily,  it is not reloaded.  This can save the computational effort of creating embedding on every call. However,  as that code had some issue, I had removed that from the latest version.  It looks like you are still using the previous code. Could you plz do a viewdiff ?

I just copied the text from the link you sent and ran it. It has the changes indicated by hugginface on lines 52 and 188.
Line 52: chunk = f'[Page no. {idx+start_page}]' + ' ' + '"' + chunk + '"'
Is this the correct version?

Yes that is correct

the error still happens after a while

I have tried it again and again but Not able to replicate it anymore.


Add tests

This project was completed in Pair-Programming working Online with @normainobary2021 ✅
We've implemented the followings

Add Unit Tests for Calculator Logics operator.js and calculator.js
Add Snapshot Testing for Home.js
Add Snapshot Testing for Quote.js
Add Snapshot Testing for Calculator.js
Add Snapshot Testing for App.js
Add Snapshot Testing for Footer.js
Add Snapshot Testing for NavBar.js
Add Mock data For Dynamic Quote Generator
Add React Router Render
Update ReadMe With Testing Instructions

Thank you @zieeco


PTX-1175 fix elasticsearch to proper deploy and check readiness

@thiguetta post-merge, please monitor es on few initial jobs manually.

this PR had fixed #122


README.md Requirements lack versions

@tillberg one thing I forgot to mention when starting the Grunt.js changes was that I noticed the versions are not listed in the README.md "Requirements" section for:

JQuery
Zepto
Underscore.js

As of 052bd43ed8fe4b3170cc5d4b05ecb3823ff8d8ea, JQuery/Zepto are only used for the ajax model's ajax function. I may look into creating a basic version of that function which doesn't depend on JQuery/Zepto at all by using the XHR API directly.
As for version requirements for Underscore/Lodash, I've not yet tested for what minimum versions would satisfy the various things that TBone needs. But that would be a good thing to do at some point.


[Bug]: Playground authentification from Bitkit widget doesn't work

Describe the bug
From 3 devices we can auth from the Playground website but when we try to login from the SlashAuth Demo Widget, there is a 404 error message.
Reproduce

Go to 'SlashAuth demo widget'
Click on 'login'
See error

Screenshots / Recording

Operating system
Graphene OS and iOS
Bitkit version
v47
Log output
No response

Hey @JeanlChristophe !
This issue has already been fixed in this PR:
https://github.com/synonymdev/slashtags-playground-auth-demo/pull/3
I've already asked @rbndg to update the slashtags-playground-auth-demo repository to match the lasted commit.
When the server is updated, you can try again and verify that the authentication redirects to the correct link.
Note: will assign this issue to @rbndg

Thanks Miguel


Threshold for obtaining nudity.csv

Hello, Author!
Sorry for reaching out again. I wanted to inquire about the threshold you mentioned here for obtaining the "nudity.csv". Thank you so much for your assistance!

Hi. The threshold for NudeNet score is 0.75


KeyError: 'TXT'

Hi,
I get the following error when I use news_extract to read the file below
3634_08_b1.txt

KeyError                                  Traceback (most recent call last)
Cell In[28], line 21
19     print(n+1)
20     fc_file = filenames_fc[n]  #file exported from Factiva
---> 21     fc_data += ne.factiva_extract(fc_file)
23 data=ne.fix_fac_fieldnames(fc_data)
24 dataframe=ne.news_export(data,to_pandas=True, master_fields = [], jacc_threshold=1.1)
File ~\anaconda3\lib\site-packages\news_extract\news_extract.py:176, in factiva_extract(article_fn)
173 article_dict3 = dict(zip(field_names3,fields3))
175 if 'LP' in article_dict2:
--> 176     article_dict3['TXT'] += article_dict2['LP']
177     del article_dict2['LP']
178 if 'TD' in article_dict2:
KeyError: 'TXT'
This is the full code that I use for extracting news from a set of files in a folder:
import news_extract as ne
import os, glob
import pandas
directory = '.../FactivaDownloads/'
filenames_fc = []
for filename in glob.glob(os.path.join(directory, "*.txt")):
print(filename)
with open(os.path.join(os.getcwd(), filename), 'r') as f:
filenames_fc += [filename]
fc_data = []
for n in range(0, len(filenames_fc)):
#for n in range(0,2):
print(n+1)
fc_file = filenames_fc[n]  #file exported from Factiva
fc_data += ne.factiva_extract(fc_file)
data=ne.fix_fac_fieldnames(fc_data)
dataframe=ne.news_export(data,to_pandas=True, master_fields = [], jacc_threshold=1.1)
dataframe.to_excel(directory + "News.xlsx")
I would appreciate your assistance for solving the issue.
Thank you,
Best,
Birgul

Did you figure out a solution? I am getting the same error, it seems that something in the way factiva encodes the output has changed - but it only happens with some files, not others.


mmctl: init at 6.2.1

Motivation for this change
mmctl is a usefool tool for Mattermost server admins.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@globin @lheckemann @ryantm @fpletz @jokogr,
As I saw you maintain mattermost-related packages, it may interest you :)

ryantm I requested a new review because the force-push don't integrate well with GitHub review's requests. I don't know if it's the way to do, or if it's over-soliciting you, sorry!


precedence parser assumes existence of binary operators

This is the failure I mentioned earlier. The current PR is a hack to make parsing succeed, while we investigate next.
Below is the precedence alternative. It currently fails with A TerminalTrie with no entries should never have been constructed. It assumes the existence of a binary operator, and fails as such. Might also be a part of our discussion on enforcing the explicit structure of each operator type (ternary/binary/unary) via YAML (an EBNF variant) instead detecting it later.
- name: "YulExpression"
  kind: "Rule"
  unversioned:
    parserType: "Precedence"
    choice:
      - reference: "YulFunctionCall"
      - reference: "YulPrimaryExpression"

- name: "YulFunctionCall"
  kind: "Rule"
  unversioned:
    sequence:
      - reference: "YulExpression"
      - delimitedBy:
          open: "("
          expression:
            optional:
              separatedBy:
                separator: ","
                expression:
                  reference: "YulExpression"
          close: ")"

- name: "YulPrimaryExpression"
  kind: "Rule"
  unversioned:
    choice:
      - reference: "YulIdentifierPath"
      - reference: "YulLiteral"

Originally posted by @OmarTawfik in https://github.com/NomicFoundation/slang/pull/307#discussion_r1086546507

I'm digging some more into the current parser codegen to see what other issues we have in the current schema.

@AntonyBlakey proposed the following form:
- name: "Expression"
  kind: "PrecedenceExpressionRule"
  versioned:
    0.4.11:
      # as below, but exponentiation is left associative
    0.6.0:
      operators:
        - binaryLeftOperator:
          name: "AssignmentExpression"
          choice:
            - terminal: "="
            - terminal: "|="
            - terminal: "^="
            - terminal: "&="
            - terminal: "<<="
            - terminal: ">>="
            - terminal: ">>>="
            - terminal: "+="
            - terminal: "-="
            - terminal: "*="
            - terminal: "/="
            - terminal: "%="
        - suffixOperator:
          name: "ConditionalExpression"
          sequence: # This subsequence forms the correct CST for the suffix expression parser
            - terminal: "?"
            - reference: "Expression"
            - terminal: ":"
            - reference: "Expression"
        - binaryLeftOperator:
          name: "OrExpression"
          terminal: "||"
        - binaryLeftOperator:
            name: "AndExpression"
            terminal: "&&"
        - binaryLeftOperator:
            name: "EqualityComparisonExpression"
            choice:
              - terminal: "=="
              - terminal: "!="
        - binaryLeftOperator:
            name: "OrderComparisonExpression"
            choice:
              - terminal: "<"
              - terminal: ">"
              - terminal: "<="
              - terminal: ">="
        - binaryLeftOperator:
            name: "BitOrExpression"
            terminal: "|"
        - binaryLeftOperator:
            name: "BitXOrExpression"
            terminal: "^"
        - binaryLeftOperator:
            name: "BitAndExpression"
            terminal: "&"
        - binaryLeftOperator:
            name: "ShiftExpression"
            choice:
              - terminal: "<<"
              - terminal: ">>"
              - terminal: ">>>"
        - binaryLeftOperator:
            name: "AddSubExpression"
            choice:
              - terminal: "+"
              - terminal: "-"
        - binaryLeftOperator:
            name: "MulDivModExpression"
            choice:
              - terminal: "*"
              - terminal: "/"
              - terminal: "%"
        - binaryRightOperator:
            name: "ExponentiationExpression"
            terminal: "**"
        - suffixOperator:
            name: "UnarySuffixExpression"
            choice:
              - terminal: "++"
              - terminal: "--"
        - prefixOperator:
            name: "UnaryPrefixExpression"
            choice:
              - terminal: "++"
              - terminal: "--"
              - terminal: "!"
              - terminal: "~"
              - terminal: "-"
        - suffixOperator:
            name: "FunctionCallExpression"
            sequence:
              - optional:
                  reference: "NamedArgumentList"
              - reference: "ArgumentList"
        - suffixOperator:
            name: "MemberAccessExpression"
            sequence:
              - terminal: "."
              - choice:
                  - reference: "Identifier"
                  - terminal: "address"
        - suffixOperator:
            name: "IndexAccessExpression"
            delimitedBy:
              open: "["
              expression:
                sequence:
                  - optional:
                      reference: "Expression"
                  - optional:
                      sequence:
                        - terminal: ":"
                        - optional:
                            reference: "Expression"
              close: "]"
      primaryExpressions:
        - reference: "TypeExpression"
        - reference: "NewExpression"
        - reference: "ParenthesisExpression"
        - reference: "ElementaryType"
        - reference: "ArrayLiteral"
        - reference: "AsciiStringLiteral"
        - reference: "UnicodeStringLiteral"
        - reference: "HexStringLiteral"
        - reference: "NumericLiteral"
        - reference: "BooleanLiteral"
        - reference: "Identifier"


Python 3.7

Codecov Report

Merging #2841 into master will decrease coverage by 2.91%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2841      +/-   ##
==========================================
- Coverage   56.67%   53.75%   -2.92%
==========================================
  Files        7628     5247    -2381
  Lines      158120   134763   -23357
==========================================
- Hits        89611    72441   -17170
+ Misses      68509    62322    -6187

Impacted Files
Coverage Δ

...ure/mgmt/recoveryservicesbackup/models/__init__.py
51.91% <0%> (-48.09%)
:arrow_down:

...ure-mgmt-media/azure/mgmt/media/models/__init__.py
53.3% <0%> (-46.7%)
:arrow_down:

.../azure/mgmt/compute/v2017_12_01/models/__init__.py
53.38% <0%> (-46.62%)
:arrow_down:

...iveservices/search/entitysearch/models/__init__.py
53.75% <0%> (-46.25%)
:arrow_down:

...ration/azure/mgmt/datamigration/models/__init__.py
53.89% <0%> (-46.11%)
:arrow_down:

...mgmt-monitor/azure/mgmt/monitor/models/__init__.py
54.1% <0%> (-45.9%)
:arrow_down:

azure-eventgrid/azure/eventgrid/models/__init__.py
54.54% <0%> (-45.46%)
:arrow_down:

...ure-mgmt-logic/azure/mgmt/logic/models/__init__.py
54.68% <0%> (-45.32%)
:arrow_down:

...ce/azure/mgmt/containerinstance/models/__init__.py
54.79% <0%> (-45.21%)
:arrow_down:

...mgmt-batchai/azure/mgmt/batchai/models/__init__.py
54.9% <0%> (-45.1%)
:arrow_down:

... and 2432 more

Continue to review full report at Codecov.

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


Builtin Victoria 3 CWT files are Victoria 2 files

Hi,
I am using the latest release from github (1.3.18):

For testing purposes I tried downloading cwtools-vic3-config manually and putting the config files in .config/vic3/ now the plugin properly references everything.
Seems like this script needs to be run before the next release:
https://github.com/DragonKnightOfBreeze/Paradox-Language-Support/blob/master/cwt/scripts/clone_all.sh
Regards,
Chris

Ok it's a mistake in build.gradle.kts


dep ensure -add should add constraint to Gopkg.toml even if imported already

Edit by @carolynvs: After discussion, we would like to see the following behavior:

Import a new project in my code.
Run dep ensure. This adds a project entry in Gopkg.lock but not Gopkg.toml.
Later realize that I want to have a constraint set in my manifest. Instead of looking in the lock to for the locked project and figuring out what to add to the manifest manually I want to...
Run dep ensure -add github.com/pkg/example and dep will infer the appropriate constraint from the existing locked project, and append the constraint to the manifest. If a constraint or required is already in the manifest, an error is still displayed as it does already today.

(assuming you still take UX reports) (carolyn: We do! ❤)
Today I merged a PR in a repository I manage with dep. The PR added a dependency but did not vendor it, so I updated dep and ran dep ensure to add it.
In #1313 I learned that I want constraints for my direct dependencies, but just running that command did not add one, so I tried dep ensure -add github.com/godbus/dbus:
Fetching sources...

Failed to add the dependencies:

  ✗ github.com/godbus/dbus is already imported or required, so -add is only valid with a constraint

adding dependencies failed

So instead I had to go into Gopkg.lock, take note of the version, open Gopkg.toml, copy-paste a constraint, lookup what the behavior of version without operator is (since I forgot), and edit the constraint.
It looks to me like there are two natural flows to add a dependency:

-add first

decide to add a dependency
call dep ensure -add
import and use it

import first

add a dependency
call dep ensure to vendor it

1 results in a constraint, 2 does not. The preferred result between the two, or even what difference it makes, would be completely opaque to me had I not asked on #1313, and getting there via 2 is clunky.

BTW, https://golang.github.io/dep/docs/daily-dep.html is great.
But the idea that import-then-ensure will only be used for "rapid iteration and off-the-cuff experimenting" is unrealistic.

I was going to suggest that at least -add should add the constraint for me, so that we can say "just always run -add, but it looks to me like that's what it's documented to do. (Row 5/6.)

So maybe just turn this into "-add should infer constraint and add to Gopkg.toml even if imported".

So maybe just turn this into "-add should infer constraint and add to Gopkg.toml even if imported" or (tell me to) open an issue for that.

👍 I agree it's confusing and annoying how dep works today in this case. I'll update the title and OP to make it clear that is what we would like to change the behavior to.

Hey @carolynvs, can I work on this? If yes, could you please give me some pointers on how I could get started on the changes required?

@sudo-suhas I don't really have pointers, but if you'd like to work on this, no one else is. :-)

I written a small application just to check this, which forces our build to fail and therefore, the developer to include them manually. In case it's useful for you as it was for us.


[graphql-pod] 3. Add framework to amplify

Add framework in amplify config
Background
Each framework.dev site is deployed from the same codebase using amplify. In this ticket, we are adding this new framework to be added to the amplify config so that it gets deployed correctly
Acceptance

[x] Add the new framework on amplify.yml
[x] Test the created PR to make sure that the deployment works as expected

NOTE:

You may require someone with AWS access to create the project for you.

It has been successfully deployed here
https://graphql.framework.dev/


Request: value binding

Is it possible?
vue checkbox value binding

In toggle options, set sync to true.

Hi @akhchan99, as @tylerjheslop rightly said, just use sync=true. Take a look in demo for examples and to readme for more info.

Can't see reason to do it, why simply not to do: v-bind:value=" v === 'a' "?

Reason being setting the v-model will end up being a boolean again, not 'a' or 'b', and will need a @change event to update the model to the desired value.
Just trying to reduce the extra methods, and use v-model instead of binding the value directly


IP addresses are missing from events

Hi there, we've been trying to get IP addresses stamped on our Segment events, but so far we have not been successful. All events coming from this package do not have an IP address on them, as we can see in the segment.com Debugger.
I noticed that there is a previous issue, that seems to have already resolved this issue: https://github.com/segmentio/analytics_flutter/issues/43#issuecomment-1997825449. But, we still haven't seen any IP addresses.
@oscb Do you have any additional information on IP addresses? Is there any change required on our side, or is there something that needs to be adjusted on Segment? Thank you!

I'm looking into this.  I'll try to get you an update or a fix soon.

A fix should be deployed early next week.

Should be working now, let us know if you have any further issues.

Thank you @MichaelGHSeg!


Add Watchtower option for updating containers selectively

I had some issues in the past when watchtower was enabled and started updating specific containers, which broke functionality. To me allowing the user to specify selected containers for updating (as well as updating everything as it is now) would be a nice addition, and I implemented it on my own ansible-nas fork.
What you basically need to do is:
add a variable in watchtower like watchtower_label_enable (false by default), which would be a boolean and would enable updating only selected containers. Now the watchtower task becomes
- name: Watchtower Docker Container
  docker_container:
    name: watchtower
    ...
    env:
      ...
      WATCHTOWER_LABEL_ENABLE: "{{ watchtower_label_enable | ternary('1', '0') }}" #<- important, as watchtower expects 1 or 0, not true/false
    ...

Now every application needs a new variable, which I called *_watchtower_update_enabled which is also a boolean and set to false by default. Each app receives a new docker label in the form of
com.centurylinklabs.watchtower.enable: "{{ (watchtower_enabled and watchtower_label_enable) | ternary(*_watchtower_update_enabled, omit) | string }}"

The reasoning is the following:

watchtower_enabled: false: no containers are updated as usual
watchtower_enabled: true and watchtower_label_enable: false: all containers are updated, regardless of individual preferences
watchtower_enabled: true and watchtower_label_enable: true: a label is added for watchtower to monitor only if *_watchtower_update_enabled: true, otherwise the label is not added and the container doesn't get updated.

The setup has been tested on my two ansible-nas machines and works as expected.
Side note: you need to add recreate: true to each application task if not there already, as labels don't get updated without a container being recreated

Let me know if it would be interesting and I can make a PR for it

I agree with this approach and would like to see this added one way or another. On my Ansible-nas machine I have added a label per container:
com.centurylinklabs.watchtower.enable: "{{ vaultwarden_watchtower_enable }}"
to decide if I want this particular container getting updated or not. I works fine.


[Doc Improvement][Tools and SDKs-TTK-Deploy Teams app to the cloud]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/deploy.md
97
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 3c94fe4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/deploy.md
97
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 10513cc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-cloud_1.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/deploy.md
100
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 609e1c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-cloud_1.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/deploy.md
100
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 5cf14b5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-cloud_1.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/deploy.md
100
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit cb7fff3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-cloud_1.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/deploy.md
100
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 26601ce:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/deploy-teams-app-cloud-vs/sideload-teams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-cloud_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-preview-teams_1.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/deploy.md
100
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit e8809d0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/deploy-teams-app-cloud-vs/sideload-teams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-cloud_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-preview-teams_1.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/deploy.md
100
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 3111ca8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/deploy-teams-app-cloud-vs/sideload-teams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-cloud_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-preview-teams_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-preview-teams_2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/mstdd-landing.yml
100
0
link
:white_check_mark:

msteams-platform/toolkit/deploy.md
100
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 45574ac:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: CannotMergeCommit] Cannot merge commit 45574aca9514017f53dea29ae369a08e60c994e5 in branch doc-improvement-deploy-teams-app-to-cloud of repository https://github.com/MicrosoftDocs/msteams-docs into branch main (commit 21c9ca864c9d588218d20949725ebba670d7d8d8). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/deploy.md
100
1
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 68d345b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/deploy-teams-app-cloud-vs/sideload-teams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-cloud_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-preview-teams_1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/deploy-teams-app-cloud-vs/vs-deploy-preview-teams_2.png
:white_check_mark:Succeeded
View

msteams-platform/toolkit/deploy.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Bugfix for issue#77

This is the bugfix for issue #77
@jgrossi, I think we should create a CorcelModel which redefines the belongsTo/belongsToMany/hasMany, etc... functions to pass the DB connection along, and all our models can extend that class. What do you think ?

Thanks @rundef!

@rundef let me check some parts of the code and tell you.. but the idea of have a default model is great! these relation problems can be solved by that! give me some hours to make some tests and I contact you again, ok? thanks again for the awesome support :D

@rundef let's create a Corcel\Model class, where we'll set all information about relationships and all Corcel model classes will extend it... so users should create their own Post class extending Corcel\Model and not Corcel\Post.
Maybe this can be a easier solution in relationship instead of set all connections in relationships: http://laravel.io/forum/02-12-2014-many-to-many-relationship-not-working-across-databases

Yes that's a good idea. But if Corcel\Post extends Corcel\Model it's okay if the users extends Corcel\Post :)

Yep :-)


How to use the Kiwi unit testing library within an OSX application?

Hi,
I might be missing something, but I have tried following the Kiwi tutorial online and haven't managed to get further than the end of Step 5. Running a test at the end of Step 5 does not succeed for me, but fails with ld: library not found for -lKiwi
When I start from scratch with an OSX application, the same thing happens. When I start with an iOS application, everything works fine, as presented in the tutorial.
Therefore, I believe there is a different step that needs to be taken in order to include the Kiwi testing framework into a OSX application, not just what is presented in the tutorial.
Any help would be appreciated. Thanks!

I don't know if this is a recommended way, but for OSX I just added that Kiwi folder to my project under Dependencies/External (or some suitable directory). Worked ok that way. (Add -fno-obj-arc to all files, if you're using ARC elsewhere).
Not sure why it didn't link following the docs procedure.

Thanks @jasperblues for the tip on llvm-gcc. I also had to change Kiwi to 64-bit architecture to get it to build on my Mac. I now have it building on the Xcode 4.4 beta. Running a test? That's a different story.

Thanks @jasperblues for the tip on llvm-gcc. I also had to change Kiwi to 64-bit >architecture to get it to build on my Mac. I now have it building on the Xcode 4.4 beta. >Running a test? That's a different story.

You're welcome. Once you have the examples running:

Copy the Kiwi folder to your project, and create a separate static-lib target with that folder as source. Turn off ARC, use llvm-gcc, etc
Now that the target is there, you can add libKiwi.a as library in the build phases section of your target.
Set the header search path to include ${SRCROOT}/path/to/kiwi/source/folder
Run tests.

Thanks for the followup. I had actually made it that far on my own :) When I tried to run the tests yesterday after finally getting Kiwi to compile Xcode crashed. Like I said, I'm running 4.4 beta, so I'm sure it's related to that.

Got it working, had to write a plugin to hack Xcode. I'll post instructions later today and post the link here.

Oh - that's interesting re Kiwi and Xcode 4.4.
Look forward to seeing the details on how you got it to work.
On Feb 27, 2012, at 4:13 AM, Joe Fiorini wrote:

Got it working, had to write a plugin to hack Xcode. I'll post instructions later today and post the link here.

Reply to this email directly or view it on GitHub:
https://github.com/allending/Kiwi/issues/86#issuecomment-4184057

I think they removed a method from the built-in test runner, but SenTestingKit is still calling it somewhere. Here's the plugin that fixes the problem. https://github.com/joefiorini/Xcode-IDETestFixes

What did it look like when your tests crashed. I have a test suite that runs fine in Xcode 4.2, but crashes with EXC_BAD_ACCESS in 4.3. . . . . turning on zombie objects tells me nothing.
On Feb 27, 2012, at 7:51 AM, Joe Fiorini wrote:

I think they removed a method from the built-in test runner, but SenTestingKit is still calling it somewhere. Here's the plugin that fixes the problem. https://github.com/joefiorini/Xcode-IDETestFixes

Reply to this email directly or view it on GitHub:
https://github.com/allending/Kiwi/issues/86#issuecomment-4185936

It wasn't just the tests that crashed, it was Xcode itself. It crashed with a "couldn't find selector localizedStandardCompare for IDETest".
Are you depending on any settings (maybe command line tool or ARC-related) that could have changed in 4.3?

Ok, so not related.
I'm not sure, all my other projects (ARC & non-ARC) work fine. It's just this one. . . . I could try dropping the test target and create from scratch. Also add test classes one by one, i guess. . . have a deadline so right now I'm running 4.2 and 4.3 on the same machine.
On Feb 27, 2012, at 11:32 AM, Joe Fiorini wrote:

It wasn't just the tests that crashed, it was Xcode itself. It crashed with a "couldn't find selector localizedStandardCompare for IDETest".
Are you depending on any settings (maybe command line tool or ARC-related) that could have changed in 4.3?

Reply to this email directly or view it on GitHub:
https://github.com/allending/Kiwi/issues/86#issuecomment-4187470


Bulk actions with error flow

Context
HEIs currently use the ITT provider portal to recommend trainees for QTS/EYTS and record their academic outcome. To improve the user’s experience and retire the ITT provider portal we need a way for users to recommend large groups of trainees for QTS/EYTS.
We've added a way for users to download a template of trainees that are missing data or ready to be recommended for QTS/EYTS. The user can add the details and bulk update their records.
The adding missing information flow and the recommend flows are the same, but with different content and ask for different information.
# Screenshots
Start of bulk update flow

Add missing information flow

Recommend for QTS/EYTS flow

Cancel page

Notes

this assumes we won't need type of undergrad degree or undergrad degree grade
works on the same assumption that providers will give postgrad qualification ahead of the trainee getting it as the manual flow
assumes CSV upload for v1, but there are advantages to Excel if we can handle virus scanning and the file format
this doesn't update ways to get to bulk actions, will add that later (this pr is already massive)

Flow diagam

I wonder if the instructions should use bold for the data items to call out - similar to how GovWifi does it


Default configuration works better for 16.04

Research why.

Hi!
The drive is already installed, however the network-manager hang; doesn't work after drive enabled.
Ubuntu 16.04 LTS
Dell Inspiration
Emerson

I'm gonna reupload properly this repo this next week, so you can download the correct version, thank you for throwing this issue. Please open a new one so I can track it.

I do appreciate that.
Best Regards
Emerson


sendimage is not working for me please help me

sendimage is not working for me please help me

Actively search, usually someone will publish a solution ...
https://github.com/mukulhase/WebWhatsapp-Wrapper/issues/1165


OCPBUGS-23811: UPSTREAM: 354: Bump Bump OpenTelemetry to fix CVEs

There were several upstream OpenTelemetry bumps, this is just the last one.
Fixing CVE-2023-45142 and CVE-2023-47108.
@openshift/storage

/label qe-approved
CI looks good and the bump version is above the CVE fixed version.


fix issue when upgrade from 1.2.0rc1 to 1.3.0

fix legacy issue #3077

Coverage decreased (-0.03%) to 56.212% when pulling 4802f9ce3f7ee668edbed0114ed4b91ce820bc1e on ninjadq:migrator_1_2_0_rc_to_1_3_0 into 367c2b142fb744538bbf3156a85bff54a6c843d9 on vmware:master.

Coverage increased (+0.03%) to 56.244% when pulling f2868f2033ef5ecebe85fffbb51d89781b97334f on ninjadq:migrator_1_2_0_rc_to_1_3_0 into a0bd3ed8dbf41f74a5159d69bee3a988a301c868 on vmware:master.


[Bug]: appium is giving Error "Failed to instantiate remote driver instance"

shaft v7.1.20230227
Appium 2
android real device
3b5794f1be2138a2.txt

the attached logs show this error message
[DEBUG] 2023-03-08 12:07:45.105 [main] ReportManager - org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 400. Message: 'automationName' can't be blank

please make sure to setup automationName properly, here's a working sample for reference:
SHAFT.Properties.platform.set().targetPlatform(Platform.ANDROID.name());
SHAFT.Properties.mobile.set().automationName(AutomationName.ANDROID_UIAUTOMATOR2);
SHAFT.Properties.platform.set().executionAddress("localhost:4723");

also please note that it is within appium best practices to use appUrl rather than appName and appPackage, here's a working sample for that as well:
SHAFT.Properties.mobile.set().app("src/test/resources/testDataFiles/apps/ApiDemos-debug.apk");

lastly you are strongly advised to use the SHAFT wizard syntax instead as it provides enhanced sessions management and stability, you can read more about it in our official user guide, and here's a full working sample:
private SHAFT.GUI.WebDriver driver;

@BeforeMethod
public void setup() {
    // common attributes
    SHAFT.Properties.platform.set().targetPlatform(Platform.ANDROID.name());
    SHAFT.Properties.mobile.set().automationName(AutomationName.ANDROID_UIAUTOMATOR2);
    SHAFT.Properties.platform.set().executionAddress("localhost:4723");
    SHAFT.Properties.mobile.set().app("src/test/resources/testDataFiles/apps/ApiDemos-debug.apk");
}

@AfterMethod(alwaysRun = true)
public void teardown() {
    driver.quit();
}

@Test
public void wizard_scrollInExpandableLists_verticalScrolling_insideScreen() {
    ((AndroidDriver) driver.getDriver()).runAppInBackground(Duration.ofSeconds(5));
    driver.element().performTouchAction()
            .swipeElementIntoView(AppiumBy.accessibilityId("Views"), TouchActions.SwipeDirection.DOWN)
            .tap(AppiumBy.accessibilityId("Views"))
            .swipeElementIntoView(AppiumBy.accessibilityId("Expandable Lists"), TouchActions.SwipeDirection.DOWN)
            .tap(AppiumBy.accessibilityId("Expandable Lists"))
            .swipeElementIntoView(AppiumBy.accessibilityId("3. Simple Adapter"), TouchActions.SwipeDirection.DOWN)
            .tap(AppiumBy.accessibilityId("3. Simple Adapter"))
            .swipeElementIntoView(By.xpath("//android.widget.TextView[@text='Group 18']"), TouchActions.SwipeDirection.DOWN)
            .tap(By.xpath("//android.widget.TextView[@text='Group 18']"))
            .swipeElementIntoView(By.xpath("//android.widget.TextView[@text='Child 13']"), TouchActions.SwipeDirection.DOWN)
            .swipeElementIntoView(By.xpath("//android.widget.TextView[@text='Group 1']"), TouchActions.SwipeDirection.UP);
}

I'm closing this as it's not a bug, but kindly feel free to open new issues whenever you need support with something.


Develop

Mohammad Tamim
<EMAIL_ADDRESS>Pull Request - Addition of Sepsis-3 Mortality Prediction Models and Datasets
This pull request includes several components that extend PyHealth's capabilities for analyzing mortality in sepsis patients using the MIMIC-III dataset.
Changes include:

datasets/mimic3_sepsis3.py: A dataset script for preprocessing sepsis-related data.
tasks/mortality_prediction_sepsis3.py: A task definition for mortality prediction.
models/xgboost.py: An XGBoost model tailored for predicting mortality.
examples/mortality_mimic3_sepsis3.py: An example script demonstrating the workflow from data loading to prediction.

I've tested these additions with data from the MIMIC-III public dataset, focusing on ensuring compatibility and performance within the existing PyHealth framework.
I welcome any feedback on code style, performance improvements, or integration aspects. Thank you for considering this contribution!

Hello,
I've completed the requested changes and there are no conflicts with the base branch. Could you please confirm the next steps for merging this pull request? Do I need to take any further action?
Additionally, I would like to confirm that this contribution meets the requirements for the 10 bonus points as outlined in the course instructions. If there is any additional information or action needed from my side, please let me know.
Thank you!

Hi @tamimuiuc , thanks for your PR. I have started to test your PR locally.

It seems that the current dataset does not support the internal stat() function.

Hello, I have carefully reviewed your PR.

the CSV sepsis dataframe is somewhat useful as an addition to the package.
the task function is not helpful.
the example does not run (xgb.XGBClassifier needs X and y as input, but you use one dataframe).

We will give partial bonus points based on this.

Thank you for your feedback. Actually, the XGBClassifier uses:

feature_keys=['urineoutput', 'lactate_min', 'bun_mean', 'sysbp_min', 'metastatic_cancer', 'inr_max', 'age', 'sodium_max', 'aniongap_max', 'creatinine_min', 'spo2_mean'] as x.
label_key='thirtyday_expire_flag' as y.
The code should run successfully on your end as it does on mine.

Y, I can quickly make it run. There are just some minor bugs, such as XGBClassifier is not imported anywhere.

Hi, in 'xgboost.py', I did 'import xgboost as xgb' and created 'XGBoostModel' class. Also, in 'mortality_mimic3_sepsis3.py', I did both 'import xgboost as xgb' and called 'XGBoostModel'. You should be able to run the classifier successfully.

WHERE DID YOU IMPORT XGBoostModel in mortality_mimic3_sepsis3.p?

I see, you are right. I compiled all the code in Google Colab and ran it there. I did not import XGBoostModel.Thank you!


Sonoff SNZB-02D temp and humidity sensor shows up as some kind of clock

Sonoff SNZB-02D shows up on ewelink app as temp and humidity sensor with temp and humidity, but now in HomeAssistant.  Shows up as a clock I think.  It's there, just no temperature or humidity information.

I don't understand what you wrote.

   Hi Alex.  Sorry for the confusion.  I can’t set values in homeassistant.  Usually there are tempearature and humidity values.   I’m not sure what the colors mean here.  The temp and humidity values show in the ewelink app.  But this is all I get from homeassistant.  I have a clock icon on the left?   Also, the “changed to March” part I don’t know.   Thanks for your time.     Sent from Mail for Windows From: Alex XSent: Monday, March 27, 2023 11:08 AMTo: AlexxIT/SonoffLANCc: edwoody; AuthorSubject: Re: [AlexxIT/SonoffLAN] Sonoff SNZB-02D temp and humidity sensor shows up as some kind of clock (Issue #1145) I don't understand what you wrote.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>Virus-free.www.avast.com

I don't think your messages related to this integration. There is no any colors or clocks.


chore: add deprecation notice to README, point folks to istanbuljs

@gotwarlost @davglass the Istanbuljs 2.0 API is pretty battle tested at this point:

nyc has over 9.5k repositories using it.
jest has 11.6K repositories using it.
babel-plugin-istanbul has 5.13K

I noticed quite a few issues confused about the relationship between istanbul and the istanbuljs org -- along with quite a few open bugs, and pull requests, that it would be great to start helping people with.
@gotwarlost how do you feel about adding a deprecation notice to:

[ ] the istanbul repo.
[ ] the GitHub pages branch of this repo.

I think this would help us bring more folks onto your great version 2.0 API.

Coverage remained the same at 97.523% when pulling 4cb298a078b2d8b95159122a6bd95f615d02ef66 on bcoe:deprecation into 89e338fcb1c8a7dea3b9e8f851aa55de2bc3abee on gotwarlost:master.

:+1:

👍

Do you think this repository should be archived? It would be more clear that no further development is happening here :)


FT: Add component to Utapi config

Adds a component property to the Utapi configuration.
When introducing service-level metrics, including this property will allow the Utapi client to determine which service is pushing the metrics (the configuration is passed in the instantiation of UtapiClient).

@ironman-machine

Hello @bennettbuchanan
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "ft/add_component_to_utapi_config", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/8867 for CI status.

please rebase and I will merge

e2e running here: http://ci.ironmann.io/gh/scality/Integration/9113#build-parameters

e2e passed here after retry: http://ci.ironmann.io/gh/scality/Integration/9114


tab.2. and tab.3. Experiments value may wrong..?

Hi. Thank you to open nice work.
I have a few questions.
When i was reading a paper, i found that it might be wrong expression on your description in paper on page 6 paragraph 5.2. Performance on UBody is not that correct on Table2 and 3's result.
in paragraph 5.2. Performance on UBody, you said,
"Different from COCO, the gains that our TPD brings on UBody mainly focus on the face and hand. As for COCO, the performance on the body, foot, and hand all get significant improvements, but the gains on the face are limited, as shown in Tab. 2. "
but On Tab.2 every value is improved compared with baseline. so i can agree with UBody's effect on my mind but not that agree with this description "Different from COCO, the gains that our TPD brings on UBody mainly focus on the face and hand." and also "As for COCO, the performance on the body, foot, and hand all get significant improvements, but the gains on the face are limited, as shown in Tab. 2" this description too..  i mentioned above, every result had improve.. i think.
Maybe i didn't understand your paper enough. But i think that is the wrong expression..
And, i want to know in Tab.3. why face evaluation result 73.8 is the best on RTM-l(384x288)
Please reply if you don't mind.
Sincerely,

On UBody, TBD brings 0.4, 0.3, 1.0, 1.1 AP gains for body, foot, face, hand, respectively. On COCO, TBD brings 0.7, 0.7, 0.2, 1.5 for body, foot, face, hand, respectively. So "the gains that our TPD brings on UBody mainly focus on the face and hand" and "As for COCO, the performance on the body, foot, and hand all get significant improvements, but the gains on the face are limited."

@yzd-v Thanks for rapid response!
I'm sorry, but I can't match your answer with the paper's results.
In tab2., I understand the expression that "-" sign means "not use" and 'check' sign means "use"
In this perspective, I can understand first column means just baseline RTMPoose on COCO,
and second column means RTMPose with COCO+UBody, last column means your strategy DWPose.
Is there any wrong interpreting in this way? If I interpret it correctly,
On UBody, TPD brings 0.7, 0.7, 0.2, 1.5 for body, foot, face, hand respectively.  And On COCO, TPD brings 0.9, 0.4, 1.0, 4.7 for body, foot, face, hand respectively.

Adding extra dataset (UBody) can improve the performance on COCO and UBody. And such operation is not included in TPD, which is a distillation method.

Thanks!


any plan to merge the current pr?

Hey, it has been a long time since last release. Is there any plan to add more function binding, say the ones in https://github.com/menpo/cyvlfeat/pulls?

I currently don't have any bandwidth to work on these things - but if you want to review and test the existing PRs then I am happy to merge them and cut a new release

@patricksnape OK, I have create a pr https://github.com/menpo/cyvlfeat/pull/49. I add some modification to fix the conflicts and update __init__.py files.
Another question, https://github.com/menpo/cyvlfeat/blob/master/conda/lena.dat is not installed by python setup.py install, but https://github.com/menpo/cyvlfeat/blob/master/cyvlfeat/test_util.py#L1 needs it. Or maybe test_util.py should be not installed, but just for testing?

Yes we should ship a test file with the package. We also shouldn't use Lena really. I'll make an issue to track this

Release made - thanks for the hard work
https://github.com/menpo/cyvlfeat/releases/tag/v0.6.0
https://github.com/conda-forge/cyvlfeat-feedstock/pull/3


Clean up packages

Documentation and packaging cleanup for:

[ ] org.bdgenomics.adam.projections
[ ] org.bdgenomics.adam.rich
[ ] org.bdgenomics.adam.serialization
[ ] org.bdgenomics.adam.util
[ ] org.bdgenomics.adam.rdd classes not cleaned up in #1051

I'd like to propose the following package name changes:
org.bdgenomics.adam.rdd.features --> org.bdgenomics.adam.feature
org.bdgenomics.adam.rdd.variation --> org.bdgenomics.adam.variant

object Timers in package org.bdgenomics.adam.instrumentation could use some higher level doc, when to define one, how to use one, etc.

+1 @heuermh


Resource Not found exception in Mac

Hi ,
I have cloned git project from below link,
https://github.com/Kong/docker-kong.git
Executed docker-compose up command - below is the terminal output.
rajamuthua-a01:compose rajamuthua$ docker-compose up
Starting compose_db_1 ... done
Starting compose_kong-migrations-up_1 ... done
Starting compose_kong-migrations_1    ... done
Starting compose_kong_1               ... done
Attaching to compose_db_1, compose_kong-migrations-up_1, compose_kong-migrations_1, compose_kong_1
db_1                  | LOG:  database system was interrupted; last known up at 2019-08-09 13:33:39 UTC
db_1                  | LOG:  database system was not properly shut down; automatic recovery in progress
db_1                  | LOG:  invalid record length at 0/187BAB0
db_1                  | LOG:  redo is not required
db_1                  | LOG:  MultiXact member wraparound protections are now enabled
db_1                  | LOG:  database system is ready to accept connections
db_1                  | LOG:  autovacuum launcher started
kong-migrations-up_1  | Database is already up-to-date
kong-migrations_1     | Database already bootstrapped
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: using the "epoll" event method
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: openresty/<IP_ADDRESS>
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: built by gcc 8.3.0 (Alpine 8.3.0)
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: OS: Linux 4.9.125-linuxkit
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: getrlimit(RLIMIT_NOFILE): 1048576:1048576
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: start worker processes
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: start worker process 33
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: start worker process 34
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: start worker process 35
kong_1                | 2019/08/09 13:50:19 [notice] 1#0: start worker process 36
kong_1                | 2019/08/09 13:50:19 [notice] 33#0: 1 [lua] cache_warmup.lua:42: cache_warmup_single_entity(): Preloading 'services' into the cache ..., context: init_worker_by_lua
kong_1                | 2019/08/09 13:50:19 [notice] 33#0: 1 [lua] cache_warmup.lua:81: cache_warmup_single_entity(): finished preloading 'services' into the cache (in 0ms), context: init_worker_by_lua
kong_1                | 2019/08/09 13:50:19 [notice] 33#0: 1 [lua] cache_warmup.lua:42: cache_warmup_single_entity(): Preloading 'plugins' into the cache ..., context: init_worker_by_lua
kong_1                | 2019/08/09 13:50:19 [notice] 33#0: 1 [lua] cache_warmup.lua:81: cache_warmup_single_entity(): finished preloading 'plugins' into the cache (in 0ms), context: init_worker_by_lua
compose_kong-migrations-up_1 exited with code 0
Exception faced "Resource Not found"
rajamuthua-a01:compose rajamuthua$ http :8001/apis
HTTP/1.1 404 Not Found
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 23
Content-Type: application/json; charset=utf-8
Date: Fri, 09 Aug 2019 13:58:41 GMT
Server: kong/1.2.1
{
"message": "Not found"
}
Kindly assist.
Thanks

The /apis endpoint has been deprecated / removed since 0.14. If you want to build / run older versions of Kong via the docker compose export KONG_DOCKER_TAG=0.13 should handle that


Apparent memory leak when duping DocumentFragment

Ruby 2.1, Nokogiri 1.6.1
Title explains the issue I'm seeing. Here's a simple case to reproduce:
puts `ps -o rss= -p #{$$}`.to_i
doc = Nokogiri::HTML.fragment('
foobar
')
10000.times do
  doc.dup
  GC.start
end
puts `ps -o rss= -p #{$$}`.to_i

Memory usage goes from 11.9KB to 18.7KB. The contents of the fragment do not seem to matter but the bigger the fragment the bigger the leak (ran it with a large fragment and it peaked at > 1GB).
Having trouble with valgrind on OSX so unable to provide that analysis. It should be clear there's a problem if you run it. Compare to this example, which does not continue to eat up memory (from 11.12KB to 11.16KB):
doc = Nokogiri::HTML::Document.parse('
foobar
')
puts `ps -o rss= -p #{$$}`.to_i
10000.times do
  doc.dup
  GC.start
end
puts `ps -o rss= -p #{$$}`.to_i

Happy to provide more info if necessary.

Some notes:

verified this leak with Nokogiri <IP_ADDRESS> using libxml 2.9.4 with patches
leak does not occur when re-parsing fragments in a loop
leak does not occur when duping a full Document
leak does occur when duping a DocumentFragment

OK, this is because DocumentFragment#dup inherits from Node, which is copying the node subtree and rooting it in the doc. These unparented nodes just hang around for the lifetime of the doc.
Suggestion: we could implement DocumentFragment#dup to copy the DocumentFragment's parent Document, and thus treat it more like a full-blown Document (which I think is what people generally expect).

Hello, just chiming in to say I encountered the same memory leak, and I'm using this code to get around it.
# Just doing root.dup would result in the duplicate being attached to the
# same document as the original. As long as the original exists, every
# copy is also kept in memory, causing a crippling memory leak.
# So we need to go a roundabout way to create a copy that's disassociated
# from the original's document.
def clone_node(root)
  @empty_doc ||= parse("") #where parse wraps Nokogiri.HTML5
  case root
  when Nokogiri::XML::Element
    e = @empty_doc.dup #create a new document
    deepcopy = root.dup #create a deep copy of the element
    e.root << deepcopy #add it into the new doc, which creates a shallow copy of the element
    e.root.last_element_child #retrieve the copy
  when Nokogiri::XML::Text
    e = @empty_doc.dup #create a new document
    deepcopy = root.dup #create a deep copy of the node
    e.root << deepcopy #add it into the new doc, which changes the document
    deepcopy
  when Nokogiri::XML::DocumentFragment
    e = @empty_doc.dup #create a new document
    f = root.class.new(e) #create a new fragment
    root.children.each do |node| #for each element
      deepcopy = node.dup #create a deep copy
      f << deepcopy #add into the new fragment (which may create a shallow copy of the node)
    end
    f
  else #Document
    root.dup
  end
end

But imho the real fix is that when doing a dup or remove, the node can still reference the document, but the document should no longer reference the node. Although tbh I don't know if that's a libxml issue or not.

OK - I've got a second branch up in which I punt on trying to implement this optimization in the JRuby implementaiton. branch is 1063-flavorjones-dup-document-fragment-attempt-2 and I'm going to poke @jvshahid about this decision in the morning.

Chatted with @jvshahid and he agrees we should just address this issue in the libxml2/MRI code base and leave JRuby alone, at least for now. I've created #1832 to track this work for JRuby should eventually decide to do it.
Will ship a PR based on the above mentioned branch.


Unexpected error fetching intelligent_dispatches data: 'utf-8' codec can't decode byte 0xe8 in position 11: invalid continuation byte

Describe the bug
After restarting Home Assistant I am getting an error and the integration isn't initialising.
Reproduction steps
Restart Home Assistant
Expected behaviour
Integration initialises
Tariff Code
Unknown
Integration Version
9.0.2
Home Assistant Version
2023.11.3
Fresh Install?
After upgrading
Home Assistant Logs
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/util/json.py", line 68, in load_json
    return orjson.loads(fdesc.read())  # type: ignore[no-any-return]
                        ^^^^^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe8 in position 11: invalid continuation byte

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 290, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 246, in _async_update_data
    return await self.update_method()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/octopus_energy/coordinators/intelligent_dispatches.py", line 78, in async_update_intelligent_dispatches_data
    dispatches.completed = await async_merge_dispatch_data(hass, account_id, dispatches.completed)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/octopus_energy/coordinators/intelligent_dispatches.py", line 42, in async_merge_dispatch_data
    saved_dispatches = await store.async_load()
                       ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/storage.py", line 133, in async_load
    return await self._load_task
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/storage.py", line 142, in _async_load
    return await self._async_load_data()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/storage.py", line 161, in _async_load_data
    data = await self.hass.async_add_executor_job(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/json.py", line 74, in load_json
    raise HomeAssistantError(error) from error
homeassistant.exceptions.HomeAssistantError: 'utf-8' codec can't decode byte 0xe8 in position 11: invalid continuation byte

Confirmation

[X] I confirm that I cannot find my solution within the documentation
[X] I confirm that I cannot find my solution within the FAQ

Hi. It looks like HA has corrupted the local save for the intelligent dispatches. I'll try and have a look at some defensive code around this at some point this week. However in the mean time, you can resolve this by going into .storage within your HA config directory and removing the file octopus_energy.{{ACCOUNT_ID}}-completed-intelligent-dispatches.json and reload the integration (if you feel comfortable doing that). This will result in you losing the completed dispatches for the last few days, which could effect the cost calculations for the last few days.

Hello. I've added some recovery logic for this situation. If you upgrade to v9.1.0, then the integration should work. You'll probably get a warning stating that the local completed dispatches have been removed.


java.lang.NullPointerException: throw with null exception - Exception for release apks with progaurd enabled.

java.lang.NullPointerException: throw with null exception
    at com.microsoft.identity.client.u.b.a(Unknown Source:3)
    at com.microsoft.identity.client.p.a(SourceFile:21)
    at com.microsoft.identity.client.p.d(SourceFile:6)
    at com.microsoft.identity.client.p.<init>(SourceFile:6)
    at com.microsoft.identity.client.s.<init>(SourceFile:1)
    at com.microsoft.identity.client.p$d.a(SourceFile:6)
    at com.microsoft.identity.client.p$d.a(SourceFile:1)
    at c.d.a.a.f.d.e$b.run(SourceFile:3)
    at android.os.Handler.handleCallback(Handler.java:883)
    at android.os.Handler.dispatchMessage(Handler.java:100)
    at android.os.Looper.loop(Looper.java:237)
    at android.app.ActivityThread.main(ActivityThread.java:7762)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1047)

@mrudulamrudu Can you provide a bit more information like which library are you using? MSAL or ADAL? and which version?
Also When do you see this issue? Does it happen when you call a specific method in our library?

@shahzaibj I am using msal:1.2.0
The issue happens When I open the Activity with msal login code.
I am calling the below method in my onCreate()
// Creates a PublicClientApplication object with res/raw/auth_config_single_account.json
```
PublicClientApplication.createSingleAccountPublicClientApplication(this,
R.raw.auth_config_single_account,
new IPublicClientApplication.ISingleAccountApplicationCreatedListener() {
@Override
public void onCreated(ISingleAccountPublicClientApplication application) {
//
* This test app assumes that the app is only going to support one account.
* This requires "account_mode" : "SINGLE" in the config json file.
*//
mSingleAccountApp = application;
loadAccount();
}
                @Override
                public void onError(MsalException exception) {
                    displayError(exception);
                }
            });

this is only happening for release APKs.

Do I need to provide a release hash key before creating a release APK ? I suspect if its causing the app to crash ?

Are you referring the package signature? You will need to provide the redirect_uri  in the config file as well as in the AndroidManifest. The redirect uri will need to contain the package name as well as the signature. See these instructions: https://github.com/AzureAD/microsoft-authentication-library-for-android#using-msal Did you follow these when integrating with MSAL?

@shahzaibj Thanks for the response. I have followed the steps from the same link and the app works fine when I create a debug build, I am able to sign in to my account using msal and access the graph request as well. But app crashes on launch with the mentioned crash when I create a release APK with Keystore. I don't see any other errors in the logcat apart from the above crash.

Did you change the redirect uri for the release APK? The release APK will be signed with a different key, and hence result in a different package signature. Did you make sure to add two different redirect uri in the portal, one for debug and one for release? and also update according in your app based on whether the build is a debug build of release build?

No, I haven't done that. How do I create a Redirect URI for release APK ? Could you please give me a link for that ?

You can go in the Azure Portal->app registrations->select your app
->Now go to the Authentication tab
You will see option to add another redirect uri, click that it will ask you for your apps package name and singature hash and will generate a redirect uri based on those values for you.
It will also provide instructions on how to obtain the signature hash, but you can also refer to this FAQ: https://github.com/AzureAD/microsoft-authentication-library-for-android/wiki/MSAL-FAQ

@shahzaibj I have followed the steps and created a new package hash using Keystore, added it in the portal and in the app as well. The app still crashes with the same NullPointer exception.

So I guess it is a Pro Guard issue then. I found this similar issue here and may be this can help you.
https://github.com/AzureAD/microsoft-authentication-library-for-android/issues/513
I'll see if I can find something else related to Pro Guard in the past

@shahzaibj
-keep public enum com.microsoft.identity.client.configuration.AccountMode { *; }
-keep public class com.microsoft.identity.client.configuration.HttpConfiguration { *; }
-keep public class com.microsoft.identity.client.configuration.LoggerConfiguration { *; }
Adding them to progaurd fixed the issue. Thank you so much !


Update kg-microbe using latest version of KGX

This task involves avoiding pinning package version in the requirements.txt and setup.py files.

The PR #25 takes care of this.


Rename person providers

@OlgaMaciaszek
the rest of the translation work that closes #62

Coverage increased (+0.09%) to 90.975% when pulling e55672e6ffca523518979a07cc3d828b58b088bc on andidev:rename-person-providers into 688d087945c9b027abe8612f93a41629be0b4323 on Codearte:master.

Coverage increased (+0.1%) to 91.691% when pulling 0d6cb6c92ccc96b912417ba3e3826231d19dcba0 on andidev:rename-person-providers into a33c32c35a451d48f8ae9e45b953c8ffbf4ec9a5 on Codearte:master.

Thanks @andidev . The changes look good, but I think you could add comments, with information that the number represents SocialSecurityNumber (for EN) or (DNI) for ES. I would avoid excessive comments in general, but in case of such translated concepts maybe it will be useful.

LGTM.


Vue HMR does not work unless component has an active instance

Describe the bug
This bug is related to https://github.com/vitejs/vite/issues/131, and is the same one described in https://github.com/vuejs/vue-next/issues/4757.
For example, in a Vue app with Vue Router:
When a page component file is modified, if the page:

is the current route HMR works.
is not the current route, HMR does not work

As a result, when modifying a component that is not the current route, the HMR update is sent as usual, but because the component has no active instances, the Vite client does not update the module.
If the modified page component has already being imported, when its route is visited, the original module is used, which doesn't include the changes since it was never updated by HMR.

It's not specific to Vue Router though, it could happen for any development flow where a component is imported, but it might not have an active instance.
For example:
<Welcome v-if="condition"/>

If Welcome.vue is modified when the condition is false, then once the condition is true, an outdated version of the component will be rendered.
The reason I mention Vue Router first, is that it's a very typical way for users to experience the bug.
Reproduction
github.com
System Info
System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-3635QM CPU @ 2.40GHz
    Memory: 53.61 MB / 8.00 GB
    Shell: 5.8 - /usr/local/bin/zsh
  Binaries:
    Node: 16.5.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.19.1 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Browsers:
    Chrome: 94.0.4606.71
    Firefox: 91.0
    Safari: 14.0.1
  npmPackages:
    @vitejs/plugin-vue: ^1.9.3 => 1.9.3
    vite: ^2.6.3 => 2.6.4

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Fixed in https://github.com/vuejs/vue-next/commit/9e3d7731c7839638f49157123c6b372fec9e4d46


Update CHANGELOG.md

Add wrong livereload pattern fix to the list of unreleased PR's

Can you please add this to #83, it should be part of the same PR

sure, going to fix te failing tests also.


Fixed Favicon Bug

Description

This PR addresses the issue of the favicon not being found in the project. The favicon.ico file was missing from the HTML files, causing browsers to return a 404 error when trying to fetch it.
Fixes #(issue)
Getting favicon.ico not found when running demo
Checklist

[✓] My code follows the contributing guidelines of this project.
[✓] I am aware that all my commits will be squashed into a single commit, using the PR title as the commit message.
[✓] I have performed a self-review of my own code.
[✓] I have commented my code in hard-to-understand areas.
[✓] I have updated the user-facing documentation to describe any new or changed behavior.
[✓] My changes generate no new warnings.
[✓] I have added tests that prove my fix is effective or that my feature works.
[✓] I have not reduced the existing code coverage.

Comments

Hey @BasmaElhoseny01, could you do the same for lit-wes and lit-tes packages as well.

Hey @BasmaElhoseny01, could you do the same for lit-wes and lit-tes packages as well.

Of course I will 😎

@BasmaElhoseny01 I understand this PR because it gave an error, but lets try to first work on the issues that are open, if there are bugs open an issue first and then a PR :slightly_smiling_face:


"Distributed minio on docker swarm" docs have mulltiple errors

I'm talking about the following page: https://docs.min.io/docs/deploy-minio-on-docker-swarm.html
The docs say:

The docker-compose.yml file also exposes the MinIO services behind a single alias on the minio_distributed network.

and

Services in the Swarm which are attached to that network can interact with the host "minio-cluster" instead of individual services' hostnames. This provides a simple way to loosely load balance across all the MinIO services in the Swarm as well as simplifies configuration and management.

The docker-compose.yaml does not define an alias at all.
The different services (this are not load-balanced swarm service tasks) are not accessible by a common alias because the file does not define such a network alias.

Docker Swarm uses ingress load balancing by default. [...]

This does apply only to service tasks but they are not used at all. The file defines 4 services which are bound to a specific node. Thereas the ingress network of docker does not play any role at all. (Each instance uses a different port and is constrained to one node).

@Sebi2020 how about fixing the doc? happy to accept a PR.

This doc has been dropped, and we are not documenting Swarm going forward.


PROPFIND for personal space is flaky

Describe the bug
We noticed that the PROPFIND for the personal space is flaky on current master.
Steps to reproduce

Curl your personal space a few ties: curl -X PROPFIND https://localhost:9200/remote.php/dav/spaces/1284d238-aa92-42ce-bdc4-0b0000009157%2412a30d44-3145-4659-9a86-b4cfdc4e3d19 -k -u admin:admin -i

Expected behavior
A consistent 207 response.
Actual behavior
From time to time, oCIS returns a 502: Bad gateway

This is basically a duplicate of https://github.com/owncloud/ocis/issues/3134
Happens when multiple ocis instances (all using the mdns registry) are running in the same network. This results in both instance "seeing" each others service registrations -> :bomb: :boom:

closing because of duplicate.


Review updates: reviewer consensus: display

This issue covers the display of agreeing/disagreeing with a review.
Acceptance criteria

[x] Review block on submission detail page: agreement/disagreement shown as 'Agree' or 'Disagree' associated with the parent review (as per screenshot in design section below).
[x] Expanded submission on Submissions listing: agreement/disagreement shown in Review outcomes section as 'Agree' or 'Disagree' associated with the parent review. (Image shows location only, no need to match design)

[x] Review detail view (e.g. https://dev-apply.opentech.fund/apply/submissions/11/reviews/4/): will show agreement/disagreement from anyone who has agreed or disagreed with the review. A list of:  <user> <role icon> <agree|disagree>s will appear in the header to the right of the title.
[x] View all reviews view (e.g. https://dev-apply.opentech.fund/apply/submissions/6/reviews/) will show agreement/disagreement from anyone who has agreed or disagreed with the review. This will be an extra row above the score with a list as per Review Detail page.

Design:

Dev Notes
Table for reviews is constructed here:
https://github.com/OpenTechFund/opentech.fund/blob/7b49da51dcc08407abf3d9a9a94b29fadb849a2b/opentech/apply/review/views.py#L136
QA criteria
Dev:

[x] checked feature meets acceptance criteria/conforms exactly to the specification.
[x] provided good unit test coverage (if this is non-trivial behaviour).
[x] checked all tests for the project pass with this feature enabled.
[x] checked code conforms to the project coding standards.
[x] had code reviewed by another developer and resolved any issues raised.
[x] tested this feature as an end user of the website/app (Can I get to it? Is it useable? Can I break it? Does it work in an end-to-end context?)
[x] checked that this feature works on the server/s I am deploying it to.

QA:

[x] tested this feature as a front end user and it meets the acceptance criteria/conforms to the specification and design.
[x] checked that the feature works on the server/s deployed to

@gibbsmaya We have varied the acceptance criteria here. Your opinion will remain visible regardless of having submitting a review.
This simplifies the logic and is a less surprising behaviour.

AC updated. Thanks.

I've made changes per Todd's review and merged this into develop. It is ready for testing, @gibbsmaya .

This looks good to me. @todd-dembrey does this need a final review or can we mark this as ready for staging?

Hi @fourthletter, @danblah, @arduina,
This work is now ready for testing. This work follows on from #960, displaying the agreement/disagreement on reviews. The acceptance criteria describes each of the places this is displayed. This can be tested alongside #960, ensuring that every time you make an agreement/disagreement, it is displayed as expected. Please note that the front end display for this (the styling) is covered in #979 which can also be tested alongside this.
Please test this against the acceptance criteria noted in the initial issue description.
Please let us know if anything is unclear or if you have any questions. Otherwise please provide feedback of any issues you find or if everything is working as expected, please confirm and we can get this work deployed to the live site and issue closed off.
Thanks,
Maya

All acceptance criteria are visible and functional. Thanks! 💥

Great, thanks @fourthletter. Moving to @todd-dembrey ready for deployment to live.


Add Rickey07 Youtube-thumbnail-Project

I've added one project which let's you download the youtube thumbnail of any video request.

Please add the complete directory of your project with a discriptive readme and a live link for the same.


Exec failure on Node 21

Node version (or tell us if you're using electron or some other framework):
21.3.0
ShellJS version (the most recent version/Github branch you see the bug on):
0.8.5
Operating system:
NixOS and Ubuntu 22.04
Description of the bug:
A script that ran fine in Node 16/18/20 errors when run in Node 21.
[nix-shell:~/code/ironcore/recrypt-node-binding]$ node publish.js
/home/mumu/code/ironcore/recrypt-node-binding/node_modules/shelljs/src/common.js:399
        throw e;
        ^

Error [ShellJSInternalError]: ENOENT: no such file or directory, open '/run/user/1000/shelljs_6f547a18b9ffbc16419a'
    at Object.writeFileSync (node:fs:2352:20)
    at writeFileLockedDown (/home/mumu/code/ironcore/recrypt-node-binding/node_modules/shelljs/src/exec.js:61:8)
    at execSync (/home/mumu/code/ironcore/recrypt-node-binding/node_modules/shelljs/src/exec.js:66:3)
    at Object._exec (/home/mumu/code/ironcore/recrypt-node-binding/node_modules/shelljs/src/exec.js:223:12)
    at Object.exec (/home/mumu/code/ironcore/recrypt-node-binding/node_modules/shelljs/src/common.js:335:23)
    at Object.<anonymous> (/home/mumu/code/ironcore/recrypt-node-binding/publish.js:31:7)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
    at Module.load (node:internal/modules/cjs/loader:1207:32)
    at Module._load (node:internal/modules/cjs/loader:1023:12) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/run/user/1000/shelljs_6f547a18b9ffbc16419a'
}

Node.js v21.3.0

Example ShellJS command to reproduce the error:
shell.exec("yarn install --ignore-scripts");

I'm going to close this as wontfix. As discussed on #1144, this issue was a nodejs bug that was fixed in 21.4 so there's no need to patch shelljs.


views: optional replace refs addition

Allows resolving all $ref in the served schema. (closes #42)

Signed-off-by: Javier Martin Montull<EMAIL_ADDRESS>

👍  Thanks for the comments, makes sense to me.

Just pushed a new version with configurable loader and accepting the parameter ?refs=resolve
Also removed the invenio-records dependency.
At the moment it works well through the UI but during testing this entry point hook is not being called so a JsonRefError is raised. I am not sure how to make that work atm.
Comments on this new version?

Mmh. My only concern is that if the resolution is only opt-in, then we have the same issue of the beginning, where e.g. a record specifying a schema would actually specify a partial schema unless you add ?refs=resolve on the schema URL inside the record metadata. This doesn't look nice.

Mmh. My only concern is that if the resolution is only opt-in, then we have the same issue of the beginning, where e.g. a record specifying a schema would actually specify a partial schema unless you add ?refs=resolve on the schema URL inside the record metadata. This doesn't look nice.

Thats a good point. I agree it is nicer to set a config site-wide and avoid having to add the URL parameter in the schema.

Tests are passing now, so ok to add JSONSCHEMAS_REPLACE_REFS config so that a site can configure if schemas are always resolved?

Comments addressed. Please check again and let me know if there is anything more to be done on this PR.

Sure, you can force push that change. I will test later if that works with
our schemas and if it works then we are good. thanks
On Oct 11, 2016 4:22 PM, "Jiri Kuncar"<EMAIL_ADDRESS>wrote:

@jirikuncar commented on this pull request.
In invenio_jsonschemas/views.py
https://github.com/inveniosoftware/invenio-jsonschemas/pull/43:

     except JSONSchemaNotFound:

         abort(404)

   if request.args.get(

       'refs',

       current_app.config.get('JSONSCHEMAS_REPLACE_REFS'),

       type=int

   ):

       schema = {'$ref': request.base_url}

I will force-push this change if you are fine with it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/inveniosoftware/invenio-jsonschemas/pull/43, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAjcd155WUge0JOsHOLIZhDEm0Q0Qxbiks5qy5uxgaJpZM4KSVcm
.

Just checked and trying to load this schema https://github.com/inspirehep/inspire-schemas/blob/master/inspire_schemas/records/hep.json the problem persists.
Accessing it with http://localhost:5000/schemas/records/hep.json?refs=1 makes the page load indefinitely, it gets stuck in:
JsonRef.replace_refs(schema, base_uri=request.base_url, loader=state.loader)

One way to make it work for our schemas is to correct https://github.com/inveniosoftware/invenio-jsonschemas/pull/43#discussion_r82847525
And then use as a loader:
json_loader_factory(jsonresolver.JSONResolver(plugins=['invenio_jsonschemas.jsonresolver']))

In that case indeed with base_uri=request.base_url it works and it does't without.

So as long as https://github.com/inveniosoftware/invenio-jsonschemas/pull/43#discussion_r82847525 is addressed should be ok for us.
On the other hand, I am not sure how other people are writing their schemas, if they use the same technique of relative URLs as us to compose the schema, then out of the box setting JSONSCHEMAS_REPLACE_REFS=True will not work.

LGTM. :shipit: Thanks for the changes.


camlistore/go repository doesn't seem to exist

Getting an error when doing docker build ..
$ docker build .
Sending build context to Docker daemon  65.92MB
Step 1/32 : FROM camlistore/go
pull access denied for camlistore/go, repository does not exist or may require 'docker login'

Am I missing something?

Actually this has nothing to do with hosting, as we never hosted the camlistore/go image anywhere either.
As the comment in the Dockerfile says, you're supposed to build the {camlistore/perkeep}/go image yourself with misc/docker/go.
Image name fixed here:
https://camlistore-review.googlesource.com/#/c/camlistore/+/14026


html table code of DataFrame and Vector are modified

It will be better if we use thead and tbody tag in the html table code of  the DataFrame and Vector . Also I have defined to_html_thead and to_html_tbody method to get the header and body part of the html table. These things will be helpful for daru-view table ( generate table using DataTables gem ).
See how I am using this PR branch in datatables example to generate table code with pagination, search and other features.  . Actually DataTables gem will check the thead and tbody of the table.

@athityakumar use this in daru-io.

Few things that can be useful in future (TODO):

df.to_html(options) : where options may contains table id, class or other styling to include in table tag. (this can be done using content_tag)

In each row , first column must have th tag (first column is always index. Right now it is in tr tag. )  Just need to modify the tbody erb file.


fix: endpoint migration when EXTERNAL_URL is not present

For URI.parse to work the URI needs to be a FQDN otherwise nil is returned.

Pull Request Test Coverage Report for Build df575a9c6b50648ccd1dcf20bffee40dd6b75fae-PR-1232

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.092%

Totals

Change from base Build 38c41feb67c270efbe511db271ec3d9a44f79ea8:
0.0%

Covered Lines:
1189

Relevant Lines:
1799

💛  - Coveralls


Automated Package Upgrade

:tada: This PR is included in version 7.0.104 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: