Floating point representation errors may cause incorrect codes

How floating point numbers are represented in different languages can cause surprising results on common operations. If these occur, we could generate incorrect codes. A few cases have been identified where this happens.
This doesn't seem to occur when the latitude or longitude have four or more decimal places. Browser locations and GPS coordinates return more than this so it doesn't appear to affect codes generated using these as input.
One example is when either latitude or longitude is 35.6. This should be encoded as follows:

Add 90 to force it into a positive range giving 125.6
20 (the place value for the first digit) goes into 125.6 six times, leaving 5.6 over and returning "8" (the digit with the value of 6)
1 (the place value for the second digit) goes into 5.6 five times, leaving 0.6 over and returning "7" (the digit with the value of 5)
0.05 goes into 0.6 twelve times, leaving 0 over, and returning the digit "J".
Further digits would be "2"s, since there is nothing left over.

If 35.6 was provided as latitude, it's code would look like "8.7.J.2.+2." (where "."s are the longitude digits.) However many of the current implementations will return "8.7.H.X.+X.". (This is the OLC cell immediately to the north.)
This is due to how numbers are represented using mantissa and exponent. For example, in some languages 125.6 - 120 is 5.59999999999999000, not 5.6, and eventually the error becomes large enough to push the coordinate into the next OLC cell. (There's a good explanation of the problem here, and a much more technical explanation here).
Similarly, 3.033 will be encoded incorrectly due to 0.0005 divided by 0.000125 being rounded to 3 instead of 4.
I believe the solution is to use integer arithmetic to compute the codes. This is the approach taken by the new JS implementation in #305, and it was testing of this implementation that identified that it behaved differently to the other implementations. Initially I thought it was a bug - I just didn't realise it was a bug in everything else.
I suggest:

Adding a couple of test cases to identify implementations that are affected.
Submitting the JS implementation to confirm it fixes this issue.
Modifying affected implementations to use the integer arithmetic method.

This isn't good but I think that given the conditions that cause it are fairly unusual, that it's manageable and that it probably isn't affecting anyone in practice.

This looks like the same issue that I ran across in the Java implementation (#217). From our internal discussion, we decided that we would live with the slight imprecision so that we would have consistency between all the implementations.
Are you saying now that we should go the other way? Is there a more "correct" code to return in this edge case?

We thought it was only the Java implementation. It turns out that AFAICT they're all wrong. Since they're not operating how described, I think they should be updated?

I believe the Java implementation was behaving correctly before I made the change (floating point precision was correctly handled by BigDecimal). Looking back, instead of matching the Java implementation to the others, we should have matched the others to the Java implementation.
I think updating them makes sense if it leads to a more precise code returned. I'll revert the change I made to the Java library.

Oops didn't mean to close this.

Work plan

[ ] Adding a couple of test cases to identify implementations that are affected.
[ ] Submitting the JS implementation to confirm it fixes this issue.
[ ] Modifying affected implementations to use the integer arithmetic method.

Recommended tag: implementation testing

@drinckes Thank you for the reference to #305 as a potential solution. There's a lot in that PR, could you please point to the relevant code or summarize here?
Personally I am considering to encode as:
function encode(double lat, double long)
    set latToEncode = floor( lat.plus(90).clamp(-90, 90) * 25_000_000 )
    set longToEncode = floor( long.mod(360) * 8_192_000 )

    ... then encode in bases(20, 20, 20, 20, 20, 4, 5, 4, 5, 4)
    ... and bases(20, 20, 20, 20, 20, 5, 4, 5, 4, 5)

I have not yet tested it to your test cases above. And I'm studying your other options. I am also considering to propose this as the reference implementation if it is correct.

This issue is partially fixed in https://github.com/google/open-location-code/pull/463
The Open Location Code API Specification includes notes about floating point errors and it includes a recommendation implementation that produces correct results.
It also references classes of floating point errors that are not discussed in this issue.

The above PR does NOT implement the required/recommended functionality. But because we also have https://github.com/google/open-location-code/pull/306, I recommend to close this issue as a (pre) duplicate of https://github.com/google/open-location-code/pull/306


Add a hover with the exact time

Adding a hover over the "created at" times, with the exact timing information, will make easier to see when a smoke detector stopped submitting data / otherwise has changed
Notice that this commit is untested, as it's hard to configure Ruby on Rails on Windows

Should work. If dual-booting Linux isn't an option (or getting a VM somewhere; Amazon will give you a year free), then the Windows subsystem for Linux has I think been released.


Can't marshal / serialize GoogleHash object

Is there any way to marshall / searialze a google hash object? I would ideally like to create the hash, store it in a db, and then recreate it from the db.

I'd be extremely interested in this, as I'd like to use this lib for my search engine, http://pickyrb.com/ – sorry that this is just a +1.

Could somebody please elaborate on what their use case is for this? They
need a super fast serial/deserialize to disk?
On Sun, Feb 1, 2015 at 5:36 AM, Florian R. Hanke<EMAIL_ADDRESS>wrote:

I'd be extremely interested in this, as I'd like to use this lib for my
search engine, http://pickyrb.com/ – sorry that this is just a +1.
—
Reply to this email directly or view it on GitHub
https://github.com/rdp/google_hash/issues/21#issuecomment-72363084.

In Picky, I'd like to be able to dump/load the Hash-based indexes to/from disk. Currently, I could use #each to dump to disk, and then load it again – however, if the faster version was available, I'd gladly use that.

Yes, I am using it the same way: calculating millions of combinations and storing them in google_hash while in app. Cannot really save them anywhere because google_hash is not dumpable.
+1 a lot!

OK are you folks all just looking for dumping native types or Ruby objects?
On Mon, Mar 16, 2015 at 4:46 PM, Alex<EMAIL_ADDRESS>wrote:

Yes, I am using it the same way: calculating millions of combinations and
storing them in google_hash while in app. Cannot really save them anywhere
because google_hash is not dumpable.
+1 a lot!
—
Reply to this email directly or view it on GitHub
https://github.com/rdp/google_hash/issues/21#issuecomment-81972366.

@rdp For me it's not as important how they are stored, just that they can be reloaded.

what type of objects, though, does this include ruby objects or just native
ones [storing ruby objects is far more tricky]
On Thu, Mar 19, 2015 at 10:25 AM, Florian R. Hanke<EMAIL_ADDRESS>
wrote:

@rdp https://github.com/rdp For me it's not as important how they are
stored, just that they can be reloaded.
—
Reply to this email directly or view it on GitHub
https://github.com/rdp/google_hash/issues/21#issuecomment-83650905.

I think storing native objects is enough. Storing custom objects requires marshaling which is not a good idea at all.

@rdp By "native", do you mean String/Numeric/…?

Exactly, + symbols

@rdp For me, it would already be great if "native" objects would be supported.

Native means numeric in this case [I don't special store Strings yet,
though that would be interesting...]
On Tue, Mar 24, 2015 at 4:34 AM, Florian R. Hanke<EMAIL_ADDRESS>wrote:

@rdp https://github.com/rdp For me, it would already be great if
"native" objects would be supported.
—
Reply to this email directly or view it on GitHub
https://github.com/rdp/google_hash/issues/21#issuecomment-85443561.


Cannot use translate.lua without -gpuid

Hi,
translate.lua without -gpuid
Following the guide on github(some differences has been noticed and reported between doc on github and opennmt.net), i ran:
th translate.lua <some_path>.t7 -src <data_path>.txt -output pred.txt
which gives:
Loading '<path>.t7'...
/home/<user>/torch/install/bin/luajit: /home/<user>/torch/install/share/lua/5.1/torch/File.lua:343: unknown Torch class <torch.CudaTensor>
stack traceback:
  [C]: in function 'error'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:343: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:369: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/nn/Module.lua:184: in function 'read'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:351: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:369: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:369: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:353: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:368: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:369: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:369: in function 'readObject'
  ...
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:369: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:369: in function 'readObject'
  /home/<user>/torch/install/share/lua/5.1/torch/File.lua:409: in function 'load'
  ./onmt/translate/Translator.lua:29: in function '__init'
  /home/<user>/torch/install/share/lua/5.1/torch/init.lua:91: in function 'new'
  translate.lua:65: in function 'main'
  translate.lua:193: in main chunk
  [C]: in function 'dofile'
  ...<user>/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:150: in main chunk
  [C]: at 0x00406670

translate.lua with -gpuid 1
th translate.lua <some_path_>.t7 -src <data_path>.txt -output pred.txt -gpuid 1
It runs! :)
For sure I want to run with GPU, still, I'm not sure if this is related to my setup, if its an actual issue or an undocumented requirement.
Hope it helps
pltrdy

If the model was trained on the GPU, you then need to load it on the GPU and specify the -gpuid option.
You can use the tools/release_model.lua script to make it work on the CPU so you don't need to set the -gpuid option.

Ok my bad then. I thought about it just after posting.
Thanks for the clarification.
Closing.


Handle a manifest version in the payload

We need a version on the manifest, this ensures that we do not think
"version" is a type of provider.

Ivanchuk backport details:
$ git log -1
commit 3358ceb9d2392d221fe3308720abc0ef01be80da
Author: Jason Frey<EMAIL_ADDRESS>Date:   Tue Jul 30 13:43:19 2019 -0400

    Merge pull request #27 from agrare/handle_manifest_version

    Handle a manifest version in the payload

    (cherry picked from commit a615c52368c0f2e196915b586b0b6a15cac1f922)


Mobile phones resolution

Win 11 in React doesn’t fit mobile phones,please fix that.

I believe that it was not intended for mobile devices.

I believe that it was not intended for mobile devices.

I know, but look at dustinbrett.com, it's made for PC and it works on Phone, I'm using dustinbrett.com on phone because I cannot use Win11 in React on phone, I like Win11 in React but I'm not using my PC that much so I wanted to use it on a Phone.

Microsoft themselves failed how could we (Cough, cough windows phone)

I believe that it was not intended for mobile devices.

You in fact are correct, refer to #107 for the message that should show up

Microsoft themselves failed how could we (Cough, cough windows phone)

It was a good concept, just poorly implemented. I wish they would retry it

Microsoft themselves failed how could we (Cough, cough windows phone)

It was a good concept, just poorly implemented. I wish they would retry it

Disagreed, as iOS is superior, it mus stay that way. If WindowsOS makes a successful emergence on the market, it will dethrone the deserved ruler of the land, Apple. In conclusion, it was both a bad concept and a poorly implemented concept.

Microsoft themselves failed how could we (Cough, cough windows phone)

It was a good concept, just poorly implemented. I wish they would retry it

Disagreed, as iOS is superior, it must stay that way. If WindowsOS makes a successful emergence on the market, it will dethrone the deserved ruler of the land, Apple. In conclusion, it was both a bad concept and a poorly implemented concept.

Android is better. Change my mind.

oops

I angered the beast

I angered the beast

I was being sarcastic. I like iOS and iPhone,But I still prefer android due to customizability and it being open source

Microsoft themselves failed how could we (Cough, cough windows phone)

It was a good concept, just poorly implemented. I wish they would retry it

Yeah

I angered the beast

I was being sarcastic. I like iOS and iPhone,But I still prefer android due to customizability and it being open source

I’m an Apple fan ☺

You guys noobs, I have used Nokia 3310, It is superior is every sense possible.
It can also be used to throw as a weapon in warzone to cause substantial damage.

You guys noobs, I have used Nokia 3310, It is superior is every sense possible.
It can also be used to throw as a weapon in warzone to cause substantial damage.

😂😂😂🤣🤣🤣🤣🤣😂😂😂🤣🤣

I am going to close this, as it is irrelevant, and now off-topic.

Won't Fix (for now) as there are so many different sizes of mobile devices.


problems with "hard refresh"

hard refresh triggers a reconstruction
this is the expected behavior

but for some strange reason when it is used more than 2 times hard refresh does not perform the reconstruction process 🙍

This has been fixed.


Build failed in mount stage

Hello! Please, help me. i am use our project long time, since 2021 years. I'm trying update my instance. Clone last release version and trying build, but i have this error.
What is it, how i can fixed this error?
------
 > [base 2/2] RUN        --mount=type=cache,target=/var/cache/apt,sharing=locked,id=var-cache-apt-linux/amd64
 --mount=type=cache,target=/var/lib/apt,sharing=locked,id=var-lib-apt-linux/amd64            --mount=type=tmpfs,target=/var/cache/apk            --mount=type=tmpfs,target=/tmp            --mount=type=bind,from=build-scripts,source=/build-scripts,target=/build-scripts            sh /build-scripts/postfix-install.sh:
#9 0.291 /build-scripts/postfix-install.sh: set: line 2: illegal option -
------
executor failed running [/bin/sh -c sh /build-scripts/postfix-install.sh]: exit code: 2```

Ok,
you have given me too little information to actually go on anything. I have no idea how you're building this, on which environment and why you are even trying to build it as you could be using the prebuilt image instead.
Either way, second line of /build-scripts/postfix-install.sh is set -e, so my best guess is that you are running a build on shell that does not support set -e. See man set.


Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:chromium:chromium:2.0.48:*:*:*:*:*:*:*
cpe:2.3:a:chromium_project:chromium:2.0.48:*:*:*:*:*:*:*
CVE

CVE-2011-1797
CVE-2015-1346
CVE-2015-1205
CVE-2017-7000

ODC Integration
{"label"=>"Maven Plugin"}
ODC Version
7.0.0
Description
As far as I understand from https://github.com/jeremylong/DependencyCheck/issues/4065, version 7.0.0 should contain already the fix for this case but it doesn't seem to be the case
[ERROR] Failed to execute goal org.owasp:dependency-check-maven:7.0.0:check (default) on project ***REDACTED***:
[ERROR]
[ERROR] One or more dependencies were identified with vulnerabilities that have a CVSS score greater than or equal to '7.0':
[ERROR]
[ERROR] netty-tcnative-boringssl-static-2.0.48.Final-osx-x86_64.jar: CVE-2015-1346(7.5), CVE-2011-1797(9.3), CVE-2017-7000(8.8), CVE-2015-1205(7.5)
[ERROR]
[ERROR] See the dependency-check report for more details.
[ERROR] -> [Help 1]

@jeremylong I use version 7.0.4 trying to solve the FP, but it seems not work, could please take a look when you have time :)
Any help will be greatful.
<plugin>
            <groupId>org.owasp</groupId>
            <artifactId>dependency-check-maven</artifactId>
            <version>${dependency-check-maven.version}</version>
            <configuration>
              <suppressionFiles>
                <suppressionFile>src/owasp-dependency-check-suppressions.xml</suppressionFile>
              </suppressionFiles>
              <failBuildOnCVSS>7</failBuildOnCVSS>
              <msbuildAnalyzerEnabled>false</msbuildAnalyzerEnabled>
              <nodeAnalyzerEnabled>false</nodeAnalyzerEnabled>
              <yarnAuditAnalyzerEnabled>false</yarnAuditAnalyzerEnabled>
              <pyDistributionAnalyzerEnabled>false</pyDistributionAnalyzerEnabled>
              <pyPackageAnalyzerEnabled>false</pyPackageAnalyzerEnabled>
              <pipAnalyzerEnabled>false</pipAnalyzerEnabled>
              <pipfileAnalyzerEnabled>false</pipfileAnalyzerEnabled>
              <retireJsAnalyzerEnabled>false</retireJsAnalyzerEnabled>
              <msbuildAnalyzerEnabled>false</msbuildAnalyzerEnabled>
              <mixAuditAnalyzerEnabled>false</mixAuditAnalyzerEnabled>
              <nugetconfAnalyzerEnabled>false</nugetconfAnalyzerEnabled>
              <assemblyAnalyzerEnabled>false</assemblyAnalyzerEnabled>
            </configuration>
            <executions>
              <execution>
                <goals>
                  <goal>aggregate</goal>
                </goals>
              </execution>
            </executions>
          </plugin>

It seems this issue reactive as https://github.com/apache/pulsar/runs/7942966298?check_suite_focus=true
CVE-2011-1797
Error:  Failed to execute goal org.owasp:dependency-check-maven:7.1.0:aggregate (default) on project pulsar:
Error:
Error:  One or more dependencies were identified with vulnerabilities that have a CVSS score greater than or equal to '7.0':
Error:
Error:  netty-tcnative-boringssl-static-2.0.52.Final-osx-x86_64.jar: CVE-2011-1797(9.3)


add gazebo_sfm_plugin to .rosinstall

the plugin wasn't in the .rosinstall. this should be fixed now

implemented change requested and added comments to dynamic_manager.py


Help Text for getaccountinfo

Help text for getaccountinfo is not very descriptive, it is not clear that this command is referencing a smart contract vs. the Core "account" concept. Suggest blockchain.cpp line 781
            "1. \"address\"          (string, required) The account address\n"

be changed and add two results lines:
            "1. \"address\"  (string, required) The contract address hash\n"
            "\nResult:\n"
            "Contract details including complete storage table and code\n"

Fixed here: https://github.com/qtumproject/qtum/commit/1774408722fe0b332b6109a33b21e8018dd73b6d


Tx setters for inputs and outputs

In the mutable Transaction constructor we sort the inputs and outputs
and in the immutable Transaction constructor we assert if given
unsorted inputs and outputs. There was still an issue if the zero
arg constructor was used and then unsorted inputs or outputs were
set. This adds setters that assert if the lists are not valid when set.

Just a thought, if we receive a transaction (with duplicate input utxo or unsorted inputs or outputs) over the network we may end up asserting now. Perhaps we should use exceptions or we have to deserialize to an intermediate struct that we can pre-validate before creating our Transaction.

For now we will update the TxBuilder only as the problem with the invalid Transactions causes assert would be a show stopper. Will open a new PR with those changes only and close this one.


Is "tx size" from the document always be fixed size ?

If the transations are from different chaincode's method:
i.e,  one tx aims to set a value (Key xxx: Value(int)), that maybe a short size of the transaction
another tx aims to  store huge data(Key: xxx, value (big-array-bytes)), that maybe a size gap to the tx size according to previous one ?

Then , from the document:
I learnt that the block_size can be caculated by block size = min(PreferredMaxBytes，MaxMessageCount * tx size， AbsoluteMaxBytes), but ... if the tx size differs from each transaction, will the result maybe not such precise? (Or, tape use a unique chaincode method for testing, so tx should be always fixed size. )
（For tx size understanding, I‘m not sure whether it should be a tape's question :-) ）
@SamYuan1990

your 1st question will be supported by https://github.com/Hyperledger-TWGC/tape/issues/109.
the second one, general speaking, you can calculate avg size instead.
at my point of view, when taking about tx size, it should be considered from one case to avg/mixed case.
as every tx has it's own size. even we do a simple logic as counting() { read i;i++; write i; } the size is different for each tx due to cert, and value of i. (9 -> 10, 99 -> 100 ...)
so, it should be considered as avg size of tx.
and it's possible to calculate/get the avg size of tx by statistics...

Got that . Thankyou! Now close it..
@SamYuan1990

Now I have known what does the tx size mean from view of tape/probe.


Dummy test app

When I merged https://github.com/nickcharlton/administrate-field-nested_has_many/pull/18, @nickcharlton threw the question of how we could go about testing that. This PR attempts to provide an answer.
Here I set up an dummy app, same as the ones used for engines, as well as feature specs that run on this dummy app.
 In summary, I added:

A dummy app at spec/dummy. I copied it from a newly-created engine project and adapted it to work here.
In the dummy app I added in turn:

A couple of models, ensuring a has_many relationship.
An admin section with administrate, using administrate-field-nested_has_many.

A feature spec for the problem at hand.
Appraisal, to allow testing the dummy app against different versions of Administrate.

To run the tests: bundle exec appraisal rake. Should document this and set it up on CI.
To run the dummy app: rails s.
On an implementation note, there's too much logic in the template at app/views/fields/nested_has_many/_show.html.erb. This is because I couldn't get a helper to work.

I am, you'll be happy to hear, finally merging your work here!
I think removing them in fine and if it turns out to not be, is not that significant.
We do indeed include the lock files for Appraisals.


Czech locale coordination issue

Issue for coordination of Czech locale.
Current locale state: finished full translation and testing on my side

Update: game UI locale in PR, Steam store page locale in works

Update: PR now contains full locale for both game and Steam store when checked against state at the time of writing this comment. (commit 7a4bf0d)

Initial translation was merged, Czech locale is now being kept up to date and polished when needed.

Update: Added registration errors, tutorial teleporter error, + proofreading and fix of one typo.
PR open.

Created a new PR #100 to update what words are used to be more consistent across the whole document.
With collaboration from @rampa3

What should be additionally done:
Check the document for usage of english+czech mutation words and use the proper czech word (authentifikace -> authentifikace)
Check the usage of word "moderace", should refer to tools, not moderation as a team.
Change the usage of "Váš" to "váš" and all similar forms, as the use of capital V is overly formal and out of use outside very specific circumstances.


fix bug #204 in Aberdeenshire scraper

Description
See #204. Mapping of categories in Aberdeenshire_council_scraper was not working correctly. This PR intends to fix this by correcting the check of multiple or conditionals.
Motivation and Context
Fixes #204
How Has This Been Tested?

ran aberdeenshire_council_scraper.py
checked output in aberdeenshire.csv, whether more than 3 categories where applied
checked random datasets in aberdeenshire.csv, whether the matched category fits the title

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.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@KarenJewell, I've taken all category processing out of aberdeenshire_council_scraper.py and put the keywords in merge_data.py, if they haven't been there, yet. This should fix the bug resolve the issue of processing categories outside of merge_data.py.
However, until we solve #172, Aberdeenshire datasets will show up as 'uncategorized' from now on.

Tested. Behaves as expected. Taken note of caveat with issue #172


Handle ORC files with corrupt checkpoints

When ORC switched to low memory mode it can create invalid checkpoints.  When
reading the file if the checkpoints can not be decoded, treat the entire strip
as a single row group.  DWRF files with a row group dictionary still fail
because the row group dictionary length is contained in the checkpoint stream.

looks good


fix: feat/epmadpafic 878 review GitHub security permissions

This PR is included in version 1.0.0 :tada:


Update ag-Grid to 21.0.0

Just released - we could test immediately, or see if they do any follow-up patch releases.
https://www.ag-grid.com/ag-grid-changelog/?fixVersion=21.0.0
Some compelling changes:

Scroll performance "vastly improved"
More control over react prop change detection to avoid re-renders - https://www.ag-grid.com/react-more-details/#react-row-data-control - as well as a note "declarative column definitions now reactive"
Icon customization - maybe we can get our standard glyphs in

Note I don't see any tickets re. performance in tree mode - this was a blocker for us with the 20.2.0 upgrade - we should be sure to test to see if performance is OK or if we are still stuck.

Looks like AG-2879 is in the list of fixed issues, though the title only noted "investigating" the performance issues so not really clear if anything was done, but seems promising


Add attributes to class-level CkAbort function declarations

Fortunately I did not see any new warnings appear as a result of these attributes.


[Xcodeproj] Unknown object version (60).

New Issue Checklist

[X]  Updated fastlane to the latest version
[X]  I read the Contribution Guidelines
[X]  I read docs.fastlane.tools
[X]  I searched for existing GitHub issues

Issue Description
Fastlane fails bulding MacOS app if project.pbxproj  version  is "60"
Command executed
fastlane with lane desa_app
    lane :desa_app do
        build_app(scheme: "XXX", output_directory: XXX, export_method:"developer-id",export_options: {
                  provisioningProfiles: {
                  "com.a.b" => "DeveloperID App Profile",
                  "com.a.b" => "DeveloperID Extension Profile"
                  }
                  })

fastlane finished with errors
[Xcodeproj] Unknown object version (60).
This error only happens when using String Catalog
https://developer.apple.com/documentation/Xcode/localizing-and-varying-text-with-a-string-catalog
project.pbxproj file is updated from version 56 to 60 when enabling string catalog
Environment

fastlane 2.217.0
macOS 14.1 (23B74)
xCode 15.0.1 (15A507)

Complete output when running fastlane, including the stack trace and command used
/Library/Ruby/Gems/2.6.0/gems/xcodeproj-1.22.0/lib/xcodeproj/project.rb:228:in `initialize_from_file': [!] [Xcodeproj] Unknown object version (60). (RuntimeError)
	from /Library/Ruby/Gems/2.6.0/gems/xcodeproj-1.22.0/lib/xcodeproj/project.rb:113:in `open'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane_core/lib/fastlane_core/project.rb:120:in `project'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane_core/lib/fastlane_core/project.rb:207:in `configurations'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/gym/lib/gym/detect_values.rb:163:in `detect_configuration'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/gym/lib/gym/detect_values.rb:34:in `set_additional_default_values'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/gym/lib/gym/module.rb:15:in `config='
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/gym/lib/gym/manager.rb:8:in `work'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/actions/build_app.rb:68:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	from Fastfile:134:in `block (2 levels) in parsing_binding'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/lane.rb:41:in `call'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/commands_generator.rb:110:in `block (2 levels) in run'
	from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
	from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
	from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/commands_generator.rb:354:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/commands_generator.rb:43:in `start'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in `take_off'
	from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.217.0/bin/fastlane:23:in `<top (required)>'
	from /usr/local/bin/fastlane:23:in `load'
	from /usr/local/bin/fastlane:23:in `<main>'

Fixed after updating coapods and ruby to last version

@mcgrawhill
hi...
what do you mean "updating cocoapods and ruby to last version" did you mean the latest version? can you pls specify the version you used. I am facing similar issue when running fastlane in Jenkins.
Issue:
[!] Xcodeproj doesn't know about the following attributes {"expectedSignature"=>"AppleDeveloperProgram:8VDxxx"} for the 'PBXFileReference' isa.
If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new
[!] Xcodeproj doesn't know about the following attributes {"expectedSignature"=>"AppleDeveloperProgram:8VDxxx""} for the 'PBXFileReference' isa.
If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new
[!] Xcodeproj doesn't know about the following attributes {"expectedSignature"=>"AppleDeveloperProgram:8VDxxx""} for the 'PBXFileReference' isa.
If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new
[!] Xcodeproj doesn't know about the following attributes {"expectedSignature"=>"AppleDeveloperProgram:8VDxxx""} for the 'PBXFileReference' isa.
If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new
+------------------+-----------+
|         Lane Context         |
+------------------+-----------+
| DEFAULT_PLATFORM | ios       |
| BUILD_NUMBER     | 235       |
| PLATFORM_NAME    | ios       |
| LANE_NAME        | ios build |
+------------------+-----------+
[11:37:32]: [Xcodeproj] Unknown object version (60).

Same here. What are the versions that have worked for you? I'm using cocoapods 1.14.3 and ruby 3.1.4

I faced the same issue and the fix for me was just updating the Fastlane version in my Gemfile from 2.214 to 2.219.

I'm facing similar issue in 2.219 :/

I have the same issue but with [Xcodeproj] Unknown object version (63). in Xcode 15.3.

I have the same issue but with [Xcodeproj] Unknown object version (63). in Xcode 15.3.

Same here

@mcgrawhill hi... what do you mean "updating cocoapods and ruby to last version" did you mean the latest version? can you pls specify the version you used. I am facing similar issue when running fastlane in Jenkins.
Issue:
[!] Xcodeproj doesn't know about the following attributes {"expectedSignature"=>"AppleDeveloperProgram:8VDxxx"} for the 'PBXFileReference' isa. If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new [!] Xcodeproj doesn't know about the following attributes {"expectedSignature"=>"AppleDeveloperProgram:8VDxxx""} for the 'PBXFileReference' isa. If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new [!] Xcodeproj doesn't know about the following attributes {"expectedSignature"=>"AppleDeveloperProgram:8VDxxx""} for the 'PBXFileReference' isa. If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new [!] Xcodeproj doesn't know about the following attributes {"expectedSignature"=>"AppleDeveloperProgram:8VDxxx""} for the 'PBXFileReference' isa. If this attribute was generated by Xcode please file an issue: https://github.com/CocoaPods/Xcodeproj/issues/new +------------------+-----------+ | Lane Context | +------------------+-----------+ | DEFAULT_PLATFORM | ios | | BUILD_NUMBER | 235 | | PLATFORM_NAME | ios | | LANE_NAME | ios build | +------------------+-----------+ [11:37:32]: [Xcodeproj] Unknown object version (60).

Resolved after updating to latest Fastlane version.

I solved it using XCode 14.0 instead of XCode 15.3 in the xcode project inspectors (right panel) -> Project Document -> Project Format

Issue
Fix

	archiveVersion = 1;
 	classes = {
 	};
-	objectVersion = 63;
+	objectVersion = 56;
 	objects = {

 			buildConfigurationList = ... /* Build configuration list for PBXProject "yourProject" */;
-			compatibilityVersion = "Xcode 15.3";
+			compatibilityVersion = "Xcode 14.0";
 			developmentRegion = en;


Add example with roks

Finally, I do not know why the validate is failing.  It is producing this error:


Docs: EFS with sst dev

This may be expected at this stage as it looks like the EFS component was only shipped recently, but I can't find anything in the docs mentioning that local development isn't supported in this case.
Steps to reproduce:

clone down the aws-efs-sqlite example from the sst repo
install deps with package manager of your choice
run sst dev
resources will deploy successfully
attempt to access deployment url
response will hang in the browser, eventually returning 500 response with text it does not seem like sst dev is running
the Functions tab in the terminal will log out Cannot open database because the directory does not exist where better-sqlite3 attempts to create the database file at /mnt/efs (attempting to stat /mnt/efs directly will also return ENOENT: no such file or directory, stat '/mnt/efs')
checking in the AWS console, all resources appear to be successfully created and linked (i.e. Lambda, local mount path, filesystem accesspoint etc)

From looking at other examples using Lambda with VPCs, it looks as though the new sst tunnel may be required to use private resources alongside functions with sst dev - however, I still get the same errors after installing the tunnel and setting bastion: true via the VPC constructor in sst.config.ts.
For context, when running sst deploy and accessing the deployed function url things work perfectly. However, the sst dev errors appear to be common to all 3 EFS examples.
Is this likely a bug, or is the EFS component not supported with sst dev at this time?
Many thanks!

Yeah I'll mention this in the docs but your Lambda function (or container) running locally does not have access to EFS. The assumption is that you are using the local filesystem.

Ahh apologies that's mainly me misunderstanding where things were running during sst dev 🤦♂
Many thanks for the quick response! I've got things running now using some conditional logic keyed from process.env.SST_LIVE.


Documentation on custom type adapters outdated

The documentation on custom type adapters that is written in the README.md is outdated and only partially correct. While the configuration part within the project's gradle config is still valid, the registration of the custom type adapter is no longer done using a "custom type adapter factory" but via the ApolloClient builder.

Believe we can close this


Sanitizing/removing client request headers

Please describe your use case / problem.
I'm looking for a way to remove request headers sent by a client, while allowing an AuthService to still return that header and have it forwarded to the upstream service. While it's not completely clear from the docs, it looks like adding a header to remove_request_headers would effectively remove the header whether it was sent directly from the client or returned by the AuthService.
Describe the solution you'd like
I would like to be able to ensure that a specific request header can not be passed through from a client but can still be added by an AuthService. Is there a way to handle this scenario within Ambassador?

I confirmed that remove_request_headers removes headers from the client request as well as headers returned from the AuthService. However, I found I could do what I wanted with Lua scripts. For example:
  lua_scripts: |
    function envoy_on_request(request_handle)
      request_handle:headers():remove("x-my-custom-header")
    end


Ark Note

This PR implements offchain notes. The server creates the note and signs it, user can swap notes for VTXOs in rounds.
https://arkdev.info/blog/introducing-ark-notes
Context
It introduces Ark Notes, a new feature designed to enhance fund recovery for offline clients within the Ark network, while simultaneously optimizing liquidity management for servers. Ark notes allow clients to seamlessly reclaim expired VTXOs, ensuring that users retain access to their funds even after prolonged offline periods.
While an unspent VTXO is swept by the server, it creates and sign a "note". This note is sent via nostr notification and can be exchanged for a VTXO in a round.
Test it yourself
generates an ark note using the admin interface:
curl -X POST http://localhost:7070/v1/admin/notes -H "Content-Type: application/json" -d '{"amount": 2000}'

swap the note for a VTXO using the CLI:
> ark redeem-notes -n arknote9gQ2zCq2xDERZmHTCjWARLMyZcKfyJD9CALjLhN8FngF5eZ7jMMkHwEmUBD1EsfZEvkjkqHi2e9Y7oonfXmREL4P6Pv2QzHL49aB
INFO[0000] payment registered with id: ec706f59-3048-4727-8a1e-639d1840839c
INFO[0004] a round signing started
INFO[0004] round combined nonces generated
INFO[0004] a round finalization started
INFO[0004] congestion tree validated
INFO[0004] finalizing payment...
INFO[0004] done.
INFO[0004] waiting for round finalization...
{
	"txid": "7cb63f7f01f557de2c811a35d3e3050c2c6985d030fcb8b22f4a3f72c57aedda"
}

@tiero @altafan please review

@louisinger please solve conflicts


Do not hardcode the UDP listen port in ChipDeviceController

Problem
TLDR; Same PR as this https://github.com/project-chip/connectedhomeip/pull/9309, but for the C++ library
ChipDeviceController hardcodes the UDP listen port to CHIP_PORT. This makes it impossible to have more than one instance of any of the controllers that use this on the same host.
The target device is unable to tell which one is which and messages arrive to both which results in communication failure.
Change overview
Do not hardcode the UDP listen port.
Testing

If manually tested, what platforms controller and device platforms were manually tested, and how?
Tested pairing with two instances of the chip-tool cli with the same accessory.

@saurabhst ?


fix: do not send package via outdated socket session

We found an edge-case where a websocket transport session would be closed/unavailable on the client agent side, but mediator still thinks it is available (due to client being offline).
When client returns back online and initiates a flow via mediator, the mediator will attempt to send the package to the now outdated websocket, instead of the newest / current session.
This PR fixes the problem, but is there any reason why a single connection may need multiple open WebSocket transport sessions?

FYI - this bug was found using AFJ 0.3.3, so perhaps it is not relevant anymore, but I can't see why it wouldn't be.

Codecov Report

Merging #1559 (c460a86) into main (c0d9304) will decrease coverage by 0.98%.
The diff coverage is 12.50%.

:exclamation: Current head c460a86 differs from pull request most recent head e741b6a. Consider uploading reports for the commit e741b6a to get more accurate results

@@            Coverage Diff             @@
##             main    #1559      +/-   ##
==========================================
- Coverage   85.73%   84.76%   -0.98%
==========================================
  Files         950      950
  Lines       22745    22753       +8
  Branches     3978     3981       +3
==========================================
- Hits        19500    19286     -214
- Misses       3060     3252     +192
- Partials      185      215      +30

Files Changed
Coverage Δ

packages/core/src/agent/TransportService.ts
72.41% <12.50%> (-22.83%)
:arrow_down:

... and 5 files with indirect coverage changes

@TimoGlastra - adjusted for any type


Update index.md

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

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

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Congrats @hkRho on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Update page.md

Modification to the spelling of Programing to Programming
See this stack overflow link for a more detailed explanation on why this distinction has been made.

I have a minute here ... I'll take care of those other spots.
Thanks @dmtomczyk! ✈

Thanks for the quick responses @guardrex
I appreciate the work you're doing!


Print error message if deployment fails, not getting compile version

@hmusum please review.
This would make it impossible to deploy under user tenants to a new application. I don't really want people to do this, as we'd like them to stop using the user tenants, but we said it should continue to work.

Long term we just need to expose more info through the API, so we can display correct error messages to the end user.

Not relevant anymore when people are using the sandboxtenant when deploying to dev


Export do not include document  of  .kibana index where  _type:index-pattern

As  proposed in #9 ,  I've check dotkibana --export all --pkg but  entries where  _type:index-pattern is not in the exported json.
I see data I expected to found in export with this query
GET /.kibana/_search?q=_type:index-pattern
When I export  the kibana config,  I  can't import them in a new kibana because search need to found the index-pattern
So I need to manually create/define the index-pattern.
My need is to prepare the board in my local vagrant, and then share it via export.
Other developers need to import the config into their local installation.
It must also be able to import new board / visually / search in Kibana production and staging.

ok I found  what I need in this project : https://download.elastic.co/beats/dashboards/beats-dashboards-1.1.0.zip
in save/kibana_dump.py

The provisoning of mappings and visualizations are two separate tasks. For instance, what if you restored a dashboard with out-of-date mappings, or deleted mappings with a skeleton index-pattern. For one project I'm on we use a skeleton index-pattern and post it with curl, then dotkibana --refresh to cache the mapping.
I could expand all to include a skeleton index pattern (without cached mappings), but I don't recommend saving the index-pattern. In fact, I should remove config if it is in all.
What is your use case? Maybe I'm not understanding your problem.

I should mention that I use vagrant with ansible to provision kibana for that project.


Fix text position

Fixes #1934
Describe the changes you have made in this PR -
The text position (project name) at smaller screen size than 991px is adjusted
Screenshots of the changes (If any) -

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage remained the same at 88.019% when pulling 671fb89d4a85370cff6de69bf1e268b1326dd80a on shivamkushwah0:fix_text_position#1934 into 6131de0bf2a82c3f1a3e76132947468621a2f097 on CircuitVerse:master.

Please send any PRs regarding simulator to new_UI branch

okay sure.....


Linked accounts

Describe the bug
In the user profile at 'Account Management' is not showing the linked accounts list.
To Reproduce
Steps to reproduce the behavior:

Click in your picture
Click on 'Profile'
On the left menu select 'Settings'
Scroll down to 'Account Management'

Expected behavior
At Linked accounts it should appear for the two accounts you link. The association works and if you log in to one of the accounts you have my profile data. But instead of showing the accounts just by saying "No accounts linked"
The linked account also don't show the account where it was linked from
Screenshots
No screenshots because privacy
Desktop (please complete the following information):

OS: Windows 10 and Microsoft Edge
Browser Firefox and
Version Firefox 77.0.1; Microsoft Edge 44.18362.449.0

I also experienced that when I try to link two accounts, the app prompts me to log in to the account I want to link. What happens is that I just get logged in to the other account.
I am logged in to live account (A)
I go to Profile -> Settings -> Account Management -> [+ Add account]
Login prompt
I log in to work account (B)
Am logged in to account (B) with no sign of any link.
It doesn't matter which way I try to link (A to B or B to A), the behavior is always just switching accounts, never actually linking. There is no indication of an error in the UI.

Duplicate of #2726

Try again @Nasto and @rramoscabral , I had a similar problem but now it worked.


Conditional TimelineNodes don't work as the first node of the experiment

... because .advance() is not called before the first trial and the logic for skipping conditionals lives in that function.

This is fixed with the new TimelineNode evaluation routine built for #250.


Starting streaming jobs via mist-cli / rest api results in 504 timeout

Streaming jobs start, but return a 504 timeout because they do not return a result (they run forever).  Streaming jobs need special handling...
$ curl -s --data '{}' -H 'Content-Type:application/json' -X POST http://myserver:2004/v2/api/functions/myfunction/jobs?force=true

<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx/1.13.8

Job succeeded

The force parameter keeps your http connection alive until your job returns a response. You can run jobs without the ?force=true parameter, this will work asynchronously.

I will try that - thanks.
As an enhancement, I think calling a streaming function should return started/failed/etc .


MSID: 89281 Version: 2 DOI: 10.1101/2<IP_ADDRESS>91786

MSID: 89281
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>91786
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=89281
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>91786

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/89281v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>91786
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/89281/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

(waiting for docmap/reimport)


🧸 argocd 2.1.8 🧸

What is this PR About?
update default to latest argocd 2.1.8
How do we test this?
helm install instructions
cc: @redhat-cop/day-in-the-life

/lgtm
/approve


[Bug]: OBSStudio returns correct version, but wrong Url

What happened?
Trying to get the updated version for OBSStudio:
Get-EvergreenApp -Name 'OBSStudio' | Where-Object { $_.Architecture -match 'x64' }
This returns:
Version Architecture URI

27.2.0  x64          https://cdn-fastly.obsproject.com/downloads/OBS-Studio-27.2.0-Full-Installer-x64.exe
This Url throws a 404.
The actual download Url is https://cdn-fastly.obsproject.com/downloads/OBS-Studio-27.2-Full-Installer-x64.exe
Version
2202.525
What PowerShell edition/s are you running Evergreen on?
Windows PowerShell
Which operating system/s are you running Evergreen on?
Windows 10, Windows Server 2016+
Have you reviewed the documentation?

[X] Troubleshooting at: https://stealthpuppy.com/evergreen/troubleshoot/
[X] Known issues at: https://stealthpuppy.com/evergreen/issues/

Verbose output
VERBOSE: Get-EvergreenApp: Function exists: C:\Program Files\WindowsPowerShell\Modules\Evergreen\2202.525\Apps\Get-OBSStudio.ps1.
VERBOSE: Get-EvergreenApp: Dot sourcing: C:\Program Files\WindowsPowerShell\Modules\Evergreen\2202.525\Apps\Get-OBSStudio.ps1.
VERBOSE: Get-FunctionResource: read application resource strings from [C:\Program Files\WindowsPowerShell\Modules\Evergreen\2202.525\Manifests\OBSStudio.json]
VERBOSE: Get-EvergreenApp: Calling: Get-OBSStudio.
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: [UseBasicParsing: True].
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: [MaximumRedirection: 1].
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: [DisableKeepAlive: True].
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: [UserAgent: Mozilla/5.0 (Windows NT; Windows NT 10.0; en-NL) AppleWebKit/534.6 (KHTML, like Gecko) Chrome/7.0.500.0 Safari/534.6].
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: [Method: Default].
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: [Uri: https://obsproject.com/update_studio/manifest.json].
VERBOSE: Invoke-RestMethodWrapper: Invoke-RestMethod parameter: [ContentType: application/octet-stream].
VERBOSE: GET with 0-byte payload
WARNING: Invoke-RestMethodWrapper: Error at URI: https://obsproject.com/update_studio/manifest.json.
WARNING: Invoke-RestMethodWrapper: Error encountered: The remote server returned an error: (404) Not Found..
WARNING: Invoke-RestMethodWrapper: For troubleshooting steps see: https://stealthpuppy.com/evergreen/troubleshoot/.

I can't get to https://obsproject.com/update_studio/manifest.json right now to validate.
Binaries are available on the GitHub repo, so the function could pull from there instead: https://github.com/obsproject/obs-studio/releases

OBSStudio 27.2.4 is released and the downloads are now working.
The function could be updated to skip the minor build number if it equals 0 which might work; however, going through the GitHub repo, they remove older binaries, so this is a guess.


[BUG] Plotly html output not working. ERROR: BoundsError

Description
When producing html output, plots made with plotly backend give an error
This is what I see in the generated report:

versions

using InteractiveUtils; versioninfo():

Julia Version 1.4.1
Commit 381693d3df* (2020-04-14 17:20 UTC)
Platform Info:
  OS: Windows (x86_64-w64-mingw32)
  CPU: Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-8.0.1 (ORCJIT, skylake)
Environment:
  JULIA_EDITOR = "C:\Users\asimd\AppData\Local\atom\app-1.47.0\atom.exe"  -a
  JULIA_NUM_THREADS = 3

using Pkg; Pkg.status():

  [c52e3926] Atom v0.12.11
  [94b1ba4f] AxisKeys v0.1.3
  [ad839575] Blink v0.12.3
  [717857b8] DSP v0.6.7
  [31a5f54b] Debugger v0.6.4
  [31c24e10] Distributions v0.23.2
  [634d3b9d] DrWatson v1.11.0
  [7a1cc6ca] FFTW v1.2.1
  [6a3955dd] ImageFiltering v0.6.11
  [e5e0dc1b] Juno v0.8.2
  [23992714] MAT v0.8.0
  [442fdcdd] Measures v0.3.1
  [288cda28] MegTools v0.1.0 [`C:\Users\asimd\.julia\dev\MegTools`]
  [47be7bcc] ORCA v0.3.1
  [5fb14364] OhMyREPL v0.5.5
  [f0f68f2c] PlotlyJS v0.13.1
  [91a5bcdd] Plots v1.3.1 #master (https://github.com/JuliaPlots/Plots.jl.git)
  [08abe8d2] PrettyTables v0.9.0
  [d330b81b] PyPlot v2.9.0
  [295af30f] Revise v2.6.6
  [322a6be2] Sass v0.1.0
  [2913bbd2] StatsBase v0.33.0
  [f3b207a7] StatsPlots v0.14.6
  [30cdaa97] SystemBenchmark v0.3.0 #master (https://github.com/ianshmean/SystemBenchmark.jl)
  [40c74d1a] TableView v0.6.0
  [29a6e085] Wavelets v0.9.0
  [44d3d7a6] Weave v0.10.0
  [37e2e46d] LinearAlgebra
  [9a3f8284] Random
  [10745b16] Statistics

Minimum reproducible steps

using Plots
plotly()
plot(rand(10))

gr()
plot(rand(10))

In REPL:
using Weave
weave("my_script.jl")

in this environment your example works:
plotenv) pkg> st
Status `...`
  [91a5bcdd] Plots v1.3.1

so, let's try to create a separate environment that only contains Plots and try weave there.
(it's okay to keep Weave in your default environment)

Thanks for testing it out, but it still gives me the same error.
using Weave

st
Status `C:\Users\asimd\keft\Project.toml`
  [91a5bcdd] Plots v1.3.1

weave("test.jl")
┌ Warning: ERROR: BoundsError occurred, including output in Weaved document
└ @ Weave C:\Users\asimd\.julia\packages\Weave\74s70\src\run.jl:248
[ Info: Report weaved to test.html
"C:\\Users\\asimd\\keft\\test.html"

ah, so you're weaving a script. then it might be Weave itself causes the problem. I'll take a look at this later

okay, so my current guess is that this line causes this problem. well this doesn't happen on macOS (I'm using), but I'm sure that code should be refactored into more robust code.
I will let you know when I tweak the code. Would be very appreciated if you can test that on your machine then.

That sounds good, thanks for taking a look 👍

fwiw, do you have some special setup for plotting in your startup script ?

Nope.

Installed Juliapro with the same Julia version (1.4.1) to test this, and it works
Status C:\Users\asimd\.juliapro\JuliaPro_v1.4.1-1\environments\v1.4\Project.toml
[c52e3926] Atom v0.12.10 ⚲
[7073ff75] IJulia v1.20.0
[e5e0dc1b] Juno v0.8.1 ⚲
[442fdcdd] Measures v0.3.1
[4722fa14] PkgAuthentication v0.1.2
[91a5bcdd] Plots v1.0.14
[44d3d7a6] Weave v0.9.4
Any ideas how this differs from my other installation? Is a fresh start the only way?

I'm still on a way to find a solution, but here is my understanding:

the error you faced seems happen if this method gets called
but I found on my environment (macOS and on Weave mater) that doesn't get called, rather, one of these "unspecialized" display methods seems to get called (I've not detect which one gets called yet) for Plotly images, somehow

Will take another look on this when I have time.

Any updates on this? Is this because I'm on windows or something?


Formatting not kept on copy+paste

Azure Data Studio Version: 1.48.0 + 1.49.0-insider
OS Version: Win 11 Home 22H2

Steps to Reproduce:

Commit formatted html to cell (nvarchar(MAX))
Copy cell text and paste into editor -> text spacing will be all messed up. If doing the same in SSMS it works fine. Formatting is maintained.

How field actually looks (hovering over field in results pane):

How it looks after pasting into IDE:

Same as issue #16915 but I was unable to get it re-opened. More info there.

Does this issue occur when all extensions are disabled?: Yes/No

Also, is there a way to just edit the field using the built-in editor? I can't find a way to do this.
Thanks


Include arch in ubuntu/debian repo instructions

See https://github.com/allinurl/goaccess/issues/2321#issuecomment-1129074851

Merged. Thank you!


Hacktoberfest

Hacktoberfest is an event organized by Digital Ocean. Anyone who has registered to Hacktoberfest and sends 5 PRs resolving issues marked with the label 'hacktoberfest' gets a T-shirt from Digital Ocean. Its quite famous, especially in India. I think its a good way to increase Intermine's outreach through this. The only thing to do from our side is mark the issues we need help with 'hacktoberfest' label :)

I love Hacktoberfest! I've been planning to mark up some issues with this tag soon  primarily bluegenes / clojure / js related ones. @nupurgunwant I wonder if you should have a word with @julie-sullivan about whether there are any simpler python client issues that we could add the tag to?


Material CSS included after component style causes cascading problems

Bug, feature request, or proposal:
Material CSS is loaded after the component's style which makes it more specific. This becomes an issue when using ng-deep to style child components.
What is the expected behavior?
The Material CSS should be loaded before the component's style.
What is the current behavior?
The Material CSS is loaded after the component's style.
What are the steps to reproduce?
Simple ng-deep example: https://stackblitz.com/edit/angular-material2-issue-mkwnum?file=app%2Fapp.component.ts
This behavior does not occur when a material 2 element is used before because this (sort of) preloads the style.
I encountered this in a scenario where depending on a user's login status, a mat-button would be present in a header component. If the user was logged in, the mat-button would make sure the style was loaded before my routed component's style. This made my routed component's style have higher specificity and be applied. When the user is not logged in, the material style is loaded after the component and stops the routed component's style from being applied.
Minimum reproduction of this: https://stackblitz.com/edit/angular-material2-issue-8rmpmc.
What is the use-case or motivation for changing an existing behavior?
To prevent issues with specificity of rules.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular CLI: 1.7.2
Node: 9.2.0
OS: linux x64
Angular: 5.2.8
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cdk: 5.2.4
@angular/cli: 1.7.2
@angular/flex-layout: 5.0.0-beta.13
@angular/material: 5.2.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.1
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.5.3
webpack: 3.11.0

A potential solution might be ordering the style according to their respective view encapsulation. If the style were to be included in the following order: none, native, emulated; then this problem would not occur.  This is not a material2 solution but I'm willing to take this to the respective repository if this seems like a good idea. Any thoughts?

Closing. As you noted, this is something that is handled at the platform level and Material does not have any control over.  You will need to open an issue in angular/angular to have the conversation there.


IGNITE-20705 Switch user context when reconnecting

https://issues.apache.org/jira/browse/IGNITE-20705
Thank you for submitting the pull request.
To streamline the review process of the patch and ensure better code quality
we ask both an author and a reviewer to verify the following:
The Review Checklist

[ ] Formal criteria: TC status, codestyle, mandatory documentation. Also make sure to complete the following:
- There is a single JIRA ticket related to the pull request.
- The web-link to the pull request is attached to the JIRA ticket.
- The JIRA ticket has the Patch Available state.
- The description of the JIRA ticket explains WHAT was made, WHY and HOW.
- The pull request title is treated as the final commit message. The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
[ ] Design: new code conforms with the design principles of the components it is added to.
[ ] Patch quality: patch cannot be split into smaller pieces, its size must be reasonable.
[ ] Code quality: code is clean and readable, necessary developer documentation is added if needed.
[ ] Tests code quality: test set covers positive/negative scenarios, happy/edge cases. Tests are effective in terms of execution time and resources.

Notes

Apache Ignite Coding Guidelines

@valepakh during manual check I've got this:

You are already connected to the http://localhost:10300 as org.apache.ignite.internal.cli.core.style.element.UiElements$$Lambda$684/0x000000013e43f220@7a55f148, do you want to connect as org.apache.ignite.internal.cli.core.style.element.UiElements$$Lambda$684/0x000000013e43f220@2e2f720? [Y/n]


Add support for project-level and part-level settings

Currently we have only one block of settings that are shared between all projects and files. As @JBEmbedded pointed out, this can lead to confusing behavior if a user thinks they are setting something like the Base Units for their project to Centimeters, then come to find that their units have changed in another project they meant to keep in Inches.
### Tasks
- [x] Create an architecture plan, looking at VS Code and Obsidian's config systems as inspiration
- [ ] Create a way to define user-level settings, project-level settings, and part-level settings
- [ ] Make it possible to read and write these settings from files (#1361 extended)

More relevant research: a substantial number of obsidian power users hate that it defaults to per-vault settings, and that it lacks a way to set global defaults for new vaults (our equivalent is projects).

I've made a Figma mockup flow here. Here's the most important screen from it:

Requirements

[ ] Make settings into a modal (but keep the routing functionality)
[ ] When entered from /home, the modal will only show one tab for "User"
[ ] When entered from /file/[id], the modal will show three tabs: User, This Project, and This Part, with This Project selected
[ ] Editing the User tab saves only changed settings to the App Data directory as settings.json, and is used as the setting value if no overrides are set for This Project
[ ] Editing the This Project tab saves only changed settings to the project's directory, and is used as the setting value if no overrides are set for This Part
[ ] Editing the This Part tab saves only changed settings to the same directory as the currently-opened part within a [id].settings.json file, and is used at the setting value.
[ ] Editing a setting via the command bar from Home changes the User-level setting
[ ] Editing a setting via the command bar from a file changes the Part-level setting if possible, Project if not, and User if Project is not allowed.
[ ] Theme will be the first setting that is only able to be set at the User level

Starting implementation of this now, here's my plan.

I'm planning on storing the settings in a tree-like object where the nested objects are categories and subcategories, and leaf node objects are settings.

This tree will be only one level deep for now, no subcategories.

The leaf node objects must have at least a default value provided by Modeling App, but can have overrides at the user, project, or part level.

For now I think I'll allow any setting to be overridden for each level, but in future I think we may find that some settings don't make sense to be set at all scope levels (I mentioned theme in a previous comment), and we'll want to make that more restrict-able.

An example
Here is an example settings object (the context of settingsMachine) after reading in the default, user, project, and part-level settings files:
const settings = {
  units: {
    length: {
      default: "millimeters",
      user: "inches",
      part: "millimeters",
    },
    angle: {
      default: "degree",
      project: "radians",
    },
  },
  editor: {
    mouseControls: {
      default: "Zoo",
    },
  },
}

In the example above, the user has the following settings files on their desktop app. Note that these will likely be .json files, but I'm showing them as JS settings constants for comparability to the object above:
in $APP_DATA/settings.json:
const settings = {
  units: {
    length: "inches",
  },
}

in <some-zoo-project-dir>/settings.json:
const settings = {
  units: {
    angle: "radians",
  },
}

and in <some-zoo-project-dir>/<part-name>.settings.json:
const settings = {
  units: {
    length: "millimeters",
  },
}

So the settings are applied as follows:

No overrides are saved for mouseControls, so we use the default "Zoo" value
A project-level override is provided for units.angle, so we use "radians" instead of the default "degrees"
Both a user- and part-level override are provided for units.length, so we use the part-level override that takes precedence.

If we're going to write to and read from a settings file within the current project's directory and using the current part's name, we have to find a way to resolve the fact that currently the settingsMachine doesn't know about the existence of the fileMachine or indeed the currently-open project or part at all.
I think that we need to do the work of #1248 and then we can implement an actor system to avoid this "which machine is truly global" and let them coordinate across each other responsibly.

While this actor system is very compelling from my first forays into implementing it, I think it's impractical to make the changes I outlined above right now. While I believe it would ultimately be less code, it would nearly touch every file in the repo, and require rethinking the entire command bar registration system as far as I can tell.
Instead, I will do solve only the problem at hand by hoisting the FileMachine up to live alongside the Settings and Auth machines, giving Settings access to the currently-opened project and file to allow it to know where to write to.
I will post my findings from exploring the XState V5 actor model into a separate issue, because it will be a substantial refactor if we do it.

After discussing a bit more with @Irev-Dev I'm making two more requirements changes:

We're not going to support Part-level settings in this manner. We will likely allow them in a "cargo-script"-like manner down the line.
We'll write these to .toml files, since we were planning on having a project.toml with project info soon anyway. The settings can simply live under a [settings] section.

A more fine-grained tasklist:
- [x] rework settings config to easily add to settingsMachine
- [x] persist only changed settings to the appropriate files
- [ ] read persisted changed settings from the appropriate files
- [ ] change settings to modal appearance
- [ ] make all settings show up in command bar
- [ ] make level argument skipped and fixed when not in a project
- [ ] make settings modal UI derived
- [ ] Make commands have optional labels, generate these to look better for settings


Craft 4 Support

First of all, thank you for this plugin. Now that Craft 4 is about to be released, do you plan to have the plugin ready by then?

I'm also interested in this. Any plans here? : )

+1 : Be good to see this in Craft 4 soon.

Yes please!

Yes please too, great plugin thanks

+1 this, I tried deploying my own package with the craft version simply set to 4 and now I get this error
Fatal error: Declaration of luwes\codemirror\CodeMirror::createSettingsModel() must be compatible with craft\base\Plugin::createSettingsModel(): ?craft\base\Model in /Users/lopu/things/git/thirstcreative/craft4-starter-template-backend/vendor/luwes/craft3-codemirror/src/CodeMirror.php on line 74

+5 :)

Please bring this to Craft 4

See: https://verbb.io/craft-3

+1
Great plugin that must continue it's road to Craft 4!

Just to chime in, we've added this to our Craft 3 migration project, as people are keen to see this plugin on Craft 4.
If you're no longer developing this plugin, we'd be happy to continue development at Verbb (including updating to Craft 4) - but just let us know if you've got plans to continue things and update to Craft 4! @luwes

hey guys, I don't have any plans to migrate or continue maintenance on this plugin.
feel free to take over! cheers

💰 sold to verbb!
congratulations 🤣
But sounds great, thanks!

@luwes Sounds good! If you want to transfer this repository to verbb or myself engram-design (you might have to add me as a collaborator first, then promote to admin), that'd be great, and we'll get this ported to Craft 4.

Totally amazing news! Thanks Verbb and thanks @luwes for such a useful plugin.

Thanks in advance, I'm a big fan of this valuable addition to CraftCMS

Thanks in advance, I'm a big fan of this helpful field. Looking forward.

@luwes Just wanted to check in about transferring this repo, so we can kick things off?

Thanks @khamer and @engram-design!
Sorry for the misunderstanding, I didn't mean to transfer this repo.
I merged @khamer 's PR adding Craft 4 support. thanks for your patience all!

@luwes Works for me, thanks!

just checking.... you merged PR for Craft 4 support.. but still not avaible in CRAFT 4 . store to download..


Redundant endpoint for editing collection descriptions

Feature Request
Desired behaviour

Why are there separate endpoints for the collection's description? There is already an endpoint for updating the collection as a whole. Not saying we shouldn't, but we don't seem to have this pattern elsewhere.

Think this can just be removed, follow-up to https://github.com/dockstore/dockstore/issues/2342
┆Issue is synchronized with this Jira Story
┆Fix Versions: Dockstore 2.X
┆Issue Number: DOCK-883
┆Sprint: Sprint 57- Frilled shark
┆Issue Type: Story

There are separate endpoints for the organization's description too. Perhaps we should use more patch.

Oops, this is 2.x


Sidbar scrollbar auto hides incorrrectly

When i try to move my mouse over to try and click the sidebar it disappears/hides itself, think the hover area for the sidebar might be wrong i'm not sure, i haven't tried to look into it.
Please check this video for a better explanation:
https://github.com/reactjs/react.dev/assets/87710251/5e0895c2-db28-4ee8-97ac-4f5139e64a0e

Hi @Kathenae . Actually there is an issue with the sidebar in Reference section in the react.dev site.
Issue happening at  : https://react.dev/reference/react/useState

Screencast from 10-12-23 01:13:41 AM IST.webm
Isuue happening :
Every time in the of sidebar in Reference section.

Screencast from 10-12-23 01:14:41 AM IST.webm
Browser and device :
Google-chrome : Version 120.0.6099.71
OS : Ubuntu 22.04.3 LTS


Upload data to OpenNeuro

@Kyota-exe please describe this issue and add the URL to the database on OpenNeuro
Related to #15

I have uploaded the data on OpenNeuro: https://openneuro.org/datasets/ds005025
As I have not published it publicly yet, I believe only people who have been given access have access to the data for now. I have added @jcohenadad as an administrator. I have also tried to add @evaalonsoortiz as an administrator via the email<EMAIL_ADDRESS>but I get the following error:

I would appreciate feedback on the dataset settings and dataset_description.json file, which I created based on the one for the RF shimming 7T project, for example regarding the list of authors, as I do not know everyone who contributed to this project and may be missing some authors.

I was also wondering if anyone knows of an effective way to update the dataset. Ideally, I would like to re-upload the entire dataset every time I make modifications to it, as the dataset is generated from the bids_conversion.py file and I want to make sure I don't miss any changes I made, but I believe the OpenNeuro interface only allows you to remove/add individual files. One possible solution may be to delete all the directories for the subjects and re-upload each directory one at a time every time I want to update the dataset. Unfortunately this method may become cumbersome when we add more sites.

but I believe the OpenNeuro interface only allows you to remove/add individual files. One possible solution may be to delete all the directories for the subjects and re-upload each directory one at a time every time I want to update the dataset. Unfortunately this method may become cumbersome when we add more sites.

see https://docs.openneuro.org/git.html

Thanks! I’ve updated the OpenNeuro dataset with the fix for DREAM FOVs.

I’ve updated the OpenNeuro dataset with the fix for DREAM FOVs.

What upload solution did you end up using?

@Kyota-exe Can you try with my gmail<EMAIL_ADDRESS>

@evaalonsoortiz I believe this worked! Can you confirm that you have access as an administrator?

I just updated the notebook to download data from OpenNeuro instead of Google Drive. For now, the notebook uses the OpenNeuro CLI, and assumes the user already installed and logged into the OpenNeuro CLI. Once the repository becomes public, the user will no longer need to login to OpenNeuro to download the data.
@evaalonsoortiz Could you send me the manual segmentations you did? I will update the bids_conversion.py script to include them in the OpenNeuro dataset. We could just upload them on OpenNeuro directly, but since I will continue updating and using the bids_conversion.py script to regenerate the dataset when I do the DICOM to NIFTI conversion for more sites, I think it may be better to modify this script so that it automatically adds the manual segmentations to the generated dataset so that I can upload the generated dataset to OpenNeuro directly.

I think it might be better to wait until I have the manual segmentations for all subjects, that way I send them to you just once.

I would wait for the automatic processing to be settled, see e.g. #22 (the manual segmentation are not valid anymore)

Human and phantom data are now on openneuro:
https://openneuro.org/datasets/ds005025
https://openneuro.org/datasets/ds005090


[consensus] simplify timestamp guarantee

Motivation
This commit removes the length wait_if_possible function, instead split the guarantees in two places:

round manager guarantees block.timestamp <= round deadline
block store guarantees any block inside has timestamp < current timestamp

Have you read the Contributing Guidelines on pull requests?
Y
Test Plan
Existing tests.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

Ack, at first glance I'm concerned that removing these counters gets rid of debugging information that will be useful in understanding the issues related to timestamps.

this type of errors belong to logs not counters imo. we never used those counters, not even once, in the mean time we got a panic with one of those counters because it's never tested.

Sure, we could do some debugging on the fly to aggregate logs to reverse generate these counters, but given this is a complex mechanism, I think counters are appropriate to get a clear signal and alert on it.
I have looked at it in the past and observed it is non-zero, just didn't take the time to figure out what the issue was.
Personally, I find the logic split harder to understand and also the waiting semantics appear to be different.  For instance, an honest node no longer waits until the previous block's timestamp has passed prior to proposing.  It might even propose a block with a timestamp less than the previous block or one so far in the future that it has no chance of being accepted.
Is there still an issue with a panic on the counters?

Sure, we could do some debugging on the fly to aggregate logs to reverse generate these counters, but given this is a complex mechanism, I think counters are appropriate to get a clear signal and alert on it.

I don't expect any alerts on this type of counters, and not sure if we'd like to debug even it's non-zero if other metrics are healthy.

Personally, I find the logic split harder to understand and also the waiting semantics appear to be different. For instance, an honest node no longer waits until the previous block's timestamp has passed prior to proposing. It might even propose a block with a timestamp less than the previous block or one so far in the future that it has no chance of being accepted.

That's the simplicity of it, it doesn't need to worry about timestamp when generate proposals.
Honest node always waits for the block timestamp to past before inserting into the block store so there's no chance proposed timestamp less than its parent.
Honest node also proposes block when the round starts so there's no chance the proposed timestamp exceeds then round deadline.

Is there still an issue with a panic on the counters?
no, but it shows we have never executed such code path for more than a year.

Fixed linter and added counters and error messages.

:umbrella: The latest upstream changes (presumably 827f8cf7485fd6716e319a4c61ccb0c90df4e569) made this pull request unmergeable. Please resolve the merge conflicts.

@aching a lot of  your concern comes from clock goes backwards which I don't think it's the application's problem to deal with.
rather the TimeService should guarantee a monotonically non-decreasing timestamp view like  Instant::now https://doc.rust-lang.org/std/time/struct.Instant.html

@aching a lot of your concern comes from clock goes backwards which I don't think it's the application's problem to deal with.
rather the TimeService should guarantee a monotonically non-decreasing timestamp view like Instant::now https://doc.rust-lang.org/std/time/struct.Instant.html

I thought about that too, but I think it would not be practical to have a monotonically non-decreasing timestamp.  Imagine if your clock gets set to 10 years in the future.  We don't want to have to wait 10 years until this validator can participate again.  The dynamic clock will adjust faster, I think we just need to adjust our properties to reflect the correct guarantee.

@aching I don't  think we should bother with the  property definition this much, it's easy to add assuming  honest nodes' timestamp is monotonically increasing.
If it goes back 10 years , it  certainly falls into byzantine fault category. similarly if the time goes back so that the node proposes a block with timestamp less than parent block.
Those are all the points of why we have a bft algorithm, byzantine fault is not necessarily malicious, a bug in the OS can cause a byzantine fault too e.g. timestamp goes backwards.

@zekun000, overall looks good.  Can you please resolve the minor comments I made and then we can commit?

@bors-libra r=aching

:pushpin: Commit bf5362a has been approved by aching

:hourglass: Testing commit bf5362ab3bfbce1f1d78e933a1cdaba6dc9fc3fd with merge 002c16c0134b606357887dba3a45fd900f863472...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra r=aching

:pushpin: Commit 2e202a4 has been approved by aching

:hourglass: Testing commit 2e202a40225fef5c3b605d242a4c51e0dbf20f47 with merge bbbbdfbd136ea2544cccabbef9f68c6ddfe653b4...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra retry

:hourglass: Testing commit 2e202a40225fef5c3b605d242a4c51e0dbf20f47 with merge 10ac5672fe6e8d798af5f4c8d29472eb72964f33...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra retry

@bors-libra r=aching

:pushpin: Commit 297ec94 has been approved by aching

:hourglass: Testing commit 297ec9491b0af32c9ab0d8b3af0cc59770a68aba with merge f5ee167b6e95b66da5cf4e59302eb5026813caff...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: aching
Pushing f5ee167b6e95b66da5cf4e59302eb5026813caff to master...


Atom is stuck,  take few minute for its release

[Enter steps to reproduce below:]

Install the package selection-highlight
click on some word in opened document. Error appears immediately

Atom Version: 1.7.2
System: "CentOS Linux
Thrown From: selection-highlight package, v0.1.4
Stack Trace
Uncaught TypeError: Failed to execute 'item' on 'HTMLCollection': 1 argument required, but only 0 present.
At /home/eduardm/.atom/packages/selection-highlight/lib/highlighted-status-view.coffee:20

TypeError: Failed to execute 'item' on 'HTMLCollection': 1 argument required, but only 0 present.
    at TypeError (native)
    at highlighted-status-bar.module.exports.HighlightedStatusView.detach (/home/eduardm/.atom/packages/selection-highlight/lib/highlighted-status-view.coffee:20:14)
    at highlighted-status-bar.module.exports.HighlightedStatusView.destroy (/home/eduardm/.atom/packages/selection-highlight/lib/highlighted-status-view.coffee:28:6)
    at HighlightedAreaView.module.exports.HighlightedAreaView.removeMarkers (/home/eduardm/.atom/packages/selection-highlight/lib/highlighted-area-view.coffee:127:21)
    at HighlightedAreaView.removeMarkers (/home/eduardm/.atom/packages/selection-highlight/lib/highlighted-area-view.coffee:1:1)
    at HighlightedAreaView.module.exports.HighlightedAreaView.handleSelection (/home/eduardm/.atom/packages/selection-highlight/lib/highlighted-area-view.coffee:54:6)
    at HighlightedAreaView.handleSelection (/home/eduardm/.atom/packages/selection-highlight/lib/highlighted-area-view.coffee:1:1)
    at /home/eduardm/.atom/packages/selection-highlight/lib/highlighted-area-view.coffee:27:8

Commands
     -1:03.3.0 core:undo (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "themes": [
      "one-light-ui",
      "atom-light-syntax"
    ]
  }
}

Installed Packages
# User
auto-indent, v0.5.0
autocomplete-go, v1.0.6
build, v0.59.0
builder-go, v1.0.0
cursor-history, v0.5.9
environment, v1.2.0
file-icons, v1.7.4
go-config, v1.1.4
go-find-references, v1.2.3
go-get, v1.0.3
go-plus, v4.1.0
go-rename, v0.3.0
gofmt, v1.1.6
gometalinter-linter, v1.1.0
gorename, v1.0.2
highlight-line, v0.11.1
highlight-selected, v0.11.2
language-docker, v1.1.6
language-protobuf, v0.5.0
linter, v1.11.4
linter-golinter, v1.2.0
minimap, v4.22.1
minimap-git-diff, v4.3.0
minimap-highlight-selected, v4.4.0
minimap-linter, v1.1.1
minimap-pigments, v0.2.0
minimap-selection, v4.4.0
nav-panel, v0.0.11
navigator-godef, v1.0.2
pigments, v0.26.0
pretty-json, v1.0.3
selection-highlight, v0.1.4
symbol-gen, v1.0.0
tester-go, v1.0.4

# Dev
No dev packages

It seems a duplicate https://github.com/richrace/highlight-selected/issues/121
I think it should be reported only in that repo.
Generally speaking, you may read the recent post about issue guidelines.
Finally, please, feel free to talk about it on the official Atom forum at https://discuss.atom.io.

Anyway it's reproducing in another OS(CentOs)
thanks

Thanks @elasti-eduardm for the heads up on this. I've published a patch for this now.


can't load float into bigquery by StreamWriter

If my proto schema contains float type, I can't load it into bigqery by StreamWriter. I check code, I found that there is not FLOAT type in BQTableSchemaToProtoDescriptor.java.
Thanks!

Hi @qcli ,
I see Double type in the file. According to the data types defined in BigQuery documentation, FLOAT64 is a Double precision datatype.
Do you have any code failures due to the missing float data type?
If yes, can you provide a code snippet to reproduce the issue?

Closing due to inactivity. Feel free to re open if issue persists.

Hi @qcli ,
I see Double type in the file. According to the data types defined in BigQuery documentation, FLOAT64 is a Double precision datatype.
Do you have any code failures due to the missing float data type? If yes, can you provide a code snippet to reproduce the issue?

Hi Neenu，
I'm sorry I missed your reply. Now I've changed all the float in my proto schema to double, and it works fine. It means that if I want to use StreamWriter, I can't define float type in my proto schema.


What's the status of this fork?

Hi @tjchambers, I just noticed your fork of rspec-kickstarter. As the last commit to seratch/rspec-kickstarter was back in Jan 2016, would it be correct to say that it is better to use your fork now?
In particular, I'm interested in seeing this issue in the seratch/rspec-kickstarter repo resolved https://github.com/seratch/rspec-kickstarter/issues/7. I was thinking of tackling it myself - has it been something you've looked at?

I am actively using this fork myself. It shares some of the original mode of discovery, but a much different mode of spec creation (more complete IMHO).
I have not looked at that issue, and it is not something I need, but would welcome any contribution.

BTW I am using this on a number of other projects where test coverage is spotty, so am making adjustments/enhancements to make it more widely useful.


Add CSpell

Related issue(s)

Resolves #681
Description
Summary of changes

Dependency additions / changes

Test additions / changes

Checklist

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[ ] I have linked this PR to the issue(s) that it resolves.
[ ] I have reviewed the changes on GitHub, line by line.
[ ] I have ensured all changes are covered in the description.

Additional context

Note that the json file also includes words which are misspelt -- This is intentional and once they have been removed and corrected, the PR will be ready for review

To print out all of the unknown words, one can install the cli and run:
cspell-cli "crates/**/*.{md,rs}" --words-only --no-summary --no-progress --unique

A large group of the spelling mistakes fall into two categories:

Mispelled words (Seems to be about half of the list)
incorrect casing; for example myfunc is seen as one word, but my_func or myFunc will be recognised as two words

Then we have domain specific words like acvm, acir and rustc which should indeed be added to the list.

In the worse case, if we keep adding new words to the codebase one will need to keep updating the list.
The upside is that we no longer need to manually check for spellling mistakes from each contributor and the introduction of a new word will immediately be obvious (warranting an explanation)

Does this PR fix any issues with the codebase? I'm somewhat dubious of the need for a spellchecker. I don't see it solving any issues and it just adds an extra CI step.

We do have quite a lot of spelling mistakes -- if you check the cspell.json file, I have added the words which were misspelled into the json file to indicate them and to have the CI pass.
The top ones are spelling mistakes and in other places, it is because we are not using the snake case to correctly separate two words for example.
Getting it in the CI is a pain -- we can also opt to make them warnings in the PR instead of errors, though I don't expect us to add a bunch of new unknown words, so I'm up for trying it out and seeing how often it catches new spelling mistakes introduced by a PR

If it is not too much trouble then, I think this PR should also fix the spelling mistakes it finds rather than committing an ignore file with many mistakes we do not want ignored. If it is too much work, you can pass it off to someone else on the team.

If it is not too much trouble then, I think this PR should also fix the spelling mistakes it finds rather than committing an ignore file with many mistakes we do not want ignored. If it is too much work, you can pass it off to someone else on the team.

I agree -- to clarify, this PR is not ready while we are ignoring spelling mistakes. This was just done so that the CI can pass and we are aware of the list of problematic words.
I then removed a word from the list to check that the CI failed and now it's a matter of correcting the spelling mistakes present in the code and removing them from the Json file. I will do this and then re-request your review :)


Caching in pipe cause bug after change locale in case of interpolate params

I'm submitting a bug  (check one with "x")
[х] bug report => check the FAQ and search github for a similar issue or PR before submitting
[ ] support request => check the FAQ and search github for a similar issue before submitting
[ ] feature request

Reproduction of the problem
Translations = {"hello with interpolation": "hello with interpolation, number={{number}}"}
Template: Interpolation Pipe: {{ 'hello with interpolation' | translate:{number:42} }}
On page load call translateService.use('en');
Then call  translateService.use('other locale');
Current Behavior: page still contains hello with interpolation, number=42
Expected Behavior: page cotains text in different locale
Seems in TranslatePipe#transform it is needed to check locale in
        // if we ask another time for the same key, return the last value
        if(equals(query, this.lastKey) && equals(args, this.lastParams)) {
            return this.value;
        }

or simply remove this block.
Please tell us about your environment:

ngx-translate version: 6.0.0

Angular version: 2.x.x

Browser: [all]

Retest issue and can't reproduce. Sorry for inconvience.


[manila-csi-plugin] Lots of RBAC issues when manually installing without helm

/kind bug
What happened:
I tried to install manila-csi-plugin exactly according to the documentation, but I got lots of permission/RBAC errors afterwards, which I could only circumvent by applying the cluster-admin role to the service account openstack-manila-csi-controllerplugin.

I could start the nodeplugin container of the controllerplugin, when applying "system:persistent-volume-provisioner"
I could never start the snapshotter container. I get lots of:

github.com/kubernetes-csi/external-snapshotter/pkg/client/informers/externalversions/factory.go:117: Failed to list *v1alpha1.VolumeSnapshotClass:volumesnapshotclasses.snapshot.storage.k8s.io is forbidden: User "system:serviceaccount:kube-system:openstack-manila-csi-controllerplugin" cannot list resource "volumesnapshotclasses" in API group "snapshot.storage.k8s.io" at the cluster scope
E0625 16:35:49.814460       1 reflector.go:126] github.com/kubernetes-csi/external-snapshotter/pkg/client/informers/externalversions/factory.go:117: Failed to list *v1alpha1.VolumeSnapshotContent: volumesnapshotcontents.snapshot.storage.k8s.io is forbidden: User "system:serviceaccount:kube-system:openstack-manila-csi-controllerplugin" cannot list resource "volumesnapshotcontents" in API group "snapshot.storage.k8s.io" at the cluster scope

What you expected to happen:
Should work without errors
How to reproduce it:
Anything else we need to know?:
Environment:

openstack-cloud-controller-manager(or other related binary) version:
OpenStack version:
Others:

I guess that https://github.com/kubernetes/cloud-provider-openstack/blob/master/manifests/manila-csi-plugin/csi-controllerplugin-rbac.yaml deploys the role config always in the default namespace.

@cohomology In documentation its already mentioned to first deploy rbacs of both nodeplugin and controller plugin.
kubectl create -f csi-controllerplugin-rbac.yaml
kubectl create -f csi-nodeplugin-rbac.yaml ,
Ref: https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/using-manila-csi-plugin.md
Are you saying you are facing issues after that as well?

Yes, because I (as a total beginner) deployed accidently into another namespace. The rbac files are only working for the default namespace. Finding this error is not trivial for a non-expert.

@cohomology good to see, issue is resolved.
Your contributions to update the documentation to make it better is much welcome.

/close


Create the UI for displaying summaries.

This page should display the keywords and summaries. It should also display the extracted text at the top. Maybe add some relevant plots at the bottom.

To be more descriptive:

Display the extracted text in a card that can be toggled open/close. Have it closed initially.
Display the summaries along with the corresponding keyword in cards stacked vertically. Make each summary toggled close by default, so only the keyword is displayed. This will help when there's a lot of extracted keywords.


Reconsider use of PSMTabBarControl

With the native tab support of Cocoa it might be worth considering using that instead of the custom PSMTabBarControl solution. However, #1 - Project Context, might still want a custom solution.

A potential removal is tracked in #43

I think we can close this with https://github.com/subethaedit/SubEthaEdit/pull/73.

I think we can close this with #73.


Kubeflow Pipelines V2 does not work with artifacts

When running simple code with KFP V2 in the notebook:
import kfp
from kfp.v2 import dsl
from kfp.v2.dsl import component, OutputPath, Artifact, Output

@component(
    packages_to_install=['transformers'],
    output_component_file='download-comp.yaml',
    base_image='python:3.9.13'
)
def download_artifacts(repo_id: str,
                       revision: str,
                       output_file: Output[Artifact]):
    pass

@dsl.pipeline(
  name='chatbot-pipeline',
  description='The pipeline to create and deploy the chatbot model',
)
def my_pipeline():
    download_artifacts_op = download_artifacts(repo_id='facebook/detr-resnet-50',revision='c783425425d573f30483efb0660bf6207deea991')

client = kfp.Client()

client.create_run_from_pipeline_func(
    my_pipeline,
    namespace="admin",
    mode=kfp.dsl.PipelineExecutionMode.V2_COMPATIBLE,
    arguments={})

The log in the Pod:
I1016 19:06:23.565782      43 env.go:30] cannot find launcher configmap: name="kfp-launcher" namespace="admin"
I1016 19:06:23.565945      43 launcher.go:144] PipelineRoot defaults to "minio://mlpipeline/v2/artifacts".
I1016 19:06:23.566163      43 cache.go:143] Cannot detect ml-pipeline in the same namespace, default to ml-pipeline.kubeflow:8887 as KFP endpoint.
I1016 19:06:23.566179      43 cache.go:120] Connecting to cache endpoint ml-pipeline.kubeflow:8887
F1016 19:06:25.594237      43 main.go:50] Failed to execute component: unable to get pipeline with PipelineName "pipeline/chatbot-pipeline" PipelineRunID "168f2ed7-39b6-40a8-9130-9b9b0a752db8": Failed GetContextByTypeAndName(type="system.Pipeline", name="pipeline/chatbot-pipeline")

Kubeflow bundle - 1.6 (full bundle) + mlflow, microk8s 1.22
Am I doing something wrong?

I haven't tried using v2 yet so these are guesses.
I think the kfp.v2 package is meant to use some yet-to-be-released backend features (aimed for kf 1.7).  So out of the box, it might be trying to access those.  Looking at this guide, I see they import only component from kfp.v2.dsl (and use the kfp.dsl.pipeline, not the v2 version).  So it might be that you're using the v2 compiler atm, and submitting that v2 pipeline to our v1 backend.  They also mention using the mode=...V2_COMPATIBLE arg.  I think that's telling the 1.7 compiler to compile in v2's syntax, but it might mean the other way around and might help you here.
As far as I know, kfp hasn't released for wide use the v2 backend (I think they plan that for the next release), although I believe the images we deploy atm do support it.  I expect there's some feature flags that would enable it, but I haven't looked into them.


Getting error while running the spec-fuzzer

I'm getting an error as follows:
ERR:    TNT 1052361 at position <0xffffffffc0739083,0xffffffffc0739083>
Any hints on how to debug this ?

Just FYI,
I'm getting the following warning and it seems to be related to intel-pt
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]


fix logrus path according to case-sensitive problems which described …

…on logrus page repo https://github.com/sirupsen/logrus

please see issue:
https://github.com/sirupsen/logrus/issues/451

Seems like it enough to specify logrus into godpes file in uppercase.
Thank you.