[Table] mat-ripple does not work with new  format.

Bug, feature request, or proposal:
Bug
What is the expected behavior?
The ripple effect should be contained within the table row.
What is the current behavior?
When using <tr mat-row> in Angular 6 instead of <mat-row ...>, the ripple effect isn't contained within its parent container. I believe this is caused by the fact that div (the container used for the ripple) is not a valid child of the tr element it's applied to.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-myteuk
What is the use-case or motivation for changing an existing behavior?
N/A
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6.x

Actually that's a different issue than #11165. The issue seems to be that position: relative on elements with display table-row  does not have any effect.
Meaning that the ripples won't have the proper positions. Also overflow: hidden does not work. Both things are the foundation for the ripples.

Have exactly the same problem. Any workrounds here?

A workaround would be using <mat-row> instead of the native <tr> element.

I have faced the same problem too and it would be nice to have a fix for this.

Also have the same issue.

  <table mat-table [dataSource]="items">
    <!-- Name Column -->
    <ng-container matColumnDef="name">
      <mat-header-cell *matHeaderCellDef> Name </mat-header-cell>
      <mat-cell *matCellDef="let item"> {{item.name}} </mat-cell>
    </ng-container>

    <mat-header-row *matHeaderRowDef="displayedColumns"></mat-header-row>
    <mat-row *matRowDef="let row; columns: displayedColumns;" matRipple></mat-row>
  </table>

That works for me. :)

Using Material 7.0.1 - I still experience this issue.

@rocos-yishi solution worked for me. It would be nice if it were added to the Examples section for Table on the Angular Material website.

@MatthiasKunnen Using the mat-row element, the ripple effect indeed works now.

Still not working?
You probably forgot imports: [ MatRippleModule ]

@simeyla thats the exact cause.. ripple is working fine for me even on tr.

@gautamkrishnar It's not working for me either, and @MatthiasKunnen's comment does make sense to me.
Would you be able to share a working StackBlitz using <tr mat-row matRipple> please? We can't get it to work wit the "plain" <table mat-table><tr mat-row><td mat-cell> model :(

Any valid workaround on the <table mat-table><tr mat-row><td mat-cell> scenario?

@MicMicMon, have you tried using the flex version of the table?
I'm using that in a project and matRipple works for me. If you have buttons in the row, you need to work some magic to disable the ripple effect from being propagated by the buttons, but other than that it seems to work.
See this link for more info:
https://material.angular.io/components/table/overview#tables-with-code-display-flex-code-

Thanks @spyter
Actually, because of the warning in the docs, and all the good reasons listed here, I wanted to stick with the <table mat-table> scenario - but indeed, moving to <mat-table> makes ripple work out of the box.

Thanks @spyter
Actually, because of the warning in the docs, and all the good reasons listed here, I wanted to stick with the <table mat-table> scenario - but indeed, moving to <mat-table> makes ripple work out of the box.

When i used like u said then sticky scenario will broken
Sorry for bad english

2 years later, Angular 9 still has this issue...
Luckily the workaround by @rocos-yishi still works, thanks!

@QuickScoP3s Do you have any proposal in mind? This is obviously a limitation in browsers we are hitting due to our ripple implementation. tr, td elements are not displayed as blocks, hence overflow: hidden does not work. he incorrect position is also caused by a limitation of these table elements. See: https://bugs.chromium.org/p/chromium/issues/detail?id=417223.
There is not much we can do about this. Given there is a reasonable solution of using the non-native table when needing ripples, I'm closing this issue.
I'd love chatting more about this, but given our current situation, I believe there is no good way to make this work for native tables.
Here is an alternative example that shows how to make ripples work for native table-rows: https://stackblitz.com/edit/comp-11883?file=app/app.component.html.

I didn't mean to sound rude (apologies if I did), but since the issue was still open, so I though the team was still working on it. I've been using the  approach to work around the problem, as suggested, with the downside being the sticky headers not working...  I'd loved seeing a solution as I originally wanted to use sticky headers 😉 I had no idea that the table itself was the limiting factor, but thanks for clearing this up!

@QuickScoP3s No worries at all! Sorry if the state of the issue was unclear. I think we failed communicating clearly why this hasn't been resolved yet. Hopefully my latest message is clear enough. I've also created a demo StackBlitz that shows how ripples can be used together with native tables. That might be helpful to some people.

@devversion StackBliz demo works as advertised.  If this issue is not easily solvable your work around should be discoverable from the docs. Would save a bit of hair pulling ;)

@Spencer-Easton Sounds reasonable. I'll re-open this as we could certainly have this documented in the ripple overview. Any help on this would be appreciated as it's most likely low-priority for us.


Link rewriter step

Use custody information to track how file names change, then rewrite links to those files accordingly in HTML, CSS, and perhaps JS.

Big issue to solve— how do you pick between different downstreams, for example between thumbnails and new file types? Distinguishing between template inputs like a Jinja HTML and the real input like an MD isn't hard because you start with the MD file in the link, but telling between a Jinja index of those MD files and the rendered MD will require a heuristic as well.


Serving owlapy within a web framework (FastAPI or LitServe)

owlapy-serve

something like this: 4ad8c2d2f3cfe7234386c5efaae7eb1fa1d1a1c8 ?

Yes indeed!

I will extend the functionality and create a PR than 👍🏼


docs: fix conn type in airflow integration

Fix adding connection to lakefs using airflow command-line:
UserWarning: The type provided to --conn-type is invalid: HTTP

Already have a pending issue to have custom connection type, which can be a better option than customize http connection


Integrate with dask>=2023.7.1

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.65% :tada:

Comparison is base (dbeeb1b) 99.34% compared to head (77f3827) 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##           master      #502      +/-   ##
===========================================
+ Coverage   99.34%   100.00%   +0.65%
===========================================
  Files         128       128
  Lines       12184     12027     -157
===========================================
- Hits        12104     12027      -77
+ Misses         80         0      -80

Files Changed
Coverage Δ

fugue_ray/execution_engine.py
100.00% <ø> (ø)

fugue_spark/execution_engine.py
100.00% <ø> (ø)

fugue_test/builtin_suite.py
100.00% <ø> (ø)

fugue_test/execution_suite.py
100.00% <ø> (+12.04%)
:arrow_up:

fugue/_utils/io.py
100.00% <100.00%> (ø)

fugue/dataframe/array_dataframe.py
100.00% <100.00%> (ø)

fugue/dataframe/arrow_dataframe.py
100.00% <100.00%> (ø)

fugue/dataframe/dataframe.py
100.00% <100.00%> (ø)

fugue/dataframe/iterable_dataframe.py
100.00% <100.00%> (ø)

fugue/dataframe/pandas_dataframe.py
100.00% <100.00%> (ø)

... and 14 more

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


refactor: avoid index order conversion for MP2

Summary
I want to be able to reuse the MP2 computing functionality elsewhere and would like to avoid the physicist-to-chemist conversion. So this PR refactores the internal _compute_mp2 utility to rely on physicist-ordered two-body terms instead.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

7 of 7 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 85.928%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
17421

Relevant Lines:
20274

💛  - Coveralls


Normalise author & publication data where possible

I've noticed that the data we have is a bit unpredictable in terms of formatting and structure. A few examples from the searches I keep running:

Note here that the darker text indicates the author, and the lighter text indicates the publication information. Because of the slightly messy data, it's not always apparent that this is the structure here.
A few things I notice:

