bump to image version 3.2.4 is causing failures

All our pipelines started throwing this error this morning, which have all been after the bump to image version 3.2.4
2024-02-01 17:36:11,719 [MainThread  ] [WARNI]  Failed to get the checkov mappings and guidelines from None/bridgecrew/api/v2/guidelines. Skips using BC_* IDs will not work.
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/urllib3/connection.py", line 203, in _new_conn
    sock = connection.create_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/util/connection.py", line 60, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/socket.py", line 962, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -2] Name or service not known

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 791, in urlopen
    response = self._make_request(
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 497, in _make_request
    conn.request(
  File "/usr/local/lib/python3.11/site-packages/urllib3/connection.py", line [39](https://github.com//actions/runs/7745327156/job/21121047707#step:10:40)5, in request
    self.endheaders()
  File "/usr/local/lib/python3.11/http/client.py", line 1289, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.11/http/client.py", line 1048, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.11/http/client.py", line 986, in send
    self.connect()
  File "/usr/local/lib/python3.11/site-packages/urllib3/connection.py", line 2[43](https://github.com//actions/runs/7745327156/job/21121047707#step:10:44), in connect
    self.sock = self._new_conn()
                ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connection.py", line 210, in _new_conn
    raise NameResolutionError(self.host, self, e) from e
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPConnection object at 0x7ff4874e1510>: Failed to resolve 'none' ([Errno -2] Name or service not known)

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/checkov/common/bridgecrew/platform_integration.py", line 1162, in get_public_run_config
    request = self.http.request("GET", self.guidelines_api_url, headers=headers)  # type:ignore[no-untyped-call]
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/_request_methods.py", line 110, in request
    return self.request_encode_url(
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/_request_methods.py", line 143, in request_encode_url
    return self.urlopen(method, url, **extra_kw)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/poolmanager.py", line [44](https://github.com//actions/runs/7745327156/job/21121047707#step:10:45)3, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 875, in urlopen
    return self.urlopen(
           ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 875, in urlopen
    return self.urlopen(
           ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 875, in urlopen
    return self.urlopen(
           ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 8[45](https://github.com//actions/runs/7745327156/job/21121047707#step:10:46), in urlopen
    retries = retries.increment(
              ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/util/retry.py", line 515, in increment
    raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='none', port=80): Max retries exceeded with url: /bridgecrew/api/v2/guidelines (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x7ff[48](https://github.com//actions/runs/7745327156/job/21121047707#step:10:49)74e1[51](https://github.com//actions/runs/7745327156/job/21121047707#step:10:52)0>: Failed to resolve 'none' ([Errno -2] Name or service not known)"))

Hi @igitcode, are you using a Bridgecrew API Key or is this without any API key?

No API key. Have now seen this same issue across 2 customer environments. For now we've change from using @master to using previous release tag @v12.2655.0

Hi @igitcode , any special configuration, environment variables, flags we should consider for the investigation? Currently we fail to reproduce it 🙏

I am getting exactly the same error while scanning my helm chart. Action invocation is quite simple:
      - name: Scan chart with checkov
        uses: bridgecrewio/checkov-action@v12
        with:
          directory: ${{ github.workspace }}/helm
          var_file: ${{ github.workspace }}/helm/ci/default-values.yaml
          framework: kubernetes
          output_format: cli,sarif
          output_file_path: console,results.sarif
          soft_fail: true

My config looks like this. We are passing in different skip_check ID's between 2 customers, but otherwise the config is the same between the two.
      - name: Checkov
        id: checkov
        uses<EMAIL_ADDRESS>        with:
          directory: ${{ inputs.working-directory }}
          framework: terraform
          skip_check: ${{ inputs.checkov-ignore }} # skip a specific check_id. can be comma separated list
          quiet: true # display only failed checks
          soft_fail: false # do not return an error code if there are failed checks
          output_format: github_failed_only
          download_external_modules: false

Thank you. We will prioritize it internally. If you are Prisma Cloud customers, feel free to contact your Customer Success representatives to increase the priority of this issue.

v12.2655.0

I can confirm, that switching the action to this version makes it work again.

Experiencing same using below GH Action step. Curious part of the error seems to be url resolution:

...from None/bridgecrew/api/v2/guidelines.
...
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPConnection object at 0x7f7eea62d010>: Failed to resolve 'none' ([Errno -2] Name or service not known)

GH Action Step:
name: Scan GitHub Actions
continue-on-error: true
uses: bridgecrewio/checkov-action@v12
with:
  framework: github_actions
  directory: ./.github
  compact: false
  quiet: false
  log_level: WARNING      # optional: set log level.  Skips using BC_* IDs will not work.

I feel that some may not notice it's happening as is doesn't cause the GH workflow to fail

so if it is the transition from 3.2.3(Jan 31) to 3.2.4(Feb1) perhaps this issue should be attached to the checkov repo, specifically this commit
I searched the checkov-action and checkov repo's for 'v2/guidelines' and the only file I came back with was

checkov/checkov/common/bridgecrew/platform_integration.py
216,56:         self.guidelines_api_url = f"{self.api_url}/api/v2/guidelines"

In the above commit, on line 116, removed from the definition value "self.bc_api_url" was the default "https://www.bridgecrew.cloud". So it is now only populated if the OS has BC_API_URL set.

In a third customer environment the same issue was reported, on latest version 3.2.19.
The Checkov action still reported violations it found, but also accompanied by the same stack trace.

Thanks, folks. We will investigate the issue and get this resolved.

@igitcode
we did some modifications in the code so it will fix it.
can you try a newer version to see if it works for you ?
should be from 3.2.28 forward

@omryMen Still seeing the issue on 3.2.32

@igitcode can you add the new log you're seeing
also see the version of checkov-action..
see @ppawlowski 's comment which he mentioned it's already working

we're pulling master version in our workflow:

Showing version 3.2.32 being pulled when workflow runs:

Error message:
2024-03-07 16:57:03,375 [MainThread  ] [WARNI]  Failed to get the checkov mappings and guidelines from None/bridgecrew/api/v2/guidelines. Skips using BC_* IDs will not work.
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/urllib3/connection.py", line 203, in _new_conn
    sock = connection.create_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/util/connection.py", line 60, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/socket.py", line 962, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -2] Name or service not known

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 791, in urlopen
    response = self._make_request(
               ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 497, in _make_request
    conn.request(
  File "/usr/local/lib/python3.11/site-packages/urllib3/connection.py", line [39](https://github.com/NT-NinjaTrader/cd-github-runners/actions/runs/8191886297/job/22402147206#step:11:40)5, in request
    self.endheaders()
  File "/usr/local/lib/python3.11/http/client.py", line 1293, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.11/http/client.py", line 1052, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.11/http/client.py", line 990, in send
    self.connect()
  File "/usr/local/lib/python3.11/site-packages/urllib3/connection.py", line 2[43](https://github.com/NT-NinjaTrader/cd-github-runners/actions/runs/8191886297/job/22402147206#step:11:44), in connect
    self.sock = self._new_conn()
                ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connection.py", line 210, in _new_conn
    raise NameResolutionError(self.host, self, e) from e
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPConnection object at 0x7bef5ac20110>: Failed to resolve 'none' ([Errno -2] Name or service not known)

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/checkov/common/bridgecrew/platform_integration.py", line 1179, in get_public_run_config
    request = self.http.request("GET", self.guidelines_api_url, headers=headers)  # type:ignore[no-untyped-call]
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/_request_methods.py", line 110, in request
    return self.request_encode_url(
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/_request_methods.py", line 143, in request_encode_url
    return self.urlopen(method, url, **extra_kw)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/poolmanager.py", line [44](https://github.com/NT-NinjaTrader/cd-github-runners/actions/runs/8191886297/job/22402147206#step:11:45)3, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 875, in urlopen
    return self.urlopen(
           ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 875, in urlopen
    return self.urlopen(
           ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 875, in urlopen
    return self.urlopen(
           ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 8[45](https://github.com/NT-NinjaTrader/cd-github-runners/actions/runs/8191886297/job/22402147206#step:11:46), in urlopen
    retries = retries.increment(
              ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/urllib3/util/retry.py", line [51](https://github.com/NT-NinjaTrader/cd-github-runners/actions/runs/8191886297/job/22402147206#step:11:52)5, in increment
    raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='none', port=[80](https://github.com/NT-NinjaTrader/cd-github-runners/actions/runs/8191886297/job/22402147206#step:11:81)): Max retries exceeded with url: /bridgecrew/api/v2/guidelines (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x7bef5ac20110>: Failed to resolve 'none' ([Errno -2] Name or service not known)"))

confirmed this is no longer happening as of 3.2.36

We are facing this issue when using a custom SSL certificate. Is there a way to pass the custom SSL cert or ignore warning?

@askkhan84 The issue is you have a self-signed certificate in certificate chain which fails the cert verification.
You can pass a custom CA certificate that signs the certificate (I had a similar issue while using vpn and needed to pass my organization CA cert).
The argument is --ca-certificate <path_to_CA_cert>.


Create Kenya

Person finder for disasters in Kenya

:-1: This does nothing unless I am missing something obvious.

I agree. Closing. Let me know if you actually meant to make any change.


Feature/v1.2 loxonq

pull request that adds:

Optional Screenshot when it encounters Legendaries, Shinies or Golden
Optional Headless mode
Logging improvements
Pokemon json info file for fishing

thanks @loxonq for these improvements !

Issues related to Feature v1.2-Loxonq

Statistics are not updated

Screenshots includes Super Rares

Need to move the  pokemon_info.json file

Use pokemon_info.json for fishing command  ;f

Move held_item emoji at the end or right after the pokemon count


BlobClient.OpenWriteAsync()

SDK Changes

OpenWrite/Async added to BlobClient, calls into BlockBlobClient OpenWrite/Async.
BlobClient.OpenWriteAsync() will wrap a BlockBlobWriteStream in a CryptoStream to be written to when using client-side encryption.

While callers are already expected to call Dispose() properly on a write stream, they MUST call it here to finish writing the blob contents if they are using client-side encryption. FlushAsync() isn't enough. This is due to the nature of CryptoStream when in write mode.

Test Changes

Open write tests in BlockBlobClientTests moved to abstract class Azure.Storage.Common/test/Shared/OpenWriteTestBase.cs.
Added abstract BlobBaseClientOpenWriteTests, BlockBlobClientOpenWriteTests, BlobClientOpenWriteTests, and ClientSideEncryptedBlobClientOpenWriteTests. These implement the client-specific methods to run the tests and allow these three classes to run the same exact tests with different clients.

Client-side encryption gets its own child class because client-side encryption tests that touch the service can only be run live due to the nature of key generation. It's difficult to branch recordable vs live tags on single tests, so a child class with the [LiveOnly] attribute on the test class was made.
Original recordings worked for ported block blob tests, aside from a few that were just generating different names for blobs due to RNG usage.

NOT in this PR

Porting other client's open write tests to use the centralized tests, like we have done with open read. #25621

Potential Confusion in PR

New methods in ClientSideEncryptor and BlobClientSideEncryptor.

Chicken and egg problem to deal with.
Creating a writable CryptoStream requires an already-existing StorageWriteStream for it to forward transformed content to. But we need the crypto metadata we got while generating the CryptoStream's encryption provider BEFORE we make the StorageWriteStream, as StorageWriteStreams need metadata on creation. The way using statements are needed makes this even harder.
Solution was to inject the OpenWrite() call into the CryptoStream generation, letting us call it in between provider and stream generation, when we have the necessary metadata.

API changes have been detected in Azure.Storage.Blobs. You can review API changes here

/azp run net - storage - tests

Resolves #18780

API changes have been detected in Azure.Storage.Blobs. You can review API changes here

/azp run net - storage - tests

API changes have been detected in Azure.Storage.Blobs. You can review API changes here


Revert builder.Unreachable() and add reachable check to builder.Build()

With the controller-runtime upgrade from 8cfdcca, our remote client
Builder interface's Build() method got lazier. Before, if the remote
client was unreachable, Build() itself would fail. Now it won't fail
until the resulting client is actually used. This resulted in our
"unreachable" controller incorrectly marking the ClusterDeployment's
APIURLOverride as reachable when it wasn't, which had the ripple effect
of making the clustersync controller fail early by trying to use that
URL rather than falling back to the default.
This was exposed in situations where the DNS for the APIURLOverride was
being configured via a syncset: the clustersync controller tried to use
a URL that wouldn't resolve, so it couldn't sync the resource that would
make that DNS work.
Initially, to fix this issue, a Reachable() method was added to the Builder, but on further inspection, there are many cases where uses of the Build()`
method result in a client being falsely marked as reachable.
To fix, this PR reverts the Reachable() commit 576401b8d
and the reachability check to the Build() method of the Builder interface.
This internally builds the client and then uses it to query the /apis of the remote client.
xref: HIVE-2300

/assign @2uasimojo

Need to add to kubeconfigBuilder as well

/test e2e-azure
Ignore me, drive by.
/test coverage
infra flake

/retest coverage


Add host functions to support BLS digital signatures

BLS digital signatures are becoming increasingly popular due to their short signatures (relative to the level of security), efficient aggregation property and enabling simple threshold constructions. These are already implemented in some other blockchains such as the ethereum beacon chain and chia.
For Soroban this can enable various advanced authorization schemes for, amongst other things, multisig smart wallets and oracle constructions (as pointed out by chainlink in this blog post).
Most current implementations use the BLS12-381 elliptic curve, which has been proposed in https://github.com/stellar/rs-soroban-env/issues/779.
Questions

Does anyone disagree?
Do we actually need explicit host support for BLS Digital signatures? Depending on the host functions in https://github.com/stellar/rs-soroban-env/issues/779 it might be trivial to implement these on the guest side.
What is the exact set of host functions required? should we introduce anything for threshold constructions or is that left to the contract developer to figure out?
What implementation should we choose?

Note: if you're confused (as I was) about the relationship between BLS digital signatures and the BLS12-381 elliptic curve this is a good starting point.

As you guessed @tomerweller, if you implement the host functions from #779 (including the full hash-to-curve functionality; see my comment in that thread), it will be more or less trivial to add BLS signatures support on top.
For threshold constructions, the most important thing is the ability to do relatively efficient field and group operations. The host functions in #779 already give the required group operations. What's required here is polynomial interpolation, so you'll need field ops in the scalar field of the curve (for BLS12-381, that's a 255-bit field). Adding anything beyond this as host functions probably isn't needed: it should be fine to implement Lagrange interpolation in a smart contract given efficient scalar and group operations.
I'd stick with blst for the implementation, as I mentioned in #779.


Ability to Skip In-Progress Batches in RolloutRun

Dear KusionStack Team,
I am an avid user of the KusionStack rollout project, and I would like to suggest a new feature that I believe would greatly enhance its functionality and flexibility.
Feature Request
I propose the addition of a feature that would allow users to skip in-progress batches during a RolloutRun. This feature would enable operators to bypass certain batches that are deemed unnecessary or if a critical issue has been identified that warrants them to halt and move onto the next batch without completing the current one.
Current Limitations
Currently, users are required to let each batch in a RolloutRun to either fully complete or fail before moving on to subsequent batches. However, there might be scenarios where the need to skip an in-progress batch arises, and the current system does not accommodate this level of control.

I need to rethink the skip operation and need to answer the following questions

Should we allow skipping of ongoing grayscale releases
Should we allow skipping of ongoing batch releases
How should we safely skip them to properly recycle or revert changes made during the release process, such as the release generating new workloads, services, routes, etc.?


Clear notification value in mdns_hostname_set.

When calling mdns_hostname_set, xTaskNotifyWait is called without clearing the notification value on exit.
This causes subsequent calls to xTaskNotifyWait or ulTaskNotifyTake to unexpectedly not block.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your contribution.

Thanks for your contribution, changes have been merged with https://github.com/espressif/esp-idf/commit/83a4ddbd250e2b386bccabb4705d4c58c1a22bcb.

Thanks!


Changing the Browse Order, cont.

Discussed in https://github.com/orgs/CollectionBuilder/discussions/72

Originally posted by **mldhistory** December 15, 2022
Hello!
I'm having trouble understanding the implementation of the config-browse.csv file. I would like to modify the sort order on the browse page of my collection so the default order shows the cards in the order that I have them entered in my .csv file. The current default is a random sort.  Also, how would I add additional sort-fields to the drop-down? The current list of sort fields in the dropdown (random,title,date) doesn't seem to correspond to the existing config-browse.csv file entries.
Any advice is much appreciated!
Thanks, Marcie
IN REGARD TO THE ABOVE DISCUSSION
Is there a way to have the Browse page sort to any other parameter (e.g. Title) by default?

@eobrandon99 yes, but it's not a configuration option so involves editing the template a bit. For example, to sort by Title by default:
In "_layouts/browse.html", you will find text inside a button element that looks like:
Sort by Random

Replace the Random with Title.
Next, just below that look for the buttons that look like:
<button class="dropdown-item browse-sort-item active" data-filter="random">Random</button>
<button class="dropdown-item browse-sort-item" data-filter="title">Title</button>

Swap the order around like:
<button class="dropdown-item browse-sort-item active" data-filter="title">Title</button>
<button class="dropdown-item browse-sort-item" data-filter="random">Random</button>

Next in "_includes/js/browse-js.html", search for the lines that look like:
/* randomize items once at page load */
shuffle(items);

Comment out the shuffle and add a sorting function instead, so it looks like:
/* randomize items once at page load */
//shuffle(items);
/* sort by title at page load */
sorting(items,"title");

You could do the same with any other metadata field that you want to make default.
(honestly, this is harder than it should be, we hope to re-write the browse js before too long, and might make this a configuration option or at least easier to do!)


Example for training CNN with mixed precision

I've added an example for training a CNN to classify images from CIFAR10 using the new mixed-precision API in TF 1.14.
This notebook explains briefly the idea of mixed-precision, and proceeds to train a CNN with and without mixed-precision to demonstrate the speed-up in training without sacrificing model performance.
The "Link to Colab" in the notebook is set to the link if the notebook is merged (I assumed I was supposed to do that, else the link needs to be edited after merging).
For review purposes, here is the same notebook from my fork.
This is my first contribution, please feel free to provide feedback or comments!
EDIT: identified some performance issues that can significantly improve performance, forced pushed over the previous commit.

@tlkh very impressive PR! Suggestion: would be great to include some links to blog posts as background info in your notebook to explain what is mixed precision - for example, Automatic Mixed Precision in TensorFlow for Faster AI Training on NVIDIA GPUs, and Automatic Mixed Precision for NVIDIA Tensor Core Architecture in TensorFlow

Noted, I’ll be making some improvements then I’ll amend the commit

I have updated the commit and pushed again.
Minor changes to the rest of the notebook, but wrote a bit more about mixed-precision and added some links to useful resources.


The entity(table_name) of JDL can't work well  --"entity B (the_best_entity) // the_best_entity is the table's name"

https://jhipster.github.io/jdl/
entity B (the_best_entity) // the_best_entity is the table's name
my code:
entity Activity (cs_activity)  {
activityId Integer required ,
activityTitle String required maxlength(255),
activityType String  ,
activityBanner String required maxlength(255),
activityStyle String required maxlength(255),
activityDesc String required maxlength(1000),
activityStartDate Integer required ,
activityEndDate Integer required ,
activitySort Integer required ,
activityState Integer required
}
yo jhipster:import-jdl yourfile.jh

paste exception trace here
{ gateway }  » yo jhipster:import-jdl dbentity.jh                                     /cygdrive/e/project/jhipster_micro/gateway
The jdl is being imported.
SyntaxError: Expected "/*", "//", "dto", "entity", "enum", "paginate", "relationship", "service", "{", a space or end of input but "(" found.
at peg$buildException (C:\Users\centling\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\jhipster-uml\lib\dsl\jhGrammar.js:364:14)
at Object.peg$parse [as parse] (C:\Users\centling\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\jhipster-uml\lib\dsl\jhGrammar.js:4403:13)
at DSLParser.parse (C:\Users\centling\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\jhipster-uml\lib\dsl\dsl_parser.js:30:27)
at module.exports.JDLGenerator.extend.default.parseJDL (C:\Users\centling\AppData\Roaming\npm\node_modules\generator-jhipster\generators\import-jdl\index.js:65:37)
at Object. (C:\Users\centling\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\yeoman-generator\lib\base.js:436:25)
at C:\Users\centling\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\yeoman-generator\node_modules\run-async\index.js:26:25
at C:\Users\centling\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\yeoman-generator\node_modules\run-async\index.js:25:19
at C:\Users\centling\AppData\Roaming\npm\node_modules\generator-jhipster\node_modules\yeoman-generator\lib\base.js:448:8
at processImmediate [as _immediateCallback] (timers.js:383:17)

Sorry, I was on holidays and didn't want to check my mails.
I'll reproduce it and fix it.
Thanks for reporting this.

Hello, this issue will have to be checked after work on core objects is done and the JDL parser is moved here. However, it looks like a subgen issue because they don't share everything yet.

Hi @MathieuAA ,
i have the same issue. Is there a workaround to generate the jhipster-Files with the adapted table names? Do you have an approximate schedule when the error will be corrected? Thanks for this nice JDL!

Hi! It should be fixed as soon as the subgen uses this project. In the meantime, you cam use JHipster UML to process your entities. We are working to get this released ASAP, but I don't have an ETA on this.
Le 20 juin 2016 13:28:11 GMT+02:00, "Matthias Grünewald"<EMAIL_ADDRESS>a écrit :

Hi @MathieuAA ,
i have the same issue. Is there a workaround to generate the
jhipster-Files with the adapted table names? Do you have an approximate
schedule when the error will be corrected? Thanks for this nice JDL!

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/jhipster/jhipster-domain-language/issues/19#issuecomment-227117265

--
Mathieu ABOU-AICHI

The feature lacking in the subgen has been implemented in the dev branch, which should be released very, very, very soon (today or tomorrow). Therefore, I'm closing this. Thanks to all of you for reporting this!

Hi Mathieu, was this issue solved ? I am also facing this issue

What? Again? It has already been released... Are you sure you're using the last version of JHipster?

yes. I am new with JHispter. Just installed it two days ago

I'll reopen this in a "to test" state. I'll test it tonight.

Thanks a lot :) waiting for your test results and reply

Hi, I didn't have any issue with grammar... are you sure it's the same stacktrace? if not, please create a new issue and give us all the information we might need.

Thanks Mathieu, I will try again tomorrow and let you know

I forgot: is it the same JDL? if it differs, then you might have found a bug.

Same one as in JHipster studio. Not sure if it matters, but it was on a monolithic App.
I have created a new microservice and will try the JDL again today

Oh. What does matter is the fact that the problem seems to happen when one uses the JDL-Studio. @deepu105 can you investigate please?

First of all there is no such sample in JDL studio, second I do not do any processiing on the JDL content its exported as it is. Third @davidweianibone hasnt given any useful info like JDL file, stack trace etc for us to investigate
@davidweianibone if you have an issue please open a new ticket with JDL used and error stack trace and steps to reproduce


Rails.application.assets return nil when config.assets.compile = true

With sprockets-rails 3.0.0. When we set
config.assets.compile = true
we get
Rails.application.assets #=> nil
With this it causes default_load_path to error. undefined method '#path' for NilClass. https://github.com/Compass/compass-rails/blob/master/lib/compass-rails/configuration.rb#L43
Because this https://github.com/Compass/compass-rails/blob/master/lib/compass-rails.rb#L37 returns nil.
Does anybody know any workaround this for now?
similar issues

https://github.com/rails/sprockets-rails/issues/306

I think more details should be provided about your environment (like related gems & their versions)
to help them understand & solve this issue

This isn't an issue with his environment; this is a change in Sprockets-Rails that renders Compass-Rails incompatible with version 3.0. In version 3.0, in production environments, config.assets (the Sprockets environment) is nil. Compass-Rails depends on having access to the Sprockets environment in production during the precompile process.
I fixed this in my gem by generating the Sprockets environment manually; see https://github.com/SquareSquash/javascript/commit/5873143f38e83f9c23108c082414c0d2d815d33d

The code in compass-rails access through Rails.application.assets
But the sprockets-rails README in both 2.3.3 (latest 2.x) & 3.0.0 mentioned that it should be accessed through config.assets

Those two are different things entirely. In development:
>> Rails.application.assets
=> #<Sprockets::Environment:0x3fe3b630d980 root="/Documents/Programs/Rails/flightseein", paths=["/Documents/Programs/Rails/flightseein/app/assets/images", "/Documents/Programs/Rails/flightseein/app/assets/javascripts", "/Documents/Programs/Rails/flightseein/app/assets/stylesheets", "/Documents/Programs/Rails/flightseein/lib/assets/images", "/Documents/Programs/Rails/flightseein/lib/assets/javascripts", "/Documents/Programs/Rails/flightseein/lib/assets/stylesheets", "/Documents/Programs/Rails/flightseein/vendor/assets/javascripts", "/Documents/Programs/Rails/flightseein/vendor/assets/stylesheets"<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>> Rails.application.config.assets
=> {:_blocks=>[#<Proc:0x007fc76b8ead20@/Users/tmorgan/.rvm/gems/ruby-2.3.0@flightseein/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:88>, #<Proc:0x007fc76b8eaa78@/Users/tmorgan/.rvm/gems/ruby-2.3.0@flightseein/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:92>, #<Proc:0x007fc76b8ea730@/Users/tmorgan/.rvm/gems/ruby-2.3.0@flightseein/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:99>, #<Proc:0x007fc76b8e9ce0@/Users/tmorgan/.rvm/gems/ruby-2.3.0@flightseein/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:110>, #<Proc:0x007fc76b8e9718@/Users/tmorgan/.rvm/gems/ruby-2.3.0@flightseein/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:114>, #<Proc:0x007fc76f302a80@/Users/tmorgan/.rvm/gems/ruby-2.3.0@flightseein/gems/autoprefixer-rails-6.3.1/lib/autoprefixer-rails/railtie.rb:12>, #<Proc:0x007fc76f158ab8@/Users/tmorgan/.rvm/gems/ruby-2.3.0@flightseein/gems/sass-rails-5.0.4/lib/sass/rails/railtie.rb:56>], :paths=>["/Documents/Programs/Rails/flightseein/app/assets/images", "/Documents/Programs/Rails/flightseein/app/assets/javascripts", "/Documents/Programs/Rails/flightseein/app/assets/stylesheets", "/Documents/Programs/Rails/flightseein/lib/assets/images", "/Documents/Programs/Rails/flightseein/lib/assets/javascripts", "/Documents/Programs/Rails/flightseein/lib/assets/stylesheets", "/Documents/Programs/Rails/flightseein/vendor/assets/javascripts", "/Documents/Programs/Rails/flightseein/vendor/assets/stylesheets"<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:prefix=>"/assets", :manifest=>nil, :precompile=>[#<Proc:0x007fc76b8f3178@/Users/tmorgan/.rvm/gems/ruby-2.3.0@flightseein/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:61 (lambda)>, /(?:\/|\\|\A)application\.(css|js)$/, "ie.js", "*.png", "*.jpg", "*.jpeg", "*.gif"], :version=>"1.0", :debug=>true, :compile=>true, :digest=>true, :cache_limit=>52428800, :raise_runtime_errors=>true, :resolve_with=>[:environment]}

In production:
2.3.0 :001 > Rails.application.assets
 => nil
2.3.0 :002 > Rails.application.config.assets
 => {:_blocks=>[#<Proc:0x0000000166e418@/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:88>, #<Proc:0x0000000166e1e8@/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:92>, #<Proc:0x0000000166e0a8@/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:99>, #<Proc:0x0000000166da90@/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:110>, #<Proc:0x0000000166d8b0@/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:114>, #<Proc:0x000000035dc570@/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/autoprefixer-rails-6.3.1/lib/autoprefixer-rails/railtie.rb:12>, #<Proc:0x00000003c27da8@/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/sass-rails-5.0.4/lib/sass/rails/railtie.rb:56>], :paths=>["/var/www/www.timothymorgan.info/releases/20160126054631/app/assets/fonts", "/var/www/www.timothymorgan.info/releases/20160126054631/app/assets/images", "/var/www/www.timothymorgan.info/releases/20160126054631/app/assets/javascripts", "/var/www/www.timothymorgan.info/releases/20160126054631/app/assets/stylesheets", "/var/www/www.timothymorgan.info/releases/20160126054631/vendor/assets/javascripts", "/var/www/www.timothymorgan.info/releases/20160126054631/vendor/assets/stylesheets", "/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/font-awesome-rails-<IP_ADDRESS>/app/assets/fonts", "/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/font-awesome-rails-<IP_ADDRESS>/app/assets/stylesheets", "/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/coffee-rails-4.1.1/lib/assets/javascripts", "/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/jquery-rails-4.1.0/vendor/assets/javascripts"], :prefix=>"/assets", :manifest=>nil, :precompile=>[#<Proc:0x00000001670f10@/var/www/www.timothymorgan.info/shared/bundle/ruby/2.3.0/gems/sprockets-rails-3.0.0/lib/sprockets/railtie.rb:61 (lambda)>, /(?:\/|\\|\A)application\.(css|js)$/, "print.css"], :version=>"1.0", :debug=>false, :compile=>false, :digest=>true, :cache_limit=>52428800, :js_compressor=>:uglifier, :css_compressor=>:sass, :resolve_with=>[:manifest]}

@RISCfuture @ChristianStancu @thaichor @mvastola @craigmcnamara @vojtad  I've added a PR to fix this.  Could someone review it please?  If it's okay, I'll tidy up the changes and version numbers etc to make it easy for @craigmcnamara to release it.  All feedback welcome.
After submitting this PR, I noticed @vojtad also created a PR earlier today, taking a different approach: https://github.com/Compass/compass-rails/pull/262

@thaichor I think you intended to say config.assets.compile = false in the title of this issue.  If that's the case could you edit the issue title please, to change true to false?

@timhaines See https://github.com/Compass/compass-rails/issues/257#issuecomment-174849030 — Rails.application.assets and Rails.application.config.assets are completely different things.


chore: do not build all binaries atomically

Description
Make sure one failing binary builds doesn't cancel all others. This is useful when experimenting and you still want others binary to build.
The step will still fail if one of the binary build fails, retaining the current atomicity of the release.

:tada: This PR is included in v1.19.0 :tada:


Dead code-paths in Hi Haddock

Removing this code has no impact on the output (try accepting before and after the commit). Offhand, it doesn't seem to impact any of the docs for libraries bundled with GHC either. We should either:

add test cases exercising the code paths this PR removes (I can't think of any such cases)
add test cases which used to (before Hi Haddock) exercise these code paths and are now broken
merge this

Thanks for the quick review! :D
There is definitely some more global cleanup to do too, but I wanted to make sure this code was really supposed to be dead. I agree with getting rid of Maps in a separate PR.


[fix] liquid template "{{ page.html }}" contains tags for preview

Coverage decreased (-9.7%) to 59.5% when pulling 2f0135cd3a41b029d3fc08f2fcabceee7b51df2b on sunny4381:fixes/liquid-template-html-contains-preview-controller into 6eda73163d44033bb46b69d2d6aeb4dadf15d4e9 on shirasagi:master.


New Extensions

-EdgeInsets.zero added as paddingZero,
-Network Images added on StringExtension as NetworkImageExtension,
-LocalizationExtension added on StringExtension,
-warnings cleaned

localization is removed and it is committed


bug: Commands that require open files continue instead of stopping

Version
main e75560d7d7380a662a663ed2c10bc1607c7db60b
Describe the bug
Some commands require an open file and post unhelpful output to the transcript:
https://github.com/sourcegraph/cody/assets/153/2b23fc69-961f-40de-95b0-adcbfe885f5e
Expected behavior
Only the native VS Code error notification is posted, and both the request and response is never added to the transcript.
Additional context
No response

following up on this - this seems to only happen if you invoke commands from the chat input and not the side panel
https://github.com/sourcegraph/cody/assets/51868853/db295441-7d9b-4051-8226-e7d1a683bc56

I had a go at fixing this a couple of different ways, but they all feel bad for different reasons so I'm hoping for some pointers.
The native VS Code error message shown comes from here in the CommandRunner:
https://github.com/sourcegraph/cody/blob/2a00da01ae8b83ecd5450af7be2682c32edf3080/vscode/src/commands/CommandRunner.ts#L70-L74
But this code doesn't directly seem to have the ability to influence the call to the LLM. I thought maybe we should set some kind of errorKind flag on the command runner to indicate that it won't be able to run.
Here seems like a convenient place to read such a flag to avoid sending anything to the LLM and perhaps showing a nicer error in the chat conversation. There seems to be something similar for missing selections:
https://github.com/sourcegraph/cody/blob/2a00da01ae8b83ecd5450af7be2682c32edf3080/lib/shared/src/chat/recipes/custom-prompt.ts#L61-L63
However, at this point we only have access to the command (CodyPrompt) and not the CommandRunner (since getCommand returns only the command, and disposes the runner). Changing getCommand() to the runner could work, but since that interface is outside vscode/ presumably would be breaking to other editors.
Putting the errorKind on the command (CodyPrompt) instead seemed like it could work, and it did.. but it seems like that object may be reused reused (once I trigger the error, every /smell command fails with it, even if I've no opened the file). This seems slightly odd to me, as other properties on that class look like they're specific to each prompt.
Another thing I thought could work is if we could have the equivalent of the "selection" check above for this command (eg. check whether this command requires an active file and we don't have one), but it's not clear to me where the flags on this contextConfig come from (of what they really mean... contextConfig.selection appears to be used in this condition as if it means "we need a selection", however the the comment on the interface says "Type of context available for prompt building" so I'm unsure if it really means we need this, or we have this.
Not sure who has the most context around this that might be able to provide pointers (I suspect @abeatrix?).


cmd/gofmt: make gofmt always insert a blank line between functions

What version of Go are you using (go version)?
go version go1.8.3 darwin/amd64
What did you do?
I did gofmt on golang code as below.
package main
import "fmt"
func foo() {

	fmt.Println("this is foo!")
	// ...
	// may lots codes here
	// ...

}
func bar() {

	fmt.Println("this is bar!")
	// ...
	// may lots codes here
	// ...

}
func main() {

	fmt.Println("hello, world")
	foo()

	bar()

}

What did you expect to see?
package main

import "fmt"

func foo() {
	fmt.Println("this is foo!")
	// ...
	// may lots codes here
	// ...
}

func bar() {
	fmt.Println("this is bar!")
	// ...
	// may lots codes here
	// ...
}

func main() {
	fmt.Println("hello, world")
	foo()

	bar()
}

What did you see instead?
package main

import "fmt"

func foo() {

	fmt.Println("this is foo!")
	// ...
	// may lots codes here
	// ...

}
func bar() {

	fmt.Println("this is bar!")
	// ...
	// may lots codes here
	// ...

}
func main() {

	fmt.Println("hello, world")
	foo()

	bar()

}

cc @griesemer

I'm not sure on the "always" part. For example, this sort of thing is useful:
func (n *Node) Noescape() bool { return n.flags&nodeNoescape != 0 }
func (n *Node) Bounded() bool  { return n.flags&nodeBounded != 0 }
func (n *Node) Addable() bool  { return n.flags&nodeAddable != 0 }
func (n *Node) HasCall() bool  { return n.flags&nodeHasCall != 0 }
func (n *Node) Likely() bool   { return n.flags&nodeLikely != 0 }
func (n *Node) HasVal() bool   { return n.flags&nodeHasVal != 0 }
func (n *Node) HasOpt() bool   { return n.flags&nodeHasOpt != 0 }
func (n *Node) Embedded() bool { return n.flags&nodeEmbedded != 0 }

However, I would agree that it makes little sense to allow no empty line between two funcs if either is multi-line.

This is working as intended. We went back and forth on this many times. The conclusion here is that gofmt respects the decision of the source author. Sometimes you have a situation with multiple one-liners where one of them, in the middle, spans multiple lines. We don't want to break that grouping; i.e., we want to keep all these functions together to express that they belong together.
There's lots of if's and when's etc. and there's just no good way to capture intent well, automatically. Better to let the author decide.


MAINT: ensure tests are included in wheels

Also test install via sdist and wheel on TravisCI. Closes gh-280.

A test unrelated to this PR is failing:
FAIL: test_deprecations.test_MODES_attributes_usage_deprecation
....
AssertionError: No warning raised when calling dwt

I can't reproduce the failure locally, but it's consistent on TravisCI it looks like. I'm tempted to just delete that test. We're removing that deprecated code anyway before the next release.

the same error is also present in python 2.7 on Appveyor, but I do not see it locally when using 2.7.
I would be find with removing that test.

Nice to see tests for wheel and sdist builds were added on Travis!
I see you have included the files via package_data rather than adding an __init__.py in the test folders.  I don't see a problem with doing it that way, but out of curiosity, do you recall the drawbacks of the __init__.py approach?

Failing test removed, seems happy now.

do you recall the drawbacks of the __init__.py approach?

One is that tests will start to show up when tab-completing. There was something more subtle as well, but can't remember.

Codecov Report

Merging #292 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #292   +/-   ##
=======================================
  Coverage   86.26%   86.26%
=======================================
  Files          21       21
  Lines        3086     3086
  Branches      532      532
=======================================
  Hits         2662     2662
- Misses        371      372    +1
+ Partials       53       52    -1

Impacted Files
Coverage Δ

pywt/_wavelet_packets.py
78.12% <0%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

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

Thanks @rgommers!


refactor: style in ValidatedFrame

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #626

PR #627   👈

This stack of pull requests is managed by Graphite.


fix(STONEINTG-897): don't require chains for failed build PLRs

It's not guaranteed that a failed build pipelineRun will be processed by Tekton chains
The integration service still needs to process those pipelineRuns in order to remove their finalizers

Signed-off-by: dirgim<EMAIL_ADDRESS>Maintainers will complete the following section

[ ] Commit messages are descriptive enough (hints)
[ ] Code coverage from testing does not decrease and new code is covered (check the PR coverage on codecov)
[ ] Controllers diagrams are updated when PR changes controllers code  (if applicable)

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

Please upload report for BASE (main@9aebb5b). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #873   +/-   ##
=======================================
  Coverage        ?   69.12%
=======================================
  Files           ?       43
  Lines           ?     4447
  Branches        ?        0
=======================================
  Hits            ?     3074
  Misses          ?     1054
  Partials        ?      319

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


Fix for current node-sass 404 error

Added node-sass to devDependecies. This normally installs as a sub-dependency of one of the packages already listed in devDependencies but currently users get a 404 error when running npm install without it.
Also added a warning about a conflict arrising from altering the package.json fields without altering the relevant sections of the Header also.

Thanks for this... good changed!
Do you mind bumping the boilerplate version to 2.2.6 in package.json and I'll merge this in?
https://github.com/cferdinandi/gulp-boilerplate/blob/master/package.json#L16

No problem. Done.


More intelligent Vue polyfills

We don't need to add most of polyfills if they are not used in component, that we can try to detect based on analyzing ast. Need to check for the following:

[ ] el based on .el access
[ ] slots based on .slots access
[ ] dispatchEvent based on .dispatchEvent access
[ ] setState based on .dispatchEvent access
[ ] children based on .children access
[ ] parents based on .parents access
[ ] refs based on .parents access

Done


Forwarding SMTP connection not closed

Investigate and fix why email was not forwarding and complaining about previous connection not being closed:
noggin-forward-server  | 11:51:30 fail: Nogginbox.MailForwarder.Server.MessageStores.ForwardingMessageStore[0]
Error forwarding email - Failed to connect to mailserver:fb84e8e09caf4a8ae811c7a2320746.pamx1.hotmail.com. on port 25
System.Exception: Failed to connect to mailserver:fb84e8e09caf4a8ae811c7a2320746.pamx1.hotmail.com. on port 25
---> System.InvalidOperationException: The SmtpClient is already connected.
at MailKit.Net.Smtp.SmtpClient.ValidateArguments(String host, Int32 port)
at MailKit.Net.Smtp.SmtpClient.ConnectAsync(String host, Int32 port, SecureSocketOptions options, CancellationToken cancellationToken)
at Nogginbox.MailForwarder.Server.MessageStores.ForwardingMessageStore.ForwardEmailAsync(String mailserverDomain, MailboxAddress sender, List`1 forwardRecipients, ISessionContext context, IMessageTransaction transaction, MimeMessage message, CancellationToken cancellationToken) in /src/Nogginbox.MailForwarder.Server/MessageStores/ForwardingMessageStore.cs:line 97
 --- End of inner exception stack trace ---
at Nogginbox.MailForwarder.Server.MessageStores.ForwardingMessageStore.ForwardEmailAsync(String mailserverDomain, MailboxAddress sender, List`1 forwardRecipients, ISessionContext context, IMessageTransaction transaction, MimeMessage message, CancellationToken cancellationToken) in /src/Nogginbox.MailForwarder.Server/MessageStores/ForwardingMessageStore.cs:line 102
at Nogginbox.MailForwarder.Server.MessageStores.ForwardingMessageStore.<>c__DisplayClass6_2.<<SaveAsync>b__9>d.MoveNext() in /src/Nogginbox.MailForwarder.Server/MessageStores/ForwardingMessageStore.cs:line 69
 --- End of stack trace from previous location ---
at Nogginbox.MailForwarder.Server.MessageStores.ForwardingMessageStore.SaveAsync(ISessionContext context, IMessageTransaction transaction, ReadOnlySequence`1 buffer, CancellationToken cancellationToken) in /src/Nogginbox.MailForwarder.Server/MessageStores/ForwardingMessageStore.cs:line 71

As a catch, can we send a timout cancelation token into the mail client methods?


Try out virtual cards on Open Collective

As documented here.
Some companies don't accept these, but we should use them wherever possible to simplify administrative work.
Depends on:

[x] #14
[ ] #13

It doesn't seem like Stripe Issuing is available in Denmark yet: https://stripe.com/docs/issuing/global

This will be handled by our fiscal host going forward; see #31.


[5.7] an array of messages for custom validation rules

At a current project we're working on we have a lot(+200) rules for validating a request. The solution is splitting these rules into separate custom rule classes. Like so
// Before
'units.*.articles.*.date_start' => 'required|date'
'units.*.articles.*.date_end' => 'required|date'

// After
'units.*.articles' => new UnitArticlesRule

Then in our UnitArticlesRule class we do the following:
class HabitantContractArticlesRule implements Rule
{
    /** @var array */
    protected $messages = [];

    public function passes($attribute, $value)
    {
        foreach ($value as $article){
            $validator = Validator::make($article, $this->rules($article));

            if($validator->fails()){
                $this->messages = array_merge($this->messages, $validator->errors()->all());
            }
        }

        return count($this->messages) === [];
    }

    public function message()
    {
        return $this->messages;
    }

    public function rules(array $article){
        $rules = [
            'date_start' => 'nullable|date',
            'date_end' => 'nullable|date',
        ];

        if($article['date_start'] !== null){
            $rules["date_end"][] = 'after:' . Carbon::make($article['date_start']);
         }

        return $rules;
    }
}

As you can see, multiple articles can have validation errors. In the current implementations of custom validation rules we can only return a string. This PR adds the ability to return an array of messages so the example above will work.
The PR won't break any functionality and two tests are added.

Should be fixed now!

How about being able to return \Illuminate\Support\MessageBag ? If you're using validator in your custom rule, as the example shows, you could just return $validator->errors() instead of having to parse it into an array.

Also: I think you should keep in mind that the field where the error is shown. Right now multiple errors are shown on the parent field:
foreach ($messages as $message) {
    $this->messages->add($attribute, $this->makeReplacements(
        $message, $attribute, get_class($rule), []
    ));
}

While I expected it to be more like:
foreach ($messages as $childAttribute => $message) {
    $nestedAttribute = "{$attribute}.{$childAttribute}";

    $this->messages->add($nestedAttribute, $this->makeReplacements(
        $message, $nestedAttribute, get_class($rule), []
    ));
}

@brendt Interesting. Why would it make assumptions about a child attribute? I'm not sure I would expect that behavior.

@taylorotwell let's assume the following example, it's nothing I'd do IRL, but it illustrates my point.
// The rules in the request class

$rules = [
    'articles' => new ArticleRule(),
];

// ArticleRule will validate two properties: type and amount

public function passes($attribute, $value)
{
    if (!in_array($value['type'], ArticleType::toArray())) {
        $this->messages['type'] = 'The article type must be defined in the ArticleType enum.';
    }

    if ($value['amount'] < 0) {
        $this->messages['amount'] = 'You can only specify a positive amount.';
    }

    return empty($this->messages);
}

Say both rules fail, we'd get two errors in the final result, mapping to the type and amount field respectively. I don't think this is the correct behaviour, as they should map to articles.*.type and articles.*.amount.


Wait for testhost stderr to be available if connection is broken.

This allows to provide user information if the test host has crashed.
Don't send stderr to console runner output if it's null or empty.

@codito,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


chown : file is not working

I recently noticed that the command chown is not working correctly.
When executing chown <user>: file.txt the command succeeds without any error, but not the user nor the group is changed.
I think this behaviour should be covered by the test test_chown_myself_second, but there only the succeed is checked, not the change of the user.
I sadly don't know how this could be checked in the tests nor how the group is determined just from the username :cry:. Maybe somebody else could solve this.

I'm working on this.

When executing chown <user>: file.txt the command succeeds without any error, but not the user nor the group is changed.

Afaik only the user should be changed in this case.

I think this behaviour should be covered by the test test_chown_myself_second, but there only the succeed is checked, not the change of the user.

The test would be to check if the owner really changed. However this is tricky since afaik only superuser can change ownership to another user. This cannot be done in the test environment.

I sadly don't know how this could be checked in the tests nor how the group is determined just from the username 😢. Maybe somebody else could solve this.

I did a workaround to test for this issue. See the commit.

When executing chown : file.txt the command succeeds without any error, but not the user nor the group is changed.

Afaik only the user should be changed in this case.

I just read in the manpage that the group is indeed also changed:
If a colon but no group name follows the user name, that user is made the owner of the files and the group of the  files  is  changed  to  that user's login group.
From what I read in the code so far, uu_chown is not doing that right now.
Also I noticed that the behavior for a single colon is wrong:
If only a colon is given, or if the entire operand is empty, neither the owner nor the group is changed.
$ chown -v : file.txt 2>out_err ; echo $? ; cat out_err
ownership of 'file.txt' retained
0
$ target/debug/chown --verbose : file.txt 2>out_err ; echo $? ; cat out_err
1
chown: invalid user: ':'

wrong message, wrong stdout/stderr, wrong return code :(


Pair js-crawler with PhantomJS

Hey,
First of all I would like express my gratitude for developing this sweet web crawler.
Is there a way integrate js-crawler with PhantomJS?
I really need their functionalities in a single place as I would like to use PhantomJS for network monitoring.
Looking forward to hearing from you!

Hi Tynael,
Now js-crawler is using Node.js 'request' module to make requests. In the future versions it is possible to add support to using other request 'engines' such as PhantomJS.

Is there a way integrate js-crawler with PhantomJS?
So in the future there are such plans, unfortunately no at the moment.

Please, note, that it seems that the active development of PhantomJS has ended, and a better option to use may be to use headless Chrome.
https://groups.google.com/forum/#!topic/phantomjs/9aI5d-LDuNE


PHP 8 compatibility

Does this library run on PHP 8.1? Im getting errors which seem to stem from the League\Url library. Any ideas how to get this working pls? Thnx
Deprecated function: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in League\Url\Components\AbstractComponent->__toString() (line 67 of /var/www/html/drupal/vendor/league/url/src/Components/AbstractComponent.php)

This library does not provide PHP 8 support. Let me clarify with the main developers if there is a plan for that!

Thanks that would be help as PHP 7.4 is end of life. I would be happy to assist with upgrade as I need this to upgrade my site to Drupal 10.

Hello all,
I try to use the Drupal module phpcmis, which depends on this library. But the library does not work with PHP 8.0. Is there a plan to migrate ?
Thanks,
Alexander

We are open for PR. This Library was funded many years ago by an EU project that has ended.
There is usage in the Drupal community: Maybe there is a way to coordinate an effort there, too?


RxJava线程

computationScheduler  >>> EventLoopsScheduler
EventLoopsScheduler.java
static final FixedSchedulerPool NONE = new FixedSchedulerPool(null, 0);

static final class FixedSchedulerPool {
        final int cores;

        final PoolWorker[] eventLoops;
        long n;

        FixedSchedulerPool(ThreadFactory threadFactory, int maxThreads) {
            // initialize event loops
            this.cores = maxThreads;
            this.eventLoops = new PoolWorker[maxThreads];  // 这里新建了一个线程组
            for (int i = 0; i < maxThreads; i++) {
                // new出每个线程
                this.eventLoops[i] = new PoolWorker(threadFactory);
            }
        }

        public PoolWorker getEventLoop() {
            int c = cores;
            if (c == 0) {
                return SHUTDOWN_WORKER;
            }
            // simple round robin, improvements to come
            return eventLoops[(int)(n++ % c)];
        }

        public void shutdown() {
            for (PoolWorker w : eventLoops) {
                w.unsubscribe();
            }
        }
    }

    static final class PoolWorker extends NewThreadWorker {
        PoolWorker(ThreadFactory threadFactory) {
            super(threadFactory);
        }
    }

NewThreadWorker.java
    public NewThreadWorker(ThreadFactory threadFactory) {
        ScheduledExecutorService exec = Executors.newScheduledThreadPool(1, threadFactory);
        // Java 7+: cancelled future tasks can be removed from the executor thus avoiding memory leak
        boolean cancelSupported = tryEnableCancelPolicy(exec);
        if (!cancelSupported && exec instanceof ScheduledThreadPoolExecutor) {
            registerExecutor((ScheduledThreadPoolExecutor)exec);
        }
        executor = exec;
    }


set --gen_kwargs arg to None

and added some help messages.

@haileyschoelkopf @lintangsutawika should we add short args as well? will make inputs a bit more convenient and allow for chaining flags (for e.g. -ws for -w and -s).

I'm open to it, but would be better as a different PR


API: read_csv should default to ignore_index=True when no index_col

xref https://github.com/pydata/pandas/issues/12618
In [13]: import dask

In [14]: dask.__version__
Out[14]: '0.8.0'

In [15]: pd.__version__
Out[15]: '0.18.0+7.g17a5982'

In [4]: import glob

In [5]: DataFrame(np.arange(10).reshape(-1,2)).to_csv('file1.csv')

In [6]: DataFrame(np.arange(10).reshape(-1,2)).to_csv('file2.csv')

In [7]: pd.concat([ pd.read_csv(f, index_col=0) for f in glob.glob('file*.csv') ], ignore_index=True)
Out[7]:
   0  1
0  0  1
1  2  3
2  4  5
3  6  7
4  8  9
5  0  1
6  2  3
7  4  5
8  6  7
9  8  9

In [11]: import dask.dataframe as dd

In [12]: dd.read_csv('file*.csv', header=0, usecols=[1,2]).compute()
Out[12]:
   0  1
0  0  1
1  2  3
2  4  5
3  6  7
4  8  9
0  0  1
1  2  3
2  4  5
3  6  7
4  8  9

the concat should be ignore_index=True, otherwise you are implicitly setting the index

Side issue (maybe an example in the docs would help), about how to ignore an index.

I'd really like to do:

dd.read_csv('file*.csv', header=0, index_col=0).compute()
(see the above linked issue). This requires me to .set_index(...) after on a dummy column though
I know I have an index, but I
In [17]: dd.read_csv('file*.csv', header=0, names=['col',0,1]).compute()
Out[17]:
   col  0  1
0    0  0  1
1    1  2  3
2    2  4  5
3    3  6  7
4    4  8  9
0    0  0  1
1    1  2  3
2    2  4  5
3    3  6  7
4    4  8  9

Then drop it or .reset_index

This is tricky to do correctly, and in most cases doesn't matter:

You really only see the default index if you're reading in many files and then concatenating into a large frame. If you're using dask to work with many files, it's likely that the concatenated result is a bit big.
 We might be able to track this using a lot more metadata, but would be a large maintenance burden
I can't think of many cases where knowing the row numbers (the default index) is important to the analysis.

I'm going to close this for now, feel free to reopen if needed.

Looks like I said I'd close it, but never did :/. Closing now.


Flatten scores in inference forward

The transformers pipeline runs each input sequentially with batch size 1, and in the post-processing step when using top_k, it requires a 1D tensor to iterate over. This PR flattens the output of the model if it's batch size one. I've tested this:
from fastfit import FastFit
from transformers import AutoTokenizer, pipeline

model = FastFit.from_pretrained("../fast-fit")
tokenizer = AutoTokenizer.from_pretrained("roberta-large")
classifier = pipeline("text-classification", model=model, tokenizer=tokenizer,)

# This worked before and still works
print(classifier("I love this package!"))

# This failed before
print(classifier(["When do you think my card will arrive in Sweden?", "Give me back my money!"], top_k=10))

# This still works
x = tokenizer(["Hi", "Hello"], return_tensors="pt")
print(model(x["input_ids"], x["attention_mask"]))

# This will be different
x = tokenizer(["Hi"], return_tensors="pt")
print(model(x["input_ids"], x["attention_mask"]))  # This is a 1D tensor now

I wasn't able to find another implementation of a pipeline-compatible model that I could piggyback off of. Do you see any potential problems with changing the shape of the output for single size batches? Am I missing an obvious solution?
This is the problematic code:
# From transformers/pipelines/text_classification.py in TextClassificationPipeline.postprocess

# score needs to be 1D
dict_scores = [
    {"label": self.model.config.id2label[i], "score": score.item()} for i, score in enumerate(scores)
]

Closes #4

Thanks @OskarLiew !


fwcfg64: Using PackOne instead of PostBuildEvent

I think, PackOne is a better way to place driver files into Install dir.
Signed-off-by: Ilya Rudakov<EMAIL_ADDRESS>

Thanks!


Update value nesting for anchore-engine

Updated the nesting of the values to match that of anchore-engine chart.
https://github.com/kubernetes/charts/blob/master/stable/anchore-engine/values.yaml#L62

Thanks @MMartyn!!!


JMS Endpoints should allow dynamic destination name

Problem
Currently, a JMS endpoint in Citrus (2.7.1) is defined with a static destination-name like this:
<citrus-jms:endpoint id="someJmsEndpoint"
                     destination-name="some.queue"
                     connection-factory="someConFactory"/>

This is problematic if you have tests with lots of different queues which all use the same connection factory. For every queue you need to define a separate endpoint even if only the queue name is different.
Moreover, it is impossible to send messages to a queue whose name is only known at runtime.
Solution
Include a dynamic endpoint header to the JMS endpoint, similar to the HTTP one:
<header>
   <element name="citrus_endpoint_uri"
            value="http://localhost:${port}/${context}"/>
</header>

Example
<send endpoint="someJmsEndpoint">
    <message>
        ...
    </message>
    <header>
        <element name="citrus_jms_destination_name"
                 value="some.other.queue"/>
    </header>
</send>

👍 Thanks for the implementation!

I updated my test code to use Citrus 2.7.2 and wanted to use this feature. I have noticed that the dynamic destination resolver is only used in send actions (JmsProducer) and not in receive (JmsConsumer) actions.
However, being able to set a dynamic destination in receive actions is equally important as doing so in send actions.
Thus, the DestinationNameResolver should also be used in receive actions.

I've digged through the code and realized that it's not easy to support the special header citrus_jms_destination_name for receive actions.
The headers are part of the message Object, which obviously has not yet been created in the receive method. So in case of a receive action the mechanism to extract the special header would have to work differently.
We'd need to somehow extract the header from the validation headers which are also not accessible in the JmsConsumer.
Theoretically, we could use the JMS selector, but I think this would be ugly.

As a workaround you can use the following syntax, see Citrus documentation - Dynamic Endpoints:
<receive endpoint="jms:Hello.Response.Queue?timeout=5000">
    ...
</receive>

This also works for sync JMS like this: jms:sync:Hello.Response.Queue

I think using dynamic endpoints here is the best solution. As you already mentioned accessing the dynamic endpoint resolver is not easy for receive operations due to design limitations. Will close this issue if no further objections.

👍


@material-ui/styles 5.0.0-alpha.22 break styles

[+] The issue is present in the latest release.
[+] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Styles inside the Drawer are broken
Expected Behavior 🤔
Everything works the same as before
Steps to Reproduce 🕹

Open any of the examples with Drawer

2 Add the last version of @material-ui/styles 5.0.0-alpha.22 (everything works with alpha.20)

Replace this import import { StylesProvider } from "@material-ui/core"; to import { StylesProvider } from "@material-ui/styles";

example code:
https://codesandbox.io/s/minidrawer-material-demo-forked-kxrok?file=/index.js

https://codesandbox.io/s/minidrawer-material-demo-forked-kxrok?file=/index.js

https://codesandbox.io/s/minidrawer-material-demo-forked-kxrok?file=/index.js

@oliviertassinari please, can you provide the link to the actual issue?

@oliviertassinari please, can you provide the link to the actual issue?

https://github.com/mui-org/material-ui/issues?q=is%3Aissue+5.0.0-alpha.21+is%3Aclosed+label%3Aduplicate

https://github.com/mui-org/material-ui/issues?q=is%3Aissue+5.0.0-alpha.21+is%3Aclosed+label%3Aduplicate


Some addresses on explorer have wrong balance

https://navexplorer.com/address/NgsX4oTujuBfTNcoTxAtwUPhmE4MiSK8iW

Fixed with a script added to indexer via this commit https://github.com/navcoin/navexplorer-indexer-go/commit/f78a06f2ea5756116e68981604123ed775a34d34


[Bug]: race condition with cleanup and parallel

Description
It seems there's a race condition with cleaning up snapshots when using parallel tests that means if a snapshot changes there's a chance any of the snapshots in the same file could be duplicates, moved around, etc.
Steps to Reproduce
package main

import (
	"fmt"
	"math/rand"
	"os"
	"strings"
	"testing"
	"time"

	"github.com/gkampitakis/go-snaps/snaps"
)

var runCount = 2
var testsCount = 10

func init() {
	rand.Seed(time.Now().UnixNano())
}

var letters = []rune("abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ")

func randSeq(n int) string {
	b := make([]rune, n)
	for i := range b {
		b[i] = letters[rand.Intn(len(letters))]
	}
	return string(b)
}

func TestMain(m *testing.M) {
	for i := 0; i < runCount; i++ {
		code := m.Run()

		snaps.Clean(m, snaps.CleanOpts{Sort: true})

		b, err := os.ReadFile("__snapshots__/main_test.snap")

		if err != nil {
			if i == 0 {
				// ignore on the first run, since it should generate the snapshot
				continue
			}

			panic(err)
		}

		content := string(b)

		for i := 0; i < testsCount; i++ {
			header := fmt.Sprintf("[TestSnaps/#%02d - 1]", i)
			count := strings.Count(content, header)

			if count > 1 {
				code = 1

				fmt.Printf("Saw '%s' %d times\n", header, count)
			}
		}

		if code != 0 {
			os.Exit(code)
		}
	}

	os.Exit(0)
}

func TestSnaps(t *testing.T) {
	t.Parallel()

	type args struct {
		str string
	}
	type testCase struct {
		name string
		args args
	}

	tests := make([]testCase, 0, testsCount)

	for i := 0; i < testsCount; i++ {
		tests = append(tests, testCase{args: args{str: randSeq(10)}})
	}

	for _, tt := range tests {
		tt := tt
		t.Run(tt.name, func(t *testing.T) {
			t.Parallel()

			snaps.MatchSnapshot(t, tt.args.str)
		})
	}
}

Run with UPDATE_SNAPS=true go test ./...:
❯ UPDATE_SNAPS=true go test ./...
PASS

Snapshot Summary

✎ 10 snapshots added

PASS

Snapshot Summary

✎ 12 snapshots added
✎ 8 snapshots updated

Saw '[TestSnaps/#05 - 1]' 2 times
Saw '[TestSnaps/#08 - 1]' 2 times
FAIL    github.com/g-rath/go-snaps-testing      0.003s
FAIL

Running it multiple times will compound the result:
❯ UPDATE_SNAPS=true go test ./...
PASS

Snapshot Summary

✎ 7 snapshots added
✎ 3 snapshots updated

Saw '[TestSnaps/#01 - 1]' 3 times
Saw '[TestSnaps/#03 - 1]' 3 times
Saw '[TestSnaps/#04 - 1]' 2 times
Saw '[TestSnaps/#05 - 1]' 2 times
Saw '[TestSnaps/#06 - 1]' 2 times
Saw '[TestSnaps/#07 - 1]' 3 times
Saw '[TestSnaps/#08 - 1]' 4 times
Saw '[TestSnaps/#09 - 1]' 2 times
FAIL    github.com/g-rath/go-snaps-testing      0.004s
FAIL

Note that you can reproduce this without the looping, it just makes it a lot easier - but importantly my TestMain here is not interfering with the cleanup function.
Commenting out the t.Parallel calls resolves the issue
Expected Behavior
The snapshot order is stable, and snapshots are not duplicated.

it seems like this also might impact the general writing/updating of snapshots - I've been finding while working on https://github.com/google/osv-scanner/pull/889 that I have to run the suite twice to ensure all snapshots are updated

Hey 👋  sorry I have been off sick. But will have a look asap when I am back. Thanks for the investigation and creating this issue.

Hey no worries - you focus on getting better :)
For now I've written a python script that ill post shortly to do the sorting and cleanup

Hey I am partially back 😄 . I have rewritten this message three times thinking i knew what the problem is 😅 This time I think I know. I think the problem lies at https://github.com/gkampitakis/go-snaps/blob/main/snaps/snapshot.go#L131 not being protected with a lock. Will try to verify my theory the coming days and create a pr if you want to test it with. Needs some thinking the way I am handling locking there.
Again thank you for opening this issue and sorry for the inconvenience.

awesome stuff! fwiw this is the Python script I wrote:
#!/usr/bin/env python

import glob
import re

def deduplicate_snapshots(snapshots):
  by_name = {}

  for snapshot in snapshots:
    if snapshot[1] in by_name:
      are_identical = len(snapshot) == len(by_name[snapshot[1]]) and [
        i for i, j in zip(snapshot, by_name[snapshot[1]]) if i == j
      ]

      print(
        "  removed duplicate of",
        snapshot[1].strip(),
        "(were identical)" if are_identical else "",
      )
      continue
    by_name[snapshot[1]] = snapshot
  return by_name.values()

def sort_snapshots(snapshots):
  return sorted(
    snapshots,
    key=lambda lines: [
      int(x) if x.isdigit() else x for x in re.split(r"(\d+)", lines[1])
    ],
  )

def sort_snapshots_in_file(filename):
  snapshots = []
  snapshot = []

  with open(filename, "r") as f:
    for line in f.readlines():
      if line == "---\n":  # marks the start of a new snapshot
        snapshots.append(snapshot)
        snapshot = []
      else:
        snapshot.append(line)
  print("found", len(snapshots), "snapshots in", filename)

  snapshots = deduplicate_snapshots(snapshots)
  snapshots = sort_snapshots(snapshots)

  if filename.endswith("v_test.snap") or filename.endswith("v_test2.snap"):
    return
  with open(filename, "w") as f:
    for snapshot in snapshots:
      f.writelines(snapshot)
      f.writelines("---\n")

for snapshot_file in glob.iglob("**/__snapshots__/*.snap", recursive=True):
  sort_snapshots_in_file(snapshot_file)

(I want to share it somewhere since it won't even need to go into a PR now 😅)

Sorry for the need of the script. Hope the change solves this problem 😄 Feel free to reopen the issue if you still notice an error.


Twitter Sign in

Hey , i would like to work on twitter sign in/sign up  , i have worked on them before using react js and firebase hope you assign it to me and also add GSSoC tag Thanks !

Sure Go Ahead @hridhi

Hey, can I work on this as well?

Can i work on this @avinashkranjan ?

If @Jaagrav Isn't interested, I can assign it you..as the issues are FCFS..

Okay @avinashkranjan

Oh I'll make the PR soon @avinashkranjan

@Jaagrav , any update on this?

Sorry I am kinda busy with my exams, They'll be over by 30th so will work on Recess then... 😅

Sorry I am kinda busy with my exams, They'll be over by 30th so will work on Recess then... 😅
The code is ready, I need just need to make the PR the same for Facebook sign-in #117

Hey @Jaagrav , Please do it at the earliest.

@Utkarsh1999 @avinashkranjan Can i work on this ?


[TUBEMQ-548] Handle the LICENSE authorization of font files in the resources

Co-authored-by: zakwu<EMAIL_ADDRESS>

+1 pending on test results

+1 pending on test results

Codecov Report

Merging #415 (066c445) into master (02881c1) will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #415      +/-   ##
===========================================
+ Coverage      7.36%   7.40%   +0.03%
+ Complexity      474     472       -2
===========================================
  Files           268     268
  Lines         29922   29593     -329
  Branches       5020    4864     -156
===========================================
- Hits           2203    2190      -13
+ Misses        27240   26932     -308
+ Partials        479     471       -8

Impacted Files
Coverage Δ
Complexity Δ

...pache/tubemq/corebase/policies/FlowCtrlResult.java
0.00% <0.00%> (-60.00%)
0.00% <0.00%> (-1.00%)

.../apache/tubemq/corebase/policies/FlowCtrlItem.java
36.66% <0.00%> (-2.23%)
7.00% <0.00%> (-1.00%)

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
42.52% <0.00%> (-1.47%)
34.00% <0.00%> (ø%)

...er/master/web/handler/WebBrokerDefConfHandler.java
0.00% <0.00%> (ø)
0.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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

Codecov Report

Merging #415 (066c445) into master (02881c1) will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #415      +/-   ##
===========================================
+ Coverage      7.36%   7.40%   +0.03%
+ Complexity      474     472       -2
===========================================
  Files           268     268
  Lines         29922   29593     -329
  Branches       5020    4864     -156
===========================================
- Hits           2203    2190      -13
+ Misses        27240   26932     -308
+ Partials        479     471       -8

Impacted Files
Coverage Δ
Complexity Δ

...pache/tubemq/corebase/policies/FlowCtrlResult.java
0.00% <0.00%> (-60.00%)
0.00% <0.00%> (-1.00%)

.../apache/tubemq/corebase/policies/FlowCtrlItem.java
36.66% <0.00%> (-2.23%)
7.00% <0.00%> (-1.00%)

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
42.52% <0.00%> (-1.47%)
34.00% <0.00%> (ø%)

...er/master/web/handler/WebBrokerDefConfHandler.java
0.00% <0.00%> (ø)
0.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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


Improvements

Fixes #92
Skeleton for compaction handler.

Coverage remained the same at 100.0% when pulling a6f8f1801797b4777fb6a19459401b50cc7094e4 on FlorianLautenschlager:master into 04a772cd7d9c60b645b37067f935b3ce47701c8d on ChronixDB:master.


Table multiselect does not work

I cloned the react-toolbox-example. I then copied the code from the playground from http://react-toolbox.com/#/components/table. The multiselect works in the playground but not when it is copied to the example. Is the code base different in the playground compared to the main code base?

Ok, it works when I download the code and import from the Component directory but does not work when importing from lib, which means the lib code has not been generated as  yet.


Nuxt3 fresh project double render

Environment

Operating System: Windows_NT
Node Version:     v16.14.1
Nuxt Version:     3.1.2
Nitro Version:    2.2.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, runtimeConfig, experimental, vite, ignore, app, vue, components, typescript, css, hooks
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-9ukebr-bvynb9?file=nuxt.config.ts,app.vue,package.json
Describe the bug
App.vue and whole app renders twice on initial render, when u reload the whole page/server. That causes all the request through the whole app to launch at least twice or more.
It happens in the fresh nuxt app created by npx nuxi init as shown in reproduction link, so I think it's a bug inside nuxt3 itself.
Additional context
No response
Logs
No response

@danielroe sorry for pinging, but I think it can be crucial

I can't reproduce this. Note that sometimes stackblitz logs are confusing in this way. When I clone and run the reproduction locally there is only one request made.

What I've found is that if u start fresh starter project using npx nuxi init than inside app.vue file I'm getting double render, but when I create /pages directory and put at least 1 file with .vue extension than double render problem dissapears. Than when I put <NuxtPage /> component inside app.vue I'm getting double render again.
Is it not possible to have app.vue that renders pages and launch all the scripts that are necessary for initial app load?
Reproduction without pages
https://codesandbox.io/p/sandbox/objective-euler-98kgx8?file=%2Fapp.vue&selection=[{"endColumn"%3A1%2C"endLineNumber"%3A8%2C"startColumn"%3A1%2C"startLineNumber"%3A8}]
Reproduction with pages
https://codesandbox.io/p/sandbox/nice-sea-k59bid?file=%2Fpages%2Findex.vue&selection=[{"endColumn"%3A42%2C"endLineNumber"%3A8%2C"startColumn"%3A42%2C"startLineNumber"%3A8}]
Reproduction with NuxtPage
https://codesandbox.io/p/sandbox/condescending-hodgkin-obrtdz?file=%2Fpages%2Findex.vue&selection=[{"endColumn"%3A9%2C"endLineNumber"%3A5%2C"startColumn"%3A9%2C"startLineNumber"%3A5}]

Can you see if your browser is making two requests (as I think likely)? Maybe it's performing a hard reload of the page for some reason?

I have a similar problem，
I create a new project by npx nuxi init <project-name>, cd <project-name>andnpm run dev
I replace the <NuxtWelcome /> with Hello in app.vue, Browser displays Hello, but when I use F5 to refresh my browser, a momentary <NuxtWelcome />appears, and then Hello appears, Console got an error Hydration completed but contains mismatches.. I stop the project and run npm run dev again. Browser displays Hello normally.
Is this normal? Should I rerun this command every time after text content changed?

I think this should be resolved in the edge channel, or in the next release via https://github.com/nuxt/nuxt/pull/19179


OSE rebase proposal

@jupierce @stevekuznetsov @tdawson @bbguimaraes @smunilla

@stevekuznetsov @kargakis
I was discussing this with Jon Toppins (kernel dev) and he has seen a successful pattern that leverages a "branding branch" instead of using cherry-picks/tags. Not sure if this would be easier to reason about, but thought I'd bring it up.
 For CVEs, perhaps another release specific branch which could managed as a "layer" on top of branding.

@jupierce I'm not clear as to what that achieves that having branding commits in master and doing a rebase does not. Seems like it is roughly equivalent, but will also generate merge commits? The process I was considering was:
git clone<EMAIL_ADDRESS>pushd ose
git remote add upstream<EMAIL_ADDRESS>git fetch upstream
git checkout master
git rebase upstream/master

@stevekuznetsov .. yeah, merge commits aside, it looks like Jon's pattern collapses to yours.

@kargakis Since it seems like the rebase approach is workable, can the proposal be written to include "standard operating procedures" for the various eventualities? This would include what the automated and manual git steps are.
(1) What the nightly build looks like in terms of git steps.
(2) What cutting an OSE release looks like / corresponding steps in Origin (ongoing or one-time).
(3) What introducing a new branching change into OSE looks like.
(4) What introducing a CVE into OSE looks like.
(5) How to handle that CVE moving into origin (cherry picking from OSE?).
(6) What normal conflicts can arise / how to reconcile the conflict.
(7) What might go wrong if normal procedures aren't followed (e.g. someone doesn't follow the right procedure for (5)) / how to reconcile the conflict.

@jupierce I just pushed an update addressing most if not all comments from @stevekuznetsov. I agree that even more granularity in this proposal is needed so as part of my next push I will try to address your points, thanks.

@jupierce the card was focused on master -- do we want to address the CVE stuff and releases as well right now?

@jupierce the card was focused on master -- do we want to address the CVE stuff and releases as well right now?

IIUC the card is about proposing a mechanism that will address rebases on both master and the release branches. I don't mind exploring this in greater detail for the release branches.

@stevekuznetsov Unless it somehow explodes the scope, this seems like a good moment to ensure the entire OSE lifecycle is clean / automation friendly.

Thinking about this more, I don't think we need to do rebases for OSE release branches from Origin release branches. Since we don't need to update Origin release branches, we can simply:

rebase OSE master onto Origin master
rebase OSE latest_release_branch onto OSE master
the rebase process doesn't care about old release branches, fixes would continue to land there as today

Since we don't need to update Origin release branches,

Origin release branches get updated with CVEs and important bug-fixes. I'm not sure this holds.

Origin release branches get updated with CVEs and important bug-fixes

e.g.
https://github.com/openshift/origin/pull/12634
https://github.com/openshift/origin/pull/12606
https://github.com/openshift/origin/pull/12470
https://github.com/openshift/origin/pull/12263
https://github.com/openshift/origin/pull/12388
...

These land first in OSE though, right? So a mechanism that pulls them back
to Origin should be a separate thing and it's still not required to rebase
branches?
On Wed, Jan 25, 2017 at 3:40 PM, Steve Kuznetsov<EMAIL_ADDRESS>wrote:

Origin release branches get updated with CVEs and important bug-fixes
e.g.
openshift/origin#12634 https://github.com/openshift/origin/pull/12634
openshift/origin#12606 https://github.com/openshift/origin/pull/12606
openshift/origin#12470 https://github.com/openshift/origin/pull/12470
openshift/origin#12263 https://github.com/openshift/origin/pull/12263
openshift/origin#12388 https://github.com/openshift/origin/pull/12388
...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/aos-cd-jobs/pull/1#issuecomment-275124695,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADuFf4woDRRpJVMQDqaFTvqGwXpNQOpJks5rV17ngaJpZM4LnC3O
.

They land first in OSE, but I would expect us to rebase OSE release branches onto Origin release branches to keep the diff valid. Pulling them back is a manual process and will remain a manual process. Why would we not want to rebase release branches? I thought in all cases we were wanting to keep the diff on top of Origin minimal.

Since fixes land in OSE first, creating an admittedly complex process that
involves mapping commits by names and resolving conflicts seems to
outweight what we would gain by keeping the diffs minimal. I am not sure
that divergence (a commit in OSE lands in Origin slightly different) in
release branches is a real problem at all. I think simply rebasing the
latest OSE release branch against OSE master should do what we need.
On Wed, Jan 25, 2017 at 4:12 PM, Steve Kuznetsov<EMAIL_ADDRESS>wrote:

They land first in OSE, but I would expect us to rebase OSE release
branches onto Origin release branches to keep the diff valid. Pulling them
back is a manual process and will remain a manual process. Why would we not
want to rebase release branches? I thought in all cases we were wanting to
keep the diff on top of Origin minimal.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/aos-cd-jobs/pull/1#issuecomment-275133402,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADuFfyoLk0fpLQbS3DcnKRAx-PBsSXM3ks5rV2ZBgaJpZM4LnC3O
.

A situation I would like to avoid would look like:

bob adds a CVE fix to OSE release branch
bob backports this to Origin but for whatever reason needs to change it a little
we don't rebase the OSE release branch
joe adds a new CVE fix on top of bob's in the OSE release branch
joe can't cleanly backport his fix to Origin since it sits on top of the OSE version of joe's patch

@tdawson what are your thoughts? should we bother rebasing OSE release branches at all?

I don't see what rebasing released branches from Origin gives us.
For starters, we currently don't do it.  When was the last time we saw anything in the Origin 1.2 branch.  Yet we just released errata for OCP 3.2.  We have no plans to merge in the Origin 1.3.3 release because it only has a small percentage of the bugs fixed that are in OCP 3.3.
You need to keep in your mind that Origin does not support it's releases for the length of time that OCP does.
I think  @kargakis says it correctly.  It creates a very large level of complexity that totally throws away any benefit you get from doing what you have planned.

Cool. That makes it simpler. Only rebase on master and forget release branches. No need for complexity around dropping UPSTREAM commit as master should have none.

Updated the proposal with all latest comments.

After talking with @danmcp  today we now know we need some brand-less generic master and other branches that follow it for Online, OCP, Dedicated, maybe more. Sorry this comes really late in the game but I don't think we were aware of this until now.

@stevekuznetsov Make sure we loop in @tdawson on this.  It's possible some of these can be shared.

We ended up agreeing that this proposal is just for master and we already
strive for stripping away whatever we can. What do the new branches mean
for this proposal? I would expect them to be orthogonal to how we update
master.
On Tue, Feb 21, 2017 at 12:11 AM, Steve Kuznetsov<EMAIL_ADDRESS>wrote:

After talking with @danmcp https://github.com/danmcp today we now know
we need some brand-less generic master and other branches that follow it
for Online, OCP, Dedicated, maybe more. Sorry this comes really late in the
game but I don't think we were aware of this until now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/aos-cd-jobs/pull/1#issuecomment-281203133,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADuFf2S1W3rSngbAJ_EiUqafq19OZzd6ks5reh2xgaJpZM4LnC3O
.

But that is also just my view I think in reality we should choose whatever makes the process easiest.

Updated the proposal with feedback from the latest discussions with @stevekuznetsov @tdawson and @jupierce - the git commands are tentative but at least there is agreement into what we want to do.

@stevekuznetsov @jupierce @tdawson any final comments - this should be ready now

Proposal looks fine, lets get a MVP together

Updated the proposal with comments from https://github.com/openshift/aos-cd-jobs/pull/40

There seems to be consensus over this proposal so I am going to merge it, mainly because I want to use it as a link in sanity_check.py so when developers submit a PR in OSE master that is not following the naming requirements, they will get an error message pointing to this proposal. Additional comments can be addressed in separate PRs.


Failed compiling object src/Parser.o

I can compile neovim with homebrew.
I checked #44 for the troubleshooting but it did not help.
Here is the output of brew install --HEAD neovim --verbose:
Warning: falling back to curl - install luasec to get native HTTPS support

Missing dependencies for xml:
lub >= 1.0.3, < 2

Using https://rocks.moonscript.org/lub-1.0.7-1.src.rock... switching to 'build' mode
In file included from src/Parser.cpp:1:
In file included from include/xml/Parser.h:33:
In file included from src/bind/dub/dub.h:54:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/string:439:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/algorithm:628:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/memory:604:
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/iterator:341:10: fatal error: '__debug' file not found
#include <__debug>
         ^
1 error generated.

Error: Build error: Failed compiling object src/Parser.o
Updating manifest for /tmp/neovim20150417-51436-1jhfmux/.deps/usr/lib/luarocks/rocks
lub 1.0.7-1 is now built and installed in /tmp/neovim20150417-51436-1jhfmux/.deps/usr (license: MIT)

/usr/local/Library/ENV/4.3/clang -O2 -fPIC -I/tmp/neovim20150417-51436-1jhfmux/.deps/usr/include/luajit-2.0 -c src/Parser.cpp -o src/Parser.o -Iinclude -Isrc/bind -Isrc/vendor
make[3]: *** [usr/lib/luarocks/rocks/stable-busted-deps] Error 1
make[2]: *** [CMakeFiles/stable-busted-deps.dir/all] Error 2
make[1]: *** [all] Error 2
make: *** [deps] Error 2

See https://github.com/neovim/homebrew-neovim/issues/39#issuecomment-92319395.

thanks, it works like a charm! :)


CDK-938: Add kite-data-s3

This adds both s3n and s3a dataset URIs, s3n is working with a test.
Both URI patterns assume the bucket is the dataset repository.
Until a mock S3 service can be added, this expects real S3 credentials
and a bucket name passed as S3_ID, S3_KEY, and S3_BUCKET environment
variables. If those are not present, then the test will not run. To
disable tests for the hadoop1 and cdh4 profiles, the credentials are
explicitly set to empty.

Looks good to me, pending one naming point.

I've updated this in https://github.com/kite-sdk/kite/pull/356 with the renames, and also to allow a path in the S3 URI.


perf: reduce usage of Object.values

Did some profiling with a large number of dimensions in either Top or Left grid. The 3 calls that stood out as costly was calls to Object.values and toFixed, both methods where called for each cell in every react window list on every render.

For Object.values the solution was to use the already resolved listValues
There was no need to call toFixed everytime getRightGridColumnWidth was called. So simple moved that logic out

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Make sure IFileSystem is registered in DI during tests.

(for #8882)

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
~[ ] Has a news entry file (remember to thank yourself!)~
~[ ] Appropriate comments and documentation strings in the code~
~[ ] Has sufficient logging.~
~[ ] Has telemetry for enhancements.~
~[ ] Unit tests & system/integration tests are added/updated~
~[ ] Test plan is updated as appropriate~
~[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)~
~[ ] The wiki is updated with any design decisions/details.~

Codecov Report

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

@@            Coverage Diff             @@
##           master    #8902      +/-   ##
==========================================
- Coverage   57.95%   57.32%   -0.63%
==========================================
  Files         527      527
  Lines       27532    27204     -328
  Branches     4146     4146
==========================================
- Hits        15955    15595     -360
- Misses      10700    10731      +31
- Partials      877      878       +1

Impacted Files
Coverage Δ

...nt/datascience/jupyter/invalidNotebookFileError.ts
0% <0%> (-60%)
:arrow_down:

src/client/formatters/serviceRegistry.ts
50% <0%> (-50%)
:arrow_down:

...cience/jupyter/jupyterDebuggerNotInstalledError.ts
33.33% <0%> (-33.34%)
:arrow_down:

...jupyter/kernels/jupyterKernelPromiseFailedError.ts
0% <0%> (-33.34%)
:arrow_down:

...ent/datascience/jupyter/jupyterWaitForIdleError.ts
0% <0%> (-33.34%)
:arrow_down:

...ience/jupyter/jupyterDebuggerRemoteNotSupported.ts
50% <0%> (-30%)
:arrow_down:

src/client/testing/codeLenses/main.ts
42.85% <0%> (-27.15%)
:arrow_down:

...t/datascience/jupyter/jupyterDataRateLimitError.ts
50% <0%> (-25%)
:arrow_down:

.../client/datascience/jupyter/jupyterConnectError.ts
50% <0%> (-25%)
:arrow_down:

src/client/common/utils/icons.ts
75% <0%> (-25%)
:arrow_down:

... and 31 more

Continue to review full report at Codecov.

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


Fix test case file names

:tada: This issue has been resolved in version 0.30.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: