[SPARK-13838][SQL] Clear variable code to prevent it to be re-evaluated in BoundAttribute

JIRA: https://issues.apache.org/jira/browse/SPARK-13838
What changes were proposed in this pull request?
We should also clear the variable code in BoundReference.genCode to prevent it  to be evaluated twice, as we did in evaluateVariables.
How was this patch tested?
Existing tests.

cc @davies

Test build #52995 has started for PR 11674 at commit 0068ff8.

Test build #52995 has finished for PR 11674 at commit 0068ff8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52995/
Test PASSed.

cc @davies This is tiny. Do you think this is useful?

LGTM, merging into master.

who will re-evaluate ctx.currentVars?

If one variable is used as input to many expressions?

for example, spark.range(10).select('id + 1 as 'i).filter('i + 'i < 4). When the filter opetator consumes input, it already pre-evalute i, and 'id + 1 is only evaluated once, IIUC.

It is correct that we evaluate the variables before generating codes for bound attributes. The variables' codes are clear and won't be evaluated twice.
Here this is a safety guard that prevents possible missing, I think.

It's different from evaluateRequiredVariables, evaluateRequiredVariables pulls out the code to be evaluated and put it in the beginning of the generated code. However here we just clear the code, which looks unsafe. If we can't come up with a real case, shall we revert this?

Ok. I think it should be safe to revert this.

Thanks! Since it's a small change, we can do it in future whole-stage-codegen-related PRs.

Oh. I see. After looking at the source file at that time:
https://github.com/viirya/spark-1/blob/0068ff81bf9e90194ba9dc5631ac85683b9606f2/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/BoundAttribute.scala#L68-L70
The genCode method directly returns the code of the used currentVars. I guess the returned code might be pasted into generated code previously.
After iterations of revamping, this is not anymore.


Matrix calculator

Have you read the Contributing Guidelines ?
YES.
Description
It can do multiple operations such as (add, subtract, multiple, transpose) of 2-matrices.
Given the menu to let the user choose what operation he like first, then by choosing the number of operation he'll enter the dimensions of matrices and it's elements.
Fixes #495

Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Issue #495

@mohanadtalat91 It's been more than 15days but you didn't response so this PR gonna closed . Thanks .


Documentation: where to add the template

Sorry for the dumb question, but where is the template supposed to go? I tried placing it in configurations.yaml at the top level, under ecotrend_ista:, under sensor:, under platform: template and so on, everything throws errors. I was also unable to find any documentation in homeassistant itself about what to do with templates formatted in that kind.

Easily in the configuration.yaml file
Check: https://github.com/Ludy87/ecotrend-ista#basis-configuration

Doing that I get the following error:

                    Error loading /usr/lib/homeassistant/.homeassistant/configuration.yaml: while parsing a block mapping
  in "/usr/lib/homeassistant/.homeassistant/configuration.yaml", line 3, column 1
expected <block end>, but found '-'
  in "/usr/lib/homeassistant/.homeassistant/configuration.yaml", line 24, column 1

@jklmnn please take a screenshot of the configuration

I found the issue. The doc says that it has to start with a - while I had to remove it. So I got it working and my current configuration looks like this (see the missing - infront of template):
template:
  - sensor:
      - name: ECO Heizung Einheiten
        unit_of_measurement: "Einheiten"
 ...


Added CMMotionActivity support

As promised this is my CMMotionActivity support contribution. I had to make a few minor changes to the way you present the dialog for the permissions to avoid a "flash" that was happening when all permissions were satisfied and the dialog shouldn't appear.

This looks good, thanks! Where was the flash being seen? Device or sim?

Now that I'm integrating this into my app I'm also experiencing the flash issue with bluetooth.
The problem with bluetooth, and from what I saw, coremotion as well, is that to get the status you need to perform an async request. So when the show method is called the status is still .Unknown and therefore the alert is shown, but shortly afterwards (I found that for bluetooth about 10ms) the status is updated and the alert is dismissed (if previously accepted).
I've been thinking of a few different ways to solve this. Would be great to have some feedback.

The first measure we can take is on the addPermission method, as soon as bluetooth or coremotion are added, we can trigger the status update - so there is some extra time from that point until show is called.

Then we can either do what is already done here - delay the alert by some time in order for all statuses to update, or we can modify the statusForBluetooth (and motion) methods so they become synchronous and therefore wait for the status to be updated. <- This would involve moving a significant part of the code to a background thread and maybe making some methods require completion closures.

We can also delay the alert while we are still waiting for either bluetooth or coremotion to complete. (instead of a fixed amount of time).

Sorry I forgot to answer about the flash issue. Indeed this was happening when the dialog should not appear (conditions met) because the motion status check was an async request. This gave the time to the dialog to appear momentarily and then disappear resulting in a flash effect.
The way I solved this was:

The initial position of the dialog before transitioning is outside the visible window
I set a few seconds delay before starting the transition

@Navideck-fotis I did not try it, but from the changes you made I'm fairly confident it would solve it.

I like the way this is handled in #57 versus relying on the implementation in the app (which is what I think you're suggested?). It should be simple enough to duplicate the async detection similar to bluetooth. Fix that up and we can pull this in.

@nickoneill Done!
@felix-dumit Nice implementation! It should be bullet-proof this way.
I did my testing and everything works the same for me as before.

Thanks!


alpine for docker image

docker: switch to alpine for CI docker image

reduces image from ~37 MB to ~12 mb on the registry side (compressed)
reduces image from ~104 MB to ~30 mb on the local disk (uncompressed)

security: run lychee as non-root user
docs: add example about running lychee on Windows PowerShell
docs: add --rm flag to docker run command to remove container after the run (self-cleanup)
docs: add -w /input flag to docker run command to set working directory to /input

better UX when running lychee from docker locally (feeling like cli)

Thanks @DariuszPorowski,
that's a great achievement. I personally use the Debian image as a base for custom additions, so I'd prefer if the main image stayed Debian for that reason. However, what do you think about renaming the image, such that we could support both Debian and Alpine? E.g. how about lycheeverse/lychee:0.13-alpine for example? That's also how PHP does it. (Reference)

Love the idea, will update PR probably later today or tomorrow :)

@mre tried to figure out your current docker tags
current:
latest -> debian
master -> debian
0.13 -> debian
0.13.0 -> debian
sha-1234567 -> debian
proposal for alpine:
latest-alpine -> alpine
master-alpine -> alpine
0.13-alpine -> alpine
0.13.0-alpine -> alpine
sha-1234567-alpine -> alpine
Am I missed something? :)

Yes, that's perfect. 👏 Don't think you missed any tag.

@mre so, I think Pr is ready :)

Awesome. Just fixed a few typos (and added a comment for reference, in case you want to have a look). Other than that looks great! ✨ Merging!

@mre btw... just saw latest tag is bind to master branch, not sure it's the best approach ;) IMHO latest should point to the latest production release, so currently 0.13.0

🤔 you're probably right. Up for another pull request? 😅

@mre sure, but not this week, probably closer to end of the following one.

Of course, no rush. 👍


B13:  Taint outbreak:  Questions/suggestions

So, I got my first taint outbreak in 1.12.  Small outbreak that satisfied the flux research objective, right by my essentia smelter.  Fairly readily overcome with a good bow to kill the taint seed from a survivable distance.  I need to make a better bow though.
Observations:

Tainted soil is really hard to break.  Harder than obsidian.  Is it really meant to be that hard to break?  It's almost the only source I've found so far of vitium.  (Mycelium has vitium, but I haven't found any mycelium yet.)
Sand gets turned into tainted soil which, as the taint dies and fades, reverts back to ... dirt.  Perhaps there should be a separate tainted sand block as well?

Using a focus with plan and break or exchange is a good way to collect tainted soil pretty quickly. If you're using it, Tinkers Construct knightslime also makes short work of it, especially combined with haste modifiers.

Point 2 was discussed at #607 if you're interested.

This issue was moved to Azanor/thaumcraft-suggestions#377


Python36 enum34 issue

I'm attempting to build a project using the Python36 interpreter, and there's a package that calling for enum34, and I can't figure out how to prevent it from being installed. Any suggestion regarding which of the built in packages are calling for this or how to prevent it from being installed?
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/Users/jmeekho/projects/vof/mail-extract/build/venv/lib/python3.6/site-packages/setuptools/__init__.py", line 6, in <module>
        import distutils.core
      File "/Users/jmeekho/projects/vof/mail-extract/build/venv/lib/python3.6/distutils/__init__.py", line 4, in <module>
        import imp
      File "/Users/jmeekho/projects/vof/mail-extract/build/venv/lib/python3.6/imp.py", line 27, in <module>
        import tokenize
      File "/Users/jmeekho/projects/vof/mail-extract/build/venv/lib/python3.6/tokenize.py", line 33, in <module>
        import re
      File "/Users/jmeekho/projects/vof/mail-extract/build/venv/lib/python3.6/re.py", line 142, in <module>
        class RegexFlag(enum.IntFlag):
    AttributeError: module 'enum' has no attribute 'IntFlag'

plugins {
    id 'com.linkedin.python-cli' version '0.9.9'
}

python {
    testDir = file("tests")
    details.pythonVersion = '3.6'
    details.systemPythonInterpreter = '/usr/local/bin/python3.6'
}
project.tasks.findByName('installPythonRequirements').sorted = false

dependencies {
    python 'pypi:DateTime:4.3'
    python('pypi:exchangelib:1.12.1') {
        exclude module: 'enum34'
    }
}

repositories {
 ivy {
    name 'pypi-local'   //optional, but nice
    url './repo'
    layout "pattern", {
      ivy "[organisation]/[module]/[revision]/[module]-[revision].ivy"
      artifact "[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier]).[ext]"
      m2compatible = true
    }
  }
  pyGradlePyPi()
}

python.cli.generateCompletions = true

You can try finding if Gradle considers it a dependency, or one of your Python packages asks for it.
To look for it using Gradle try:
/path/to/gradlew dependencyInsight --configuration python --dependency enum34

Replace python with build, test, or setupRequires to check other configurations besides the runtime python configuration.
You can also check the Python package metadata:
cd build/venv/lib/python2.7/site-packages/
find . -type f -exec grep -H "Requires-Dist: enum34" {} \;

The output should show the conditional dependency only. For example:
./Sphinx-1.8.1.dist-info/METADATA:Requires-Dist: enum34; (python_version<"3") and extra == 'test'
./flake8-3.6.0.dist-info/METADATA:Requires-Dist: enum34; python_version<'3.4'

If you get an unconditional dependency on enum34, then that Python package needs to fix its metadata.
If you get the dependency through Gradle, and the build is failing because Gradle thinks it needs it as a dependency there may be some workarounds, but let's first see what is the package in question.
For what it's worth, we have internally at LinkedIn several plugins that deal with builds of products with multiple versions of Python. They provide features that allow:

declaring the versions of Python that library supports
declaring environment markers -- conditions under which the package is a dependency
automatic exclusion of known backports from Python 3 to 2, such as enum34
updates to DistGradle class used in setup.py to support these new features

We need to port these to open-source pygradle. Obviously, this is not going to happen overnight. They would certainly solve your issue, but until we port them we'll try to work around this with you, once we know what is the package causing this issue.

Thanks for the quick reply. What I'm seeing is that Flake is at fault here:
pypi:enum34:1.1.6
   variant "default" [
      org.gradle.status = integration (not requested)
   ]

pypi:enum34:1.1.6
\--- pypi:flake8:3.6.0
     \--- build

Workarounds:

Try putting in the python { ... } closure: forceVersion("pypi", "flake8", "3.2.1") if you can use lower version of flake8. It seems that versions below 3.3.0 did not have that dependency.
Alternatively, use older version of pygradle that did not update to flake8-3.6.0.

Notice that there's nothing wrong here with the flake8 itself. It declares the dependency conditionally in its Python package metadata. It's the Ivy format used by Gradle that has no notion of conditional dependencies that's at fault. So, the full solution would be porting our plugins mentioned above.
I hope this helps you.

Using an earlier forcedVersion did the trick. Thanks.
python {
    testDir = file("tests")
    details.pythonVersion = '3.6'
    details.systemPythonInterpreter = '/usr/local/bin/python3.6'
    forceVersion('pypi', 'flake8', '3.2.1')

}


refactor(shared-data): allow api level dependent flow rates

Recent hardware changes allow us to update the default flow rate for
Gen2 Single pipettes to 10mm/s plunger speed (resulting flow rate varies
per pipette class), including retroactively. To avoid changing user
protocols under them, this adds new data for the changed values:

flow rate values now can be organized in an object keyed with api
levels
this will eventually supercede the single-value structure
the api level 2.0 key is the "default", and should be used unless
operating at a higher api level for which there is a superceding value.

Review requests

Does this structure look good?  Nothing  uses this data yet (that'll be a follow up pr)
Do the values for api level 2.0 match the "value" defaults?
Are the 2.6 values properly twice the 2.0 levels, where they exist?

We either need to remove the ability to modify default flow rates in pipette settings

I think this is the path forward. Flow rate modification is a first-class feature in the protocol API.


Create colour palette document

Need to create a document that defines each of the colour palettes identified in the preprocessing script. What colours are they? Are they related to logos? Are they colour blind friendly?
@topherhuebel specifically requested this in the script.

This is a good point.
I find this site helpful for complementary palettes, and which includes colour blind simulations for each colour.
https://convertingcolors.com/


Render wiring diagrams using Graphviz

Generate Graphviz DOT files for abstract wiring diagrams.

The basic functionality is implemented. Some features are missing, like drawing outer boxes and nested wiring diagrams. I'll create a new issue for that.


[test-only][full-ci] added test to create odt file inside deleted parent folder

Description
Added test to create odt file inside a deleted parent folder.
Related Issue

https://github.com/owncloud/ocis/issues/9682

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[x] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[x] Acceptance tests added
[ ] Documentation ticket raised:

Lets wait for the PR https://github.com/owncloud/ocis/pull/9978 to get merged first.

LGTM :+1:


Cordova

Adds a phonegap folder with a phonegap sample project
Adds sending notifications to all other samples

what's the status of this

@helsont The status of this PR is that this works, but has not yet been reviewed/polished.  And actually merging this may still be a few months off as this project is relatively low priority.

Branches have been renamed; the retargetting Cordova sample to the 3.0 Beta


Seeking Assistance with Errors in Example Run

Hello,
I seem to have encountered some errors while running an example. Could you please advise on how to proceed?
Traceback (most recent call last):
File "/public/home/jyan/test.py", line 8, in
cp = CompetingPhases("ZrO2")
^^^^^^^^^^^^^^^^^^^^^^^
File "/public/home/jyan/anaconda3/lib/python3.11/site-packages/doped/chemical_potentials.py", line 395, in init
self.MP_full_pd_entries = mpr.get_entries_in_chemsys(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/public/home/jyan/anaconda3/lib/python3.11/site-packages/mp_api/client/mprester.py", line 1192, in get_entries_in_chemsys
self.get_entries(
File "/public/home/jyan/anaconda3/lib/python3.11/site-packages/mp_api/client/mprester.py", line 759, in get_entries
doc.model_dump()[property]  # type: ignore
~~~~~~~~~~~~~~~~^^^^^^^^^^
KeyError: 'pretty_formula'
Thank you for your time and assistance.

Hi @yanjin-tech
Are you using the new Materials Project API, rather than the legacy API? Doped currently only supports the old legacy API, see installation docs. This issue has been raised in the past and the response goes into detail explaining why we still use the legacy API.
Hope this helps!

As @adair-nicolson points out, this error is caused by using the new Materials Project API, for which doped is currently not compatible (though will be updated to also work with this in the near future). For now, I've updated our error catching to give a more informative error message when this issue occurs (https://github.com/SMTG-Bham/doped/commit/7577c5fd502fb3bbdcb5605025112154e3c092c0).
Closing this issue now as the problem has been addressed.

Thank you very much for your suggestions and assistance!


Compat: introduce a conditional to detect ActivityPub requests

Proposed changes:
This conditional could be used within the plugin, but also by third-party plugins, to detect whether a request is an ActivityPub request, without having to manually check for query vars and headers every time.
Other information:

[ ] Have you written new tests for your changes, if applicable?

Testing instructions:
This is better tested with a code snippet, just like a third-party plugin would use on their end. Something like this:
add_action(
	'wp',
	function () {
		if ( function_exists( '\Activitypub\is_activitypub_request' ) ) {
			error_log( 'the function exists' );
			if ( \Activitypub\is_activitypub_request() ) {
				error_log( 'This is an ActivityPub request' );
			}
		}
	}
);

Then make requests and see the output of the function:

Single posts
Single posts with a custom Accept: application/activity+json header.
Archive pages.

Maybe we could/should also use this function for the internal detection, to be consistant.
See: https://github.com/Automattic/wordpress-activitypub/blob/master/includes/class-activitypub.php#L37

Maybe we could/should also use this function for the internal detection, to be consistant.

Yeah, that seems like a good idea. I think we should do it in a follow-up PR though, since it will require refactoring that method. What do you think?

@jeherve fine!


Fix argument order in readme

I feel like I'm being monumentally stupid here but... aren't the arguments in the readme completely the wrong way round?

...plus the third one (dev/unicorn) seems to return false whichever way round it is.
I feel like I might be doing something wrong here?

Yup, you're right. And the reason dev/unicorn fails is because it matches from left to right.

Great, thanks for the quick response!


Largish commit. In essence it implements a couple of features. multip…

Details:
manifests/params.pp
manifests/init.pp
manifests/config.pp
    - $::redis::params::redis_init_template
      $::redis::params::redis_init_file_mode
      $::redis::redis_binary_path
      $::redis::redis_binary_name
      Running multiple instances will give a bunch of redis-server processes, unless the name of the binary has the name of the instance, it becomes very confusing to see what process is running which instance. This makes the output nice. We need to modify the init file in order to pass the instance name to e process name.
       ps: I don't have suse/bsd/debian to test on. this may be wrong for those platforms.

    - $::redis::params::slaveof_port
      Multiple instances run on different ports and need multiple entries for master/slave, thus, we need to move the slave port to be independent of the slave of host. This would need changes in existing configuration. if someone upgrades.

    - $::redis::params::client_output_buffer_limit_normal
      $::redis::params::client_output_buffer_limit_slave
      $::redis::params::client_output_buffer_limit_pubsub
      Made the output buffer limits configurable.

    - $::redis::params::instances
      Takes a hash of instances. All the config variables that can be tuned in config can be passed along with each instance. if nothing is passed. the redis defaults from params and config are observed.

    - $::redis::provider
      Allows one to overload the puppet provider in case you use a different one from the default puppet provider

    - $::redis::params::sentinel_init_template
      template/redis-sentinel.init.redhat.erb
      start-stop-daemon is not a CentOS thing, so we need a Redhat/CentOS specific init script.

manifests/sentinel.pp
    - $::redis::params::sentinel_log_file
      Sentinel needs its own log file and should not write to the same one as redis.

    - $::redis::instances
      Sentinel is configured with multiple instances. the name of sentinel master is the name of the instance.

    - $::redis::sentinel::members
      $::redis::params::sentinel_discover_master
      $::redis::params::sentinel_members
      $::redis::params::sentinel_multiple_instances
      Sentinel configuration is tricky, You can bake who the master is in the configuration, but as the infrastructure lives on, the reality of who the sentinel thinks is the master for an instance changes. With the discovered_master flag you can use a simple .erb script (discover_master.erb) to find out wholl the sentinel think the master is for a given instance. This allows you to reflect the current master in the sentinel configuration. If none of the sentinels are reachable or if the qourem is not reached, it defaults to the first item of $::redis::sentinel::members

Closing in favour of #200


Explicit many to many relationship typescript error during update

Bug description
Hi, Prisma team! I have error when trying to update supplier table alongside the bank accounts table that relate to it.
The error says that the ownerId is incompatible.
Previously I have also tried implicit many to many relationship and met with same error plus happen during create.
I did found an issue similar to mine on here https://github.com/prisma/prisma/discussions/10366.
Any help would be greatly appreciated, thank you in advance.
How to reproduce

Create suppliers and bank accounts schema
Create explicit many to many relationships between suppliers and bank accounts schema
Using prisma client to update supplier alongside bank account

Expected behavior
It should update the supplier data alongside bank account data that relate to it.
Prisma information
Prisma Schema
model Supplier {
  id String @id @default(cuid())

  handle String? @unique
  name   String?
  phone  String?
  email  String?

  avatarUrl         String?
  category          SupplierCategory?
  nationalTax       String?
  certificationFile String?

  // Relations
  ownerId            String?
  owner              Profile?                  @relation(fields: [ownerId], references: [id], onDelete: Cascade)
  addresses          Address[]
  supplierProducts   SupplierProduct[]
  businessOrderItems BusinessOrderItem[]
  bankAccounts       BankAccountsOnSuppliers[]

  // Timestamp
  createdAt DateTime @default(now())
  updatedAt DateTime @default(now()) @updatedAt

  @@map(name: "suppliers")
}

model BankAccount {
  id String @id @default(cuid())

  bankName          String
  accountNumber     String
  accountHolderName String

  suppliers BankAccountsOnSuppliers[]

  @@map(name: "bank_accounts")
}

model BankAccountsOnSuppliers {
  bankAccount   BankAccount @relation(fields: [bankAccountId], references: [id], onDelete: Cascade)
  bankAccountId String // relation scalar field (used in the `@relation` attribute above)

  supplier   Supplier @relation(fields: [supplierId], references: [id], onDelete: Cascade)
  supplierId String // relation scalar field (used in the `@relation` attribute above)

  @@id([bankAccountId, supplierId])
  @@map(name: "_bank_accounts_on_suppliers")
}

Prisma Client Update Query
 const payloadData = {
      name: supplier.name,
      handle: supplier.handle,
      phone: supplier.phone,
      category: supplier.category,
      nationalTax: supplier.nationalTax,
      certificationFile: supplier.certificationFile,
      ownerId: profileId,
      addresses: {
        update: {
          where: { id: prevSupplier.addresses[0].id },
          data: supplier.address,
        },
      },
      bankAccounts: {
        update: {
          where: { id: prevSupplier.bankAccounts[0].bankAccountId },
          data: supplier.bankAccount,
        },
      },
    }

    const updatedSupplier = await prisma.supplier.update({
      where: {
        handle: prevSupplier.handle,
      },
      data: payloadData,
      include: {
        owner: true,
        addresses: true,
        supplierProducts: true,
        bankAccounts: true,
      },
    })

Typescript Error
Type '{ name: any; handle: any; phone: any; category: any; nationalTax: any; certificationFile: any; ownerId: any; addresses: { update: { where: { id: string; }; data: any; }; }; bankAccounts: { update: { where: { id: string; }; data: any; }; }; }' is not assignable to type '(Without<SupplierUpdateInput, SupplierUncheckedUpdateInput> & SupplierUncheckedUpdateInput) | (Without<...> & SupplierUpdateInput)'.
  Type '{ name: any; handle: any; phone: any; category: any; nationalTax: any; certificationFile: any; ownerId: any; addresses: { update: { where: { id: string; }; data: any; }; }; bankAccounts: { update: { where: { id: string; }; data: any; }; }; }' is not assignable to type 'Without<SupplierUncheckedUpdateInput, SupplierUpdateInput> & SupplierUpdateInput'.
    Type '{ name: any; handle: any; phone: any; category: any; nationalTax: any; certificationFile: any; ownerId: any; addresses: { update: { where: { id: string; }; data: any; }; }; bankAccounts: { update: { where: { id: string; }; data: any; }; }; }' is not assignable to type 'Without<SupplierUncheckedUpdateInput, SupplierUpdateInput>'.
      Types of property 'ownerId' are incompatible.
        Type 'any' is not assignable to type 'never'.

Environment & setup

OS: MX Linux
Database: PostgreSQL
Node.js version: v14.18.2

Prisma Version
prisma                  : 3.5.0
@prisma/client          : 3.5.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 78a5df6def6943431f4c022e1428dbc3e833cf8e (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 78a5df6def6943431f4c022e1428dbc3e833cf8e (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 78a5df6def6943431f4c022e1428dbc3e833cf8e (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 78a5df6def6943431f4c022e1428dbc3e833cf8e (at<EMAIL_ADDRESS>Default Engines Hash    : 78a5df6def6943431f4c022e1428dbc3e833cf8e
Studio                  : 0.439.0

Sorry for the late reply here, but can you please share a complete reproduction. Right now values are missing from the calls so I can't reproduce the problem you are facing. Maybe share a small runnable script inside of Git repo for this purpose.

I am going to close this as its been 3 months now and there is no activity here.
Please reply if you want us to take another look.


Doesn't seem to work as expected

Image shows until the JS is loaded, at which point it disappears. Tested in IE11, IE10 and IE9.
No JS errors.

Same for me. When I run "objectFit.polyfill" (android phone native android browser (Mozilla/5.0 (Linux; U; Android 4.2.1; ru-ru; PAP7600DUO Build/JOP40D) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30)), the image just disappears from the DOM.

Duplicate of #38.


Where do you get all this data?

Hey, guys!
I wanted to make poe.filter syntax highlight for Atom just for fun and practice, but then discovered that you already made this great plugin!
My question is, where do you get all the data for completion and such? And are you typing it manually? That is such a massive amount of info, almost 2k lines.
Great work, nevertheless!

I copy/pasted a lot of it off the wiki and the main site and used fine/replace to reformat it. I still typed up quite a lot of it. No sure how Glen did the divination card part.
If you want to play around, you can use the stuff out of completion.coffee


added deno example and hosted it

This PR adds a hosted example using Deno. The README in the Deno dir should have all the info you need on hitting it.

There appears to be an issue with the API. When I've sent a request to the /register endpoint I got "Internal Server Error":
I am not sure what causes this behavior in the code.

oh heh,... probably should've said this won't work with web just yet. Can you run the expo client? It should work with that. If not, I'll update this server for web in this pr.

That makes sense, I don't have the environment to run the client right now.


Add navigate tool

Closes #155

Nice, this is awesome to have added!
Eventually it would be great to slightly refine this behavior and make it so zooming is relative to the position where you clicked down, and also a click without dragging should zoom in to the next increment (IncreaseCanvasZoom) while holding Shift and clicking does DecreaseCanvasZoom. Except unlike IncreaseCanvasZoom/DecreaseCanvasZoom it zooms relative to the place you click.
But we can make that refinement at a later time. Feel free to merge this whenever! (Hopefully it doesn't conflict too badly with #418, since we changed the way some messages interact with tools, take a look at the ToolMessageHandler changes from that PR.)


Fix forward reference issues with forward pointer

Fix for #429

Allows OpTypeForwardPointer to reference IDs not yet declared in
the module
Allows OpTypeStruct to reference IDs not yet declared in the
module

Possible Issue: OpTypeStruct should only allow forward references
if the ID is a pointer that is referenced by a forward pointer. Need
Type support in Validator which is currently a work in progress.

This is a correct relaxation of the rule.

Possible Issue: OpTypeStruct should only allow forward references
if the ID is a pointer that is referenced by a forward pointer.

Agreed.
We can tighten up the check here just a bit: OpTypeStruct word 0 can't be a forward reference since that's the result ID.  I'll do that in a followup CL.
+2

Rebased and pushed into master as a6ef1ea29

The result_id is not passed into that function but I guess it would be beneficial to handle all cases if this function was used elsewhere.

Never mind on this:

We can tighten up the check here just a bit: OpTypeStruct word 0 can't be a forward reference since that's the result ID. I'll do that in a followup CL.

Doesn't apply since the calling code only checks for Id parameters that are not result ids.  So there's no way to make a test case that triggers the difference.

... and now I see your comment from 4 minutes ago.  :-)


fix(nextjs): Stop ts errors for non-static nextjs typed routes in authMiddleware

Description

This PR reverts a change in the types that caused authMiddleware types to not accept anything except static routes when using the experimental typed routes feature in nextjs.

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[x] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Hiding page source from browser

How was hiding the page source from the browser achieved?
The aws cognito details (app id and user pool id) can be easily found from the browser by viewing the page source and navigating the javascripts. This is a security issue.
Thanks in advance.

Has this issue been resolved and then closed ?

No it has not been resolved. I opened a new issue and asked the question differently hoping that maybe someone will offer some guidance.


feat: Distinguish between reusable workflow inputs and trigger workflow inputs

closes https://github.com/slsa-framework/slsa-github-generator/issues/1737

@ianlewis any idea what's going on with pre-submit failures? We updated cosign or another dep recently I suppose. Not urgent to merge.

@ianlewis any idea what's going on with pre-submit failures? We updated cosign or another dep recently I suppose. Not urgent to merge.

Not sure. The only thing touching go.mod recently was the update to Go 1.20. Are the changes you made to go.mod on this PR necessary?

@ianlewis any idea what's going on with pre-submit failures? We updated cosign or another dep recently I suppose. Not urgent to merge.

Not sure. The only thing touching go.mod recently was the update to Go 1.20. Are the changes you made to go.mod on this PR necessary?

absolutely not. I must have tried something while in the wrong folder. Reverted.


Implement fallback MDC implementation for JUL

Part of https://github.com/elastic/apm-agent-java/issues/2492
Adds a fallback MDC implementation for JUL that can be instrumented by the Java agent.

Checklist

[ ] adding at least some comments to explain that the agent might rely on the code structure (the agent should test for that too)
[ ] how to properly size the custom MDC size and load factor ?

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-07-12T12:28:35.307+0000

Duration: 7 min 20 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
254

Skipped
0

Total
254

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@eyalkoren correct me if I'm wrong but I think the idea was to not rely on the MDC from slf4j at all anymore. Instead remove MdcSupplier and add a MDC class with static methods similar to org.slf4j.MDC.

@eyalkoren correct me if I'm wrong but I think the idea was to not rely on the MDC from slf4j at all anymore. Instead remove MdcSupplier and add a MDC class with static methods similar to org.slf4j.MDC.

Correct, that's the preferable option described in https://github.com/elastic/apm-agent-java/issues/2492#issue-1158621899, and the less preferable alternative described is to rely on slf4j MDC


N36: CyberGate

Part of #1098

is everything good now? @17cupsofcoffee

:construction:

I've rephrased a few things. @cybersoulK are you ok with my changes?

Thanks for the PR!


Add MLFlowLogger

I've just started using OML and I absolutely love it! (More questions are on the way...)
It'd be nice if it supported MLFlowLogger.
https://lightning.ai/docs/pytorch/stable/extensions/generated/lightning.pytorch.loggers.MLFlowLogger.html

@deepslug Use can use the following code example to add the mlflow logger to your pipeline:
import logging
import warnings

import hydra
from omegaconf import DictConfig
from oml.const import HYDRA_VERSION
from oml.lightning.pipelines.train import extractor_training_pipeline
from oml.registry.loggers import LOGGERS_REGISTRY
from pytorch_lightning.loggers import MLFlowLogger

logging.basicConfig(level=logging.INFO)

logger = logging.getLogger(__name__)

warnings.filterwarnings("ignore")

LOGGERS_REGISTRY["mlflow"] = MLFlowLogger

@hydra.main(
    config_path="./configs/",
    config_name="train_vit_mlflow.yaml",
    version_base=HYDRA_VERSION,
)
def main_hydra(cfg: DictConfig) -> None:
    logger.info("Training model.")
    extractor_training_pipeline(cfg)

if __name__ == "__main__":
    main_hydra()

Then add something similar to your config:
logger:
  name: mlflow
  args:
    experiment_name: "ViT_oml"
    run_name: "vit_log_artifacts"

@deepslug Thank you for using OML :) Waiting for your further questions
@Fissium Thank you so much for such a great answer! It's a valid approach, but it requires changing source code of the library (as you mentioned in the "final step"). To avoid this and make it available from pip, we need someone who can add this functionality to the repo. So, contributions are welcome :)

@Fissium
Thank you for your detailed answer! I've actually tried something similar and realized I had to modify parser.py, hence my question.
@AlekseySh
I'll post my question when I have everything sorted out.

@deepslug , great, thank you

@armored-guitar is going to work on this issue.


Cannot navigate to an https url.

Following the documentation does not work.
Please, see https://stackoverflow.com/questions/59587973/docker-unable-to-navigate-to-a-web-site-using-https OR https://social.msdn.microsoft.com/Forums/en-US/a64a99f2-b761-4ce3-b70e-2b2711c233f6/how-to-visit-a-url-using-https-from-a-windows-container?forum=windowscontainers
I have a feeling that no one in the whole world uses Windows Containers, at least not on Windows 10. Because no example I find on the internet works as expected.

@MarkKharitonov Thank you for the feedback and apologies for the documentation issues.
Please provide a link to document in question and we will assign this to an author for review.

https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/docker?view=azure-devops
When following the guide I had these problems:

Downloading agent failed because of the presence of zscaler in our environment. To make it work one needs to import the zscaler root certificate into the LocalMachine\Root certificate store in the container.
The user which PAT is used must be able to create agent pools and register agents. The documentation should emphasize it.


Why deprecating account_id on the provider?

Current Terraform and Cloudflare provider version
Terraform v1.2.3
on darwin_arm64

provider registry.terraform.io/cloudflare/cloudflare v3.17.0

Description
In a recent version, the provider marked account_id as being deprecated:

[account_id](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs#account_id) (String, Deprecated) Configure API client to always use a specific account. Alternatively, can be configured using the CLOUDFLARE_ACCOUNT_ID environment variable.

But when I remove it from the provider, my resources (e.g. cloudflare_account_member) is complaining that no account id is set:
│ Error: account ID is empty and must be provided
│
│   with cloudflare_account_member.platform_infra_team_members["XXXXXX"],
│   on users.tf line 158, in resource "cloudflare_account_member" "platform_infra_team_members":
│  158: resource "cloudflare_account_member" "platform_infra_team_members" {
│

And there is no way to set the account id on the cloudflare_account_member resource:
╷
│ Error: Unsupported argument
│
│   on users.tf line 135, in resource "cloudflare_account_member" "owners":
│  135:   account_id    = local.account_id
│
│ An argument named "account_id" is not expected here.

Use cases
Enforce the account ID of the cloudflare provider in a terraform workspace.
Potential Terraform configuration
provider "cloudflare" {
  account_id = "XXX"
}

resource "cloudflare_account_member" "example_user" {
  email_address =<EMAIL_ADDRESS>  role_ids = [
    "68b329da9893e34099c7d8ad5cb9c940",
    "d784fa8b6d98d27699781bd9a7cf19f0"
  ]
}

References
No response

this configuration sets the account value for all API calls and breaks partners and tentant usage.
resources will be adding more support the closer we get to 4.x

I don't understand. How are we supposed to remove the deprecated warning?

Plus one to adding account_id to cloudflare_account_member, there is no way to get around this deprecation. Also, seems like most resources are has an account_id attribute, so would be more consistent with the rest of the API.

The problem also occurs for cloudflare_access_rule when you want to make a rule that applies to the account.

yeah cloudflare_load_balancer_monitor is the same, documentation is not updated either anywhere

The problem also occurs for cloudflare_access_rule when you want to make a rule that applies to the account.

I am also affected by this. I was looking to transition from using account_id on the provider to on the cloudflare_access_rules but there isn't support for it yet.
This deprecation notice was implemented way too early. There should be an upgrade path in place if warnings are thrown for it.

Also getting a warning for cloudflare_argo_tunnel.  Both issues related to this are closed without being fixed.

Why would you ever mark a feature as deprecated without first providing an alternative? Baffling.

Hopefully a useful link for anyone searching for the deprecation warning on Google, check this issue instead: https://github.com/cloudflare/terraform-provider-cloudflare/issues/1646

3 months later, we still have no way to get rid of the warning on every plan and apply.


Add pmtiles extract command

It would be useful to be able to extract tiles from a pmtiles file for a certain area and put the extracted tiles into a new pmtiles file.
It could look something like this:
pmtiles extract input.pmtiles output.pmtiles --bounds "47.5,7.5,48.0,8.5"

A usecase could be to have a global tileset and allow users to download an extract for a city or so.

Maybe there is already a trivial way to do something like this with mbtiles tools like tile-join, but it would be super nice to be able to do this directly with pmtiles.

Yeah, this is not implemented yet for v3. The new design should allow for really efficient spatial extracts from remote archives, but the implementation will be a bit more complex.

I guess the Hilbert ordering of tiles helps with the efficient extracts, right? Where do you think will be the main complexity in implementing area downloads?

Can I help implementing an extract command?

Here is list of all the tasks I can think of right now:

[ ] extract should work with rectangular BBOX
[ ] extract should work with given polygon
[ ] extract should work with multipolygon
[ ] extract should find tileID coverings efficiently using boundary Hilbert algorithm
[ ] extract should batch together consecutive IO in clustered mode
[ ] extract should work with remote archives
[ ] when doing MVT extract should create masking features on tiles outside the query area
[ ] when doing PNG/WebP extract should create transparent mask on tiles outside query area
[ ] when doing JPEG extract should create black or chosen color mask on tiles outside query area

Cool, thanks for the list. What also could be nice is geofabrik-like area names, e.g. --area switzerland

What also could be nice is geofabrik-like area names, e.g. --area switzerland

Supporting the .poly format would allow for that. (They have the downloadable polygons in that format on Geofabrik.)

Haha my first go program!
	case "extract":
		var z uint8 = 14
		var x_min uint32 = 0
		var x_max uint32 = 10000 // included
		var y_min uint32 = 0
		var y_max uint32 = 10000 // included

		var tile_ids []uint64

		for x := x_min; x <= x_max; x++ {
			for y := y_min; y <= y_max; y++ {
				// fmt.Println(z, x, y, pmtiles.ZxyToId(z, x, y))
				tile_ids = append(tile_ids, pmtiles.ZxyToId(z, x, y))
			}
		}

		sort.Slice(tile_ids, func(i, j int) bool { return tile_ids[i] < tile_ids[j]})

		var tile_id_ranges [][2]uint64

		tile_id_ranges = append(tile_id_ranges, [2]uint64{tile_ids[0], tile_ids[0]})

		for i := 1; i < len(tile_ids); i++ {
			if tile_id_ranges[len(tile_id_ranges)-1][1] + 1 == tile_ids[i] {
				tile_id_ranges[len(tile_id_ranges)-1][1] = tile_ids[i]
			} else {
				tile_id_ranges = append(tile_id_ranges, [2]uint64{tile_ids[i], tile_ids[i]})
			}
		}

		fmt.Println(len(tile_ids))
		fmt.Println(len(tile_id_ranges))

It computes the ranges of tiles which lie in hilbert ordering inside a rectangle which is defined by a x, y bounding box. Running it at z14 for something which is almost as large as the planet takes like 20 seconds on my laptop...

https://github.com/wipfli/go-pmtiles/commit/16bea229f355545a2c36ee82db4cd9bec71a5fb3

I found a few snippets on how to write a .pmtiles file, but I am not sure how to read one. Can I use the code in loop.go for reading directory entries and tile data?

You should reuse the code in https://github.com/protomaps/go-pmtiles/blob/main/pmtiles/directory.go#L135 etc
loop.go isn't the best comparison, because that requires random access over an archive. for extracting you should only need to iterate over the entire directory once, so you can keep just one leaf in memory at a time instead of an LRU cache.

Thanks for the hint. It seems like show.go is a good starting point for reading .pmtiles as it uses also the deserialize function. At least I find there the logic for going from tile_id and .pmtiles file to the entry.
By the way, the z/x/y = 0/0/0 tile in my example archive has offset = 0. Does that mean that the first byte of the pmtiles file is where the 0/0/0 tile starts?

for tile entries (runlength > 0) the offset is relative to header.tile_data_offset

I don't quite understand yet how pmtiles works. Maybe you can help me with an example... Let's say I would like to extract a single tile tile_id from input.pmtiles and write it to output.pmtiles. What would be the main steps to do this?

The logic to extract a single tile is these lines in show.go: https://github.com/protomaps/go-pmtiles/blob/main/pmtiles/show.go#L126-L164
https://github.com/protomaps/go-pmtiles/blob/main/pmtiles/show.go#L144 is the point at which you know you have a matching tile in the archive and grab the bytes using TileDataOffset, and then can write It out on L154

https://github.com/protomaps/go-pmtiles/issues/20 is relevant so we can refactor the write logic out of convert.go

Can I suggest that it would also be nice if there was a --maxzoom option, similar to what is implemented in the python version, so that it would be possible to extract tiles down to a specific zoom level.


Move system-probe to cobra commands

What does this PR do?
It transitions system-probe to using cobra commands/subcommands versus plain flag usage.
Motivation
This is in preparation for adding subcommands to change runtime configuration and runtime debugging.
Additional Notes
The way to perform a couple actions has changed:

Running is now system-probe run (mirrors core agent)
Version information is accessed via system-probe version now.

Describe your test plan
system-probe should start and accept the same command line parameters as before (-config and -pid).

@albertvaka @hush-hush I ended up being able to make run the default subcommand if none is specified. I've removed the changelog warning since it will be backwards-compatible now.


Missing execution rights for robozonky.sh

After installing latest 4.1.0 snapshot via installer (mostly accepting defaults) and executing
./run.sh
./run.sh: line 4: /home/hrk/Tools/robozonky/Dist/robozonky.sh: Permission denied

I could work around that by by granting execute permission for robozonky.sh to my user.

Interesting. There's code in there that does exactly that. :-) I'll take a look, thanks for reporting!


dpcs: add project proposal template

Fixes #4
Proposed Changes

Add project proposal template.

Please review this pull request first.
@troyxiao @dy11
We will continue to write proposal based on this file.

I will merge this pull request directly because I want to continue work on the proposal.


Check problems with XSS filtering

The XSS filter sometimes prevents legitimate actions. It seems like the XSS filter needs some rework. We need to check where and what it filters and make sure that it doesn't filter too much. We also need to check if it is still up to date and can prevent current attacks. A unit test based on OWASP should be added.

[x] #822
[x] #864
[ ] #1339

#864 turned out not to be a XSS related problem and #822 is not reproducible, so seems already fixed.
Moving this to milestone 1.10.1. I'll leave it open, since the XSS filtering may turn out to become a bigger topic.


Support for BPF on ARM64

As it says in
https://docs.projectcalico.org/maintenance/enabling-bpf

eBPF mode only supports x86-64. (The eBPF programs are not currently built for the other platforms.)

This Issue is a place for people who want Calico to support BPF on ARM64 to add their vote.

It seems that preliminary work on this has begun: https://github.com/projectcalico/node/pull/1044/files

Just out of curiosity, what's the status on this after that last pull?
I'm on v3.20.1 but getting BPF dataplane mode enabled but not supported by the kernel.  Disabling BPF mode.
It seems the actual error from checking if BPF is supported is not actually logged - https://github.com/projectcalico/felix/blob/master/daemon/daemon.go#L339 - so it's hard to diagnose what the actual issue is. I do have BPF supported on the cluster (they are raspi 4s with a custom compiled kernel to ensure all the BPF flags) and the bpf filesystem is mounted.
Does the stub just need to be yanked out at this point, or is there more to do?


How scalable is collider?

Could anyone explain the apprtc architecture related to the collider & how well it scales?
Thanks

AppRTC runs on a Google App Engine instance and Collider runs on a couple of GCE VM's. Collider handles all the signalling via WebSockets between AppRTC clients.
It scales pretty well, we are using two instances for 2K+ calls a day and the load is very low (less than 1% on a 1 core, 3.75GB VM) hence it should be able to handle loads more.

Wow thats great. Thanks for the info!


feat: change process.env.VERCEL to process.env.VERCEL_URL in serverSchema

Is your feature request related to a problem? Please describe.
Zod validation object for serverSchema makes use of both VERCEL and VERCEL_URL environment variables for checking whether the user is deploying their app on vercel to preprocess the default value for NEXTAUTH_URL environment variable. Two files named with-auth-prisma.mjs and with-auth.mjs make use of this. Path to the files is this:-  cli/template/extras/src/env/schema/
This is what it currently looks like:-

Describe the solution you'd like to see
The environment variable VERCEL should be replaced by VERCEL_URL so that the vercel environment check works only against VERCEL_URL thus making serverSchema look more consistent.
This is what it should look like:-

Describe alternate solutions
Nope
Additional information
I have the changes ready for pull request just need your confirmation.

We could although it doesn't make a difference.


Unable to switch on Android Emulator from VS Code for a flutter project.

System used: Ubuntu 18.04
I use VS Code for flutter projects.
when I type
flutter emulators
my output is:

1 available emulator:

Pixel_API_27_oreo • Pixel API 27 oreo • Google • android

To run an emulator, run 'flutter emulators --launch <emulator id>'.
To create a new emulator, run 'flutter emulators --create [--name
xyz]'.

You can find more information on managing emulators at the links
below:
  https://developer.android.com/studio/run/managing-avds
  https://developer.android.com/studio/command-line/avdmanager

when I type
flutter emulators --launch Pixel_API_27_oreo
my output is:
The Android emulator exited with code 1 during startup
Android emulator stderr:
Address these issues and try again.

How do I solve this?
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.18.0-10.0.pre, on Linux, locale en_IN)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Android Studio (version 3.2)
[✓] VS Code (version 1.32.3)
[✓] Connected device (1 available)

• No issues found!

Can you try GenyMotion for your emulator? I am using that currently and it works flawlessly. No lag whatsoever. It will immediately be detected by Vscode through normal flutter run command.
https://www.genymotion.com/

Can you try GenyMotion for your emulator? I am using that currently and it works flawlessly. No lag whatsoever. It will immediately be detected by Vscode through normal flutter run command.
https://www.genymotion.com/

I think its paid right? any better way?

Can you try GenyMotion for your emulator? I am using that currently and it works flawlessly. No lag whatsoever. It will immediately be detected by Vscode through normal flutter run command.
https://www.genymotion.com/

I think its paid right? any better way?

Nope it isn't. I am using it currently with VSCODE. Just download the software and select personal use after you create an account. You can then choose whichever device you want and download that.
Once the emulator is running it will automatically be detected by VSCODE in the bottom right corner which will say the device name. Just run the flutter run command and your code will run on the emulator.

Hi @saurabhpetkar
Trying to remove the issue on latest master channel on PopOS linux and it launches emulator with no issues

flutter emulator --launch Nexus -v
tesser@pop-os:~/AndroidStudioProjects/master_app$ flutter emulator --launch Nexus -v
[   +9 ms] executing: [/home/tesser/Code/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +32 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 793e6a48a1e679074da7f47813c138abb2f0a6f6
[        ] executing: [/home/tesser/Code/flutter/] git tag --contains HEAD
[ +172 ms] Exit code 0 from: git tag --contains HEAD
[   +7 ms] executing: [/home/tesser/Code/flutter/] git describe --match *.*.*-*.*.pre --first-parent --long --tags
[ +133 ms] Exit code 0 from: git describe --match *.*.*-*.*.pre --first-parent --long --tags
[        ] 1.19.0-0.0.pre-26-g793e6a48a
[  +13 ms] executing: [/home/tesser/Code/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +6 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/master
[        ] executing: [/home/tesser/Code/flutter/] git ls-remote --get-url origin
[   +6 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +76 ms] executing: [/home/tesser/Code/flutter/] git rev-parse --abbrev-ref HEAD
[   +5 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] master
[  +48 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[   +7 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[  +38 ms] executing: /home/tesser/Code/SDK/emulator/emulator -list-avds
[  +15 ms] Exit code 0 from: /home/tesser/Code/SDK/emulator/emulator -list-avds
[        ] Nexus_4_API_29
[  +11 ms] executing: /home/tesser/Code/SDK/emulator/emulator -avd Nexus_4_API_29
[+3049 ms] "flutter emulators" took 3,131ms.
[  +81 ms] Android emulator stdout:
[        ] emulator: ERROR: Running multiple emulators with the same AVD is an experimental feature.
[        ] Please use -read-only flag to enable this feature.
[        ] The Android emulator exited with code 1
tesser@pop-os:~/AndroidStudioProjects/master_app$ flutter emulator --launch Nexus -v
[   +9 ms] executing: [/home/tesser/Code/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +28 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 793e6a48a1e679074da7f47813c138abb2f0a6f6
[        ] executing: [/home/tesser/Code/flutter/] git tag --contains HEAD
[ +168 ms] Exit code 0 from: git tag --contains HEAD
[   +7 ms] executing: [/home/tesser/Code/flutter/] git describe --match *.*.*-*.*.pre --first-parent --long --tags
[ +144 ms] Exit code 0 from: git describe --match *.*.*-*.*.pre --first-parent --long --tags
[        ] 1.19.0-0.0.pre-26-g793e6a48a
[  +14 ms] executing: [/home/tesser/Code/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +6 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/master
[        ] executing: [/home/tesser/Code/flutter/] git ls-remote --get-url origin
[   +4 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +55 ms] executing: [/home/tesser/Code/flutter/] git rev-parse --abbrev-ref HEAD
[   +6 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] master
[  +43 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[   +7 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[  +38 ms] executing: /home/tesser/Code/SDK/emulator/emulator -list-avds
[  +16 ms] Exit code 0 from: /home/tesser/Code/SDK/emulator/emulator -list-avds
[        ] Nexus_4_API_29
[  +22 ms] executing: /home/tesser/Code/SDK/emulator/emulator -avd Nexus_4_API_29
[+3044 ms] "flutter emulators" took 3,142ms.

flutter doctor -v
[✓] Flutter (Channel master, 1.19.0-1.0.pre.26, on Linux, locale en_US.UTF-8)
    • Flutter version 1.19.0-1.0.pre.26 at /home/tesser/Code/flutter
    • Framework revision 793e6a48a1 (30 hours ago), 2020-05-10 12:14:01 +0800
    • Engine revision 9b905d3f03
    • Dart version 2.9.0 (build 2.9.0-7.0.dev 617bc54b71)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /home/tesser/Code/SDK
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /home/tesser/Code/SDK
    • Java binary at: /home/tesser/Code/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Android Studio (version 3.6)
    • Android Studio at /home/tesser/Code/android-studio
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.45.0)
    • VS Code at /usr/share/code
    • Flutter extension version 3.10.1

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API
      29) (emulator)

• No issues found!

Can you please upgrade to latest master and delete this emulator and create a new emulator provide your flutter emulator --launch Pixel_API_27_oreo -v
Thank you

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.

I can't say for sure (since I am not @saurabhpetkar), but I think the error he had was:

[ +478 ms] Android emulator stdout:
[   +1 ms] emulator: ERROR: x86_64 emulation currently requires hardware acceleration!
[        ] Please ensure Windows Hypervisor Platform (WHPX) is properly installed and usable.
[   +6 ms] CPU acceleration status: HAXM is not installed on this machine
[   +2 ms] The Android emulator exited with code 1 during startup
[   +2 ms] Android emulator stderr:
[   +1 ms] Address these issues and try again.

The installation instructions do not mention that one needs to enable WHPX, and the default verbosity seems to exclude the crucial error message. That would seem like something of an oversight.

Could everyone who still has this problem please file a new issue with the exact description of what happens, logs and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.

If after doing flutter doctor -v  you happen to run across:
[!] Connected device
    • Device emulator-5554 is not authorized.
      You might need to check your device for an authorization dialog.

You may just need to enable usb debugging. Normally you should see a dialog that asks you to enabled it. I've seen that dialog flicker and then not reappear.
https://stackoverflow.com/questions/46898322/emulator-5554-unauthorized-for-adb-devices/51119381 should help with the issue if it is the same as the one I ran into.


Comma seperated list of Repos not working

I've set my repos with set -gx TTC_REPOS '/Users/Ste/react,/Users/Ste/valet' and it stops finding repos. Single folders seem to work.

Node Version: 10.9.0
tiny-core-terminal version: 1.4.1
Shell: fish
Terminal Program: iterm
Operating System: MacOS

Thank you!

:tada:

Could someone please confirm, that this is an issue on MacOS. Thx!

Could someone please confirm, that this is an issue on MacOS. Thx!


prevent KnifeItem being input into cutting board

Unless you have to cut knife....

Hello @aria1th,
Thanks you for the help, a new issue has been created to add a tag to prevent some items being placed on cutting board while they're in offhand, so the issue will be fix on the next release.


Remove flaky test

Per the tin
Motivation

Test started flaking recently
Test plan

See included automated tests.

I fixed this in a slightly different way in #5457.  I think it's valuable to have the verification that validating the exp file fails.

@froydnj thanks, closing this PR


Adds golintCI to travis job

What kind of PR is this?
/kind cleanup
What does does this PR do / why we need it:
It adds golangci-lint as a travis job
It also adds the golangci-lint as make target.
It also fixes the current lint errors in our code base.
Which issue(s) this PR fixes:
Fixes #1927
How to test changes / Special notes to the reviewer:
run golangci-lint run and check that no errors occur

/retest

Git commit message is blank and the PR description is very limited. Please update them both!
/hold

Git commit message is blank and the PR description is very limited. Please update them both!

@cdrage Fixed

E1104 09:01:02.793480   16615 occlient.go:2664] Command 'tar xf - -C /tmp/src --strip 1' in container failed.
[odo] E1104 09:01:02.793514   16615 occlient.go:2665] stdout:
[odo] E1104 09:01:02.793520   16615 occlient.go:2666] stderr: tar: /tmp/src: Cannot open: No such file or directory
[odo] tar: Error is not recoverable: exiting now
[odo]

/retest

Running oc with args [oc get pods --namespace drcyasvliu --selector=deploymentconfig=nodejs-push-atonce-nodejs-create-now-test -o jsonpath='{.items[0].metadata.name}']
[oc] 'nodejs-push-atonce-nodejs-create-now-test-1-6blpv'Running oc with args [oc exec nodejs-push-atonce-nodejs-create-now-test-1-6blpv --namespace drcyasvliu -c nodejs-push-atonce-nodejs-create-now-test -- ls -la /tmp/src/package.json]
[oc] ls: cannot access /tmp/src/package.json: No such file or directory

/retest

/hold cancel

Caching blobs under "/var/cache/blobs".
[odo] Warning: Pull failed, retrying in 5s ...
[odo] Warning: Pull failed, retrying in 5s ...
[odo] Warning: Pull failed, retrying in 5s ...
[odo] error: build error: After retrying 2 times, Pull image still failed due to error: while pulling "docker://image-registry.openshift-image-registry.svc:5000/openshift/php@sha256:d30db914ff173925adb9e3a65d61e863e19ea679d80fe91ab6ac3c99bc5c5ccb" as "image-registry.openshift-image-registry.svc:5000/openshift/php@sha256:d30db914ff173925adb9e3a65d61e863e19ea679d80fe91ab6ac3c99bc5c5ccb": Error initializing source docker://image-registry.openshift-image-registry.svc:5000/openshift/php@sha256:d30db914ff173925adb9e3a65d61e863e19ea679d80fe91ab6ac3c99bc5c5ccb: pinging docker registry returned: Get https://image-registry.openshift-image-registry.svc:5000/v2/: dial tcp <IP_ADDRESS>:5000: connect: no route to host

/retest

Caching blobs under "/var/cache/blobs".
[odo] Warning: Pull failed, retrying in 5s ...
[odo] Warning: Pull failed, retrying in 5s ...
[odo] Warning: Pull failed, retrying in 5s ...
[odo] error: build error: After retrying 2 times, Pull image still failed due to error: while pulling "docker://image-registry.openshift-image-registry.svc:5000/openshift/php@sha256:d30db914ff173925adb9e3a65d61e863e19ea679d80fe91ab6ac3c99bc5c5ccb" as "image-registry.openshift-image-registry.svc:5000/openshift/php@sha256:d30db914ff173925adb9e3a65d61e863e19ea679d80fe91ab6ac3c99bc5c5ccb": Error initializing source docker://image-registry.openshift-image-registry.svc:5000/openshift/php@sha256:d30db914ff173925adb9e3a65d61e863e19ea679d80fe91ab6ac3c99bc5c5ccb: pinging docker registry returned: Get https://image-registry.openshift-image-registry.svc:5000/v2/: dial tcp <IP_ADDRESS>:5000: connect: no route to host

/retest

@mik-dass This is network glitch. I have seen similar error in my previous minishift project

 Timed out after 600.000s.
    Running odo with args [odo service create -w dh-postgresql-apb --project vbnoqraanu --plan dev -p postgresql_user=luke -p postgresql_password=secret -p postgresql_database=my_data -p postgresql_version=9.6]
    Expected process to exit.  It did not.

/retest

/lgtm


refactor(transformer): remove no-op scopes code

#3210  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


BMSLD Updates

Renames fields and updates formatting
Moves functions from OSRR to MEDS

Unsure if keeping `reference[layer/actor]' is worthwhile. It feels very verbose.

Unsure if keeping reference[layer/actor] is worthwhile. It feels very verbose.
scenario.remove_entity({"layer": 9, "actor": "LE_GrappleDest_007"}) vs scenario.remove_entity(9, "LE_GrappleDest_007")

In this case the first variant is just an ugly way of providing two arguments as one argument to the method.
It only makes sense to me because it wouldn't require "unpacking" such things from an input json in the patcher. But as the schema validation guarantees that the keys exists in the dict from the input json, it is definitely better to unpack it in the patcher and use the second variant here because MEDS doesn't know anything about the schema.

So I should use the less verbose version here then? Or are you saying keep this in OSRR, which probably shouldn't happen?


[19.09] djvulibre: patching multiple CVEs

Motivation for this change
Addresses:
https://github.com/NixOS/nixpkgs/issues/73624
https://github.com/NixOS/nixpkgs/issues/70086

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @ckauhaus @Anton-Latukha

@GrahamcOfBorg build djvulibre

Merged into staging-19.09 due to the high number of rebuilds


visibleIf for checkbox questions

Hi,
Is it possible to somehow use contain-function for checkbox questions? I would like to show a question is one of the checkboxes is selected regardless of the other checkboxes.
For example, is it possible to modify the attached survey to show the age question for child number 1 regardless if other childs are selected?
example.txt
Thanks!
Samuli

Hi @samuliasmala,
I have just checked: visibleIf: "{haveKids}='Yes' and {kids} contains 3" works just fine.
Thank you,
Andrew

A bit embarrassing since I tried that but I had the 's' missing from contains... Big thanks for quick answer!
Best,
Samuli


[Bug]: Failed to launch the browser process!

Bug description
Steps to reproduce the problem:
I am having difficulty running puppeteer functions . I keep getting this error -
(node:13460) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!
/node_modules/puppeteer/.local-chromium/linux-970485/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
at onClose (/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:237:20)
at Interface.helper_js_1.helper.addEventListener (/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:227:68)
at Interface.emit (events.js:203:15)
at Interface.close (readline.js:397:8)
at Socket.onend (readline.js:173:10)
at Socket.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
(node:13460) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:13460) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I have tried installing all dependencies and all 1000 resolutions to disable sandbox and what not but no luck , i will be really glad if you can help me out with this error resolution.
Puppeteer version
13.5.1
Node.js version
17.0.0
npm version
6.14.4
What operating system are you seeing the problem on?
Linux, Windows
Relevant log output
node:13460) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!
/node_modules/puppeteer/.local-chromium/linux-970485/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

at onClose (/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:237:20)
at Interface.helper_js_1.helper.addEventListener (/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:227:68)
at Interface.emit (events.js:203:15)
at Interface.close (readline.js:397:8)
at Socket.onend (readline.js:173:10)
at Socket.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
(node:13460) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:13460) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

We encounter this issue aswell, while using mermaid-cli version ^8.13.5

/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:237
reject(new Error([
        Getting this anyone any luck so far ?

even i'm too facing the same error in Heroku

Same here on Netlify. It was working fine a couple of weeks ago.

Facing this issue too on Node 16 too using Puppeteer 16.1.0

Can't run my app in digital ocean "apps" because of this issue.

This issue indicates that your OS is missing the required dependencies for the Chromium binary. Please follow the troubleshooting.md guide linked in the error message to see which dependencies are missing.

Also please use our new Docker image that comes with the dependencies pre-installed https://github.com/puppeteer/puppeteer/pkgs/container/puppeteer

Hi @OrKoN unfortunately this would not work for me in my case as my Node image is provided by AWS Lambda. What would you advise in this situation?

@samdharris there are projects like chrome-aws-lambda that try to bundle all dependencies for AWS Lambda. In a nutshell, they built a custom chromium binary statically linking all dependencies https://github.com/alixaxel/chrome-aws-lambda/tree/master/_/ansible

same issue when using OS  (local)

I have the same problem on Digital Ocean Apps, trying to fix it.
Any solution?
2023-03-13T19:07:22.571255562Z /workspace/node_modules/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241
2023-03-13T19:07:22.571287294Z             reject(new Error([
2023-03-13T19:07:22.571295988Z                    ^
2023-03-13T19:07:22.571301598Z
2023-03-13T19:07:22.571307148Z Error: Failed to launch the browser process!
2023-03-13T19:07:22.571313908Z /workspace/node_modules/whatsapp-web.js/node_modules/puppeteer/.local-chromium/linux-982053/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
2023-03-13T19:07:22.571320003Z
2023-03-13T19:07:22.571324374Z
2023-03-13T19:07:22.571329591Z TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
2023-03-13T19:07:22.571334192Z
2023-03-13T19:07:22.571339065Z     at onClose (/workspace/node_modules/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20)
2023-03-13T19:07:22.571349144Z     at ChildProcess.<anonymous> (/workspace/node_modules/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:232:79)
2023-03-13T19:07:22.571362012Z     at ChildProcess.emit (node:events:525:35)
2023-03-13T19:07:22.571368445Z     at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)

it seems i'v been missing some packages, installing these fixed the issue :
sudo apt-get install ca-certificates fonts-liberation libappindicator3-1 libasound2 libatk-bridge2.0-0 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgbm1 libgcc1 libglib2.0-0 libgtk-3-0 libnspr4 libnss3 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 lsb-release wget xdg-utils

it seems i'v been missing some packages, installing these fixed the issue :
sudo apt-get install ca-certificates fonts-liberation libappindicator3-1 libasound2 libatk-bridge2.0-0 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgbm1 libgcc1 libglib2.0-0 libgtk-3-0 libnspr4 libnss3 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 lsb-release wget xdg-utils

In a similar way installing chromium installs the required dependencies (and a little more)


Sometimes Testem test fails with timeout

Sometimes Testem test fails with timeout
    ...
not ok 27 Firefox 48.0 - SyncedDB "after each" hook for "puts several already saved records in series"
    ---
        message: >
            timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
        Log: |
    ...
1..27
# tests 27
# pass  26
# skip  0
# fail  1
npm ERR! Test failed.  See above for more details.
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.
Done. Your build exited with 1.

I wonder if this is because the test case never finishes or if because executing the test takes longer than 2 seconds. Instead of giving a retry count me might try increasing the time given to each test unit.

Yes if actual duration of the tests takes more than 2 sec we should do that. But I also feel browser testing is not 100% stable. I'll investigate it anyway 👍

Recent builds do not contains this kind of failure. I'll close this for now.


Minor change in SERVER_API.md

It seems the below line was originally from the main repo's README file and that's the reason we have "(as above)" in the text.

After you have installed (as above)

As SERVER_API.md is made standalone now, it would be helpful by making reference to the installation steps in the main README file instead

Fixed by #175


feat: change findByKeyword to findByKeywords

BREAKING CHANGE: findByKeyword removed.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Blazor WASM hot reload and debugging

Fixes #28940
Artak ... This covers the following from the Preview 1 blog post remarks ...

Hot reload support for instance fields, properties, and events for .NET on WebAssembly
Support for symbol servers when debugging .NET on WebAssembly
Blazor WebAssembly debugging in Firefox

... but note that I couldn't find PU PRs for these. I don't have explicit instructions for how to use a symbol server to debug WASM apps outside of our normal VS guidance, so I currently have the PR point to the general guidance at ...
https://learn.microsoft.com/en-us/aspnet/core/test/debug-aspnetcore-source?view=aspnetcore-7.0
Also, don't sweat the version flipping at the top of the debugging article. I'll circle around and clean up the versioning later. I just haven't reached this one yet for a pass on that ... it's coming soon 🏃.
Last item ...... Firefox debugging ..... This will need a clean-up pass, possibly including for if VS can debug with FF using the same approach laid out for Chrome/Edge. I have a tracking item for it to circle back around to this guidance for futher updates later.
Tom, this touches your Hot Reload topic in the main doc set.

Internal previews

📄 File
🔗 Preview link

aspnetcore/blazor/debug.md
[Visual Studio for Mac](https://review.learn.microsoft.com/en-us/aspnet/core/blazor/debug?branch=pr-en-us-28953)

aspnetcore/test/hot-reload.md
.NET Hot Reload support for ASP.NET Core

@lambdageek Can you confirm that the list of supported hot reload edits on WebAssembly is accurate? Or are we at the point that hot reload on WebAssembly is at parity with CoreCLR and we no longer need to maintain a separate list of supported edits for .NET 8?

@lambdageek Can you confirm that the list of supported hot reload edits on WebAssembly is accurate? Or are we at the point that hot reload on WebAssembly is at parity with CoreCLR and we no longer need to maintain a separate list of supported edits for .NET 8?

We're almost at parity. The remaining things are:

Renaming method parameter (@fanyang-mono is working on it - https://github.com/dotnet/runtime/issues/56626)
The new stuff in .net8p4 isn't quite on par with coreclr (details offline)

I'll make a tracking note on ...

Renaming method parameter (@fanyang-mono is working on it - https://github.com/dotnet/runtime/issues/56626)

... to check back and update again after that's resolved.