Add ability to hide/show "Save as..." panel/components at right of Results Pane

I frequently write SQL scripts that output results from several different queries, and they get displayed successively in the Results Pane.
On the right side of the Results Pane is a single-column panel of icons that allow the resulting data to be saved to different formats, such as CSV, Excel, and JSON. This panel is repeated on the panel for each result set displayed. When my results have fewer than 4 rows, this panel of icons is taller than the data's table format, so it makes that particular pane of data have wasted white space below it, and may cause the next result set to reach the point where the pane needs to be scrolled to see it. This makes what was a quick, on-screen display  in SSMS be something that requires interaction to see all of the data.
I would like─and, therefore, suggest─that there be an option to either hide this entire panel of icons, or to be able to select which are displayed all the time. If needed, add the "Save as..." options to a context menu for the Results Pane, or have a single "Save as..." icon that opens a context menu of formats to choose from.
Otherwise, so far, I'm liking ADS. I really like being able to change the connection for an editor tab that's already open to test/run the code on another server/database. Thanks!

I watched the video of your solution, @lewis-sanchez, and my only complaint is that it removes the ability to actually do the "Save as..." action. This doesn't affect me, since I don't use it, but it means that anyone who does use the functionality has to put up with the wasted space. That's why I suggested either adding a context menu to do the same thing (you don't see anything until you right-click on the pane) or make it a single button that gives you the list of destination formats to choose from (and having one button won't take up more space than a single row of output). Personally, this doesn't seem like the right solution.

@lewis-sanchez, I watched the video of your solution, and it appears to do exactly what I asked for! I didn't realize until a few minutes ago that you could right-click on the data in the Result Pane and get the context-menu I suggested (I had only right-clicked on the open space and gotten nothing). Thanks!


How to persist a pytorch lightning module that depends on external data?

❓ Questions and Help
What is your question?
Hi! We're using pytorch lightning to train language models and transformers from scratch. This includes training tokenizers and applying them text data, resulting in binarized data.
The way we've structured the process is to train a tokenizer, apply it to text data (coupling the binarized data and the tokenizer), and apply a language model on the binarized data.
Since the language model depends on the tokenizer (number of tokens, special tokens, et.c.) the pytorch lightning model needs a tokenizer/vocabulary as part of its hparams. This does not play very nicely with the way hparams and loading works: If we transfer the model from one computer to another, we would need to move a tokenizer to the exact same path on the other computer.
Generally i guess the problem boils down to this: If the inner pytorch modules of the pytorch lightning module depends on some kind of external data (e.g. a vocabulary, or a random sparsity graph), and you then wish to share the pytorch lightning module, we can't find an easy way of doing this.
on_load/save_checkpoint does not work, since they take effect after the model has been initialized, whereas we would like to persist data to the initialization logic in itself.
Is there an elegant way to do this in pytorch lightning?

good points. been thinking about this as well.
can you share pseudocode so we can come up with the changes to the API?

FWIW, we did find a workaround that makes the module self-contained, but it's not very pretty. It is built on the kwarg workaround, adding a separate hparams only classmethod make responsible for tokenizer initialization and a separate classmethod load responsible for loading from checkpoint.
class Transformer(LightningModule):
  def __init__(self, hparams, tokenizer=None):
    ...
    # set the tokenizer (tokenizer loading logic outside of Transformer)
    self.tokenizer = tokenizer

    # Initialize the pytorch model (dependent on tokenizer)
    self.transformer = torch.nn.Transformer(
      dimension = hparams.dimension,
      num_embeddings = self.tokenizer.vocab_size,
      padding_index = self.tokenizer.padding_index,
      ...)
    def on_save_checkpoint(self, checkpoint):
        checkpoint['tokenizer'] = self.tokenizer

    @classmethod
    def make(cls, hparams):
        # Essentially a wrapper around init responsible for tokenizer loading
        tokenizer = get_tokenizer(hparams)
        return cls(hparams, tokenizer=tokenizer)

    @classmethod
    def load(
            cls,
            checkpoint_path,
            map_location = None
            ):
        # Copied from load_from_checkpoint, but we extract tokenizer (saved during on_save) and make it a kwarg.

        if map_location is not None:
            checkpoint = torch.load(checkpoint_path, map_location=map_location)
        else:
            checkpoint = torch.load(checkpoint_path, map_location=lambda storage, loc: storage)

        args = []
        tokenizer = checkpoint['tokenizer']   # extract the tokenizer
        kwargs = {'tokenizer': tokenizer}      # Make it a kwarg to _load_model_state

        model = cls._load_model_state(checkpoint, *args, **kwargs)
        return model

This is obviously particular to our use case, but I think it is possible to polish it a bit by, for example, making it possible use a saved kwargs-dictionary in load_from_checkpoint.

If we transfer the model from one computer to another, we would need to move a tokenizer to the exact same path on the other computer.

It's a completely valid requirement. That's why people wrap up their training experiments into Dockerfiles. A different example is that Polyaxon supports this with YAML scripts that help you define running environment.


[REST API] Inconsistent error message format

Environment details:
Irrelevant
Steps to reproduce the issue:

Invoke different REST API and check the error messages returned.

Provide the expected results and outputs:
A unified format of error

Provide the actual results and outputs:
Some error responses only contain "error", not "code", like:
{"error":"Malformed request, did you specify a bluemix namespace?"}

Additional information you deem important:

Just want to clarify which property should be used to check whether there is an error? It seems that we should check "error", not "code", right?

code refers to the TransactionId your Transaction had and is mainly useful for the operations team to debug user issues. If you want to check if stuff went wrong, error will be sufficient.

Any error that results from the API controller (backend) will always have both error and code. Errors that result from frontend routers will not contain code.

Thanks for the clarification.


Support API Key Auth

DB2Rest needs to support API Key Auth. The source of API Key auth data can be

file system in this case the user is responsible for creating the API Keys
external API that provides the API Keys and the mappings (In this case this external end point should be polled periodically to refresh the configuration). The config can also be cached in an in memory cache like apache ignite which also allows overflow to file and running sql to query.

The configuration is shown below :
`
name: db2rest-security
resourceRoles:

resource: "/v1/rdbms/pgdb/actor/**"
method: post
roles:

role2
role3
role4

resource: "/api/v2/host"
method: get
roles:

role2
role3
role4

excludedResources:

resource: "/v1/rdbms/**"
method: get
resource: "/v1/rdbms/pgdb/factor"
method: post
resource: "/v1/rdbms/**"
method: put
resource: "/v1/rdbms/**"
method: delete

apiKeys:

key: apikey1
roles: [role1,role6]
active: true
key: apikey2
roles: [role1,role4]
key: apiKey3
roles: [role3]
`

If active attribute is missing then the default value is false in which case DB2Rest should not allow the call.

@kdhrubo
I have a question: where to get the username while authenticating?
An AuthProvider should return the UserDetail object, which has a property username.
I do propose to enrich the apiKeys config by adding the username property.

When API key is created there is no concept of username. Treat api key as username.
In case of validation we have to look into the store (in this case file.store).to verify that API key is present otherwise reject the request.


Hierarchical training using multi-agents - Feature Request

The implementation of hierarchical training inside TT will be a crucial part of implementing profitable strategies.
It may be the difference between winning and losing strategy.
By implementing hierarchical training, the training decisions can be grouped into different levels of granularity (e.g. timeframes based - long/short term, etc..) this way a group of agents can cooperate and create a powerful combination of trading decisions capable of executing profitable strategies.
See, for example, this sample Ray hierarchical training strategy
https://github.com/ray-project/ray/blob/master/rllib/examples/hierarchical_training.py
Also a good reference - https://arxiv.org/pdf/1811.09549.pdf
Points:
4.2 Hierarchical decision making
4.3 Algorithmic, regulatory and computational challenges
5 Hierarchical reinforcement learning scheme

no need to implement this from scratch - it is already available in Ray rllib and it is distributed

@123mitnik did this go anywhere?

This is not within the scope of what the library aims to do. If you want to think about this type of training put try to explore the ray library.


Fixed bug in ProbingHashMap - indexOf method could cause exception

Fixed bug in ProbingHashMap - indexOf method could cause indexOutOfBoundariesException if the hashcode of a key was less than zero. I've added Math.abs(key.hashCode()) to prevent this.

Thanks again!


Investigate performance of parallelization

Computing the erasure coding of each row and column, along with computing the namespace Merkle trees, can be done in parallel. Investigate the potential performance gains of doing so.

I made a quick and dirty implementation that can be found here, and the benchmarks can be found here
On an 8 core cpu, this implementation gets roughly 4 times faster

I should have a chance to give the nmt library a similar treatment sometime in the next few days.

I ran some more benchmarks for the nmt generation portion of hashing the data availability header, and fortunately (unfortunately?) everything went as one might expect. This task is even more parallelizable than generating the erasure data, but this implementation doesn't get the full benefits for such a parallelizable load.

~6x performances gains on a 8 core cpu for max width data square, with very little overhead introduced.
Summary: These unoptimized implementations show that there are easy options for performance gains should that be required.
Write-up w/ code and traces: https://github.com/evan-forbes/rsmt2dbench
Implementation for multi-threaded nmt generation: https://github.com/evan-forbes/lazyledger-core/tree/evan/multithreaded-rsmt
Thanks to @adlerjohn for the fun the idea
Shoutout to @musalbas and @liamsi for writing easy to read code
As for further investigation

it might be useful to run pprof on the current implementations and see if there are any low hanging fruit
see how fast the current implementations allow for creating proofs

Thanks for this @evan-forbes, this looks like great work.

@evan-forbes, I didn't see this before. Nice graphs! Curios, how did you generate those?

A few ideas towards parallelizing(it is getting annoying to wait for tests to generate the compute the square already):

Parallelization should be enabled by default
With runtime.NumCPU() workers/routines

There is no point in having more than that for CPU heavy load.

Amount of workers should be optionally configurable
We should spawn workers globally for any amount of squares

If ten squares are getting re/computed simultaneously, they won't spawn their workers but will rely on the global ones.
Instead of having some singleton square processor, we can rely on global vars and init, spawning workers for us. If designed carefully, there won't be any issues with the global state.
The main advantage of this approach is that we won't need to modify the API.

Additional thoughts regarding parallelization: whether rsmt2d erasure coding/NMT root computing should be done in parallel largely depends on how parallelized the user of the library is. For example, if only a single block is verified at a time, then indeed there will be gains if rsmt2d is parallelized. But if multiple blocks are verified in parallel, then the CPU will already be saturated.
That being said, there's always the case that once you've completed IBD and are at the tip, you'll be verifying one block at a time, and in such cases rsmt2d being parallelized is a requirement to saturate CPU cores.

Curios, how did you generate those?

just Google sheets iirc

Users can potentially rely on Go's scheduler to distribute the load during sync, e.g., 10 blocks sync and reconstruction for each runs in its own routine. This is the simplest approach, but it has its downsides:

No control over how and in what way processing is going for the user

Indeterministic ordering of the block processing. Scheduler picks routines pseudorandomly.
Passing complexities to the user that can be solved more efficiently in the lib itseld

Inability to parallelize one block, as you mentioned
Performance implications

Allocating a new routine per block instead of having a constant amount of routines.
More context switching for the scheduler

Additional thoughts regarding parallelization: whether rsmt2d erasure coding/NMT root computing should be done in parallel largely depends on how parallelized the user of the library is. For example, if only a single block is verified at a time, then indeed there will be gains if rsmt2d is parallelized. But if multiple blocks are verified in parallel, then the CPU will already be saturated.

The best long-term approach I would propose is to have rsmt2d lib also do some form of concurrency and parallelization on the axis level. Writing some small global engine that processes axises and does not even aware of the square notion. It can even be implementing the Codec interface, but I have to think about it more.

I was going through the code for another reason and realized that it wouldn't be possible to do this on the Codec level, unfortunately. Codec is strictly sync interface, and the only way I see rn to make parallelization of repair by axis is to change solveCrossword method.

we can probably change this issue to be about actually implementing parallelization, with the above feedback from @adlerjohn and @Wondertan, instead of only investigating it.


Add peer review URL to API

A simple test for the peer review URL.

Hi @ryscher I'm now seeing this failure in the travis tests. Can you look into why or add a fix?
  1) StashApi::DatasetsController#show shows the peer review URL when the dataset is in review status
     Failure/Error: expect(hsh['sharingLink']).to match(/http/)
       expected nil to match /http/
     # ./spec/responses/stash_api/datasets_controller_spec.rb:321:in `block (3 levels) in <module:StashApi>'