Spacing and punctuation is unpredictable and unexpected (spaces around colons, no spaces after commas, trailing commas, open braces that don't close, spacing around parentheses, square braces vs parentheses, etc)
Multiple authors are attributed oddly (Wahl, Jan,Tomes, Margot)
Authors sometimes have dates inserted (Phillips, Vernon Sirvilian, 1871-) or needless metadata (Broughton, Oliver M., author.)
Metadata repeated needlessly (Edinburgh (Scotland ), Edinburgh , Edinburgh, Edinburgh (Scotland, Scottish burgh records society Printed for the lordprovost, magistrates andcouncil 1899)

These are all relatively minor issues, but they do make the metadata harder to parse. Are there ways that we could normalise this data? Given that we don't have full control over the data as it comes in, I'm thinking we'd need to build something of a "translation" layer on top of the existing data, so we can parse it a bit prior to outputting it. The trick, of course, is to ensure that we aren't over-correcting the problem and we're only improving the readability of the text—some of these issues might be easier to fix than others.

If we're set on trying to do this algorithmically, first steps would be to start collecting some larger subsets of data that we can try and experiment with - I have a definite fear that any algorithmic approach will end up overzealous though.

Whilst its good to keep an eye on this, I think it isn't an easy one to solve.  In a sense, it's a worldwide library problem.  We all work to standards, but interpret them differently!  The joy(!) of aggregating data from so many varied sources is that the data will naturally not match cleanly like this.  This is one of the reasons for trying to keep to quite a sinmple set of core fields which are hard to misinterpret and should translate well between countries / languages / material types: e.g. title and creator.
Having said that... I think one of the (many) benefits this site could bring, is that as the aggregation of data grows, it becomes a richer source that can be used  for different purposes, such as cleaning or tidying up data.

So me and Sarah discussed this a while back actually, I had suggested what might be quite nice is if we supported crowdsourcing data correction. We can't easily correct data algorithmically but we can probably identify data we don't understand - if we were to have a separate page where users could work through that and correct it in such a way that (provided enough people agree this is the correct interpretation) it got written back to the database that would be... an interesting project in itself. :smile:

Also what we would ideally want is for the corrections to also be sent back to the source library for them to include in their catalogues, so the next time we get a data feed, the corrected data isn't overwritten.


 I am using fedora 28 with KDE.
Here is the output I got,

me@linux: $ . ~/.vimrc
bash: $'\n': command not found
bash: $'       Amir Salihefendic — @amix3k\n': command not found
bash: $' Awesome_version:\n': command not found
bash: $'\n': command not found
bash: $'\n': command not found
bash: $'\n': command not found
bash: $'    -> General\n': command not found
bash: $'    -> Colors and Fonts\n': command not found
bash: $'    -> Text, tab and indent related\n': command not found
bash: $'    -> Moving around, tabs and buffers\n': command not found
bash: $'    -> Editing mappings\n': command not found
bash: $'    -> Spell checking\n': command not found
bash: $'    -> Helper functions\n': command not found
bash: $'\n\n\n': command not found
bash: $' => General\n': command not found
bash: $' Sets how many lines of history VIM has to remember\nset history=500\n\n': command not found
bash: filetype: command not found
bash: filetype: command not found
bash: /home/nayabsd/.vimrc: line 103: syntax error near unexpected token (' bash: /home/nayabsd/.vimrc: line 103: " Don't redraw while executing macros (good performance config)'

Could anybody tell me how to fix it? Thank you.

.vimrc is for vim .. its automatically loaded when u run vim
its not for bash
u can close this issue now

I know vimrc is for Vim. I wanted you check why it's giving errors on Fedora..:)

@nayabbashasayed If you know its for vim, then you wouldn't try to execute it from a shell. Please readup on the documentation of VIM to see how to use a vimrc.


Unable to perform az apim backup

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az apim backup
Errors:
No module named 'azure.mgmt.apimanagement.models.api_management_client_enums'
Traceback (most recent call last):
Temp\pip-install-mjd5h3hf\knack\knack\cli.py, ln 206, in invoke
azure\cli\core\commands\__init__.py, ln 523, in execute
azure-cli-core\azure\cli\core\__init__.py, ln 294, in load_arguments
azure\cli\command_modules\apim\__init__.py, ln 28, in load_arguments
azure\cli\command_modules\apim\_params.py, ln 11, in <module>
ModuleNotFoundError: No module named 'azure.mgmt.apimanagement.models.api_management_client_enums'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az apim backup --verbose --debug --output {} --subscription {} --resource-group {} --name {} --no-wait

Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
Shell: cmd.exe

azure-cli 2.0.77

Additional Context

This should be fixed now. Recommend closing.

This is fixed now.


Positive test result page hides button

On the positive test result page, if the font is large then the screen does not scroll and there is no way to access the start button.

This has been resolved.


app exception option for keyboard manager shortcuts

Description of the new feature / enhancement
self explanatory
Scenario when this would be used?
self explanatory
Supporting information
No response

/dup #8809


Argument #1 ($value) must be of type Countable|array, stdClass given

Caused by #170

It was trying to call count on a stdClass object which this fixes.
Also when showTotal with a value of false was in the request because of the way we are resolving the options the value was resolving to the string "false" and, therefore, always treating showTotal as true.
I have applied a fix for this also

Thank you for the contribution @dmason30  , I've release it at version 0.4.3 https://github.com/coroo/nova-chartjs/releases/tag/v0.4.3
Please let me know if you encounter any problem. Again, Thank you.


Invalid emoji regular expression

Here is the full error message:
Invalid regular expression: /^(\p{Extended_Pictographic}|\p{Emoji_Component})+$/: Invalid property name
based on sentry, it says the error is happening on this line:
const emojiRegex = /^(\p{Extended_Pictographic}|\p{Emoji_Component})+$/u;
Looking thru the zod source code quickly it seems like this line is the origin.
For context, this is happening on a NextJS (13.1.6) site with zod v3.21.4.
Based on sentry it seems like it's happening on Android phones exclusively on the following browsers:

UC Browser 13.4.2: 24%
Chrome Mobile 68.0.3440: 16%
Chrome Mobile 66.0.3359: 16%
Chrome Mobile WebView 62.0.3202: 12%
Other: 30%

Per this issue: https://github.com/colinhacks/zod/issues/2302 I'm going to try downgrading to<EMAIL_ADDRESS>and see if it fixes things.
Hopefully the info in this issue is helpful in the meantime!

https://github.com/colinhacks/zod/blob/a8be4500851923aa865e009fe9c2855e80482047/src/types.ts#L556
The Unicode Sequence Properties proposal has offered the ability to match all emoji sequences valid for interexchange:
/^\p{RGI_Emoji}$/v

And @babel/preset-env supports the v flag.

hi：
I also encountered this issue on Android 8
zod： 3.21.4
Is there any solution？

any solution?

This regex is now lazily created: https://twitter.com/colinhacks/status/1709688442316312846
So as long as you aren't using z.string().emoji() you shouldn't get an error.
If you really need emoji validation that works on these older browsers, I'd recommend using z.string().regex() and using an emoji regex that uses older syntax. They tend to be really long and complex so I don't want to put them in Zod core.


Fixes this component not rendering on custom post type

fixes https://github.com/frontity/saturn-theme/issues/58

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

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


how to start

dev@dev-x:~$ cd Documentos
dev@dev-x:~/Documentos$ cd go-base
dev@dev-x:~/Documentos/go-base$ go build   OK
dev@dev-x:~/Documentos/go-base$ go run main.go
A longer description that spans multiple lines and likely contains
examples and usage of using your application. For example:
Cobra is a CLI library for Go that empowers applications.
This application is a tool to generate the needed files
to quickly create a Cobra application.
Usage:
go-base [command]
Available Commands:
gendoc      Generate project documentation
help        Help about any command
migrate     use go-pg migration tool
serve       start http server with configured api
Flags:
--config string   config file (default is $HOME/.go-base.yaml)
--db_debug        log sql to console
-h, --help            help for go-base
Use "go-base [command] --help" for more information about a command.
dev@dev-x:~/Documentos/go-base$ go-base migrate init
go-base: comando não encontrado
dev@dev-x:~/Documentos/go-base$ go-base migrate
go-base: comando não encontrado
dev@dev-x:~/Documentos/go-base$ go-base serve
go-base: comando não encontrado
dev@dev-x:~/Documentos/go-base$

Sorry for the late reply. You basically have to follow the steps listed below "Start Application":

create a postgres database if you haven't already
build the application executable go build
create the database tables with go-base migrate init
run the migrations scripts to populate some data with go-base migrate
run the http server with go-base serve


WIP: Bounty with new contract

This contract has no knowledge of target contract. Also this contract allows researchers to create own copy of the target so very similar to how current contract works.
The current implementation can be compiled without error but I am getting out of gas error when running tests against it. I was also advised from @axic and @Arachnid to use factory pattern instead as this implementation would require cost more gas. Also I am less confident with this code as I copied & pasted someone's solution without firm understanding of how this code works.

I will close this PR in favor of https://github.com/OpenZeppelin/zeppelin-solidity/pull/43


Merging this into apex / pytorch?

Hi!
Your algorithm looks like a generally superior way to compute multi-head attention for heads 16,32,64 and 128.
Do you consider merging this project into standard libraries such as apex?
It would make it accessible to most DL researchers automatically and simplify using this in other libraries like transformers and fairseq.
Your codebase appears to be a modification of apex's FMHA - and it even seems to recover FMHA exactly in case there is only one block, so perhaps it would be possible to merge the two somehow?

Indeed we used Apex's FMHA as a starting point.
Yes, we'd love eventually integrate our implementation with other libraries (apex / pytorch). Let's chat more about it!

Did you get in contact with apex maintainers to get this merged?

[disclaimer: I'm not the author, just a random observer, but] i have a reasonable suspicion that they'll have a call with apex devs reasonably soon.

As of Pytorch 2.0, FlashAttention is now available through F.scaled_dot_product_attention.


Calling 'depends_on :python' is deprecated

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.
Please always follow these steps:

[x] Confirmed this is a problem with running a brew command and not brew installing or the post-install behaviour of one or more formulae? If it's a formulae-specific problem please file this issue at the relevant tap e.g. for Homebrew/homebrew-core https://github.com/Homebrew/homebrew-core/issues/new
[x] Ran brew update and retried your prior step?
[ ] Ran brew doctor, fixed all issues and retried your prior step?

Warning: Calling 'depends_on :python' is deprecated!
Use 'depends_on "python"' instead.
/usr/local/Homebrew/Library/Homebrew/dependency_collector.rb:88:in `parse_spec'

[x] Ran brew config and brew doctor and included their output with your issue?

HOMEBREW_VERSION: 1.5.0-6-gd14fd49
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: d14fd49b3062ab1d95e86b78a8228c8aee3a3304
Last commit: 2 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 7ac6f28b4dd06a5a086d085d2b1ada65ba64aa51
Core tap last commit: 80 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DEV_CMD_RUN: 1
CPU: quad-core 64-bit broadwell
Homebrew Ruby: 2.3.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/bin/ruby
Clang: 9.0 build 900
Git: 2.16.0 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Perl: /usr/bin/perl
Python: /usr/local/opt/python/libexec/bin/python => /usr/local/Cellar/python/2.7.14_2/Frameworks/Python.framework/Versions/2.7/bin/python2.7
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Java: 1.8.0_45
macOS: 10.13.3-x86_64
Xcode: 9.2
CLT: <IP_ADDRESS>.1.1510905681
X11: 2.7.11 => /opt/X11

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
  /usr/local/include/python2.7/greenlet/greenlet.h
  /usr/local/include/python3.6m/greenlet/greenlet.h
Warning: Calling 'depends_on :python' is deprecated!
Use 'depends_on "python"' instead.
/usr/local/Homebrew/Library/Homebrew/dependency_collector.rb:88:in `parse_spec'

To help us debug your issue please explain:
On brew update or brew doctor I have this warning. Brew is still working but on every updated formula this rows pop up.

I'm getting the same thing but I'm not quite sure if I should remove everything and reinstall?
Warning: Calling 'depends_on :fortran' is deprecated!
Use 'depends_on "gcc"' instead.
/usr/local/Homebrew/Library/Taps/staticfloat/homebrew-julia/arpack-julia.rb:19:in `<class:ArpackJulia>'
Please report this to the staticfloat/julia tap!

Warning: Calling 'depends_on :python' is deprecated!
Use 'depends_on "python"' instead.
/usr/local/Homebrew/Library/Taps/staticfloat/homebrew-julia/llvm37-julia.rb:149:in `<class:Llvm37Julia>'
Please report this to the staticfloat/julia tap!

ind $(brew --cellar) -maxdepth 4 -mindepth 4 -regex '.*\.rb$' -exec grep -r 'depends_on :python' "{}" \;
/usr/local/Cellar/libmagic/5.32/.brew/libmagic.rb:  depends_on :python => :optional
/usr/local/Cellar/nlopt/2.4.2_2/.brew/nlopt.rb:  depends_on :python => "numpy" if build.with? "python"
/usr/local/Cellar/tbb/2018_U2/.brew/tbb.rb:  depends_on :python if MacOS.version <= :snow_leopard
/usr/local/Cellar/graphviz/2.40.1/.brew/graphviz.rb:    depends_on :python

find $(brew --cellar) -maxdepth 4 -mindepth 4 -regex '.*\.rb$' -exec grep -r 'depends_on :fortran' "{}" \;
/usr/local/Cellar/hdf5/1.10.1_2/.brew/hdf5.rb:  depends_on :fortran
/usr/local/Cellar/openblas-julia/0.2.20/.brew/openblas-julia.rb:  depends_on :fortran

staticfloat/homebrew-julia

@kirk86 Report this to that tap.

@MikeMcQuaid  Thanks, I just did! I didn't notice the message indicating where to report the bug in the first place.


Do not reify dependencies everytime the same module is looked up

We ideally only need to reify the dependencies of a module once for the first time it is looked up. Thereafter, we can reuse the store reified values. This PR fixes that. Earlier it was reifiying the dependencies of a module and evaluating the sub tree irrespective of if the dependencies were already resolved.
cc: @chadhietala

I think this is correct but would like @stefanpenner to take a look.

I think @stefanpenner this PR also does the same thing with other changes: https://github.com/ember-cli/loader.js/pull/75. If that get's merged, we can close this PR.

this is in addition to: https://github.com/ember-cli/loader.js/commit/6ccb0a45db2e5d436281209cb1240aa144e3413c

@stefanpenner do you want me to close this PR?

I may have missed a scenario, if this commit covers such a case we should add it. I'll try to look closely tomorrow, but if you can provide an example that this fixes but the other does not please share.


Add internal unsubscription if we know the websocket has disconnected

The client keeps a list of subscriptions now so that we can stop listening if the connection is closed
closes #86

two of the three new test cases seem unrelated, at least they don't fail if the list is not being copied.
Please split such commits next time and add a bit more information.  The reviewer will thank you.
If we fix bugs and write tests for them, I would really like us to write a failing test,commit that, and commit the fix afterwards. Not sure if that works with our CI setup.
I feel like streams.py could/should be simplified. If it was simple enough we wouldn't have the discussions if the list that is being iterrated over, is also being modified or not. But that's probably a different issue.
Nevertheless please push this as is.


Possible bug: fsync() required after calling rename()

Original issue 189 created by madthanu on 2013-07-17T03:34:10.000Z:
Similar to issue 187, this bug is about what happens during a power-failure.
Also, this bug is not actually triggered atop file-systems that I usually use (ext3/ext4), so I haven't tried reproducing it on a real system.
The bug: When LevelDB opens a database, it compacts the current log files to a ".sst" file, creates a new MANIFEST, and updates the CURRENT file. Updating the CURRENT file is done with the usual atomic technique using rename(). It then deletes the old log files and old MANIFEST file.
In this entire sequence of operations, LevelDB does not explicitly ensure that the rename() (corresponding to the CURRENT file) actually happens before the unlink()s (of the old MANIFEST and log files). If the unlink()s happen before the rename, the database can be left corrupted (due to a missing MANIFEST) or wrong (due to a deleted, non-compacted log). I verified the corruption and wrong-behavior by simulating the unlink()s happening before the rename().
Saying that, considering Linux, neither ext3 nor ext4 never "re-order" calls like unlink() or rename(). Btrfs comes close to affecting LevelDB by doing re-ordering, but it seems to only re-order  such that rename()s get pushed before unlink()s, and so seems to do no real harm.
Nevertheless, LevelDB should not depend on the unlink()s happening after the rename(). There are lots of operating systems and file-systems out there.

@cmumford Hi Chris.
I've been getting pretty reliable leveldb issues with google-chrome on my linux laptop with btrfs.
Basically most times my laptop crashes, when I reboot, my google-chrome profile ends up corrupted in various ways.
See https://bugs.chromium.org/p/chromium/issues/detail?id=738961#c9
I don't know the details, nor do I have direct proof, but it's happened enough times that it seems that there is something wrong, now.


Adding torchtext to requirements.txt

Signed-off-by: Shrinath Suresh<EMAIL_ADDRESS>Adding torchtext to the requirements.txt file as it is needed for bert training.

@shrinath-suresh we are installing torchtext from src. https://github.com/chauhang/uber-prof/blob/fe41b9abef9081dcedf2ce3f4d507991d97ac51f/training-job/install_PT1.10_from_src.sh#L23

Per discussion with @jagadeeshi2i , torchtext is already getting installed from source. Hence, its not needed in requirements.txt.


Report panel header text is not honored unless edited.

Describe the bug
Report panel header is blank unless the text is edited in the config, saved and published.
Expected Behavior
Display the text in the report panel header
Reproduction Steps & Sample

Other Relevant Info
No response

@jmhauck
By default when the configuration panel is loaded is it not setting those values in reporter component props?
Is it something we need to change in the reporter or does this need to be fixed in Instant App, please suggest
Similar issue #518

Ready to test after next build...fix added to IA repo


Add Phi-3.5-mini-instruct

Please add the latest Phi-3.5-mini-instruct model to PicoLLM, which is much better than Phi-2.

Hello @niutech, adding Phi-3.5-mini-instruct is on our roadmap but I don't have an estimate for when it will be finished.

Hello @niutech, Phi-3.5-mini-instruct has been added to PicoLLM and is usable with the 1.2 version of the sdk.

@matt200-ok Fantastic! Thank you!


Unable to find/see ApiManagementGatewayLogs table

This issue is for a: (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

I followed the docs very closely. When I got to the Configure the Diagnostic Logs settings step, and click on the Azure Monitor tab, I receive the message saying:

After clicking here, I'm navigated to the Diagnostic Setting screen of the APIM resource. I created a new Diagnostic Setting then navigated back to the API Settings screen. Same issue, nothing changes.
I created an App Insights resource and a Log Analytics Resource, etc. Still no change.
Are there App Insights/Azure Monitor provisioning steps missing from the setup documentation?
Minimal steps to reproduce

The formal docs, I followed closely

Any log messages given by the failure

N/A

Expected/desired behavior

When I navigate to the App Insights resource that is connected  to APIM, I should see the ApiManagementGatewayLogs table with all the APIM OpenAI logs.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Windows 11

Versions

Current

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Disregard!
The Log Analytic Workspace where logs are landing was in another Resource Group.


fix: TypeError: "cwd" must be a string

In Node 8, using process.cwd as a property rather than a method throws.

For reference, see https://github.com/indexzero/daemon.node/pull/42


Fixed strict mode incompatible with Firefox.

The issue will caused to Firefox syntax error.

The issue cause to my app interrupted in Firefox, please fix as soon as possible.


OH - User specific request - Needs Screenshot of their results going to the State by (EOD Monday)

Problem statement
Dr. Matthews<EMAIL_ADDRESS>is being audited by Department of Health on July 18 and needs to demonstrate full compliance.  A screenshot of her results being submitted to the state would be sufficient.
What you need to know
This is a test results from the State of Ohio.  She needs documentation showing that she's in full compliance with the State of OH by EOD Monday July 18.

...

Acceptance criteria

Screenshot of her test result submitted to the state of OHIO.

To do
Someone needs to locate her test results being submitted to the State of OHIO.

[ ] ...

Hey team! Please add your planning poker estimate with ZenHub @brick-green @oslynn @jorg3lopez @greene858 @TomNUSDS @sarahnw


for aws based and password less logins to boxes

@rghose you can also add ssh-add ~/.pem/your-key-name.pem and then run the command.
That would be another good documentation addition IMHO

Thanks!


should mrujs.fetch trigger the event chain?

Describe Problem
When calling window.mrujs.fetch() should it trigger the ajax:<name> events?
Additional Details
UJS did not do this, but I view Mrujs as a superset and wonder if some cool interactions could happen from this....
Edit:
thumbsup for "yes trigger events"
thumbsdown for "no, async / await is plenty."

And as a follow up, should you be able to opt-in / opt-out of dispatching events when calling fetch? 🤔

Good catch!  Thinking about it this morning, my personal preference is to dispatch them with an available opt-out.
This is new functionality, so nobody’s going to have expectations based on old UJS behavior.  It’s also a nice to have.  As a user I can recreate this now if I need to by manually dispatching events from the promise handlers.
That said, I can see a use where I’m sharing common handling behavior between data-remote links/forms and fetch requests.  Having fetch dispatch events would be really convenient for that.  But honestly 90% of my fetches will just be handling the promise.
One other consideration is on the code itself.  Do data-remote links/forms go through mrujs.fetch under the hood?  If so that could be a case for always dispatching events to keep things consistent.
I guess events would fire on ‘document’ since there’s no associated DOM node?  Maybe callers could provide an eventTarget option that takes a DOM node and the events will be dispatched from there.  This would be useful for integrating with data-remote handling based on bubbling.

@existentialmutt I havent fully thought about the API, but i do agree providing an element to trigger off of and a boolean for dispatching events is a good idea.
And yes, data-remote and data-method both hook into fetch, although slightly differently as theres an actual formSubmitDispatcher that handles dispatching events.
Perhaps something like fetchWithEvents() or fetchAndDispatchEvent() may be more explicit than using kwargs...the API needs a little more thinking. But i do agree it would be cool to hook onto events.

cool!  My vote is for keyword args to keep the overall surface area of the API smaller.

@existentialmutt im still kinda back and forth on this. Im not sure theres a good reason to trigger the event chain...but i could also be entirely wrong...Im still thinking about this one.


ENHANCEMENT: added site-tree icons to simple theme due to the fact that ...

...they no longer exist in framework where the docs.silverstripe tutorial states they are. I will submit a pull request for the tutorial file-path change afterwards.

Thanks for the pull request and sorry it has had no feedback in six years! I'm going to close since it's unlikely to still be relevant. Please feel free to reopen if you think it's still an issue!


Oracle Database installation failed in Kubernetes Environment (Permission Denied issue)

Unable to create Oracle Database in Kubernetes
Oracle Database Express Edition 18
kubectl --kubeconfig=kube.config logs oracle-rdbms-599b96bcf9-5nh9c -n test
/bin/sh: /opt/oracle/runOracle.sh: Permission denied
/bin/sh: line 0: exec: /opt/oracle/runOracle.sh: cannot execute: Permission denied
kubectl --kubeconfig=kube.config version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.8", GitCommit:"35dc4cdc26cfcb6614059c4c6e836e5f0dc61dee", GitTreeState:"clean", BuildDate:"2020-06-26T03:43:27Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.9+vmware.1", GitCommit:"f856d899461199c512c21d0fdc67d49cc70a8963", GitTreeState:"clean", BuildDate:"2021-03-19T23:57:11Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Deployment File:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: oracle-rdbms-oradata
namespace: test
labels:
app: oracle-rdbms
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 15Gi
apiVersion: v1
kind: ConfigMap
metadata:
name: oracle-rdbms-config
namespace: test
labels:
app: oracle-rdbms
data:
ORACLE_CHARACTERSET: "AL32UTF8"
ORACLE_EDITION: "enterprise"
ORACLE_SID: "ORCLCDB"
ORACLE_PDB: "ORCLPDB1"
apiVersion: apps/v1
kind: Deployment
metadata:
name: oracle-rdbms
labels:
app: oracle-rdbms
namespace: test
spec:
replicas: 1
selector:
matchLabels:
app: oracle-rdbms
strategy:
type: Recreate
template:
metadata:
labels:
app: oracle-rdbms
spec:
securityContext:
runAsUser: 54321
fsGroup: 54321
containers:
- name: rdbms
image: harbor.dev/oracle/express
envFrom:
- configMapRef:
name: oracle-rdbms-config
securityContext:
runAsUser: 54321
ports:
- containerPort: 1521
name: oracle-listener
- containerPort: 5500
name: oem-express
volumeMounts:
- name: oradata
mountPath: /opt/oracle/oradata
readinessProbe:
initialDelaySeconds: 60
periodSeconds: 60
exec:
command:
- /bin/sh
- "-c"
- $ORACLE_BASE/$CHECK_DB_FILE
livenessProbe:
initialDelaySeconds: 300
periodSeconds: 60
exec:
command:
- /bin/sh
- "-c"
- $ORACLE_BASE/$CHECK_DB_FILE
volumes:
- name: oradata
persistentVolumeClaim:
claimName: oracle-rdbms-oradata
apiVersion: v1
kind: Service
metadata:
name: database
namespace: test
labels:
app: oracle-rdbms
spec:
ports:
- name: listener
port: 1521
targetPort: oracle-listener
selector:
app: oracle-rdbms

I also tried
spec:
  securityContext:
    runAsUser: 0
    fsGroup: 54321

However after 34% pct of the Database Creation it failed.

@viju2008 you need to clean up the failed setup. Exec into the pod and do a rm -rf /opt/oracle/oradata/* Then delete the pod using command kubectl delete pod. This will spin up a new replacement pod that should create the DB successfully
You may also want to try this https://github.com/oracle/oracle-database-operator

Hello ,
I have deleted the whole persistent volume , the deployment and then tried again.
That also dosent  help.
I cannot exec into the pod after the error comes as it goes into failed state, hence its not possible to execute rm command. We can exec into pods only in runnimg state by design of kubernetes.
Vijay

@viju2008 deleting the PV may not help as the content would still reside in the volume.
Do a kubectl edit on deployment yaml and add a command section as shown below
containers:

name: rdbms
command:
- bash

The restarted pod should just come with the bash shell. Exec into the pod, clean up the datafiles
Now revert the change you made. Hopefully this should resolve the issue.

@viju2008 deleting the PV may not help as the content would still reside in the volume.
Do a kubectl edit on deployment yaml and add a command section as shown below
containers:

name: rdbms
command:

bash

The restarted pod should just come with the bash shell. Exec into the pod, clean up the datafiles Now revert the change you made. Hopefully this should resolve the issue.

Whenever a new PV is created a new volume is created in the storage VSAN.  Hence the issue will not occur

The issue still persists we are unable to create the Oracle Database . We have tried few combinations of SecurityContext
runAsUser
runAsGroup
fsGroup
Please provide a solution. Can you check if the image has some issue we have downloaded the same from Oracle official container registry

Are you still seeing this FATAL error?
Configuring Oracle Database XE.
[FATAL] [DBT-06607] The data file (/opt/oracle/oradata/XE/system01.dbf) already exists on the file system.
If yes, then the PV is not clean

Whenever I apply the yaml a new VMFS folder i created and the contents are created on that.
When i delete the deployment using YAML the contents of the PV are moved to another VMFS folder.
Whenever the yaml is reapplied again  a new PV with a new GUID is created and a new VMFS folder with the same GUID (i.e. new GUID) is created hence the chance of old data being there is the PV volume is ruled out

/opt/oracle/oradata/XE is created but never deleted by runOracle.sh
If you are seeing this FATAL error, then PV is not clean for sure. The restriction with XE image is that you cannot change the SID, hence the PV has to be clean to recreate the DB with same SID.
Alternatively you may want to try the enterprise edition where you may change the SID to workaround this issue

We had tried to download enterprise image but we are getting download issues highlighted to our local Oracle ACS Team

To download the enterprise image, please provide a image pull secret in your yaml file and also make sure to login and accept the licensing terms. This is a must

To download the enterprise image, please provide a image pull secret in your yaml file and also make sure to login and accept the licensing terms. This is a must

Dear Sir
It is downloading but breaking in between due to unexpected EOF

@viju2008 is this still an issue?
Btw, there is a 21.3 XE image published in container-registry.
container-registry.oracle.com/database/express:21.3.0-xe

@viju2008 plz retry with new OraOperator 0.2.0
https://github.com/oracle/oracle-database-operator


Using Conditions to assert maps entries/keys/values

I wonder if it makes sense to make a next step from #205 and #690 and add more methods to MapAssert.
Like:
hasEntry(Condition<? super E> entryCondition)
hasValue(Condition<? super V> valueCondition)
hasKey(Condition<? super K> keyCondition)

and their negative counterparts.

the first one already exists : http://joel-costigliola.github.io/assertj/core-8/api/org/assertj/core/api/AbstractMapAssert.html#hasEntrySatisfying-K-org.assertj.core.api.Condition-
I'm ok to add the other if you can give me a real life use case.

the first one already exists

That's not quite true. I have to know the key in order to use that method. But I'm talking about more general approach where I have some criteria for an entry, which may or may not include a specific key.
A real life use case. I was trying to create a test case today where I had to check if a map didn't have a value which satisfied some predicate.
The only way to do that now is something like:
Assertions.assertThat(map.values()).areNot(new Condition<>(s -> ..., "desc"))

//or use `doNotHave`

The only problem with that approach, is if assertion fails I'll get map.values() in a error message, and not the map itself.
Hamcrest does have matchers like the ones from the description

You are right about the API.
I would use a different syntax:
hasEntrySatisfying(Condition<? super E> entryCondition)
hasValueSatisfying(Condition<? super V> valueCondition)
hasKeySatisfying(Condition<? super K> keyCondition)

I'm fine with any naming as long as it provides the functionality 👍


Zephyr UART shell crashes on start if main() is blocked

@jarz-nordic @nordic-krch
Describe the bug
Zephyr UART shell crashes on start if main() is blocked.
To Reproduce
Steps to reproduce the behavior:

compile samples/subsys/shell with blocked main()

patch -p1 <<EOF;
--- a/samples/subsys/shell/shell_module/src/main.c
+++ b/samples/subsys/shell/shell_module/src/main.c
@@ -120,4 +120,5 @@ SHELL_CMD_ARG_REGISTER(version, NULL, "Show kernel version", cmd_version, 1, 0);
 void main(void)
 {

+	while(1);
 }
EOF

cd samples/subsys/shell/shell_module
rm -rf build && mkdir build && cd build
cmake -DBOARD=olimexino_stm32  ..
make

burn zephyr image into MCU;
open your favorite communication application (e.g. minicom or screen) and connect to MCU UART_1;
reset MCU;
see no characters from MCU UART_1 (or one garbage character sometimes);
send one character into MCU UART_1;
see zephyr crash message in the communication application:

***** BUS FAULT *****
  Imprecise data bus error
***** Hardware exception *****
Current thread ID = 0x200005f0
Faulting instruction address = 0x80056d4
Fatal fault in ISR! Spinning...

Expected behavior
I expect to see zephyr UART_1 shell prompt in my communication application just after MCU reset.
Impact
showstopper. If main thread is not blocked but introduce just delay (e.g. USB CDC ACM initial activity) and UART_1 receives a character then I see the same crash on start.
Environment:

OS: Linux
Toolchain: Zephyr SDK 0.10.0
Zephyr git describe: zephyr-v1.14.0-712-g59eb48329e

I've been sitting on this patch for a little while, but I think it addresses the issue you are seeing.  Let me know if it helps.
From 78e8ec84f8040afef0e7b6a8caa57e5bdf156596 Mon Sep 17 00:00:00 2001
From: Bradley Bolen<EMAIL_ADDRESS>Date: Thu, 14 Feb 2019 11:28:37 -0500
Subject: [PATCH] shell: Move the call to uart_irq_rx_enable to the enable
callback
The uart could get an RX interrupt before the main shell init code has
finished initializing.  The race looks like:
shell.c                   shell_uart.c
shell_init()
->instance_init()
init()
->uart_irq_init()
->uart_irq_callback_user_data_set()
                      RX interrupt
                      uart_rx_handle()
                       ->sh_uart->ctrl_blk->handler

transport_evt_handler()
->k_poll_signal_raise()
->k_thread_create(shell_thread)
Unfortunately, the code that initializes the signals is not run until
the beginning of shell_thread.  But that comes after
k_poll_signal_raise() has alread been called.
subsys/shell/shell_uart.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/subsys/shell/shell_uart.c b/subsys/shell/shell_uart.c
index f9dba45..ce3333c 100644
--- a/subsys/shell/shell_uart.c
+++ b/subsys/shell/shell_uart.c
@@ -137,7 +137,6 @@ static void uart_irq_init(const struct shell_uart *sh_uart)
struct device *dev = sh_uart->ctrl_blk->dev;
uart_irq_callback_user_data_set(dev, uart_callback, (void *)sh_uart);

uart_irq_rx_enable(dev);
#endif
}

@@ -195,6 +194,10 @@ static int enable(const struct shell_transport *transport, bool blocking_tx)
#endif
}
+#ifdef CONFIG_SHELL_BACKEND_SERIAL_INTERRUPT_DRIVEN

uart_irq_rx_enable(sh_uart->ctrl_blk->dev);
+#endif
return 0;
}

--
2.7.4

@bbolen
I have just tested your patch on top of 59eb48329e. It works perfectly and solves my problem.
Thanks!

@bbolen Could you send a PR for this issue as you have a working solution?

fyi I've tried this patch on the latest repo and it breaks cdc_acm shell comms. If I put the rx irq enable back where it was then cdc_acm shell works again. The symptom is that outgoing messages will appear in the terminal but no incoming traffic is seen by the shell.


Release/4.58.2

          2 Errors

:no_entry_sign:
Please, follow the PR template to better document your changes.

:no_entry_sign:
The PR title should follow the title convetion: (Added,Changed,Deprecated,Removed,Fixed,Security)[JIRA-XXX] - (brief description here)

          1 Warning

:warning:
Big PR, consider splitting into smaller ones.

          1 Message

:book:
This PR does not include any JIRA tasks in the title. (e.g. [TICKET-1234])

Current coverage for MercadoPagoSDKV4.framework is 4.05%
✅ No files affecting coverage found

Powered by xcov

  Generated by :no_entry_sign: Danger


Interoperability On Taiko Mainnet Moving Forward

Title of your project
Add Interoperability Protocols To Taiko
Short (1-2 sentence) description of your project
Wormhole Integration on Taiko
Link to your project
https://wormhole.com/
Live on Testnet
No
If your project is live on one of Taiko's testnets, please provide evidence of that here (eg. links, screenshots). If your project is NOT live, please provide your plan for integration here.
Interoperability Protocols Play A Crucial Role In Enabling Communication & Interaction Between Different Systems, Software Applications & Technologies.
Upload a quality logo to your project
No response

Please read the template again and fill it out completely, otherwise this will be treated as spam.

Okay Then


Feature Request - Add support for different published vs listener URL and port

What happened:
In our environment an achore service might get exposed to clients at https://anchore-apiext.fqdn but internally the application is configured to listen on http://anchore-apiext:8080.
What did you expect to happen:
When using external_tls: true in the config.yaml I also need the services published URL in postgres to reflect https://anchore-apiext.fqdn not http://anchore-apiext:8080 as the external services cannot connect directly to http://anchore-apiext:8080.
What docker images are you using:
anchore/anchore-engine:dev 85d781a75749
How to reproduce the issue:
Create a configuration with following config.yaml
services:
  apiext:
    enabled: True
    require_auth: True
    endpoint_hostname: '${ANCHORE_APIEXT_HOSTNAME}'
    listen: '<IP_ADDRESS>'
    port: '8228'
    external_tls: true

Note the published endpoint in the database is https://anchore-apiext:8228.
Anything else we need to know:
Ideally I need something like;
Create a configuration with following config.yaml
services:
  apiext:
    enabled: True
    require_auth: True
    endpoint_hostname: '${ANCHORE_APIEXT_HOSTNAME}'
    listen: '<IP_ADDRESS>'
    port: '8228'
    external_tls: true
    external_port: 443

I believe this feature will make a good addition for the next release (0.2.2) to round out the 'external_tls' option.  We'll track the progress here!


Add refresh method to CryptographyClient

It should reset the client's state such that the key and permissions are retrieved again as appropriate.

We decided not to add this to the API because it introduces a versioning pitfall:
encrypted_thing = client.encrypt(...)

# then someone creates a new version of the key

client.refresh() # client gets the new key

# round-trip fails because client no longer holds the first key
client.decrypt(encrypted_thing)


QUESTION: Is it possible to use SCAN and/or scanStream in Redis Cluster?

Hi,
is it possible to use scan and/or scanStream in redis cluster?
And if it's possible, the scan command will scan all redis nodes?
Thanks

Hi @Pistacchione ,
I faced the same problem few days ago.
To the best of my knowledge, the SCAN operation iterates over all keys on a single Redis node.
Take a look at #175 or https://paluch.biz/blog/162-iterate-over-all-keys-in-a-redis-cluster.html.
Hope it helps.
Roberto

HI,
How to query keys from redis.cluster by using specific pattern (using scanStream).
Please do needful.
Thanks,
Swetha

Hi guys, we should open this issue. I cannot get all keys with patterns in all nodes.


Adding etharscan.io into blacklist

https://twitter.com/etherscan/status/972055165074198528

https://urlscan.io/result/11a9b505-13d4-4cbb-8626-6dbac6b3e427#summary


How update_info_plist update Bunder Identifier

Hi team:
I have a .plist like below:
    update_info_plist(
      xcodeproj: PROJECT,
      plist_path: INFO,
      block: lambda { |plist|
        plist[:CFBundleDisplayName] = 'The Name I Want to Change'
        plist[:CFBundleIdentifier] = 'The Bunder Id I want to change'
        plist["CFBundleURLTypes"]???[:CFBundleURLSchemes] = 'The Bunder Id I want to change'
      }
    )

How can I change CFBundleURLSchemes's value?
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>CFBundleDisplayName</key>
	<string>AAAAAAAAAAAAA</string>
	<key>CFBundleIdentifier</key>
	<string>$(PRODUCT_BUNDLE_IDENTIFIER)</string>
	<key>CFBundleURLTypes</key>
	<array>
		<dict>
			<key>CFBundleURLSchemes</key>
			<array>
				<string>$(PRODUCT_BUNDLE_IDENTIFIER)</string>
			</array>
		</dict>
	</array>
</dict>
</plist>

I can't quite confirm that on the real plist, but it seems like you are looking for that:
plist["CFBundleURLTypes"].first["CFBundleURLSchemes"] = ['The Bunder Id I want to change']

plist = {"CFBundleURLTypes" => [{"CFBundleURLSchemes" => ["$(PRODUCT_BUNDLE_IDENTIFIER)"]}]}
=> {"CFBundleURLTypes"=>[{"CFBundleURLSchemes"=>["$(PRODUCT_BUNDLE_IDENTIFIER)"]}]}

plist["CFBundleURLTypes"].first["CFBundleURLSchemes"] = ['The Bunder Id I want to change']
=> ["The Bunder Id I want to change"]

plist
=> {"CFBundleURLTypes"=>[{"CFBundleURLSchemes"=>["The Bunder Id I want to change"]}]}


Table grid responsive heading css

Seeing this today after experimenting again w/ the vanilla responsive table... thanks @mcoker for helping resolve... we should possibly remove that width specifier?

Looks like this is due to improperly scoped expandable table styles...
https://github.com/patternfly/patternfly-next/blob/master/src/patternfly/components/Table/table.scss#L221-L240

cc @rhamilto

Closing, this ended up being an issue w/ downstream style overrides applied. Updated this in the PR notes of 2014.


Provide custom explorer contents for TDBMemory

New display - old display:

Rejected because this solution would suggest the existence of fictive dictionaries in the data structure.


Updated deps and removed deleted bits

Fixes #

Proposed Changes

Updating to latest eventing, and getting rid of delted test image "heartbeats", using actual instead.

Release Note

Docs

/retest


changing the props 'width' can't change qrcode size

It sees that the props change the qrcode not rerender~~

umm~~it seems that u just watch the props 'value',  which makes no effects to the others props


Fix downloading of the specific version

Because the format of the package URL has changed, Downloader cannot find package and return 404.
Description
Downloader now checks all existing packages, sort them in descendant order (from newest to oldest) and selects URL for the platform from archives element of the package.
Related Issue
https://github.com/cake-contrib/Cake.Android.SdkManager/issues/8
Motivation and Context
Unable to download specific version of the SDK manager.
How Has This Been Tested?
New test case has been added.
Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] My code follows the code style of this project.
~My change requires a change to the documentation.~
~I have updated the documentation accordingly.~
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

No reaction. Closing.


#756 SWAG syncing.

Addresses #756, adds a new command line option that allows syncing account metadata between swag and security monkey. Marks accounts with security_monkey enabled as an 'active' account in security_monkey's database.

Coverage decreased (-0.05%) to 68.784% when pulling 4341d04afe1c5de8795a616379f5f97d6d50349d on kevgliss:756-swag-sync into ef4847e2fd308a7e478feb90ff67856806de5bac on Netflix:develop.


WIP Add repro for https://github.com/containerd/containerd/issues/10589

WIP: for repro in https://github.com/containerd/containerd/pull/10603
cc @ningmingxiao @laurazard @samuelkarp

I still can't repro 😅  I wonder why that is.
[...]
    issue10589_linux_test.go:105: Wait for container a50f8afa4ea8f1dac37f31d1cb2a6d4505eaffd9248cd22d3f09b6db1293d2cb status to become exited
    issue10589_linux_test.go:117: Completed running TestIssue10589 iteration 9
--- PASS: TestIssue10589 (15.75s)
PASS

full log

/ok-to-test

I still can't repro 😅 I wonder why that is.
[...]
    issue10589_linux_test.go:105: Wait for container a50f8afa4ea8f1dac37f31d1cb2a6d4505eaffd9248cd22d3f09b6db1293d2cb status to become exited
    issue10589_linux_test.go:117: Completed running TestIssue10589 iteration 9
--- PASS: TestIssue10589 (15.75s)
PASS

full log

Yes, doesn't appear to be repro easily in the CI jobs unfortunately. However, I was able to repro after a few times on my dev workstation by running it a few times.

I guess it's either too fast/slow/not the exact conditions necessary for this to reproduce. Regardless, it's better to have something than not.

On my workstation:
porterdavid@ubuntu-dev-1:~/containerd$ sudo crictl ps
CONTAINER           IMAGE                             CREATED             STATE               NAME                     ATTEMPT             POD ID              POD
4f06a04aec427       ghcr.io/containerd/busybox:1.36   57 seconds ago      Running             test-container-10589-0   0                   33021914f5594       unknown

root      220922  3.4  0.0 1242780 23248 pts/3   Sl   23:10   0:03 /usr/local/bin/containerd-shim-runc-v2 -namespace k8s.io -id 33021914f5594d64cc6482aaaefe69905b2db8d3fa00d85e16e0f95d3835424e -address /run/containerd/containerd.sock -debug
65535     220941  0.0  0.0   1020   512 ?        Ss   23:10   0:00  \_ /pause

Test log: https://gist.github.com/bobbypage/bfc64fbbc946c951cf2bd3e286e322ec
  issue10589_linux_test.go:106:
        	Error Trace:	/home/porterdavid/containerd/integration/issue10589_linux_test.go:106
        	Error:      	Received unexpected error:
        	            	timeout exceeded
        	Test:       	TestIssue10589
E0820 23:11:54.250068  220818 remote_runtime.go:159] StopPodSandbox "33021914f5594d64cc6482aaaefe69905b2db8d3fa00d85e16e0f95d3835424e" from runtime service failed: rpc error: code = DeadlineExceeded desc = failed to stop container "4f06a04aec427acdb360643d5000dbe78647c1a30d89f5f0ac481fcafb42f138": an error occurs during waiting for container "4f06a04aec427acdb360643d5000dbe78647c1a30d89f5f0ac481fcafb42f138" to be killed: wait container "4f06a04aec427acdb360643d5000dbe78647c1a30d89f5f0ac481fcafb42f138": context deadline exceeded
    main_test.go:255:
        	Error Trace:	/home/porterdavid/containerd/integration/main_test.go:255
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/testing/testing.go:1176
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/testing/testing.go:1354
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/testing/testing.go:1684
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/runtime/panic.go:629
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/testing/testing.go:1006
        	            				/home/porterdavid/containerd/integration/issue10589_linux_test.go:106
        	Error:      	Received unexpected error:
        	            	rpc error: code = DeadlineExceeded desc = failed to stop container "4f06a04aec427acdb360643d5000dbe78647c1a30d89f5f0ac481fcafb42f138": an error occurs during waiting for container "4f06a04aec427acdb360643d5000dbe78647c1a30d89f5f0ac481fcafb42f138" to be killed: wait container "4f06a04aec427acdb360643d5000dbe78647c1a30d89f5f0ac481fcafb42f138": context deadline exceeded
        	Test:       	TestIssue10589
E0820 23:12:54.251139  220818 remote_runtime.go:179] RemovePodSandbox "33021914f5594d64cc6482aaaefe69905b2db8d3fa00d85e16e0f95d3835424e" from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
    main_test.go:256:
        	Error Trace:	/home/porterdavid/containerd/integration/main_test.go:256
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/testing/testing.go:1176
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/testing/testing.go:1354
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/testing/testing.go:1684
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/runtime/panic.go:629
        	            				/home/porterdavid/.gimme/versions/go1.23.0.linux.amd64/src/testing/testing.go:1006
        	            				/home/porterdavid/containerd/integration/issue10589_linux_test.go:106
        	Error:      	Received unexpected error:
        	            	rpc error: code = DeadlineExceeded desc = context deadline exceeded
        	Test:       	TestIssue10589
--- FAIL: TestIssue10589 (151.99s)
FAIL
FAIL	github.com/containerd/containerd/v2/integration	152.011s
FAIL

ah actually, looking at https://github.com/containerd/containerd/actions/runs/10480313036/job/29027785178?pr=10620, I see the test failed as well:
2024-08-20T23:03:56.7266799Z     issue10589_linux_test.go:105: Wait for container 654ee26e03399137d4ef6ce5dd603c9b52d49f0e165e4a3d3bce6abbce8afee2 status to become exited
2024-08-20T23:04:26.7407469Z     issue10589_linux_test.go:106:
2024-08-20T23:04:26.7409378Z         	Error Trace:	/home/runner/work/containerd/containerd/integration/issue10589_linux_test.go:106
2024-08-20T23:04:26.7410662Z         	Error:      	Received unexpected error:
2024-08-20T23:04:26.7412285Z         	            	timeout exceeded
2024-08-20T23:04:26.7413182Z         	Test:       	TestIssue10589
2024-08-20T23:05:26.7423588Z E0820 23:05:26.741869   77689 remote_runtime.go:159] StopPodSandbox "4e3ee5c84275575a39a6c2fde6f12ac9c9189545e1218e773487bd29824cb10e" from runtime service failed: rpc error: code = DeadlineExceeded desc = failed to stop container "654ee26e03399137d4ef6ce5dd603c9b52d49f0e165e4a3d3bce6abbce8afee2": an error occurs during waiting for container "654ee26e03399137d4ef6ce5dd603c9b52d49f0e165e4a3d3bce6abbce8afee2" to be killed: wait container "654ee26e03399137d4ef6ce5dd603c9b52d49f0e165e4a3d3bce6abbce8afee2": context deadline exceeded
2024-08-20T23:05:26.7428074Z     main_test.go:255:
2024-08-20T23:05:26.7429206Z         	Error Trace:	/home/runner/work/containerd/containerd/integration/main_test.go:255
2024-08-20T23:05:26.7431296Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/testing/testing.go:1176
2024-08-20T23:05:26.7432674Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/testing/testing.go:1354
2024-08-20T23:05:26.7433651Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/testing/testing.go:1684
2024-08-20T23:05:26.7434590Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/runtime/panic.go:629
2024-08-20T23:05:26.7435906Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/testing/testing.go:1006
2024-08-20T23:05:26.7437105Z         	            				/home/runner/work/containerd/containerd/integration/issue10589_linux_test.go:106
2024-08-20T23:05:26.7437778Z         	Error:      	Received unexpected error:
2024-08-20T23:05:26.7440979Z         	            	rpc error: code = DeadlineExceeded desc = failed to stop container "654ee26e03399137d4ef6ce5dd603c9b52d49f0e165e4a3d3bce6abbce8afee2": an error occurs during waiting for container "654ee26e03399137d4ef6ce5dd603c9b52d49f0e165e4a3d3bce6abbce8afee2" to be killed: wait container "654ee26e03399137d4ef6ce5dd603c9b52d49f0e165e4a3d3bce6abbce8afee2": context deadline exceeded
2024-08-20T23:05:26.7442698Z         	Test:       	TestIssue10589
2024-08-20T23:06:26.7427148Z E0820 23:06:26.742158   77689 remote_runtime.go:179] RemovePodSandbox "4e3ee5c84275575a39a6c2fde6f12ac9c9189545e1218e773487bd29824cb10e" from runtime service failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
2024-08-20T23:06:26.7429259Z     main_test.go:256:
2024-08-20T23:06:26.7434218Z         	Error Trace:	/home/runner/work/containerd/containerd/integration/main_test.go:256
2024-08-20T23:06:26.7436327Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/testing/testing.go:1176
2024-08-20T23:06:26.7437469Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/testing/testing.go:1354
2024-08-20T23:06:26.7438751Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/testing/testing.go:1684
2024-08-20T23:06:26.7440475Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/runtime/panic.go:629
2024-08-20T23:06:26.7441689Z         	            				/opt/hostedtoolcache/go/1.23.0/x64/src/testing/testing.go:1006
2024-08-20T23:06:26.7443259Z         	            				/home/runner/work/containerd/containerd/integration/issue10589_linux_test.go:106
2024-08-20T23:06:26.7444280Z         	Error:      	Received unexpected error:
2024-08-20T23:06:26.7445903Z         	            	rpc error: code = DeadlineExceeded desc = context deadline exceeded
2024-08-20T23:06:26.7446997Z         	Test:       	TestIssue10589
2024-08-20T23:06:28.4281337Z --- FAIL: TestIssue10589 (169.28s)

(but for some reason the github action succeeded?)


Making boundary changeable

I've got a project where I need be able to change a boundary. Is there a reason to prohibit that ?

The reason it is not exposed is that we didn't think there should ever be a need to specify your own value. The current implementation follows the RFC specs which are a bit vague. Could you shed some more light on what the server is doing so we can better understand the use case? Opening this up is something I'd rather avoid unless there is a valid reason to do so.

Hi @FrankJaeger, I'm going to close this PR for now. If you end up posting a valid case for making this change, I may re-open and merge. Cheers.


Document --coverage-ignore-choice

shouldn't this also target 2.8?

Is this ready for review by daml-docs now? (I had started a review but then you applied more wording improvements -- which is great! -- so just making sure you're done with that sort of thing.)

I'm done now - sorry, I was worried this would happen :P

I'm done now - sorry, I was worried this would happen :P

No problem! Feel free to make more changes -- I won't get to this until a bit later today anyway

Rebased on https://github.com/digital-asset/docs.daml.com/pull/469.


[BUG] Additional management v3 cluster created after upgrade

Description:
Additional management v3 cluster created after upgrade, resulting in failed sequential v3 auto-migration.
What steps did you take and what happened?

Install turtles v0.8.0 (v3 option disabled) and import CAPI cluster

Upgrade turtles to latest dev version by keeping settings to default (v3 is auto-enabled to true)

An additional v3 cluster is created and corresponding v1 cluster

$ kubectl get cluster.provisioning.cattle.io -A
NAMESPACE       NAME            READY   KUBECONFIG
default         cluster1-capi   true    cluster1-capi-kubeconfig
fleet-default   c-7q8g7
fleet-local     local           true    local-kubeconfig

$ kubectl get cluster.management.cattle.io -A
NAME           AGE
c-7q8g7        92s
c-m-6tl52brj   7m6s
local          16m

Update turtles settings and set managementv3-cluster-migration to true and let the operation complete.
The migrated cluster is Unavailable in Rancher.

$ kubectl get cluster.management.cattle.io -A
NAME      AGE
c-7q8g7   6m20s
local     20m

$ kubectl get cluster.provisioning.cattle.io -A
NAMESPACE       NAME      READY   KUBECONFIG
fleet-default   c-7q8g7   true    c-7q8g7-kubeconfig
fleet-local     local     true    local-kubeconfig

What did you expect to happen?
No additional cluster creation after upgrade from v0.8.0
How to reproduce it?
Steps mentioned above.
Rancher Turtles version
Dev version - d7ecf2b
Rancher - v2.8-head
Anything else you would like to add?
While upgrade from v0.8.0 if both managementv3-cluster, managementv3-cluster-migration = true, then migration completes successfully.
Label(s) to be applied
/kind bug

@cpinjani can you please try the latest version of Turtles and see if this is still the case?

Validated on v0.9.0, the issue is not occurring. Filed a separate issue for failure on Step 4 (https://github.com/rancher/turtles/issues/588)
Cluster details after upgrade:
$ kubectl get cluster.provisioning.cattle.io -A
NAMESPACE     NAME            READY   KUBECONFIG
default       cluster1-capi   true    cluster1-capi-kubeconfig
fleet-local   local           true    local-kubeconfig

$ kubectl get cluster.management.cattle.io -A
NAME           AGE
c-m-2j2gwvd4   14m
local          27m

@cpinjani I am closing this, steps 1-3 are not issue anymore after upgrading to the new release v0.9.0 and only Step 4 was, but that has a separate issue: #588
Please re-open if you face the same issue again in the future.
/close


Preservation modes

Our preservation modes do not exactly match the PBDB choices for their collection entry. How shall we handle this? Do I remember correctly that this is a node?
PBot has: charcoalification, compression, impression, mold/cast, other, permineralization, unaltered remains, unknown
PBDB has: body, trace, permineralized, cast, mold/impression, adpression/compression, soft parts, recrystallized, concretion, dissolution traces, charcoalification, coalified.
I think it is fine to have a subset of the PBDB values, as things like "soft parts" don't really make sense for plants. the main problems I see:

we have choices PBDB does not, and this is a required PBDB field.
we lumped molds & casts, whereas PBDB has cast as an option and lumped mold & impression.

Yes, you should pick an exact subset of pbdb choices
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ellen Currano @.>
Sent: Wednesday, July 12, 2023 2:15:18 PM
To: paleobot/pbot-dev @.>
Cc: Zaffos, Andrew - (azaffos) @.>; Assign @.>
Subject: [EXT][paleobot/pbot-dev] Preservation modes (Issue #147)
External Email
Our preservation modes do not exactly match the PBDB choices for their collection entry. How shall we handle this? Do I remember correctly that this is a node?
PBot has: charcoalification, compression, impression, mold/cast, other, permineralization, unaltered remains, unknown
PBDB has: body, trace, permineralized, cast, mold/impression, adpression/compression, soft parts, recrystallized, concretion, dissolution traces, charcoalification, coalified.
I think it is fine to have a subset of the PBDB values, as things like "soft parts" don't really make sense for plants. the main problems I see:

we have choices PBDB does not, and this is a required PBDB field.
we lumped molds & casts, whereas PBDB has cast as an option and lumped mold & impression.

—
Reply to this email directly, view it on GitHubhttps://github.com/paleobot/pbot-dev/issues/147, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACPQSQ7CBV3XIITGBXDIHA3XP4HWNANCNFSM6AAAAAA2IBHHKM.
You are receiving this because you were assigned.Message ID: @.***>

To clarify.
What Dori said makes sense to me. Use whatever the PBOT team wants for specimens, but make the options for collections consistent with PBDB as she described.
RE: the question about why it exists for both collections and specimens – the short answer is simply for legacy compatibility reasons.
From: doricon @.>
Date: Thursday, July 13, 2023 at 9:35 AM
To: paleobot/pbot-dev @.>
Cc: Zaffos, Andrew - (azaffos) @.>, Assign @.>
Subject: [EXT]Re: [paleobot/pbot-dev] Preservation modes (Issue #147)
External Email
I would like to keep our current PBot options for the specimen node's Preservation field. This is just internal PBot info and doesn't pipe over to PBDB.
For the PBDB field list on collections: I think the following subset should suffice: trace, permineralized, cast, mold/impression, adpression/compression, recrystallized, concretion, charcoalification, coalified
(i don't know how soft parts, body, or dissolution traces would relate to plants - so those are the ones I would nix)
I totally understand if other folks don't want two different lists on different nodes, in which case we will have to standardise to the PBDB version. I don't like their groupings, but also don't have strong sentiment either way! :)
—
Reply to this email directly, view it on GitHubhttps://github.com/paleobot/pbot-dev/issues/147#issuecomment-1634551739, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACPQSQ6GWRXCNXFYAPRGVDDXQAPTPANCNFSM6AAAAAA2IBHHKM.
You are receiving this because you were assigned.Message ID: @.***>

Can we consider asking Mark if they would be willing to add our new/additional types to PBDB as options?

Either way this is too complex to be handled before hackathon.

For the Hack-a-Thon we do need to match the collection node preservation modes to PBDB's. Here is the subset of PBDB entries that we would like to include:
Body
Trace
Permineralized
Cast
Mold/impression
Adpression/compression
Recrystallized
Concretion
Charcoalification
Coalified
@doricon : I left Body since otherwise I wasn't necessarily sure where to put pollen. You can select multiple, so really someone could select body and many of the choices below. Botany team needs to come up with definitions of charcoalification vs. coalified for the cheat sheet.

We have agreed to go with this final list for both specimen and collection.

This is in 2062b7f33d73f9104699c60445aab62849f783dd


Role command

Feature Overview & Customer Need
As a  Conjur user
I would like to use the Conjur cli
In order to understand which roles are members of a specific role
A new command will be called role
We will use 1 sub command

list-members     - Lists all direct members of the role. The membership list is not recursively expanded.

For example
conjur role list-members -i demo:policy:server <- returns array of roles
[ ...]
Out of scope

memberships - Lists role memberships. The role membership list is recursively expanded.

The commands will be used as follow:
TBD
Args description:
-i --id  - provide the role identifier
Expected behavior should not change from the corresponding command in Ruby CLI
@sharonr78 should provide the right help screen
Help is according to https://ljfz3b.axshare.com/#id=s9nycf&p=conjur_help__policy&g=1
Quality
Make sure we have test coverage of the role command.  Create test plan and execute accordingly.
Process logic and Demo
Conjur user with a machine that the Python CLI already been installed and conjur init & login run against a Conjur/ Conjur Enterprise machine with the following:
Given the following roles when performing 'conjur list'
[
"MyAccount:policy:root",
"MyAccount:user:alice",
"MyAccount:user:bob",
"MyAccount:group:conjur-root-admins",
"MyAccount:group:ops-admin",
"MyAccount:host:www-01",
"MyAccount:layer:app-layer",
"MyAccount:host:bob_machine"
]
If the user performs
conjur role list-members -i MyAccount:group:conjur-root-admins
[
"MyAccount:user:admin",
"MyAccount:user:alice"
]
Demo each option that was implemented
Show that the role has members
Delete a role by using !delete in a policy
Show that the option of running members is failing.
User messages
All user messages regarding resource actions should be reviewed
Especially error messages
if an argument is missing we need to return the help of the command
Documentation
Please provide enhance documentation in online help and readme
DOD

[ ] Implement the role's commands Conjur Python CLI in all 3 platforms
[ ] Demo the flow described above
[ ] Automatic integration tests written according to a test plan and passed successfully
[ ] Fill in the user messages - link to a page with all user messages for CLI saved and reviewed.
[ ] Fill in the logs and place here a link to the logs files - link to a page with all logs for CLI saved and reviewed.
[ ] Logs were reviewed by TW and PO
[ ] Are there new Audits to this feature? If so please document them and provide here a link (N/A)

Hi @InbalZilberman
Regarding the subcommands:

exists - Determines whether a role exists - why shouldn't we call the subcommand validate?  all our subcommands are actually verbs, and "exists" is not.
members - Lists all direct members of the role - should also be changed to a verb. We can use list.
The flag -r, --role should also be changed to -i, --id like we use in variable, host or user for identification.

The syntax would then be:
conjur role validate -i demo:policy:server
conjur role list -i demo:policy:server
I don't think we need the quotes, unless there's a technical limitation here.
WDYT?

@InbalZilberman

Why list membership is out of scope?
added this under the logic section:
given the following roles when performing 'conjur list'
[
"MyAccount:policy:root",
"MyAccount:user:alice",
"MyAccount:user:bob",
"MyAccount:group:conjur-root-admins",
"MyAccount:group:ops-admin",
"MyAccount:host:www-01",
"MyAccount:layer:app-layer",
"MyAccount:host:bob_machine"
]
If the user performs
conjur role exists -i MyAccount:group:conjur-root-admins
true
conjur role members -i MyAccount:user:conjur-root-admins
false
conjur role members -i MyAccount:group:conjur-root-admins
[
"MyAccount:user:admin",
"MyAccount:user:alice"
]
conjur role membership -i MyAccount:group:conjur-root-admins
[
"MyAccount:host:sapirs_machine",
"MyAccount:group:conjur-root-admins"
]

@szamir1 Thanks! Ill add this to the logic!
membership is out of scope as in the customer research we conducted it seems that it is not used.

@sharonr78 exists is a verb. Validate does not have the same meaning as exist... Maybe we can consult TW here.
@sharonr78 we cant use simply list how about members list? it does become a bit long
conjur role members list -i demo:policy:server
3 I agree thanks! changed
quotes should be supported for all cases as I believe there are special chars that will require this.

@InbalZilberman How about:

role check -i ... or role verify -i ...? since we're checking/querying/verifying whether that role exists. The true/false response still works here.
role list-members -i ...
I'm trying to find a verb that will be a clear sub-command after role.

Does DavidP need an invite to this repo?

Same as in issue https://github.com/cyberark/conjur-api-python3/issues/215
list-members fine
i think exists provide better readability and is a verb

I suggest we consult @pdavid2 or @shulifink in this matter.
David/Shuli, we would like to have a subcommand for the commands "Role" and "Resource" which determines whether a role exists or not (so the output would no True/False).
Since a subcommand should also be a verb (and I think it should be the infinitive form), should we use "exist" or "exists" or maybe a different word to represent this action.
For instance:
conjur role exists -i "demo:policy:server" (where -i is the role's identifier)

The membership list is not recursively expanded

But in the Ruby CLI it is. Why has this changed?
@InbalZilberman

@InbalZilberman I am not really understanding the significance of exists because the user can just run conjur list and see that the resource there

for list-members will we support flags (limit, count, etc)? See REST here https://docs.conjur.org/Latest/en/Content/Developer/Conjur_API_List_Role_Members.htm?tocpath=Developer|REST APIs|_____16

I think the language is very confusing. Are we listing the entities associated with groupings? For example, if the group mygroup, there are two entities sigal and inbal?

for list-members will we support flags (limit, count, etc)? See REST here https://docs.conjur.org/Latest/en/Content/Developer/Conjur_API_List_Role_Members.htm?tocpath=Developer|REST APIs|_____16

No

I think the language is very confusing. Are we listing the entities associated with groupings? For example, if the group mygroup, there are two entities sigal and inbal? or are we talking about ownership? as in mygroup owns sigal and inbal? could very well be both but it should be explicit and clear

I will go over the language with @shulifink  and make sure it is fixed in help and in our documentation

@InbalZilberman I am not really understanding the significance of exists because the user can just run conjur list and see that the resource there
also for your examples, it is enough to provide resource: so policy:server

Thank you for challenging! We decided to remove the exists option


Add configuration for XLNet-Base

The XLNet authors have just released a new pre-trained model checkpoint named XLNet-Base, Cased (https://github.com/zihangdai/xlnet#released-models). We should add support for this checkpoint.

Thank you for the information. I think our current code structure should automatically support this checkpoint.

@gpengzhi It's not just the checkpoint, but also the configs. We'll need to convert the config JSON file into Texar XLNet hparams, and currently we don't have such functionality.

We could also take this chance to change everything to batch-first (now XLNet models use the 2nd dimension as the batch dimension). It would be nice to have a unified interface with the rest of the toolkit.

Yes, we are building XLNet modules following a similar way of Bert/GPT2 modules. It will take care of both the checkpoint and the JSON file. @huzecong

@AvinashBukkittu FYI, please change everything to batch-first as well in texar-tensorflow.


Set Kotlin module name to fix library conflict

By default, the Kotlin compiler creates a kotlin_module file with the name of the Gradle module. The resulting name is "library_release.kotlin_module" for this library, which conflicts with other libraries that also use the default generic "library" name. This causes builds to fail when multiple such libraries are used in the same project:
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > More than one file was found with OS independent path 'META-INF/library_release.kotlin_module'.

Set a unique Kotlin module name to fix the issue.

Thanks!


Feature/updated ai logic & bot helpers

@thoughtmanifest I know you were talking about adding functions that will make writing bots a bit easier. I added a bot-helpers namespace with a few that I'm planning on using for the AI bots. If you get a few mins I'd like to get you opinion on them.

I'll try to take a look at this tomorrow night.  I've got plans tonight.  One thing I immediately notice is the naming of the file.  Consider using directories and namespaces to help with organizing code.  For instance, consider a bot directory in the game directory.  Then in the bot directory there would be a helpers.clj so the namespace would be ...game.bot.helpers.  This same could be applied to decisions.  bot-decisions.clj could be renamed to decisions.clj  Does that make sense?

Yeah it does. I'll see if I get those changes in. Thanks!

Another note based on looking a little closer, is the use of atoms, especially with reduce.  There should be a compelling reason to maintain state that I don't think is present in the bot helpers code.  Generally, you'd reach for an atom when dealing with concurrency or parallelism, not when traversing a collection as is done in those fns.  I'll try to present a better way to do what you're doing if I get a chance to work on this tonight, but I wanted to note it here as food for thought.

Yeah that didn't feel quite right. I could update the outer reduce to include counter and then just return the coords when it resolves. ?

So I refactored it to use loop. get-items-coords is now far more performant since will bail it finds a match. Let me know what you think.

I like the change to loop.  I was also toying with a reduce version and a non-looping version of the sort-arena function.  Take a look:
(defn- arena-by
  ([arena]
   (arena-by arena :type "none"))

  ([arena akey default]
   (apply concat
          (map-indexed
           #(map-indexed
             (fn [idx itm]
               (let [coords [idx %1]]
                 [(keyword (or (get itm akey) default)) (assoc itm :coords coords)]))
             %2)
           arena))))

(defn sort-arena2
  [arena]
  (reduce (fn [m [k v]]
            (update-in m [k] (fnil conj []) v))
          {}
          (arena-by arena)))

(defn- arena-by2
  ([arena]
   (arena-by2 arena :type "none"))

  ([arena akey default]
   (apply concat
          (map-indexed
           #(map-indexed
             (fn [idx itm]
               (let [coords [idx %1]]
                 {(keyword (or (get itm akey) default)) [(assoc itm :coords coords)]}))
             %2)
           arena))))

(defn sort-arena3
  [arena]
  (apply merge-with into (arena-by2 arena)))

What do you think?  It returns everything but the match key, but that could be easily added. I'm  wondering though, what the motivation is for the final data structure. How do you expect it to be used?

Oh I really like just adding the coords prop to the item instead of along side it. As for the decision on the data structure, I believe the return of sort-arena gives players a really easy way to evaluate their current environment (and probably even more so with within-n-spaces which operates on a sorted arena).  The plan for bot.helpers is to make it publicly accessible to anyone writing bots, (it is also in use for some of the ai logic).
I'm liking the second sort method  that uses arena-by2 a lot.  Which one are you leaning towards? I'm going to see if I can get that plugged in and update the coords in the other functions. Any thoughts, ideas, or additional helper functions would be much appreciated.

Okay, I think that's pretty much what we were doing in the other bot code, looking around us, grabbing the interesting things and picking one of them at random to move towards. I do like the arena-by2 more as well.  So deliciously dense =)
One other note, I think we should change the type values to keywords.  That will simplify not just this code, but I think it's more clojurey to represent those values which don't have to be strings as keywords. Also, could be handy since you can use keywords as functions to maps in clojure. And if necessary, at the edges of the api you can call (name type) and get the string version.

Yeah I had that thought as well (changing types to keywords). I think I want that in a separate PR however so this one doesn't bloat too much. I added https://github.com/willowtreeapps/battlebots/issues/73 to track it.

Plug and play! Love it when you can confidently swap out code with tests to back you up. I went with the second arena sort method, let me know if you see anything else.


Use variable names "degree" and "strength" consistently (Refactoring)

Currently I have been using variable names "degree" or "strength" both for how many factors whose all possible combinations of levels to be covered covered in a test suite, but there is no policy.
Maybe I should always use "strength" since I haven't seen the usage of "degree" as much as the other's.

This was done in 0.8.x development and only 'strength' is used now. This will not be fixed in earlier versions.


add discriminator property support

This more fully fixes https://github.com/openapi-generators/openapi-python-client/issues/219, and supersedes https://github.com/openapi-generators/openapi-python-client/pull/717.
Any valid discriminator definition as described in OpenAPI 3.1.0 should work correctly with these changes, including:

Discriminators with a mapping that specifies all valid discriminator values.
Discriminators with no mapping, in which the discriminator value for each type is the simple name of the type (equivalent to {"Model1": {"$ref": "#/components/schemas/Model1"}}).
Discriminators with a mapping that specifies values for some classes, but not all of them; in this case the default for the unspecified classes is the same as if there was no mapping.
Unions of unions where each of the sub-unions has its own discriminator mapping.

Validation during parsing is not as thorough as it could be: see the code comment in _validate_discriminators (I do have some further changes in mind to improve this, but I wanted to keep the scope of this PR manageable). But there is a fair amount of validation... so this is a breaking change in the sense that generation will now fail on some invalid specs that previously would have passed.
Also, I've added a new category of tests within the end-to-end tests: importing classes from the actual generated code and testing whether they work. Specifically, for this PR there's a test of whether the ModelWithDiscriminatedUnion class behaves correctly for various inputs. I verified that this test fails as expected if you don't have the union_property.py.jinja template changes: without those changes, it would always deserialize the field as ADiscriminatedUnionType1 regardless of the modelType value (because the two types in the union don't have any mutually exclusive validation rules).

Here's a case where I'm not 100% sure what the behavior should be:
components:
  schemas:
    ModelA:
      type: object
      properties:
        modelType:
          type: string
    ModelB:
      type: object
      properties:
        modelType:
          type: string
    NullType:
      type: null
    NullableUnionType:
      oneOf:
        - $ref: "#/components/schemas/ModelA"
        - $ref: "#/components/schemas/ModelB"
        - $ref: "#/components/schemas/NullType"
      discriminator:
        property: modelType

Should this be considered valid? In my current implementation, it is not valid, because that's my literal reading of this statement from the spec: "The expectation now is that a property with name [the discriminator property name] MUST be present in the response payload." If the value is null, then it does not have a modelType property.
However, like many things in OpenAPI, the spec language doesn't really say "if you do this, it's a malformed spec"; it's just a thing that would not have a well-defined behavior if you were writing a validator or a client generator. When someone raised a question about this scenario in the OpenAPI spec repo, the official answer was basically that. They just advised people that instead of writing their specs that way, to avoid ambiguity they should do it like this:
    NullableUnionType:
      oneOf:
        - $ref: "#/components/schemas/NullType"
        - oneOf:
            - $ref: "#/components/schemas/ModelA"
            - $ref: "#/components/schemas/ModelB"
          discriminator:
            property: modelType

My implementation does support that nested approach. What I'm wondering is whether it would make sense to loosen it so it also supports the questionably-valid shorter version, i.e. have a specific loophole for letting one of the variants be null, simply because I'm guessing it's not uncommon for people to write specs that way.
And if so, should it also allow an inline - type: null instead of a named NullType? The OpenAPI language says that "when using the discriminator, inline specs will not be considered"... but in this example, it arguably would not be "using" the discriminator in a case where the deserialization logic detected a None value and returned early.

Putting this back to draft because I have a couple ideas to simplify/clarify things.

OK, I pushed some more changes to simplify things a bit.
There was some extra validation that I could add in a follow-up PR, which I don't think is essential to the feature. I was also thinking about adding a new category of end-to-end tests that verify the behavior of the generated code (importing a generated model class and calling from_dict on it, etc.), but I could do that as a follow-up too and it's not specific to this feature.


fix(HMS-3593): Added unit test cases for instance type selection

This PR adds unit test cases to verify the filtering functionality of the application. The test cases cover different scenarios, including filtering with queries greater than, less than, equal to, and combinations.
Local execution results :
npm test -- --testNamePattern="filter with a query greater than|filter with a query less than|filter with a query combination|filter with a query equal"

Test Suites: 11 skipped, 1 passed, 1 of 12 total
Tests:       53 skipped, 4 passed, 57 total
Snapshots:   0 total
Time:        36.834 s
Ran all test suites with tests matching "filter with a query greater than|filter with a query less than|filter with a query combination|filter with a query equal".

Great work.


Heap out of bounds read - WASM_OP_I64_STORE16: wasm_interp_call_func_bytecode (wasm_interp.c:1234)

Environment

Questions
Answers

Related Binary
./iwasm (linux build)

Commit
commit 9a02c49d7c2bb2012fe8d2bd2b9cb2bdaf88ba79

Vulnerability/issue
Heap out of bounds read in wasm_interp_call_func_bytecode (wasm_interp.c:1234)
case: WASM_OP_I64_STORE16
Steps to reproduce the behavior

Download:
PoC.zip

Run:
./iwasm PoC.wasm

Fixed with c47baf221fa8139ee45cd31e7dbf1a8310669d8e


Differentiate "narrative" from "scenario"

Description of the issue
We already defined scenario: A scenario is an information content entity that contains statements about a possible future development based on a coherent and internally consistent set of assumptions and their motivation.
However, we also talk often about a narrative or a scenario narrative. These are not yet defined and the distinction to scenario is not clear.
Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

I would be fine with that. However, in yesterday's discussion I had the impression that you all meant something different than a scenario when talking about a narrative.

There were no further comments on this issues for months. Thus I will implement narrative and storyline as alternative terms to scenario.


[Bug]:

Version
29.6.2
Steps to reproduce
Steps to reproduce:

Clone https://github.com/patrickdawson/jestIsolateModulesAsyncBug.git
npm install
npm run test
Test shows the error

Expected behavior
In this testcase
 it('should have a fresh module state in each isolateModulesAsync context', async () => {
    await jest.isolateModulesAsync(async () => {
      const { getState, incState } = await import('../src/main.js');
      expect(getState()).toBe(0);
      incState();
      expect(getState()).toBe(1);
    });
    await jest.isolateModulesAsync(async () => {
      const { getState, incState } = await import('../src/main.js');
      expect(getState()).toBe(0);
      incState();
      expect(getState()).toBe(1);
    });
  });

I expect according to the docs https://jestjs.io/docs/jest-object#jestisolatemodulesasyncfn that each isolateModulesAsync context has its own 'fresh" module so all module variables should be in the intial state. The test shows that this is not the case
Actual behavior
The state of the previous isolateModulesAsync context affects the second scope.
Additional context
No response
Environment
System:
  OS: Windows 11 22H2 (Build 22621.1992)
  CPU: 12th Gen Intel(R) Core(TM) i9-12900K, 3200 MHz, 16 Core, 24 logical cores
Binaries:
  Node: 18.17.2
  npm: 9.6.7

It works with CJS, but fails with ESM modules. There is no need to have "type": "module" in package.json, enough to await import() an .mjs file. I guess this is because _isolatedEsmoduleRegistry is not yet implemented:
https://github.com/jestjs/jest/blob/0fd5b1c37555f485c56a6ad2d6b010a72204f9f6/packages/jest-runtime/src/index.ts#L181-L183

@patrickdawson Could you add a title to this issue, please? Something, like: "jest.isolateModulesAsync does not work with ESM modules".

Thanks for the quick follow up. I updated the title and the code example in the repository to verify that cjs indeed works. If this is not an easy fix maybe add a hint to the docs so it becomes clear that only cjs is supported at the moment.

@mrazauskas Can I pick up this？

Sure. Would be nice to fix this.


Default dwarfs missing profile argument

It looks like profile is required by Target but is not included in defaults.yaml
ValueError: ('One or more required properties are missing ', ['profile'])

It seems like this could be fixed by adding:
profile: {type: 'NFW'}
to each dwarf in defaults.yaml, but I'm not 100% sure this doesn't conflict with how the profiles is overwritten later on.

Bumping this again since I hit the problem in trying to update the dwarfs. I'm not sure if anyone knows the answer off-hand, so it may require a deep dive.

Bumping this again since I hit the problem in trying to update the dwarfs. I'm not sure if anyone knows the answer off-hand, so it may require a deep dive.


Fixes for issue raised in #161 - missing finished field

This is changes and new tests to add a finished field into OutgoingMessage to make it compatible with the other node modules - specifically on-finished which is used by send which is used by serve-static.

Squashed, cleaned up, and merged in https://github.com/molnarg/node-http2/commit/8d12b2950b8738e63e785c3f52408b6f2f6f1cae


Some Suggestions

1.目前项目的框架使用的是Winui2.7，未来有机会升级到Winui2.8或Windows App SDK 1.1.2吗？

Currently, the framework of the project uses Winui2.7. Is there any chance to upgrade to Winui2.8 or Windows App SDK 1.1.2 in the future?
2.上次我提交的语言列表信息是/Strings/zh-cn，希望您能够将这个文件夹重命名为/Strings/zh-Hans（适用于所有简体中文地区），谢谢。
The language list information I submitted last time was /Strings/zh-cn, please rename this folder to /Strings/zh-hans (applicable to all simplified Chinese regions), thank you.
希望下一次发布的时候打捆绑包（X86，X64）
Expect bundles for the next release (X86, X64)

Not sure, since WinUI 2.8 requires 17763+, whereas this app targets 15063+.
I'll do it.
Currently, it's impossible for me to target all four architectures (x86, x64, ARM, ARM64) in a bundle since the ARM64 has a different target version to the rest of them.

1.那这个版本未来就有可能面临抉择了，是选择更高的Winui版本，还是支持低版本系统了。

This version may face a choice in the future, whether to choose a higher version of Winui, or support a lower version of the system.
2.这个打捆绑包不是可以不选择所有的架构吗，去除掉ARM，ARM64也不是可以为X86，X64生成捆绑包的吗？
This bundle can not select all architecture, remove ARM, ARM64 can not generate bundles for X86, X64?

该安装包仅供我个人使用，不做任何其他用途。
This installation package is for my personal use only, not for any other purpose.

Bundling exclusively 2 architectures seem to be quite messy for me.

Bundling exclusively 2 architectures seem to be quite messy for me.

额。。。。。。
Er...

Not sure, since WinUI 2.8 requires 17763+, whereas this app targets 15063+.
I'll do it.
Currently, it's impossible for me to target all four architectures (x86, x64, ARM, ARM64) in a bundle since the ARM64 has a different target version to the rest of them.

Not sure, since WinUI 2.8 requires 17763+, whereas this app targets 15063+.
I'll do it.
Currently, it's impossible for me to target all four architectures (x86, x64, ARM, ARM64) in a bundle since the ARM64 has a different target version to the rest of them.

关于第一个我忘记说了，也许您可以在商店上传的时候保留一个适用于旧版本系统的安装包。就像Microsoft Store一样，虽然目前都是基于22XXX的版本，但是商店里面还是保留了11XXX的版本。而且根据市场占有率Win10 1809的版本基本上很少了，15063也是LTSC版本的居多吧。基本上大部分软件都是基于17763+的版本了。这只是我个人的意见，仅供参考。
On the first one, I forgot to mention that maybe you can keep an installation package for older systems when you upload it to the store. Just like the Microsoft Store, although it is currently based on the 22XXX version, the 11XXX version remains in the Store.And according to the market share of Win10 1809 version is basically very few, 15063 is also the majority of LTSC version.
Basically most of the software is based on the 17763+ version. This is just my personal opinion for reference only.