This test should work once the corresponding stash PR is merged: https://github.com/CDL-Dryad/stash/pull/239

Looks good Ryan.  I think tests passed.


Added Acknowledgements Doc

Since Fred was integral to the creation of this code pattern but has no commits I thought we should add this optional doc to give him credit.

LGTM

@djalova Since the commits are squashed I can't check, but did you do most of the work on this model? I know Nick started the work and you finished it.

@ajbozarth Yeah, Nick created a base template for all the MAX models and I worked on this specific model.

thought so, @stevemart given Daniel is a co-author on this project I think this is fine as is. merging

👍


Index/Glossary

Need a clickable index at the top of the README so users can jump straight to the method they're looking for.
Example:
.between() - Return a number, or array of numbers, within a given range.
.boolean() - Return a boolean or array or booleans

Added a clickable table of contents in #17.


Cannot read properties of undefined at telos mainnet #1365289

Currently if started from block #1365289 we crash with the following exception:
node:internal/event_target:1033
  process.nextTick(() => { throw err; });
                           ^

TypeError: Cannot read properties of undefined (reading 'blockInfo')
    at HyperionSequentialReader.collectDelta (file:///home/guille/full-history-node-mainnet/telosevm-translator/node_modules/@eosrio/hyperion-sequential-reader/lib/esm/reader.js:512:31)
    at HyperionSequentialReader.handleWorkerMessage (file:///home/guille/full-history-node-mainnet/telosevm-translator/node_modules/@eosrio/hyperion-sequential-reader/lib/esm/reader.js:457:22)
    at Worker.<anonymous> (file:///home/guille/full-history-node-mainnet/telosevm-translator/node_modules/@eosrio/hyperion-sequential-reader/lib/esm/reader.js:437:22)
    at Worker.emit (node:events:517:28)
    at MessagePort.<anonymous> (node:internal/worker:243:53)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:757:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)

Block info:
{
  "timestamp": "2018-12-21T17:00:03.000",
  "producer": "blindblocart",
  "confirmed": 0,
  "previous": "0014d528d0e56853bc86d313807dfe5fea33240adc3735667f8d378dc1be8dbd",
  "transaction_mroot": "ed11e999aa8583f4e7bb19587ca6b5b8932161dde36b86096390c12d5aa210fb",
  "action_mroot": "5df64537dddb180bee026e8a038be43f50f11f49771ab8df2d61502031b093c2",
  "schedule_version": 20,
  "new_producers": null,
  "producer_signature": "SIG_K1_KjcBr7YGXHHBmTidGv8xVHsbvgdtTYozead1VoqxYos9xEJa6jC971kqd2ECsZPN7SHPfMr3jwNMppLwYURqNrh89QPof1",
  "transactions": [
    {
      "status": "hard_fail",
      "cpu_usage_us": 260,
      "net_usage_words": 0,
      "trx": "5c7ba03c6544f4a86a0a0e18982155ab6420f923e622eb35fc65d614583a8b1f"
    }
  ],
  "id": "0014d529bda71a556537d12b38b6443b1e613cc23c7e867b700195fc875e18a6",
  "block_num": 1365289,
  "ref_block_prefix": 735131493
}

A v1 history query for the hard_fail tx returns not found:
{
  "code": 500,
  "message": "Internal Service Error",
  "error": {
    "code": 3040011,
    "name": "tx_not_found",
    "what": "The transaction can not be found",
    "details": [
      {
        "message": "Transaction 5c7ba03c6544f4a86a0a0e18982155ab6420f923e622eb35fc65d614583a8b1f not found in history and no block hint was given",
        "file": "",
        "line_number": 1,
        "method": "get_transaction"
      }
    ]
  },
  "query_time_ms": 130.411
}

As kevin mentioned:
Kevin Heifner, [11/16/23 12:18 PM]
v1 history does not store hard_fail trxs
Kevin Heifner, [11/16/23 12:18 PM]
hard_fail means neither the trx nor the onerror executed so there are no side-affects to state.
So we can probably just safely ignore blocks like this, error was on collectDelta function so must add some logic to ignore.


Stratification Factor Feature

This PR contain all changes of adding stratification factors feature from front-end and back-end. This PR also contains backend integration test cases. We will create separate PR's for backend unit test cases and frontend test cases. The details of the tickets covered in this PR are mentioned in the document.

The backend build is failing, please check (@Yagnik56?)


chore: parse all the response items from MeijuCloud for get_device_info

Summary by CodeRabbit

New Features

Enhanced device information with additional attributes like description, active status, active time, master ID, WiFi version, enterprise, is other equipment, attributes, room name, Bluetooth MAC, Bluetooth token, is Bluetooth, bind type, ability, name changed, support WOT, template of TSL, shadow level, smart product ID, and brand.

Documentation

Updated docstrings for better clarity on API URL, headers, input, and response structure.

Tests

Added multiple assertions in tests to verify new device attributes, improving test coverage and robustness of device information retrieval functionality.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 35.95%. Comparing base (b364248) to head (18774d7).
Report is 12 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #231      +/-   ##
==========================================
+ Coverage   32.83%   35.95%   +3.12%
==========================================
  Files          80       81       +1
  Lines        6981     7064      +83
==========================================
+ Hits         2292     2540     +248
+ Misses       4689     4524     -165

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

Please improve tests to check the parse process

thanks for your review comments, add test done, please help to review and check the testcase info.

@chemelli74 @rokam
I'm sorry for the delay these days, any comments with it?  especially for @chemelli74 , we should have a agreement with it, for this PR and also for fututure PRs.
in addition, these response info is json format from cloud server, so all the types should be json types, and NOT python types. for example, json null vs python none.
thanks.

@chemelli74 @rokam
I'm sorry for the delay these days, any comments with it?  especially for @chemelli74 , we should have a agreement with it, for this PR and also for fututure PRs.
in addition, these response info is json format from cloud server, so all the types should be json types, and NOT python types. for example, json null vs python none.
thanks.

It's ok for me.

If you guys both think that's fine, go ahead

thanks.


Get ready for laravel 5.4

already done. See https://github.com/rinvex/repository/issues/129

Since this has been asked a lot recently (which is reasonable), I've tagged a new release v2.0.2 with Laravel 5.4 support and it's currently available for use. Next major release v3 which include criteria support, and other awesome stuff still under review and not yet approved for release. Enjoy either of the stable v2.x releases or cutting edge dev-master as you wish :)


Crash on iOS 10

in method didSelectSubRowAtIndexPath,
has an error: property 'subRow' not found on object of type 'NSIndexPath *'. So my app crash.

I am facing same issue, @anhhtbk did you got the solution for this?

In method didSelectSubRowAtIndexPath, first I add a variable long subRow = indexPath.subRow;, after I use subRow instead indexPath.subRow.
I don't understand it work correctly with me. 💃

@anhhtbk Are you using swift 3.0?

Nope. I am using Obj

@anhhtbk Opps, I am working on swift 3.0 and its same issue. unable to access indexpath.subrow. Thanks for help man

Hi, @tejas-ardeshna Did you solve this issue?


Add docker module

Add docker module
https://github.com/Silex/docker.el

Perhaps add it to init.example.el also

Good work! Thanks for your help and this PR.
I will remove dockerfile-mode from lang/data shortly.


Fix ambient .d.ts file import violations.

In issue #81, I explained that imports outside of the declare module scope violated the rules of ambient .d.ts files and the issues that comes with it.
In PR #85, I made some changes to the import order, but I forgot  that relative import where also forbidden.
In #87, @chungweileong94 suggested to change the import style.
This PR refactor generateTypes.ts once again to change the _next-typesafe-url_.d.ts generation with the following changes:

Imports are all in the declare module scope.
DynamicRouter interface generation as been simplified with a compatible import strategy (see below).

interface DynamicRouter {
   '/items/[id]': InferRoute<import('./src/app/items/[id]/routeType')>;
}

Look about right to me👏

Will review tonight, but for now can you add a changeset?
Thanks for the contribution

Sorry, but I am not sure what you mean?

I see something about changeset in the package, I will try to understand what it is...

Yes, this project is using changesets to manage the release + changelog. You can just run npx changesets, and follow the steps to add your change summary.

^^ yep thanks for explainaing
to clarify this would be a patch change
just run pnpm changeset write a description of the change and commit the file it generates

I had a commit with the changeset with a thanks to @chungweileong94.

something came up will not be able to review tonight- hopefully tomorrow
thanks for understanding

No problem. Happy to help. Take care.

looks great thanks so much

now live in 4.0.6!


delay on detect change

To support sftp programs where it uploads the files remotely.
To prevent EOF error.

rizla -delay=5s main.go for example, it will wait 5 seconds for reload and will also skip any changes that will happen in that time in order to not build two executable in the same or near to time, file changer works concurrently.  Please try it @scorpnode with go get -u github.com/kataras/rizla and tell me the results for the sftp.


Wrong examples in calling the methods

Hello
Thanks for this nice package.
According to the examples posted, the calling of the method is static (Share::page...)
In fact these methods aren't static so they should be called
$share = new Share();
$share->page(request()->url())->facebook()
$share->currentPage()->onlyLinks()

The example assumes that you are using the Laravel Facade.
// config/app.php
'aliases' => [
    'Share' => Jorenvh\Share\ShareFacade::class,
];

The example assumes that you are using the Laravel Facade.
// config/app.php
'aliases' => [
    'Share' => Jorenvh\Share\ShareFacade::class,
];


there are not active source control provides

Issue Type: Bug
when i first time install vscode (i don't install xcode or command line tools at that time), I opened a GIT extension (and it doesn't show on extension list),I disable it. How did I enable it.


[release-1.6] [kiali] pilot version endpoint is gone, use the new istiod replacement

This is an automated cherry-pick of #23678

@googlebot I consent


Appointment Type - Global Picklists

Per a previous Sprint, there is additional documentation needed on the utilization of Global Picklist in association to Appointment Category.
Why are they categorized the way they are? What is the intention of them? How are they difference from other picklists?
Overall need more insight into Appointment Category on Appointment Types Object.
Appointment Category and Appointment Type are correspond with one another, so that should be included in the documentation.

@rdblake21 I think that this information should be embedded in page that discusses all the picklists here:  https://github.com/SFDO-Community-Sprints/summit-events-app-documentation/issues/48


PCAP Encryption & Compression

Add the ability to Moloch to have pcap files that are encrypted and compressed on disk.  Would be nice if they are each an option.

[ ] Design file format (probably 64k blocks that are compressed and then encrypted)
[ ] Design key/iv implementation (probably a key/iv per file (not block) that is stored in ES with the file encrypted with the master key)
[ ] Figure out where master key is stored (config file?  in ES?  Per node?)
[ ] Figure out how to encode? we have file, block position in file, packet position in uncompress/unencrypted block
[ ] Change viewer support reader plugins
[ ] Code writer
[ ] Code reader

0.17 supports encryption now (but not compression)

Hello,
Is there a way currently to compress pcaps on the fly with moloch even if it cannot be read into the viewer?
Thank you in advance,
Louis-Henri

No.  pcaps don't compress very well, especially if there is a lot of TLS.  The best way to save space for pcaps is to drop TLS traffic after the first few packets.
This can be done in 0.19 with the following rules file
---
version: 1
rules:
- name: "Drop tls"
  when: "fieldSet"
  fields:
    protocols:
    - tls
  ops:
    _maxPacketsToSave: 10

Where would this rule file be located? Is it part of yara rules?
Thank you in advance.

Added rulesFileds to docs


Recover w/link: Add confirm account page

@kcole16 WDYT, may you help with copy for that?

@vgrichina Here is the latest pass:(https://www.figma.com/file/kFY8wtRYKa6jit4zxTU5Nv/email-confirmation-error?node-id=0%3A1)
Currently pretty minimal on the copy.

@kcole16

@vgrichina Here is the latest pass:(https://www.figma.com/file/kFY8wtRYKa6jit4zxTU5Nv/email-confirmation-error?node-id=0%3A1)

I think it might be confusing when we start burning keys already used for recovery. Like if you just clicked link in wrong message this might cause pretty big panic.

@vgrichina @Patrick1904 @corwinharrell
"If you've enabled email recovery, please check your inbox for the latest message, as all earlier messages are considered invalid. "

so the flow now handles wrong link properly when one tries to recover
https://near-wallet-pr-359.onrender.com/recover-with-link/some-account/foobar
however there are spinners displayed for some reason in top right corner (see attached)

LGTM other than that, feel free to merge


Write Alt-text in all 18 images on the landing page, find alt-texts at the end of this document: https://docs.google.com/document/d/1lG-AUyM-DgMzIbVjw1vL10o18avtT6Av52F4_gxN92c/edit?usp=sharing

Done.


feat: add setDefaultHeaders method on base service class

This change adds a setter for the default headers stored on the base service.
These headers are sent with every SDK request. All of the other language cores
supported setting these values post-construction so this brings Node to parity.
Signed-off-by: Dustin Popp<EMAIL_ADDRESS>

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Temperature sensors not inheriting SensorEntity warning in HA 2022.4

Describe the bug
Starting with HA 2022.4 release, log entries are listed on HA startup stating that a couple of the temperature sensors are not inheriting SensorEntity, which will be unsupported starting in HA 2022.7.
To Reproduce
Steps to reproduce the behavior:

Update to HA 2022.4
View logs
See the warning message about the temperature sensors.

Expected behavior
No warnings.
Screenshots
Server:

OS: HA OS
HA: core 2022.4.b6
docker?: no

Additional context
Logs:
Temperature sensor sensor.prusa_mini_temp_nozzle (<class 'custom_components.prusa_connect.sensor.PrusaSensor'>) does not inherit SensorEntity, this will be unsupported in Home Assistant Core 2022.7.Please report it to the custom component author.
Temperature sensor sensor.prusa_mini_temp_bed (<class 'custom_components.prusa_connect.sensor.PrusaSensor'>) does not inherit SensorEntity, this will be unsupported in Home Assistant Core 2022.7.Please report it to the custom component author.

Thanks for letting me know! I'll fix it when I have some free time...

I think this might be because the various temperature sensors are not declaring the "device class" property as being "temperature". But I'm not a developer, and don't know that for sure.
I think this would probably be set up in class PrusaSensor(Entity):, but again, I'm not a developer so I'm grasping at straws.


NonPrintableCharacterFixer - Add option to replace with escape sequences

Using this option makes the fixer non-risky by replacing characters with \u{...} escape sequences instead of removing them.
I also replaced pack('CCC', x, y, z) with pack('H*', 'xyz') because I find the later easier to read, is it ok?

Thank you @julienfalque.


Remove code related to the gas based staking pools

Fixes #143

LGTM! I just noticed a couple of messages that we may also want to remove:

/staking/src/utils/labels.ts - gasTaxCommission
/staking/src/utils/messages.ts - messages.commission.model.gasBased

Hey @dandheedge,
Do you mind removing these as well before we merge?

LGTM! I just noticed a couple of messages that we may also want to remove:

/staking/src/utils/labels.ts - gasTaxCommission
/staking/src/utils/messages.ts - messages.commission.model.gasBased

Hey @dandheedge, Do you mind removing these as well before we merge?

Just giving a nudge on that before we merge cc: @dandheedge

LGTM! I just noticed a couple of messages that we may also want to remove:

/staking/src/utils/labels.ts - gasTaxCommission
/staking/src/utils/messages.ts - messages.commission.model.gasBased

Hey @dandheedge, Do you mind removing these as well before we merge?

Just giving a nudge on that before we merge cc: @dandheedge

@brunomenezes @nevendyulgerov already removed it


command in "~/.local/bin"  can not be activated

command in ~/.local/bin  can not be activated.
for example , /home/{whoami}/.local/bin/jupyter  exists , but when I ranjupyter notebook, I was told jupyter: command not found
when I ran the same command in bash.exe windows, everything was OK.

That's mean your ~/.local/bin is not included in your $PATH. Run echo $PATH to verify.
Easy fix, add this in your .bashrc to check if $HOME/.local/bin directory exists but not available in your $PATH, then add it to $PATH.
[[ -d $HOME/.local/bin && -z "${PATH##*$HOME/.local/bin*}" ]] || PATH=$PATH:$HOME/.local/bin

I've also had experience that for some reason /sbin, /usr/sbin & /usr/local/sbin are not available in my $PATH
for sbin_dir in {/sbin,/usr/sbin,/usr/local/sbin}; do
        [[ -d $sbin_dir && -z "${PATH##*$sbin_dir*}" ]] || PATH=$PATH:$sbin_dir
done
unset sbin_dir

And I am not sure if this issue have any correlation with any terminal emulator including wsl-terminal.

command in ~/.local/bin can not be activated.
for example , /home/{whoami}/.local/bin/jupyter exists , but when I ranjupyter notebook, I was told jupyter: command not found
when I ran the same command in bash.exe windows, everything was OK.

Are you running wsl-terminal with login shell or not? By default $HOME/bin:$HOME/.local/bin is added to $PATH in .profile and this is done only if you start the shell with -l (you can also use open-wsl-login shortcut which is created with 4-create-start-menu-shortcut-login-shell.js)

@hillerliao, any feedback on this?

sorry I delete the  wsl .


How to mount a Azure File Service Snapshot on Linux

Hello,
Can you please tell me how I can mount an Azure File Service snapshot on Linux. I can successfully mount the File Service container without issues but I would like to mount a snapshot to restore files using cifs?
Thanks
Chanaka

@chanaka-jostle Thanks for the feedback. I assigned the issue for further investigation.

Today, it is not possible to mount an Azure file share snapshot on Linux. This is because the Linux SMB client does not support mounting snapshots like Windows does. We would like to contribute this feature to Linux in the future, so your question is very helpful for us in prioritizing this work, More info can be found here: https://github.com/Azure/azure-cli/issues/5712

Can we re-open this GitHub issue and add a note to the doc page on this?
In this comment, it was suggested that a note would be added to the doc but I don't believe that has happened yet as I see no mention of it (Windows only support) on this page - https://docs.microsoft.com/en-us/azure/storage/files/storage-snapshots-files.
https://github.com/Azure/azure-cli/issues/5712#issuecomment-369791031
The current wording of the doc makes it seem like both Windows and Linux are supported when it doesn't appear to be the case.
@wmgries, @seguler a note be added?

Hello,
Do you plan on providing support to connect to a snapshot directly from
CIFS on Linux? I would be really beneficial.
On Mon, Jul 9, 2018 at 12:56 PM Derek Bekoe<EMAIL_ADDRESS>wrote:

Can we re-open this GitHub issue and add a note to the doc page on this?
In this comment, it was suggested that a note would be added to the doc
but I don't believe that has happened yet as I see no mention of it
(Windows only support) on this page -
https://docs.microsoft.com/en-us/azure/storage/files/storage-snapshots-files
.
Azure/azure-cli#5712 (comment)
https://github.com/Azure/azure-cli/issues/5712#issuecomment-369791031
The current wording of the doc makes it seem like both Windows and Linux
are supported when it doesn't appear to be the case.
@wmgries https://github.com/wmgries, @seguler
https://github.com/seguler a note be added?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/5187#issuecomment-403600718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWbFj4dSuJ1ZjrDEBFKEXSrRakvy_A3Hks5uE7V0gaJpZM4SYzBb
.


Created matcher to compare xmls

Working on #272 I've discovered that xmlunit does not work with Path instances - it simply always matches. To fix this problem I've created IsXmlEqual matcher and used it where necessary.

This pull request #274 is assigned to @vatavuk/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @g4s8/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewer; there will be a monetary reward for this job

@olegmoz thanks, corrected, approve please

Job was finished in 0 hours, bonus for fast delivery is possible (see §36)

@sereshqua/z please review this job completed by @vatavuk/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat quality bad

Quality is low, no payment, see §31


Missing Licensing Information

I want to add this package to Buildroot proper, but it's lacking any licensing information.
Is it BSD/MIT/GPL?

@gamaral I don't have familiar about open source license. What do you recommend ?

@tasanakorn Usually GPLv2 or MIT are pretty good licenses. If you have any trouble choosing a license I would go here or here if you want a more extensive list and explanation of licenses.
I am interested in using this in one of my projects however licensing is preventing me from using it. (Without a license I can't distribute or really fork the project.) Looking forward to a license getting placed in this repo.

I just ran into the lack of a license as well. Would it be possible to add one?


HDDS-5791. Use Guava Cache to replace current ResourceLimitCache for stateMachineDataCache

https://issues.apache.org/jira/browse/HDDS-5791

@ChenSammi , i think we need much finer control over sizing as well eviction strategy here. Simple guava cache has not worked earlier as well. Eviction has to be controlled based on how the threshold of difference between majority and min index for datanode look like.
Let's hold on this patch for now and let's discuss other alternatives.

opened https://github.com/apache/ozone/pull/2704 for resorting to commit index based eviction policy.

Closing this as alternate solutions have been proposed to address this.


Example command line for Nextera Paired-End data?

Could you please provide the command line for Nextera paired-end reads?
(Not mate pair)

$ skewer -x CGAGCCCACGAGACNNNNNNNNATCTCGTATGCCGTCTTCTGCTTG -y GACGCTGCCGACGANNNNNNNNGTGTAGATCTCGGTGGTCGCCGTATCATT -m any -t 10 raw_R1.fastq.gz raw_R2.fastq.gz -o data

Thanks @relipmoc !

Hello, I do not think that the provided sequences are fully appropriate for Nextera. It will remove most of the sequencing adapters, but not the transposase adapter itself, which has the sequence GTATAAGAGACAG and appears right upstream of the actual insert sequence that you are interested in:
Simplified:
5'-[5' adapter]-[GTATAAGAGACAG transposase adapter]-[sequence of interest]-[3' adapter]-3'
That means when the sequencing-by-synthesis starts from 3' adapter, the GTATAAGAGACAG will be sequenced before those sequences listed above. So just offering CTGTCTCTTATA for -x and -y should remove the entire "contamination".
-x and -y are the same in this case, as the Nextera transposase is loaded with two different sequences, sharing the same "core" (GTATAAGAGACAG) but different 5' overhangs for the primers. See the Illumina adapter sequences sheet for details:
http://support.illumina.com/content/dam/illumina-support/documents/documentation/chemistry_documentation/experiment-design/illumina-adapter-sequences_1000000002694-01.pdf


fix(core): enable details for analyzer

https://github.com/unocss/unocss/issues/2682
Currently Analyzer shows incorrect info, because config.details is disabled by default.

I don't actually mind turning details on by default on dev mode. This PR's implementation feels a bit verbose and duplicated

But in this case user will be able to break the Analyzer by setting "details: false" in config.

@antfu 3rd attempt :)


Cow: Watch ki-zu.com

Cow requests the watch of the watch_keyword ki-zu\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

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

Self-rejected by Cow in Charcoal HQ. Reason: 'this is not spam as deemed by SU mods'


Git Bash Terminal Slash issue

Issue Type: Bug
git bash terminal can't handle path with one slashes like C:\Users<username>............it makes problem when automatically installing extensions because terminal couldn't access to python interpreter,  when automatically installing extensions i got an error : "No such file or directory",  so for every plugin i have to add 1 more slashes manually like "C:\Users\..... then it works
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.19042

`

sorry for my english but please do not refer me to another closed issue...I need solution here thanks

No it doesn't work so many settings I have to configure to start using vscode((

have you tried this?

I don't understand how to configure this

I need this too..

I need this too..


segmentation fault for 01_basics/GaN_infiles

Dear developers,
When I try to run the basic examples for GaN via extract_forceconstants -rc2 100 --polar -s 50, I obtain some error:
 ... reading unitcell
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source
libpthread-2.31.s  0000151BA2979420  Unknown               Unknown  Unknown
extract_forcecons<PHONE_NUMBER>9B0882  Unknown               Unknown  Unknown
extract_forcecons<PHONE_NUMBER>9A09E1  Unknown               Unknown  Unknown
extract_forcecons<PHONE_NUMBER>7E260D  Unknown               Unknown  Unknown
extract_forcecons<PHONE_NUMBER>415D02  Unknown               Unknown  Unknown
extract_forcecons<PHONE_NUMBER>410A3D  Unknown               Unknown  Unknown
libc-2.31.so       0000151B9A2BD083  __libc_start_main     Unknown  Unknown
extract_forcecons<PHONE_NUMBER>41095E  Unknown               Unknown  Unknown

If you have any suggestion?

I have also obtained similar error. Is it due to incorrect INCAR?

Hi, I also have this problem. Have you solve it ?

I also have this problem. I compiled TDEP using Intel Fortran compiler mpiifort version 2021.11.1


Deploy Checklist: New Expensify 2022-06-28

Release Version: 1.1.79-18
Compare Changes: https://github.com/Expensify/App/compare/production...staging
This release contains changes from the following pull requests:

https://github.com/Expensify/App/pull/7702

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/8549

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9218

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9350

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/9405

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9469

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9493

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9507

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9512

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9534

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9536

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9549

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9550

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9553

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9554

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9555

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9558

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9563

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9569

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9574

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9610

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9619

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9626

[ ] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/9632

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9639

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9643

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9672

[ ] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9674

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9682

[x] QA
[ ] Accessibility

https://github.com/Expensify/App/pull/9690

[x] QA
[x] Accessibility

https://github.com/Expensify/App/pull/9714

[ ] QA
[ ] Accessibility

Deploy Blockers:

[x] https://github.com/Expensify/App/issues/9594
[x] https://github.com/Expensify/App/issues/9598
[x] https://github.com/Expensify/App/issues/9606
[x] https://github.com/Expensify/App/issues/9614
[x] https://github.com/Expensify/App/issues/9671
[x] https://github.com/Expensify/App/issues/9685
[x] https://github.com/Expensify/App/issues/9695

Deployer verifications:

[ ] I checked the App Timing Dashboard and verified this release does not cause a noticeable performance regression.
[ ] I checked Firebase Crashlytics and verified that this release does not introduce any new crashes.

cc @Expensify/applauseleads

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-3 has been deployed to staging :tada:

@sketchydroide Regression is completed
Deploy Blockers
#9598
#9606
#9614
PR https://github.com/Expensify/App/pull/7702 is failing due to multiple issues https://github.com/Expensify/App/issues/9594, https://github.com/Expensify/App/issues/9606, https://github.com/Expensify/App/issues/9598
PR https://github.com/Expensify/App/pull/9512#issuecomment-1169510399 need clarification. We are blocked to proceed as There is no settings in workspace as in the video attached in the PR
PR https://github.com/Expensify/App/pull/9469 we are not able to execute on native app or mWeb. Is it ok to check off? https://github.com/Expensify/App/pull/9469#issuecomment-1169108708
Issues logged
https://github.com/Expensify/App/issues/9594
https://github.com/Expensify/App/issues/9595
https://github.com/Expensify/App/issues/9605
https://github.com/Expensify/App/issues/9608
https://github.com/Expensify/App/issues/9620

added https://github.com/Expensify/App/issues/9594 as a deploy blocker as it blocks the test of https://github.com/Expensify/App/issues/7702, and until we understand what is needed it should have maximum attention.

Checked off https://github.com/Expensify/App/issues/9594 and https://github.com/Expensify/App/issues/9614 as they're not deploy blockers.
https://github.com/Expensify/App/issues/9606 should be fixed by https://github.com/Expensify/App/pull/9610, but the CP failed. Just manually merged it so that fix should be deployed soon

All GH Actions are currently down, so merging that failed CP did not result in a deploy. We'll just need to wait for the GH incident to be resolved, then we will evaluate. We probably will need to manually CP the PR again.

This issue either has unchecked items or has not yet been marked with the :shipit: emoji of approval.
Reopening!

https://github.com/Expensify/App/issues/9598 is not a deploy blocker, @roryabraham just confirmed this.

I've answered https://github.com/Expensify/App/pull/9469#issuecomment-1169108708 comment

@mvtglobally please give an email for me to add to the policyExpenseChat beta, I'm not sure if I should add all of the expensifails at the moment.

Checking off https://github.com/Expensify/App/pull/9469#issuecomment-1170389690
https://github.com/Expensify/App/pull/7702 &  #9512 are the only 2 outstanding PRs

@sketchydroide add<EMAIL_ADDRESS>&<EMAIL_ADDRESS>
Done, it might take a few minutes for this to be in effect

@roryabraham what can we do to unblock #7702

@roryabraham what can we do to unblock https://github.com/Expensify/App/pull/7702?

Sorry, @mvtglobally why is https://github.com/Expensify/App/pull/7702 blocked?

@sketchydroide #9512 is a pass. Checking off
@roryabraham  there were couple of blockers for #7702 (https://github.com/Expensify/App/issues/9594, https://github.com/Expensify/App/issues/9606) But seems like they are resolved. there are other issues which are not blockers. We didn't retest any new CPs. Not sure if we need to.

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-7 :rocket:

Checked off https://github.com/Expensify/App/issues/9598 because it's not a deploy blocker.

https://github.com/Expensify/App/pull/9610 should be fixed in v1.1.79-3+. I verified the fix on web. @Expensify/applauseleads please retest.

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-7 has been deployed to staging :tada:

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-9 :rocket:

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-9 has been deployed to staging :tada:

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-11 :rocket:

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-11 has been deployed to staging :tada:

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-12 :rocket:

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-12 has been deployed to staging :tada:

Marked off #7702 as a separate issue was created here

marked off #9671 as it should have been fixed. Will be confirmed when this issue  is tested

Resolved blocker #9685 as a revert Pr was just merged.

9671 was reopened, as the fix PR had to be reverted. The remaining two blockers are:

https://github.com/Expensify/App/issues/9606
https://github.com/Expensify/App/issues/9671

I'll be back to look into these after finishing the rest of my chores.

9671 was reopened, as the fix PR had to be reverted. I'll be back to work on another fix after finishing the rest of my chores.

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-13 :rocket:

^ The CP was successful. I just need to resolve the remaining blocker before QA can be started

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-13 has been deployed to staging :tada:

Hi @Expensify/applauseleads could you please go ahead with testing the release? One blocker remains, but I'm tempted to remove the blocking status if we can't find consistent reproducible steps...

No new fatal crashes in firebase, or noticable timing regressions.

@Expensify/applauseleads the last blocker has been resolved, please go ahead with testing when you are ready 🎉

@Julesssss / @roryabraham Wanted to double check that there's no need to verify https://github.com/Expensify/App/pull/9674 since it was reverted here https://github.com/Expensify/App/pull/9690
I checked them off already, let me know is there's anything we need to QA regarding those changes.
We're currently checking https://github.com/Expensify/App/pull/9672 at the moment. Will post the results here.

@Julesssss @roryabraham
We retested https://github.com/Expensify/App/pull/9672 and found this issue https://github.com/Expensify/App/issues/9695, here it explains what step is failing.
We added the deploy blocker bc it's not reproducible in production but since it's a new behavior it's probably not deploy blocker 🤔 We'll leave the label on for your review.
Will leave https://github.com/Expensify/App/pull/9672 unchecked until the above reviewed. If the issue is not a deploy blocker, we can check it off.

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-14 :rocket:

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-14 has been deployed to staging :tada:

Closed https://github.com/Expensify/App/issues/9695 because it's the expected behavior.

Looks like we're waiting on the results of https://github.com/Expensify/App/pull/9672, and also need to QA https://github.com/Expensify/App/pull/9682

@roryabraham can we possibly hold this deploy on -> https://github.com/Expensify/App/pull/9350
This PR in Web-Expensify will reintroduce the "double notification" issue temporarily once deployed and if we can time things right we can minimize the impact.

@roryabraham can we possibly hold this deploy on -> https://github.com/Expensify/App/pull/9350

Sure, no problem

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-15 :rocket:

https://github.com/Expensify/App/pull/9682 is pass. checking off

Just a heads up that this PR was merged (unsure if it has been CP'd will look in a second) but is not yet ready to be tested and will be tested after the Web-Expensify deploy. So we are holding the NewDot deploy on the Web-E deploy.

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-15 has been deployed to staging :tada:

https://github.com/Expensify/App/pull/9714 just finished CPing so we should test that too. It fixes an issue that we weren't treating as a blocker.

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-16 :rocket:

https://github.com/Expensify/App/pull/9626 also just started CPing, and it fixes another non-blocker bug introduced in this release: https://github.com/Expensify/App/issues/9598

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-16 has been deployed to staging :tada:

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-17 :rocket:

:clap: Heads up @Expensify/applauseleads :clap:
A new pull request has been :cherries: cherry-picked :cherries: to staging, and will be deployed to staging in version 1.1.79-18 :rocket:

:tada: All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.79-18 has been deployed to staging :tada:

Sorry for all the CP announcements, I'm testing some new deploy stuff

https://github.com/Expensify/App/pull/9714 is pass Checking off. Will update https://github.com/Expensify/App/pull/9626 & https://github.com/Expensify/App/pull/9672 tomorrow

Checked all PRs on Production / Staging and created accessibility issues for all PRs where accessibility issues were found.
The non-applicable PRs are - #8549, #9218, #9405, #9469, #9493, #9507, #9512, #9536, #9549, #9553, #9554, #9558, #9563, #9574, #9569, #9555, #9610, #9632, #9639, #9643, #9672, #9674, #9690, #9619, #9350, #9626, #9682, #9714
Logged Issues - #8419, #8465, #8435, #8430, #8616, #8463, #8434, #8432, #8433, #8651, #8413, #8430, #8668, #9666, #9667, #9669, #8419, #9634, #8393, #8392, #8560, #8465, #8385, #8400

@roryabraham  @Julesssss
PR https://github.com/Expensify/App/pull/9626 is failing due to  https://github.com/Expensify/App/issues/9742 & https://github.com/Expensify/App/issues/9745
PR #9672 is failing due to https://github.com/Expensify/App/issues/9747. repro in prod. ok to check off?
Waiting for the green light on https://github.com/Expensify/App/pull/9350

Removed #9745 as a blocker as I'm unable to reproduce.

Still blocked by the Web-E PR. I've asked for someone to add a comment here when it's done.

PR https://github.com/Expensify/App/pull/9672 is failing due to https://github.com/Expensify/App/issues/9747. repro in prod. ok to check off?

Yeah, as it's occuring in prod it's not a deployBlocker. I'll mark it off now.

@roryabraham I'm a bit confused by this Web-E blocker... I can't find any information about it in the linked issue. The only mentioned Web-E PR was merged weeks ago 😕

Anyway, the Web-E deploy seems to be the final remaining blocker now 👍

Yeah, I'm trying to piece together what exactly we're waiting on, as this deploy is holding up the #VIP-550-engaged reach-outs that we'd ideally like to pull the trigger on today. My understanding is this..
This Web-E PR needs to go to prod before the NewDot deploy, as it needs to go before this APP PR hits prod. We got held up because that Web PR introduced a couple of regression, that have both been fixed by this PR that is now also on staging.
QA confirmed the retests last night after the PR to fix those regressions were CP'd to staging. With that, will we do a prod deploy (Web) today (CC: @stitesExpensify as I think you're on duty), or can we at least CP the two PRs that are holding up the NewDot deploy here?

Woo woo! Let's lift off.

:shipit:

This issue either has unchecked items or has not yet been marked with the :shipit: emoji of approval.
Reopening!

Oh, actually now that Web-E is deployed we need to run QA on https://github.com/Expensify/App/pull/9350

CC @Expensify/applauseleads

Oh, actually now that Web-E is deployed we need to run QA on #9350

How we looking here, ya'll?

@trjExpensify You can follow along in slack here

Looks like the only issue that popped up was https://github.com/Expensify/App/issues/9766. While it looks like a legitimate bug, I'm thinking we should not treat it as a blocker because it's pretty minor and we have a pressing need to get this release out the door. Thoughts?

Actually, https://github.com/Expensify/App/issues/9766, is reproducible in production. So it's definitely not a blocker

Following confirmation in slack, https://github.com/Expensify/App/pull/9350 passed without any blockers, so I'm going to check it off.

:shipit:

This issue either has unchecked items or has not yet been marked with the :shipit: emoji of approval.
Reopening!

Oh, https://github.com/Expensify/App/pull/9626 had some issues but no blockers. Checking that off as well.

:shipit:

Need to reopen this due to a failed deploy workflow

https://github.com/Expensify/App/pull/9771 should fix NewDot deploys 🤞

https://github.com/Expensify/App/pull/9771 merged. Let's try this again, shall we?

:shipit:

Not quite

Going to ship this again. I think the staging deploy + new checklist creation should happen automatically 🤞, but I'll need to manually do the production deploy. Slack context here

:shipit:

Thanks @roryabraham!


Bumping version to 0.1.6

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (140a01d) 84.51% compared to head (6448119) 84.51%.
Report is 19 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   84.51%   84.51%
=======================================
  Files          32       32
  Lines        2712     2712
=======================================
  Hits         2292     2292
  Misses        420      420

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


[Interactable Objects] Connecting Objects Together

I'm not sure if you are already planning this but:
I would love to see a way of connecting objects together. Things like keys into keyholes, ammo clips and mods on to guns etc.
Once two connectable objects get close enough they would try and orient themselves to connect (locking an axis if needed) and eventually connect when close enough and/or released.
Thanks for your awesome work on the toolkit!

I thought I already had an issue with this! Can't find it though :) so thanks for posting it :)
Yeah it's something I want to implement, same as in Job Simulator where you just put an object near something else and it snaps into place.
Now typing that I think I remember where I was talking about it...in the bow mechanics issue!
But yeah, it's something I want to implement

Are you still planning on implementing this in bow mechanics?
I have a simple modification to the grabbable object script where you provide a string and when the object is picked up all objects with the same tag are also grabbed. You can also supply a Vector3 offset for the grouped object.
Its not very robust but I will submit a pull request if its not being implemented elsewhere

I'm currently working on the bow mechanics should be ready soon :)

I would like to second this request. Specifically, what would be great is if I could grab-and-hold an object (like a key) which has the VR_InteractableObject attached and - with the grabbed object in hand - touch another object (like a door lock) which also has the VR_InteractableObject attached - so I can get notified in "OnTouch" with the grabbed object.
The problem with this currently is that I can't move the objects into one another as both have colliders/collision detection. I could change this in Grabbed/Ungrabbed (detectCollisions=false/true). However, even when doing this, the object passed in StartTouching() seems to be the controller, not the grabbed object.
This makes me feel that the current scripts weren't really made for that use case ;-) --- What do you think of an addition which allows such interactions with grabbed objects? Or, if it can already be done with the current scripts, what do you suggest as the best way?

@thjmorgan Heh, I was just replying to your other issue before you closed it. I was going to refer to this exact issue, but you've beat me to it :)
Yeah it's something that is a good addition!

Trello Card https://trello.com/c/NPsRmgYC

In order to work on a lock, key hole, "insert radio active rods here", plug something into electric sockets and many more we need this to be a general purpose snapping mechanism.
It should be proximity and direction based (e.g. don't snap the key if you are not facing the hole) and then rotate the object into the needed position. Once snapped, it should only allow limited movement, e.g. move along x-axis (min/max) or rotate around z (min/max).

Following the same issue request: I would also like to add mine here
Hi @thestonefox ,  Is there also a possibility to "snap two objects" based on their relative distance and relative orientation from eachother? Since the objects can be anywhere in the world space. E-g 3D puzzle objects to be docked at right point to complete puzzle.

Resolved with
https://github.com/thestonefox/VRTK/pull/670


fips_unittests.cmake: remove Oryol specific code

The generated main.cc file for a UnitTest has Oryol-specific calls in it: https://github.com/floooh/fips/blob/master/cmake/fips_unittests.cmake#L44, this should be replaced with a project-specific template file (and if the project doesn't provide a template file, use a generic file).
Probably use cmake's configure_file for this: http://www.cmake.org/cmake/help/v3.1/command/configure_file.html

btw, the same is true for the plist templates. Should go into MacOSX.plist.in and configure_file should be used here, too
(sorry for hijacking this issue)

Oryol dependency of unittest code has been removed (without configure_file, this would have been overly complex.


new(charts): add k8s-metacollector chart

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If this PR will release a new chart version please make sure to also uncomment the following line:

/kind chart-release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area falco-chart

/area falco-exporter-chart

/area falcosidekick-chart

/area event-generator-chart

What this PR does / why we need it:
This PR adds a new chart for k8s-metacollector.  Since we have not release yet the k8s-metacollector the chart uses the main tag.
In this PR are included unit tests for the chart. Tests are written in golang, using the  helm module of the great terratest library.
Note that tests are not enabled yet, the main reason is that the chart uses the main tag causing some tests to fail.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: alacuku
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 6f52e541ab33c9e00ea23c812be61d11a744791e

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Fix some colour settings in swaybar

This should fix #932 - if binding_mode colours are not defined, use urgent_workspace colours as a fallback.
Three missing settings were also implemented: focused_(workspace|statusline|separator)
They provide different colours for swaybar on the focused output.

Why not keep the static buffers? Is there any need for them to be dynamically allocated?

Putting them on the heap is a bit cleaner imo


Self-Referencing cannot generate such a statement

Your issue may already be reported! Please search on the issue track before creating one.
What version of Go are you using (go version)?
1.12.4
Which database and its version are you using?
postgre 11.0.1
Please provide a complete runnable program to reproduce your issue. IMPORTANT
Need to runnable with GORM's docker compose config or please provides your config.
package main

import (
	"github.com/jinzhu/gorm"
	_ "github.com/jinzhu/gorm/dialects/postgres"
)

var db *gorm.DB

func init() {
	var err error
	db, err = gorm.Open("postgres", "user=gorm password=gorm DB.name=gorm port=9920 sslmode=disable")
	if err != nil {
		panic(err)
	}
	db.LogMode(true)
}

type Comment struct {
	ID uint
        PraentID uint
	SubComment  []Comment  `gorm:"association_jointable_foreignkey:praent_id"`
}

func main() {
	db.Preload("SubComment").First(&comment , "id = ?", 1)
}

why not
SELECT a.* FROM "comment" a INNER JOIN "comment" b ON a.praent_id = b.id WHERE b.id =1;

Try to use foreignkey and association_foreignkey.
type Comment struct {
	ID         uint
	PraentID   uint
	SubComment []Comment `gorm:"foreignkey:id;association_foreignkey:praent_id"`
}

http://gorm.io/docs/has_many.html#Association-ForeignKey

thanks


Re-add openstackclient implementation

I'd say the chances of me not understanding what's going on are pretty high. What I see is after applying 2024.X to openstack client, making any call will lead to some stderr output complaining it can't find the requested module 'console_auth_token' . I thought that was because of the extra line in setup.cfg which is pointing at code that doesn't exist. I saw that the code was in previous versions but is missing here and just figured it was a copy paste error of some kind, but it sounds like it's more that the command itself doesn't need to be there because we can use the additional option instead of the additional command.
So I guess now my question is what code is this meant to be calling or should this line be removed?
console_connection_show = openstackclient.compute.v2.console_auth_token:ShowConsoleConnectionInformation


Update github-actions

Add daily audit
Add update coverage version
Change clippy to actions-rs/clippy-check

Coverage remained the same at 100.0% when pulling be0234262722668456d8dc1a742ac7e18f8bf141 on actions-updates into 66103bf4ec4df805bbc561a99c99bf3784c04a2c on main.


fix(web-app): proxy server conversion to esm

Closes #969

@francinelucca good call. There's one change I missed in the esbuild file. I'll update that now.

@jdharvey-ibm
Should I be able to see the app?  👀

@andreancardona If you're just running start:proxy, then you won't see the app. The docs over here give some info about how the proxy-server relates to the web app, but the net is that you'd need to run both the dev server and the proxy server, and then navigate to localhost:8080 to see the web-app through the proxy.

he proxy-server relates to the we

okay thank you :)


Gradle build broken

Error:Failed to find: com.commonsware.cwac:camera-v9:0.6.+

i can still see the issue. Android studio failed to find the dependency.
Steps:

created a new android studio project and added dependency as follows

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile 'com.android.support:appcompat-v7:21.0.3'
compile 'com.commonsware.cwac:camera:0.6.+'
}
result
Failed to find : com.commonsware.cwac:camera:0.6.+
what else i need to do to compile the project with this library if im missing any thing as i could see this issue is fixed .

Please add the artifact's repository to the repositories closure of your app module's build.gradle file, as is illustrated in the project README.

Same problem here, did what readme says:
repositories {
    maven {
        url "https://repo.commonsware.com.s3.amazonaws.com"
    }
}

dependencies {
    compile 'com.commonsware.cwac:camera:0.6.+'
}

And still getting the same error

@CoericK As I pointed out previously, the artifact exists. And, as I pointed out previously, you may need to use the --refresh-dependencies to force Gradle to check again for the dependency, as it tends to only check once per day, if you ran into some hiccup previously.

Thanks @commonsguy but im using Android Studio, so i just go to Build->Generated Signed APK, how can i build the project, or update the dependencies?

Using gradle --refresh-dependencie on termial i get this error log:
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugCompile'.
   > Could not find any version that matches mocom.comnsware.cwac:camera:0.6.+.
     Searched in the following locations:
         https://jcenter.bintray.com/mocom/comnsware/cwac/camera/maven-metadata.xml
         https://jcenter.bintray.com/mocom/comnsware/cwac/camera/
         https://repo.commonsware.com.s3.amazonaws.com/mocom/comnsware/cwac/camera/maven-metadata.xml
         https://repo.commonsware.com.s3.amazonaws.com/mocom/comnsware/cwac/camera/
         https://repo1.maven.org/maven2/mocom/comnsware/cwac/camera/maven-metadata.xml
         https://repo1.maven.org/maven2/mocom/comnsware/cwac/camera/
         https://oss.sonatype.org/content/repositories/snapshots/mocom/comnsware/cwac/camera/maven-metadata.xml
         https://oss.sonatype.org/content/repositories/snapshots/mocom/comnsware/cwac/camera/

@CoericK The artifact is not named mocom.comnsware.cwac:camera:0.6.+. It is named com.commonsware.cwac:camera:0.6.+.

I updated my gradle file and i still gets the error:
Unindexed remote maven repositories found. Disable...
         The following repositories used in your gradle projects were not indexed yet:
         https://repo.commonsware.com.s3.amazonaws.com
         If you want to use dependency completion for these repositories artifacts,
         Open Repositories List, select required repositories and press "Update" button (show balloon)

@CoericK I have never seen that message before from Android Studio. It would not appear to necessarily be a build error, and it gives you instructions for how to resolve the problem.


[JDK 8] Add local variable information to JDK class library

Apparently the JDK class libraries don't seem to include local variable information in the JDK class files. Actual:
$ ./bin/javap -J-showversion -l java.lang.Object | grep LocalVariableTable
openjdk version "1.8.0_352"
OpenJDK Runtime Environment (Temurin)(build 1.8.0_352-b08)
OpenJDK 64-Bit Server VM (Temurin)(build 25.352-b08, mixed mode)

Expected (something like this):
$ bin/javap -J-showversion -l java.lang.Object | grep LocalVariableTable
openjdk version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-b09)
OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)

    LocalVariableTable:
    LocalVariableTable:
    LocalVariableTable:
    LocalVariableTable:
    LocalVariableTable:
    LocalVariableTable:

On Fedora we achieve this by passing JAVAC_FLAGS=-g to the make invocation. See:
https://src.fedoraproject.org/rpms/java-1.8.0-openjdk/blob/rawhide/f/java-1.8.0-openjdk.spec#_2215
Temurin should use the same. JDK 11+ don't have that issue.

Size difference seems to be about 8 MB.
Temurin:
-rw-r--r--. 1 sgehwolf sgehwolf 63M Oct 20 10:37 jre/lib/rt.jar

Fedora:
$ ls -l -h jre/lib/rt.jar
-rw-r--r--. 1 root root 71M Jan 26 04:33 jre/lib/rt.jar

See also https://github.com/adoptium/adoptium-support/issues/734


What are the checkboxes next to the titles for?

What are these checkboxes for?

bulk delete and drag

Thx, it's a handy feature


It's election time for the Chairperson of Community Committee!

It's election time for the Chairperson of Community Committee!
Nominations are now published for candidates to be considered for election! Candidates will each have their own Q&A issue, linked by their name, where they will answer questions through the election period ending Sunday, September 9 at 11:59pm UTC. Ballots will be emailed Friday, September 7 to all voting members of CommComm in order to give time for candidates to answer questions and have time to consider responses through September 9 before voting.

The CC will elect from amongst voting CC members a CC Chairperson to work on building an agenda for CC meetings and collaborate with the Individual Membership Directors the wishes of the CC to the Board for a term of one year according to the Node.js Foundation’s By-laws. The CC shall hold annual elections to select a CC Chairperson; there are no limits on the number of terms a CC Chairperson may serve.

Nominated candidates:

Abraham Jr. Agiri @codeekage --> Q&A
Jem Bezooyen @jembijoux --> Q&A
Adam Miller @amiller-gh --> Q&A
Joe Sepi @joesepi --> Q&A
Dan Shaw @dshaw --> Q&A

As stated in the previous election, expected responsibilities include but are not limited to:

Chair and facilitate each CommComm member meeting. It is the chairperson's responsibility to ensure that the meeting stays on track, sticks to the agenda, and finishes within the allotted time.
Cultivate and maintain good working relationships with the members of CommComm and groups contributing under the CommComm scope.
Coordinate with the CommComm Director( @hackygolucky) on presenting requests to the Board from CommComm that need attention.
Collaborate closely with the TSC Chair(@mhdawson), TSC Director(@MylesBorins), Individual Membership Director(@williamkapke), and appropriate ecosystem/Foundation stakeholders
Coordinate efforts in shared repos, as listed in Admin
Create each CommComm meeting's agenda and help facilitate other meetings under the CommComm's scope.
Create events and ensure appropriate meetings are live-streamed on YouTube.

All Community Committee active members are eligible to vote and will receive a ballot after the Q&A window has been open for a few days. If you are having trouble with voting, please email<EMAIL_ADDRESS>

Ballots have been emailed to all members listed on the CommComm README. Please ping me if you did not receive it!

On the streamed meeting yesterday, I heard somebody express confusion about multiple-candidate voting methods (eg: Single Transferable Vote aka instant-runoff voting aka ranked-choice voting).
I just wanted to share an old (but good) video on the specifics & benefits of such a system (4mins): https://youtu.be/3Y3jE3B8HsE?t=1m14s

Shared this in the Zoom chat during the meeting too – best (interactive!) example I’ve ever seen of different voting systems: https://ncase.me/ballot/
@ncase ===  ✨🌟🎉🤯🎉🌟✨


[Bug]: There is an unusable selection box in session management memory

ODC version
odc422
OB version
not have
What happened?

What did you expect to happen?
No selection box present
How can we reproduce it (as minimally and precisely as possible)?

Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 275fc78ab6a324efbb22f0d71dfb10e407732614
------
晓康
Wed Nov 1 15:51:34 2023 +0800

pass


Expand dependency version support.

This change expands support for new versions Event Loop and Evenement without abandoning the versions already supported.

Thanks!


CMake enables hardware dependent tests by default

By default IREEs compilation/tests builds and tests hardware dependent tests (like Vulkan/CUDA tests). While Vulkan tests I can fix locally by installing swiftshader, without a NVIDIA card, the CUDA tests fail.
Setting -DIREE_HAL_CUDA_DRIVER=OFF was suggested as a solution on Discord. That works, but might not be something that helps new users. This bug is to track solution for this. Maybe Vulkan/CUDA tests must not be built by default, and be an opt-in if users have their system setup for it.

Cross-posting from Discord:
I don't want the tests themselves to silently pass if Vulkan setup fails. That's how you end up with broken things. So to disable building, you can disable the driver and to disable testing only you can exclude with CMake labels. You don't need to be using ctest_all.sh. This is sort of the concern I was expressing in the PR where we turned on Cuda by default, btw Scott 🙂 (https://github.com/iree-org/iree/pull/11832)
We have the same issue with Vulkan fp16 and I set my ctest labels to exclude it. We could have yet another set of options (besides target backends and hal drivers) that is "runtime tests"
And we could make the default for those do some different querying. I'm not aware of a ctest option for configuring default label exclusions, but maybe?
Presets might help here? https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html

Setting as P2 - please bump up if needed.

Had some random thoughts about this and related issues... brainstorming notes:
High level goals

Continuous integration builds (using GitHub Actions) should run all possible tests without accidently skipping any. For example, a test_gpu_nvidia job running with a physical NVIDIA GPU attached should run all Vulkan and CUDA tests. Configurations should be simple enough for coverage gaps to be obvious to spot or impossible by construction.
Developer builds should only run what the current hardware supports, with clear indications of what isn't supported. These should be easy to debug, with either opt-in or opt-out logging and options to force enable/disable each configuration.

Feature detection
We already have some automatic CPU feature detection (parse_target_cpu_features_variant + IREE_ARCH). We could do something similar for GPU APIs. This would probably get messy, but there are helpers like FindCUDA and FindVulkan that we could try leaning on.
Another option is to run a script ahead of the CMake configure command, like the configure_bazel.py script. That could attempt to auto-detect but fall back to asking for user input about which configurations could be enabled. Such a script could generate a CMake preset file with each of the underlying CMake options set.
Developer builds could use conservative defaults such as Vulkan/CUDA/ROCm/etc. disabled if not detected.
CTest behavior
We can set the DISABLED or WILL_FAIL properties on tests that are not in a supported/enabled configuration, rather than return() before defining them. The output from ctest should then include those tests, making it more obvious what tests could have been run if the detected/specified configuration was different.

This is a bit more complicated with iree_bytecode_module running at build time instead of configure time

Test suite definitions
Along the lines of https://github.com/openxla/iree/issues/4644, we could split the tests/e2e/ folder into

Test suite declarations (programs and their expected outputs)
Test suite instantiations (compiler targets + runtime HAL drivers pairs, test inclusions/exclusions)

That would make it easier to add new tests to the suite, add new backends, and see which tests are passing/failing on each backend.

Another CMake feature to try out is RESOURCE_GROUPS. Not sure if that has all the behaviors we would want, or what the ergonomics are like (e.g. https://discourse.cmake.org/t/ctest-skip-tests-when-resource-groups-is-not-available/7208). On the surface, that seems like a built-in way to say "this test needs a GPU". See also https://cmake.org/cmake/help/latest/manual/ctest.1.html#resource-specification-file.


TypeError when packaging guessit in standalone mode

Nuitka version, full Python version, flavor, OS, etc. as output by this
command.

python -m nuitka --version

1.4.6
Commercial: None
Python: 3.10.9 (main, Dec 19 2022, 17:35:49) [GCC 12.2.0]
Flavor: Unknown
Executable: /usr/bin/python
OS: Linux
Arch: x86_64
Distribution: Manjaro (based on arch) None
Version C compiler: /usr/bin/gcc (gcc).

How did you install Nuitka and Python
Installed factory version in virtualenv using pip.

The specific PyPI names and versions

guessit==3.5.0
rebulk==3.1.0

Also supply a Short, Self Contained, Correct, Example
https://github.com/iamkroot/nuitka-guessit-repro

Provide in your issue the Nuitka options used
python -m nuitka repro.py --standalone

Details
On running the binary generated by nuitka, I get an error saying:
File ".../nuitka-repro/myrepro.dist/guessit/rules/common/numeral.py", line 51, in <module guessit.rules.common.numeral>
  File ".../nuitka-repro/myrepro.dist/guessit/rules/common/numeral.py", line 47, in __build_word_numeral
TypeError: unsupported operand type(s) for +=: 'NoneType' and 'str'

guessit is a dependency. These are the relevant lines inside numeral.py:
english_word_numeral_list = [
    'zero', 'one', 'two', 'three', 'four', 'five', 'six', 'seven', 'eight', 'nine', 'ten',
    'eleven', 'twelve', 'thirteen', 'fourteen', 'fifteen', 'sixteen', 'seventeen', 'eighteen', 'nineteen', 'twenty'
]

french_word_numeral_list = [
    'zéro', 'un', 'deux', 'trois', 'quatre', 'cinq', 'six', 'sept', 'huit', 'neuf', 'dix',
    'onze', 'douze', 'treize', 'quatorze', 'quinze', 'seize', 'dix-sept', 'dix-huit', 'dix-neuf', 'vingt'
]

french_alt_word_numeral_list = [
    'zero', 'une', 'deux', 'trois', 'quatre', 'cinq', 'six', 'sept', 'huit', 'neuf', 'dix',
    'onze', 'douze', 'treize', 'quatorze', 'quinze', 'seize', 'dixsept', 'dixhuit', 'dixneuf', 'vingt'
]

def __build_word_numeral(*args):
    """
    Build word numeral regexp from list.

    :param args:
    :type args:
    :param kwargs:
    :type kwargs:
    :return:
    :rtype:
    """
    re_ = None
    for word_list in args:
        for word in word_list:
            if not re_:
                re_ = r'(?:(?=\w+)'
            else:
                re_ += '|'
            re_ += word
    re_ += ')'  # line 47
    return re_

word_numeral = __build_word_numeral(english_word_numeral_list, french_word_numeral_list, french_alt_word_numeral_list) # line 51

From the error message, it seems that re_ is None, which would only happen when args is empty. However, it is definitely called with the three globals in the last line in the python source.
Seems like they are not present in the compiled version for some reason?

Update: This looks more like an optimization bug in Nuitka.
I added print statements to the source code, and it revealed that re_ is indeed populated correctly.
def __build_word_numeral(*args):
    """
    Build word numeral regexp from list.

    :param args:
    :type args:
    :param kwargs:
    :type kwargs:
    :return:
    :rtype:
    """
    re_ = None
    print(args)  # prints all the lists of strings correctly
    for word_list in args:
        for word in word_list:
            if not re_:
                re_ = r'(?:(?=\w+)'
            else:
                re_ += '|'
            re_ += word
    print(re_)  # prints the proper string
    re_ += ')'  # Type error, re_ is `NoneType`??
    return re_

I understand that the source code is pretty shitty- it assumes that re_ is never None by the time it reaches re_ += ')', so it would be best to initialize it to empty string at least.
But hey, it is valid python...

You are not on the latest hotfix, but even 1.5 shows this. Of course has nothing to do with standalone code, the given example does it in accelerated mode.
What's strange is that adding a print of the type(_re) gives str, so the optimization there is also correct. When I change the start value to [] however, the type becomes list and adding the str in-place suddenly works. It appears almost as if a merge trace is not considering both of its sides properly to answer a type/value related question.

This is a bug of the loop shape analysis, I believe. It seems that the operation is considered between <ShapeLoopInitialAlternative None OBJECT> <ShapeTypeStr str UNICODE>, and then suddenly <ShapeTypeNoneType NoneType OBJECT> <ShapeTypeStr str UNICODE>.
What is going on there is that after a loop iteration, relatively quickly _re is decided to not be a loop variable, and therefore is then not a merge trace. Most likely because it's value is always replaced, so Nuitka might actually see through None becoming replaced. The type giving a different result than the operation, is something to investigate. Maybe different levels of optimization quality of the += and type1 node.

Ok, the type optimization looks at the type shape, and only if it has a type name, resolves it to a built-in name. That doesn't cover all the types, esp. not NoneType. Checking the typical_value and creating a constant out of its type, is a much better way to go.
With that, the phenonemon about None and [] working differently for the type output can be explained.

The reproducer is with that new optimization added down to this one:
def __build_word_numeral(*args):
    re_ = None
    for word_list in args:
        for word in word_list:
            if not re_:
                re_ = r'(?:(?=\w+)'
            re_ += word

    assert type(re_) is str

__build_word_numeral("lala")

So the nested loop analysis is going wrong. I believe this must be because the outer loop concludes that nothing is going on with re_ and therefore the value is unchanged, not seeing what is happening for the inner loop.
I will have to make the flow graph output for the variable tracing here, to become sure of that, but I believe this may require a major surgery on the loop optimization. I want to do that anyway, because I am unhappy with the value traces from in-place operations that are type changing already. But I guess, I need to think more about this.

This rewrite is on for 2.0 I believe, but it's not clear how much effort it is. Mainly it's about scalability, making the merge traces static operations, and the hope is that loop variable analysis will then automatically be able to handle this properly.

the reproducible example is not longer around, i think you recently did some optimizations in this area?

The original example still seems to not work.

Something about nested loops is not going right, with the type analysis of _re there. Need to investigate.


Fingerprints: add missing FW versions from users for Mazda, Nissan, Tesla, Volkswagen [bot]

✅ Updating FW version database with FW from 4 dongles (3 platforms) in last 30 days:
View table

Dongle, platform, VIN
Name from VIN 🆚 CarInfo
Segments
Bad seg tags
Good seg tags

23daff6c438612d2AUDI A3 3RD GEN3VWCA7AU3........
VOLKSWAGEN Golf SportWagen 2015 🆚Audi A3 Sportback e-tron 2017-18🎉 New model year! 🎉
119 routes, 4387 segments
- VIN model mismatch (info): 1- VIN make mismatch (info): 1
- all lat active: 146- no input all lat active: 107

0649d406184b7131VOLKSWAGEN JETTA 7TH GEN3VWEB7BUX........
VOLKSWAGEN Jetta 2019 🆚Volkswagen Jetta 2018-22
129 routes, 2075 segments

- all lat active: 193- no input all lat active: 175

7605de164f235364NISSAN LEAF<PHONE_NUMBER>000........
None 🆚None
71 routes, 764 segments

- all lat active: 91- no input all lat active: 76

969dd380d52937c6NISSAN LEAF<PHONE_NUMBER>000........
None 🆚None
106 routes, 2274 segments

- all lat active: 231- no input all lat active: 32

Dongles to re-run category: 969dd380d52937c6 0649d406184b7131 23daff6c438612d2 7605de164f235364

⏳ 9 dongles (4 platforms) do not yet have enough data to be added:
View table

Dongle, platform, VIN
Name from VIN 🆚 CarInfo
Segments
Bad seg tags
Good seg tags

637ba3a706c81f0fVOLKSWAGEN GOLF 7TH GEN3VWH17AU6........
VOLKSWAGEN Golf Alltrack 2019 🆚Volkswagen Golf Alltrack 2015-19
1 routes, 6 segments

- all lat active: 0

35adf91a01670b4cVOLKSWAGEN TIGUAN 2ND GEN3VV3B7AX0........
VOLKSWAGEN Tiguan 2020 🆚Volkswagen Tiguan 2018-24
4 routes, 4 segments

- all lat active: 0

725e437a2d0887daVOLKSWAGEN GOLF 7TH GENWVWZZZAUZ........
VOLKSWAGEN  2018 🆚Volkswagen Golf 2015-20
7 routes, 18 segments

- all lat active: 0

bd349df2aad3c6fcNISSAN LEAF<PHONE_NUMBER>000........
None 🆚None
122 routes, 2002 segments

- all lat active: 0

c45851925d1d1d67VOLKSWAGEN GOLF 7TH GEN3VWH17AU0........
VOLKSWAGEN Golf Alltrack 2017 🆚Volkswagen Golf Alltrack 2015-19
3 routes, 31 segments

- all lat active: 0

9299dd7dadb9007eNISSAN LEAF<PHONE_NUMBER>000........
None 🆚None
22 routes, 545 segments

- all lat active: 42- no input all lat active: 23

77db91ca5676dfd9VOLKSWAGEN GOLF 7TH GEN3VW6T7AUX........
VOLKSWAGEN Golf GTI Hatchback 2021 🆚Volkswagen Golf GTI 2015-21
84 routes, 1130 segments

- all lat active: 16- no input all lat active: 10

9d1379c2a3912015VOLKSWAGEN JETTA 7TH GEN3VWG57BU4........
VOLKSWAGEN Jetta 2021 🆚Volkswagen Jetta 2018-22
35 routes, 352 segments

- all lat active: 49- no input all lat active: 22

a97d27ce2a78958aVOLKSWAGEN JETTA 7TH GEN3VWG57BUX........
VOLKSWAGEN Jetta 2019 🆚Volkswagen Jetta 2018-22
43 routes, 1058 segments

- all lat active: 55- no input all lat active: 53

Dongles to re-run category: 35adf91a01670b4c 637ba3a706c81f0f 725e437a2d0887da bd349df2aad3c6fc c45851925d1d1d67 9299dd7dadb9007e 77db91ca5676dfd9 9d1379c2a3912015 a97d27ce2a78958a

⚠ 2 dongles (2 platforms) have issues that need to be resolved before adding:
View table

Dongle, platform, VIN
Name from VIN 🆚 CarInfo
Segments
Bad seg tags
Good seg tags

2024aefc4c4f766cMAZDA CX-9 2021JM3TCBAYX........
MAZDA CX-9 2023 🆚Mazda CX-9 2021-23
83 routes, 1706 segments
- car faulted: 8
- all lat active: 571- no input all lat active: 298

6e6e342fad47dd29VOLKSWAGEN GOLF 7TH GENWVWVF7AU2........
VOLKSWAGEN Golf R Hatchback 2018 🆚Volkswagen Golf Alltrack 2015-19
54 routes, 550 segments
- car faulted: 5- VIN model mismatch (info): 1
- all lat active: 35- no input all lat active: 9

Dongles to re-run category: 2024aefc4c4f766c 6e6e342fad47dd29

@jyoung8607 this is that fingerprinting exact match mismatch I was talking about


fix(#264): skip simple on list in used_for_releases

closes #264
History:

feat(#264): test case
feat(#264): simple list

PR-Codex overview
This PR enhances the used_for_releases function in workflows.py to handle lists in addition to strings. It also adds a test case in test_workflows.py to ensure the function returns False when the on parameter is a list.
Detailed summary

Updated the condition in workflows.py to check if on is a list.
Added a new test method test_returns_false_on_simple_list in test_workflows.py.
The test verifies that used_for_releases returns False for a list input.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 11min).


update rust-rocksdb for forward compatibility with v5.2

Signed-off-by: tabokie<EMAIL_ADDRESS>What problem does this PR solve?
Problem Summary:
https://github.com/tikv/rocksdb/pull/252 introduced a new RocksDB configuration item to v5.2.0, making it unable to rollback to older versions.
The error message reads:
[lib.rs:466] ["failed to load_latest_options \"Invalid argument: Unable to parse the specified CF option disable_write_stall\""]

What is changed and how it works?
What's Changed:
Cherry-pick the configuration item to older release.
Related changes
https://github.com/tikv/rocksdb/pull/252
https://github.com/tikv/rust-rocksdb/pull/657
Check List
Tests

Unit test

Release note
None

I would like to include https://github.com/tikv/titan/pull/223. will merge that one soon.

/merge


Improve Dutch translation

This fixes several space issues, d/t errors, and encoding errors, and changes the wording to be more in line with other Dutch translations.

Thanks. Seems to me that you forgot to generate the updated pacaur.pot file before translating (I cannot see the new string that has been added recently). You might want to double check that.

You're right, I hadn't thought of checking for updated strings. Should all be in there now.

Squashed both commits and merged. Thanks again!


How to access laravel functions in the twig

I want to use env('VERSION') , variable inside twig, but it is saying The function "env" does not exist in "base"

To use Cdn::asset() function of vinelab cdn , it is giving me the error Unexpected token "punctuation" of value ":" ("end of print statement" expected)

you can add function in twigbridge.php inside function array.
First, you have to add Cdn facade inside facade array in twigbridge.php and you can call Cdn.asset()

Search helpers.php file for a function with "env" word in it. I believe there should be getenv() somewhere there.

I also got a solution...
Just add env in the functions array in config/twigbridge.php and it works well.

Here's my solution. If you find that you're using a PHP function a lot, you should add it to the twigbridge config file. Otherwise, below can be used for "quick fixes". It uses PHP 5.6 features, so make sure to update if you're using something lower.
FuncProxy class:
// app/Twig/FuncProxy.php

<?php

namespace App\Twig;

class FuncProxy
{
    public function __call($func, $args)
    {
        if (function_exists($func)) {
            return $func(...$args);
        } else {
            // You might want to do something else here, like throw an exception.
            return null;
        }
    }
}

And a global instance of the class. You're welcome to change the global's name, but I find "PHP" to be helpful, so that I know I'm using the function proxy. You could also use something like "Func", etc.
// config/twigbridge.php

// ...

'globals' => [
    'PHP' => new \App\Twig\FuncProxy(),
],
// ...

Then in your twig files:

<span>{{ PHP.ucfirst('foobar baz') }}</span>

This doesn't support namespaced functions, static method, etc.

Thanks @kfriend for a global solution.


"DBInstanceClass" parameter is interpreted as a secure string

cfn-lint version: (cfn-lint --version)
cfn-lint 0.10.1
Description of issue.
I was prompted to add NoEcho to my DBIstanceClass Parameter in CloudFormation
14:26 MacOS: infrastructure_as_code/ >$ cat -n NestedTemplates/datastore-resources.yml | head -n 30
     1	---
     2	AWSTemplateFormatVersion: '2010-09-09'
     3
     4	Parameters:
...
    24	  DBInstanceClass:
    25	    Description: The desired size of RDS instances.
    26	    Type: String
    27	    Default: db.r4.xlarge
    28
    29	Resources:
...
14:26 MacOS: infrastructure_as_code/ >$ cfn-lint NestedTemplates/datastore-resources.yml
W2501 Parameter DBInstanceClass should have NoEcho True
NestedTemplates/datastore-resources.yml:24:3

14:26 MacOS: infrastructure_as_code/ >$

After perusing through the code I have determined that this is user error:
15:34 MacOS: NestedTemplates/ >$ grep DBInstanceClass datastore-resources.yml
  DBInstanceClass:
        DBInstanceClass: !Ref DBInstanceClass
        DBInstanceClass: !Ref DBInstanceClass
        DBInstanceClass: !Ref DBInstanceClass
      MasterUserPassword: !Ref DBInstanceClass
15:34 MacOS: NestedTemplates/ >$

https://github.com/awslabs/cfn-python-lint/blob/master/src/cfnlint/rules/resources/properties/Password.py#L36
😿

Reopening this for PR #519.

PR has been merged.


test staging

Marked as status/ready for test in 0.9-9-STAGING by CI build #16.

Marked as status/tested in 0.9-9-SNAPSHOT by CI build #8.